1.
|
Clear description of the referenced document:
|
|
Name:
|
IETF RFC 6818 (2013)
|
Title:
|
Updates to the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile
|
|
2.
|
Status of approval:
|
|
approved
|
3.
|
Justification for the specific reference:
|
|
This recommendation calls out the use of PKI as defined in the reference.
|
4.
|
Current information, if any, about IPR issues:
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/.
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
proposed Standard
|
6.
|
The degree of stability or maturity of the document:
|
|
approved an stable
|
7.
|
Relationship with other existing or emerging documents:
|
|
Updates RFC 5280
|
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./
/
[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./
/
[RFC5914] Housley, R., Ashmore, S., and C. Wallace, "Trust Anchor/
Format", RFC 5914, June 2010./
/
[X.509] ITU-T Recommendation X.509 (2008) | ISO/IEC 9594-8:2008,/
Information Technology - Open Systems Interconnection -/
The Directory: Public-key and attribute certificate/
frameworks./
|
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.
|