|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 2136 (1997)
|
|
Title:
|
Dynamic Updates in the Domain Name System (DNS UPDATE). P. Vixie. Ed., S. Thomson, Y. Rekhter, J. Bound. April 1997.
|
|
|
2.
|
Status of approval:
|
|
|
Normative
|
|
3.
|
Justification for the specific reference:
|
|
|
When, in TCP/IP binding, network configuration is dynamic using DHCP, it is possible to dynamically update DNS database with the DNS UPDATE method described in RFC 2136.
|
|
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=2136
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Document published in April 1997 (http://www.ietf.org/rfc/rfc2136.txt). The status is PROPOSED STANDARD.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Document published in April 1997 (http://www.ietf.org/rfc/rfc2136.txt). The status is PROPOSED STANDARD.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
DNS UPDATE is used in relation with DHCP.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[RFC1035] Mockapetris, P., "Domain Names - Implementation and Specification", STD 13, RFC 1035, USC/Information Sciences Institute, November 1987./
[RFC1982] Elz, R., "Serial Number Arithmetic", RFC 1982, University of Melbourne, August 1996./
[RFC1995] Ohta, M., "Incremental Zone Transfer", RFC 1995, Tokyo Institute of Technology, August 1996./
[RFC1996] Vixie, P., "A Mechanism for Prompt Notification of Zone Changes", RFC 1996, Internet Software Consortium, August 1996./
[RFC2065] Eastlake, D., and C. Kaufman, "Domain Name System Protocol Security Extensions", RFC 2065, January 1997./
[RFC2137] Eastlake, D., "Secure Domain Name System Dynamic Update", RFC 2137, 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
|
