9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] rudp
Date: Sun,  9 Sep 2001 21:46:04 -0400	[thread overview]
Message-ID: <20010910014607.248C4199D5@mail.cse.psu.edu> (raw)

An rudp channel really is a datagram channel.  Packets are
separately addressed by the user program so that one fd
can be used to maintain conversations with multiple other
end points.  IL is one to one.

IL does have flow control, Rudp doesn't.

Rudp has no keep alive, IL does.

IL does some small amount of congestion control by measuring the
bandwidth delay product of the connection, Rudp doesn't care.

Rudp connections don't hangup when one of the sides reboots, it
just flushes any undelievered messages to that side (and the side(s)
that stays up can know that there was a restart by looking at the error
file).

We used rudp as the protocol between things like controllers
and devices that they control.  For example, between a switch
and a switch controller in a telephony product.

Rudp is just udp with a some extra bytes.  It was originally
done as an option on udp and we later just made it a
separate protocol.  It's protocol number is not registered
witn IANA.


             reply	other threads:[~2001-09-10  1:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-10  1:46 presotto [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-15 16:55 andrey mirtchovski
2002-04-15 15:31 rog
2002-04-15 15:21 Russ Cox
2002-04-15 14:58 andrey mirtchovski
2001-09-08 17:52 bwc
     [not found] <ehg@research.bell-labs.com>
2001-09-08 16:59 ` Eric Grosse
2001-09-10  1:33   ` Scott Schwartz
2001-09-10 18:58   ` Boyd Roberts
2001-09-08 15:48 Sam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010910014607.248C4199D5@mail.cse.psu.edu \
    --to=presotto@plan9.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).