Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Cc: babel-users@lists.alioth.debian.org, cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] [Babel-users] Babel extension mechanism
Date: Thu, 27 Jun 2013 10:31:00 -0700	[thread overview]
Message-ID: <CAA93jw5czkgxfuSSUprk=rdpH37TEULM3tLWN5B8Q5sksVPxFA@mail.gmail.com> (raw)
In-Reply-To: <7ihagjttv2.wl%jch@pps.univ-paris-diderot.fr>

On Thu, Jun 27, 2013 at 9:13 AM, Juliusz Chroboczek
<jch@pps.univ-paris-diderot.fr> wrote:
> Dear all,
>
> I've finally written up the Babel extension mechanism; a first draft
> is available on
>
>   http://www.pps.univ-paris-diderot.fr/~jch/software/babel/draft-chroboczek-babel-extension-mechanism.html

What tool are you using? Very pretty results. (I ask because I too am
in RFC hell)

>   http://www.pps.univ-paris-diderot.fr/~jch/software/babel/draft-chroboczek-babel-extension-mechanism.txt

Two quick notes: "Silently ignored" implies that the presence of this
tlv in the packet is ignored, when in fact it is silently parsed as to
length and skipped...

"Silently skipped", perhaps?

Also http://tools.ietf.org/html/rfc6126 is an *expired* draft. It
probably would be best (not my call, bounce it off the right ADs) to
update that and merge in with this mechanism, bringing it back into
currency, rather than do it separately. That said there are multiple
edits to rfc6126 I'd like to see, and defining the extension mechanism
is a clean addition rather than an edit, soo... gah...


> The registry of known TLV and sub-TLV types is on
>
>   http://www.pps.univ-paris-diderot.fr/~jch/software/babel/babel-tlv-registry.text

Heh. I'd have skipped the number "13" for superstitious reasons, but I
look forward to seeing that tlv tried.

one piece of data I've longed to have is gps-related data
(lat/long/height/motion).

Similarly, connectivity stats (endpoint, speed, current bandwidth
usage) harvested from minstrel and elsewhere.

Another is carrying the mtu of a given gateway, for example mtu 1480
for a 6in4 connection to the outside world saves on pmtu one way.

> I hope to do something with this (hopefully an experimental RFC), so
> please take the time to review it.


> Thanks,
>
> -- Juliusz
>
> _______________________________________________
> Babel-users mailing list
> Babel-users@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users



-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

       reply	other threads:[~2013-06-27 17:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7ihagjttv2.wl%jch@pps.univ-paris-diderot.fr>
2013-06-27 17:31 ` Dave Taht [this message]
2013-07-02  0:07   ` Juliusz Chroboczek

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='CAA93jw5czkgxfuSSUprk=rdpH37TEULM3tLWN5B8Q5sksVPxFA@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=babel-users@lists.alioth.debian.org \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=jch@pps.univ-paris-diderot.fr \
    /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