Purge Originator Identification TLV for IS-IS
draft-ietf-isis-purge-tlv-05
Yes
(Adrian Farrel)
(Ron Bonica)
(Stewart Bryant)
No Objection
(Alexey Melnikov)
(Gonzalo Camarillo)
(Lars Eggert)
(Peter Saint-Andre)
(Robert Sparks)
(Russ Housley)
(Tim Polk)
Note: This ballot was opened for revision 05 and is now closed.
Adrian Farrel Former IESG member
Yes
Yes
()
Unknown
Ron Bonica Former IESG member
Yes
Yes
()
Unknown
Stewart Bryant Former IESG member
Yes
Yes
()
Unknown
Alexey Melnikov Former IESG member
No Objection
No Objection
()
Unknown
Dan Romascanu Former IESG member
No Objection
No Objection
(2011-02-14)
Unknown
> This document requests that IANA assign code point 13 for the 'Purge Originator Identification' TLV from the IS-IS 'TLV Codepoints Registry'. The additional values for this TLV should be: IIH:n, LSP:y, SNP:n, Purge:y. I assume that this is OK with this document but usually an Internet-Draft cannot / should not make a request for a specific value, but just require a code point value and recommend that this value be 13.
Gonzalo Camarillo Former IESG member
No Objection
No Objection
()
Unknown
Jari Arkko Former IESG member
No Objection
No Objection
(2011-02-17)
Unknown
Some comments from Ari Keränen who helped me in some of my reviews today: Abstract This document updates 3 RFCs, should say that in the abstract. Also LSP acronym should be expanded.
Lars Eggert Former IESG member
No Objection
No Objection
()
Unknown
Peter Saint-Andre Former IESG member
No Objection
No Objection
()
Unknown
Ralph Droms Former IESG member
No Objection
No Objection
(2011-02-16)
Unknown
Balloting no objection assuming there is an easy answer to my question (posted to draft-ietf-isis-reg-purge-00) about the IANA ISIS-TLV registry and notifying ISO JTC1.
Robert Sparks Former IESG member
No Objection
No Objection
()
Unknown
Russ Housley Former IESG member
No Objection
No Objection
()
Unknown
Sean Turner Former IESG member
No Objection
No Objection
(2011-02-16)
Unknown
Please add a pointer for where I can find the definition of system ID.
Tim Polk Former IESG member
No Objection
No Objection
(2011-02-16)
Unknown
In the Intro, this document states: Field experience has observed several circumstances where an IS can improperly generate a purge. These are all due to implementation deficiencies or implementations that predate [ISO TC1] and generate a purge when they receive a corrupted LSP. In the security considerations, it is noted that: Therefore, all implementations in a domain implementing authentication MUST be upgraded to receive the POI TLV before any IS is allowed to generate a purge with the POI TLV. Since you need to touch every ISIS implementation in the domain anyway, is it worth stating that implementations SHOULD be updated for consistency with [ISO TC1] (i.e., and not generate a purge when they receive a corrupted LSP) at the same time?