Re: OT: X.400 mhs-OR-Addresses

[Chris R. <Chr...@me...>]

On Wed, 10 May 2000 11:48:02 BST, Stuart Squibb wrote:
> I realise that this is not strictly a perl-ldap issue, but given the breadth
> of LDAP/X.500 knowledge available on the list I thought I'd ask here.
> 
> One of the attributes we currently store in our Exchange server is an X.400
> address. Current we use textencodedoraddress. A 'standard' with our
> organisation nationally is to use mhs-or-addresses. Can anyone enlighten me
> as to what this should look like? I know it is defined in X.402, but is
> there an 'easy' description I can use to implement this on an LDAP server?
> 
> Thanks,
> 
> Stuart.
> 
> Stuart Squibb
> IT Systems Manager
> Isle of Wight Health Authority
> 01983 535440 (Direct Line)
> 
> 

The text encoding should look roughly the same as you use for the 
textEncodedORAddress attribute. The difference between mhsORAddresses 
and textEncodedblahblah is that the former is only defined to have an 
equality matching rule, whereas since the latter is a string, substring 
matches are permitted. And of course the directory should barf if you 
try to enter a bogus mhsORAddress...

The text encoding is defined in RFC 1327. Section 4.2 looks like a good 
place to start. If your names have printable and teletex alternatives, 
then the encoding of these is ... bizarre ... I blame the author (my 
boss :-)

Cheers,

Chris