|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 2459 (1999)
|
|
Title:
|
Internet X.509 Public Key Infrastructure Certificate and CRL Profile, IETF RFC, January 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 Internet X.509 Public Key Infrastructure Certificate and CRL Profile, IETF RFC, January 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=2459
|
|
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:
|
|
|
[FIPS 180-1] Federal Information Processing Standards Publication/
(FIPS PUB) 180-1, Secure Hash Standard, 17 April 1995./
[Supersedes FIPS PUB 180 dated 11 May 1993.]/
/
[FIPS 186] Federal Information Processing Standards Publication/
(FIPS PUB) 186, Digital Signature Standard, 18 May/
1994./
/
[RC95] Rogier, N. and Chauvaud, P., "The compression function/
of MD2 is not collision free," Presented at Selected/
Areas in Cryptography '95, May 1995./
/
[RFC 791] Postel, J., "Internet Protocol", STD 5, RFC 791,/
September 1981./
/
[RFC 822] Crocker, D., "Standard for the format of ARPA Internet/
text messages", STD 11, RFC 822, August 1982./
/
[RFC 1034] Mockapetris, P., "Domain names - concepts and/
facilities", STD 13, RFC 1034, November 1987./
/
[RFC 1319] Kaliski, B., "The MD2 Message-Digest Algorithm," RFC/
1319, April 1992./
[RFC 1321] Rivest, R., "The MD5 Message-Digest Algorithm," RFC/
1321, April 1992./
/
[RFC 1422] Kent, S., "Privacy Enhancement for Internet Electronic/
Mail: Part II: Certificate-Based Key Management," RFC/
1422, February 1993./
/
[RFC 1423] Balenson, D., "Privacy Enhancement for Internet/
Electronic Mail: Part III: Algorithms, Modes, and/
Identifiers," RFC 1423, February 1993./
/
[RFC 1519] Fuller, V., Li, T., Yu, J. and K. Varadhan. "Classless/
Inter-Domain Routing (CIDR): an Address Assignment and/
Aggregation Strategy", RFC 1519, September 1993./
/
[RFC 1738] Berners-Lee, T., Masinter L., and M. McCahill./
"Uniform Resource Locators (URL)", RFC 1738, December/
1994./
/
[RFC 1778] Howes, T., Kille S., Yeong, W. and C. Robbins. "The/
String Representation of Standard Attribute Syntaxes,"/
RFC 1778, March 1995./
/
[RFC 1883] Deering, S. and R. Hinden. "Internet Protocol, Version/
6 (IPv6) Specification", RFC 1883, December 1995./
/
[RFC 2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RFC 2247] Kille, S., Wahl, M., Grimstad, A., Huber, R. and S./
Sataluri. "Using Domains in LDAP/X.500 Distinguished/
Names", RFC 2247, January 1998./
/
[RFC 2277] Alvestrand, H., "IETF Policy on Character Sets and/
Languages", RFC 2277, January 1998./
/
[RFC 2279] Yergeau, F., "UTF-8, a transformation format of ISO/
10646", RFC 2279, January 1998./
/
[RFC 2313] Kaliski, B., "PKCS #1: RSA Encryption Version 1.5", RFC/
2313, March 1998./
/
[SDN.701] SDN.701, "Message Security Protocol 4.0", Revision A/
1997-02-06./
/
[X.208] CCITT Recommendation X.208: Specification of Abstract/
Syntax Notation One (ASN.1), 1988./
/
/
[X.501] ITU-T Recommendation X.501: Information Technology -/
Open Systems Interconnection - The Directory: Models,/
1993./
/
[X.509] ITU-T Recommendation X.509 (1997 E): Information/
Technology - Open Systems Interconnection - The/
Directory: Authentication Framework, June 1997./
/
[X.520] ITU-T Recommendation X.520: Information Technology -/
Open Systems Interconnection - The Directory: Selected/
Attribute Types, 1993./
/
[X9.42] ANSI X9.42-199x, Public Key Cryptography for The/
Financial Services Industry: Agreement of Symmetric/
Algorithm Keys Using Diffie-Hellman (Working Draft),/
December 1997./
/
[X9.55] ANSI X9.55-1995, Public Key Cryptography For The/
Financial Services Industry: Extensions To Public Key/
Certificates And Certificate Revocation Lists, 8/
December, 1995./
/
[X9.57] ANSI X9.57-199x, Public Key Cryptography For The/
Financial Services Industry: Certificate Management/
(Working Draft), 21 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
|
|
