rfc1617.txt

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

RFC 1617      Naming and Structuring Guidelines for X.500       May 1994


   postalCode [X.520]

      The postalCode will be the same as used in the postalAddress (in
      international notation).

      Example: CH-8001

   streetAddress [X.520]

      It shall be the street where the person has its office. Mostly, it
      will be the street part of the postalAddress.

      Example: Limmatquai 138

4.4.7 Telecom Attributes

   telephoneNumber, facsimileTelephoneNumber & iSDNAddress [X.520]

      The phone number in the international notation according to CCITT
      E.123. The separator '-' instead of space may be used according to
      the local habit, it should be used consistently within a country.

      Format: "+" <country code> <national number> ["x" <extension>]
      Example: [phone]

   telexNumber [X.520]

      The telex number in the international notation

      Example: 817379, ch, ehhg

5. Miscellany

   This section draws attention to two areas which frequently provoke
   questions, and where it is felt that a consistent approach will be
   useful.

5.1 Schema consistency of aliases

   According to the letter of the standard, an alias may point at any
   entry. It is beneficial for aliases to be 'schema consistent'.

   The following two checks should be made:

      1.   The Relative Distinguished Name of the alias should use an
           attribute type normally used for naming entries of the
           object class of the main entry.




RARE Working Group on Network Applications Support (WG-NAP)    [Page 22]

RFC 1617      Naming and Structuring Guidelines for X.500       May 1994


      2.   If the entry (aliased object) were placed where the alias
           is, there should be no schema violation.

5.2 Organisational Units

   There is a problem that many organisations can be either
   organisations or organisational units, dependent on the location in
   the DIT (with aliases giving the alternate names). For example, an
   organisation may be an independent national organisation and also an
   organisational unit of a parent organisation. To achieve this, it is
   important to allow an entry to be of both object class organisation
   and of object class organisational unit.

6. References

   [1] Barker, P., and S. Hardcastle-Kille, "The COSINE and Internet
       X.500 schema", RFC 1274, Department of Computer Science,
       University College London, November 1991.

   [2] "The Directory --- Overview of concepts, models and services",
       CCITT X.500 Series Recommendations, December 1988.

   [3] The North American Directory Forum. "A Naming Scheme for C=US",
       RFC 1255, NADF-175, NADF, September 1991.

   [4] Michaelson, G., and M. Prior, "Naming Guidelines for the AARNet
       X.500 Directory Service", RFC 1562, AEN-001, The University of
       Queensland, The University of Adelaide, December 1993.

   [5] Hardcastle-Kille, S., "Using the OSI Directory to achieve user
       friendly naming", RFC 1484, Department of Computer Science,
       University College London, July 1993.

   [6] Barker, P., "Preparing data for inclusion in an X.500 Directory",
       Research Note RN/92/41, Department of Computer Science,
       University College London, May 1992.

   [7] Jeunink, E., and E. Huizer, "Directory Services and Privacy
       Issues", RARE WG-DATMAN, TF-LEGAL, Work in Progress, May 1993.

   [8] Howes, T., Kille, S., Yeong, W., and C. Robbins, "The X.500
       String Representation of Standard Attribute Syntaxes", RFC 1488,
       University of Michigan, ISODE Consortium, Performance Systems
       International, NeXor Ltd., July 1993.

7. Security Considerations

   Security issues are not substantially discussed in this memo.



RARE Working Group on Network Applications Support (WG-NAP)    [Page 23]

RFC 1617      Naming and Structuring Guidelines for X.500       May 1994


8. Authors' Addresses

   Paul Barker
   Department of Computer Science
   University College London
   Gower Street
   London WC1E 6BT
   England

   Phone: [phone]
   EMail: [e-mail]

   DN:  CN=Paul Barker, OU=Computer Science, O=University College
        London, C=GB

   UFN: Paul Barker, Computer Science, UCL, GB


   Steve Kille
   ISODE Consortium
   The Dome
   The Square
   Richmond TW9 1DT
   England

   Phone: [phone]
   EMail: [e-mail]

   DN:  CN=Steve Kille, O=ISODE Consortium, C=GB

   UFN: S. Kille, ISODE   Consortium, GB


   Thomas Lenggenhager
   SWITCH
   Limmatquai 138
   CH-8001 Zurich
   Switzerland

   Phone: [phone]
   EMail: [e-mail]

   DN:  CN=Thomas Lenggenhager, O=SWITCH, C=CH

   UFN: Thomas Lenggenhager, SWITCH, CH






RARE Working Group on Network Applications Support (WG-NAP)    [Page 24]

RFC 1617      Naming and Structuring Guidelines for X.500       May 1994


9. Appendix - Example Entries

9.1 Country

    DN: C=CH

    objectClass=top & country & domainRelatedObject & friendlyCountry
    country=CH
    associatedDomain=ch
    friendlyCountryName=CH
    friendlyCountryName=Confoederatio Helvetica
    friendlyCountryName=Schweiz
    friendlyCountryName=Suisse
    friendlyCountryName=Svizzera
    friendlyCountryName=Switzerland

9.2 Organisation

    DN: O=SWITCH, C=CH

    objectClass=top & organization & mhsUser & domainRelatedObject
    description=Swiss Academic and Research Network
    organizationName=SWIss TeleCommunication system for Higher
    education\and research
    organizationName=Swiss Academic and Research Network
    organizationName=SWITCH
    localityName=Zuerich
    localityName=Zurich
    localityName={T.61}Z\c8urich
    stateOrProvinceName=ZH
    stateOrProvinceName=Zuerich
    stateOrProvinceName=Zurich
    stateOrProvinceName={T.61}Z\c8urich
    postalAddress=SWITCH
                  Limmatquai 138
                  CH-8001 Zurich
    postalCode=CH-8001
    streetAddress=Limmatquai 138
    telephoneNumber=[phone]
    facsimileTelephoneNumber=[phone]
    seeAlso=CN=Postmaster, O=SWITCH, C=CH
    mhsORAddresses=S=postmaster, O=switch; P=switch; A=arcom; C=ch;
    associatedDomain=switch.ch








RARE Working Group on Network Applications Support (WG-NAP)    [Page 25]

RFC 1617      Naming and Structuring Guidelines for X.500       May 1994


9.3 Organisation Unit

    DN: OU=SWITCHdirectory, O=SWITCH, C=CH

    objectClass=top & organizationalUnit
    description=The SWITCH X.500 pilot project
    organizationalUnitName=SWITCHdirectory
    localityName=Zurich
    localityName=Zuerich
    localityName={T.61}Z\c8urich
    stateOrProvinceName=Zurich
    stateOrProvinceName=Zuerich
    stateOrProvinceName=ZH
    stateOrProvinceName={T.61}Z\c8urich
    postalAddress=SWITCHdirectory
                  SWITCH
                  Limmatquai 138
                  CH-8001 Zurich
    postalCode=CH-8001
    streetAddress=Limmatquai 138
    telephoneNumber=[phone]
    facsimileTelephoneNumber=[phone]

9.4 Organizational Role

    DN: CN=Directory Manager, O=SWITCH, C=CH

    objectClass=top & organizationalRole & mhsUser
    commonName=Directory Manager
    description=SWITCH Directory Managers
    roleOccupant=CN=Martin Berli, O=SWITCH, C=CH
    roleOccupant=CN=Thomas Lenggenhager, O=SWITCH, C=CH
    localityName=Zuerich
    localityName=Zurich
    localityName={T.61}Z\c8urich
    stateOrProvinceName=Zurich
    stateOrProvinceName=Zuerich
    stateOrProvinceName=ZH
    stateOrProvinceName={T.61}Z\c8urich
    postalAddress=SWITCHdirectory
                  SWITCH
                  Limmatquai 138
                  CH-8001 Zurich
    postalCode=CH-8001
    streetAddress=Limmatquai 138
    telephoneNumber=[phone]
    facsimileTelephoneNumber=[phone]
    mhsORAddresses=S=switchinfo; O=switch; P=switch; A=arcom; C=ch;



RARE Working Group on Network Applications Support (WG-NAP)    [Page 26]

RFC 1617      Naming and Structuring Guidelines for X.500       May 1994


    DN: CN=Postmaster, O=SWITCH, C=CH

    objectClass=top & organizationalRole & mhsUser
    commonName=Postmaster
    commonName=Helpdesk
    roleOccupant=CN=Christoph Graf, O=SWITCH, C=CH
    roleOccupant=CN=Felix Kugler, O=SWITCH, C=CH
    roleOccupant=CN=Marcel Parodi, O=SWITCH, C=CH
    roleOccupant=CN=Marcel Schneider, O=SWITCH, C=CH
    telephoneNumber=[phone]
    facsimileTelephoneNumber=[phone]
    mhsORAddresses=S=postmaster; O=switch; P=switch; A=arcom; C=ch;

    DN: CN=Secretary, O=SWITCH, C=CH

    objectClass=top & organizationalRole & quipuObject
    commonName=Secretary
    roleOccupant=CN=Franziska Remund, O=SWITCH, C=CH

































RARE Working Group on Network Applications Support (WG-NAP)    [Page 27]

RFC 1617      Naming and Structuring Guidelines for X.500       May 1994


9.5 Person

    DN: CN=Thomas Lenggenhager, O=SWITCH, C=CH

    objectClass=top & person & organizationalPerson & mhsUser &
    pilotObject & newPilotPerson
    commonName=Thomas Lenggenhager
    commonName=T. Lenggenhager
    surname=Lenggenhager
    description=SWITCHinfo, Project Leader
    localityName=Zuerich
    localityName=Zurich
    localityName={T.61}Z\c8urich
    stateOrProvinceName=ZH
    stateOrProvinceName=Zuerich
    stateOrProvinceName=Zurich
    stateOrProvinceName={T.61}Z\c8urich
    postalAddress=SWITCH
                  Limmatquai 138
                  CH-8001 Zurich
    postalCode=CH-8001
    streetAddress=Limmatquai 138
    telephoneNumber=[phone]
    facsimileTelephoneNumber=[phone]
    mhsORAddresses=S=lenggenhager; O=switch; P=switch; A=arcom; C=ch;
    userPassword=secret
    textEncodedORaddress={T.61}S=lenggenhager; O=switch; P=switch; \
                                  A=arcom; C=ch;
    rfc822mailbox=[e-mail]
    secretary=CN=Franziska Remund, O=SWITCH, C=CH





















RARE Working Group on Network Applications Support (WG-NAP)    [Page 28]