Paul and I talked about this on the phone. We decided to place the OIDs in
each document. The rationale is simple. If a particular document need a
new OID, then corresponding text on the use of the OID should be added at
the same time. Putting the OID definition and the descriptive text in the
same place ensure synchronizations.
Russ
At 01:59 PM 2/26/98 -0500, John Pawling wrote:
Russ,
Whatever you want to do is fine with me. I thought that the S/MIME OIDs was
a part of the document tree, but if it is easier to divvy up these OIDs in
the various docs, then that is fine with me.
- John Pawling
At 01:44 PM 2/26/98 -0500, Russ Housley wrote:
John:
If we take that approack, then the OID module must be added to our document
tree.
Russ
At 12:06 PM 2/26/98 -0500, John Pawling wrote:
Russ,
The CMS and ESS modules could import the OIDs from the S/MIME OIDs module.
Defining the OIDs in multiple modules invites inconsistencies.
- John Pawling
At 09:40 AM 2/26/98 -0500, Russ Housley wrote:
Paul:
The OID in the registry is not sufficient. Please look at CMS Appendix A,
and you will see that the OIDs needed to implement CMS are part of the CMS
module.
Russ