On Wed, 14 Sep 1994, Peter Williams wrote:
The encoding rules for encoding or "presenting" ASN.1 Certificate
values when conforming to the ISO 9735 EDIFACT standard - the
international EDI application of messaging - are given in the
"UN/EDIFACT Security implementation Guidelines." Given the nature of
the EDIFACT syntax level definitions used to constrain multilateral and
[...]
I know zip about EDIFACT, but your following comments about encoding '@'
and whatnot seem a bit weird to me. A BER-encoded Certificate is already
a very weird binary object that will need something like base64 (which
supposedly would get through Telex machines fine). Whether '@' is used or
not is irrelevant once the base64 wrapper has been added. I've probably
missed something though, so forgive this tired Aussie if that is the case.
I do find it strange that Internet WWW culture accepts such as
"URL: gopher://naic.nasa.gov:70/00/Notice";
as acceptable to users as a resource reference string,
but the Internet-types will no doubt scream at the equally machine-oriented
"To: /S=williams/OU=Sterling/O=ARC/PRMD=NASA/ADMD=TELEMAIL/C=US/ at
sprint.com"
or
"To: /S=williams/OU=Sterling/O=ARC/PRMD=NASA/ at arc.nasa.gov"
The X.400 forms are unnecessarily verbose and include unnecessary routing
instructions (ADMD=TELEMAIL). IMHO of course.
Cheers,
Rhys.