Committed to connecting the world

  •  

ITU-T work programme

Home : ITU-T Home : ITU-T Work Programme : Q.3070     
  ITU-T A.5 justification information for referenced document IETF RFC 2986 (2000) in draft Q.3070
1. Clear description of the referenced document:
Name: IETF RFC 2986 (2000)
Title: PKCS #10: Certification Request Syntax Specification - Version 1.7
2. Status of approval:
Approved by NWG (Network Working Group)
3. Justification for the specific reference:
IETF RFC 2986 defines the syntax for Certification Request, which is referenced by ITU-T Q.3070 (ex Q.TSCA).
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:
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 RFC are listed under item (8).
8. Any explicit references within that referenced document should also be listed:
[1] RSA Laboratories. PKCS #1: RSA Encryption Standard. Version 2.0,/
October 1998./
[2] RSA Laboratories. PKCS #7: Cryptographic Message Syntax/
Standard. Version 1.5, November 1993./
[3] RSA Laboratories. PKCS #9: Selected Attribute Types. Version/
2.0, February 2000./
[4] Adams, C. and S. Farrell, "Internet X.509 Public Key/
Infrastructure - Certificate Management Protocols", RFC 2510,/
March 1999./
[5] Kaliski, B., "Privacy Enhancement for Internet Electronic Mail:/
Part IV: Key Certification and Related Services", RFC 1424,/
February 1993./
[6] Kaliski, B., "PKCS #10: Certification Request Syntax Version/
1.5", RFC 2314, March 1998./
[7] ITU-T Recommendation X.500 (1997) | ISO/IEC 9594-1:1998,/
Information technology - Open Systems Interconnection - The/
Directory: Overview of concepts, models and services./
[8] ITU-T Recommendation X.501 (1993) | ISO/IEC 9594-2:1995,/
Information technology - Open Systems Interconnection - The/
Directory: Models./
[9] ITU-T Recommendation X.509 (1997) | ISO/IEC 9594-8:1998,/
Information technology - Open Systems Interconnection -The/
Directory: Authentication framework./
[10] ITU-T Recommendation X.680 (1997) | ISO/IEC 8824-1:1998,/
Information Technology - Abstract Syntax Notation One (ASN.1):/
Specification of Basic Notation./
[11] ITU-T Recommendation X.681 (1997) | ISO/IEC 8824-2:1998,/
Information Technology - Abstract Syntax Notation One (ASN.1):/
Information Object Specification./
[12] ITU-T Recommendation X.682 (1997) | ISO/IEC 8824-3:1998,/
Information Technology - Abstract Syntax Notation One (ASN.1):/
Constraint Specification./
[13] ITU-T Recommendation X.683 (1997) | ISO/IEC 8824-4:1998,/
Information Technology - Abstract Syntax Notation One (ASN.1):/
Parameterization of ASN.1 Specifications./
[14] ITU-T Recommendation X.690 (1997) | ISO/IEC 8825-1:1998,/
Information Technology - ASN.1 Encoding Rules: Specification of/
Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and/
Distinguished Encoding Rules (DER).
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
Note: This form is based on Recommendation ITU-T A.5