textEncodedORAddress format?/mhsORAddresses storage?

Peter Ruczynski <pjr@pyramid-technology.co.uk> Fri, 26 June 1992 15:53 UTC

Received: from ietf.nri.reston.va.us by IETF.NRI.Reston.VA.US id aa05681; 26 Jun 92 11:53 EDT
Received: from NRI.NRI.Reston.Va.US by IETF.NRI.Reston.VA.US id aa05677; 26 Jun 92 11:53 EDT
Received: from haig.cs.ucl.ac.uk by NRI.Reston.VA.US id aa16120; 26 Jun 92 11:54 EDT
Received: from bells.cs.ucl.ac.uk by haig.cs.ucl.ac.uk with local SMTP id <g.05670-0@haig.cs.ucl.ac.uk>; Fri, 26 Jun 1992 14:26:37 +0100
Via: uk.ac.uknet-relay; Fri, 26 Jun 1992 14:26:24 +0100
Received: from pyra.co.uk by eros.uknet.ac.uk with UUCP id <10212-0@eros.uknet.ac.uk>; Fri, 26 Jun 1992 13:34:31 +0100
Received: from pyrrot by pyrltd.pyra.co.uk; Fri, 26 Jun 92 12:49:54 +0100
From: Peter Ruczynski <pjr@pyramid-technology.co.uk>
Message-Id: <29786.9206261149@pyrrot.pyra.co.uk>
Subject: textEncodedORAddress format?/mhsORAddresses storage?
To: osi-ds@cs.ucl.ac.uk
Date: Fri, 26 Jun 92 11:49:50 GMT
X-Mailer: ELM [version 2.3 PL11]

A few questions about storing ORAddresses using QUIPU:

Is there a well known format for the textEncodedORAddress attribute?
If so, could some kind soul please send me some information about it.

Am I right in thinking that it is not the same as mhsORAddresses which
uses an ORAddress syntax which has to be put into the QUIPU database as
raw ASN.1?  Or is it just another name for the same thing, I suspect
not as it's syntax is CaseIgnoreString.

Are there any routines anywhere for putting mhsORAddresses into the
QUIPU database?  I've tried having a look at the PP code but I can't
seem to spot anything... any pointers anyone?

Any info much appreciated.

Pete.

-- 
Peter Ruczynski               Boldon James               email: pjr@pyra.co.uk
                               Pyramid House             phone: 0252 373035
#include <std/disclaimer.h>     Farnborough              fax:   0252 373135
Wot no funny comment :-)         Hants GU14 7PL,  England.