Problem with oid root used in RFC 1274
Peter Furniss <cziwprf@pluto.ulcc.ac.uk> Wed, 09 June 1993 16:05 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06542; 9 Jun 93 12:05 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa06538; 9 Jun 93 12:05 EDT
Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa17913; 9 Jun 93 12:05 EDT
Received: from bells.cs.ucl.ac.uk by haig.cs.ucl.ac.uk with local SMTP id <g.03427-0@haig.cs.ucl.ac.uk>; Wed, 9 Jun 1993 16:57:10 +0100
Via: uk.ac.nsfnet-relay; Wed, 9 Jun 1993 16:56:47 +0100
Via: uk.ac.ulcc.pluto; Wed, 9 Jun 1993 16:56:28 +0100
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Peter Furniss <cziwprf@pluto.ulcc.ac.uk>
Message-Id: <14060.9306091556@pluto.ulcc.ac.uk>
Subject: Problem with oid root used in RFC 1274
To: Steve Hardcastle-Kille <S.Kille@isode.com>
Date: Wed, 09 Jun 1993 16:56:13 -0000
Cc: osi-ds@cs.ucl.ac.uk
Reply-To: P.Furniss@ulcc.ac.uk
X-Mailer: ELM [version 2.3 PL11]
Steve, Some while ago we exchanged messages about this problem, with no final conclusion. The JNT's OSI technical group has suggested I bring it to this mailing list. RFC 1274 (The COSINE and Internet X.500 Schema) defines Directory objects and attributes which have the following object id root for their identifications: {ccitt(0) data(9) pss(2342) ucl(19200300) pilot(100)} However, it appears that this is not a valid object id, as annex C of ISO/IEC 8824:1990 identifies only four arcs below ccitt(0). CCITT (now ITU-TS) have not assigned any new arcs. (as far as I can make out) The OSI-tg interest is because some of the attributes cover transition from the UK NRS scheme to Directory. The problem is whether the oid root should be changed to a valid one, or we just carry on and don't worry. If we don't change, there is some risk that some (commercial) Directory implementation may include something that refuses to allow invalid oids, and which therefore could not accept or access entries using the 1274 schema. Since the awkward implementation could claim to be a more accurate implementation of the CCITT/ISO standard, this might produce some strange arguments. We would be propagating something that is nearly, but not quite osi. There would obviously be some difficulty with a change-over to synonymous valid oids. It will be extremely difficult unless Directory implementations can handle synonyms - but I believe many can. If the oid root is changed, it would be possible to make it appreciably shorter - using an additional, IANA-assigned, arc from the same root as SNMP uses would seem sensible. What should be done ? Peter Furniss
- Problem with oid root used in RFC 1274 Peter Furniss
- Re: Problem with oid root used in RFC 1274 Colin Robbins
- Re: Problem with oid root used in RFC 1274 Steve Kille
- Re: Problem with oid root used in RFC 1274 Peter Furniss