The EAP Re-authentication Protocol (ERP) Local Domain Name DHCPv6 Option
RFC 6440

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

(Stephen Farrell) Yes

Comment (2011-03-31 for -)
No email
send info
Taking this over from Tim

(Tim Polk) Yes

(Jari Arkko) No Objection

Comment (2011-03-03 for -)
No email
send info
I agree with others that the document must be changed so that its title, abstract, and the option name match the use for ERP. This is not about general domains (e.g., DNS).

(Ron Bonica) No Objection

(Stewart Bryant) No Objection

(Gonzalo Camarillo) No Objection

(Ralph Droms) (was Discuss, No Objection) No Objection

Comment (2011-05-06)
No email
send info
Based on the edited text in -10, I've cleared my Discuss.

(Lars Eggert) No Objection

(Adrian Farrel) No Objection

Comment (2011-03-01 for -)
No email
send info
Acronyms need to be expaneded on first use in the body of the document. 
For example, EAP, DSRK, etc.

(Russ Housley) No Objection

Alexey Melnikov No Objection

(Dan Romascanu) No Objection

(Peter Saint-Andre) (was Discuss) No Objection

Comment (2011-03-02 for -)
No email
send info
1. Please spell out FQDN and other relevant acronyms (e.g., perhaps AAA) on first use.

2. Section 5 has "DHPv6" instead of "DHCPv6".

3. The apps-review team review raised the following issue:

   This document also specifies a length limitation of 256 octets that does
   not take into account issues raised by RFC 4282.  My recommendation
   would be to either match or reference the text in RFC 4282.

(Robert Sparks) No Objection

(Sean Turner) (was Discuss) No Objection