IPv6 Implications for Network Scanning
RFC 5157

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

Lars Eggert No Objection

Comment (2007-10-27 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
Section 1., paragraph 6:
>    Finally, note that this document is currently intended to be
>    informational; there is not yet sufficient deployment experience for
>    it to be considered BCP.

  Suggest to rephrase "is currently intended to be" as "has been
  published as".


Section 10., paragraph 2:
>    [2]   Thomson, S. and T. Narten, "IPv6 Stateless Address
>          Autoconfiguration", RFC 2462, December 1998.

  Obsoleted by RFC 4862.


Section 10., paragraph 3:
>    [3]   Narten, T. and R. Draves, "Privacy Extensions for Stateless
>          Address Autoconfiguration in IPv6", RFC 3041, January 2001.

  Obsoleted by RFC 4941.


Section 10., paragraph 12:
>    [12]  Davies, E., Krishnan, S., and P. Savola, "IPv6 Transition/
>          Co-existence Security Considerations
>          (draft-ietf-v6ops-security-overview-06)", October 2007.

  Published as RFC 4942.

(Ron Bonica; former steering group member) Yes

Yes ( for -** No value found for 'p.get_dochistory.rev' **)
No email
send info

(Cullen Jennings; former steering group member) No Objection

No Objection (2007-10-31 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
Section 3.2 

I suspect I am not understanding this because I am thinking it might require a huge number of DNS entries. How many entries will this be in DNS? Is that amount alright? 


Section 5.5 , para 2.

I don't see how this would help - wouldn't spammer just use the DNS name?


Section 2.5 

I'm a little confused by what you mean by "on link" here when we are talking about switches. Do you just mean that the Administrator will have ways of knowing all the IP talking to the switches? 

Section 5.4 - note this is a comment not discuss. 
I am somewhat uncomfortable with a information document from a different WG putting strong specifications on how a DHCP server should work.

(Dan Romascanu; former steering group member) No Objection

No Objection ( for -** No value found for 'p.get_dochistory.rev' **)
No email
send info

(David Ward; former steering group member) No Objection

No Objection ( for -** No value found for 'p.get_dochistory.rev' **)
No email
send info

(Jari Arkko; former steering group member) (was Discuss) No Objection

No Objection ()
No email
send info

(Magnus Westerlund; former steering group member) No Objection

No Objection ( for -** No value found for 'p.get_dochistory.rev' **)
No email
send info

(Ross Callon; former steering group member) No Objection

No Objection ( for -** No value found for 'p.get_dochistory.rev' **)
No email
send info

(Russ Housley; former steering group member) (was Discuss) No Objection

No Objection ()
No email
send info

(Tim Polk; former steering group member) (was No Record, Discuss) No Objection

No Objection ()
No email
send info

(Chris Newman; former steering group member) Abstain

Abstain (2007-11-01 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
I concur with Sam.

(Sam Hartman; former steering group member) Abstain

Abstain (2007-10-30 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
I don't think the quality or value of this document justifies publication.