RFC 1417
NADF Standing Documents: A Brief Overview
RFC 1417: NADF Standing Documents: A Brief Overview 💖🦋
Network Working Group 🌸 Written by: The North American Directory Forum (NADF), c/o Theodore H. Myer 🧚 Date: February 1993 📅 Obsoletes: RFCs 1295, 1255, and 1218 💅 Category: This memo provides information for the Internet community. It does not specify an Internet standard. ✨
Status of this Memo ✨
This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. 🌈
Table of Contents 🎀
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 ........................................ 41. Introduction ✨
Okay so, the North American Directory Forum (NADF) is a group of service providers that plans to cooperatively offer a Public Directory Service in North America, built on the CCITT X.500 Recommendations. 🌸 Lots of groups are working on realizing X.500, but the NADF is seriously unique because it has to pull off a cooperative service even though every provider is competing with the others. Main character energy 👑
This doc gives you a quick overview of the NADF's Standing Document series. As of writing, the standing documents are:
No Title
---- ------------------------------------------------
SD-0 NADF Standing Documents: A Brief Overview
SD-1 Terms of Reference
SD-2 Program Plan
SD-3 Service Description
SD-4 The Directory Schema
SD-5 An X.500 Naming Scheme for National DIT Subtrees
and Its Application for c=CA and c=US
SD-6 Guidelines on Naming and Subtrees
SD-7 Mapping the North American DIT
onto Directory Management Domains
SD-8 The Experimental Pilot Plan
SD-9 Charter, Procedures and Operations of the
Central Administration for NADF
SD-10 Security & Privacy: Policy & Services
SD-11 Directory Security: Mechanisms and Practicality
SD-12 Registry of ADDMD NamesSD-1 defines the scope of the NADF 🎯, and SD-2 describes issues of interest to the NADF.
The rest of the docs cover the agreements needed to get a cooperative Public Directory Service running across competing providers. Just so you know, the NADF leans on X.500(88) as much as it possibly can 🫶
SD-3 holds the agreements about the Directory "service", like quality of service, and SD-4 holds the agreements about the Directory schema. 📋
SD-5 is all about how a national authority should structure its DIT subtree. It then applies those principles to the naming scheme for the c=CA and c=US parts of the DIT. 🇺🇸🇨🇦 The NADF splits a national DIT subtree into two portions. First there's the public name-space, which holds information objects with some kind of public recognition (states, counties, businesses, and so on). Second, there are several private name-spaces, each one unilaterally managed by a public provider of Directory services. (SD-12 is the registry of those providers.) Based on an entity's civil standing, it can choose to list one or more entries in the public name-space. Registration, per se, happens outside of the Directory, which is a huge deal because it lets an entity show up where people are actually likely to search 🔍
SD-6 gives guidelines on how organizations might organize their private name-space, and it also talks about how multinationals might choose to list themselves. 🌍
SD-7 covers how the DIT is mapped onto multiple DMDs. X.500(88) doesn't have knowledge maintenance procedures, and products that support X.500(92) are years away 😭 Also, the competitive relationships between North American Directory providers rule out any chance of one entity having exclusive management rights to the public name-space. So the NADF goes with cooperative management: each service provider gets to link from the public name-space into its own private name-space. That linkage is limited to knowledge references and naming links, with very little (if any) payload 🎀 SD-9 explains how a central authority (called the CAN) coordinates and spreads this information. Basically, the CAN publishes a roadmap for North American Public Directory Service 🗺️
SD-8 describes the agreements reached for the NADF Pilot. 🧪
SD-10 lays out the NADF's policy on security and privacy. Attachment 1 of SD-10 has the "User Bill of Rights for entries and listings in the Public Directory". 💜 SD-11, on the other hand, describes the security facilities available in the Directory, then specifies which mechanisms will be used in the Public Directory service 🔐
1.1. Document Availability 📚
Right now, the NADF standing documents only exist in hardcopy and PostScript form. Since they aren't in ASCII form, they can not be distributed as informational RFCs. Here are the ways you can get them 💖
1.1.1. Hardcopy 📮
Postal: NADF Secretariat
c/o Rapport Communication
3055 Q Street NW
Washington, DC 20007
US
Tel: +1 202 342 2727
Fax: +1 202 625 4101
E-Mail: Ted Myer <4454742@mcimail.com>1.1.2. Anonymous FTP 💻
host: ftp.ics.uci.edu
area: mrose/nadf/
files: sd-*.ps
mode: ascii1.1.3. Electronic Mail 📧
addr: archive-server@ftp.ics.uci.edu
body: mimesend mrose/nadf/sd-NN.ps
(where "NN" is the desired SD)Security Considerations 🔐
Okay, real talk: security issues are not discussed in this memo. 😭 Bestie, go check SD-10 and SD-11 if you want the good stuff.
Author's Address 🖊️
North American Directory Forum
c/o Theodore H. Myer
Rapport Communication
3055 Q Street NW
Washington, DC 20007
Phone: +1 202-342-2727
EMail: 0004454742@mcimail.com📦 where this page comes from
- ietf: rfc1417 1993-02
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms