RFC 2798 on The LDAP inetOrgPerson Object Class

RFC Editor <rfc-ed@ISI.EDU> Mon, 24 April 2000 23:22 UTC

Message-Id: <200004242252.PAA21189@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2798 on The LDAP inetOrgPerson Object Class
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Mon, 24 Apr 2000 15:52:59 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

A new Request for Comments is now available in online RFC libraries.


        RFC 2798

        Title:	    Definition of the inetOrgPerson LDAP Object Class 
        Author(s):  M. Smith
        Status:     Informational
	Date:       April 2000
        Mailbox:    mcs@netscape.com
        Pages:      20
        Characters: 32929
        Updates/Obsoletes/SeeAlso: None    

        I-D Tag:    draft-smith-ldap-inetorgperson-04.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2798.txt


While the X.500 standards define many useful attribute types [X520]
and object classes [X521], they do not define a person object class
that meets the requirements found in today's Internet and Intranet
directory service deployments.  We define a new object class called
inetOrgPerson for use in LDAP and X.500 directory services that
extends the X.521 standard organizationalPerson class to meet these
needs. 

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

ftp://ftp.isi.edu/in-notes/rfc2798.txt"><ftp://ftp.isi.edu/in-notes/rfc2798.txt>

RFC 2798 on The LDAP inetOrgPerson Object Class RFC Editor