Blake Ramsdell wrote:
On Tuesday, November 11, 1997 4:29 PM, Jim Schaad (Exchange)
[SMTP:jimsch(_at_)EXCHANGE(_dot_)MICROSOFT(_dot_)com] wrote:
A complete search and replace should be done. Even the ASN.1 construct
in appends A is lower-cased. SMIMECapability is uppercased but
sMIMECapabilities is not.
AAAAAAHHHHHH!!!!
Can someone please, please, PLEASE explain the rules here!
My understanding is:
1. OIDs MUST have an initial lower case letter. This was cited and
acknowledged.
2. ASN.1 structures such as SMIMECapability and SMIMECapabilities have
an initial capitalized letter. I don't know if this is a MUST or not.
This is consistent with ContentInfo, SignedData, EnvelopedData, etc.
etc. etc.
If these two statements are true, then I believe that the changes in my
last message were accurate.
If this is not the case, then my universe has collapsed and I have to
start over with the Great ASN.1 Capitalization Understanding.
Blake
--
Blake C. Ramsdell
Worldtalk Corporation
For current info, check http://www.deming.com/users/blaker
Voice +1 425 882 8861 x103 Fax +1 425 882 8060
Blake is not loosing it. All types must start with an initial
cap, and all identifiers must start with an initial lowercase
letter. Classes (if you do 1994) must be all caps. So an OID
value, say
signedData OBJECT IDENTIFIER ::= { stuff }
identifies (names) a value of type OBJECT IDENTIFIER, but
SignedData ::= SEQUENCE { stuff }
defines an ASN.1 type.
Phil
--
Phillip H. Griffin Griffin Consulting
asn1(_at_)mindspring(_dot_)com ASN.1-SET-Java-Security
919.828.7114 1625 Glenwood Avenue
919.832.7008 [mail] Raleigh, North Carolina 27608 USA
------------------------------------------------------------
Visit http://www.fivepointsfestival.com
------------------------------------------------------------