INDEX OF IETF OSI DS Documents (OSI-DS 0) January 1992 The following topics may be obtained from the info-server using a request in the form: request: osi-ds topic: For example: From: Joe.Soap@somedomain To: info-server@cs.ucl.ac.uk Subject: Anything you like request: osi-ds topic: scope.txt Files are available in Text, Postscript or both. FILENAME.txt for plain text format FILENAME.ps for postscript Note that not all the files are available in all the formats. All documents are numbered, in the form OSI-DS nnn or OSI-DS-MINUTES nnn The files are also available by FTP, NIFTP, and FTAM. FTP to CS.UCL.AC.UK, username anonymous and your own name as password cd osi-ds; FTAM to bells, computer science, university college london, gb username = anon, no password NIFTP to uk.ac.ucl.cs, binary mode, username = guest, password = (Your mail address in the form user@site) filenames should be prepended with (Note that the angle brackets and capital letters are vital) ------------------------------------------------------------------------ INDEX OSI-DS 0 index.txt This document ------------------------------------------------------------------------ SCOPE OF GROUP OSI-DS 1 osi-ds-1-04.ps osi-ds-1-04.txt IETF Directory Working Group Scope (Version 4) S.E. Kille December 22, 1990 Abstract: This document defines the scope for the IETF OSI Directory Ser- vices Working Group (OSI-DS). The OSI-DS group works on issues relating to building an OSI Di- rectory Service using X.500 and its deployment on the Internet. Whilst this group is not directly concerned with piloting, the focus is practical, and technical work needed as a pre-requisite to deployment of an open Directory will be considered. ------------------------------------------------------------------------ CHARTER OSI-DS 2 osi-ds-2-02.txt November 1990 Abstract: A synopsis of the scope in the IETF WG format ------------------------------------------------------------------------ MINUTES OF MEETINGS minutes-1-oct90.txt (OSI-DS-MINUTES 1) 1st Meeting, San Jose, Oct 90 minutes-2-dec90.txt, ps (OSI-DS-MINUTES 2) 2nd Meeting, Boulder, Dec 90 minutes-3-feb91.txt (OSI-DS-MINUTES 3) 3rd Meeting, SRI, Feb 91 minutes-4-apr91.txt, ps (OSI-DS-MINUTES 4) 4th Meeting, Videoconference, Apr 91 minutes-5-jul91.txt (OSI-DS-MINUTES 5) 5th Meeting, Atlanta IETF, Jul 91 minutes-6-oct91.txt (OSI-DS-MINUTES 6) 6th Meeting, San Jose Interop, Oct 91 minutes-7-mar92.txt (OSI-DS-MINUTES 7) 7th Meeting, San Diego IETF, Mar 92 ------------------------------------------------------------------------ MAIL ARCHIVES arch-current.txt - Mail Archive arch-1.txt - Mail archive up to Jan 92 ------------------------------------------------------------------------ RFCs RFC 1274: rfc1274.txt Title: The COSINE and Internet X.500 Schema Author: P. Barker & S. Kille Mailbox: P.Barker@cs.ucl.ac.uk, S.Kille@cs.ucl.ac.uk Pages: 60 Characters: 92,827 Updates/Obsoletes: none pathname: rfc/rfc1274.txt This document suggests an X.500 Directory Schema, or Naming Architecture, for use in the COSINE and Internet X.500 pilots. The schema is independent of any specific implementation. As well as indicating support for the standard object classes and attributes, a large number of generally useful object classes and attributes are also defined. An appendix to this document includes a machine processable version of the schema. This document also proposes a mechanism for allowing the schema to evolve in line with emerging requirements. Proformas to support this process are included. This RFC specifies a Proposed Standard Protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited. RFC 1275: rfc1275.ps rfc1275.txt Title: Replication Requirements to provide an Internet Directory using X.500 Author: S. Kille Mailbox: S.Kille@cs.ucl.ac.uk PS-Pages: 2 ASCII-Pages: 3 PS-Characters: 83,736 ASCII-Characters: 4,616 Updates/Obsoletes: none pathname: rfc/rfc1275.ps This RFC considers certain deficiencies of the 1988 X.500 standard, which need to be addressed before an effective open Internet Directory can be established using these protocols and services. The only areas considered are primary problems, to which solutions must be found before a pilot can be deployed. This RFC concerns itself with deficiencies which can only be addressed by use of additional protocol or procedures for distributed operation. This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. RFC 1276: rfc1276.ps rfc1276.txt Title: Replication and Distributed Operations extensions to provide an Internet Directory using X.500 Author: S. Kille Mailbox: S.Kille@cs.ucl.ac.uk PS-Pages: 17 ASCII-Pages: 17 PS-Characters: 217,170 ASCII-Characters: 33,731 Updates/Obsoletes: none pathname: rfc/rfc1276.ps Some requirements on extensions to X.500 are described in RFC 1275, in order to build an Internet Directory using X.500(1988). This document specifies a set of solutions to the problems raised. These solutions are based on some work done for the QUIPU implementation, and demonstrated to be effective in a number of directory pilots. By documenting a de facto standard, rapid progress can be made towards a full-scale pilot. These procedures are an INTERIM approach. There are known deficiencies, both in terms of manageability and scalability. Transition to standard approaches are planned when appropriate standards are available. This RFC will be obsoleted at this point. This RFC specifies a Proposed Standard Protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited. RFC 1277: rfc1277.ps rfc1277.txt Title: Encoding Network Addresses to support operation over non-OSI lower layers Author: S. Kille Mailbox: S.Kille@cs.ucl.ac.uk PS-Pages: 10 ASCII-Pages: 12 PS-Characters: 176,169 ASCII-Characters: 22,254 Updates/Obsoletes: none pathname: rfc/rfc1277.ps The OSI Directory specifies an encoding of Presentation Address, which utilises OSI Network Addresses as defined in the OSI Network Layer standards. The OSI Directory, and any OSI application utilising the OSI Directory must be able use these Network Addresses to identify end systems. Currently, OSI applications are often run over lower layers other than the OSI Network Service. It is neither reasonable nor desirable for groups wishing to investigate and use OSI Applications in conjunction with the OSI Directory to be dependent on a global OSI Network Service. This document defines a new network address format, and rules for using some existing network address formats. The scope of this document is: 1. Any TCP/IP network supporting COTS using RFC 1006. 2. Any mapping of COTS onto X.25 (usually X.25(80)), where X.25 is not used to provide CONS (i.e., only DTE and not Network address is carried). The approach could also be extended to use with other means of providing COTS (or CLTS). It is not appropriate for use where CONS or CLNS is used to provide COTS (or CLTS). This RFC specifies a Proposed Standard Protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited. RFC 1278: rfc1278.ps rfc1278.txt Title: A string encoding of Presentation Address Author: S. Kille Mailbox: S.Kille@cs.ucl.ac.uk PS-Pages: 5 ASCII-Pages: 7 PS-Characters: 128,696 ASCII-Characters: 10,256 Updates/Obsoletes: none pathname: rfc/rfc1278.ps There are a number of environments where a simple string encoding of Presentation Address is desirable. This specification defines such a representation. This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. RFC 1279: rfc1279.ps rfc1279.txt Title: X.500 and Domains Author: S. Kille Mailbox: S.Kille@cs.ucl.ac.uk PS-Pages: 13 ASCII-Pages: 15 PS-Characters: 170,029 ASCII-Characters: 26,669 Updates/Obsoletes: none pathname: rfc/rfc1279.ps This RFC considers X.500 in relation to Internet and UK Domains. A basic model of X.500 providing a higher level and more descriptive naming structure is emphasised. In addition, a mapping of domains onto X.500 is proposed, which gives a range of new management and user facilities over and above those currently available. This specification proposes an experimental new mechanism to access and manage domain information on the Internet and in the UK Academic Community. There is no current intention to provide an operational replacement for DNS. This memo defines an Experimental Protocol for the Internet community. Discussion and suggestions for improvement are requested. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited. ------------------------------------------------------------------------ IETF DRAFTS OSI-DS 3 (Historical) osi-ds-3.txt osi-ds-3.ps A proposed strategy for deploying an OSI Internet Directory S.E. Kille March 1991 Abstract: This document is a first cut at describing an overall strategy for deploying an OSI Directory on the Internet. This is a draft document, and does not carry any implications of agreement on policy. OSI-DS 4 (Historical) osi-ds-4.txt osi-ds-4.ps Overall plan of the IETF Working Group on OSI Directories (OSI-DS) to build an Internet Directory using X.500 S.E. Kille February 1991 Abstract: The IETF has established a Working Group on OSI Directory Services (IETF-OSI-DS). A major component of the initial work of this group is to establish a technical framework for establishing a Directory Service on the Internet, making use of the X.500 protocols and services [CCI88b]. This document summarises the plan established by the working group to achieve this, and describes a number of RFCs which the working group will write in order to establish the technical framework. This document has now been submitted as an RFC OSI-DS 5 (Replaced by RFC 1277) OSI-DS 6 (Replaced by RFC 1278) OSI-DS 7 (Replaced by RFC 1279) OSI-DS 8 (obsoleted by OSI-DS 23 and OSI-DS 24) osi-ds-8-02.ps osi-ds-8-02.txt Using the OSI Directory to achieve User Friendly Naming S.E. Kille March 1991 draft-ietf-osids-friendlynaming-02.txt, or .ps Abstract: The OSI Directory has user friendly naming as a goal. A simple minded usage of the directory does not achieve this. Two aspects not achieved are: o A user oriented notation o Guessability This proposal sets out some conventions for representing names in a friendly manner, and shows how this can be used to achieve really friendly naming. This then leads to a specification of a standard format for representing names, and to procedures to resolve them. OSI-DS 9 (Replaced by RFC 1275) OSI-DS 10 (Replaced by RFC 1274) OSI-DS 11 (Replaced by RFC 1276) OSI-DS 12 osi-ds-12-05.ps osi-ds-12-05.txt P. Barker S.E. Kille January 1992 Naming Guidelines for Directory Pilots draft-ietf-osids-dirpilots-03.ps Abstract: Deployment of a Directory will benefit from following certain guidelines. This document defines a number of naming guidelines. Alignment to these guidelines is recommended for directory pilots. OSI-DS 13 osi-ds-13-02.ps osi-ds-13-02.txt DSA Naming S.E. Kille January 1992 draft-ietf-osids-dsanaming-02.txt, or .ps Abstract: This INTERNET--DRAFT describes a few problems with DSA Naming as currently deployed in pilot exercises, and suggests a new approach. An approach is suggested for use in the Internet Directory Pilot, which overcomes a number of existing problems, and is an important component for the next stage in increase of scale. OSI-DS 14 osi-ds-14-00.txt Interim Schema for Internet Network Infrastructure Information In X.500 C. Weider M. Knopper draft-ietf-disi-netinfrax500-00.txt March 1991 Abstract: As the OSI Directory progresses into an operational structure which is being increasingly used as a primary resource for Directory Information, it was perceived that having the Internet Site Contacts and some limited network information in the Directory would be immediately useful and would also provide the preliminary framework for some distributed NIC functions. This paper describes the interim schema used to contain this information. OSI-DS 15 osi-ds-15-01.ps osi-ds-15-01.txt Handling QOS (Quality of service) in the Directory S.E. Kille August 1991 draft-ietf-osids-qos-01.txt,.ps Abstract: This document describes a mechanism for specifying the Quality of Service for DSA Operations and Data in the Internet Pilot Directory Service [Kil90]. OSI-DS 16 osi-ds-16-01.txt Schema for NIC Profile information in X.500 Chris Weider Mark Knopper March 1992 Abstract: The authors wish to put put up a readily accessible, distributed Directory of Network Information Centers, or NICs. This paper discusses the schema used to hold the NIC Profiles, as well as the DIT structure necessary for this information. OSI-DS 17 osi-ds-17-01.txt Schema for Information Resource Description in X.500 Chris Weider March 1992 Abstract: The authors are interested in allowing distributed access and updating for Information Resource Description information to users of the Internet. This paper discusses the schema used to hold the Information Resource Description information. The new attributes are taken from the US-MARC fields, and subfields, with the mapping described in the text. OSI-DS 18 (Document Inactive) osi-ds-18-00.ps osi-ds-18-00.txt Directory Requirements for COSINE and Internet Pilots Steve Hardcastle-Kille July 1991 draft-ietf-osids-requirements-00.txt, .ps Abstract: This document specifies operational requirements for DUAs and DSAs in the Internet and COSINE communities. This document summarises conformance requirements. In most cases, technical detail is handled by reference to other documents. This document refers to core directory infrastructure. Each application using the directory may impose additional requirements. OSI-DS 19 osi-ds-19-00.txt Interim Directory Tree Structure for Network Infrastructur Information Mark Knopper Ruth Lang April 1991 draft-ietf-disi-netinfrax500-00.txt Abstract: As work progresses on incorporating WHOIS and Network Infrastructure infor- mation into X.500, we thought it would be useful to document the current DIT structure for this information, along with some thoughts on future expansion and organization of this subtree of the DIT. The first section of this document describes the current structure, the second section the possible expansion of the structure. OSI-DS 20 osi-ds-20-01.txt X.500 Schema for a pilot Educator's Directory Service Mark Knopper Chris Weider March 1992 Abstract: From kindergarden to graduate school, educators are placing more and more emphasis on computers, computer techniques, and computer networks. As these concepts become more pervasive, the Internet is being seen as a valuable tool for students and educators who previously had neither the resources nor the time to become involved in computers. To enhance and support the resources currently available to and for educators on the Internet, Merit and Educom would like to implement a directory of educators and resources using the X.500 protocol. OSI-DS 21 osi-ds-21-00.ps osi-ds-21-00.txt An Access Control approach for Searching and Listing S.E. Hardcastle-Kille T. Howes draft-ietf-osids-accesscntrl-00.txt, .ps September 1991 Abstract: This memo defines an extended ACL (Access Control List) mechanism for the OSI Directory. It is intended to meet strong operational requirements to restrict searching and listing externally, while allowing much more freedom within an organization. In particular, this mechanism makes it possible to restrict searches to certain sets of attributes, and to prevent ``trawling'': the disclosure of large organizational data or structure information by repeated searches or lists. This capability is necessary for organizations that want to hide their internal structure, or to prevent dumping of their entire database. This memo describes functionality beyond, but compatible with, that expected in the 1992 X.500 standard. OSI-DS 22 osi-ds-22-00.txt Representing Public Archives in the Directory Wengyik Yeong November 1991 Abstract: The proliferation of publicly accessible archives in the Internet has created an ever-widening gap between the fact of the existence of such archives, and knowledge about the existence and contents of these archives in the user community. Related to this problem is the problem of also providing users with the necessary information on the mechanisms available to retrieve such archives. In order for the Internet user community to better avail themselves of this class of resources, there is a need for these gaps in knowledge to be bridged. Given the richness of its existing information framework, it is interesting to experiment with the use of the Directory as a solution to these information dissemination problems. This document specifies the schema necessary to provide the infrastructure for such experimental efforts. Note that it is the purpose of this schema to provide for the representation of publicly available archives of the most generic nature in the Directory. It is explicitly beyond the scope of this document to provide the necessary support for the representation of specialized archives with more than a minimum of structuring information. The representation of specialized archives such as document repositories or mail archives is left to other schema specifications which will emerge as the problems of information access are better understood. OSI-DS 23 osi-ds-23-03.ps osi-ds-23-03.txt A String Representation of Distinguished Names S.E. Hardcastle-Kille April 1992 Abstract: The OSI Directory uses distinguished names as the primary keys to entries in the directory. Distinguished Names are encoded in ASN.1. When a distinguished name is communicated between to users not using a directory protocol (e.g., in a mail message), there is a need to have a user-oriented string representation of distinguished name. OSI-DS 24 osi-ds-24-01.ps osi-ds-24-01.txt Using the OSI Directory to achieve User Friendly Naming S.E. Hardcastle-Kille January 1992 Abstract: The OSI Directory has user friendly naming as a goal. A simple minded usage of the directory does not achieve this. Two aspects not achieved are: o A user oriented notation o Guessability This proposal sets out some conventions for representing names in a friendly manner, and shows how this can be used to achieve really friendly naming. This then leads to a specification of a standard format for representing names, and to procedures to resolve them. This leads to a specification which allows directory names to be communicated between humans. The format in this specification is identical to that defined in [HK92], and it is intended that these specifications are compatible. OSI-DS 25 osi-ds-25-00.ps osi-ds-25-00.txt Representing the Real World in the OSI Directory S.E. Hardcastle-Kille February 1992 Abstract: This document discusses a set of related issues, concerning the evolution of the OSI Directory. They are all broadly concerned with the problem that the simple-minded hierarchical model of countries, organisations, and people is insufficient for many real world problems. The na"ive might immediately react by suggesting that X.500 is deficient. This document shows how X.500 can be used in a more sophisticated manner, in order to broaden its scope of application. The issues considered include: o Dealing with real organisational structures, and multiple views onto such structures. o Dealing with groupings which run counter to the simple directory hierarchy, such as committees and and special interest groups. o Showing how the directory can be used to provide listing services, and describing the conflict between registration and listing. A model is proposed which is scalable, and gives a basis for multi-provider provision of a large scale directory. o The relationship between documents and the directory, and advocating the need for universal document registration. OSI-DS 26 osi-ds-26-2.txt Lightweight Directory Access Protocol W. Yeong T. Howes S.E. Hardcastle-Kille August 1992 Abstract: The tremendous interest in X.500 [1,2] technology in the Internet has lead to efforts to reduce the high ``cost of entry'' associated with use of the technology, such as the Directory Assistance Service [3] and DIXIE [4]. While efforts such as these have met with success, they have been solutions based on particular implementations and as such have lim- ited applicability. This document continues the efforts to define Directory protocol alternatives but departs from previous efforts in that it consciously avoids dependence on particular implementations. The protocol described in this document is the first of a series of pro- tocols designed to provide access to the Directory while not incurring the resource requirements of the Directory Access Protocol (DAP). This protocol is specifically targeted at simple management applications and browser applications that provide simple read/write interactive access to the Directory, and is intended to be a complement to the DAP itself. OSI-DS 27 osi-ds-27-02.txt The String Representation of Standard Attribute Syntaxes T. Howes S.E. Hardcastle-Kille W. Yeong C. Robbins August 1992 Abstract: The lightweight directory protocols require that the contents of Attri- buteValue fields in protocol elements be octet strings. This document defines the requirements that must be satisfied by encoding rules used to render Directory attribute syntaxes into a form suitable for use in the lightweight directory protocols, then goes on to define the encoding rules for the standard set of attribute syntaxes defined in [1,2] and [3]. OSI-DS-28 osi-ds-28-00.txt T. Berners-Lee February 1992 What W3 needs from WAIS and x.500 (OSI-DS 28) Abstract: There has been much discussion about the relative roles of the WAIS protocol and the x.500 distributed naming scheme in the information universe. This paper notes a few requirements on such protocols for a global hypertext/index documentation system. OSI-DS-29 osi-ds-29-00.txt T. Berners-Lee J.F. Groff R. Cailliau February 1992 Universal Document Identifiers on the Network Abstract: Many protocols and systems for document search and retrieval are currently in use, and many more protocols or refinements of existing protocols are to be expected in a field whose expansion is explosive. These systems are aiming to achieve global search and readership of documents across differing computing platforms, and despite a plethora of protocols and data formats. As protocols evolve, gateways can allow global access to remain possible. As data formats evolve, format conversion programs can preserve global access. There is one area, however, in which it is impractical to make conversions, and that is in the names used to identify documents. This is because names of documents are passed on in so many ways, from the backs of envelopes to hypertext documents, and may have a long life. This paper discusses the requirements on a universal naming syntax which can be used to refer to documents available using existing protocols, and may be extended with technology. It makes a recommendation for a generic syntax, and its specific application to existing internet protocols. OSI-DS 30 osi-ds-30-00.ps osi-ds-30-00.txt Counting the Directory Information Tree S.E. Hardcastle-Kille February 1992 Abstract: Pilot Directory Services are growing rapidly. It is useful to know how much information is available in the directory. This is important for management purposes, both to understand the level of growth, and to provide publicity as to what is there. Current counting techniques are both ad hoc and implementation specific. A more general technique is proposed here. It is likely that such estimates will always be on the low side, for example because an organisation is not prepared to indicate the number of entries is has. However, it is useful to be able to estimate the size of the Directory Information Tree. This specification defines a means for doing this. OSI-DS 31 osi-ds-31-00.ps osi-ds-31-00.txt The Simple OSI Stack S.E. Hardcastle-Kille March 992 Abstract: This document specifies a mapping of protocols defined by the Abstract Service Description Conventions onto Connection Oriented Transport Service, Connectionless Transport Service, TCP, and UDP [MHS88b]. This mapping will support all ROS (Remote Operation Service) based protocols, such as directory, both with and without use of RTS (Reliable Transfer Service), and all of the X.400 services [ISO88, CCI88, MHS88a]. Four example applications of the Simple OSI Stack (SOS) are given in appendices. These are all ``real'' examples, which will are quite likely to evolve into formal specifications. They are intended to show that specification of SOS applications is very straightforward and useful. These examples will be dropped from future versions of this document, and perhaps be replaced by artificial examples. OSI-DS 32 osi-ds-32-00.txt Supporting national characters in the Internet and COSINE X.500 Directory G. Pedersen March 1992 We are in the process of building a global X.500 based directory. In many countries it is seen as essential for the success of the dir- ectory that it is able to recognise, store and present textual info- rmation, like personal and organisational names, represented in the character sets used by those concerned. This means the directory must be able to handle national characters not found in the English alpha- bet. As we are still in an early phase in establishing the directory as a widly available network service, now is a good time to tackle the issues related to supporting usage of national characters in the directory. This document discusses the requirements with respect to support for national characters from the directory as well as ways to meet the identified requirements. Finaly a recommendation on how to support national characters in the Internet and COSINE X.500 Directory is given. OSI-DS 33 osi-ds-33-01.ps osi-ds-33-01.txt DUA Metrics P. Barker June 1992 This is a part of a PARADISE Deliverable. The note defines a set of criteria by which a DUA implementation, or more precisely a Directory user interface, may be judged. Particular issues covered include terminal requirements; style of interface; target user; default object classes and attribute types; use of DAP; error handling. The intention is that the replies to the questions posed describe the DUA / user interface fairly fully. Some of the questions will yield answers which are purely descriptive; others, however, are intended to yield answers which give some measure of the utility of the DUA. The marks awarded for a DUA in each particular area should give a good indication of the DUA's capabilities, and its suitability for various tasks. It should be noted that the focus of this document is very much on ``white pages'' DUAs. this is a reflection of the current information base. Nevertheless much of the document will be applicable to DUAs developed for other types of Directory usage. OSI-DS 34 osi-ds-34-01.ps osi-ds-34-01.txt DSA Metrics P. Barker S.E. Hardcastle-Kille June 1992 This is a part of a PARADISE Deliverable. The note defines a set of criteria by which a DSA implementation may be judged. Particular issues covered include conformance to standards; performance; demonstrated interoperability. The intention is that the replies to the questions posed describe the DSA fairly fully. Some of the questions will yield answers which are purely descriptive; others, however, are intended to yield answers which give some measure of the utility of the DSA. The marks awarded for a DSA in each particular area should give a good indication of the DSA's capabilities, and its suitability for particular uses. OSI-DS 35 osi-ds-35-00.txt AN X.500 SCHEMA FOR HOTELS AND RESTAURANTS A. Zahm October 1992 Abstract: This document suggests an X.500 Directory Schema, or Naming Architecture, for the purpose of storing useful information about hotels and restaurants in the COSINE and Internet X.500 pilots. The schema is independent of any specific implementation. As well as indicating support for the standard object classes and attributes, some useful object classes and attributes are also defined. Corrections and additions to the schema should be sent to zahm@e3x.fr ------------------------------------------------------------------------