|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
Approved standards track document.
|
|
3.
|
Justification for the specific reference:
|
|
|
ITU-T H.248.1 defines the use of IPSEC for the secure transport of H.248.1 messages over IP. IETF RFC 2409 defines the use of an internet key exchange mechanism for use with IPSEC. Albeit obsolete, ITU-T H.248.1 has used, since its version 1, IPSEC for the secure transport of H.248.1 messages over IP. As part of the IPSEC suite of protocols, IETF RFC 2409 defines the use of an internet key exchange (IKEv1) mechanism for use with IPSEC, and is now widely implemented in H.248 equipment. H.248.1v3 upgrades the reference to IETF RFC 2409 to be normative.
|
|
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=2409
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
RFC 2409 has been in existence since 1998. These documents have been reviewed extensively in IETF. It has been obsoleted by RFC 4306.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC is a standards-track document and is currently in the "Proposed Standard" state. 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 2409 defines the Internet Key Exchange mechanism to be used with IP Security Protocol (IPsec).
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[CAST] Adams, C., "The CAST-128 Encryption Algorithm", RFC 2144, May 1997./
[BLOW] Schneier, B., "The Blowfish Encryption Algorithm", Dr.Dobb's Journal, v. 19, n. 4, April 1994./
[Bra97] Bradner, S., "Key Words for use in RFCs to indicate Requirement Levels", BCP 14, RFC 2119, March 1997./
[DES] ANSI X3.106, "American National Standard for Information Systems-Data Link Encryption", American National Standards Institute, 1983./
[DH] Diffie, W., and Hellman M., "New Directions in Cryptography", IEEE Transactions on Information Theory, V. IT-22, n. 6, June 1977./
[DSS] NIST, "Digital Signature Standard", FIPS 186, National Institute of Standards and Technology, U.S. Department of Commerce, May, 1994./
[IDEA] Lai, X., "On the Design and Security of Block Ciphers," ETH Series in Information Processing, v. 1, Konstanz: Hartung- Gorre Verlag, 1992/
[KBC96] Krawczyk, H., Bellare, M., and R. Canetti, "HMAC: Keyed- Hashing for Message Authentication", RFC 2104, February 1997./
[SKEME] Krawczyk, H., "SKEME: A Versatile Secure Key Exchange Mechanism for Internet", from IEEE Proceedings of the 1996 Symposium on Network and Distributed Systems Security./
[MD5] Rivest, R., "The MD5 Message Digest Algorithm", RFC 1321, April 1992./
[MSST98] Maughhan, D., Schertler, M., Schneider, M., and J. Turner, "Internet Security Association and Key Management Protocol (ISAKMP)", RFC 2408, November 1998./
[Orm96] Orman, H., "The Oakley Key Determination Protocol", RFC 2412, November 1998./
[PKCS1] RSA Laboratories, "PKCS #1: RSA Encryption Standard", November 1993./
[Pip98] Piper, D., "The Internet IP Security Domain Of Interpretation for ISAKMP", RFC 2407, November 1998./
[RC5] Rivest, R., "The RC5 Encryption Algorithm", Dr. Dobb's Journal, v. 20, n. 1, January 1995./
[RSA] Rivest, R., Shamir, A., and Adleman, L., "A Method for Obtaining Digital Signatures and Public-Key Cryptosystems", Communications of the ACM, v. 21, n. 2, February 1978./
[Sch96] Schneier, B., "Applied Cryptography, Protocols, Algorithms, and Source Code in C", 2nd edition./
[SHA] NIST, "Secure Hash Standard", FIPS 180-1, National Institue of Standards and Technology, U.S. Department of Commerce, May 1994./
[TIGER] Anderson, R., and Biham, E., "Fast Software Encryption", Springer LNCS v. 1039, 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.
|
|
