I hope I get this right. I think its close ;-)
Type references and module references MUST start with an uppercase
letter. Value references and identifiers MUST start with a lower case
letter.
ThisIsAModuleReference {1 2 3} DEFINITIONS
BEGIN
ThisIsATypeReference ::= SEQUENCE
{
thisIsAnIdentifier INTEGER (1..10),
thisIsAnotherIndetifier INTEGER (1..10)
}
thisIsAValueReference ThisIsATypeReference ::=
{
thisIsAnIdentifier 1,
thisIsAnotherIndentifier 2
}
END
The name of an OID is by its nature a value reference therefore it MUST
start with lowercase.
Roger
----------
From: Blake Ramsdell[SMTP:BlakeR(_at_)deming(_dot_)com]
Sent: 12 November 1997 00:46
To: 'Jim Schaad (Exchange)'; 'Paul Hoffman / IMC';
'ietf-smime(_at_)imc(_dot_)org'
Subject: RE: Even newer versions of the drafts
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