This Working Group Did Not Meet
NOTE: This charter is a snapshot of the 40th IETF Meeting in Washington, DC. It may now be out-of-date. Last Modified: 05-Aug-97
Chair(s):
Tim Howes <howes@netscape.com>
Patrik Faltstrom <paf@swip.net>
Applications Area Director(s):
Keith Moore <moore@cs.utk.edu>
Harald Alvestrand <Harald.T.Alvestrand@uninett.no>
Applications Area Advisor:
Harald Alvestrand <Harald.T.Alvestrand@uninett.no>
Mailing Lists:
General Discussion:ietf-asid@umich.edu
To Subscribe: ietf-asid-request@umich.edu
Archive: ftp://terminator.rs.itd.umich.edu/ietf-asid/archive
Description of Working Group:
There is a clear need to provide and deploy a well managed Directory Service for the Internet. A so-called White Pages Directory Service providing people and organizational information is especially long overdue. While the ultimate goal is a general Directory Service for the Internet, this is too ambitious a goal to be tackled by a single working group. Therefore ASID will keep a tight focus on access and synchronization protocols for an Internet White Pages Directory Service.
Other related working groups will be formed in the Applications Area that will deal with other aspects of the Internet Directory Service.
Currently there are various protocols under development in the Internet that aim to provide such a service: Internet X.500, WHOIS++, NETFIND, CSO, RWHOIS, etc. To allow these services to evolve to a ubiquitous Internet Directory Service, a hybrid system that allows interaction between the various different services is a requirement.
The ASID Working Group will define, evolve, and standardize protocols, algorithms and access methods for a White Pages Directory Service on the Internet.
The following protocols (some still under development, some completed by other IETF working groups) will be considered by the working group:
- Lightweight Directory Acces Protocols (LDAP and Connectionless LDAP)
- User Friendly Naming (UFN) and User Friendly Searching (UFS)
- The SOLO directory access and searching system
- The WHOIS++ directory service
The following work items are handled by other groups, and as such are outside the scope of this group. However their results are important to the development of a White Pages Directory Service, and will be taken into account:
- The Hypertext Transfer Protocol (HTTP)
- The UR* definitions
- The NETFIND directory service
The group will focus on harmonizing, evolving and developing protocols and algorithms that deal with access to and synchronization of Directory Service, both ad hoc and standards-based, with a goal of converging here possible towards a hybrid system that ties together various forms of Directory Service. Clearly, protocol-level integration is only part of the solution. But to keep this group tightly focused, harmonizing directory information and service models will be tackled by other working groups.
Goals and Milestones:
Jul 94 |
|
SOLO revised Internet-Draft published. |
Jul 94 |
|
CLDAP Internet-Draft submitted as Proposed Standard. |
Done |
|
X.500 URL Internet-Draft published. |
Sep 94 |
|
SOLO URL Internet-Draft published. |
Sep 94 |
|
Stand-alone LDAP Internet-Draft published (LDAP without X.500). |
Sep 94 |
|
SOLO Internet-Draft submitted as Proposed Standard. |
Done |
|
LDAP URL Internet-Draft published. |
Nov 94 |
|
Revised versions of all Internet-Drafts. |
Jan 95 |
|
Submit all Internet-Drafts as Proposed Standards. |
Internet-Drafts:
· A MIME Content-Type for Directory Information
· A Simple Caching Scheme for LDAP and X.500 Directories
· WHOIS++ URL Specification
· Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions
· Lightweight Directory Access Protocol (v3)
· vCard MIME Directory Profile
· Lightweight Directory Access Protocol (v3): Extensions for Dynamic Directory Services
· Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished Names
· Using Domains in LDAP/X.500 Distinguished Names
· Use of Language Codes in LDAPv3
· WHOIS++ templates
· Definition of the inetOrgPerson Object Class
· The LDAP Data Interchange Format (LDIF) - Technical Specification
· Architecture of the WHOIS++ service
· Definition of an Object Class to Hold LDAP Change Records
· LDAP Control Extension for Simple Paged Results Manipulation
· Lightweight Directory Access Protocol: Schema for Storing RPC Entries in a Directory Service
· LDAP Multi-Master Replication Protocol
· The LDAP URL Format
· The String Representation of LDAP Search Filters
· LDAP-based Routing of SMTP Messages: Approach Used by Netscape
· LDAP-based Routing of SMTP Messages: Approach at Stanford University
· X.500 Strong Authentication Mechanisms for LDAPv3
· A Summary of the Pilot X.500 Schema for use in LDAPv3
· A Summary of the X.500(96) User Schema for use with LDAPv3
· LDAP Control Extension for Server Side Sorting of Search Results
· Referrals and Knowledge References in LDAP Directories
· Lightweight Directory Access Protocol (v3): Extension for Transport Layer Security
· Lightweight Directory Access Protocol: Dynamic Attributes
· The vCard Schema For Use In LDAPv3
· LDAP Replication Requirements
· The Java LDAP Application Program Interface
· Schema for Replication Information
· LDAP API Extensions for Sort and Simple Paged Results
· Referral Whois Protocol (RWhois) 2.0
· The C LDAP Application Program Interface
· Java LDAP Controls
Request For Comments:
RFC |
Status |
Title |
RFC1781 |
PS |
Using the OSI Directory to Achieve User Friendly Naming |
RFC1777 |
DS |
Lightweight Directory Access Protocol |
RFC1778 |
DS |
The String Representation of Standard Attribute Syntaxes |
RFC1779 |
DS |
A String Representation of Distinguished Names |
RFC1804 |
E |
Schema Publishing in X.500 Directory |
RFC1959 |
PS |
An LDAP URL Format |
RFC1960 |
PS |
A String Representation of LDAP Search Filters |
RFC2079 |
PS |
Definition of X.500 Attribute Types and an Object Class to Hold Uniform Resource Identifiers (URIs) |