Issue Security Credentials Command and Response payloads – structure definition Each instance of @IssueSecurityCredentials.CommandPayload and of @IssueSecurityCredentials.ResponsePayload shall be an octet string containing the DER encoding of the populated structure defined in this Section 13.4.6 which specifies the structure in ASN.1 notation. IssueSecurityCredentials DEFINITIONS ::= BEGIN CommandPayload ::= SEQUENCE { -- specify the keyUsage to which the generated key-pair will be put, if subsequently authorised keyUsage KeyUsage } ResponsePayload ::= CHOICE { -- if the Command was successful, provide the generated Certification Request. CertificationRequest shall -- be as defined in ASN.1 by IETF RFC 5912. For reference, it is in the section headed ‘ASN.1 Module for RFC 2986’ certificationRequest CertificationRequest, -- if the Command was unsuccessful, detail the failure issueCredentialsResponseCode IssueCredentialsResponseCode } -- KeyUsage is only repeated here for ease of reference. It is defined in IETF RFC 5912 KeyUsage ::= BIT STRING { -- Define valid uses of Public Keys held by Devices in their Trust Anchor Cells. digitalSignature (0), contentCommitment (1), -- not valid for GBCS compliant transactions keyEncipherment (2), -- not valid for GBCS compliant transactions dataEncipherment (3), -- not valid for GBCS compliant transactions keyAgreement (4), keyCertSign (5), -- not valid for this Use Case cRLSign (6), -- not valid for this Use Case encipherOnly (7), -- not valid for GBCS compliant transactions decipherOnly (8) -- not valid for GBCS compliant transactions } IssueCredentialsResponseCode::= INTEGER
Issue Security Credentials Command and Response payloads – structure definition Each instance of @IssueSecurityCredentials.CommandPayload and of @IssueSecurityCredentials.ResponsePayload shall be an octet string containing the DER encoding of the populated structure defined in this Section 13.4.6 which specifies the structure in ASN.1 notation. IssueSecurityCredentials DEFINITIONS ::= BEGIN CommandPayload ::= SEQUENCE { -- specify the keyUsage to which the generated key-pair will be put, if subsequently authorised keyUsage KeyUsage } ResponsePayload ::= CHOICE { -- if the Command was successful, provide the generated Certification Request. CertificationRequest shall -- be as defined in ASN.1 by IETF RFC 5912. For reference, it is in the section headed ‘ASN.1 Module for RFC 2986’ certificationRequest CertificationRequest, -- if the Command was unsuccessful, detail the failure issueCredentialsResponseCode IssueCredentialsResponseCode } -- KeyUsage is only repeated here for ease of reference. It is defined in IETF RFC 5912 KeyUsage ::= BIT STRING { -- Define valid uses of Public Keys held by Devices in their Trust Anchor Cells. digitalSignature (0), contentCommitment (1), -- not valid for GBCS compliant transactions keyEncipherment (2), -- not valid for GBCS compliant transactions dataEncipherment (3), -- not valid for GBCS compliant transactions keyAgreement (4), keyCertSign (5), -- not valid for this Use Case cRLSign (6), -- not valid for this Use Case encipherOnly (7), -- not valid for GBCS compliant transactions decipherOnly (8) -- not valid for GBCS compliant transactions } IssueCredentialsResponseCode::= INTEGER
GBCS_v0.8.1.docx