Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ukma!xanth!ames!lll-winken!ncis.llnl.gov!CS.UCL.AC.UK!S.Kille From: S.Kille@CS.UCL.AC.UK (Steve Kille) Newsgroups: comp.protocols.iso.x400 Subject: Re: Problem with mapping between RFC and X.400 adresses Message-ID: <14253.602344917@UK.AC.UCL.CS> Date: 2 Feb 89 01:01:00 GMT References: Sender: daemon@ncis.llnl.gov Distribution: inet Organization: The Internet Lines: 37 Approved: post-x400@tis.llnl.gov Phone: +44-1-380-7294 ermmmm - how about using the quoting mechanism specied in RFC 987?? Steve >From: P4403@se.qz.com >To: mhsnews >Subject: Problem with mapping between RFC and X.400 adresses >Date: 1 Feb 89 12:44 +0100 >>X-Bitnet-Sender: "Johan Lundberg TeleDelta (Swedish Telecom)" >A serius problem has been discovered with the current RFC-987 >mapping >of >X.400 >addresses to domain address that is used by the >academic comunity. The problem is the usage of the separator "." >(punctuation mark, full stop) between the "attributes" in the domain address. > >In an X.400 address the "." is a leagal character in any of the attributes. >Many organizations make use of this character in their names >If such an organisationName or orgUnitName is used mapping from X.400 to RFC >will cause problem since the routing will probably fail. >And trying to map a sucsessfully transformed but not routable address >back again to X.400 will also fail. > >One could perhaps circumvent this if one knows about those that uses "." >in thier names, but that will only work for the known ones and will make a >gateway more complex. > >Has this been discussed and is there a solution to this problem? >