Path: utzoo!utgpu!watserv1!watmath!att!emory!swrinde!zaphod.mps.ohio-state.edu!usc!orion.oac.uci.edu!ucivax!gateway
From: Stef@ICS.UCI.EDU (Einar Stefferud)
Newsgroups: comp.protocols.iso.x400
Subject: Re: CRLF
Message-ID: <21581.664711621@nma>
Date: 24 Jan 91 11:19:18 GMT
Reply-To: Stef@ICS.UCI.EDU
Lines: 18
Approved: usenet@ICS.UCI.EDU
In-reply-to: Your message of Wed, 23 Jan 91 22:49:39 +0000.
             <ENAG.91Jan23234930@hild.ifi.uio.no>

Come on now you guys!  Cut that out!  IA% is defined to be an external
transfer format, and it is not ambiguous as to what it means in every
case, as I read what hs een quot4ed from various standards, including
RFC822 and RFC821.

Now, if we start mucking it up with verious internatl conventions, and
mix them together, we weil simply destroy the whole concept of an
external format!

It seems all to obvious to me that when you decode the ASN.1 trhat
contains IA5, that you can easily make all teh right translations
between the external format and your specific internal conventions in
each instance.

So, lets just go back to using IA% and ASN.1 and RFC822 as they were
written, without mucking them up!

Onward!  Cheers...\Stef