[saag] Re: [Ext] Re: draft-paulwh-crypto-components-02 : recommended, MTI, OIDx
"Salz, Rich" <[email protected]>
| Newsgroups | gmane.ietf.saag |
|---|---|
| Message-ID | <[email protected]> |
>>> Hrm. This points to another reason to promote IANA registries instead of (or in addition to) OIDs. >> >> I don't think so. OIDs can be created and used by anyone, but OIDs not in a standards-track RFC seem to me just like private-use identifiers. > > Maybe you don't deal much with PKIX or CMS. The OIDs there are absolutely the way that the cryptographic components are identified. Yes, I know. I guess I wasn't clear. Anyone can define an OID and use it in an RFC. I am saying that if that RFC is Informational, not in the IETF stream, or anything else -- THAT IS NOT STANDARDS-TRACK -- then there is little noticeable difference between that(those) OID and private-use space in an IANA registry. Using your example, I can define a new PKCS#8 private key type that and publish an Individual draft or Experimental. But unless it came from LAMPS and is on the standards track, it's just (er) yelling into the wind, or a private-use identifier. _______________________________________________ saag mailing list -- [email protected] To unsubscribe send an email to [email protected]