Rep (2) : Problem with oid root used in RFC 1274

Ascan Woermann <> Fri, 11 June 1993 13:21 UTC

Received: from by IETF.CNRI.Reston.VA.US id aa05446; 11 Jun 93 9:21 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa05441; 11 Jun 93 9:21 EDT
Received: from by CNRI.Reston.VA.US id aa09858; 11 Jun 93 9:21 EDT
X400-Received: by mta in / 400/C=gb/; Relayed; Fri, 11 Jun 1993 13:22:30 +0100
Date: Fri, 11 Jun 1993 13:22:30 +0100
X400-Recipients: non-disclosure:;
X400-MTS-Identifier: [/ 400/C=gb/; haig.cs.uc.469:]
Priority: Non-Urgent
DL-Expansion-History: ; Fri, 11 Jun 1993 13:22:30 +0100;
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Ascan Woermann <>
Message-ID: <7398012707464woer*/S=Woermann/OU=OSI/O=E3X/PRMD=E3X/ADMD=atlas/C=FR/@MHS>
To: Colin Robbins <>,,
In-Reply-To: "(q)7254 Wed Jun 9 18:57:59 1993(q)(a)":
References: "14060.9306091556(a)":
Subject: Rep (2) : Problem with oid root used in RFC 1274

>    >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.

I wouldn't bet on it.

> FYI, The paper OSI-DS 36 describes a general alias mechanism that can
> be used to alias  OIDS with exactly this form of transition in mind.
> Colin

I still haven't read this paper, but the current practise, as I've said
previously, is unacceptable in my opinion. A DUA or DSA requesting an
attribute by a given OID, should obtain it tagged with this OID. This should
be possible. Currently you require all implementations - even newcomers - 
to support the alias mechanism and, thus, know about the old OIDs. In practise,
a good moment after publication of RFC1274, we're effectively still running 
with old quipu-assigned OIDs for some attributes.