Skip to main content

Lightweight DHCPv6 Relay Agent
RFC 6221

Yes

(Ralph Droms)

No Objection

Lars Eggert
(Adrian Farrel)
(Alexey Melnikov)
(Dan Romascanu)
(Gonzalo Camarillo)
(Peter Saint-Andre)
(Russ Housley)
(Stewart Bryant)

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

Lars Eggert No Objection

(Ralph Droms; former steering group member) Yes

Yes ()

                            

(Adrian Farrel; former steering group member) No Objection

No Objection ()

                            

(Alexey Melnikov; former steering group member) No Objection

No Objection ()

                            

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

No Objection ()

                            

(Gonzalo Camarillo; former steering group member) No Objection

No Objection ()

                            

(Jari Arkko; former steering group member) No Objection

No Objection (2010-11-18)
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 ()

                            

(Russ Housley; former steering group member) No Objection

No Objection ()

                            

(Stewart Bryant; former steering group member) No Objection

No Objection ()

                            

(Tim Polk; former steering group member) No Objection

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