|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 2798 (2000)
|
|
Title:
|
Definition of the inetOrgPerson LDAP Object Class, IETF RFC, 2000.
|
|
|
2.
|
Status of approval:
|
|
|
|
|
3.
|
Justification for the specific reference:
|
|
|
Draft Rec. X.websec-1 uses Definition of the inetOrgPerson LDAP Object Class in its binding profiles.
|
|
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=2798
|
|
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:
|
|
|
[JFIF] E. Hamilton, "JPEG File Interchange Format (Version 1.02)",/
C-Cube Microsystems, Milpitas, CA, September 1, 1992./
/
[LDIF] G. Good, "The LDAP Data Interchange Format (LDIF) -/
Technical Specification", Work in Progress./
/
[PKCS12] "PKCS #12: Personal Information Exchange Standard", Version/
1.0 Draft, 30 April 1997./
/
[RFC1274] Barker, P. and S. Kille, "The COSINE and Internet X.500/
Schema", RFC 1274, November 1991./
/
[RFC1847] Galvin, J., Murphy, S., Crocker, S. and N. Freed, "Security/
Multiparts for MIME: Multipart/Signed and/
Multipart/Encrypted", RFC 1847, October 1995./
/
[RFC2068] Fielding, R., Gettys, J., Mogul, J., Frystyk, H. and T./
Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC/
2068, January 1997./
/
[RFC2079] Smith, M., "Definition of an X.500 Attribute Type and an/
Object Class to Hold Uniform Resource Identifiers (URIs)",/
RFC 2079, January 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):
|
|
|
None
|
|
