Re: RFC1274 textEncodedORAddress Sat, 08 August 1992 14:12 UTC

Received: from by IETF.NRI.Reston.VA.US id aa05699; 8 Aug 92 10:12 EDT
Received: from NRI.NRI.Reston.Va.US by IETF.NRI.Reston.VA.US id aa05695; 8 Aug 92 10:12 EDT
Received: from by NRI.Reston.VA.US id au08676; 8 Aug 92 10:12 EDT
Received: from by with local SMTP id <>; Wed, 5 Aug 1992 14:55:03 +0100
Received: from by with Internet SMTP id <>; Wed, 5 Aug 1992 14:54:55 +0100
Received: from by (911016.SGI/4.7) id AA25677; Wed, 5 Aug 92 09:53:08 -0400
Message-Id: <>
Posted-From: The MITRE Corporation, Bedford, MA
Received: from localhost by with SMTP (PP) id <>; Wed, 5 Aug 1992 09:49:46 -0400
To: ren <>
Subject: Re: RFC1274 textEncodedORAddress
In-Reply-To: Your message of Wed, 05 Aug 92 09:30:58 +1000. <9208042331.AA09781@sicsds7.SICS.BU.OZ.AU>
Date: Wed, 05 Aug 92 09:49:43 -0400

> In RFC1274 - The Cosine and Internet X.500 Schema - section 9.3.2 says that
> the textEncodedORAddress attribute " intended for interim use only...".

> Why is this? 
> What other attribute can/should I use to indicate a users X.400 adddress?

You include "mhs-user" as an objectClass of the entry, and use the
"mhs-or-addresses" attribute to store addresses.  Unfortunately, this
method is still not perfect -- there is no linkage between multiple
O/R addresses and the values in the "mhs-deliverable-content-length"
and "mhs-deliverable-content-types" attributes.  That is, there is
no way to indicate that your O/R Address A can accept G3Fax and IA5
messages of any length, but your O/R Address B can only accept IA5
messages of length 80 (ASCII pagers anyone?).