INDEX OF IETF OSI DS Documents (OSI-DS 0) August 1991 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; Note that listing of the directory is not supported by the UCL FTP 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 scope.ps scope.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 charter.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 ------------------------------------------------------------------------ MAIL ARCHIVES arch-current.txt - Mail Archive ------------------------------------------------------------------------ IETF DRAFTS OSI-DS 3 strategy.txt strategy.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 goals.txt goals.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 nsap.ps nsap.txt "An Interim Approach to use of Network Addresses" S.E. Kille September 1991 draft-ucl-kille-networkaddresses-05.txt, or .ps Abstract: The OSI Directory specifies an encoding of Presentation Address, which utilises OSI Network Addresses as defined in the OSI Network Layer standards [CCI88] [ISO87a]. 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 INTERNET--DRAFT defines mechanisms to encode addressing information within Network Addresses, in order to support operation over non-OSI lower layers. In particular, support is defined for RFC 1006 mapping of COTS onto TCP/IP and COTS mapped onto X.25(1980). OSI-DS 6 string.ps string.txt A String encoding of Presentation Address draft-ucl-kille-presentationaddress-03.txt, ps S.E. Kille July 1991 Abstract: There are a number of environments where a simple string encoding of Presentation Address is desirable. This specification defines such a representation. OSI-DS 7 domain.ps domain.txt Domains and X.500 S.E. Kille March 1991 Filename : draft-ucl-kille-x500domains-03.txt, or .ps Abstract: This INTERNET--DRAFT 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. OSI-DS 8 ufn.ps ufn.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 repl-req.ps repl-req.txt Replication Requirement to provide an Internet Directory using X.500 S.E. Kille August 1991 draft-ietf-osids-replication-03.txt, .ps Abstract: A companion document discussed an overall framework for deploying X.500 on the Internet [Kil90 ]. This document considers certain deficiencies of the 1988 standard, which need to be addressed before an effective open Internet Directory can be established [CCI88 ]. The only areas considered are primary problems, to which solutions must be found before a pilot can be deployed. This INTERNET--DRAFT concerns itself with deficiencies which can only be addressed by use of additional protocol or procedures for distributed operation. OSI-DS 10 na.txt P. Barker S.E. Kille March 1991 The COSINE and Internet X.500 Schema draft-ietf-osids-cosinex500-05.txt Abstract: 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 commonly held requirements. Proformas to support this process are included. It is important to note that this version of the document is a draft, and comments on the updating mechanisms are particularly welcome. Corrections and additions to the schema should now be sent the list, as described within. OSI-DS 11 repl-sol.ps Replication and Distributed Operations extensions to provide an Internet Directory using X.500 S.E. Kille August 1991 draft-ietf-osids-replsoln-03.txt, or .ps Abstract: Some requirements on extensions to X.500 are described in the INTERNET--DRAFT [Kil90b ], in order to build an Internet Directory as described in the INTERNET--DRAFT [Kil90a ]. 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 INTERNET--DRAFT will be obsoleted at this point. OSI-DS 12 structure.ps structure.txt P. Barker S.E. Kille September 1991 Naming Guidelines for Directory Pilots draft-ietf-osids-dirpilots-02.ps Abstract: Deployment of a Directory will benefit from following certain guidelines. This document defines a number of guidelines which are recommended. Conformance to these guidelines will be recommended for national pilots. OSI-DS 13 dsanaming.ps dsanaming.txt DSA Naming S.E. Kille September 1991 draft-ietf-osids-dsanaming-01.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. This approach is suggested for use in the Internet Directory Pilot. I believe this note to be an important step forward, as it begins to evolve a clear model of a Directory Management Domain. OSI-DS 14 contacts.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 qos.ps qos.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 nic-profile.txt Schema for NIC Profile information in X.500 Chris Weider Mark Knopper June 1991 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 resource-schema.txt Schema for Information Resource Description in X.500 Chris Weider May 1991 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 requirements.ps requirements.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 treestructure.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 educator-schema.txt X.500 Schema for a pilot Educator's Directory Service Mark Knopper Chris Weider July 1991 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 newacl.ps newacl.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. ------------------------------------------------------------------------