rfc1274.txt

著名的RFC文档,其中有一些文档是已经翻译成中文的的.

   classes is reproduced for completeness in Appendix C.

8.2.  X.400 standard object classes

   A number of object classes defined in X.400 are supported.  Refer to
   X.402 for descriptions of the usage of these object classes.  The
   ASN.1 for these object classes is reproduced for completeness in
   Appendix C.

8.3.  COSINE/Internet object classes

   This section attempts to fuse together the object classes designed
   for use in the COSINE and Internet pilot activities.  Descriptions



Barker & Kille                                                  [Page 8]

RFC 1274            COSINE and Internet X.500 Schema       November 1991


   are given of the suggested usage of these object classes.  The ASN.1
   for these object classes is also reproduced in Appendix C.

8.3.1.  Pilot Object

   The PilotObject object class is used as a sub-class to allow some
   common, useful attributes to be assigned to entries of all other
   object classes.

     pilotObject OBJECT-CLASS
         SUBCLASS OF top
         MAY CONTAIN {
             info,
             photo,
             manager,
             uniqueIdentifier,
             lastModifiedTime,
             lastModifiedBy,
             dITRedirect,
             audio}
     ::= {pilotObjectClass 3}

8.3.2.  Pilot Person

   The PilotPerson object class is used as a sub-class of person, to
   allow the use of a number of additional attributes to be assigned to
   entries of object class person.

     pilotPerson OBJECT-CLASS
         SUBCLASS OF person
         MAY CONTAIN {
                     userid,
                     textEncodedORAddress,
                     rfc822Mailbox,
                     favouriteDrink,
                     roomNumber,
                     userClass,
                     homeTelephoneNumber,
                     homePostalAddress,
                     secretary,
                     personalTitle,
                     preferredDeliveryMethod,
                     businessCategory,
                     janetMailbox,
                     otherMailbox,
                     mobileTelephoneNumber,
                     pagerTelephoneNumber,
                     organizationalStatus,



Barker & Kille                                                  [Page 9]

RFC 1274            COSINE and Internet X.500 Schema       November 1991


                     mailPreferenceOption,
                     personalSignature}
     ::= {pilotObjectClass 4}

8.3.3.  Account

   The Account object class is used to define entries representing
   computer accounts.  The userid attribute should be used for naming
   entries of this object class.

     account OBJECT-CLASS
         SUBCLASS OF top
         MUST CONTAIN {
             userid}
         MAY CONTAIN {
             description,
             seeAlso,
             localityName,
             organizationName,
             organizationalUnitName,
             host}
     ::= {pilotObjectClass 5}

8.3.4.  Document

   The Document object class is used to define entries which represent
   documents.

     document OBJECT-CLASS
         SUBCLASS OF top
         MUST CONTAIN {
             documentIdentifier}
         MAY CONTAIN {
             commonName,
             description,
             seeAlso,
             localityName,
             organizationName,
             organizationalUnitName,
             documentTitle,
             documentVersion,
             documentAuthor,
             documentLocation,
             documentPublisher}
     ::= {pilotObjectClass 6}






Barker & Kille                                                 [Page 10]

RFC 1274            COSINE and Internet X.500 Schema       November 1991


8.3.5.  Room

   The Room object class is used to define entries representing rooms.
   The commonName attribute should be used for naming pentries of this
   object class.

     room OBJECT-CLASS
         SUBCLASS OF top
         MUST CONTAIN {
             commonName}
         MAY CONTAIN {
             roomNumber,
             description,
             seeAlso,
             telephoneNumber}
     ::= {pilotObjectClass 7}

8.3.6.  Document Series

   The Document Series object class is used to define an entry which
   represents a series of documents (e.g., The Request For Comments
   papers).

     documentSeries OBJECT-CLASS
         SUBCLASS OF top
         MUST CONTAIN {
             commonName}
         MAY CONTAIN {
             description,
             seeAlso,
             telephoneNumber,
             localityName,
             organizationName,
             organizationalUnitName}
     ::= {pilotObjectClass 9}

8.3.7.  Domain

   The Domain object class is used to define entries which represent DNS
   or NRS domains.  The domainComponent attribute should be used for
   naming entries of this object class.  The usage of this object class
   is described in more detail in [3].

     domain OBJECT-CLASS
         SUBCLASS OF top
         MUST CONTAIN {
             domainComponent}
         MAY CONTAIN {



Barker & Kille                                                 [Page 11]

RFC 1274            COSINE and Internet X.500 Schema       November 1991


             associatedName,
             organizationName,
             organizationalAttributeSet}
     ::= {pilotObjectClass 13}

8.3.8.  RFC822 Local Part

   The RFC822 Local Part object class is used to define entries which
   represent the local part of RFC822 mail addresses.  This treats this
   part of an RFC822 address as a domain.  The usage of this object
   class is described in more detail in [3].

     rFC822localPart OBJECT-CLASS
         SUBCLASS OF domain
         MAY CONTAIN {
             commonName,
             surname,
             description,
             seeAlso,
             telephoneNumber,
             postalAttributeSet,
             telecommunicationAttributeSet}
     ::= {pilotObjectClass 14}

8.3.9.  DNS Domain

   The DNS Domain (Domain NameServer) object class is used to define
   entries for DNS domains.  The usage of this object class is described
   in more detail in [3].

     dNSDomain OBJECT-CLASS
         SUBCLASS OF domain
         MAY CONTAIN {
             ARecord,
             MDRecord,
             MXRecord,
             NSRecord,
             SOARecord,
             CNAMERecord}
     ::= {pilotObjectClass 15}

8.3.10.  Domain Related Object

   The Domain Related Object object class is used to define entries
   which represent DNS/NRS domains which are "equivalent" to an X.500
   domain: e.g., an organisation or organisational unit.  The usage of
   this object class is described in more detail in [3].




Barker & Kille                                                 [Page 12]

RFC 1274            COSINE and Internet X.500 Schema       November 1991


     domainRelatedObject OBJECT-CLASS
         SUBCLASS OF top
         MUST CONTAIN {
             associatedDomain}
     ::= {pilotObjectClass 17}

8.3.11.  Friendly Country

   The Friendly Country object class is used to define country entries
   in the DIT.  The object class is used to allow friendlier naming of
   countries than that allowed by the object class country.  The naming
   attribute of object class country, countryName, has to be a 2 letter
   string defined in ISO 3166.

     friendlyCountry OBJECT-CLASS
         SUBCLASS OF country
         MUST CONTAIN {
             friendlyCountryName}
     ::= {pilotObjectClass 18}

8.3.12.  Simple Security Object

   The Simple Security Object object class is used to allow an entry to
   have a userPassword attribute when an entry's principal object
   classes do not allow userPassword as an attribute type.

     simpleSecurityObject OBJECT-CLASS
         SUBCLASS OF top
         MUST CONTAIN {
             userPassword }
     ::= {pilotObjectClass 19}

8.3.13.  Pilot Organization

   The PilotOrganization object class is used as a sub-class of
   organization and organizationalUnit to allow a number of additional
   attributes to be assigned to entries of object classes organization
   and organizationalUnit.

     pilotOrganization OBJECT-CLASS
         SUBCLASS OF organization, organizationalUnit
         MAY CONTAIN {
                     buildingName}
     ::= {pilotObjectClass 20}







Barker & Kille                                                 [Page 13]

RFC 1274            COSINE and Internet X.500 Schema       November 1991


8.3.14.  Pilot DSA

   The PilotDSA object class is used as a sub-class of the dsa object
   class to allow additional attributes to be assigned to entries for
   DSAs.

     pilotDSA OBJECT-CLASS
         SUBCLASS OF dsa
         MUST CONTAIN {
             dSAQuality}
     ::= {pilotObjectClass 21}

8.3.15.  Quality Labelled Data

   The Quality Labelled Data object class is used to allow the
   assignment of the data quality attributes to subtrees in the DIT.

   See [8] for more details.

     qualityLabelledData OBJECT-CLASS
         SUBCLASS OF top
         MUST CONTAIN {
             dSAQuality}
         MAY CONTAIN {
             subtreeMinimumQuality,
             subtreeMaximumQuality}
     ::= {pilotObjectClass 22}

9.  Attribute Types

9.1.  X.500 standard attribute types

   A number of generally useful attribute types are defined in X.520,
   and these are supported.  Refer to that document for descriptions of
   the suggested usage of these attribute types.  The ASN.1 for these
   attribute types is reproduced for completeness in Appendix C.

9.2.  X.400 standard attribute types

   The standard X.400 attribute types are supported.  See X.402 for full
   details.  The ASN.1 for these attribute types is reproduced in
   Appendix C.

9.3.  COSINE/Internet attribute types

   This section describes all the attribute types defined for use in the
   COSINE and Internet pilots.  Descriptions are given as to the
   suggested usage of these attribute types.  The ASN.1 for these



Barker & Kille                                                 [Page 14]

RFC 1274            COSINE and Internet X.500 Schema       November 1991


   attribute types is reproduced in Appendix C.

9.3.1.  Userid

   The Userid attribute type specifies a computer system login name.

     userid ATTRIBUTE
         WITH ATTRIBUTE-SYNTAX
             caseIgnoreStringSyntax
             (SIZE (1 .. ub-user-identifier))
     ::= {pilotAttributeType 1}

9.3.2.  Text Encoded O/R Address

   The Text Encoded O/R Address attribute type specifies a text encoding
   of an X.400 O/R address, as specified in RFC 987.  The use of this
   attribute is deprecated as the attribute is intended for interim use
   only.  This attribute will be the first candidate for the attribute
   expiry mechanisms!

     textEncodedORAddress ATTRIBUTE
         WITH ATTRIBUTE-SYNTAX
             caseIgnoreStringSyntax
         (SIZE (1 .. ub-text-encoded-or-address))
     ::= {pilotAttributeType 2}

9.3.3.  RFC 822 Mailbox

   The RFC822 Mailbox attribute type specifies an electronic mailbox
   attribute following the syntax specified in RFC 822.  Note that this
   attribute should not be used for greybook or other non-Internet order
   mailboxes.

     rfc822Mailbox ATTRIBUTE
         WITH ATTRIBUTE-SYNTAX
             caseIgnoreIA5StringSyntax
             (SIZE (1 .. ub-rfc822-mailbox))
     ::= {pilotAttributeType 3}

9.3.4.  Information

   The Information attribute type specifies any general information
   pertinent to an object.  It is recommended that specific usage of
   this attribute type is avoided, and that specific requirements are
   met by other (possibly additional) attribute types.

     info ATTRIBUTE
         WITH ATTRIBUTE-SYNTAX



Barker & Kille                                                 [Page 15]

RFC 1274            COSINE and Internet X.500 Schema       November 1991


             caseIgnoreStringSyntax
             (SIZE (1 .. ub-information))
     ::= {pilotAttributeType 4}

9.3.5.  Favourite Drink

   The Favourite Drink attribute type specifies the favourite drink of
   an object (or person).

     favouriteDrink ATTRIBUTE
         WITH ATTRIBUTE-SYNTAX
             caseIgnoreStringSyntax
             (SIZE (1 .. ub-favourite-drink))
     ::= {pilotAttributeType 5}

9.3.6.  Room Number

   The Room Number attribute type specifies the room number of an
   object.  Note that the commonName attribute should be used for naming
   room objects.