Re: I-D ACTION:draft-rahman-rtg-router-alert-dangerous-00.txt
David Ward <[email protected]>
| Newsgroups | gmane.ietf.nsis,gmane.ietf.tsvwg |
|---|---|
| Message-ID | <[email protected]> |
The next rev of our draft will hopefully spell out what is f'bar in 2113 and an option to extend RAO for easier filtering based upon local client registration. We'll take all the help we can get. Should be out tomorrow and certainly discussed in MSP. -DWard On Nov 3, 2008, at 12:01 PM, Tony Li wrote: > > > |So obviously the whole thing has been messed up by imprecise > |specifications and weird implementation behavior. The question > |is really how to proceed now. > |a) Work on an update of RFC 2113, fixing specification flaws. > | This may cause inconsistent behavior between old implementations > | and new implementations following the new spec/RFC. > |b) Define a new RAO option type, this time with proper semantics, > | let alone existing implementations of the old RAO stuff. > | > |Please see also the "I hate Router Alert" slides (slide 13-) > |from Robert Hancock @IETF67 (Nov 2006): > |http://www.ietf.org/proceedings/06nov/slides/nsis-1/nsis-1.ppt > |So the issues of the last bullet on slide 25 are still unsolved > |(except for the IANA issues). > > > I'd be happy to help with this effort. > > Tony >