As per Relevance of the word security, we have this rfc below:
Network Working Group The North American Directory
Request for Comments: 1417 February 1993
Obsoletes: 1295, 1255, 1218
NADF Standing Documents
A Brief
Status of this
This memo provides information for the Internet community. It
not specify an Internet standard. Distribution of this memo
unlimited
Table of
1. Introduction ......................................... 1
1.1 Document Availability ............................... 3
1.1.1 Hardcopy .......................................... 3
1.1.2 Anonymous FTP ..................................... 4
1.1.3 Electronic Mail ................................... 4
Security Considerations ................................. 4
Author's Address ........................................ 4
1.
The North American Directory Forum (NADF) is a collection of
providers which plans to cooperatively offer a Public
Service in North America using the CCITT X.500 Recommendations
Although many groups are working on realizing X.500, the NADF
unique in that it must achieve a cooperative service offered
competing providers
The purpose of this document is to provide a brief overview of
NADF's Standing Document series. As of this writing, the
documents are
NADF [Page 1]
RFC 1417 NADF Standing Documents February 1993
No
---- ------------------------------------------------
SD-0 NADF Standing Documents: A Brief
SD-1 Terms of
SD-2 Program
SD-3 Service
SD-4 The Directory
SD-5 An X.500 Naming Scheme for National DIT
and Its Application for c=CA and c=
SD-6 Guidelines on Naming and
SD-7 Mapping the North American
onto Directory Management
SD-8 The Experimental Pilot
SD-9 Charter, Procedures and Operations of
Central Administration for
SD-10 Security & Privacy: Policy &
SD-11 Directory Security: Mechanisms and
SD-12 Registry of ADDMD
SD-1 defines the scope of the NADF, whilst SD-2 describes issue
interest to the NADF
The remaining documents describe the agreements necessary to
a cooperative Public Directory Service offered by
providers. In this context, it should be observed that the
relies on X.500(88) to the largest extent possible
SD-3 contains agreements concerning the Directory "service", e.g.,
quality of service, whilst SD-4 contains agreements concerning
Directory schema
SD-5 concerns itself with how a national authority should
its DIT subtree, and then applies these principles to define
naming scheme for the c=CA and c=US parts of the DIT. The NADF'
approach is to divide a national DIT subtree into two portions:
public name-space, which corresponds to information objects
some sort of public recognition (e.g., states, counties, businesses
etc.), and several private name-spaces, each unilaterally managed
a public provider of Directory services. (SD-12 defines the
of these providers.) Based on the civil standing of an entity,
entity may opt to list as one or more entries in the public name
space. That is, registration, per se, occurs outside of
Directory. This is an important concept as it allows an entity
list where others are likely to search
SD-6 provides guidelines as to how organizations might wish
organize their private name-space, and also discusses how multi
nationals might choose to list themselves
NADF [Page 2]
RFC 1417 NADF Standing Documents February 1993
SD-7 contains agreements concerning how the DIT is mapped
multiple DMDs. Knowledge maintenance procedures are absent
X.500(88), and products which support X.500(92) are years away
Further, the competitive relationships between the North
Directory providers invalidate any possibility of a single
having exclusive management rights to the public name-space.
NADF approach is to cooperatively manage the public name-space
allowing each service provider to provide linkage from the
name-space into their own private name-space. This information
limited to knowledge references and naming links; there is little,
any, payload present. SD-9 discusses how a central authority (
the CAN) coordinates and disseminates this information. In effect
the CAN publishes a roadmap for North American Public
Service
SD-8 describes agreements reached for the NADF Pilot
SD-10 describes the NADF policy toward security and privacy
Attachment 1 of SD-10 contains the "User Bill of Rights for
and listings in the Public Directory". In contrast, SD-11
the security facilities available in the Directory, and
specifies which mechanisms which will be used in the Public
service
1.1. Document
At the present time, the NADF standing documents are available
in hardcopy and PostScript form. Since they do not exist in
form, the NADF standing documents can not be distributed
informational RFCs. Following are the various
mechanisms available
1.1.1.
Postal: NADF
c/o Rapport
3055 Q Street
Washington, DC 20007
Tel: +1 202 342 2727
Fax: +1 202 625 4101
E-Mail: Ted Myer <4454742@mcimail.com
NADF [Page 3]
RFC 1417 NADF Standing Documents February 1993
1.1.2. Anonymous
host: ftp.ics.uci.
area: mrose/nadf
files: sd-*.
mode:
1.1.3. Electronic
addr: archive-server@ftp.ics.uci.
body: mimesend mrose/nadf/sd-NN.
(where "NN" is the desired SD
Security
Security issues are not discussed in this memo
Author's
North American Directory
c/o Theodore H.
Rapport
3055 Q Street
Washington, DC 20007
Phone: +1 202-342-2727
EMail: 0004454742@mcimail.
NADF [Page 4]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
