From: Aleksandar Kuktin <akuktin@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] RUDP and/or others
Date: Mon, 19 Oct 2015 21:29:21 +0200 [thread overview]
Message-ID: <20151019212921.78ec0412@ikilid> (raw)
In-Reply-To: <CAOw7k5ine2fAC1HmitO+Fg88YDrCp0M0RDD35WpNu1TAvFj5+g@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>On Mon, 19 Oct 2015 10:14:46 +0100
>Charles Forsyth <charles.forsyth@gmail.com> wrote:
>
> 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.
There are two RUDPs? O.o
> 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.
That's a good thing. The less flags and states, the better.
- --
Svi moji e-mailovi su kriptografski potpisani. Proverite ih.
All of my e-mails are cryptographically signed. Verify them.
- --
You don't need an AI for a robot uprising.
Humans will do just fine.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)
iQIcBAEBAgAGBQJWJUSRAAoJEKa4cgqNx31/aDYP/0AS8wyBKxnlkbwdWi8VT4+Z
/BbTfQa+nN5HcDPn1xI+2roFri+R8I/wqHMsSHHgTAbUMP7bar4L52aFY0yUXJiW
apmzyVzLHHBKXlmV15GAWoMWKTDstrmqArN0/xOMHys2ldyYn/chxlEBVjbKWSQD
nm96LLcKz5xDnTP0ebGg5v7P2YhIOMVCcwSyPfRDG04fY6T6HqkwfvFhnTiYhs/G
vghQJHYurF5SpcCE8KiCJgd3jnoNP+Rsm8WHdF6JCWU6jDeC16Gi3WOpIzEcFUGk
bP9HC7rB2CND8wmU1XZB1dvkLSP2OLxeR4CVZVItMoRB3HYJ0VarDxc8V4Vpst11
WVkFeSLci6VqGhAccQQCKW9kPmfo73UGZ0OXKfS+Nc4ZvDLGZ804UM9koTb5bP+C
KKTKBbYcqeKucfRAHZJ/TjsNju7zuEw1FZt/dxmjdIqrGcP3ryAFeBMfsd7ZlKZu
mHWj7oP3ipJZJS0gvtRRHBQSvRsrQ3LwAwtlKBqpXCeFyqhkh/H5TM1ji+emJ2SN
buJiCn7+1IUsy26C4lToYA9RDd52zpSaOGBDGZ+j4ol0fkfap6uM2ncUBhjfhZWs
dSITGTpWkblpcxAphMw2SdgDqcAW3p348wcdqlgaMGI2O9PDR9LL5rsBbR3Xl6RJ
XKZVPi/IAEA1eURGPGVq
=dNnW
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-10-19 19:29 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
2015-10-19 19:29 ` Aleksandar Kuktin [this message]
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=20151019212921.78ec0412@ikilid \
--to=akuktin@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).