|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Informational
|
|
3.
|
Justification for the specific reference:
|
|
|
Technical specifications that use the Internet Protocol will need to reference RFCs.
|
|
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=2983
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Informational
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Informational
|
|
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:
|
|
|
[RFC 791] Postel, J., "Internet Protocol", STD 5, RFC 791, September/
1981./
/
[RFC 1661] Simpson, W., "The Point-to-Point Protocol (PPP)", STD 51,/
RFC 1661, July 1994./
/
[RFC 1933] Gilligan, R. and E. Nordmark, "Transition Mechanisms for/
IPv6 Hosts and Routers", RFC 1933, April 1996./
/
[RFC 2003] Perkins, C., "IP Encapsulation within IP", RFC 2003,/
October 1996./
/
[RFC 2401] Kent, S. and R. Atkinson, "Security Architecture for the/
Internet Protocol", RFC 2401, November 1998./
/
[RFC 2474] 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./
/
[RFC 2475] Blake, S., Black, D., Carlson, M., Davies, E., Wang, Z./
and W. Weiss, "An Architecture for Differentiated/
Services", RFC 2475, December 1998./
/
[RFC 2597] Heinanen, J., Baker, F., Weiss, W. and J. Wroclawski,/
"Assured Forwarding PHB Group", RFC 2597. June 1999./
/
[RFC 2598] Jacobson, V., Nichols, K. and K. Poduri, "An Expedited/
Forwarding PHB", RFC 2598, June 1999./
/
[RFC 2661] Townsley, W., Valencia, A., Rubens, A., Pall, G., Zorn, G./
and B. Palter. "Layer Two Tunneling Protocol "L2TP"", RFC/
2661, August 1999./
/
[RFC 2765] Nordmark, E., "Stateless IP/ICMP Translation Algorithm/
(SIIT)", RFC 2765, February 2000.
|
|
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):
|
|
|
If the Study Group decides to make the reference to the RFC, the reference should always be made by RFC number (and not by other designations such as STD, BCP, etc.). References should not be made to documents referred to as "Internet Drafts" or RFCs categorized as "Historic".
|
|
