Three revised Internet Drafts

[Steve Hardcastle-Kille <[e-mail]>]

Following the RARE WG3 meeting, I have revised three documents.  These
are available from the UCL archive, and are being submitted as
Internet Drafts.  These will be discussed in San Diego.  I hope that
the US views will not radically change the European work!

Let me summarise the changes:

1) Naming guidelines.   Some minor edits.  The direction for naming
was supported by the group (preference for the H-K/PB direction, as
opposed to the CH proposal).   It was felt that documenting and not
recommending the alternative approach caused confusion, and so this
text has been removed.   

The group requests one of the advocates of that alternative approach
to document it, and to subit the document as an OSI-DS working
document to be proposed as an RFC.


2) Distinguished Name Notation.   "," should be the mandatory
separator.   <> should be the prefered delimter for use in cases where
a delimiter is desired.   Schema defaulting should be dropped.  Where
a distinguished name notation is needed, the types should be explicit
and unambiguous.   The defaulting rules are too complex.   A set of
short keywords were agreed.  Thus the DN Notation now has names of the
form <CN=Paul-Andre Pays, O=Inria, C=FR>.   


3) User Friendly Naming.  A number of clarifications and changes in
light of 2).


Steve


OSI-DS 12
osi-ds-12-04.ps
osi-ds-12-04.txt
   P. Barker
   S.E. Kille
   Janurary 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 23
osi-ds-23-01.ps
osi-ds-23-01.txt
        A String Representation of Distinguished Names
	S.E. Hardcastle-Kille
        January 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.

****************

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: [e-mail]
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 <OSI-DS> (Note that the
     angle brackets and capital letters are vital)