Reply to RFC 1327 Mappings in X.500
Michael Storz <michael.r.storz@lrz-muenchen.de> Fri, 11 March 1994 18:12 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07011; 11 Mar 94 13:12 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa07006; 11 Mar 94 13:12 EST
Received: from [129.179.91.44] by CNRI.Reston.VA.US id aa12617; 11 Mar 94 13:11 EST
Received: from mercury91.udev.cdc.com by sequoia.udev.cdc.com; Fri, 11 Mar 94 12:11:53 +0600
Received: by mercury.udev.cdc.com; Fri, 11 Mar 94 12:11:00 -0600
X-From: michael.r.storz@lrz-muenchen.de Fri Mar 11 12:11 CST 1994
Received: from cdsmail.cdc.com by mercury.udev.cdc.com; Fri, 11 Mar 94 12:10:58 -0600
Received: from cd1.lrz-muenchen.de by cdsmail.cdc.com id SMTP-0012d80b417022259; Fri, 11 Mar 94 12:10:47 -0600
Received: by cd1.lrz-muenchen.de; Fri, 11 Mar 94 19:10:11 +0100
X400-Received: by /c=de/admd=d400/prmd=lrz-muenchen/ ; Relayed ; 11 Mar 94 18:07:31 Z
X400-Received: by mta MTALRZCD1 in /c=de/admd=d400/prmd=lrz-muenchen/ ; Relayed ; 11 Mar 94 19:10:10 +0100
X400-Received: by mta MTALRZVEE in /c=de/admd=d400/prmd=lrz-muenchen/ ; Relayed ; 11 Mar 94 18:07:32 Z
X400-MTS-Identifier: /c=de/admd=d400/prmd=lrz-muenchen/ ; 940311190656791-MTALRZVEE
Content-Identifier: 940311190656791-
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: <940311190656791-MTALRZVEE*/c=de/admd=d400/prmd=lrz-muenchen/o=/ou=LRZ/s=Storz/g=Michael/i=R/@MHS>
In-Reply-To: <1756.763377842@glengoyn */c=de/admd=d400/prmd=com/o=isode/ou=glengoyne/s=763377842/g=1756/@MHS>
Date: Fri, 11 Mar 1994 18:07:31 +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 RFC 1327 Mappings in X.500
> 3) The "ommitted component" stuff fits very very badly into the open > routing tree > Suppose we would agree with this opinion. Then we could decide: The mapping of empty components alone will not be supported with routing trees. To map X.400 addresses (to and from) all posssible components one level lower in the hierarchy of the address must be registered in the routing tree. For the migration period till this registration has been done, a gateway must use the appropriate part of the RARE mapping tables locally. The advantage of this approach is: - no change of the documents and of implementaions is needed - empty organization is illegal, therefore all institutions which use such addresses should migrate to addresses with organization. If the address is not changed these organizations still have the possibility to register all OU1 in the routing tree. - empty PRMD: This will happen often with commercial organizations and ADMDs. If these organizations want to have normal RFC 822 addresses, they or their ADMD should register the organization in the routing tree. If these organizations are not registered in the routing tree, then the addresses are mapped to /s=surname/..../o=organization/@administrative-domain.country or /s=surname/..../o=organization/admd=administrative-domain/c=country/@gw which is valid and what this organization wanted. Adresses like surname@ous.organization.administrative-domain.country which would eventually be mapped to /s=surname/..../prmd=organization/admd=administrative-domain/c=country/ are invalid in RFC 822 and X.400 and therefore no problem. After I brought up this problem, I would like to withdrawn my "defect report" and go this direction. The only thing which should be done is to carefully document this decison. If we look at the RARE tables we see that more than 90 % of all entries with empty O are from Germany and some from France and nearly none from other countries. The remaining entries with empty PRMD should not be a problem because if these organizations will participate in direct routing, that means routing via X.500 and not a hierachical routing via ADMDs then these organizations will be registered automatically in the routing tree for routing and then they can specify in addition the mapping information. In Germany there is already a beginning movement to change the O/R addresses. One university has already changed their address, others are thinking about it and will change if the pressure is strong enough. We have discussed this now at several meetings here in Germany. After we have changed already our ADMD from DBP to D400, we will change next month the representation of RFC 822 addresses in X.400 from using ADMD=SPACE to ADMD=d400-gw, because SPACE is not allowed for this purpose. With the same argument we should also change the empty O. This will however again accelerate the decision of some universities to leave the X.400 world :-( Gruss Michael Regards, Michael
- Reply to RFC 1327 Mappings in X.500 Michael Storz
- Reply to RFC 1327 Mappings in X.500 Michael Storz