Lightweight DHCPv6 Relay Agent
RFC 6221

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

Lars Eggert No Objection

(Ralph Droms; former steering group member) Yes

Yes ()
No email
send info

(Adrian Farrel; former steering group member) No Objection

No Objection ()
No email
send info

(Alexey Melnikov; former steering group member) No Objection

No Objection ()
No email
send info

(Dan Romascanu; former steering group member) (was Discuss) No Objection

No Objection ()
No email
send info

(Gonzalo Camarillo; former steering group member) No Objection

No Objection ()
No email
send info

(Jari Arkko; former steering group member) No Objection

No Objection (2010-11-18)
No email
send info
In Section 5.1 you specify that three parameters are needed, but only talk about two of them. I would suggesting adding text that says peer address needs to be set as specified in Section 6.1.

In Section 6.1, you should specify what traffic pattern (UDP, DHCPv6 port number, destination address = all DHCPv6 servers)? you are looking for. Similar text already exists for the other direction in Section 6.2. And then there is some text about what pattern to use in the client=>network direction in Section 7... IMO that's in the wrong place.

(Peter Saint-Andre; former steering group member) No Objection

No Objection ()
No email
send info

(Russ Housley; former steering group member) No Objection

No Objection ()
No email
send info

(Stewart Bryant; former steering group member) No Objection

No Objection ()
No email
send info

(Tim Polk; former steering group member) No Objection

No Objection (2010-11-18)
No email
send info
Please add a pointer to RFC 3315 in the Security Considerations