|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
The referred RFCs were approved by IESG (Internet Engineering Steering Group).
|
|
3.
|
Justification for the specific reference:
|
|
|
Specoifies the authentication and key distribution protocol.
|
|
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=2284
|
|
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:
|
|
|
Obsoleted by RFC 3748
Updated by RFC 2484
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] Simpson, W., "The Point-to-Point Protocol (PPP)", STD 51,/
RFC 1661, July 1994./
/
[2] Reynolds, J. and J. Postel, "Assigned Numbers", STD 2,/
RFC 1700, October 1994./
/
[3] Simpson, W., "PPP Challenge Handshake Authentication Protocol/
(CHAP)", RFC 1994, August 1996./
/
[4] Haller, N. and C. Metz, "A One-Time Password System", RFC 1938,/
May 1996./
/
[5] Yergeau, F., "UTF-8, a transformation format of Unicode and ISO/
10646", RFC 2044, October 1996./
/
[6] Bradner, S., "Key words for use in RFCs to Indicate Requirement/
Levels", RFC 2119, March 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
|
