IS-IS Registry Extension for Purges
RFC 6233

Note: This ballot was opened for revision 01 and is now closed.

(Ron Bonica) Yes

(Stewart Bryant) Yes

(Adrian Farrel) Yes

(Jari Arkko) No Objection

Comment (2011-02-17 for -)
No email
send info
Some comments from Ari Keränen who helped me in some of my reviews:

This document updates 3 RFCs, should say that in the abstract. Also LSP acronym should be expanded.

(Gonzalo Camarillo) No Objection

(Ralph Droms) (was Discuss) No Objection

Comment (2011-02-17)
No email
send info
I cleared my DISCUSS.

(Lars Eggert) No Objection

Comment (2011-02-15 for -)
No email
send info
Agree with Dan that this document should be on a telechat AFTER it
passes IETF last call (unless this is urgent in some way?)

Section 4., paragraph 1:
>    This document requests that IANA modify the IS-IS 'TLV Codepoints
>    Registry' by adding a column in the registry for 'Purge'.  A 'y' in
>    this column indicates that the TLV for this row MAY be found in a
>    purge.  A 'n' in this column indicates that the TLV for this row MUST
>    NOT be found in a purge.

  It would be slightly more self-explanatory if the registry column was
  titled "Allowed in Purge".

(Russ Housley) No Objection

Alexey Melnikov No Objection

(Tim Polk) (was Discuss) No Objection

(Dan Romascanu) No Objection

Comment (2011-02-14 for -)
No email
send info
I have no objection with approving the document as it stands right now but I observe that there is an IETF Last Call running for it and lasting six days after the IESG telechat date. I suggest that any approval be conditional, and in case substantial comments are submitted as Last Call comments after the IESG telechat they are brought to the attention of the IESG. 

(Peter Saint-Andre) No Objection

(Robert Sparks) No Objection

(Sean Turner) No Objection