Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!ll-xn!ames!lll-tis!CS.UCL.AC.UK!steve From: steve@CS.UCL.AC.UK (Steve Kille) Newsgroups: comp.protocols.iso.x400.gateway Subject: Re: Response to comments on DRAFT/2 Message-ID: <2799.591261970@UK.AC.UCL.CS> Date: 26 Sep 88 09:26:10 GMT References: <8809211418.AA17842@cblpf.ATT.COM> Sender: root@tis.llnl.gov Distribution: inet Organization: The Internet Lines: 26 Approved: post-x400-gateway@tis.llnl.gov >From: mark@com.att.cblpf >To: ifip-gtwy@gov.llnl.tis, rare-wg1>Subject: Re: Response to comments on DRAFT/2 >Date: 21 Sep 88 21:12 +0100 >In particular, the major objection seems to be that it's not obvious how >to deal with blanks and slashes. I went back and looked at 987 to double >check. It seems that blank is encoded as _ and that / is encoded as #s# >and to encode _ you use #u# . Since slashes and underscores will be >rare, you won't see many instances of #s# in addresses. Since blanks are >more common, you will see a fair number of underscores. There are, of >course, escapes to cover other characters in the syntax, such as = , >and an octal escape to cover anything unforeseen. This is the mapping described in Appendix A. See 4.2.4 - item 4. "Use of this encoding is discouraged". This encoding was desgined for "old fashioned" (typically UUCP) RFC 822 systems, which could not handle the quoted string encoding. It should only be used by systems that really cannot avoid it. Steve