From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] RUDP and/or others
Date: Mon, 19 Oct 2015 10:14:46 +0100 [thread overview]
Message-ID: <CAOw7k5ine2fAC1HmitO+Fg88YDrCp0M0RDD35WpNu1TAvFj5+g@mail.gmail.com> (raw)
In-Reply-To: <20151019004356.3b020ab3@ikilid>
[-- Attachment #1: Type: text/plain, Size: 698 bytes --]
On 18 October 2015 at 23:43, Aleksandar Kuktin <akuktin@gmail.com> wrote:
> BAM! I run straight into RUDP. "Designed at Bell Labs for the Plan 9
> operating system". I just skimmed through the (expired) IETF draft from
> 1999 and I honestly think the design might be too much. It looks like
> it's almost completely like TCP, but without segmenting and possibly
>
The Cisco RUDP defined in the IETF draft is not the rudp in the Plan 9 code.
Both use a UDP shell to carry their packets, but the two RUDP headers are
different.
The protocols seem to be unrelated. The Cisco one is derived from an
earlier BBN one,
and all three had the tcp-like SYN/ACK/RST flags. Plan 9's does not.
[-- Attachment #2: Type: text/html, Size: 1154 bytes --]
next prev parent reply other threads:[~2015-10-19 9:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-18 22:43 Aleksandar Kuktin
2015-10-18 22:48 ` Aleksandar Kuktin
2015-10-19 0:05 ` erik quanstrom
2015-10-18 23:15 ` Skip Tavakkolian
2015-10-18 23:59 ` erik quanstrom
2015-10-19 0:09 ` Kurt H Maier
2015-10-19 0:35 ` erik quanstrom
2015-10-19 0:48 ` Kurt H Maier
2015-10-19 9:28 ` hiro
2015-10-19 20:42 ` Aleksandar Kuktin
2015-10-19 19:36 ` Aleksandar Kuktin
2015-10-19 20:53 ` Aleksandar Kuktin
2015-10-19 19:31 ` Aleksandar Kuktin
2015-10-19 20:57 ` Aleksandar Kuktin
2015-10-19 21:17 ` Charles Forsyth
2015-10-19 9:14 ` Charles Forsyth [this message]
2015-10-19 19:29 ` Aleksandar Kuktin
2023-05-10 22:33 [9fans] Romano
2023-05-10 22:36 ` [9fans] RUDP and/or others unobe
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=CAOw7k5ine2fAC1HmitO+Fg88YDrCp0M0RDD35WpNu1TAvFj5+g@mail.gmail.com \
--to=charles.forsyth@gmail.com \
--cc=9fans@9fans.net \
/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).