rfc1218.txt

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

               organization

          object is used.  The RDN is formed as

               organizationName is <registered name of organization>

          e.g.,

               organizationName is The Tied House

   might provide the RDN for a business entity registered with the City
   of Mountain View.  In this case, the entry thus named would be
   immediately subordinate to the usPlace entry for the City of Mountain
   View.




NADF                                                            [Page 8]

RFC 1218                A Naming Scheme for c=US              April 1991


   Note that other non-distinguished attributes, such as an ANSI numeric
   name form value, may be included in an entry.  (That is, the
   organization object might actually be a usOrganization object.)

          For the Local Government, if any, an instance of an

               organization

          object is also used.  The RDN is formed as:

               organizationName is Government

3.4.  Naming of MHS Distribution Lists

   Naming of MHS distribution lists remains with the scoping DMD.

4.  Optimized Civil Naming

   The structure of the civil component of the architecture can be
   concisely described as:

----------------------------------------------------------------------
Level   Element   objectClass             Superior    RDN
----------------------------------------------------------------------
root    0
----------------------------------------------------------------------
intl.   1         country                 0           countryName
----------------------------------------------------------------------
natl.   2         usStateOrEquivalent     1           localityName
        3         usOganization           1           organizationName
        4         nadfADDMD               1           addmdName
----------------------------------------------------------------------
reg.    5         usPlace                 2           localityName
        6         organization            2           organizationName
----------------------------------------------------------------------
local   7         residentialPerson       5           commonName,
                                                      other
        8         organization            5           organizationName
        9         mhsDistributionList     5           commonName
----------------------------------------------------------------------

   Consider how an interrogation algorithm might locate a residential
   person, given:

   (1)  a string denoting the person's real-world name;

   (2)  a string denoting the real-world name of the populated
        place in which the person lives; and,



NADF                                                            [Page 9]

RFC 1218                A Naming Scheme for c=US              April 1991


   (3)  the Distinguished Name of the state or state-equivalent.

   A straight-forward approach is to initiate a single-level search to
   locate the desired populated place.  The search results in zero or
   more Distinguished Names being returned which correspond to the
   string provided by the user.  Then, for each populated place, a
   subtree search might be initiated to locate the desired residential
   person.  If the number of populated places returned by the first
   search is large, then this strategy is inefficient.

   A better approach would be to initiate a single search, with a filter
   combining the strings for both the person's real-world name and the
   place's real-world name.  Unfortunately, such a search would have to
   involve the whole-subtree anchored at the Distinguished Name for the
   state or state-equivalent, which would be inefficient.

   As such, it may be desirable to optimize the civil naming component
   by listing some entries at a higher level.  This is accomplished by
   using a multi-valued RDN formed by combining the RDNs of the entry
   and its superior.

   There are three cases in civil naming:

   (1)  listing an organization with regional standing at the
        national level;

   (2)  listing an organization with local standing at the
        regional level; and,

   (3)  listing a person with local standing at the regional
        level.

   Hence, under the optimized civil naming component, a single-level
   search, anchored at the Distinguished Name for the state or state-
   equivalent, could be used.  Further, the implementation of a DSA
   supporting this optimization would highly-index the attributes used
   for searching, in order to achieve high-performance.

   In order to clearly indicate that optimized civil naming is in
   effect, a new attribute type, nadfSearchGuide, is introduced.  An
   attribute value of this type is placed in an entry to indicate which
   optimizations are in effect.  Using the residential example above,
   the entry for the state or state-equivalent would contain an
   nadfSearchGuide value indicating that when searching for entries of
   type residentialPerson, a single-level search should be performed
   with a filter containing the logical-and of two terms, one involving
   the commonName attribute, and the other involving the localityName
   attribute.  The nadfSearchGuide is a refinement of the X.500



NADF                                                           [Page 10]

RFC 1218                A Naming Scheme for c=US              April 1991


   searchGuide in that it indicates the depth of the search which should
   be performed, and always contains an indication of the object class
   for which the optimization exists.

   Finally, note that for naming within organizations, this technique
   might also be used.

4.1.  Naming at the National Level

4.1.1.  Organizations with Regional Standing

   An organization with standing within a state or state-equivalent may
   be listed directly under c=US.

   For an organization with regional standing, an instance of an

               organization

          object is used.  The RDN is multi-valued, formed as

               organizationName is <registered name of organization>
               localityName is <FIPS 5 name>

          e.g.,

               organizationName is Network Management Associates
               localityName is California

   It must be emphasized that uniqueness within the RDN comes from using
   the a regional localityName (state or state-Equivalent) in
   association with the correspondent organizationName in that region.

4.2.  Naming within a State or State-Equivalent

4.2.1.  Organizations with Local Standing

   An organization with standing within a populated place may be listed
   directly under its state or state-equivalent.

   For an organization with local standing, an instance of an

               organization

          object is used.  The RDN is multi-valued, formed as

               organizationName is <registered name of organization>
               localityName is <FIPS 55 name>




NADF                                                           [Page 11]

RFC 1218                A Naming Scheme for c=US              April 1991


          e.g.,

               organizationName is The Tied House
               localityName is City of Mountain View

   It must be emphasized that uniqueness within the RDN comes from using
   the a local localityName (populated place) in association with the
   correspondent organizationName in that place.

4.2.2.  Persons

   An person may be listed directly under its state or state-equivalent.

   For such a person, an instance of a

                residentialPerson

   object is used.  The RDN is multi-valued, formed by taking the RDN of
   the person and adding the RDN of the populated place containing the
   person.

                commonName is the Marshall T. Rose
                postalCode is 94043-2112
                localityName is City of Mountain View

   Note that for optimization to occur, the RDN of the person must not
   contain a localityName attribute value.

5.  Organizational Naming

   The internal structure of each usOrganization or organization object
   is a matter for that organization to establish.

   It is strongly recommended that organizationalUnit objects be used
   for structuring.  (If an organization uses a locality-based
   organizational hierarchy, this information can still be represented
   using the

               organizationalUnit

          object.)

6.  ADDMD Naming

   The internal structure of each nadfADDMD object is a matter for that
   service-provider to establish.





NADF                                                           [Page 12]

RFC 1218                A Naming Scheme for c=US              April 1991


7.  Application Naming

   There are (at least) four kinds of OSI entities which may be listed:

   (1)  Application Processes and Entities

   (2)  MHS Distribution Lists

   (3)  EDI Users

   (4)  Devices

7.1.  Naming of Application Processes and Entities

   Naming of OSI application processes and entities remains with the
   scoping DMD.  However, in order to foster interoperability, two
   requirements are made: first, application entity objects must be
   immediately subordinate to application process objects; and, second,
   application entities are represented by the nadfApplicationEntity
   object, which is identical to the applicationEntity object except
   that the presence of an attribute value of
   supportedApplicationContext is mandatory.

7.2.  Naming of MHS Distribution Lists

   Naming of MHS distribution lists remains with the scoping DMD.

7.3.  Naming of EDI Users

   Naming of EDI users remains with the scoping DMD.

7.4.  Naming of Devices

   Naming of OSI devices remains with the scoping DMD.

8.  Usage Examples

   Consider the following examples, expressed in a concise format (read
   left-to-right):

          Federal Government:

               { c=US, o=Government }


          The State of California:

               { c=US, l=California }



NADF                                                           [Page 13]

RFC 1218                A Naming Scheme for c=US              April 1991


          The District of Columbia:

               { c=US, l=District of Columbia }


          An organization with national standing:

               { c=US, o=Performance Systems International }


          An ADDMD:

               { c=US, addmdName=PSINet }


          The Government of the State of California:

               { c=US, l=California, o=Government }


          The Government of the District of Columbia:

               { c=US, l=District of Columbia, o=Government }


          A city within the State of California:

               { c=US, l=California, l=City of Mountain View }


          An organization licensed to operate within the State of
          California:

               { c=US,
                 l=California,
                 o=Network Management Associates, Inc. }


          An optimized listing for a organization with regional
          standing:

               { c=US,
                 { l=California,
                   o=Network Management Associates }}







NADF                                                           [Page 14]

RFC 1218                A Naming Scheme for c=US              April 1991


          A city government:

               { c=US,
                 l=California,
                 l=City of Mountain View,
                 o=Government }


          A residential person:

               { c=US,
                 l=California,
                 l=City of Mountain View,
                 { cn=Marshall T. Rose, postalCode=94043-2112 }}


          An organization licensed to operate within a city:

               { c=US,
                 l=California,
                 l=City of Mountain View,
                 o=The Tied House }


          An entity within the Federal Government:

               { c=US, o=Government, ou=Department of the Air Force }


          An entity within an organization with national standing:

               { c=US,
                 o=Performance Systems International,
                 ou=Marketing }

9.  Acknowledgements

   This document is based on many sources, including, but not limited
   to:

   - Listing Services Database Generic Requirements, Bellcore
     TA-TSY-000985;

   - Common Directory Use ED 013 (Q/511) (EWOS/EGDIR/90/156);
     and,

   - The THORN X.500 Naming Architecture (UCL-45 revision 6.1).




NADF                                                           [Page 15]

RFC 1218                A Naming Scheme for c=US              April 1991


10.  Bibliography

   X.500: The Directory --- Overview of Concepts, Models, and
        Service, CCITT Recommendation X.500, December, 1988.

   US FIPS 5: Codes for the Identification of the States, The
        District of Columbia and Outlying Areas of the United
        States, and Associated Areas, US Department of Commerce
        FIPS 5--2, May 28, 1987.

   US FIPS 6: Counties and Equivalent Entities of the United
        States, its Possessions, and Associated Areas, US
        Department of Commerce FIPS 6--4, August 31, 1990.

   US FIPS 55: Guideline: Codes for Named Populated Places,
        Primary County Divisions, and other Locational Entities