|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 2256 (1997)
|
|
Title:
|
A Summary of the X.500(96) User Schema for use with LDAPv3, December 1997
|
|
|
2.
|
Status of approval:
|
|
|
Normative
|
|
3.
|
Justification for the specific reference:
|
|
|
Draft Rec. X.websec-2 refers to A Summary of the X.500 User Schema for use with LDAPv3 in order to secure XACML messages.
|
|
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=2256
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
RFC 2256 was published in December 1997. It is a standards-track document and is currently in the "Proposed Standard" state. In addition, there are several independent, interoperable implementations of the protocol. Current status of this document can be found at ftp://ftp.isi.edu/in-notes/std/std1.txt
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
RFC 2256 was published in December 1997. It is a standards-track document and is currently in the "Proposed Standard" state. In addition, there are several independent, interoperable implementations of the protocol. Current status of this document can be found at ftp://ftp.isi.edu/in-notes/std/std1.txt
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
H.350.1
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] Wahl, M., Coulbeck, A., Howes, T., and S. Kille, “Lightweight X.500 Directory Access Protocol (v3): Attribute Syntax Definitions", RFC 2252, December 1997./
[2] The Directory: Models. ITU-T Recommendation X.501, 1996./
[3] The Directory: Authentication Framework. ITU-T Recommendation X.509, 1996./
[4] The Directory: Selected Attribute Types. ITU-T Recommendation X.520, 1996./
[5] The Directory: Selected Object Classes. ITU-T Recommendation X.521, 1996./
[6] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", RFC 2119, March 1997.
|
|
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):
|
|
|
References should always be made to RFC numbers (and not by other designations such as STD, BCP, etc.). References not to be made to documents referred to as "Internet Drafts" or RFCs categorized as "Historic". Normative references should not be made to RFCs that are not standards, for example, "Informational" and "Experimental" RFCs.
|
