Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion
RFC 6333

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

(Jari Arkko) Yes

(Ron Bonica) No Objection

(Stewart Bryant) No Objection

(Wesley Eddy) (was Discuss) No Objection

(Adrian Farrel) No Objection

Comment (2011-04-24 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
Thanks for a fine and readble document.

Herewith, a few minor points you might like to look at to improve the document.


I was surprised that the following statements use a weak "MAY"

   The B4 element MAY use any other addresses within
   the range.

   The AFTR MAY use the well-known IPv4 address 

"MAY" is usually used when there is some other more normal behavior, but
you don't say what that is.


7.2.  VPN

   Dual-stack lite implementations SHOULD NOT interfere with the
   functioning of IPv4 or IPv6 VPNs.

Seems a bit of an odd use of "SHOULD NOT". I'm not clear whether you
are commentng that "in your view the DS-Lite technology should not 
cause anything to break" or observing that it would be a broken 
implementation that *chose* to interfere with VPN function.


8.4.  Sharing global IPv4 addresses

   AFTR shares a single IP to multiple users.

s/to/address with/


8.5.  Port forwarding / keep alive

   Work on a control plane to the carrier-grade NAT is done in the PCP
   working group at IETF.  The PCP protocol enables 

What does the second 'P' in "PCP" stand for?

(Stephen Farrell) (was Discuss) No Objection

Comment (2011-04-26)
No email
send info
8.3: s/require ALG to work properly/require ALGs
to work properly/ (maybe) There are a few other English
language issues (mainly improper singluar/plurals).

(David Harrington) (was Discuss) No Objection

(Russ Housley) No Objection

Comment (2011-04-22 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
  Please consider the editorial comments from the Gen-ART Review by
  Roni Even on 9-Apr-2011.

(Pete Resnick) No Objection

(Dan Romascanu) No Objection

(Peter Saint-Andre) No Objection

(Robert Sparks) No Objection

Comment (2011-04-26 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
Consider adding a short discussion or perhaps an example of how services that sit on the Internet side of an AFTR (especially those in the same administrative domain of the AFTR) that need to know which B4 IPv4 traffic came through might get that information from the AFTR (perhaps using the information in the extended binding table described in section 6.6). Showing how a location query in a protocol like HELD (RFC5985) would be answered would be a good example.

(Sean Turner) No Objection

Comment (2011-04-26 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
The reference for 1918 should be normative based on the following:

  However, it SHOULD operate its own DHCP(v4) server handing out
   [RFC1918] address space (e.g. to hosts in the home.

(Ralph Droms) Recuse