|
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:
|
|
|
Draft Rec. X.websec-1 can use the SRP Authentication and Key Exchange System in its profiles as security means.
|
|
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=2945
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
The status of all the referred RFCs, is "Proposed Standard".
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
The status of all the referred RFCs, is "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:
|
|
|
[RFC 1321] Rivest, R., "The MD5 Message-Digest Algorithm", RFC 1321,/
April 1992./
/
[RFC 1704] Haller, N. and R. Atkinson, "On Internet Authentication",/
RFC 1704, October 1994./
/
[RFC 1760] Haller, N., "The S/Key One-Time Password System", RFC/
1760, Feburary 1995./
/
[RFC 2095] Klensin, J., Catoe, R. and P. Krumviede, "IMAP/POP/
AUTHorize Extension for Simple Challenge/Response", RFC/
2095, January 1997./
/
[RFC 2104] Krawczyk, H., Bellare, M. and R. Canetti, "HMAC: Keyed-/
Hashing for Message Authentication", RFC 2104, February/
1997./
/
[SHA1] National Institute of Standards and Technology (NIST),/
"Announcing the Secure Hash Standard", FIPS 180-1, U.S./
Department of Commerce, April 1995./
/
[SRP] T. Wu, "The Secure Remote Password Protocol", In/
Proceedings of the 1998 Internet Society Symposium on/
Network and Distributed Systems Security, San Diego, CA,/
pp. 97-111./
|
|
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
|
