|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Draft Standard which obsoletes RFC2138. Updated by RFC2868, RFC3575. Errata exists
|
|
3.
|
Justification for the specific reference:
|
|
|
G.9961 uses this protocol for external authentication of G.hn interfaces.
|
|
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=2865
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
RFC 2865 was published in June 2000. The status of the RFC is listed as draft standard. Current standards status of this document can be found at ftp://ftp.isi.edu/in-notes/std/std1.txt
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 2865 was published in June 2000. The status of the RFC is listed as draft standard. Current standards status of this document can be found at ftp://ftp.isi.edu/in-notes/std/std1.txt
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
RFC 2865 is implemented in many network access systems for back end authentication.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] Rigney, C., Rubens, A., Simpson, W. and S. Willens, "Remote Authentication Dial In User Service (RADIUS)", RFC 2138, April 1997./
[2] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March, 1997./
[3] Rivest, R. and S. Dusse, "The MD5 Message-Digest Algorithm", RFC 1321, April 1992./
[4] Postel, J., "User Datagram Protocol", STD 6, RFC 768, August 1980./
[5] Rigney, C., "RADIUS Accounting", RFC 2866, June 2000./
[6] Reynolds, J. and J. Postel, "Assigned Numbers", STD 2, RFC 1700, October 1994./
[7] Yergeau, F., "UTF-8, a transformation format of ISO 10646", RFC 2279, January 1998./
[8] Aboba, B. and M. Beadles, "The Network Access Identifier", RFC 2486, January 1999./
[9] Kaufman, C., Perlman, R., and Speciner, M., "Network Security: Private Communications in a Public World", Prentice Hall, March 1995, ISBN 0-13-061466-1./
[10] Jacobson, V., "Compressing TCP/IP headers for low-speed serial links", RFC 1144, February 1990./
[11] ISO 8859. International Standard -- Information Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 1: Latin Alphabet No. 1, ISO 8859-1:1987./
[12] Sklower, K., Lloyd, B., McGregor, G., Carr, D. and T. Coradetti, "The PPP Multilink Protocol (MP)", RFC 1990, August 1996./
[13] Alvestrand, H. and T. Narten, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998./
[14] Galvin, J., McCloghrie, K. and J. Davin, "SNMP Security Protocols", RFC 1352, July 1992./
[15] Dobbertin, H., "The Status of MD5 After a Recent Attack", CryptoBytes Vol.2 No.2, Summer 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):
|
|
|
References should always be made to RFC numbers (and not by other designations such as STD, BCP, etc.). References not to be made to documents referred to as "Internet Drafts" or RFCs categorized as "Historic". Normative references should not be made to RFCs that are not standards, for example, "Informational" and "Experimental" RFCs.
|
|
