|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF SCEP-23
|
|
Title:
|
Simple Certificate Enrollment Protocol ID draft-nourse-scep-23
|
|
|
2.
|
Status of approval:
|
|
|
This is a historic (not standards track) IETF document published on 7 September 2011 and expired on 10 March 2012. Replaced by *Informational* RFC 8894.
|
|
3.
|
Justification for the specific reference:
|
|
|
This IETF SCEP-23 defines Simple Certificate Enrollment Protocol that is used in this Recommendation.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
https://datatracker.ietf.org/ipr/search/
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This is an expired Internet Draft (=proposal) document. Replaced by *Informational* RFC 8894. No normative reference should be made to either of these documents.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
This is an expired Internet Draft (=proposal) document. Replaced by *Informational* RFC 8894. No normative reference should be made to either of these documents.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
Replaced by *Informational* RFC 8894 (2020-09).
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RFC2315] Kaliski, B., "PKCS #7: Cryptographic Message Syntax/
Version 1.5", RFC 2315, March 1998./
/
[RFC2396] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform/
Resource Identifiers (URI): Generic Syntax", RFC 2396,/
August 1998./
/
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,/
Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext/
Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999./
/
[RFC2985] Nystrom, M. and B. Kaliski, "PKCS #9: Selected Object/
Classes and Attribute Types Version 2.0", RFC 2985,/
November 2000./
/
[RFC2986] Nystrom, M. and B. Kaliski, "PKCS #10: Certification/
Request Syntax Specification Version 1.7", RFC 2986,/
November 2000./
/
[RFC4210] Adams, C., Farrell, S., Kause, T., and T. Mononen,/
"Internet X.509 Public Key Infrastructure Certificate/
Management Protocol (CMP)", RFC 4210, September 2005./
/
[RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data/
Encodings", RFC 4648, October 2006./
/
[RFC5272] Schaad, J. and M. Myers, "Certificate Management over CMS/
(CMC)", RFC 5272, June 2008./
/
[RFC5280] Cooper, D., Santesson, S., Farrell, S., Boeyen, S.,/
Housley, R., and W. Polk, "Internet X.509 Public Key/
Infrastructure Certificate and Certificate Revocation List/
(CRL) Profile", RFC 5280, May 2008./
/
[TripleDES]/
"ANSI X9.52-1998, Triple Data Encryption Algorithm Modes/
of Operation", 1998./
/
/
[RFC2409] Harkins, D. and D. Carrel, "The Internet Key Exchange/
(IKE)", RFC 2409, November 1998./
/
[RFC4306] Kaufman, C., "Internet Key Exchange (IKEv2) Protocol",/
RFC 4306, December 2005./
/
[RFC4346] Dierks, T. and E. Rescorla, "The Transport Layer Security/
(TLS) Protocol Version 1.1", RFC 4346, April 2006./
/
[RFC4945] Korver, B., "The Internet IP Security PKI Profile of/
IKEv1/ISAKMP, IKEv2, and PKIX", RFC 4945, August 2007.
|
|
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.
|
|
