Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!ucbvax!OCFMAIL.OCF.LLNL.GOV!nessett
From: nessett@OCFMAIL.OCF.LLNL.GOV (Danny Nessett)
Newsgroups: comp.protocols.iso
Subject: X509 breaks presentation level layering
Message-ID: <9008072131.AA18982@ocfmail.ocf.llnl.gov>
Date: 7 Aug 90 21:31:42 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 12

Recently I was made aware of a requirement in X509 that SIGNED or SIGNATURE data
values force certain restrictions on the Basic Encoding Rules used to encode
them (see section 8.7 in the X509 document).  After reading the relevant
restrictions, I almost fainted.  Instead of defining a new encoding of the
ASN.1 abstract syntax to parallel BER, the X509 authors break the layering of
the presentation level by their requirements (i.e., an application protocol now
specifies that certain BER encodings are illegal).  How is it possible that
this egregious violation of ISO layering made it past the standards review
process?  Is there anyone on this list who has the inside scoop on this 
nightmare?

Dan Nessett