|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 3927 (2004)
|
|
Title:
|
Dynamic Configuration for IPv4 Link-Local Addresses. S Cheshire, B. Ahoba, E. Guttman, V. Roca, P. Walsh. October 2004.
|
|
|
2.
|
Status of approval:
|
|
|
Normative
|
|
3.
|
Justification for the specific reference:
|
|
|
The network configuration of BIP endpoints in IPv4, defined in annex B, can use dynamic configuration of IPv4 link-local addresses as defined in RFC 3315 when there is no DHCP server.
|
|
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=3927
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Document published in May 2005 (http://www.ietf.org/rfc/rfc3927.txt). The status is PROPOSED STANDARD.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Document published in May 2005 (http://www.ietf.org/rfc/rfc3927.txt). The status is PROPOSED STANDARD.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
RFC 3927 is widely to get an IPv4 address in a network with no DHCP server.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[RFC792] Postel, J., "Internet Control Message Protocol", STD 5, RFC 792, September 1981./
[RFC826] Plummer, D., "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./
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997./
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998./
[802] IEEE Standards for Local and Metropolitan Area Networks: Overview and Architecture, ANSI/IEEE Std 802, 1990./
[802.3] ISO/IEC 8802-3 Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Common specifications - Part 3: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications, (also ANSI/IEEE Std 802.3- 1996), 1996./
[802.5] ISO/IEC 8802-5 Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Common specifications - Part 5: Token ring access method and physical layer specifications, (also ANSI/IEEE Std 802.5-1998), 1998./
[802.11] Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific Requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications, IEEE Std. 802.11-1999, 1999./
[RFC959] Postel, J. and J. Reynolds, "File Transfer Protocol", STD 9, RFC 959, October 1985./
[RFC1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G., and E. Lear, "Address Allocation for Private Internets", BCP 5, RFC 1918, February 1996./
[RFC2131] Droms, R., "Dynamic Host Configuration Protocol", RFC 2131, March 1997./
[RFC2462] Thomson, S. and T. Narten, "IPv6 Stateless Address Autoconfiguration", RFC 2462, December 1998./
[RFC3027] Holdrege, M. and P. Srisuresh, "Protocol Complications with the IP Network Address Translator", RFC 3027, January 2001./
[DNAv4] Aboba, B., "Detection of Network Attachment (DNA) in IPv4", Work in Progress, July 2004./
[LLMNR] Esibov, L., Aboba, B. and D. Thaler, "Linklocal Multicast Name Resolution (LLMNR)", Work in Progress, June 2004./
|
|
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
|
|
