HTTP/1.1 200 OK Date: Tue, 09 Apr 2002 00:51:29 GMT Server: Apache/1.3.20 (Unix) Last-Modified: Wed, 27 Nov 1996 00:17:00 GMT ETag: "304d85-1fa9-329b887c" Accept-Ranges: bytes Content-Length: 8105 Connection: close Content-Type: text/plain The inetOrgPerson Object Class Mark Smith INTERNET-DRAFT Netscape Communications 24 November 1996 Definition of the inetOrgPerson Object Class Filename: draft-ietf-asid-inetorgperson-00.txt Status of this Memo This document is an Internet-Draft. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet- Drafts as reference material or to cite them other than as ``work in progress.'' To learn the current status of any Internet-Draft, please check the ``1id-abstracts.txt'' listing contained in the Internet- Drafts Shadow Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or ftp.isi.edu (US West Coast). This document provides information to the Internet community. It does not specify any standard. Distribution of this memo is unlimited. Comments may be sent to the author (mcs@netscape.com). Public discussion will take place on the IETF ASID mailing list (ietf-asid@umich.edu). This Internet Draft expires on 24 May 1997. Abstract While the X.500 standards define many useful attribute types [1] and object classes [2], 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 that extends the X.521 standard organizationalPerson class to meet these needs. Background and Intended Usage The inetOrgPerson object class is a general purpose object class that holds attributes about people. The attributes it holds were chosen M. Smith IETF ASID Working Group [Page 1] INTERNET-DRAFT The inetOrgPerson Object Class 24 November 1996 to accommodate information requirements found in typical Internet and Intranet directory service deployments. The inetOrgPerson object class is designed to be used within directory services based on LDAP [3] and the X.500 [4] family of protocols, and it should be useful in other contexts as well. The attributes that are used but not defined is this document are included in the LDAPv3 Standard and Pilot Attribute Definitions [5]. The notation used in this document is also the same as that used in [5]. New Attribute Types Used in the inetOrgPerson Object Class ( 2.16.840.1.113730.3.1.1 NAME 'carLicense' DESC 'automobile license plate number' EQUALITY caseIgnoreMatch SUBSTRINGS caseIgnoreSubstringsMatch SYNTAX 'DirectoryString' ) ( 2.16.840.1.113730.3.1.2 NAME 'departmentNumber' DESC 'numerically identifies a department within an organization' EQUALITY caseIgnoreMatch SUBSTRINGS caseIgnoreSubstringsMatch SYNTAX 'DirectoryString' ) ( 2.16.840.1.113730.3.1.3 NAME 'employeeNumber' DESC 'numerically identifies an employee within an organization' EQUALITY caseIgnoreMatch SUBSTRINGS caseIgnoreSubstringsMatch SYNTAX 'DirectoryString' ) ( 2.16.840.1.113730.3.1.4 NAME 'employeeType' DESC 'a person's type of employment' EQUALITY caseIgnoreMatch SUBSTRINGS caseIgnoreSubstringsMatch SYNTAX 'DirectoryString' ) M. Smith IETF ASID Working Group [Page 2] INTERNET-DRAFT The inetOrgPerson Object Class 24 November 1996 Definition of the inetOrgPerson Object Class ( 2.16.840.1.113730.3.2.2 NAME 'inetOrgPerson' SUP organizationalPerson STRUCTURAL MAY ( audio $ businessCategory $ carLicense $ departmentNumber $ employeeNumber $ employeeType $ givenName $ homePhone $ homePostalAddress $ initials $ jpegPhoto $ labeledURI $ mail $ manager $ mobile $ pager $ photo $ roomNumber $ secretary $ uid $ userCertificate $ x500uniqueIdentifier ) ) For reference, we list the following additional attribute types which are inherited from organizationalPerson (which in turn is derived from the person object class): MUST ( objectClass $ sn $ cn ) MAY ( description $ seeAlso $ telephoneNumber $ userPassword $ destinationIndicator $ facsimileTelephoneNumber $ internationaliSDNNumber $ l $ ou $ physicalDeliveryOfficeName $ postOfficeBox $ postalAddress $ postalCode $ preferredDeliveryMethod $ registeredAddress $ st $ street $ telephoneNumber $ teletexTerminalIdentifier $ telexNumber $ title $ x121Address $ ) Example of an inetOrgPerson Entry The following example is expressed using the LDIF notation defined in [6]. dn: cn=Barbara Jensen, ou=Product Development, o=Ace Industry, c=US objectClass: top objectClass: person objectClass: organizationalPerson objectClass: inetOrgPerson cn: Barbara Jensen cn: Babs Jensen sn: Jensen givenName: Barbara initials: BJJ title: manager, product development M. Smith IETF ASID Working Group [Page 3] INTERNET-DRAFT The inetOrgPerson Object Class 24 November 1996 uid: bjensen mail: bjensen@aceindustry.com telephoneNumber: +1 408 555 1862 facsimileTelephoneNumber: +1 408 555 1992 mobile: +1 408 555 1941 roomNumber: 0209 carLicense: 6ABC246 departmentNumber: 2604 employeeNumber: 42 employeeType: full time labeledURI: http://www.aceindustry.com/users/bjensen My Home Page Security Considerations Security considerations are not discussed in this memo. Acknowledgments The Netscape Directory Server team created the inetOrgPerson object class based on experience and customer requirements. Anil Bhavnani and John Kristian in particular deserve credit for all of the early design work. References [1] Information Processing Systems -- Open Systems Interconnection -- The Directory: Selected Attribute Types. Recommendation X.520. ISO/IEC JTC 1/SC21; International Standard 9594-6, 1993. [2] Information Processing Systems -- Open Systems Interconnection -- The Directory: Selected Object Classes. Recommendation X.521. ISO/IEC JTC 1/SC21; International Standard 9594-7, 1993. [3] W. Yeong, T. Howes, S. Kille, "Lightweight Directory Access Protocol", RFC 1777, March 1995, [4] Information Processing Systems -- Open Systems Interconnection -- The Directory: Overview of Concepts, Models and Service. ISO/IEC JTC 1/SC21; International Standard 9594-1, 1988. [5] M. Wahl, A. Coulbeck, T. Howes, S. Kille, "Lightweight Directory Access Protocol: Standard and Pilot Attribute Definitions", Internet Draft (work in progress), October 1996, . M. Smith IETF ASID Working Group [Page 4] INTERNET-DRAFT The inetOrgPerson Object Class 24 November 1996 [6] G. Good, "The LDAP Data Interchange Format (LDIF)", Internet Draft (work in progress), November 1996. Author's Address Mark Smith Netscape Communications Corp. 501 E. Middlefield Rd. Mountain View, CA 94043, USA Phone: +1 415 937-3477 EMail: mcs@netscape.com This Internet Draft expires on 24 May 1997. M. Smith IETF ASID Working Group [Page 5]