Committed to connecting the world


ITU-T work programme

Home : ITU-T Home : ITU-T Work Programme : Q.3405     
  ITU-T A.5 justification information for referenced document IETF RFC 6333 (2011) in draft Q.3405
1. Clear description of the referenced document:
Name: IETF RFC 6333 (2011)
Title: Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion
2. Status of approval:
Standards Track RFC - Proposed Standard approved August 2011
3. Justification for the specific reference:
IETF RFC 6333 (2011) is referenced in Q.3405 (ex. Q.IPv6ProBB).
4. Current information, if any, about IPR issues:
Information on IPR issues regarding RFCs is available at: Specifically:
5. Other useful information describing the "Quality" of the document:
This RFC has been in existence since June 2011. No errata.
6. The degree of stability or maturity of the document:
Proposed Standard
7. Relationship with other existing or emerging documents:
References within the referenced RFCs are listed under item (8).
8. Any explicit references within that referenced document should also be listed:
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997./
[RFC2473] Conta, A. and S. Deering, "Generic Packet Tunneling in IPv6 Specification", RFC 2473, December 1998./
[RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black, "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers", RFC 2474, December 1998./
[RFC4213] Nordmark, E. and R. Gilligan, "Basic Transition Mechanisms for IPv6 Hosts and Routers", RFC 4213, October 2005./
[RFC5625] Bellis, R., "DNS Proxy Implementation Guidelines", BCP 152, RFC 5625, August 2009./
[RFC6334] Hankins, D. and T. Mrugalski, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Option for Dual-Stack Lite", RFC 6334, August 2011.
9. Qualification of ISOC/IETF:
9.1-9.6     Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7     The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8     Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at
10. Other (for any supplementary information):
Note: This form is based on Recommendation ITU-T A.5