OID Document from Arles

Skip Slone <jpslone@tag.den.mmc.com> Mon, 20 July 1992 14:47 UTC

Received: from ietf.nri.reston.va.us by IETF.NRI.Reston.VA.US id aa13906; 20 Jul 92 10:47 EDT
Received: from NRI.NRI.Reston.Va.US by IETF.NRI.Reston.VA.US id aa13896; 20 Jul 92 10:47 EDT
Received: from haig.cs.ucl.ac.uk by NRI.Reston.VA.US id aa04500; 20 Jul 92 10:50 EDT
Received: from bells.cs.ucl.ac.uk by haig.cs.ucl.ac.uk with local SMTP id <g.02886-0@haig.cs.ucl.ac.uk>; Mon, 20 Jul 1992 15:40:30 +0100
Received: from everest.den.mmc.com by bells.cs.ucl.ac.uk with Internet SMTP id <g.22537-0@bells.cs.ucl.ac.uk>; Mon, 20 Jul 1992 15:40:20 +0100
Received: from tag (tag.den.mmc.com) by everest.den.mmc.com (4.1/1.34.a) id AA27677; Mon, 20 Jul 92 08:39:43 MDT
Received: by tag (4.1/1.34.a) id AA12117; Mon, 20 Jul 92 08:41:23 MDT
Date: Mon, 20 Jul 92 08:41:23 MDT
From: Skip Slone <jpslone@tag.den.mmc.com>
Message-Id: <9207201441.AA12117@tag>
To: Sylvain.Langlois@der.edf.fr
Subject: OID Document from Arles
Cc: c.robbins@xtel.co.uk, osi-ds@cs.ucl.ac.uk, tim@terminator.cc.umich.edu

I don't think the "reply all" function worked properly the first time.  I
apologize for any duplicates of this message...

---------------------------------------------------

> From Sylvain.Langlois@der.edf.fr Mon Jul 20 02:51:00 1992
> Date: Mon, 20 Jul  02:49:13 1992
> 
> > Your comments were brought up at the osi-ds meeting on Monday, and
> > there was general agreement that a second paper is needed to address
> > the "oid hierarchy in the dit" issue.  I agreed to make a first pass
> > at this.
> As soon as I came back from Boston, I've been looking for the document
> I was talking  about concerning the  OID  tree. It's  coming from  OSI
> SC21/WG6 meeting in Arles (France) , May 91. I'll  go into it and will
> post comments on it (if any valuable) in the middle of the week.
> 
> Sylvain
> ----------------
> Sylvain.Langlois@der.edf.fr
> 

Sylvain,

The number for that document is JTC1/SC21N 6063, and
the title is "Use of Object Identifiers to Access Directory Information."

Its purpose to enable the use of OIDs as a sort of "short form name,"
rather than find out information about the OID itself.  Perhaps it could
be used that way in some indirect fashion, though.

I don't have a soft copy of the document, but I could fax it if you can't
find your copy locally.

-- Skip Slone  (jpslone@mmc.com)