keyEncipherment (2), -- not valid for GBCS compliant transactions dataEncipherment (3), keyAgreement (4), keyCertSign (5), cRLSign (6), encipherOnly (7), decipherOnly (8) -- not valid for GBCS compliant transactions } -- The GBCS only allows for a constrained set of Trust Anchor Cell operations and so the list of possible outcomes -- is more limited than in IETF RFC 5934. The list below is that more constrained subset StatusCode ::= ENUMERATED { success (0), -- trustAnchorNotFound indicates that details of a trust anchor were requested, but the referenced trust anchor -- is not represented on the Device trustAnchorNotFound (25), other (127)} END UpdateSecurityCredentials DEFINITIONS ::= BEGIN CommandPayload ::= SEQUENCE { -- Provide details to allow the Device to identify the Remote Party Role authorising -- this Command, check whether the rest of the payload is allowable, prevent replay attacks -- and allow counters / counter caches on the Device to be reset, if the Command changes the Remote Party -- in control. -- The Remote Party authorising the Command is that party which generated the KRP Signature (or the Access Control Broker -- if there is no KRP Signature) authorisingRemotePartyControl AuthorisingRemotePartyControl, -- One TrustAnchorReplacement structure is required for each Trust Anchor Cell that is to be updated replacements SEQUENCE OF TrustAnchorReplacement,
keyEncipherment (2), -- not valid for GBCS compliant transactions dataEncipherment (3), keyAgreement (4), keyCertSign (5), cRLSign (6), encipherOnly (7), decipherOnly (8) -- not valid for GBCS compliant transactions } -- The GBCS only allows for a constrained set of Trust Anchor Cell operations and so the list of possible outcomes -- is more limited than in IETF RFC 5934. The list below is that more constrained subset StatusCode ::= ENUMERATED { success (0), -- trustAnchorNotFound indicates that details of a trust anchor were requested, but the referenced trust anchor -- is not represented on the Device trustAnchorNotFound (25), other (127)} END UpdateSecurityCredentials DEFINITIONS ::= BEGIN CommandPayload ::= SEQUENCE { -- Provide details to allow the Device to identify the Remote Party Role authorising -- this Command, check whether the rest of the payload is allowable, prevent replay attacks -- and allow counters / counter caches on the Device to be reset, if the Command changes the Remote Party -- in control. -- The Remote Party authorising the Command is that party which generated the KRP Signature (or the Access Control Broker -- if there is no KRP Signature) authorisingRemotePartyControl AuthorisingRemotePartyControl, -- One TrustAnchorReplacement structure is required for each Trust Anchor Cell that is to be updated replacements SEQUENCE OF TrustAnchorReplacement,