rfc1255.txt

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

   National Standards Institute (ANSI) registers the names of the States
   in the United States of America!  That right and duty is clearly
   reserved to the Government of the United States of America.

   On the other hand, in the Internet DNS, the act of inserting a given
   rightfully-usable name and address entry into a nameserver
   constitutes simultaneous registration and directory publication.

4.  Structuring Objects

   The first step in providing a civil naming infrastructure is to model
   the geographical/governmental entities which provide a basis for the
   assignment of public names.

4.1.  The National Level

   The nation is modeled with an object of class "country", subordinate
   to the root of the DIT, and has an RDN consisting of a single
   attribute value assertion:

            countryName= US

   The entry (minimally) contains these attributes:

            objectClass= country
            description= United States of America

4.2.  The Regional Level

   Within the nation, there are regions.  Each region corresponds to a
   state or state-equivalent as recognized by the US Congress.  The list
   of these is maintained in US FIPS 5.  A sample entry from this FIPS
   document looks like this:









NADF                                                            [Page 7]

RFC 1255                A Naming Scheme for c=US          September 1991


          +------------+---------+-------+
          |            |  State  | State |
          |  FIPS-5    | Numeric | Alpha |
          |   Name     |  Code   | Code  |
          +------------+---------+-------+
          |            |         |       |
          | California |   06    |  CA   |
          |            |         |       |
          +------------+---------+-------+

          Each region is modeled with an object of class
          "usStateOrEquivalent", which is defined thusly:

             usStateOrEquivalent OBJECT-CLASS
                SUBCLASS OF locality, nadfObject
                MUST CONTAIN { localityName,
                               fipsStateNumericCode,
                               fipsStateAlphaCode,
                               stateOrProvinceName }



          Each entry is subordinate to "c=US", and has an RDN consisting
          of a single attribute value assertion:

            stateOrProvinceName= <FIPS-5 name>

          e.g.,

            stateOrProvinceName= California


          Each entry (minimally) contains these attributes:

            objectClass= usStateOrEquivalent
            description= <official name of region>
            localityName= <FIPS-5 name>
            localityName= <FIPS-5 state alpha code>
            fipsStateAlphaCode= <FIPS-5 state alpha code>
            fipsStateNumericCode= <FIPS-5 state numeric code>

          e.g.,

            objectClass= usStateOrEquivalent
            description= State of California
            localityName= California
            localityName= CA
            fipsStateAlphaCode= CA



NADF                                                            [Page 8]

RFC 1255                A Naming Scheme for c=US          September 1991


            fipsStateNumericCode= 06

4.3.  The Local Level

   Within each region, there are places.  Each place corresponds to a
   county or county-equivalent as recognized by the regional government.
   The list of these is maintained in US FIPS 55 as a populated place
   with a five-digit numeric place code starting with "99." A sample
   entry from this FIPS document looks like this:

      +---------+---------+-------+-----+----------------------+-----+
      |  State  |  Place  | State |     |                      |     |
      | Numeric | Numeric | Alpha |     |        FIPS-55       |     |
      |  Code   |  Code   | Code  |     |         Name         |     |
      +---------+---------+-------+-----+----------------------+-----+
      |         |         |       |     |                      |     |
      |   06    |  99085  |  CA   | ... | Santa Clara (County) | ... |
      |         |         |       |     |                      |     |
      +---------+---------+-------+-----+----------------------+-----+

      (Any parenthetical text in the FIPS-55 name is considered a
      "remark" about the place.)


          Each county is modeled with an object of class
          "usCountyOrEquivalent", which is defined thusly:

            usPlace OBJECT-CLASS
                SUBCLASS OF locality, nadfObject
                MUST CONTAIN { localityName,
                               fipsPlaceNumericCode }

            usCountyOrEquivalent OBJECT-CLASS
                SUBCLASS OF usPlace
                MUST CONTAIN { fipsCountyNumericCode }

          Each entry is subordinate to the entry naming the region which
          contains the county, and has an RDN consisting of a single
          attribute value assertion:

            localityName= <FIPS-55 name without remarks>

          e.g.,

            localityName= Santa Clara


          Each entry (minimally) contains these attributes:



NADF                                                            [Page 9]

RFC 1255                A Naming Scheme for c=US          September 1991


            objectClass= usCountyOrEquivalent
            fipsPlaceNumericCode= <FIPS-55 place numeric code>
            fipsCountyNumericCode= <last three digits of FIPS-55
                                    place code>
            stateOrProvinceName= <FIPS-55 state alpha code>
            stateOrProvinceName= <FIPS-5 corresponding name>
            description= <FIPS-55 name with remarks>

          e.g.,

            objectClass= usCountyOrEquivalent
            fipsPlaceNumericCode= 99085
            fipsCountyNumericCode= 085
            stateOrProvinceName= California
            stateOrProvinceName= CA
            description= County of Santa Clara

          In addition, for each populated place named within the county,
          a non-distinguished "localityName" attribute value may be
          present to aid searching, e.g.,

            localityName= Mountain View
            localityName= San Jose

          and so on.

4.4.  ADDMD Operators

   Also within the nation, there are public Directory service providers.
   Each service-provider corresponds to an ADDMD operator as recognized
   by the NADF.  Each ADDMD operator is modeled with an object of class
   "nadfADDMD", which is defined thusly:

            nadfADDMD OBJECT-CLASS
                SUBCLASS OF nadfObject
                MUST CONTAIN { addmdName }
                MAY CONTAIN { organizationName,
                              organizationalAttributeSet }

   Each entry is subordinate to "c=US", and has an RDN consisting of a
   single attribute value assertion:

            addmdName= <NADF registered name>

          e.g.,

            addmdName= PSINet




NADF                                                           [Page 10]

RFC 1255                A Naming Scheme for c=US          September 1991


          Each entry (minimally) contains this attribute:

            objectClass= nadfADDMD

   The structure of the subtree below each "nadfADDMD" entry is a matter
   for that service-provider to establish.  It must be emphasized that
   such entries are used to provide a "private" namespace for each
   service provider, as envisioned in NADF-128.  This "nadfADDMD" entry
   is distinct from a service provider's "organization" entry which
   would be used to contain organizational information about the service
   provider.

4.5.  Summary of Structuring Objects

   To summarize the naming architecture thus far:

+---------------+-----+---------------------+-----+--------------------+
|      Level    |Elem |     objectClass     |Supr |        RDN         |
+---------------+-----+---------------------+-----+--------------------+
|          root |  0  |                     |     |                    |
+---------------+-----+---------------------+-----+--------------------+
| international |  1  | country             |  0  | countryName        |
+---------------+-----+---------------------+-----+--------------------+
|      national |  2  | usStateOrEquivalent |  1  | stateOrProvinceName|
|               |  3  | nadfADDMD           |  1  | addmdName          |
+---------------+-----+---------------------+-----+--------------------+
|      regional |  4  | usCountyOrEquivalent|  2  | localityName       |
+---------------+-----+---------------------+-----+--------------------+
|         local |  5  | ...                 |  4  | ...                |
+---------------+-----+---------------------+-----+--------------------+

          Or, in pictorial form:



















NADF                                                           [Page 11]

RFC 1255                A Naming Scheme for c=US          September 1991


                                                  root
                                                   /
                                                  /
                                                 /
                                             (----)
                                             (c=US)
                                             (----)
                                              / | \
                                             /  |  \
                               /------------/   |   \------\
                              /                 |           \
        for each state or (------)             / \     (---------) for
         state-equivalent (st=...)            /   \    (addmd=...) each
                          (------)           /     \   (---------) ADDMD
                           /    \           /       \
                          /      \         /national \
            /------------/        \       / listings  \
           /                       \      -------------
          /                         \
       (-----) for each             /\
       (l=...) county or           /  \
       (-----) county-equivalent  /    \
          |                      /      \
          |                     /regional\
          |                    / listings \
          |                    ------------
         / \
        /   \
       /     \
      / local \
     /listings \
     -----------


5.  Entity Objects

   The next step in using the civil naming infrastructure is to model
   the entities which reside within the geographical/governmental
   structure.

5.1.  Organizations

   Organizations exist at several levels.

5.1.1.  Kinds of Organizations

   An organization is said to have national-standing if it is chartered
   (created and named) by the US Congress. An example of such an



NADF                                                           [Page 12]

RFC 1255                A Naming Scheme for c=US          September 1991


   organization might be a national laboratory.  There is no other
   entity which is empowered by government to confer national-standing
   on organizations.  However, ANSI maintains an alphanumeric nameform
   registration for organizations, and this will be used as the public
   directory service basis for conferring national-standing on private
   organizations.

   An organization is said to have regional-standing if it is chartered
   by the government of that region.  An example of such an organization
   might be a public university.  In addition, private organizations may
   achieve regional-standing by registering with the "Secretary of
   State" (or similar entity) within that region -- this is termed a
   "doing business as" (DBA) registration.

                                   NOTE:

         An organization may have a DBA registration in several states,
         even though it is incorporated in only one state.  Where an
         organization registers itself is largely dependent on where it
         might choose to incorporate, and where it might choose to
         locate (and license) its business operations.

         For example, a large organization might have a DBA registration
         in most of the 50 states, and be incorporated in Delaware.  For