Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Dave Taht <dave.taht@gmail.com>
Cc: Andrew McGregor <andrewmcgr@gmail.com>,
	"babel-users@lists.alioth.debian.org"
	<babel-users@lists.alioth.debian.org>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	Felix Fietkau <nbd@nbd.name>
Subject: Re: [Cerowrt-devel] [Babel-users] more wet paint - babel unicast IHU for short-rtt path optimization
Date: Tue, 07 Apr 2015 22:52:57 +0200	[thread overview]
Message-ID: <87sicbfyom.wl-jch@pps.univ-paris-diderot.fr> (raw)
In-Reply-To: <CAA93jw4Hv--0B3mNXLg9Nj7cuo+EexbudKr566qcXAFH=cru0A@mail.gmail.com>

> A timestamp is not defined for updates, presently.

No.  Only Hellos are timestamped, and no unicast Hello is defined currently.
(IHUs carry timestamp echos.)

> Do you fragment?

We don't need to -- the largest possible update is on the order of 100 octets,
and we assume that we can send 512 octets without fragmentation.

> Would an IHU be bundled with an update?

It could be, but unless it's bundled with a Hello, an IHU's timestamp echo
is ignored (read Jonglez-Boutier-Chroboczek again to see why).  And Hellos
cannot be unicast.

-- Juliusz

      reply	other threads:[~2015-04-07 20:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-07 18:56 [Cerowrt-devel] " Dave Taht
2015-04-07 20:28 ` [Cerowrt-devel] [Babel-users] " Juliusz Chroboczek
2015-04-07 20:44   ` Dave Taht
2015-04-07 20:52     ` Juliusz Chroboczek [this message]

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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=87sicbfyom.wl-jch@pps.univ-paris-diderot.fr \
    --to=jch@pps.univ-paris-diderot.fr \
    --cc=andrewmcgr@gmail.com \
    --cc=babel-users@lists.alioth.debian.org \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=nbd@nbd.name \
    /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