Steve Kille <S.Kille@cs.ucl.ac.uk> (02/20/91)
Archive-name: internet/osi/osi-ds/0--
Archive: cs.ucl.ac.uk:/osi-ds [128.16.5.31]
Original-posting-by: Steve Kille <S.Kille@cs.ucl.ac.uk>
Original-subject: IETF OSI DS working group documents
Reposted-by: emv@ox.com (Edward Vielmetti)
[Edited for comp.archives. --Ed.]
...The OSI-DS group is an open group. We have a mailing list, which covers
both the Internet IETF WG and the Directory Subgroup of RARE WG3 (European).
All members of DSSIG are invited to join this list. Send to
<osi-ds-request@cs.ucl.ac.uk> to be added.
There is an archive of documents which can be accessed by a variety of means.
I append the latest index....
regards
Steve
INDEX OF IETF OSI DS Documents
The following topics may be obtained from the info-server
using a request in the form:
request: osi-ds
topic: <one of topics the below>
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.
The files are also available by FTPm 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 00000511160013, 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 <OSI-DS> (Note that the
angle brackets and capital letters are vital)
------------------------------------------------------------------------
INDEX
index.txt This document
------------------------------------------------------------------------
SCOPE OF GROUP
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
charter.txt
November 1990
Abstract:
A synopsis of the scope in the IETF WG format
------------------------------------------------------------------------
MINUTES OF MEETINGS
minutes-1-oct90.txt
1st Meeting, San Jose, Oct 90
------------------------------------------------------------------------
MAIL ARCHIVES
arch-current.txt - Mail Archive
------------------------------------------------------------------------
IETF DRAFTS
strategy.txt
strategy.ps Building and Internet Directory using X.500
S.E. Kille
December 1990
draft-ietf-osix500-directories-01.txt
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 strategy established by the working group, and
describes a number of RFCs which will be written in order to establish the
technical framework.
nsap.ps
nsap.txt
"An Interim Approach to use of Network Addresses"
S.E. Kille
draft-ucl-kille-networkaddresses-02.txt, .ps
January 1991
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 to deal
with these Network Addresses. Currently, most environments cannot
cope with them. It is not reasonable or desirable for groups
wishing to investigate and use OSI Applications in conjunction
with the OSI Directory to have to wait for the lower layers to sort
out. This note is a proposal for mechanisms to utilise Network
Addresses.
string.ps
string.txt
A String encoding of Presentation Address
draft-ucl-kille-presentationaddress-02.txt, ps
S.E. Kille
November 1990
Abstract:
There are a number of environments where a simple string encoding
of Presentation Address is desirable. This specification defines
such a representation.
domain.ps
domain.txt
Domains and X.500
S.E. Kille
Novmember 1990
Abstract:
This INTERNET-DRAFT considers X.500 in relation to Internet/UK Do-
mains. 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.
ufn.ps
ufn.txt
Using the OSI Directory to achieve User Friendly Naming
S.E. Kille
January 1991
draft-ietf-osids-friendlynaming-01.txt, .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.
repl-req.ps
repl-req.txt
Replication Requirement to provide an Internet Directory using X.500
S.E. Kille
January 1991
draft-ietf-osids-replication-01.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.
na.txt
P. Barker
S.E. Kille
January 1991
draft-ietf-osids-cosinex500-02.txt
The COSINE and Internet X.500 Naming Architecture
Abstract:
This document suggests an X.500 Directory Naming
Architecture, or Schema, for use in the COSINE and Internet
X.500 pilots. The architecture 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
processible version of the architecture.
This document also proposes a mechanism for allowing the
naming architecture 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
naming architecture should now be sent the list, as
described within.
This draft document will be submitted to the RFC editor as a
protocol specification. Distribution of this memo is
unlimited. Please send comments to the authors or to the
discussion group <osi-ds@cs.ucl.ac.uk>.
repl-sol.txt
repl-sol.ps
Replication to provide an Internet Directory using X.500
S.E. Kille
January 1991
draft-ietf-osids-friendlynaming-01.txt, .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.
------------------------------------------------------------------------