Committed to connecting the world

  •  
ITU GSR 2024

ITU-T work programme

Home : ITU-T Home : ITU-T Work Programme : X.1083     
  ITU-T A.5 justification information for referenced document IETF RFC 826 (1982) in draft X.1083
1. Clear description of the referenced document:
Name: IETF RFC 826 (1982)
Title: Ethernet Address Resolution Protocol: Or Converting Network Protocol Addresses to 48.bit Ethernet Address for Transmission on Ethernet Hardware. D. Plummer. November 1982.
2. Status of approval:
Normative
3. Justification for the specific reference:
The network configuration of BIP endpoints described in annex B needs the ARP protocol defined in RFC 826 to obtain the MAC address of a BIP endpoint whose IPv4 address is known.
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=826
5. Other useful information describing the "Quality" of the document:
Document published in November 1982 (http://www.ietf.org/rfc/rfc0826.txt). The status is STANDARD.
6. The degree of stability or maturity of the document:
Document published in November 1982 (http://www.ietf.org/rfc/rfc0826.txt). The status is STANDARD.
7. Relationship with other existing or emerging documents:
ARP is used by all systems using IPv4 on Ethernet and referenced by some other IP protocols.
8. Any explicit references within that referenced document should also be listed:
None
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