IPv6 Enterprise Network Analysis - IP Layer 3 Focus
RFC 4852

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

(David Kessens) Yes

(Jari Arkko) (was Discuss) No Objection

(Lisa Dusseault) No Objection

Comment (2006-06-05 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
The reference [V6DEF] is not filled in (referenced in section 5), nor is [DNSV6REC], [NIS], [DHCPv4], [ADDRCONF], [IPSEC] or [PRIVv6].  I wish the "works in progress" references had pointers (like [DNSV6]), are they not Internet Drafts?

"At the time of writing, best practice in IPv6 site address planning
 is restricted due to limited wide-scale deployments."

Does this mean "At the time of writing, solid details on best practice in IPv6 address planning is restricted..."?  I  am pretty sure it doesn't mean that the applicability of best practice is limited...

(Lars Eggert) No Objection

(Dan Romascanu) (was No Record, Discuss) No Objection

(Mark Townsley) (was Discuss) No Objection

Magnus Westerlund No Objection

(Sam Hartman) Abstain

Comment (2006-06-06 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
This document rules so many important things out of scope--nat used
for V4, firewalls, application issues--that it is useless in my mind.
The best I can say is that I don't think it will do any harm.

(Russ Housley) (was Discuss) Abstain

Comment (2006-12-11)
No email
send info
  The response to my DISCUSS position was much lighter than I had
  hoped.  I do not think the point is worth further delay.  I have
  changed my position to ABSTAIN.

(Cullen Jennings) Abstain

Comment (2006-06-21 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
I think this document fails to meet many of it's goals. I don't think it will help an enterprise figure out how to transition to v6 - there is so many critical things it does not mention, like applications that run on hosts. I have a hard time imagining any easy way to fix it.