The EAP Re-authentication Protocol (ERP) Local Domain Name DHCPv6 Option
RFC 6440
Yes
No Objection
Note: This ballot was opened for revision 10 and is now closed.
Lars Eggert No Objection
(Stephen Farrell; former steering group member) Yes
Taking this over from Tim
(Tim Polk; former steering group member) Yes
(Adrian Farrel; former steering group member) No Objection
Acronyms need to be expaneded on first use in the body of the document. For example, EAP, DSRK, etc.
(Alexey Melnikov; former steering group member) No Objection
(Dan Romascanu; former steering group member) No Objection
(Gonzalo Camarillo; former steering group member) No Objection
(Jari Arkko; former steering group member) No Objection
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).
(Peter Saint-Andre; former steering group member) (was Discuss) No Objection
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.
(Ralph Droms; former steering group member) (was Discuss, No Objection) No Objection
Based on the edited text in -10, I've cleared my Discuss.
(Robert Sparks; former steering group member) No Objection
(Ron Bonica; former steering group member) No Objection
(Russ Housley; former steering group member) No Objection
(Sean Turner; former steering group member) (was Discuss) No Objection
(Stewart Bryant; former steering group member) No Objection