Re: OSI-DS 23

Tim Howes <tim@terminator.cc.umich.edu> Wed, 10 June 1992 19:42 UTC

Received: from nri.nri.reston.va.us by ietf.NRI.Reston.VA.US id aa04978; 10 Jun 92 15:42 EDT
Received: from nri.reston.va.us by NRI.Reston.VA.US id aa27136; 10 Jun 92 15:41 EDT
Received: from bells.cs.ucl.ac.uk by NRI.Reston.VA.US id aa27123; 10 Jun 92 15:41 EDT
Received: from terminator.cc.umich.edu by bells.cs.ucl.ac.uk with Internet SMTP id <g.19129-0@bells.cs.ucl.ac.uk>; Wed, 10 Jun 1992 20:14:25 +0100
Received: from vertigo.rs.itd.umich.edu by terminator.cc.umich.edu (5.65/1123-1.0) id AA12885; Wed, 10 Jun 92 15:13:53 -0400
Message-Id: <9206101913.AA12885@terminator.cc.umich.edu>
To: Steve Hardcastle-Kille <S.Kille@isode.com>
Cc: osi-ds@cs.ucl.ac.uk
Subject: Re: OSI-DS 23
In-Reply-To: Your message of "Wed, 10 Jun 92 19:50:07 BST." <2751.708202207@UK.AC.UCL.CS>
Date: Wed, 10 Jun 1992 15:13:50 -0400
From: Tim Howes <tim@terminator.cc.umich.edu>

> From:    Steve Hardcastle-Kille <S.Kille@isode.com>
> To:      Tim Howes <tim@terminator.cc.umich.edu>

> You are right about `"` and the omissions in the list of 2.3.  I don't
> see where you get <> as specials.   If you need to have DNs as RDNs,
> the current syntax will force you to hex.    Is there a serious need
> to change this?

In the BNF, you include ">" as a special character.  I assumed that
this was to allow DNs to be written in OSI-DS-23 form inside another
DN, and that you had just left out "<".  It seems like a good idea,
even if it was not what you intended.  I think using hex should be
a last last last resort.  Of course, I don't think a DN as part of
another DN will come up very often, so whatever...           -- Tim