IANA SMI Numbers
id-ct-msec-token
{1 3 6 1 5 5 12 1 1}
id-ct-msec-token
Status in source: unspecified.
{
"value": "1",
"description": "id-ct-msec-token"
}Downloaded: 2026-10-18T22:58:17.903721+00:00.
Status in source: unspecified.
Names: id-ct-msec-token
{
"smi_kind": "OBJECT IDENTIFIER",
"definition": [
"id-ct-msec-token",
"OBJECT",
"IDENTIFIER",
"::=",
"{",
"1",
".",
"3",
".",
"6",
".",
"1",
".",
"5",
".",
"5",
".",
"12",
".",
"1",
".",
"1",
"}"
]
}id-ct-msec-token OBJECT IDENTIFIER ::= {1.3.6.1.5.5.12.1.1}id-ct-msec-token OBJECT IDENTIFIER ::= {1.3.6.1.5.5.12.1.1}The content of the SignedData is the token itself. It is represented
with the ContentType object identifier of
id-ct-msec-token OBJECT IDENTIFIER ::= {1.3.6.1.5.5.12.1.1}
The CMS sid value of the SignerInfo, which identifies the public key
needed to validate the signature, MUST be that of the Group Owner.
Token Creation and Receipt · Section 2:
Literal namespace and algorithm references from this RFC edition; the cited section specifies their protocol role.
Downloaded: 2026-10-19T00:20:55.896019+00:00.