Reply to Reply to MHS-DS: Changing the tree (OUCH)
Michael Storz <michael.r.storz@lrz-muenchen.de> Tue, 01 March 1994 16:24 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa04727; 1 Mar 94 11:24 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa04723; 1 Mar 94 11:24 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa09724; 1 Mar 94 11:24 EST
Received: from mercury.udev.cdc.com by IETF.CNRI.Reston.VA.US id aa04717; 1 Mar 94 11:24 EST
Received: by mercury.udev.cdc.com; Tue, 1 Mar 94 10:23:39 -0600
X-From: michael.r.storz@lrz-muenchen.de Tue Mar 1 10:23 CST 1994
Received: from cdsmail.cdc.com by mercury.udev.cdc.com; Tue, 1 Mar 94 10:23:29 -0600
Received: from cd1.lrz-muenchen.de by cdsmail.cdc.com id SMTP-0012d736bb6000146; Tue, 1 Mar 94 10:23:17 -0600
Received: by cd1.lrz-muenchen.de; Tue, 1 Mar 94 17:22:04 +0100
X400-Received: by /c=de/admd=d400/prmd=lrz-muenchen/ ; Relayed ; 01 Mar 94 16:19:24 Z
X400-Received: by mta MTALRZCD1 in /c=de/admd=d400/prmd=lrz-muenchen/ ; Relayed ; 01 Mar 94 17:22:02 +0100
X400-Received: by mta MTALRZVEE in /c=de/admd=d400/prmd=lrz-muenchen/ ; Relayed ; 01 Mar 94 16:19:24 Z
X400-MTS-Identifier: /c=de/admd=d400/prmd=lrz-muenchen/ ; 940301170934654-MTALRZVEE
Content-Identifier: 940301170934654-
Content-Return: Allowed
X400-Content-Type: P2-1984 ( 2 )
Conversion: Allowed
Original-Encoded-Information-Types: IA5-Text
Priority: normal
Disclose-Recipients: Prohibited
Alternate-Recipient: Prohibited
X400-Originator: michael.r.storz@lrz-muenchen.de
X400-Recipients: non-disclosure: ;
Message-Id: <940301170934654-MTALRZVEE*/c=de/admd=d400/prmd=lrz-muenchen/o=/ou=LRZ/s=Storz/g=Michael/i=R/@MHS>
In-Reply-To: <2d7355a31d39002@wally.u */c=us/admd=attmail/prmd=cdc/o=udev/ou=wally/s=2d7355a31d39002/@MHS>
Date: Tue, 01 Mar 1994 16:19:24 +0000
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Michael Storz <michael.r.storz@lrz-muenchen.de>
To: Return requested <mhs-ds@mercury.udev.cdc.com>
Subject: Reply to Reply to MHS-DS: Changing the tree (OUCH)
To be sure I understand the new mapping, I need an example. I want to have the following mapping: /c=de/admd=d400/prmd=lrz-muenchen/o= /ou=lrz/ <-> lrz.lrz-muenchen.d400.de This means I need for the mapping from X.400 to RFC 822 the entry c=de@aDMDName=d400@pRMDName=lrz-muenchen@mHSO=\20 with lrz-muenchen.d400.de as associated domain and from RFC 822 to X.400 the entry domainComponent=de@domainComponent=d400@domainComponent=lrz-muenchen with /c=de/admd=d400/prmd=lrz-muenchen/o= / as associated ORaddress Is this correct? Especially the representation of SPACE, in the RDN it is '\20' and in the X.400 address it is ' ', correct? Regards, Michael
- Reply to Reply to MHS-DS: Changing the tree (OUCH) Michael Storz
- Reply to MHS-DS: Changing the tree (OUCH) Kevin E. Jordan
- Reply to Reply to MHS-DS: Changing the tree (OUCH) Michael Storz
- Re: Reply to Reply to MHS-DS: Changing the tree (… Harald T. Alvestrand
- Reply to Reply to Reply to MHS-DS: Changing the t… Kevin E. Jordan