A new Request for Comments is now available in online RFC libraries.


        RFC 1484:

        Title:      Using the OSI Directory to achieve User Friendly
                    Naming (OSI-DS 24 (v1.2)) 
        Author:     S. Hardcastle-Kille
        Mailbox:    S.Kille@ISODE.COM
        Pages:      25
        Characters: 48,974
        Updates/Obsoletes:  none


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 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 1485, and it is intended that these specifications are
compatible.

This memo defines an Experimental Protocol for the Internet community.
It does not specify an Internet standard.  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.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US.  Requests to be added
to or deleted from the RFC-DIST distribution list should be sent to
RFC-REQUEST@NIC.DDN.MIL.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to "rfc-info@ISI.EDU" with the message body 
"help: ways_to_get_rfcs".  For example:

	To: rfc-info@ISI.EDU
	Subject: getting rfcs

	help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to NIC.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1111, "Instructions to RFC
Authors", for further information.


Joyce K. Reynolds
USC/Information Sciences Institute