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 3315 (2003) in draft Q.3405
1. Clear description of the referenced document:
Name: IETF RFC 3315 (2003)
Title: Dynamic Host Configuration Protocol for IPv6 (DHCPv6). R. Droms, Ed., J. Bound, B. Volz, T. Lemon, C. Perkins, M. Carney. Juky 2003.
2. Status of approval:
RFC - Proposed Standard (IETF Stream)
3. Justification for the specific reference:
IETF RFC 3315 (2003) 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: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=3315
5. Other useful information describing the "Quality" of the document:
Document published in July 2003 (http://www.ietf.org/rfc/rfc3315.txt). Category: Standards Track. Updated by IETF RFC 4361, 5494, 6221 and 6422
6. The degree of stability or maturity of the document:
Document published in July 2003 (http://www.ietf.org/rfc/rfc3315.txt). Category: Standards Track
7. Relationship with other existing or emerging documents:
DHPCv6 is reference by many other documents related to IPv6.
8. Any explicit references within that referenced document should also be listed:
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997./
[2] Crawford, M., "Transmission of IPv6 Packets over Ethernet Networks", RFC 2464, December 1998./
[3] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6) Specification", RFC 2460, December 1998./
[4] Droms, R., Ed. and W. Arbaugh, Ed., "Authentication for DHCP Messages", RFC 3118, June 2001./
[5] Hinden, R. and S. Deering, "IP Version 6 Addressing Architecture", RFC 2373, July 1998./
[6] IANA. Private Enterprise Numbers.http://www.iana.org/assignments/enterprise-numbers.html./
[7] Kent, S. and R. Atkinson, "Security Architecture for the Internet Protocol", RFC 2401, November 1998./
[8] Krawczyk, H., Bellare, M. and R. Canetti, "HMAC: Keyed-Hashing for Message Authentication", RFC 2104, February 1997./
[9] Mills, D., "Network Time Protocol (Version 3) Specification, Implementation", RFC 1305, March 1992./
[10] Mockapetris, P., "Domain names - implementation and specification", RFC 1035, November 1987./
[11] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998./
[12] Narten, T. and R. Draves, "Privacy Extensions for Stateless Address Autoconfiguration in IPv6", RFC 3041, January 2001./
[13] Narten, T., Nordmark, E. and W. Simpson, "Neighbor Discovery for IP Version 6 (IPv6)", RFC 2461, December 1998./
[14] Plummer, D.C., "Ethernet Address Resolution Protocol: Or converting network protocol addresses to 48.bit Ethernet address for transmission on Ethernet hardware", STD 37, RFC 826, November 1982./
[15] Postel, J., "User Datagram Protocol", STD 6, RFC 768, August 1980./
[16] Rivest, R., "The MD5 Message-Digest Algorithm", RFC 1321, April 1992./
[17] Thomson, S. and T. Narten, "IPv6 Stateless Address Autoconfiguration", RFC 2462, December 1998./
[18] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor Extensions", RFC 2132, March 1997./
[19] Droms, R., "Dynamic Host Configuration Protocol", RFC 2131, March 1997./
[20] R. Droms, Ed. DNS Configuration options for DHCPv6. April 2002. Work in Progress./
[21] A. K. Vijayabhaskar. Time Configuration Options for DHCPv6.May 2002. Work in Progress./
[22] Vixie, P., Ed., Thomson, S., Rekhter, Y. and J. Bound, "Dynamic Updates in the Domain Name System (DNS UPDATE)", RFC 2136, April 1997./
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 http://www.rfc-editor.org/rfc.html.
10. Other (for any supplementary information):
None
Note: This form is based on Recommendation ITU-T A.5