Re: [Cerowrt-devel] dhcpv4 to slaac naming rfc ready to submit

[Simon Kelley <simon@thekelleys.org.uk>]

Looks good, I  just corrected a couple of typos.

Simon.

On 14/02/14 21:15, Dave Taht wrote:
>  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
> <mailto: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
>