rfc1255.txt
来自「RFC 的详细文档！」· 文本 代码 · 共 1,403 行 · 第 1/4 页
TXT
1,403 行
the purposes of this naming scheme, such an organization is
said to have regional-standing in each state where it has a DBA
registration. This DBA registration confers the sole right to
use the DBA name in association with the named jurisdiction of
the registration authority.
An organization is said to have local-standing if it is chartered by
a local government within that place. In addition, private
organizations may achieve local-standing by registering with a
"County Clerk" (or similar entity) within that place -- this is
termed a "doing business as" (DBA) registration. Note that local-
standing is somewhat ambiguous in that there may be multiple local
governments contained within a county or county-equivalent.
Depending on local government rules of incorporation and containment,
registering with one entity may prevent others from registering that
same name with other entities contained within that place. In order
to avoid ambiguity, other distinguishing attributes, such as
"streetAddress", may be needed to provide uniqueness.
5.1.2. Modeling Organizations
In the DIT, an organization is modeled with an object of
class "organization". In addition, some combination of the
following auxiliary object classes might also be used:
NADF [Page 13]
RFC 1255 A Naming Scheme for c=US September 1991
(1) if an organization has national-standing derived from
ANSI registration, then this is modeled by including in
the entry an object class attribute value of
"ansiOrgObject", which is defined thusly:
ansiOrgObject OBJECT-CLASS
SUBCLASS OF top
MUST CONTAIN { ansiOrgNumericCode }
(2) if an organization has national-standing (either in the
US or some other nation), then it may be necessary to
identify the country which corresponds to the registry
which names the organization. This is modeled by
including in the entry an object class attribute value
of "nationalObject", which is defined thusly:
nationalObject OBJECT-CLASS
SUBCLASS OF top
MUST CONTAIN { countryName }
(3) if an organization has local-standing, then it may be
necessary to identify the place in US FIPS 55 which
corresponds to the registry which names the
organization. This is modeled by including in the
entry an object class attribute value of
"fips55Object", which is defined thusly:
fips55Object OBJECT-CLASS
SUBCLASS OF top
MUST CONTAIN { fipsPlaceNumericCode }
MAY CONTAIN { stateOrProvinceName }
5.2. Persons
There are two kinds of entries for a person: organizational person
and residential person.
Definitions for an organizational person are a local matter to be
decided by each organization. It is suggested that an organizational
person be modeled with an object of class "organizationalPerson".
Outside of organizations, persons exist only in a residential context.
As such they always have local standing. For a given person, it
should always be possible to identify the place in US FIPS 55 which
corresponds to the "smallest" populated place where any person
resides, and then use the code associated with that place to aid in
NADF [Page 14]
RFC 1255 A Naming Scheme for c=US September 1991
distinguishing the person. A residential person is modeled with an
object of class "residentialPerson". In addition, since it may be
necessary to identify the place in US FIPS 55 which corresponds
to where the person resides, an object class attribute value
of "fips55Object" may be present in entries corresponding to
residential persons.
6. Listing Entities
The final step is to define how entities are listed within the
context of the civil naming infrastructure. Note than an entity may
have several listings (DNs) in different parts of the Directory.
6.1. Organizations
The RDN used when listing an organization depends on both the
standing of the organization, and where the listing is to be placed:
+----------------------------------------+
+-------------------| Listing (RDN) under |
| Entity | c=US | c=US, st=X | c=US, st=X, l=Y |
+-------------------+---------+------------+-----------------+
| national-standing | o | o, c=US | o, c=US |
+-------------------+---------+------------+-----------------+
| regional-standing | o, st=X | o | o |
+-------------------+---------+------------+-----------------+
| .. (other region) | | o, st=Z | o, st=Z |
+-------------------+---------+------------+-----------------+
| local-standing | o, st=X | o, fips55 | o, fips55 |
| | fips55 | | |
+-------------------+---------+------------+-----------------+
| .. (other region) | | o, st=Z | o, st=Z, fips55 |
| | | fips55 | |
+-------------------+---------+------------+-----------------+
| foreign-standing | o, ... | o, ..., c | o, ..., c |
| | c | | |
+-------------------+---------+------------+-----------------+
This scheme makes no requirements on the DIT structure within
an organization. However, the following naming architecture
is suggested:
NADF [Page 15]
RFC 1255 A Naming Scheme for c=US September 1991
+----------------+-----+----------------------+----------+-------------+
| Level |Elem | objectClass | Super | RDN |
+----------------+-----+----------------------+----------+-------------+
| listing | 11 | organization | 1,2,4 | |
+----------------+-----+----------------------+----------+-------------+
| organizational | 12 | organizationalUnit | 11,12,13 | orgUnitName |
| | 13 | locality | 11,12,13 | localityName|
| | 14 | organizationalRole | 11,12,13 | commonName |
| | 15 | organizationalPerson | 11,12,13 | commonName |
+----------------+-----+----------------------+----------+-------------+
| application | 16 | applicationProcess | 11,12,13 | commonName |
| | 17 | nadfApplicationEntity| 16 | commonName |
| | 18 | groupOfNames | 11,12,13 | commonName |
| | 19 | ediUser | 11,12,13 | ediName |
| | 20 | device | 11,12,13 | commonName |
+----------------+-----+----------------------+----------+-------------+
Or, in pictorial form:
(------------)
(organization)
(------------)
|
|<------------------------------+
| |
+--->(organizationalUnit)-------+
| |
+--->(locality)-----------------+
|
+--->(organizationalRole)
|
+--->(organizationalPerson)
|
+--->(applicationProcess)--->(nadfApplicationEntity)
|
+--->(groupOfNames)
|
+--->(ediUser)
|
+--->(device)
6.2. Persons
Listing organizational persons is a local matter to be decided by
each organization.
Residential persons are identified by the place where they reside,
NADF [Page 16]
RFC 1255 A Naming Scheme for c=US September 1991
usually with a multi-valued RDN consisting of a "commonName"
attribute value, and some other distinguished attribute value.
Although an obvious choice is to use something like "postalCode" or
"streetAddress", it should be noted that this information may be
considered private. Hence, some other, distinguishing attribute
value may be used -- possibly even a "serial number" attribute value
which has no other purpose other than to give uniqueness. (It should
be noted that an attribute of this kind is not helpful in regards to
searching -- other attribute values containing meaningful information
should be added to the entry and made available for public access, as
an aid to selection.)
The RDN used when listing residential persons depends on where the
listing is to be placed:
+----------------------------------------+
+-------------------| Listing (RDN) under |
| Entity | c=US | c=US, st=X | c=US, st=X, l=Y |
+-------------------+---------+------------+-----------------+
| residential | cn, ... | cn, ... | cn, ..., fips55 |
| person | st=X | fips55 | |
| | fips55 | | |
+-------------------+---------+------------+-----------------+
| .. (other region) | | cn, ... | cn, ..., st=Z |
| | | st=Z | fips55 |
| | | fips55 | |
+-------------------+---------+------------+-----------------+
Note that listing of foreign persons is for further study.
7. Usage Examples
In the examples which follow, the "*"-character is used to denote any
arbitrary value for an attribute type.
7.1. Organizations with National-Standing
Suppose that the organization
Lawrence Livermore National Laboratory
has national-standing by virtue of having been chartered by the US
Congress. According to the table in Section 6.1, this organization
has the right to list as any (or all) of these names:
(1) national-listing:
{ c=US,
NADF [Page 17]
RFC 1255 A Naming Scheme for c=US September 1991
o=Lawrence Livermore National Laboratory }
(2) regional-listing:
{ c=US, st=*,
{ o=Lawrence Livermore National Laboratory,
c=US } }
(3) local-listing:
{ c=US, st=*, l=*,
{ o=Lawrence Livermore National Laboratory,
c=US } }
Suppose that the organization
Performance Systems International, Inc.
has national-standing by virtue of having an alphanumeric nameform in
the ANSI registry. According to the table in Section 6.1, this
organization has the right to list as any (or all) of these names:
(1) national-listing:
{ c=US, o=Performance Systems International }
(2) regional-listing:
{ c=US, st=*,
{ o=Performance Systems International, c=US } }
(3) local-listing:
{ c=US, st=*, l=*,
{ o=Performance Systems International, c=US } }
7.2. Organizations with Regional-Standing
Suppose that the organization
Network Management Associates, Inc.
has regional-standing by virtue of having a DBA registration with the
Secretary of State for the State of California. According to the
table in Section 6.1, this organization has the right to list as any
NADF [Page 18]
RFC 1255 A Naming Scheme for c=US September 1991
(or all) of these names:
(1) national-listing:
{ c=US,
{ o=Network Management Associates,
st=California } }
(2) regional-listing:
{ c=US, st=California,
o=Network Management Associates }
(3) local-listing:
{ c=US, st=California, l=*,
o=Network Management Associates }
Further, in some state other than California, this
organization might also list as:
(1) regional-listing:
{ c=US, st=*,
{ o=Network Management Associates,
st=California } }
(2) local-listing:
{ c=US, st=*, l=*,
{ o=Network Management Associates,
st=California } }
7.3. Organizations with Local-Standing
Suppose that the tavern and eatery
⌨️ 快捷键说明
复制代码Ctrl + C
搜索代码Ctrl + F
全屏模式F11
增大字号Ctrl + =
减小字号Ctrl + -
显示快捷键?