Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Evan Hunt <each@isc.org>, Simon Kelley <simon@thekelleys.org.uk>,
	Ted Lemon <mellon@fugue.com>,
	cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] dhcpv4 to slaac naming rfc ready to submit
Date: Fri, 14 Feb 2014 16:15:16 -0500	[thread overview]
Message-ID: <CAA93jw7=iVq-zFkMA-xqZVTJiX=ZR0su_e-nHp15KZYAE==HPQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]

I can't see anything else to add. Eyeballs and reviewers wanted!

http://snapon.lab.bufferbloat.net/~d/draft-taht-kelly-hunt-dhpv4-to-slaac-naming-00.html
 On Feb 4, 2014 10:43 AM, "Dave Taht" <dave.taht@gmail.com> wrote:

All:

I have been trying to get this off my plate for a while, this summarizes
the early discussion on the list:

http://snapon.lab.bufferbloat.net/~d/draft-taht-kelly-hunt-dhpv4-to-slac-naming-00.html

Ted:

This is my first ever RFC draft attempt, and if you can
suggest an RFC to model this on hopefully it can flow better?

Other suggestions welcomed. My other (overdue) RFCs are WAY more hairy
than this one...

evan: I have misplaced the isc-dhcpv4 code.

there needs to be a bind specific section also talking about
modern usage of nsupdate.

all: arguably this needs ascii art for the state machine

I found a nifty site for generating such and the pandoc2rfc engine
tolerates it.

http://www.asciiflow.com/#Draw

the git repo for all this is in:

https://github.com/dtaht/bufferbloat-rfcs

--
Dave Täht

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

[-- Attachment #2: Type: text/html, Size: 2018 bytes --]

             reply	other threads:[~2014-02-14 21:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-14 21:15 Dave Taht [this message]
2014-02-14 21:28 ` Simon Kelley
2014-02-14 23:27 ` Toke Høiland-Jørgensen
2014-02-15 15:28 ` Chuck Anderson
2014-02-17 10:11   ` Baptiste Jonglez
2014-02-17 23:01     ` Chuck Anderson

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='CAA93jw7=iVq-zFkMA-xqZVTJiX=ZR0su_e-nHp15KZYAE==HPQ@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=each@isc.org \
    --cc=mellon@fugue.com \
    --cc=simon@thekelleys.org.uk \
    /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