Re: [Isms] current naming agreement

["David B. Nelson" <d.b.nelson at comcast.net>]

Wes Hardaker writes...

>   In the TM document:
>      "Documents defining a new TM implementation MUST define a security
>      name prefix that will be pre-pended to all passed securityNames.
>      This prefix MUST be from 1-4 securityName compatible octets
>      followed by a ':' (ASCII 0x3a) character."

Will there be an IANA registry for this 1 to 4 character code?  Or will we
allow implementers to each make up their own set of abbreviations?  I think
an IANA registry is required, for purposes of interoperability.


_______________________________________________
Isms mailing list
Isms at ietf.org
https://www.ietf.org/mailman/listinfo/isms