This page will soon be deactivated—explore our new, faster, mobile-friendly site, now centralized in MyWorkspace!

Committed to connecting the world

  •  
ITU GSR 2024

ITU-T work programme

Home : ITU-T Home : ITU-T Work Programme : X.1205     
  ITU-T A.5 justification information for referenced document IETF RFC 2716 (1999) in draft X.1205
1. Clear description of the referenced document:
Name: IETF RFC 2716 (1999)
Title: PPP EAP TLS Authentication Protocol, October 1999
2. Status of approval:
The referred RFCs were approved by IESG (Internet Engineering Steering Group).
3. Justification for the specific reference:
Draft Rec. X.cso refers to PPP EAP TLS Authentication Protocol, IETF RFC 2716, October 1999.
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=2716
5. Other useful information describing the "Quality" of the document:
Proposed Standard
6. The degree of stability or maturity of the document:
Proposed Standard
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:
[1] Simpson, W., Editor, "The Point-to-Point Protocol (PPP)", STD/
51, RFC 1661, July 1994./
/
[2] Sklower, K., Lloyd, B., McGregor, G., Carr, D. and T. Coradetti,/
"The PPP Multilink Protocol (MP)", RFC 1990, August 1996./
/
[3] Simpson, W., Editor, "PPP LCP Extensions", RFC 1570, January/
1994./
/
[4] Rivest, R. and S. Dusse, "The MD5 Message-Digest Algorithm", RFC/
1321, April 1992./
/
[5] Blunk, L. and J. Vollbrecht, "PPP Extensible Authentication/
Protocol (EAP)", RFC 2284, March 1998./
/
[6] Meyer, G., "The PPP Encryption Protocol (ECP)", RFC 1968, June/
1996./
/
[7] National Bureau of Standards, "Data Encryption Standard", FIPS/
PUB 46 (January 1977)./
/
[8] National Bureau of Standards, "DES Modes of Operation", FIPS PUB/
81 (December 1980)./
/
[9] Sklower, K. amd G. Meyer, "The PPP DES Encryption Protocol,/
Version 2 (DESE-bis)", RFC 2419, September 1998./
/
[10] Hummert, K., "The PPP Triple-DES Encryption Protocol (3DESE)",/
RFC 2420, September 1998./
/
[11] Bradner, S., "Key words for use in RFCs to Indicate Requirement/
Levels", BCP 14, RFC 2119, March 1997./
/
[12] Dierks, T. and C. Allen, "The TLS Protocol Version 1.0", RFC/
2246, November 1998./
/
[13] Rand, D., "The PPP Compression Control Protocol", RFC 1962, June/
1996./
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