|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 4514 (2006)
|
|
Title:
|
Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished Names, IETF RFC, June 2006.
|
|
|
2.
|
Status of approval:
|
|
|
The referred RFCs were approved by IESG (Internet Engineering Steering Group).
|
|
3.
|
Justification for the specific reference:
|
|
|
Rec. ITU-T X.518 references IETF RFC 4514 for using the string representation of distinguished names.
|
|
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=4514
|
|
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 RFCs are listed under item (8).
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] The Directory -- overview of concepts, models and services./
ITU-T Rec. X.500(1993)./
/
[2] The Directory -- Models. ITU-T Rec. X.501(1993)./
/
[3] Wahl, M., Howes, T., and S. Kille, "Lightweight Directory/
Access Protocol (v3)", RFC 2251, December 1997./
/
[4] Wahl, M., Coulbeck, A., Howes, T. and S. Kille, "Lightweight/
Directory Access Protocol (v3): Attribute Syntax Definitions",/
RFC 2252, December 1997./
/
[5] Crocker, D., "Standard of the Format of ARPA-Internet Text/
Messages", STD 11, RFC 822, August 1982./
/
[6] Bradner, S., "Key words for use in RFCs to Indicate Requirement/
Levels", RFC 2119./
|
|
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
|
