Skip to main content

DHCPv6 Options for Network Boot
RFC 5970

Yes

(Ralph Droms)

No Objection

(Adrian Farrel)
(Alexey Melnikov)
(David Harrington)
(Gonzalo Camarillo)
(Robert Sparks)
(Ron Bonica)
(Russ Housley)
(Tim Polk)

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

(Jari Arkko; former steering group member) Yes

Yes (2010-05-05)
I support David Harrington's Discuss though.

(Ralph Droms; former steering group member) Yes

Yes ()

                            

(Adrian Farrel; former steering group member) No Objection

No Objection ()

                            

(Alexey Melnikov; former steering group member) (was Discuss) No Objection

No Objection (2010-06-08)

                            

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

No Objection (2010-07-22)
1. The title of the document should refer to 'options' rather then 'option'

2. In Section 5: 

The Boot File URL option does not place any constraints on the
  protocol used for downloading the boot file, other than that it must
  be possible to specify it in a URL. 

s/must/MUST/

(David Harrington; former steering group member) (was Discuss) No Objection

No Objection ()

                            

(Gonzalo Camarillo; former steering group member) No Objection

No Objection ()

                            

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

No Objection (2010-05-03)
Section 3.1 (Boot File Uniform Resource Locator (URL) Option) states that "The server sends this option to inform the client about an URL to a boot file." and states of "boot-file-url" that "This string is the URL for the boot file." Does this specification really mean "URL"? Confer Section 1.1.3 of RFC 3986.

(Robert Sparks; former steering group member) No Objection

No Objection ()

                            

(Ron Bonica; former steering group member) No Objection

No Objection ()

                            

(Russ Housley; former steering group member) No Objection

No Objection ()

                            

(Sean Turner; former steering group member) No Objection

No Objection (2010-05-04)
Have the authors considered some additional words in the security considerations about the fact that downloading the wrong operating system could lead to compromise of data on local storage.

(Stewart Bryant; former steering group member) No Objection

No Objection (2010-05-05)
The following IANA action gets pulled out of a hat without any mention in the Abstract, Introduction or Text.

"This document also introduces a new IANA registry for processora rchitecture types.  The name of this registry shall be "Processor Architecture Type".  Registry entries consist of a 16-bit integer recorded in decimal format, and a descriptive name.  The initial values of this registry can be found in [RFC4578] section 2.1."

I have no objection to DHCP WG creating this registry, but it should not be tucked down in the bottom of this document with out prior indication to reviewers.

(Tim Polk; former steering group member) No Objection

No Objection ()