draft-ietf-smime-symkeydist-03.txt   draft-ietf-smime-symkeydist-04.txt 
SMIME Working Group S. Turner SMIME Working Group S. Turner
Internet Draft IECA Internet Draft IECA
Document: draft-ietf-smime-symkeydist-03.txt March 2, 2001 Document: draft-ietf-smime-symkeydist-04.txt April 30, 2001
Expires: September 2, 2001 Expires: October 30, 2001
S/MIME Symmetric Key Distribution S/MIME Symmetric Key Distribution
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026 [1]. all provisions of Section 10 of RFC2026 [1].
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas,
skipping to change at line 60 skipping to change at line 60
Conventions used in this document Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC-2119 [4]. document are to be interpreted as described in RFC-2119 [4].
1. INTRODUCTION....................................................3 1. INTRODUCTION....................................................3
1.1 APPLICABILITY TO E-MAIL........................................4 1.1 APPLICABILITY TO E-MAIL........................................4
1.2 APPLICABILITY TO REPOSITORIES..................................4 1.2 APPLICABILITY TO REPOSITORIES..................................4
2. ARCHITECTURE....................................................5
3. PROTOCOL INTERACTIONS...........................................6 3. PROTOCOL INTERACTIONS...........................................6
3.1 CONTROL ATTRIBUTES.............................................7 3.1 CONTROL ATTRIBUTES.............................................7
3.1.1 GL USE KEK...................................................8 3.1.1 GL USE KEK...................................................8
3.1.2 DELETE GL...................................................11 3.1.2 DELETE GL...................................................12
3.1.3 ADD GL MEMBER...............................................11 3.1.3 ADD GL MEMBER...............................................12
3.1.4 DELETE GL MEMBER............................................12 3.1.4 DELETE GL MEMBER............................................13
3.1.5 REKEY GL....................................................13 3.1.5 REKEY GL....................................................14
3.1.6 ADD GL OWNER................................................14 3.1.6 ADD GL OWNER................................................15
3.1.7 REMOVE GL OWNER.............................................14 3.1.7 REMOVE GL OWNER.............................................15
3.1.8 GL KEY COMPROMISE...........................................14 3.1.8 GL KEY COMPROMISE...........................................15
3.1.9 GL KEY REFRESH..............................................15 3.1.9 GL KEY REFRESH..............................................16
3.1.10 GL SUCCESS INFORMATION.....................................15 3.1.10 GLA QUERY REQUEST AND RESPONSE.............................16
3.1.11 GL FAIL INFORMATION........................................16 3.1.10.1 GLA QUERY REQUEST........................................16
3.1.12 GLA QUERY REQUEST..........................................18 3.1.10.2 GLA QUERY RESPONSE.......................................17
3.1.13 GLA QUERY RESPONSE.........................................18 3.1.10.3 REQUEST AND RESPONSE TYPES...............................17
3.1.14 PROVIDE CERT...............................................19 3.1.12 PROVIDE CERT...............................................17
3.1.15 UPDATE CERT................................................20 3.1.13 UPDATE CERT................................................18
3.1.16 GL KEY.....................................................21 3.1.14 GL KEY.....................................................19
3.2 USE OF CMC, CMS, AND PKIX.....................................22 3.2 USE OF CMC, CMS, AND PKIX.....................................21
3.2.1 PROTECTION LAYERS...........................................22 3.2.1 PROTECTION LAYERS...........................................21
3.2.1.1 MINIMUM PROTECTION........................................23 3.2.1.1 MINIMUM PROTECTION........................................21
3.2.1.2 ADDITIONAL PROTECTION.....................................23 3.2.1.2 ADDITIONAL PROTECTION.....................................21
3.2.2 COMBINING REQUESTS AND RESPONSES............................23 3.2.2 COMBINING REQUESTS AND RESPONSES............................22
3.2.3 GLA GENERATED MESSAGES......................................25 3.2.3 GLA GENERATED MESSAGES......................................23
3.2.4 CMC CONTROL ATTRIBUTES......................................26 3.2.4 CMC CONTROL ATTRIBUTES......................................24
3.2.5 RESUBMITTED GL MEMBER MESSAGES..............................27 3.2.4.1 USING CMCSTATUSINFOEX.....................................24
3.2.4.2 USING TRANSACTIONID.......................................27
3.2.4.3 USING NONCES..............................................27
3.2.4.4 CMC ATTRIBUTE SUPPORT REQUIREMENTS........................27
3.2.5 RESUBMITTED GL MEMBER MESSAGES..............................28
3.2.6 PKIX........................................................28 3.2.6 PKIX........................................................28
4 ADMINISTRATIVE MESSAGES.........................................28 4 ADMINISTRATIVE MESSAGES.........................................28
4.1 ASSIGN KEK TO GL..............................................28 4.1 ASSIGN KEK TO GL..............................................28
4.2 DELETE GL FROM GLA............................................31 4.2 DELETE GL FROM GLA............................................31
4.3 ADD MEMBERS TO GL.............................................33 4.3 ADD MEMBERS TO GL.............................................33
4.3.1 GLO INITIATED ADDITIONS.....................................34 4.3.1 GLO INITIATED ADDITIONS.....................................34
4.3.2 PROSPECTIVE MEMBER INITIATED ADDITIONS......................40 4.3.2 PROSPECTIVE MEMBER INITIATED ADDITIONS......................40
4.4 DELETE MEMBERS FROM GL........................................42 4.4 DELETE MEMBERS FROM GL........................................42
4.4.1 GLO INITIATED DELETIONS.....................................43 4.4.1 GLO INITIATED DELETIONS.....................................43
4.4.2 MEMBER INITIATED DELETIONS..................................47 4.4.2 MEMBER INITIATED DELETIONS..................................47
4.5 REQUEST REKEY OF GL...........................................48 4.5 REQUEST REKEY OF GL...........................................48
4.5.1 GLO INITIATED REKEY REQUESTS................................49 4.5.1 GLO INITIATED REKEY REQUESTS................................49
4.5.2 GLA INITIATED REKEY REQUESTS................................51 4.5.2 GLA INITIATED REKEY REQUESTS................................52
4.6 CHANGE GLO....................................................52
4.7 INDICATE KEK COMPROMISE.......................................54
4.7.1 GL MEMBER INITIATED KEK COMPROMISE MESSAGE..................55
Turner 2 Turner 2
4.6 CHANGE GLO....................................................52
4.7 INDICATE KEK COMPROMISE.......................................55
4.7.1 GL MEMBER INITIATED KEK COMPROMISE MESSAGE..................55
4.7.2 GLO INITIATED KEK COMPROMISE MESSAGE........................56 4.7.2 GLO INITIATED KEK COMPROMISE MESSAGE........................56
4.8 REQUEST KEK REFRESH...........................................57 4.8 REQUEST KEK REFRESH...........................................57
4.9 GLA QUERY REQUEST AND RESPONSE................................58 4.9 GLA QUERY REQUEST AND RESPONSE................................58
4.10 UPDATE MEMBER CERTIFICATE....................................60 4.10 UPDATE MEMBER CERTIFICATE....................................60
4.10.1 GLO AND GLA INITIATED UPDATE MEMBER CERTIFICATE............60 4.10.1 GLO AND GLA INITIATED UPDATE MEMBER CERTIFICATE............60
4.10.2 GL MEMBER INITIATED UPDATE MEMBER CERTIFICATE..............62 4.10.2 GL MEMBER INITIATED UPDATE MEMBER CERTIFICATE..............62
5 DISTRIBUTION MESSAGE............................................63 5 DISTRIBUTION MESSAGE............................................63
5.1 DISTRIBUTION PROCESS..........................................64 5.1 DISTRIBUTION PROCESS..........................................64
6 ALGORITHMS......................................................64 6 ALGORITHMS......................................................65
6.1 KEK GENERATION ALGORITHM......................................65 6.1 KEK GENERATION ALGORITHM......................................65
6.2 SHARED KEK WRAP ALGORITHM.....................................65 6.2 SHARED KEK WRAP ALGORITHM.....................................65
6.3 SHARED KEK ALGORITHM..........................................65 6.3 SHARED KEK ALGORITHM..........................................65
7 TRANSPORT.......................................................65 7 TRANSPORT.......................................................65
8 USING THE GROUP KEY.............................................65 8 USING THE GROUP KEY.............................................65
9 SECURITY CONSIDERATIONS.........................................66 9 SECURITY CONSIDERATIONS.........................................66
10 REFERENCES.....................................................66 10 REFERENCES.....................................................66
11 ACKNOWLEDGEMENTS...............................................66 11 ACKNOWLEDGEMENTS...............................................67
12 AUTHOR'S ADDRESSES.............................................67 12 AUTHOR'S ADDRESSES.............................................67
1. Introduction 1. Introduction
With the ever-expanding use of secure electronic communications With the ever-expanding use of secure electronic communications
(e.g., S/MIME [2]), users require a mechanism to distribute (e.g., S/MIME [2]), users require a mechanism to distribute
encrypted data to multiple recipients (i.e., a group of users). encrypted data to multiple recipients (i.e., a group of users).
There are essentially two ways to encrypt the data for recipients: There are essentially two ways to encrypt the data for recipients:
using asymmetric algorithms with public key certificates (PKCs) or using asymmetric algorithms with public key certificates (PKCs) or
symmetric algorithms with symmetric keys. symmetric algorithms with symmetric keys.
skipping to change at line 153 skipping to change at line 156
collect and validate the PKCs for each of the recipients. Each collect and validate the PKCs for each of the recipients. Each
recipient identifies their per-recipient information and uses the recipient identifies their per-recipient information and uses the
private key associated with the public key of their PKC to decrypt private key associated with the public key of their PKC to decrypt
the CEK and hence gain access to the encrypted content. the CEK and hence gain access to the encrypted content.
With symmetric algorithms, the origination process is the same as With symmetric algorithms, the origination process is the same as
with asymmetric algorithms except for what encrypts the CEK. Instead with asymmetric algorithms except for what encrypts the CEK. Instead
of using PKCs, the originator uses a previously distributed secret of using PKCs, the originator uses a previously distributed secret
key-encryption key (KEK) to encrypt the CEK (kekri RecipientInfo key-encryption key (KEK) to encrypt the CEK (kekri RecipientInfo
CHOICE). Only one copy of the encrypted CEK is required because all CHOICE). Only one copy of the encrypted CEK is required because all
Turner 3
the recipients already have the shared KEK needed to decrypt the CEK the recipients already have the shared KEK needed to decrypt the CEK
and hence gain access to the encrypted content. and hence gain access to the encrypted content.
Turner 3
The security provided by the shared KEK is only as good as the sum The security provided by the shared KEK is only as good as the sum
of the techniques employed by each member of the group to keep the of the techniques employed by each member of the group to keep the
KEK secret from nonmembers. These techniques are beyond the scope of KEK secret from nonmembers. These techniques are beyond the scope of
this document. Only the members of the list and the key manager this document. Only the members of the list and the key manager
should have the KEK in order to maintain the secrecy of the group. should have the KEK in order to maintain the secrecy of the group.
Access control to the information protected by the KEK is determined Access control to the information protected by the KEK is determined
by the entity that encrypts the information, as all members of the by the entity that encrypts the information, as all members of the
group have access. If the entity that is performing the encryption group have access. If the entity that is performing the encryption
wants to ensure some subset of the group does not gain access to the wants to ensure some subset of the group does not gain access to the
information either a different KEK should be used (shared with this information either a different KEK should be used (shared with this
skipping to change at line 245 skipping to change at line 248
support this spectrum, the mechanism described herein supports both support this spectrum, the mechanism described herein supports both
managed (i.e., where access control is applied) and unmanaged (i.e., managed (i.e., where access control is applied) and unmanaged (i.e.,
where no access control is applied) GLs. The access control where no access control is applied) GLs. The access control
mechanism for managed lists is beyond the scope of this document. mechanism for managed lists is beyond the scope of this document.
In either case, the GL must initially be constructed by an entity In either case, the GL must initially be constructed by an entity
hereafter called the Group List Owner (GLO). There may be multiple hereafter called the Group List Owner (GLO). There may be multiple
entities who 'own' the GL and who are allowed to make changes the entities who 'own' the GL and who are allowed to make changes the
GLĘs properties or membership. The GLO determines if the GL will be GLĘs properties or membership. The GLO determines if the GL will be
managed or unmanaged and is the only entity that may delete the GL. managed or unmanaged and is the only entity that may delete the GL.
GLO(s) may or may not be GL members. GLO(s) may or may not be GL members. GLO(s) may also setup lists
that are closed, where the GLO solely determines GL membership.
Turner 5 Turner 5
Though Figure 1 depicts the GLA as encompassing both the KMA and GMA Though Figure 1 depicts the GLA as encompassing both the KMA and GMA
functions, the two functions could be supported by the same entity functions, the two functions could be supported by the same entity
or they could be supported by two different entities. If two or they could be supported by two different entities. If two
entities are used, they could be located on one or two platforms. entities are used, they could be located on one or two platforms.
There is however a close relationship between the KMA and GMA There is however a close relationship between the KMA and GMA
functions. If the GMA stores all information pertaining to the GLs functions. If the GMA stores all information pertaining to the GLs
and the KMA merely generates keys, a corrupted GMA could cause and the KMA merely generates keys, a corrupted GMA could cause
havoc. To protect against a corrupted GMA, the KMA would be forced havoc. To protect against a corrupted GMA, the KMA would be forced
skipping to change at line 272 skipping to change at line 276
Henceforth, the distinction between the two agents is omitted; the Henceforth, the distinction between the two agents is omitted; the
term GLA will be used to address both functions. It should be noted term GLA will be used to address both functions. It should be noted
that corrupt GLA can always cause havoc. that corrupt GLA can always cause havoc.
3. Protocol Interactions 3. Protocol Interactions
There are existing mechanisms (e.g., listserv and majordomo) to There are existing mechanisms (e.g., listserv and majordomo) to
support managing GLs; however, this document does not address support managing GLs; however, this document does not address
securing these mechanisms, as they are not standardized. Instead, it securing these mechanisms, as they are not standardized. Instead, it
defines protocol interactions, as depicted in Figure 2, used by the defines protocol interactions, as depicted in Figure 2, used by the
GL members, GLA, and GLO to manage GLs and distribute shared KEKs. GL members, GLA, and GLO(s) to manage GLs and distribute shared
The interactions have been divided into administration messages and KEKs. The interactions have been divided into administration
distribution messages. The administrative messages are the request messages and distribution messages. The administrative messages are
and response messages needed to setup the GL, delete the GL, add the request and response messages needed to setup the GL, delete the
members to the GL, delete members of the GL, and request a group GL, add members to the GL, delete members of the GL, and request a
rekey, etc. The distribution messages are the messages that group rekey, etc. The distribution messages are the messages that
distribute the shared KEKs. The following sections describe the distribute the shared KEKs. The following sections describe the
ASN.1 for both the administration and distribution messages. Section ASN.1 for both the administration and distribution messages. Section
4 describes how to use the administration messages and section 5 4 describes how to use the administration messages and section 5
describes how to use the distribution messages. describes how to use the distribution messages.
+-----+ +----------+ +-----+ +----------+
| GLO | <---+ +----> | Member 1 | | GLO | <---+ +----> | Member 1 |
+-----+ | | +----------+ +-----+ | | +----------+
| | | |
+-----+ <------+ | +----------+ +-----+ <------+ | +----------+
skipping to change at line 302 skipping to change at line 306
+----> | Member n | +----> | Member n |
+----------+ +----------+
Figure 2 - Protocol Interactions Figure 2 - Protocol Interactions
Turner 6 Turner 6
3.1 Control Attributes 3.1 Control Attributes
The messages are based on including control attributes in CMC's The messages are based on including control attributes in CMC's
PKIData for requests and CMC's ResponseBody0 for responses. The PKIData for requests and CMC's ResponseBody for responses. The
content-types PKIData and PKIResponse are then encapsulated in CMS's content-types PKIData and PKIResponse are then encapsulated in CMS's
SignedData or EnvelopedData, or a combination of the two (see SignedData or EnvelopedData, or a combination of the two (see
section 3.2). The following are the control attributes defined in section 3.2). The following are the control attributes defined in
this document: this document:
Control Control
Attribute OID Syntax Attribute OID Syntax
------------------- ----------- ----------------- ------------------- ----------- -----------------
glUseKEK id-skd 1 GLUseKEK glUseKEK id-skd 1 GLUseKEK
glDelete id-skd 2 GeneralName glDelete id-skd 2 GeneralName
glAddMember id-skd 3 GLAddMember glAddMember id-skd 3 GLAddMember
glDeleteMember id-skd 4 GLDeleteMember glDeleteMember id-skd 4 GLDeleteMember
glRekey id-skd 5 GLRekey glRekey id-skd 5 GLRekey
glAddOwner id-skd 6 GLOwnerAdministration glAddOwner id-skd 6 GLOwnerAdministration
glRemoveOwner id-skd 7 GLOwnerAdministration glRemoveOwner id-skd 7 GLOwnerAdministration
glkCompromise id-skd 8 GeneralName glkCompromise id-skd 8 GeneralName
glkRefresh id-skd 9 GLKRefresh glkRefresh id-skd 9 GLKRefresh
glSuccessInfo id-skd 10 GLSuccessInfo glaQueryRequest id-skd 11 GLAQueryRequest
glFailInfo id-skd 11 GLFailInfo glaQueryResponse id-skd 12 GLAQueryResponse
glaQueryRequest id-skd 12 GLAQueryRequest glProvideCert id-skd 13 GLManageCert
glaQueryResponse id-skd 13 GLAQueryResponse glUpdateCert id-skd 14 GLManageCert
glProvideCert id-skd 14 GLManageCert glKey id-skd 15 GLKey
glUpdateCert id-skd 15 GLManageCert
glKey id-skd 16 GLKey
In the following conformance tables, the column headings have the In the following conformance tables, the column headings have the
following meanings: O for originate, R for receive, F for forward. following meanings: O for originate, R for receive, and F for
There are three types of implementations: GLOs, GLAs, and GL forward. There are three types of implementations: GLOs, GLAs, and
members. The GLO is an optional component hence all of the messages GL members. The GLO is an optional component hence all GLO O and R
for it are optional and the GLO forwarding messages to it or the GL messages are optional and GLA F messages are optional. The first
member. The first table includes messages that MUST be implemented table includes messages that MUST be implemented in order to be
in order to be considered conformant to this document. The second considered conformant to this document. The second table includes
table includes messages that MAY be implemented in order to be messages that MAY be implemented in order to be considered
considered conformant to this document. conformant to this document. Note that ō-ō mean not applicable.
Turner 7
Required Required
Implementation Requirement | Control Implementation Requirement | Control
GLO | GLA | GL Member | Attribute GLO | GLA | GL Member | Attribute
O R |O R F | O R | O R |O R F | O R |
-------- |------------------ |--------- |---------- ------- | ----------------- | --------- | ----------
MAY - |MUST - MAY | - MUST |glProvideCert MAY - |MUST - MAY | - MUST |glProvideCert
MAY MAY | - MUST MAY | MUST - |glUpdateCert MAY MAY | - MUST MAY | MUST - |glUpdateCert
- - |MUST - - | - MUST |glKey - - |MUST - - | - MUST |glKey
- MAY |MUST - - | - MUST |glSucessInfo
- MAY |MUST - - | - MUST |glFailInfo
Turner 7
Optional Optional
Implementation Requirement | Control Implementation Requirement | Control
GLO | GLA | GL Member | Attribute GLO | GLA | GL Member | Attribute
O R |O R F | O R | O R |O R F | O R |
-------- |------------------ |--------- |---------- ------- | ----------------- | --------- | ----------
MAY - | - MAY - | - - |glUseKEK MAY - | - MAY - | - - |glUseKEK
MAY - | - MAY - | - - |glDelete MAY - | - MAY - | - - |glDelete
MAY MAY | - MUST MAY | MUST - |glAddMember MAY MAY | - MUST MAY | MUST - |glAddMember
MAY MAY | - MUST MAY | MUST - |glDeleteMember MAY MAY | - MUST MAY | MUST - |glDeleteMember
MAY - | - MAY - | - - |glRekey MAY - | - MAY - | - - |glRekey
MAY - | - MAY - | - - |glAddOwner MAY - | - MAY - | - - |glAddOwner
MAY - | - MAY - | - - |glRemoveOwner MAY - | - MAY - | - - |glRemoveOwner
MAY MAY | - MUST MAY | MUST - |glkCompromise MAY MAY | - MUST MAY | MUST - |glkCompromise
MAY - | - MUST - | MUST - |glkRefresh MAY - | - MUST - | MUST - |glkRefresh
MAY - | - SHOULD - | MAY - |glaQueryRequest MAY - | - SHOULD - | MAY - |glaQueryRequest
- MAY |SHOULD - - | - MAY |glaQueryResponse - MAY |SHOULD - - | - MAY |glaQueryResponse
glSuccessInfo, glFailInfo, glaQueryResponse, and gloResponse are glaQueryResponse, and gloResponse are responses and go into the
responses and go into the PKIResponse content-type, all other PKIResponse content-type, all other control attributes are included
control attributes are included in requests and go into the PKIData in requests and go into the PKIData content-type. The exception is
content-type. The exception is glUpdateCert which may be included in glUpdateCert which may be included in either PKIData or PKIResponse.
either PKIData or PKIResponse.
Success and failure messages use CMC (see paragraph 3.2.4).
3.1.1 GL USE KEK 3.1.1 GL USE KEK
The GLO uses glUseKEK to request that a shared KEK be assigned to a The GLO uses glUseKEK to request that a shared KEK be assigned to a
GL. glUseKEK messages MUST be signed by the GLO. The glUseKEK GL. glUseKEK messages MUST be signed by the GLO. The glUseKEK
control attribute shall have the syntax GLUseKEK: control attribute shall have the syntax GLUseKEK:
GLUseKEK ::= SEQUENCE { GLUseKEK ::= SEQUENCE {
glInfo GLInfo, glInfo GLInfo,
glOwnerInfo SEQUENCE SIZE (1..MAX) OF GLOwnerInfo, glOwnerInfo SEQUENCE SIZE (1..MAX) OF GLOwnerInfo,
glAdministration GLAdministration DEFAULT (1), glAdministration GLAdministration DEFAULT 1,
glKeyAttributes GLKeyAttributes OPTIONAL } glKeyAttributes GLKeyAttributes OPTIONAL }
Turner 8
GLInfo ::= SEQUENCE { GLInfo ::= SEQUENCE {
glName GeneralName, glName GeneralName,
glAddress GeneralName } glAddress GeneralName }
GLOwnerInfo ::= SEQUENCE { GLOwnerInfo ::= SEQUENCE {
glOwnerName GeneralName, glOwnerName GeneralName,
glOwnerAddress GeneralName } glOwnerAddress GeneralName,
certificate Certificates OPTIONAL }
Turner 8
Certificates ::= SEQUENCE {
pKC [0] Certificate OPTIONAL,
-- See PKIX [5]
aC [1] SEQUENCE SIZE (1.. MAX) OF
AttributeCertificate OPTIONAL,
-- See ACPROF [6]
certificationPath [2] CertificateSet OPTIONAL }
-- From CMS [2]
-- CertificateSet and CertificateChoices are included only
-- for illustrative purposes as they are imported from CMS [2].
CertificateSet ::= SET SIZE (1..MAX) OF CertificateChoices
CertificateChoices ::= CHOICE {
certificate Certificate,
-- See PKIX [5]
extendedCertificate [0] IMPLICIT ExtendedCertificate,
-- Obsolete
attrCert [1] IMPLICIT AttributeCertificate }
-- See ACPROF [6]
GLAdministration ::= INTEGER { GLAdministration ::= INTEGER {
unmanaged (0), unmanaged (0),
managed (1), managed (1),
closed (2) } closed (2) }
GLKeyAttributes ::= SEQUENCE { GLKeyAttributes ::= SEQUENCE {
rekeyControlledByGLO [0] BOOLEAN DEFAULT FALSE, rekeyControlledByGLO [0] BOOLEAN DEFAULT FALSE,
recipientsNotMutuallyAware [1] BOOLEAN DEFAULT TRUE, recipientsNotMutuallyAware [1] BOOLEAN DEFAULT TRUE,
duration [2] INTEGER DEAULT (0), duration [2] INTEGER DEFAULT 0,
generationCounter [3] INTEGER DEFAULT (2), generationCounter [3] INTEGER DEFAULT 2,
requestedAlgorithm [4] AlgorithmIdentifier requestedAlgorithm [4] AlgorithmIdentifier
DEFAULT (id-alg-CMS3DESwrap) } DEFAULT id-alg-CMS3DESwrap }
The fields in GLUseKEK have the following meaning: The fields in GLUseKEK have the following meaning:
- glInfo indicates the GLĘs name in glName and the GLĘs address in - glInfo indicates the GLĘs name in glName and the GLĘs address in
glAddress. In some instances the glName and glAddress may be the glAddress. In some instances the glName and glAddress may be the
same, but this is not always the case. Both the name and address same, but this is not always the case. Both the name and address
MUST be unique for a given GLA. MUST be unique for a given GLA.
- glOwnerInfo indicates the GL ownerĘs name in glOwnerName and the - glOwnerInfo indicates:
GL ownerĘs address in glOwnerAddress. One of the names in
glOwnerName MUST match one of the names in the certificate used - glOwnerName indicates the GL ownerĘs name.
to sign this SignedData.PKIData creating the GL (i.e., the
immediate signer). - glOwnerAddress indicates the GL ownerĘs address. One of the
names in glOwnerName MUST match one of the names in the
certificate used to sign this SignedData.PKIData creating the
GL (i.e., the immediate signer).
Turner 9
- certificates MAY be included. It contains the following three
fields:
- certificates.pKC includes the GLO's encryption certificate
that will be used to at least initially encrypt the shared
KEK for that member. If the message is generated by a GLO
and they are adding another GLO (i.e., the name in one of
the certificates used to sign this message does not match
the name in glOwnerName), the pKC for the other GLO MUST be
included. Else, the pKC MAY be included.
- certificates.aC MAY be included to convey any attribute
certificate associated with the GLOĘs encryption certificate
included in certificates.pKC.
- certificates.certificationPath MAY also be included to
convey the certification path corresponding to the GLO's
encryption and any non-GLO attribute certificates are placed
in attrCert. The certification path is optional because it
may already be included elsewhere in the message (e.g., in
the outer CMS layer).
- glAdministration indicates how the GL should be administered. - glAdministration indicates how the GL should be administered.
The default is for the list to be managed. Three values are The default is for the list to be managed. Three values are
supported for glAdministration: supported for glAdministration:
- Unmanaged - When the GLO sets glAdministration to unmanaged, - Unmanaged - When the GLO sets glAdministration to unmanaged,
they are allowing prospective members to request being added they are allowing prospective members to request being added
and deleted from the GL without GLO intervention. and deleted from the GL without GLO intervention.
- Managed - When the GLO sets glAdministration to managed, they - Managed - When the GLO sets glAdministration to managed, they
are allowing prospective members to request being added to and are allowing prospective members to request being added to and
deleted from the GL, but the request is redirected by the GLA deleted from the GL, but the request is redirected by the GLA
to GLO for review. The GLO makes the determination as to to GLO for review. The GLO makes the determination as to
whether to honor the request. whether to honor the request.
- Closed - When the GLO sets glAdministration to closed, they - Closed - When the GLO sets glAdministration to closed, they
are not allowing prospective members to request being added to are not allowing prospective members to request being added to
or deleted from the GL. The GLA will only accept glAddMember or deleted from the GL. The GLA will only accept glAddMember
and glDeleteMember requests from the GLO.
Turner 9
and glDeleteMember requests from the GLO. It is GL policy as
to whether to forward the request on to the GLO.
- glKeyAttributes indicates the attributes the GLO wants the GLA - glKeyAttributes indicates the attributes the GLO wants the GLA
to assign to the shared KEK. If this field is omitted, GL rekeys to assign to the shared KEK. If this field is omitted, GL rekeys
will be controlled by the GLA, the recipients are allowed to will be controlled by the GLA, the recipients are allowed to
know about one another, the algorithm will Triple-DES (see know about one another, the algorithm will Triple-DES (see
paragrpah 7), the shared KEK will be valid for a calendar month paragrpah 7), the shared KEK will be valid for a calendar month
(i.e., first of the month until the last day of the month), and (i.e., first of the month until the last day of the month), and
two shared KEKs will be distributed initially. The fields in two shared KEKs will be distributed initially. The fields in
glKeyAttributes have the following meaning: glKeyAttributes have the following meaning:
- rekeyControlledByGLO indicates whether the GL rekey messages - rekeyControlledByGLO indicates whether the GL rekey messages
will be generated by the GLO or by the GLA. The default is for will be generated by the GLO or by the GLA. The default is for
Turner 10
the GLA to control rekeys. If GL rekey is controlled by the the GLA to control rekeys. If GL rekey is controlled by the
GLA, the GL will continue to be rekeyed until the GLO deletes GLA, the GL will continue to be rekeyed until the GLO deletes
the GL or changes the GL rekey to be GLO controlled. the GL or changes the GL rekey to be GLO controlled.
- recipientsNotMutuallyAware indicates that the GLO wants the - recipientsNotMutuallyAware indicates that the GLO wants the
GLA to distribute the shared KEK individually for each of the GLA to distribute the shared KEK individually for each of the
GL members (i.e., a separate glKey message is sent to each GL members (i.e., a separate glKey message is sent to each
recipient). The default is for separate glKey message to not recipient). The default is for separate glKey message to not
be required. be required.
skipping to change at line 491 skipping to change at line 540
(0), the shared KEK will be valid for the number of days (0), the shared KEK will be valid for the number of days
indicated by the value. For example, if the value of duration indicated by the value. For example, if the value of duration
is seven (7) and the shared KEK is requested on Monday but not is seven (7) and the shared KEK is requested on Monday but not
generated until Tuesday (2359); the shared KEKs will be valid generated until Tuesday (2359); the shared KEKs will be valid
from Tuesday (2359) to Tuesday (2359). The exact time of the from Tuesday (2359) to Tuesday (2359). The exact time of the
day is determined when the key is generated. day is determined when the key is generated.
- generationCounter indicates the number of keys the GLO wants - generationCounter indicates the number of keys the GLO wants
the GLA to distribute. To ensure uninterrupted function of the the GLA to distribute. To ensure uninterrupted function of the
GL two (2) shared KEKs at a minimum MUST be initially GL two (2) shared KEKs at a minimum MUST be initially
Turner 10
distributed. The second shared KEK is distributed with the distributed. The second shared KEK is distributed with the
first shared KEK, so that when the first shared KEK is no first shared KEK, so that when the first shared KEK is no
longer valid the second key can be used. If the GLA controls longer valid the second key can be used. If the GLA controls
rekey then it also indicates the number of shared KEKs the GLO rekey then it also indicates the number of shared KEKs the GLO
wants outstanding at any one time. See sections 4.5 and 5 for wants outstanding at any one time. See sections 4.5 and 5 for
more on rekey. more on rekey.
- requestedAlgorithm indicates the algorithm and any parameters - requestedAlgorithm indicates the algorithm and any parameters
the GLO wants the GLA to use with the shared KEK. The the GLO wants the GLA to use with the shared KEK. The
parameters are conveyed via the SMIMECapabilities attribute parameters are conveyed via the SMIMECapabilities attribute
see MSG {x}. See section 7 for more on algorithms. see MSG [7]. See section 6 for more on algorithms.
Turner 11
3.1.2 Delete GL 3.1.2 Delete GL
GLOs use glDelete to request that a GL be deleted from the GLA. The GLOs use glDelete to request that a GL be deleted from the GLA. The
glDelete control attribute shall have the syntax GeneralName. The glDelete control attribute shall have the syntax GeneralName. The
name of the GL to be deleted is included in GeneralName. The name of the GL to be deleted is included in GeneralName. The
glDelete message MUST be signed by the GLO. glDelete message MUST be signed by the GLO.
3.1.3 Add GL Member 3.1.3 Add GL Member
GLOs use glAddMember to request addition of new members and GLOs use glAddMember to request addition of new members and
prospective GL members use glAddMember to request being added to the prospective GL members use glAddMember to request being added to the
GL. The glAddMember message must be signed by either the GLO or the GL. The glAddMember message MUST be signed by either the GLO or the
prospective GL member. The glAddMember control attribute shall have prospective GL member. The glAddMember control attribute shall have
the syntax GLAddMember: the syntax GLAddMember:
GLAddMember ::= SEQUENCE { GLAddMember ::= SEQUENCE {
glName GeneralName, glName GeneralName,
glMember GLMember } glMember GLMember }
GLMember ::= SEQUENCE { GLMember ::= SEQUENCE {
glMemberName GeneralName, glMemberName GeneralName,
glMemberAddress GeneralName OPTIONAL, glMemberAddress GeneralName OPTIONAL,
certificates Certificates OPTIONAL } certificates Certificates OPTIONAL }
Certificates ::= SEQUENCE { Certificates ::= SEQUENCE {
pKC Certificate OPTIONAL, pKC [0] Certificate OPTIONAL,
-- See X.509 -- See PKIX [5]
aC SEQUENCE SIZE (1.. MAX) OF aC [1] SEQUENCE SIZE (1.. MAX) OF
AttributeCertificate OPTIONAL, AttributeCertificate OPTIONAL,
-- See X.509 -- See ACPROF [6]
certificationPath CertificateSet OPTIONAL } certificationPath [2] CertificateSet OPTIONAL }
-- From CMS [2] -- From CMS [2]
-- CertificateSet and CertificateChoices are included only
-- for illustrative purposes as they are imported from CMS [2].
CertificateSet ::= SET SIZE (1..MAX) OF CertificateChoices CertificateSet ::= SET SIZE (1..MAX) OF CertificateChoices
Turner 11
CertificateChoices ::= CHOICE { CertificateChoices ::= CHOICE {
certificate Certificate, certificate Certificate,
-- See X.509 -- See X.509
extendedCertificate [0] IMPLICIT ExtendedCertificate, extendedCertificate [0] IMPLICIT ExtendedCertificate,
-- Obsolete -- Obsolete
attrCert [1] IMPLICIT AttributeCertificate } attrCert [1] IMPLICIT AttributeCertificate }
-- See X.509 and X9.57 -- See X.509 and X9.57
The fields in GLAddMembers have the following meaning: The fields in GLAddMembers have the following meaning:
- glName indicates the name of the GL to which the member should - glName indicates the name of the GL to which the member should
be added. be added.
Turner 12
- glMember indicates the particulars for the GL member. Both of - glMember indicates the particulars for the GL member. Both of
the following fields must be unique for a given GL: the following fields must be unique for a given GL:
- glMemberName indicates the name of the GL member. - glMemberName indicates the name of the GL member.
- glMemberAddress indicates the GL memberĘs address. It MUST be - glMemberAddress indicates the GL memberĘs address. It MUST be
included. included.
Note: In some instances the glMemberName and glMemberAddress Note: In some instances the glMemberName and glMemberAddress
may be the same, but this is not always the case. may be the same, but this is not always the case.
skipping to change at line 589 skipping to change at line 641
convey the certification path corresponding to the member's convey the certification path corresponding to the member's
encryption and any non-member attribute certificates are encryption and any non-member attribute certificates are
placed in attrCert. The certification path is optional placed in attrCert. The certification path is optional
because it may already be included elsewhere in the message because it may already be included elsewhere in the message
(e.g., in the outer CMS layer). (e.g., in the outer CMS layer).
3.1.4 Delete GL Member 3.1.4 Delete GL Member
GLOs use glDeleteMember to request deletion of GL members and GL GLOs use glDeleteMember to request deletion of GL members and GL
members use glDeleteMember to request being removed from the GL. The members use glDeleteMember to request being removed from the GL. The
glDeleteMember message must be signed by either the GLO or the glDeleteMember message MUST be signed by either the GLO or the
Turner 12
prospective GL member. The glDeleteMember control attribute shall prospective GL member. The glDeleteMember control attribute shall
have the syntax GLDeleteMember: have the syntax GLDeleteMember:
GLDeleteMember ::= SEQUENCE { GLDeleteMember ::= SEQUENCE {
glName GeneralName, glName GeneralName,
glMemberToDelete GeneralName } glMemberToDelete GeneralName }
The fields in GLDeleteMembers have the following meaning: The fields in GLDeleteMembers have the following meaning:
- glName indicates the name of the GL from which the member should - glName indicates the name of the GL from which the member should
be removed. be removed.
- glMemberToDelete indicates the name of the member to be deleted. - glMemberToDelete indicates the name of the member to be deleted.
Turner 13
3.1.5 Rekey GL 3.1.5 Rekey GL
GLOs use the glRekey to request a GL rekey. The glRekey message MUST GLOs use the glRekey to request a GL rekey. The glRekey message MUST
be signed by the GLO. The glRekey control attribute shall have the be signed by the GLO. The glRekey control attribute shall have the
syntax GLRekey: syntax GLRekey:
GLRekey ::= SEQUENCE { GLRekey ::= SEQUENCE {
glName GeneralName, glName GeneralName,
glAdministration GLAdministration OPTIONAL, glAdministration GLAdministration OPTIONAL,
glNewKeyAttributes GLNewKeyAttributes OPTIONAL, glNewKeyAttributes GLNewKeyAttributes OPTIONAL,
skipping to change at line 641 skipping to change at line 693
This field is only included if there is a change from the This field is only included if there is a change from the
previously registered administered. previously registered administered.
- glNewKeyAttributes indicates whether the rekey of the GLO is - glNewKeyAttributes indicates whether the rekey of the GLO is
controlled by the GLA or GL, what algorithm and parameters the controlled by the GLA or GL, what algorithm and parameters the
GLO wishes to use, the duration of the key, and how many GLO wishes to use, the duration of the key, and how many
outstanding keys should be issued. The field is only included if outstanding keys should be issued. The field is only included if
there is a change from the previously registered there is a change from the previously registered
glKeyAttributes. glKeyAttributes.
Turner 13
- glRekeyAllGLKeys indicates whether the GLO wants all of the - glRekeyAllGLKeys indicates whether the GLO wants all of the
outstanding GLĘs shared KEKs rekeyed. If it is set to TRUE then outstanding GLĘs shared KEKs rekeyed. If it is set to TRUE then
all outstanding KEKs MUST be issued. If it is set to FALSE then all outstanding KEKs MUST be issued. If it is set to FALSE then
all outstanding KEKs need not be resissued. all outstanding KEKs need not be resissued.
Turner 14
3.1.6 Add GL Owner 3.1.6 Add GL Owner
GLOs use the glAddOwner to request that a new GLO be allowed to GLOs use the glAddOwner to request that a new GLO be allowed to
administer the GL. The glAddOwner message MUST be signed a administer the GL. The glAddOwner message MUST be signed a
registered GLO. The glAddOwner control attribute shall have the registered GLO. The glAddOwner control attribute shall have the
syntax GLOwnerAdministration: syntax GLOwnerAdministration:
GLOwnerAdministration ::= SEQUENCE { GLOwnerAdministration ::= SEQUENCE {
glName GeneralName, glName GeneralName,
glOwnerInfo GLOwnerInfo } glOwnerInfo GLOwnerInfo }
The fields in GLAddOwners have the following meaning: The fields in GLAddOwners have the following meaning:
- glName indicates the name of the GL to which the new GLO should - glName indicates the name of the GL to which the new GLO should
be associated. be associated.
- glOwnerInfo indicates the name and address of the new GLO. - glOwnerInfo indicates the name, address, and certificates of the
new GLO. As this message includes names of new GLOs, the
certificates.pKC MUST be included and it MUST include the new
GLOĘs encryption certificate.
3.1.7 Remove GL Owner 3.1.7 Remove GL Owner
GLOs use the glRemoveOwner to request that a GLO be disassociated GLOs use the glRemoveOwner to request that a GLO be disassociated
with the GL. The glRemoveOwner message MUST be signed by a with the GL. The glRemoveOwner message MUST be signed by a
registered GLO. The glRemoveOwner control attribute shall have the registered GLO. The glRemoveOwner control attribute shall have the
syntax GLOwnerAdministration: syntax GLOwnerAdministration:
GLOwnerAdministration ::= SEQUENCE { GLOwnerAdministration ::= SEQUENCE {
glName GeneralName, glName GeneralName,
glOwnerInfo GLOwnerInfo } glOwnerInfo GLOwnerInfo }
The fields in GLRemoveOwners have the following meaning: The fields in GLRemoveOwners have the following meaning:
- glName indicates the name of the GL to which the GLO should be - glName indicates the name of the GL to which the GLO should be
disassociated. disassociated.
- glOwnerInfo indicates the name and address of the GLO to be - glOwnerInfo indicates the name and address of the GLO to be
removed. removed. The certificates field SHOULD be omitted, as it will be
ignored.
3.1.8 GL Key Compromise 3.1.8 GL Key Compromise
GL members and GLOs use glkCompromise to indicate that the shared GL members and GLOs use glkCompromise to indicate that the shared
KEK possessed has been compromised. The glKeyCompromise control KEK possessed has been compromised. The glKeyCompromise control
attribute shall have the syntax GeneralName. The name of the GL to attribute shall have the syntax GeneralName. The name of the GL to
which the compromised key is associated with is included in which the compromised key is associated with is included in
GeneralName. This message is always redirected by the GLA to the GLO GeneralName. This message is always redirected by the GLA to the GLO
Turner 14
for further action. The glkCompromise MUST NOT be included in an for further action. The glkCompromise MUST NOT be included in an
EnvelopedData generated with the compromised shared KEK. EnvelopedData generated with the compromised shared KEK.
Turner 15
3.1.9 GL Key Refresh 3.1.9 GL Key Refresh
GL members use the glkRefresh to request that the shared KEK be GL members use the glkRefresh to request that the shared KEK be
redistributed to them. The glkRefresh control attribute shall have redistributed to them. The glkRefresh control attribute shall have
the syntax GLKRefresh. the syntax GLKRefresh.
GLKRefresh ::= { GLKRefresh ::= SEQUENCE {
glName GeneralName, glName GeneralName,
dates SEQUENCE (1..MAX) OF Date } dates SEQUENCE SIZE (1..MAX) OF Date }
Date ::= { Date ::= SEQUENCE {
start GeneralizedTime, start GeneralizedTime,
end GeneralizedTime OPTIONAL } end GeneralizedTime OPTIONAL }
The fields in GLKRefresh have the following meaning: The fields in GLKRefresh have the following meaning:
- glName indicates the name of the GL for which the GL member - glName indicates the name of the GL for which the GL member
wants shared KEKs. wants shared KEKs.
- dates indicates a date range for keys the GL member wants. The - dates indicates a date range for keys the GL member wants. The
start field indicates the first date the GL member wants and the end start field indicates the first date the GL member wants and the
field indicates the last date. The end date MAY be omitted to end field indicates the last date. The end date MAY be omitted
indicate the GL member wants all keys from the specified start date to indicate the GL member wants all keys from the specified
to the current date. It should be noted that a procedural mechanism start date to the current date. It should be noted that a
will be needed to restrict users from accessing messages that they procedural mechanism will be needed to restrict users from
are not allowed to access. accessing messages that they are not allowed to access.
3.1.10 GL Success Information
The GLA uses glSuccessInfo to indicate a successful result of an
administrative message. A separate glSuccessInfo is returned for
each action (e.g., if there are four successful glAddMember requests
then four glSuccessInfo responses are generated). The glSuccessInfo
message MUST be signed by the GLA. The glSucessInfo control
attribute shall have the syntax GLSucessInfo:
GLSuccessInfo ::= SEQUENCE {
glInfo GLInfo,
glIdentifier GLIdentifier,
action Action }
Action ::= SEQUENCE {
actionCode ActionCode,
glMemberName [0] GeneralName OPTIONAL,
glOwnerName [1] GeneralName OPTIONAL }
Turner 15
ActionCode ::= INTEGER {
assignedKEK (0),
deletedGL (1),
addedMember (2),
deletedMember (3),
rekeyedGL (4),
addedGLO (5),
removedGLO (6) }
The fields in GLSuccessInfo have the following meaning:
- glInfo indicates the GLĘs name in glName and the GLĘs address in
glAddress.
- glIdentifier identifies GLĘs unique shared KEK.
- action indicates the successfully performed action.
action.actionCode indicates whether the shared KEK was assigned
to the GL, whether the GL was deleted, whether a member was
added to a GL, whether a member was deleted from a GL, whether
the GL was rekeyed, whether a new GLO was added, and whether a
GLO was removed. If members were added to a GL or deleted from a
GL the members MUST be indicated in glMemberName and glOwnerName
MUST be omitted. If a GLO was added to a GL or deleted from a
GL, the GLO MUST be indicated in glOwnerName and glMemberName
MUST be omitted. If a shared KEK was assigned to a GL or a GL
was deleted both glOwnerName and glMemberName MUST be omitted.
3.1.11 GL Fail Information
The GLA uses glFailInfo to indicate that there was a problem
performing a requested action. A separate glFailInfo is returned for
each action (e.g., if there are four denied glAddMember requests
then four glFailInfo responses are generated). The glFailInfo
message MUST be signed by the GLA. The glFailInfo control attribute
shall have the syntax GLFailInfo:
GLFailInfo ::= SEQUENCE {
glName GeneralName,
error Error }
Error ::= SEQUENCE {
errorCode ErrorCode,
glMemberName [0] GeneralName OPTIONAL,
glOwnerName [1] GeneralName OPTIONAL }
Turner 16
ErrorCode ::= INTEGER {
unspecified (0),
closedGL (1)
unsupportedDuration (2)
noGLACertificate (3),
invalidCert (4),
unsupportedAlgorithm (5),
noGLONameMatch (6),
invalidGLName (7),
nameAlreadyInUse (8),
noSpam (9),
deniedAccess (10),
alreadyAMember (11),
notAMember (12),
alreadyAnOwner (13)
notAnOwner (14) }
The fields in GLFailInfo have the following meaning:
- glName indicates the name of the GL to which the error
corresponds.
- error indicates the reason why the GLA was unable to perform the
request. It also indicates the GL member or GLO to which the
error corresponds. If members were not added to a GL or deleted
from a GL the members MUST be indicated in glMemberName. If a
GLO was not added to a GL or deleted from a GL, the GLO MUST be
indicated in glOwnerName. The errors are returned under the
following conditions:
- unspecified indicates that the GLA is unable or unwilling to
perform the requested action and does not want to indicate
why.
- closedGL indicates that members can only be added or deleted
by the GLO.
- unsupportedDuration indicates the GLA does not support
generating keys that are valid for the requested duration.
- noGLACertificate indicates that the GLA does not have a valid
certificate.
- invalidCert indicates the member's encryption certificate was
not verifiable (i.e., signature did not validate,
certificateĘs serial number present on a CRL, etc.).
- unsupportedAlgorithm indicates the GLA does not support the
requested algorithm.
Turner 17
- noGLONameMatch indicates that one of the names in the
certificate used to sign a request does not match the name of
a registered GLO.
- invalidGLName indicates the GLA does not support the glName
present in the request.
- nameAlreadyInUse indicates the glName is already assigned on
the GLA.
- noSpam indicates the prospective GL member did not sign the
request (i.e., if the name in glMember.glMemberName does not
match one of the names in the certificate used to sign the
request).
- alreadyAMember indicates the prospective GL member is already
a GL member.
- notAMember indicates the prospective non-GL member is not a GL
member.
- alreadyAnOwner indicates the prospective GLO is already a GLO. 3.1.10 GLA Query Request and Response
- notAnOwner indicates the prospective non-GLO is not a GLO. There are situations where GLOs and GL members may need to determine
some information from the GLA about the GL. GLOs and GL members use
the glaQueryRequest, defined in paragraph 3.1.10.1, to request
information and GLAs use the glaQueryResponse, defined in paragraph
3.1.10.2, to return the requested information. Paragraph 3.1.10.3
includes one request and response type and value; others may be
defined in additional documents.
3.1.12 GLA Query Request 3.1.10.1 GLA Query Request
GLOs and GL members use the glaQueryRequest to ascertain information GLOs and GL members use the glaQueryRequest to ascertain information
about the GLA. The glaQueryRequest control attribute shall have the about the GLA. The glaQueryRequest control attribute shall have the
syntax GLAQueryRequest: syntax GLAQueryRequest:
GLAQueryRequest ::= SEQUENCE { GLAQueryRequest ::= SEQUENCE {
glaRequestType OBJECT IDENTIFIER, glaRequestType OBJECT IDENTIFIER,
glaRequestValue ANY DEFINED BY glaResponseType } glaRequestValue ANY DEFINED BY glaRequestType }
One request type is defined herein to support the GLO in determining
the algorithms supported by the GLA:
id-rt-algorithmSupported { id-tbd }
There is no value defined for id-rt-algorithmSupported. Including Turner 16
the id-rt-algorithmSupport indicates that the GLO wishes to know the
algorithms that the GLA supports.
3.1.13 GLA Query Response 3.1.10.2 GLA Query Response
GLAĘs return the glaQueryResponse after receiving a GLAQueryRequest. GLAĘs return the glaQueryResponse after receiving a GLAQueryRequest.
The glaQueryResponse MUST be signed by a GLA. The glaQueryResponse The glaQueryResponse MUST be signed by a GLA. The glaQueryResponse
control attribute shall have the syntax GLAQueryResponse: control attribute shall have the syntax GLAQueryResponse:
Turner 18
GLAQueryResponse ::= SEQUENCE { GLAQueryResponse ::= SEQUENCE {
glaResponseType OBJECT IDENTIFIER, glaResponseType OBJECT IDENTIFIER,
glaResponseValue ANY DEFINED BY glaResponseType } glaResponseValue ANY DEFINED BY glaResponseType }
One response type is defined herein for the GLA to indicate the 3.1.10.3 Request and Response Types
algorithms it supports:
smimeCapabilities OBJECT IDENTIFIER ::= Request and Responses are reqistered as a pair under the following
{iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9) 15} object identifier arc:
-- Identifies the algorithms supported by the GLA (see MsgSpec [5])
3.1.14 Provide Cert id-cmc-glaRR OBJECT IDENTIFIER ::= { id-cmc 99 }
This document defines one request/response pair for GL members and
GLOĘs to query the GLA as to which algorithm it supports. The
following object identifier is included in the glaQueryType field:
id-cmc-gla-skdAlgRequest OBJECT IDENTIFIER ::={ id-cmc-glaRR 1 }
There is no glaQueryValue for thie query.
If the GLA supports GLAQueryRequest and GLAQueryResponse messages,
the GLA may return the following oid in the glaQueryType field:
id-cmc-gla-skdAlgResponse OBJECT IDENTIFIER ::= { id-cmc-glaRR 2 }
The glaQueryValue has the form of the smimeCapabilities attributes
as defined in MsgSpec [7].
3.1.12 Provide Cert
GLAs and GLOs use glProvideCert to request that a GL member provide GLAs and GLOs use glProvideCert to request that a GL member provide
an updated or new encryption certificate. The glProvideCert message an updated or new encryption certificate. The glProvideCert message
MUST be signed by either GLA or GLO. If the GL memberĘs PKC has been MUST be signed by either GLA or GLO. If the GL memberĘs PKC has been
revoked, the GLO or GLA MUST NOT use it to generate the revoked, the GLO or GLA MUST NOT use it to generate the
EnvelopedData that encapsulates the glProvideCert request. The EnvelopedData that encapsulates the glProvideCert request. The
glProvideCert control attribute shall have the syntax GLManageCert: glProvideCert control attribute shall have the syntax GLManageCert:
GLManageCert ::= SEQUENCE { GLManageCert ::= SEQUENCE {
glName GeneralName, glName GeneralName,
glMember GLMember } glMember GLMember }
Turner 17
The fields in GLManageCert have the following meaning: The fields in GLManageCert have the following meaning:
- glName indicates the name of the GL to which the GL memberĘs new - glName indicates the name of the GL to which the GL memberĘs new
certificate should be associated. certificate should be associated.
- glMember indicates particulars for the GL member: - glMember indicates particulars for the GL member:
- glMemberName indicates the GL memberĘs name. - glMemberName indicates the GL memberĘs name.
- glMemberAddress indicates the GL memberĘs address. It MAY be - glMemberAddress indicates the GL memberĘs address. It MAY be
omitted. omitted.
- certificates SHOULD be omitted. - certificates SHOULD be omitted.
Turner 19 3.1.13 Update Cert
3.1.15 Update Cert
GL members and GLOs use glUpdateCert to provide a new certificate GL members and GLOs use glUpdateCert to provide a new certificate
for the GL. GL members may generate a glUpdateCert unsolicited or as for the GL. GL members may generate a glUpdateCert unsolicited or as
a result of a glProvideCert message. GL members MUST sign the a result of a glProvideCert message. GL members MUST sign the
glUpdateCert. If the GL memberĘs encryption certificate has been glUpdateCert. If the GL memberĘs encryption certificate has been
revoked, the GL member MUST NOT use it to generate the EnvelopedData revoked, the GL member MUST NOT use it to generate the EnvelopedData
that encapsulates the glUpdateCert request or response. The that encapsulates the glUpdateCert request or response. The
glUpdateCert control attribute shall have the syntax GLManageCert: glUpdateCert control attribute shall have the syntax GLManageCert:
GLManageCert ::= SEQUENCE { GLManageCert ::= SEQUENCE {
skipping to change at line 963 skipping to change at line 894
- glMemberName indicates the GL memberĘs name - glMemberName indicates the GL memberĘs name
- glMemberAddress indicates the GL memberĘs address. It MAY be - glMemberAddress indicates the GL memberĘs address. It MAY be
omitted. omitted.
- certificates MAY be omitted if the GLManageCert message is - certificates MAY be omitted if the GLManageCert message is
sent to request the GL members certificate; else it MUST be sent to request the GL members certificate; else it MUST be
included. It includes the following three fields: included. It includes the following three fields:
- certificates.pKC includes the member's encryption - certificates.pKC includes the member's encryption
certificate that will be used to encrypt the shared KEK for that certificate that will be used to encrypt the shared KEK for
member. that member.
Turner 18
- certificates.aC MAY be included to convey any attribute - certificates.aC MAY be included to convey any attribute
certificate associated with the memberĘs encryption certificate. certificate associated with the memberĘs encryption
certificate.
- certificates.certificationPath MAY also be included to - certificates.certificationPath MAY also be included to
convey the certification path corresponding to the member's convey the certification path corresponding to the member's
encryption and attribute certificates. The certification path is encryption and attribute certificates. The certification
optional because it may already be included elsewhere in the path is optional because it may already be included
message (e.g., in the outer CMS layer). elsewhere in the message (e.g., in the outer CMS layer).
Turner 20
3.1.16 GL Key 3.1.14 GL Key
The GLA uses glKey to distribute the shared KEK. The glKey message The GLA uses glKey to distribute the shared KEK. The glKey message
MUST be signed by the GLA. The glKey control attribute shall have MUST be signed by the GLA. The glKey control attribute shall have
the syntax GLKey: the syntax GLKey:
GLKey ::= SEQUENCE { GLKey ::= SEQUENCE {
glName GeneralName, glName GeneralName,
glIdentifier OCTET STRING, glIdentifier KEKIdentifier, -- See CMS [2]
glkWrapped RecipientInfos, -- See CMS [2] glkWrapped RecipientInfos, -- See CMS [2]
glkAlgorithm AlgorithmIdentifier, glkAlgorithm AlgorithmIdentifier,
glkNotBefore GeneralizedTime, glkNotBefore GeneralizedTime,
glkNotAfter GeneralizedTime } glkNotAfter GeneralizedTime }
-- KEKIdentifier is included only for illustrative purposes as
-- it is imported from CMS [2].
KEKIdentifier ::= SEQUENCE {
keyIdentifier OCTET STRING,
date GeneralizedTime OPTIONAL,
other OtherKeyAttribute OPTIONAL }
The fields in GLKey have the following meaning: The fields in GLKey have the following meaning:
- glName is the name of the GL. - glName is the name of the GL.
- glIdentifier is the key identifier of the shared KEK. When GL - glIdentifier is the key identifier of the shared KEK. See
members use the shared KEK to encrypt data objects for other GL paragraph 6.2.3 of CMS [2] for a description of the subfields.
members, they place the glIdentifier in
RecipientInfo.kekri.kekid.keyIdentifier field. There are many
ways to do this here are two options are provided to generate a
unique key identifier. The first choice concatenates the GLAĘs
subject name from the digital signature certificate used to sign
the glKey message and counter. The second choice concatenates
the GLAĘs subjectKeyIdentifier, from the digital signature
certificate used to sign the glKey message, and a counter.
- glkWrapped is the GL's wrapped shared KEK. The RecipientInfos - glkWrapped is the GL's wrapped shared KEK. The RecipientInfos
shall be generated as specified in section 6.2 of CMS [2]. The shall be generated as specified in section 6.2 of CMS [2]. The
ktri RecipientInfo choice MUST be supported. The key in the ktri RecipientInfo choice MUST be supported. The key in the
EncryptedKey field (i.e., the distributed shared KEK) MUST be EncryptedKey field (i.e., the distributed shared KEK) MUST be
generated according to the section concerning random number generated according to the section concerning random number
generation in the security considerations of CMS [2]. generation in the security considerations of CMS [2].
- glkAlgorithm identifies the algorithm the shared KEK is used - glkAlgorithm identifies the algorithm the shared KEK is used
with. The parameters are conveyed via the SMIMECapabilities with. Since no encrypted data content is being conveyed at this
attribute see MSG {x}. point, the parameters encoded with the algorithm should be the
Turner 19
structure defined for SMIMECapabilities rather than encrypted
content.
- glkNotBefore indicates the date at which the shared KEK is - glkNotBefore indicates the date at which the shared KEK is
considered valid. GeneralizedTime values MUST be expressed UTC considered valid. GeneralizedTime values MUST be expressed UTC
(Zulu) and MUST include seconds (i.e., times are (Zulu) and MUST include seconds (i.e., times are
YYYYMMDDHHMMSSZ), even where the number of seconds is zero. YYYYMMDDHHMMSSZ), even where the number of seconds is zero.
GeneralizedTime values MUST NOT include fractional seconds. GeneralizedTime values MUST NOT include fractional seconds.
- glkNotAfter indicates the date after which the shared KEK is - glkNotAfter indicates the date after which the shared KEK is
considered invalid. GeneralizedTime values MUST be expressed UTC considered invalid. GeneralizedTime values MUST be expressed UTC
(Zulu) and MUST include seconds (i.e., times are (Zulu) and MUST include seconds (i.e., times are
YYYYMMDDHHMMSSZ), even where the number of seconds is zero. YYYYMMDDHHMMSSZ), even where the number of seconds is zero.
GeneralizedTime values MUST NOT include fractional seconds. GeneralizedTime values MUST NOT include fractional seconds.
Turner 21
If the glKey message is in response to a glUseKEK message: If the glKey message is in response to a glUseKEK message:
- The GLA MUST generate separate glKey messages for each recipient - The GLA MUST generate separate glKey messages for each recipient
if glUseKEK.glKeyAttributes.recipientsNotMutuallyAware is set to if glUseKEK.glKeyAttributes.recipientsNotMutuallyAware is set to
FALSE. For each recipient you want to generate a message that FALSE. For each recipient you want to generate a message that
contains that recipientĘs key (i.e., one message with one contains that recipientĘs key (i.e., one message with one
attribute). attribute).
- The GLA MUST generate X number of glKey messages, where X is the - The GLA MUST generate X number of glKey messages, where X is the
value in glUseKEK.glKeyAttributes.generationCounter. value in glUseKEK.glKeyAttributes.generationCounter.
skipping to change at line 1066 skipping to change at line 1000
- The GLA MUST generate separate glKey messages for each recipient - The GLA MUST generate separate glKey messages for each recipient
if glUseKEK.glNewKeyAttributes.recipientsNotMutuallyAware that if glUseKEK.glNewKeyAttributes.recipientsNotMutuallyAware that
set up the GL was set to FALSE. set up the GL was set to FALSE.
- The GLA MAY generate X glKey messages prior to the duration on - The GLA MAY generate X glKey messages prior to the duration on
the last outstanding shared KEK expiring, where X is the the last outstanding shared KEK expiring, where X is the
generationCounter minus one (1). Other distribution mechanisms generationCounter minus one (1). Other distribution mechanisms
may also be supported to support this functionality. may also be supported to support this functionality.
Turner 20
3.2 Use of CMC, CMS, and PKIX 3.2 Use of CMC, CMS, and PKIX
The following sections outline the use of CMC, CMS, and PKIX. The following sections outline the use of CMC, CMS, and PKIX.
3.2.1 Protection Layers 3.2.1 Protection Layers
The following sections outline the protection required for the The following sections outline the protection required for the
control attributes defined herein. control attributes defined herein.
Turner 22
3.2.1.1 Minimum Protection 3.2.1.1 Minimum Protection
At a minimum, a SignedData MUST protect each request and response At a minimum, a SignedData MUST protect each request and response
encapsulated in PKIData and PKIResponse. The following is a encapsulated in PKIData and PKIResponse. The following is a
depiction of the minimum wrappings: depiction of the minimum wrappings:
Minimum Protection Minimum Protection
------------------ ------------------
SignedData SignedData
PKIData or PKIResponse PKIData or PKIResponse
skipping to change at line 1110 skipping to change at line 1044
Confidentiality Protection A&I of Confidentiality Protection Confidentiality Protection A&I of Confidentiality Protection
-------------------------- --------------------------------- -------------------------- ---------------------------------
EnvelopedData SignedData EnvelopedData SignedData
SignedData EnvelopedData SignedData EnvelopedData
PKIData or PKIResponse SignedData PKIData or PKIResponse SignedData
controlSequence PKIData or PKIResponse controlSequence PKIData or PKIResponse
controlSequence controlSequence
If an incoming message was encrypted, the confidentiality of the If an incoming message was encrypted, the confidentiality of the
message MUST be preserved. All EnvelopedData objects MUST be message MUST be preserved. All EnvelopedData objects MUST be
processed as specified in CMS [2]. processed as specified in CMS [2]. If a SignedData is added over an
EnvelopedData, a ContentHints attribute SHOULD be added. See
paragraph 2.9 of Extended Security Services for S/MIME [8].
Turner 21
If the GLO or GL member applies confidentiality to a request, the If the GLO or GL member applies confidentiality to a request, the
EnvelopedData MUST be encrypted for the GLA. If the GLA is to EnvelopedData MUST be encrypted for the GLA. If the GLA is to
forward the GL member request to the GLO, the GLA decrypts the forward the GL member request to the GLO, the GLA decrypts the
EnvelopedData, strips the confidentiality layer off, and applies its EnvelopedData, strips the confidentiality layer off, and applies its
own confidentiality layer for the GLO. own confidentiality layer for the GLO.
3.2.2 Combining Requests and Responses 3.2.2 Combining Requests and Responses
Multiple requests and response corresponding to a GL MAY be included Multiple requests and response corresponding to a GL MAY be included
in one PKIData.controlSequence or PKIResponse.controlSequence. in one PKIData.controlSequence or PKIResponse.controlSequence.
Requests and responses for multiple GLs MAY be combined in one Requests and responses for multiple GLs MAY be combined in one
PKIData or PKIResponse by using PKIData.cmsSequence and PKIData or PKIResponse by using PKIData.cmsSequence and
PKIResponse.cmsSequence. A separate cmsSequence MUST be used for PKIResponse.cmsSequence. A separate cmsSequence MUST be used for
Turner 23
different GLs (i.e., requests corresponding to two different GLs are different GLs (i.e., requests corresponding to two different GLs are
included in different cmsSequences). The following is a diagram included in different cmsSequences). The following is a diagram
depicting multiple requests and responses combined in one PKIData depicting multiple requests and responses combined in one PKIData
and PKIResponse: and PKIResponse:
Multiple Request and Response Multiple Request and Response
Request Response Request Response
------- -------- ------- --------
SignedData SignedData SignedData SignedData
PKIData PKIResponse PKIData PKIResponse
skipping to change at line 1149 skipping to change at line 1084
PKIData PKIResponse PKIData PKIResponse
controlSequence controlSequence controlSequence controlSequence
One or more requests One or more responses One or more requests One or more responses
corresponding to one GL. corresponding to one GL. corresponding to one GL. corresponding to one GL.
SignedData SignedData SignedData SignedData
PKIData PKIResponse PKIData PKIResponse
controlSequence controlSequence controlSequence controlSequence
One or more requests One or more responses One or more requests One or more responses
corresponding to another GL. corresponding to another GL. corresponding to another GL. corresponding to another GL.
Turner 22
When applying confidentiality to multiple requests and responses, When applying confidentiality to multiple requests and responses,
all of the requests/response MAY be included in one EnvelopedData. all of the requests/response MAY be included in one EnvelopedData.
The following is a depiction: The following is a depiction:
Confidentiality of Multiple Requests and Responses Confidentiality of Multiple Requests and Responses
Wrapped Together Wrapped Together
---------------- ----------------
EnvelopedData EnvelopedData
SignedData SignedData
PKIData PKIData
cmsSequence cmsSequence
SignedData SignedData
PKIResponse PKIResponse
controlSequence controlSequence
Zero or more requests One or more requests
corresponding to one GL. corresponding to one GL.
SignedData SignedData
PKIData PKIData
controlSequence controlSequence
Zero or more requests One or more requests
corresponding to one GL. corresponding to one GL.
Turner 24
Certain combinations of requests in one PKIData.controlSequence and Certain combinations of requests in one PKIData.controlSequence and
one PKIResponse.controlSequence are not allowed. The invalid one PKIResponse.controlSequence are not allowed. The invalid
combinations listed here MUST NOT be generated: combinations listed here MUST NOT be generated:
Invalid Combinations Invalid Combinations
--------------------------- ---------------------------
glUseKEK & glDeleteMember glUseKEK & glDeleteMember
glUseKEK & glRekey glUseKEK & glRekey
glUseKEK & glDelete glUseKEK & glDelete
glDelete & glAddMember glDelete & glAddMember
skipping to change at line 1196 skipping to change at line 1131
To avoid unnecessary errors, certain requests and responses should To avoid unnecessary errors, certain requests and responses should
be processed prior to others. The following is the priority of be processed prior to others. The following is the priority of
message processing, if not listed it is an implementation decision message processing, if not listed it is an implementation decision
as to which to process first: glUseKEK before glAddMember, glRekey as to which to process first: glUseKEK before glAddMember, glRekey
before glAddMember, and glDeleteMember before glRekey. It should be before glAddMember, and glDeleteMember before glRekey. It should be
noted that there is a priority but it does not imply an order. noted that there is a priority but it does not imply an order.
3.2.3 GLA Generated Messages 3.2.3 GLA Generated Messages
When the GLA generates a glSuccessInfo, it generates one for each When the GLA generates a success or fail message, it generates one
request. action.actionCode values of assignedKEK, deletedGL, for each request. Likewise, when the GLA generates a failure message
rekeyedGL, addedGLO, and deletedGLO are not returned to GL members. it generates one for each request. SKDFailInfo values of
Likewise, when the GLA generates glFailInfo it generates one each
request. error values of unsupportedDuration, Turner 23
unsupportedDeliveryMethod, unsupportedAlgorithm, noGLONameMatch, unsupportedDuration, unsupportedDeliveryMethod,
nameAlreadyInUse, alreadyAnOwner, notAnOwner are not returned to GL unsupportedAlgorithm, noGLONameMatch, nameAlreadyInUse,
members. alreadyAnOwner, notAnOwner are not returned to GL members.
If GLKeyAttributes.recipientsNotMutuallyAware is set to FALSE, a If GLKeyAttributes.recipientsNotMutuallyAware is set to FALSE, a
separate PKIResponse.glSucessInfo, PKIResponse.glFailInfo, and separate PKIResponse.cMCStatusInfoEx, PKIResponse.cMCStatusInfoEx,
PKIData.glKey MUST be generated for each recipient. It is valid to and PKIData.glKey MUST be generated for each recipient. It is valid
send one message with multiple attributes to the same recipient. to send one message with multiple attributes to the same recipient.
If the GL has multiple GLOs, the GLA MUST send the glSuccessInfo and If the GL has multiple GLOs, the GLA MUST send cMCStatusInfoEx
glFailInfo messages to the requesting GLO. The mechanism to messages to the requesting GLO. The mechanism to determine which GLO
determine which GLO made the request is beyond the scope of this made the request is beyond the scope of this document.
document.
Turner 25
If a GL is managed and the GLA receives a glAddMember, If a GL is managed and the GLA receives a glAddMember,
glDeleteMember, or glkCompromise message, the GLA redirects the glDeleteMember, or glkCompromise message, the GLA redirects the
request to the GLO for review. An additional, SignedData MUST be request to the GLO for review. An additional, SignedData MUST be
applied to the redirected request as follows: applied to the redirected request as follows:
GLA Forwarded Requests GLA Forwarded Requests
---------------------- ----------------------
SignedData SignedData
PKIData PKIData
cmsSequence cmsSequence
PKIData PKIData
controlSequence controlSequence
3.2.4 CMC Control Attributes 3.2.4 CMC Control Attributes
Certain control attributes defined in CMC [3] are allowed; they are Certain control attributes defined in CMC [3] are allowed; they are
as follows: cMCStatusInfo, transactionId, senderNonce, as follows: cMCStatusInfoEx transactionId, senderNonce,
recipientNonce, and queryPending. recipientNonce, and queryPending.
cMCStatusInfo is used by GLAs to indicate to GLOs and GL members 3.2.4.1 Using cMCStatusInfoEx
whether a request was or was not successfully completed. If the
request was successful, the GLA returns a cMCStatusInfo response cMCStatusInfoEx is used by GLAs to indicate to GLOs and GL members
with cMCStatus.success and optionally other pertinent information in that a request was unsuccessful. Two classes of failure codes are
stutsString. If the response was not successful, the GLA returns a used within this document. Errors from the CMCFailInfo list, found
cMCStatusInfo response with cMCStatus.failed and optionally other in section 5.1.4 of CMC, are encoded as defined in CMC. Error codes
pertinent information in statusString. defined in this document are encoded using the ExtendedFailInfo
field of the cmcStatusInfoEx structure. If the same failure code
applies to multiple commands, a single cmcStatusInfoEx structure can
be used with multiple items in cMCStatusInfoEx.bodyList. The GLA may
also return other pertinent information in statusString. The
SKDFailInfo object identifier and value is:
id-cet-skdFailInfo OBJECT IDENTIFIER ::= { iso(1)
identified-organization(3) dod(6) internet(1) security(5)
mechanisms(5) pkix(7) cet(15) skdFailInfo(1) }
Turner 24
SKDFailInfo ::= INTEGER {
unspecified (0),
closedGL (1),
unsupportedDuration (2),
noGLACertificate (3),
invalidCert (4),
unsupportedAlgorithm (5),
noGLONameMatch (6),
invalidGLName (7),
nameAlreadyInUse (8),
noSpam (9),
deniedAccess (10),
alreadyAMember (11),
notAMember (12),
alreadyAnOwner (13),
notAnOwner (14) }
The values have the following meaning:
- unspecified indicates that the GLA is unable or unwilling to
perform the requested action and does not want to indicate why.
- closedGL indicates that members can only be added or deleted by
the GLO.
- unsupportedDuration indicates the GLA does not support
generating keys that are valid for the requested duration.
- noGLACertificate indicates that the GLA does not have a valid
certificate.
- invalidCert indicates the member's encryption certificate was
not verifiable (i.e., signature did not validate, certificateĘs
serial number present on a CRL, etc.).
- unsupportedAlgorithm indicates the GLA does not support the
requested algorithm.
- noGLONameMatch indicates that one of the names in the
certificate used to sign a request does not match the name of a
registered GLO.
- invalidGLName indicates the GLA does not support the glName
present in the request.
- nameAlreadyInUse indicates the glName is already assigned on the
GLA.
- noSpam indicates the prospective GL member did not sign the
request (i.e., if the name in glMember.glMemberName does not
match one of the names in the certificate used to sign the
request).
Turner 25
- alreadyAMember indicates the prospective GL member is already a
GL member.
- notAMember indicates the prospective non-GL member is not a GL
member.
- alreadyAnOwner indicates the prospective GLO is already a GLO.
- notAnOwner indicates the prospective non-GLO is not a GLO.
cMCStatusInfoEx is used by GLAs to indicate to GLOs and GL members
that a request was successfully completed. If the request was
successful, the GLA returns a cMCStatusInfoEx response with
cMCStatus.success and optionally other pertinent information in
stutsString.
When the GL is managed and the GLO has reviewed GL member initiated When the GL is managed and the GLO has reviewed GL member initiated
glAddMember, glDeleteMember, and glkComrpomise requests, the GLO glAddMember, glDeleteMember, and glkComrpomise requests, the GLO
uses cMCStatusInfo to indicate the success or failure of the uses cMCStatusInfoEx to indicate the success or failure of the
request. If the request is allowed, cMCStatus.success is returned request. If the request is allowed, cMCStatus.success is returned
and statusString is optionally returned to convey additional and statusString is optionally returned to convey additional
information. If the request is denied, cMCStatus.failed is returned information. If the request is denied, cMCStatus.failed is returned
and statusString is optionally returned to convey additional and statusString is optionally returned to convey additional
information. information. Additionally, the appropriate SKDFailInfo can be
included in cMCStatusInfoEx.extendedFailInfo.
cMCStatusInfo is used by GLOs, GLAs, and GL members to indicate that cMCStatusInfoEx is used by GLOs, GLAs, and GL members to indicate
signature verification failed. If the signature failed to verify, that signature verification failed. If the signature failed to
the cMCStatusInfo control attribute MUST be returned indicating verify over any control attibute except a cMCStatusInfoEx, a
cMCStatusInfoEx control attribute MUST be returned indicating
cMCStatus.failed and otherInfo.failInfo.badMessageCheck. If the cMCStatus.failed and otherInfo.failInfo.badMessageCheck. If the
signature over the outermost PKIData failed, the bodyList value is signature over the outermost PKIData failed, the bodyList value is
zero (0). If the signature over any other PKIData failed the zero (0). If the signature over any other PKIData failed the
bodyList value is the bodyPartId value from the request or response. bodyList value is the bodyPartId value from the request or response.
cMCStatusInfo is also used by GLOs and GLAs to indicate that a cMCStatusInfoEx is also used by GLOs and GLAs to indicate that a
request could not be performed immediately. If the request could not request could not be performed immediately. If the request could not
be processed immediately by the GLA or GLO, the cMCStatusInfo be processed immediately by the GLA or GLO, the cMCStatusInfoEx
control attribute MUST be returned indicating cMCStatus.pending and control attribute MUST be returned indicating cMCStatus.pending and
otherInfo.pendInfo. When requests are redirected to the GLO for otherInfo.pendInfo. When requests are redirected to the GLO for
approval (for managed lists), the GLA MUST NOT return a approval (for managed lists), the GLA MUST NOT return a
cMCStatusInfo indicating query pending. cMCStatusInfoEx indicating query pending.
Turner 26 cMCStatusInfoEx is also used by GLAs to indicate that a
cMCStatusInfo is also used by GLAs to indicate that a
glaQueryRequest is not supported. If the glaQueryRequest is not glaQueryRequest is not supported. If the glaQueryRequest is not
supported, the cMCStatusInfo control attribute MUST be returned supported, the cMCStatusInfoEx control attribute MUST be returned
indicating cMCStatus.noSupport and statusString is optionally indicating cMCStatus.noSupport and statusString is optionally
returned to convey additional information. returned to convey additional information.
Turner 26
3.2.4.2 Using transactionId
transactionId MAY be included by GLOs, GLAs, or GL members to transactionId MAY be included by GLOs, GLAs, or GL members to
identify a given transaction. All subsequent requests and responses identify a given transaction. All subsequent requests and responses
related to the original request MUST include the same transactionId related to the original request MUST include the same transactionId
control attribute. If GL members include a transactionId and the control attribute. If GL members include a transactionId and the
request is redirected to the GLO, the GLA MAY include an additional request is redirected to the GLO, the GLA MAY include an additional
transactionId in the outer PKIData. If the GLA included an transactionId in the outer PKIData. If the GLA included an
additional transactionId in the outer PKIData, when the GLO additional transactionId in the outer PKIData, when the GLO
generates a cMCStatusInfo response it generates one for the GLA with generates a cMCStatusInfoEx response it generates one for the GLA
the GLAĘs transactionId and one for the GL member with the GL with the GLAĘs transactionId and one for the GL member with the GL
memberĘs transactionId. memberĘs transactionId.
3.2.4.3 Using nonces
The use of nonces (see section 5.6 of [3]) can be used to provide The use of nonces (see section 5.6 of [3]) can be used to provide
application-level replay prevention. If the originating message application-level replay prevention. If the originating message
includes a senderNonce, the response to the message MUST include the includes a senderNonce, the response to the message MUST include the
received senderNonce value as the recipientNonce and a new value as received senderNonce value as the recipientNonce and a new value as
a the senderNonce value in the response. the senderNonce value in the response.
If a GLA aggratates multiple messages together or forwards a message If a GLA aggratates multiple messages together or forwards a message
to a GLO, the GLA can optionally generate a new nonce value and to a GLO, the GLA can optionally generate a new nonce value and
include that in the wrapping message. When the response comes back include that in the wrapping message. When the response comes back
from the GLO, the GLA builds a response to the originator(s) of the from the GLO, the GLA builds a response to the originator(s) of the
message(s) and deals with each of the nonce values from the message(s) and deals with each of the nonce values from the
originating messages. originating messages.
The following is the implementation requirement for the CMC control 3.2.4.4 CMC Attribute Support Requirements
attributes:
The following are the implementation requirements for CMC control
attributes for an implementation be considered conformant to this
specification:
Required
Implementation Requirement | Control Implementation Requirement | Control
GLO | GLA | GL Member |Attribute GLO | GLA | GL Member |Attribute
O R | O R F | O R | O R | O R F | O R |
--------- | ----------------- |--------- | ---------- --------- | ------------- | --------- | ----------
MUST MUST | MUST MUST - | MUSTMUST | cMCStatus MUST MUST | MUST MUST - | MUST MUST | cMCStatusinfoEx
MAY MAY | MAY MAY - | MAY MAY | transactionId MAY MAY | MAY MAY - | MAY MAY | transactionId
MAY MAY | MAY MAY - | MAY MAY | senderNonce MAY MAY | MAY MAY - | MAY MAY | senderNonce
MAY MAY | MAY MAY - | MAY MAY | recepientNonce MAY MAY | MAY MAY - | MAY MAY | recepientNonce
MUST MUST | MUST MUST - | MUST MUST | SKDFailInfo
Turner 27
3.2.5 Resubmitted GL Member Messages 3.2.5 Resubmitted GL Member Messages
When the GL is managed, the GLA forwards the GL member requests to When the GL is managed, the GLA forwards the GL member requests to
the GLO for GLO approval by creating a new request message the GLO for GLO approval by creating a new request message
containing the GL member request(s) as a cmsSequence item. If the containing the GL member request(s) as a cmsSequence item. If the
GLO approves the request it can either add a new layer of wrapping GLO approves the request it can either add a new layer of wrapping
and send it back to the GLA or create a new message sends it to the and send it back to the GLA or create a new message sends it to the
Turner 27
GLA. (Note in this case there are now 3 layers of PKIData messages GLA. (Note in this case there are now 3 layers of PKIData messages
with appropriate signing layers.) with appropriate signing layers.)
3.2.6 PKIX 3.2.6 PKIX
Signatures, certificates, and CRLs are verified according to PKIX Signatures, certificates, and CRLs are verified according to PKIX
[6]. [5].
Name matching is performed according to PKIX [6]. Name matching is performed according to PKIX [5].
All distinguished name forms must follow the UTF8String convention All distinguished name forms must follow the UTF8String convention
noted in PKIX [6]. noted in PKIX [5].
A certificate per-GL would be issued to the GLA. A certificate per-GL would be issued to the GLA.
GL policy may mandate that the GL memberĘs address be included in GL policy may mandate that the GL memberĘs address be included in
the GL memberĘs certificate. the GL memberĘs certificate.
4 Administrative Messages 4 Administrative Messages
There are a number of administrative messages that must be performed There are a number of administrative messages that must be performed
to manage a GL. The following sections describe each of messages' to manage a GL. The following sections describe each of messages'
skipping to change at line 1362 skipping to change at line 1387
+-----+ 1 2 +-----+ +-----+ 1 2 +-----+
| GLA | <-------> | GLO | | GLA | <-------> | GLO |
+-----+ +-----+ +-----+ +-----+
Figure 3 - Create Group List Figure 3 - Create Group List
The process is as follows: The process is as follows:
1 - The GLO is the entity responsible for requesting the creation 1 - The GLO is the entity responsible for requesting the creation
of the GL. The GLO sends a of the GL. The GLO sends a
Turner 28
SignedData.PKIData.controlSequence.glUseKEK request to the GLA SignedData.PKIData.controlSequence.glUseKEK request to the GLA
(1 in Figure 3). The GLO MUST include: glName, glAddress, (1 in Figure 3). The GLO MUST include: glName, glAddress,
glOwnerName, glOwnerAddress, and glAdministration. The GLO MAY glOwnerName, glOwnerAddress, and glAdministration. The GLO MAY
also include their preferences for the shared KEK in also include their preferences for the shared KEK in
glKeyAttributes by indicating whether the GLO controls the glKeyAttributes by indicating whether the GLO controls the
rekey in rekeyControlledByGLO, whether separate glKey messages rekey in rekeyControlledByGLO, whether separate glKey messages
Turner 28
should be sent to each recipient in should be sent to each recipient in
recipientsNotMutuallyAware, the requested algorithm to be used recipientsNotMutuallyAware, the requested algorithm to be used
with the shared KEK in requestedAlgorithm, the duration of the with the shared KEK in requestedAlgorithm, the duration of the
shared KEK, and how many shared KEKs should be initially shared KEK, and how many shared KEKs should be initially
distributed in generationCounter. distributed in generationCounter.
1.a - If the GLO knows of members to be added to the GL, the 1.a - If the GLO knows of members to be added to the GL, the
glAddMember request(s) MAY be included in the same glAddMember request(s) MAY be included in the same
controlSequence as the glUseKEK request (see section 3.2.2). controlSequence as the glUseKEK request (see section 3.2.2).
The GLO MUST indicate the same glName in the glAddMember The GLO MUST indicate the same glName in the glAddMember
skipping to change at line 1398 skipping to change at line 1423
the EnvelopedData (see section 3.2.1.2). the EnvelopedData (see section 3.2.1.2).
2 - Upon receipt of the request, the GLA verifies the signature on 2 - Upon receipt of the request, the GLA verifies the signature on
the inner most SignedData.PKIData. If an additional SignedData the inner most SignedData.PKIData. If an additional SignedData
and/or EnvelopedData encapsulates the request (see sections and/or EnvelopedData encapsulates the request (see sections
3.2.1.2 and 3.2.2), the GLA MUST verify the outer signature(s) 3.2.1.2 and 3.2.2), the GLA MUST verify the outer signature(s)
and/or decrypt the outer layer(S) prior to verifying the and/or decrypt the outer layer(S) prior to verifying the
signature on the inner most SignedData. signature on the inner most SignedData.
2.a - If the signatures do not verify, the GLA MUST return a 2.a - If the signatures do not verify, the GLA MUST return a
cMCStatusInfo response indicating cMCStatus.failed and cMCStatusInfoEx response indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck. otherInfo.failInfo.badMessageCheck.
2.b ū Else if the signatures do verify but the GLA does not have a 2.b ū Else if the signatures do verify but the GLA does not have a
valid certificate, the GLA MUST return a valid certificate, the GLA MUST return a cMCStatusInfoEx
glFailInfo.errorCode.noValidGLACertificate. Instead of with cMCStatus.failed and
immediately returning the error code, the GLA MAY attempt to otherInfo.extendedFailInfo.SKDFailInfo value of
get a certificate, possibly using CMC [3]. noValidGLACertificate. Instead of immediately returning the
error code, the GLA MAY attempt to get a certificate,
possibly using CMC [3].
2.c - Else the signatures do verify and the GLA does have a valid 2.c - Else the signatures do verify and the GLA does have a valid
certificate, the GLA MUST check that one of the names in the certificate, the GLA MUST check that one of the names in the
certificate used to sign the request matches one of the certificate used to sign the request matches one of the
names in glUseKEK.glOwnerInfo.glOwnerName. names in glUseKEK.glOwnerInfo.glOwnerName.
2.c.1 - If the names do not match, the GLA MUST return a response 2.c.1 - If the names do not match, the GLA MUST return a response
indicating glFailInfo.errorCode.noGLONameMatch. indicating cMCStatusInfoEx with cMCStatus.failed and
Turner 29 Turner 29
otherInfo.extendedFailInfo.SKDFailInfo value of
noGLONameMatch.
2.c.2 - Else names do all match, the GLA MUST check that the 2.c.2 - Else names do all match, the GLA MUST check that the
glName and glAddress is not already in use. The GLA MUST glName and glAddress is not already in use. The GLA MUST
also check any glAddMember included within the also check any glAddMember included within the
controlSequence with this glUseKEK. Further processing of controlSequence with this glUseKEK. Further processing of
the glAddMember is covered in section 4.3. the glAddMember is covered in section 4.3.
2.c.2.a - If the glName is already in use the GLA MUST return a 2.c.2.a - If the glName is already in use the GLA MUST return a
response indicating response indicating cMCStatusInfoEx with
glFailInfo.errorCode.nameAlreadyInUse. cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of
nameAlreadyInUse.
2.c.2.b - Else the requestedAlgorithm is not supported, the GLA 2.c.2.b - Else the requestedAlgorithm is not supported, the GLA
MUST return a response indicating MUST return a response indicating cMCStatusInfoEx with
glFailInfo.errorCode.unsupportedAlgorithm. cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of
unsupportedAlgorithm.
2.c.2.c - Else the duration is not supportable, determining this 2.c.2.c - Else the duration is not supportable, determining this
is beyond the scope of this document, the GLA MUST is beyond the scope of this document, the GLA MUST
return a response indicating return a response indicating cMCStatusInfoEx with
glFailInfo.errorCode.unsupportedDuration. cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of
unsupportedDuration.
2.c.2.d - Else the GL is not supportable for other reasons, which 2.c.2.d - Else the GL is not supportable for other reasons, which
the GLA does not wish to disclose, the GLA MUST return a the GLA does not wish to disclose, the GLA MUST return a
response indicating glFailInfo.errorCode.unspecified. response indicating cMCStatusInfoEx with
cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of
unspecified.
2.c.2.e - Else the glName is not already in use, the duration is 2.c.2.e - Else the glName is not already in use, the duration is
supportable, and the requestedAlgorithm is supported, supportable, and the requestedAlgorithm is supported,
the GLA MUST return a glSuccessInfo indicating the the GLA MUST return a cMCStatusInfoEx indicating
glName, the corresponding glIdentifier, and an cMCStatus.success (2 in Figure 3). The GLA also takes
action.actionCode.assignedKEK (2 in Figure 3). The GLA administrative actions, which are beyond the scope of
also takes administrative actions, which are beyond the this document, to store the glName, glAddress,
scope of this document, to store the glName, glAddress,
glKeyAttributes, glOwnerName, and glOwnerAddress. The glKeyAttributes, glOwnerName, and glOwnerAddress. The
GLA also sends a glKey message as described in section GLA also sends a glKey message as described in section
5. 5.
2.c.2.e.1 - The GLA MUST apply confidentiality to the response by 2.c.2.e.1 - The GLA MUST apply confidentiality to the response by
encapsulating the SignedData.PKIResponse in an encapsulating the SignedData.PKIResponse in an
EnvelopedData if the request was encapsulated in an EnvelopedData if the request was encapsulated in an
EnvelopedData (see section 3.2.1.2). EnvelopedData (see section 3.2.1.2).
2.c.2.e.2 - The GLA MAY also optionally apply another SignedData 2.c.2.e.2 - The GLA MAY also optionally apply another SignedData
over the EnvelopedData (see section 3.2.1.2). over the EnvelopedData (see section 3.2.1.2).
3 - Upon receipt of the glSuccessInfo or glFailInfo responses, the
GLO verifies the GLA's signature(s). If an additional
SignedData and/or EnvelopedData encapsulates the response (see
section 3.2.1.2 or 3.2.2), the GLO MUST verify the outer
signature and/or decrypt the outer layer prior to verifying
the signature on the inner most SignedData.
3.a - If the signatures do not verify, the GLO MUST return a
cMCStatusInfo response indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck.
Turner 30 Turner 30
3.b - Else the signatures do verify, the GLO MUST check that one 3 - Upon receipt of the cMCStatusInfoEx responses, the GLO
verifies the GLA's signature(s). If an additional SignedData
and/or EnvelopedData encapsulates the response (see section
3.2.1.2 or 3.2.2), the GLO MUST verify the outer signature
and/or decrypt the outer layer prior to verifying the
signature on the inner most SignedData.
3.a - Else the signatures do verify, the GLO MUST check that one
of the names in the certificate used to sign the response of the names in the certificate used to sign the response
matches the name of the GL. matches the name of the GL.
3.b.1 ū If the GLĘs name does not match the name present in the 3.a.1 ū If the GLĘs name does not match the name present in the
certificate used to sign the message, the GLO should not certificate used to sign the message, the GLO should not
believe the response. believe the response.
3.b.2 ū Else the GLĘs name does match the name present in the 3.a.2 ū Else the GLĘs name does match the name present in the
certificate and: certificate and:
3.b.2.a - If the signatures do verify and the response was 3.a.2.a - If the signatures do verify and the response was
glSuccessInfo, the GLO has successfully created the GL. cMCStatusInfoEx indicating cMCStatus.success, the GLO
has successfully created the GL.
3.b.2.b - Else the signatures do verify and the response was 3.a.2.b - Else the signatures do verify and the response was
glFailInfo, the GLO MAY reattempt to create the GL using cMCStatusInfoEx.cMCStatus.failed for any reason, the GLO
the information provided in the glFailInfo response. The MAY reattempt to create the GL using the information
GLO may also use the glaQueryRequest to determine the provided in the response. The GLO may also use the
algorithms and other characteristics supported by the GLA glaQueryRequest to determine the algorithms and other
(see section 4.9). characteristics supported by the GLA (see section 4.9).
4.2 Delete GL From GLA 4.2 Delete GL From GLA
From time to time, there are instances when a GL is no longer From time to time, there are instances when a GL is no longer
needed. In this case the GLO must delete the GL. Figure 4 depicts needed. In this case the GLO must delete the GL. Figure 4 depicts
that protocol interactions to delete a GL. that protocol interactions to delete a GL.
+-----+ 1 2 +-----+ +-----+ 1 2 +-----+
| GLA | <-------> | GLO | | GLA | <-------> | GLO |
+-----+ +-----+ +-----+ +-----+
skipping to change at line 1511 skipping to change at line 1546
Figure 4 - Delete Group List Figure 4 - Delete Group List
The process is as follows: The process is as follows:
1 - The GLO is the entity responsible for requesting the deletion 1 - The GLO is the entity responsible for requesting the deletion
of the GL. The GLO sends a of the GL. The GLO sends a
SignedData.PKIData.controlSequence.glDelete request to the GLA SignedData.PKIData.controlSequence.glDelete request to the GLA
(1 in Figure 4). The name of the GL to be deleted MUST be (1 in Figure 4). The name of the GL to be deleted MUST be
included in GeneralName. included in GeneralName.
Turner 31
1.a - The GLO MAY optionally apply confidentiality to the request 1.a - The GLO MAY optionally apply confidentiality to the request
by encapsulating the SignedData.PKIData in an EnvelopedData by encapsulating the SignedData.PKIData in an EnvelopedData
(see section 3.2.1.2). (see section 3.2.1.2).
1.b - The GLO MAY also optionally apply another SignedData over 1.b - The GLO MAY also optionally apply another SignedData over
the EnvelopedData (see section 3.2.1.2). the EnvelopedData (see section 3.2.1.2).
Turner 31
2 - Upon receipt of the request the GLA verifies the signature on 2 - Upon receipt of the request the GLA verifies the signature on
the inner most SignedData.PKIData. If an additional SignedData the inner most SignedData.PKIData. If an additional SignedData
and/or EnvelopedData encapsulates the request (see section and/or EnvelopedData encapsulates the request (see section
3.2.1.2 or 3.2.2), the GLA MUST verify the outer signature 3.2.1.2 or 3.2.2), the GLA MUST verify the outer signature
and/or decrypt the outer layer prior to verifying the and/or decrypt the outer layer prior to verifying the
signature on the inner most SignedData. signature on the inner most SignedData.
2.a - If the signatures do not verify, the GLA MUST return a 2.a - If the signatures do not verify, the GLA MUST return a
cMCStatusInfo response indicating cMCStatus.failed and cMCStatusInfoEx response indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck. otherInfo.failInfo.badMessageCheck.
2.b - Else the signatures do verify, the GLA MUST make sure the GL 2.b - Else the signatures do verify, the GLA MUST make sure the GL
is supported by checking the GLĘs Name matches a glName is supported by checking the GLĘs Name matches a glName
stored on the GLA. stored on the GLA.
2.b.1 - If the glName is not supported by the GLA, the GLA MUST 2.b.1 - If the glName is not supported by the GLA, the GLA MUST
return a response indicating return a response indicating cMCStatusInfoEx with
glFailInfo.errorCode.invalidGLName. cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of
invalidGLName.
2.b.2 - Else the glName is supported by the GLA, the GLA MUST 2.b.2 - Else the glName is supported by the GLA, the GLA MUST
ensure a registered GLO signed the glDelete request by ensure a registered GLO signed the glDelete request by
checking if one of the names present in the digital checking if one of the names present in the digital
signature certificate used to sign the glDelete request signature certificate used to sign the glDelete request
matches a registered GLO. matches a registered GLO.
2.b.2.a - If the names do not match, the GLA MUST return a 2.b.2.a - If the names do not match, the GLA MUST return a
response indicating glFailInfo.errorCode.noGLONameMatch. response indicating cMCStatusInfoEx with
cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of
noGLONameMatch.
2.b.2.b - Else the names do match but the GL is not deletable for 2.b.2.b - Else the names do match but the GL is not deletable for
other reasons, which the GLA does not wish to disclose, other reasons, which the GLA does not wish to disclose,
the GLA MUST return a response indicating the GLA MUST return a response indicating
glFailInfo.errorCode.unspecified. Actions beyond the cMCStatusInfoEx with cMCStatus.failed and
scope of this document must then be taken to delete the otherInfo.extendedFailInfo.SKDFailInfo value of
GL from the GLA. unspecified. Actions beyond the scope of this document
must then be taken to delete the GL from the GLA.
2.b.2.c - Else the names do match, the GLA MUST return a 2.b.2.c - Else the names do match, the GLA MUST return a
glSuccessInfo indicating the glName, and an cMCStatusInfoEx indicating cMCStatus.success (2 in
action.actionCode.deletedGL (2 in Figure 4). Figure 4). The GLA MUST not accept further requests for
glMemberName and glOwnerName MUST be omitted. The GLA
MUST not accept further requests for member additions, Turner 32
member deletions, or group rekeys for this GL. member additions, member deletions, or group rekeys for
this GL.
2.b.2.c.1 - The GLA MUST apply confidentiality to the response by 2.b.2.c.1 - The GLA MUST apply confidentiality to the response by
encapsulating the SignedData.PKIResponse in an encapsulating the SignedData.PKIResponse in an
EnvelopedData if the request was encapsulated in an EnvelopedData if the request was encapsulated in an
EnvelopedData (see section 3.2.1.2). EnvelopedData (see section 3.2.1.2).
2.b.2.c.2 - The GLA MAY also optionally apply another SignedData 2.b.2.c.2 - The GLA MAY also optionally apply another SignedData
over the EnvelopedData (see section 3.2.1.2). over the EnvelopedData (see section 3.2.1.2).
3 - Upon receipt of the glSuccessInfo or glFailInfo response, the 3 - Upon receipt of the cMCStatusInfoEx response, the GLO verifies
GLO verifies the GLA's signature(s). If an additional the GLA's signature(s). If an additional SignedData and/or
EnvelopedData encapsulates the response (see section 3.2.1.2
Turner 32 or 3.2.2), the GLO MUST verify the outer signature and/or
SignedData and/or EnvelopedData encapsulates the response (see decrypt the outer layer prior to verifying the signature on
section 3.2.1.2 or 3.2.2), the GLO MUST verify the outer the inner most SignedData.
signature and/or decrypt the outer layer prior to verifying
the signature on the inner most SignedData.
3.a - If the signatures do not verify, the GLO MUST return a
cMCStatusInfo response indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck.
3.b - Else the signatures do verify, the GLO MUST check that one 3.a - Else the signatures do verify, the GLO MUST check that one
of the names in the certificate used to sign the response of the names in the certificate used to sign the response
matches the name of the GL. matches the name of the GL.
3.b.1 ū If the GLĘs name does not match the name present in the 3.a.1 ū If the GLĘs name does not match the name present in the
certificate used to sign the message, the GLO should not certificate used to sign the message, the GLO should not
believe the response. believe the response.
3.b.2 ū Else the GLĘs name does match the name present in the 3.a.2 ū Else the GLĘs name does match the name present in the
certificate and: certificate and:
3.b.2.a - If the signatures do verify and the response was 3.a.2.a - If the signatures do verify and the response was
glSuccessInfo, the GLO has successfully deleted the GL. cMCStatusInfoEx indicating cMCStatus.success, the GLO
has successfully deleted the GL.
3.b.2.b - Else the signatures do verify and the response was 3.a.2.b - Else the signatures do verify and the response was
glFailInfo, the GLO MAY reattempt to delete the GL using cMCStatusInfoEx.cMCStatus.failed for any reason, the GLO
the information provided in the glFailInfo response. MAY reattempt to delete the GL using the information
provided in the response.
4.3 Add Members To GL 4.3 Add Members To GL
To add members to GLs, either the GLO or prospective members use the To add members to GLs, either the GLO or prospective members use the
glAddMember request. The GLA processes GLO and prospective GL member glAddMember request. The GLA processes GLO and prospective GL member
requests differently though. GLOs can submit the request at any time requests differently though. GLOs can submit the request at any time
to add members to the GL, and the GLA, once it has verified the to add members to the GL, and the GLA, once it has verified the
request came from a registered GLO, should process it. If a request came from a registered GLO, should process it. If a
prospective member sends the request, the GLA needs to determine how prospective member sends the request, the GLA needs to determine how
the GL is administered. When the GLO initially configured the GL, the GL is administered. When the GLO initially configured the GL,
they set the GL to be unmanaged, managed, or closed (see section they set the GL to be unmanaged, managed, or closed (see section
3.1.1). In the unmanaged case, the GLA merely processes the memberĘs 3.1.1). In the unmanaged case, the GLA merely processes the memberĘs
request. For the managed case, the GLA forwards the requests from request. For the managed case, the GLA forwards the requests from
the prospective members to the GLO for review. Where there are the prospective members to the GLO for review. Where there are
Turner 33
multiple GLOs for a GL, which GLO the request is forwarded to is multiple GLOs for a GL, which GLO the request is forwarded to is
beyond the scope of this document. The GLO reviews the request and beyond the scope of this document. The GLO reviews the request and
either rejects it or submits a reformed request to the GLA. In the either rejects it or submits a reformed request to the GLA. In the
closed case, the GLA will not accept requests from prospective closed case, the GLA will not accept requests from prospective
members. The following sections describe the processing for the members. The following sections describe the processing for the
GLO(s), GLA, and prospective GL members depending on where the GLO(s), GLA, and prospective GL members depending on where the
glAddMeber request originated, either from a GLO or from prospective glAddMeber request originated, either from a GLO or from prospective
members. Figure 5 depicts the protocol interactions for the three members. Figure 5 depicts the protocol interactions for the three
options. Note that the error messages are not depicted. options. Note that the error messages are not depicted.
Turner 33
+-----+ 2,B{A} 3 +----------+ +-----+ 2,B{A} 3 +----------+
| GLO | <--------+ +-------> | Member 1 | | GLO | <--------+ +-------> | Member 1 |
+-----+ | | +----------+ +-----+ | | +----------+
1 | | 1 | |
+-----+ <--------+ | 3 +----------+ +-----+ <--------+ | 3 +----------+
| GLA | A +-------> | ... | | GLA | A +-------> | ... |
+-----+ <-------------+ +----------+ +-----+ <-------------+ +----------+
| |
| 3 +----------+ | 3 +----------+
+-------> | Member n | +-------> | Member n |
skipping to change at line 1666 skipping to change at line 1705
Figure 5). The GLO MUST include: the GL name in glName, the Figure 5). The GLO MUST include: the GL name in glName, the
member's name in glMember.glMemberName, the memberĘs address member's name in glMember.glMemberName, the memberĘs address
in glMember.glMemberAddress, and the member's encryption in glMember.glMemberAddress, and the member's encryption
certificate in glMember.certificates.pKC. The GLO MAY also certificate in glMember.certificates.pKC. The GLO MAY also
include any attribute certificates associated with the include any attribute certificates associated with the
memberĘs encryption certificate in glMember.certificates.aC, memberĘs encryption certificate in glMember.certificates.aC,
and the certification path associated with the memberĘs and the certification path associated with the memberĘs
encryption and attribute certificates in encryption and attribute certificates in
glMember.certificates.certificationPath. glMember.certificates.certificationPath.
Turner 34
1.a - The GLO MAY optionally apply confidentiality to the request 1.a - The GLO MAY optionally apply confidentiality to the request
by encapsulating the SignedData.PKIData in an EnvelopedData by encapsulating the SignedData.PKIData in an EnvelopedData
(see section 3.2.1.2). (see section 3.2.1.2).
1.b - The GLO MAY also optionally apply another SignedData over 1.b - The GLO MAY also optionally apply another SignedData over
the EnvelopedData (see section 3.2.1.2). the EnvelopedData (see section 3.2.1.2).
2 - Upon receipt of the request, the GLA verifies the signature on 2 - Upon receipt of the request, the GLA verifies the signature on
the inner most SignedData.PKIData. If an additional SignedData the inner most SignedData.PKIData. If an additional SignedData
Turner 34
and/or EnvelopedData encapsulates the request (see section and/or EnvelopedData encapsulates the request (see section
3.2.1.2 or 3.2.2), the GLA MUST verify the outer signature 3.2.1.2 or 3.2.2), the GLA MUST verify the outer signature
and/or decrypt the outer layer prior to verifying the and/or decrypt the outer layer prior to verifying the
signature on the inner most SignedData. signature on the inner most SignedData.
2.a - If the signatures do not verify, the GLA MUST return a 2.a - If the signatures do not verify, the GLA MUST return a
cMCStatusInfo response indicating cMCStatus.failed and cMCStatusInfoEx response indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck. otherInfo.failInfo.badMessageCheck.
2.b - Else the signatures do verify, the glAddMember request is 2.b - Else the signatures do verify, the glAddMember request is
included in a controlSequence with the glUseKEK request, and included in a controlSequence with the glUseKEK request, and
the processing in section 4.1 item 2.e is successfully the processing in section 4.1 item 2.e is successfully
completed the GLA MUST return a glSuccessInfo indicating the completed the GLA MUST return a cMCStatusInfoEx indicating
glName, the corresponding glIdentifier, an cMCStatus.success (2 in Figure 5).
action.actionCode.addedMember, and action.glMemberName (2 in
Figure 5).
2.b.1 - The GLA MUST apply confidentiality to the response by 2.b.1 - The GLA MUST apply confidentiality to the response by
encapsulating the SignedData.PKIData in an EnvelopedData encapsulating the SignedData.PKIData in an EnvelopedData
if the request was encapsulated in an EnvelopedData (see if the request was encapsulated in an EnvelopedData (see
section 3.2.1.2). section 3.2.1.2).
2.b.2 - The GLA MAY also optionally apply another SignedData over 2.b.2 - The GLA MAY also optionally apply another SignedData over
the EnvelopedData (see section 3.2.1.2). the EnvelopedData (see section 3.2.1.2).
2.c - Else the signatures do verify and the GLAddMember request is 2.c - Else the signatures do verify and the GLAddMember request is
not included in a controlSequence with the GLCreate request, not included in a controlSequence with the GLCreate request,
the GLA MUST make sure the GL is supported by checking that the GLA MUST make sure the GL is supported by checking that
the glName matches a glName stored on the GLA. the glName matches a glName stored on the GLA.
2.c.1 - If the glName is not supported by the GLA, the GLA MUST 2.c.1 - If the glName is not supported by the GLA, the GLA MUST
return a response indicating return a response indicating cMCStatusInfoEx with
glFailInfo.errorCode.invalidGLName. cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of
invalidGLName.
2.c.2 - Else the glName is supported by the GLA, the GLA MUST 2.c.2 - Else the glName is supported by the GLA, the GLA MUST
check to see if the glMemberName is present on the GL. check to see if the glMemberName is present on the GL.
2.c.2.a - If the glMemberName is present on the GL, the GLA MUST 2.c.2.a - If the glMemberName is present on the GL, the GLA MUST
return a response indicating return a response indicating cMCStatusInfoEx with
glFailInfo.errorCode.alreadyAMember. cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of
alreadyAMember.
Turner 35
2.c.2.b - Else the glMemberName is not present on the GL, the GLA 2.c.2.b - Else the glMemberName is not present on the GL, the GLA
MUST check how the GL is administered. MUST check how the GL is administered.
2.c.2.b.1 - If the GL is closed, the GLA MUST check that a 2.c.2.b.1 - If the GL is closed, the GLA MUST check that a
registered GLO signed the request by checking that one registered GLO signed the request by checking that one
of the names in the digital signature certificate used of the names in the digital signature certificate used
to sign the request matches a registered GLO. to sign the request matches a registered GLO.
2.c.2.b.1.a - If the names do not match, the GLA MUST return a 2.c.2.b.1.a - If the names do not match, the GLA MUST return a
response indicating response indicating cMCStatusInfoEx with
glFailInfo.errorCode.noGLONameMatch. cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of
noGLONameMatch.
Turner 35
2.c.2.b.1.b - Else the names do match, the GLA MUST verify the 2.c.2.b.1.b - Else the names do match, the GLA MUST verify the
member's encryption certificate. member's encryption certificate.
2.c.2.b.1.b.1 - If the member's encryption certificate does not 2.c.2.b.1.b.1 - If the member's encryption certificate does not
verify, the GLA MAY return a response indicating verify, the GLA MAY return a response indicating
glFailInfo.errorCode.invalidCert to the GLO. If cMCStatusInfoEx with cMCStatus.failed and
the GLA does not return a glFailInfo response, the otherInfo.extendedFailInfo.SKDFailInfo value of
invalidCert to the GLO. If the GLA does not return
a cMCStatusInfoEx.cMCStatus.failed response, the
GLA MUST issue a glProvideCert request (see GLA MUST issue a glProvideCert request (see
section 4.10). section 4.10).
2.c.2.b.1.b.2 - Else the member's certificate does verify, the GLA 2.c.2.b.1.b.2 - Else the member's certificate does verify, the GLA
MUST return a glSuccessInfo to the GLO indicating MUST return a cMCStatusInfoEx indicating
the glName, the corresponding glIdentifier, an cMCStatus.success (2 in Figure 5). The GLA also
action.actionCode.addedMember, and
action.glMemberName (2 in Figure 5). The GLA also
takes administrative actions, which are beyond the takes administrative actions, which are beyond the
scope of this document, to add the member to the scope of this document, to add the member to the
GL stored on the GLA. The GLA MUST also distribute GL stored on the GLA. The GLA MUST also distribute
the shared KEK to the member via the mechanism the shared KEK to the member via the mechanism
described in section 5. described in section 5.
2.c.2.b.1.b.2.a - The GLA MUST apply confidentiality to the 2.c.2.b.1.b.2.a - The GLA MUST apply confidentiality to the
response by encapsulating the SignedData.PKIData response by encapsulating the SignedData.PKIData
in an EnvelopedData if the request was in an EnvelopedData if the request was
encapsulated in an EnvelopedData (see section encapsulated in an EnvelopedData (see section
skipping to change at line 1767 skipping to change at line 1809
2.c.2.b.1.b.2.b - The GLA MAY also optionally apply another 2.c.2.b.1.b.2.b - The GLA MAY also optionally apply another
SignedData over the EnvelopedData (see section SignedData over the EnvelopedData (see section
3.2.1.2). 3.2.1.2).
2.c.2.b.2 - Else the GL is managed, the GLA MUST check that either 2.c.2.b.2 - Else the GL is managed, the GLA MUST check that either
a registered GLO or the prospective member signed the a registered GLO or the prospective member signed the
request. For GLOs, one of the names in the certificate request. For GLOs, one of the names in the certificate
used to sign the request MUST match a registered GLO. used to sign the request MUST match a registered GLO.
For the prospective member, the name in For the prospective member, the name in
Turner 36
glMember.glMemberName MUST match one of the names in glMember.glMemberName MUST match one of the names in
the certificate used to sign the request. the certificate used to sign the request.
2.c.2.b.2.a - If the signer is neither a registered GLO nor the 2.c.2.b.2.a - If the signer is neither a registered GLO nor the
prospective GL member, the GLA MUST return a prospective GL member, the GLA MUST return a
response indicating glFailInfo.errorCode.noSpam. response indicating cMCStatusInfoEx with
cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of
noSpam.
2.c.2.b.2.b - Else the signer is a registered GLO, the GLA MUST 2.c.2.b.2.b - Else the signer is a registered GLO, the GLA MUST
verify the member's encryption certificate. verify the member's encryption certificate.
2.c.2.b.2.b.1 - If the member's certificate does not verify, the 2.c.2.b.2.b.1 - If the member's certificate does not verify, the
GLA MAY return a response indicating GLA MAY return a response indicating
glFailInfo.errorCode.invalidCert. If the GLA does cMCStatusInfoEx with cMCStatus.failed and
not return a glFailInfo response, the GLA MUST otherInfo.extendedFailInfo.SKDFailInfo value of
issue a glProvideCert request (see section 4.10). invalidCert. If the GLA does not return a
cMCStatus.failed response, the GLA MUST issue a
glProvideCert request (see section 4.10).
Turner 36
2.c.2.b.2.b.2 - Else the member's certificate does verify, the GLA 2.c.2.b.2.b.2 - Else the member's certificate does verify, the GLA
MUST return glSuccessInfo indicating the glName, MUST return a cMCStatusInfoEx indicating
the corresponding glIdentifier, an cMCStatus.success to the GLO (2 in Figure 5). The
action.actionCode.addedMember, and GLA also takes administrative actions, which are
action.glMemberName to the GLO (2 in Figure 5). beyond the scope of this document, to add the
The GLA also takes administrative actions, which
are beyond the scope of this document, to add the
member to the GL stored on the GLA. The GLA MUST member to the GL stored on the GLA. The GLA MUST
also distribute the shared KEK to the member via also distribute the shared KEK to the member via
the mechanism described in section 5. The GL the mechanism described in section 5. The GL
policy may mandate that the GL memberĘs address be policy may mandate that the GL memberĘs address be
included in the GL memberĘs certificate. included in the GL memberĘs certificate.
2.c.2.b.2.b.2.a - The GLA MUST apply confidentiality to the 2.c.2.b.2.b.2.a - The GLA MUST apply confidentiality to the
response by encapsulating the SignedData.PKIData response by encapsulating the SignedData.PKIData
in an EnvelopedData if the request was in an EnvelopedData if the request was
encapsulated in an EnvelopedData (see section encapsulated in an EnvelopedData (see section
skipping to change at line 1816 skipping to change at line 1862
2.c.2.b.2.c - Else the signer is the prospective member, the GLA 2.c.2.b.2.c - Else the signer is the prospective member, the GLA
MUST forward the glAddMember request (see section MUST forward the glAddMember request (see section
3.2.3) to a registered GLO (B{A} in Figure 5). If 3.2.3) to a registered GLO (B{A} in Figure 5). If
there is more than one registered GLO, the GLO to there is more than one registered GLO, the GLO to
which the request is forwarded to is beyond the which the request is forwarded to is beyond the
scope of this document. Further processing of the scope of this document. Further processing of the
forwarded request by GLOs is addressed in 3 of forwarded request by GLOs is addressed in 3 of
section 4.3.2. section 4.3.2.
Turner 37
2.c.2.b.2.c.1 - The GLA MUST apply confidentiality to the 2.c.2.b.2.c.1 - The GLA MUST apply confidentiality to the
forwarded request by encapsulating the forwarded request by encapsulating the
SignedData.PKIData in an EnvelopedData if the SignedData.PKIData in an EnvelopedData if the
original request was encapsulated in an original request was encapsulated in an
EnvelopedData (see section 3.2.1.2). EnvelopedData (see section 3.2.1.2).
2.c.2.b.2.c.2 - The GLA MAY also optionally apply another 2.c.2.b.2.c.2 - The GLA MAY also optionally apply another
SignedData over the EnvelopedData (see section SignedData over the EnvelopedData (see section
3.2.1.2). 3.2.1.2).
2.c.2.b.3 - Else the GL is unmanaged, the GLA MUST check that 2.c.2.b.3 - Else the GL is unmanaged, the GLA MUST check that
either a registered GLO or the prospective member either a registered GLO or the prospective member
signed the request. For GLOs, one of the names in the signed the request. For GLOs, one of the names in the
certificate used to sign the request MUST match the certificate used to sign the request MUST match the
name of a registered GLO. For the prospective member, name of a registered GLO. For the prospective member,
the name in glMember.glMemberName MUST match one of the name in glMember.glMemberName MUST match one of
the names in the certificate used to sign the request. the names in the certificate used to sign the request.
Turner 37
2.c.2.b.3.a - If the signer is neither a registered GLO nor the 2.c.2.b.3.a - If the signer is neither a registered GLO nor the
prospective member, the GLA MUST return a response prospective member, the GLA MUST return a response
indicating glFailInfo.errorCode.noSpam. indicating cMCStatusInfoEx with cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of
noSpam.
2.c.2.b.3.b - Else the signer is either a registered GLO or the 2.c.2.b.3.b - Else the signer is either a registered GLO or the
prospective member, the GLA MUST verify the member's prospective member, the GLA MUST verify the member's
encryption certificate. encryption certificate.
2.c.2.b.3.b.1 - If the member's certificate does not verify, the 2.c.2.b.3.b.1 - If the member's certificate does not verify, the
GLA MAY return a response indicating GLA MAY return a response indicating
glFailInfo.errorCode.invalidCert to either the GLO cMCStatusInfoEx with cMCStatus.failed and
or the prospective member depending on where the otherInfo.extendedFailInfo.SKDFailInfo value of
request originated. If the GLA does not return a invalidCert to either the GLO or the prospective
glFailInfo response, the GLA MUST issue a member depending on where the request originated.
glProvideCert request (see section 4.10) to either If the GLA does not return a cMCStatus.failed
the GLO or prospective member depending on where response, the GLA MUST issue a glProvideCert
the request originated. request (see section 4.10) to either the GLO or
prospective member depending on where the request
originated.
2.c.2.b.3.b.2 - Else the member's certificate does verify, the GLA 2.c.2.b.3.b.2 - Else the member's certificate does verify, the GLA
MUST return a glSuccessInfo indicating the glName, MUST return a cMCStatusInfoEx indicating
the corresponding glIdentifier, an cMCStatus.success to the GLO (2 in Figure 5) if
action.actionCode.addedMember, and
action.glMemberName to the GLO (2 in Figure 5) if
the GLO signed the request and to the GL member (3 the GLO signed the request and to the GL member (3
in Figure 5) if the GL member signed the request. in Figure 5) if the GL member signed the request.
The GLA also takes administrative actions, which The GLA also takes administrative actions, which
are beyond the scope of this document, to add the are beyond the scope of this document, to add the
member to the GL stored on the GLA. The GLA MUST member to the GL stored on the GLA. The GLA MUST
also distribute the shared KEK to the member via also distribute the shared KEK to the member via
the mechanism described in section 5. the mechanism described in section 5.
Turner 38
2.c.2.b.3.b.2.a - The GLA MUST apply confidentiality to the 2.c.2.b.3.b.2.a - The GLA MUST apply confidentiality to the
response by encapsulating the SignedData.PKIData response by encapsulating the SignedData.PKIData
in an EnvelopedData if the request was in an EnvelopedData if the request was
encapsulated in an EnvelopedData (see section encapsulated in an EnvelopedData (see section
3.2.1.2). 3.2.1.2).
2.c.2.b.3.b.2.b - The GLA MAY also optionally apply another 2.c.2.b.3.b.2.b - The GLA MAY also optionally apply another
SignedData over the EnvelopedData (see section SignedData over the EnvelopedData (see section
3.2.1.2). 3.2.1.2).
3 - Upon receipt of the glSuccessInfo or glFailInfo response, the 3 - Upon receipt of the cMCStatusInfoEx response, the GLO verifies
GLO verifies the GLA's signature(s). If an additional the GLA's signature(s). If an additional SignedData and/or
SignedData and/or EnvelopedData encapsulates the response (see EnvelopedData encapsulates the response (see section 3.2.1.2
section 3.2.1.2 or 3.2.2), the GLO MUST verify the outer or 3.2.2), the GLO MUST verify the outer signature and/or
signature and/or decrypt the outer layer prior to verifying decrypt the outer layer prior to verifying the signature on
the signature on the inner most SignedData. the inner most SignedData.
3.a - If the signatures do not verify, the GLO MUST return a
cMCStatusInfo response indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck.
Turner 38 3.a - Else the signatures do verify, the GLO MUST check that one
3.b - Else the signatures do verify, the GLO MUST check that one
of the names in the certificate used to sign the response of the names in the certificate used to sign the response
matches the name of the GL. matches the name of the GL.
3.b.1 ū If the GLĘs name does not match the name present in the 3.a.1 ū If the GLĘs name does not match the name present in the
certificate used to sign the message, the GLO should not certificate used to sign the message, the GLO should not
believe the response. believe the response.
3.b.2 ū Else the GLĘs name does match the name present in the 3.a.2 ū Else the GLĘs name does match the name present in the
certificate and: certificate and:
3.b.2.a - If the signatures do verify and the response is 3.a.2.a - If the signatures do verify and the response is
glSuccessInfo, the GLO has added the member to the GL. If cMCStatusInfoEx indicating cMCStatus.success, the GLA
member was added to a managed list and the original has added the member to the GL. If member was added to a
request was signed by the member, the GLO MUST send a managed list and the original request was signed by the
cMCStatusInfo.cMCStatus.success to the GL member. member, the GLO MUST send a
cMCStatusInfoEx.cMCStatus.success to the GL member.
3.b.2.b - Else the GLO received a glFailInfo, for any reason, the
GLO MAY reattempt to add the member to the GL using the
information provided in the glFailInfo response.
4 - Upon receipt of the glSuccessInfo, glFailInfo, or cMCStatus 3.a.2.b - Else the GLO received a cMCStatusInfoEx.cMCStatus.failed
response, the prospective member verifies the GLA's signatures for any reason, the GLO MAY reattempt to add the member
or GLOĘs signatures. If an additional SignedData and/or to the GL using the information provided in the
EnvelopedData encapsulates the response (see section 3.2.1.2 response.
or 3.2.2), the GLO MUST verify the outer signature and/or
decrypt the outer layer prior to verifying the signature on
the inner most SignedData.
4.a - If the signatures do not verify, the prospective member MUST 4 - Upon receipt of the cMCStatusInfoEx response, the prospective
return a cMCStatusInfo response indicating cMCStatus.failed member verifies the GLA's signatures or GLOĘs signatures. If
and otherInfo.failInfo.badMessageCheck. an additional SignedData and/or EnvelopedData encapsulates the
response (see section 3.2.1.2 or 3.2.2), the GLO MUST verify
the outer signature and/or decrypt the outer layer prior to
verifying the signature on the inner most SignedData.
4.b - Else the signatures do verify, the GL member MUST check that 4.a - Else the signatures do verify, the GL member MUST check that
one of the names in the certificate used to sign the one of the names in the certificate used to sign the
response matches the name of the GL. response matches the name of the GL.
4.b.1 ū If the GLĘs name does not match the name present in the Turner 39
4.a.1 ū If the GLĘs name does not match the name present in the
certificate used to sign the message, the GL member should certificate used to sign the message, the GL member should
not believe the response. not believe the response.
4.b.2 ū Else the GLĘs name does match the name present in the 4.a.2 ū Else the GLĘs name does match the name present in the
certificate and: certificate and:
4.b.2.a - If the signatures do verify, the prospective member has 4.a.2.a - If the signatures do verify, the prospective member has
been added to the GL. been added to the GL.
4.b.2.b - Else the prospective member received a glFailInfo, for 4.a.2.b - Else the prospective member received a
any reason, the prospective member MAY reattempt to add cMCStatusInfoEx.cMCStatus.failed, for any reason, the
themselves to the GL using the information provided in the prospective member MAY reattempt to add themselves to
glFailInfo response. the GL using the information provided in the response.
Turner 39
4.3.2 Prospective Member Initiated Additions 4.3.2 Prospective Member Initiated Additions
The process for prospective member initiated glAddMember requests is The process for prospective member initiated glAddMember requests is
as follows: as follows:
1 - The prospective GL member sends a 1 - The prospective GL member sends a
SignedData.PKIData.controlSequence.glAddMember request to the SignedData.PKIData.controlSequence.glAddMember request to the
GLA (A in Figure 5). The prospective GL member MUST include: GLA (A in Figure 5). The prospective GL member MUST include:
the GL name in glName, their name in glMember.glMemberName, the GL name in glName, their name in glMember.glMemberName,
skipping to change at line 1978 skipping to change at line 2018
per 2 in section 4.3.1. per 2 in section 4.3.1.
3 - Upon receipt of the forwarded request, the GLO verifies the 3 - Upon receipt of the forwarded request, the GLO verifies the
prospective GL memberĘs signature on the inner most prospective GL memberĘs signature on the inner most
SignedData.PKIData and the GLAĘs signature on the outer layer. SignedData.PKIData and the GLAĘs signature on the outer layer.
If an EnvelopedData encapsulates the inner most layer (see If an EnvelopedData encapsulates the inner most layer (see
section 3.2.1.2 or 3.2.2), the GLO MUST decrypt the outer section 3.2.1.2 or 3.2.2), the GLO MUST decrypt the outer
layer prior to verifying the signature on the inner most layer prior to verifying the signature on the inner most
SignedData. SignedData.
Turner 40
Note: For cases where the GL is closed and either a) a Note: For cases where the GL is closed and either a) a
prospective member sends directly to the GLO or b) the GLA has prospective member sends directly to the GLO or b) the GLA has
mistakenly forwarded the request to the GLO, the GLO should mistakenly forwarded the request to the GLO, the GLO should
first determine whether to honor the request. first determine whether to honor the request.
3.a - If the signatures do not verify, the GLO MUST return a 3.a - Else the signatures do verify, the GLO MUST check to make
cMCStatusInfo response indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck.
3.b - Else the signatures do verify, the GLO MUST check to make
sure one of the names in the certificate used to sign the sure one of the names in the certificate used to sign the
request matches the name in glMember.glMemberName. request matches the name in glMember.glMemberName.
3.b.1 - If the names do not match, the GLO MAY send a 3.a.1 - If the names do not match, the GLO MAY send a
SignedData.PKIResponse.controlSequence message back to the SignedData.PKIResponse.controlSequence message back to the
prospective member with cMCStatusInfoEx.cMCStatus.failed
Turner 40
prospective member with cMCStatusInfo.cMCStatus.failed
indicating why the prospective member was denied in indicating why the prospective member was denied in
cMCStausInfo.statusString. This stops people from adding cMCStausInfo.statusString. This stops people from adding
people to GLs without their permission. people to GLs without their permission.
3.b.2 - Else the names do match, the GLO determines whether the 3.a.2 - Else the names do match, the GLO determines whether the
prospective member is allowed to be added. The mechanism prospective member is allowed to be added. The mechanism
is beyond the scope of this document; however, the GLO is beyond the scope of this document; however, the GLO
should check to see that the glMember.glMemberName is not should check to see that the glMember.glMemberName is not
already on the GL. already on the GL.
3.b.2.a - If the GLO determines the prospective member is not 3.a.2.a - If the GLO determines the prospective member is not
allowed to join the GL, the GLO MAY return a allowed to join the GL, the GLO MAY return a
SignedData.PKIResponse.controlSequence message back to SignedData.PKIResponse.controlSequence message back to
the prospective member with the prospective member with
cMCStatusInfo.cMCtatus.failed indicating why the cMCStatusInfoEx.cMCtatus.failed indicating why the
prospective member was denied in cMCStatus.statusString. prospective member was denied in cMCStatus.statusString.
3.b.2.b - Else GLO determines the prospective member is allowed to 3.a.2.b - Else GLO determines the prospective member is allowed to
join the GL, the GLO MUST verify the member's encryption join the GL, the GLO MUST verify the member's encryption
certificate. certificate.
3.b.2.b.1 - If the member's certificate does not verify, the GLO 3.a.2.b.1 - If the member's certificate does not verify, the GLO
MAY return a SignedData.PKIResponse.controlSequence MAY return a SignedData.PKIResponse.controlSequence
back to the prospective member with back to the prospective member with
cMCStatusInfo.cMCtatus.failed indicating that the cMCStatusInfoEx.cMCtatus.failed indicating that the
memberĘs encryption certificate did not verify in memberĘs encryption certificate did not verify in
cMCStatus.statusString. If the GLO does not return a cMCStatus.statusString. If the GLO does not return a
cMCStatusInfo response, the GLO MUST send a cMCStatusInfoEx response, the GLO MUST send a
SignedData.PKIData.controlSequence.glProvideCert SignedData.PKIData.controlSequence.glProvideCert
message to the prospective member requesting a new message to the prospective member requesting a new
encryption certificate (see section 4.10). encryption certificate (see section 4.10).
3.b.2.b.2 - Else the member's certificate does verify, the GLO 3.a.2.b.2 - Else the member's certificate does verify, the GLO
resubmits the glAddMember request (see section 3.2.5) resubmits the glAddMember request (see section 3.2.5)
to the GLA (1 in Figure 5). to the GLA (1 in Figure 5).
3.b.2.b.2.a - The GLO MUST apply confidentiality to the new 3.a.2.b.2.a - The GLO MUST apply confidentiality to the new
GLAddMember request by encapsulating the GLAddMember request by encapsulating the
SignedData.PKIData in an EnvelopedData if the SignedData.PKIData in an EnvelopedData if the
Turner 41
initial request was encapsulated in an EnvelopedData initial request was encapsulated in an EnvelopedData
(see section 3.2.1.2). (see section 3.2.1.2).
3.b.2.b.2.b - The GLO MAY also optionally apply another SignedData 3.a.2.b.2.b - The GLO MAY also optionally apply another SignedData
over the EnvelopedData (see section 3.2.1.2). over the EnvelopedData (see section 3.2.1.2).
4 - Processing continues as in 2 of section 4.3.1. 4 - Processing continues as in 2 of section 4.3.1.
Turner 41
4.4 Delete Members From GL 4.4 Delete Members From GL
To delete members from GLs, either the GLO or prospective non- To delete members from GLs, either the GLO or prospective non-
members use the glDeleteMember request. The GLA processes GLO and members use the glDeleteMember request. The GLA processes GLO and
prospective non-GL member requests differently. The GLO can submit prospective non-GL member requests differently. The GLO can submit
the request at any time to delete members from the GL, and the GLA, the request at any time to delete members from the GL, and the GLA,
once it has verified the request came from a registered GLO, should once it has verified the request came from a registered GLO, should
delete the member. If a prospective member sends the request, the delete the member. If a prospective member sends the request, the
GLA needs to determine how the GL is administered. When the GLO GLA needs to determine how the GL is administered. When the GLO
initially configured the GL, they set the GL to be unmanaged, initially configured the GL, they set the GL to be unmanaged,
skipping to change at line 2088 skipping to change at line 2123
+----------+ +----------+
Figure 6 - Member Deletion Figure 6 - Member Deletion
If the member is not removed from the GL, they will continue to If the member is not removed from the GL, they will continue to
receive and be able to decrypt data protected with the shared KEK receive and be able to decrypt data protected with the shared KEK
and will continue to receive rekeys. For unmanaged lists, there is and will continue to receive rekeys. For unmanaged lists, there is
no point to a group rekey because there is no guarantee that the no point to a group rekey because there is no guarantee that the
member requesting to be removed has not already added themselves member requesting to be removed has not already added themselves
back on the GL under a different name. For managed and closed GLs, back on the GL under a different name. For managed and closed GLs,
Turner 42
the GLO MUST take steps to ensure the member being deleted is not on the GLO MUST take steps to ensure the member being deleted is not on
the GL twice. After ensuring this, managed and closed GLs MUST be the GL twice. After ensuring this, managed and closed GLs MUST be
rekeyed to maintain the secrecy of the group. If the GLO is sure the rekeyed to maintain the secrecy of the group. If the GLO is sure the
member has been deleted the group rekey mechanism MUST be used to member has been deleted the group rekey mechanism MUST be used to
distribute the new key (see sections 4.5 and 5). distribute the new key (see sections 4.5 and 5).
Turner 42
4.4.1 GLO Initiated Deletions 4.4.1 GLO Initiated Deletions
The process for GLO initiated glDeleteMember requests is as follows: The process for GLO initiated glDeleteMember requests is as follows:
1 - The GLO collects the pertinent information for the member(s) 1 - The GLO collects the pertinent information for the member(s)
to be deleted (this MAY be done through an out of bands to be deleted (this MAY be done through an out of bands
means). The GLO then sends a means). The GLO then sends a
SignedData.PKIData.controlSequence with a separate SignedData.PKIData.controlSequence with a separate
glDeleteMember request for each member to the GLA (1 in Figure glDeleteMember request for each member to the GLA (1 in Figure
6). The GLO MUST include: the GL name in glName and the 6). The GLO MUST include: the GL name in glName and the
skipping to change at line 2126 skipping to change at line 2161
the EnvelopedData (see section 3.2.1.2). the EnvelopedData (see section 3.2.1.2).
2 - Upon receipt of the request, the GLA verifies the signature on 2 - Upon receipt of the request, the GLA verifies the signature on
the inner most SignedData.PKIData. If an additional SignedData the inner most SignedData.PKIData. If an additional SignedData
and/or EnvelopedData encapsulates the request (see section and/or EnvelopedData encapsulates the request (see section
3.2.1.2 or 3.2.2), the GLA MUST verify the outer signature 3.2.1.2 or 3.2.2), the GLA MUST verify the outer signature
and/or decrypt the outer layer prior to verifying the and/or decrypt the outer layer prior to verifying the
signature on the inner most SignedData. signature on the inner most SignedData.
2.a - If the signatures do not verify, the GLA MUST return a 2.a - If the signatures do not verify, the GLA MUST return a
cMCStatusInfo response indicating cMCStatus.failed and cMCStatusInfoEx response indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck. otherInfo.failInfo.badMessageCheck.
2.b - Else the signatures do verify, the GLA MUST make sure the GL 2.b - Else the signatures do verify, the GLA MUST make sure the GL
is supported by the GLA by checking that the glName matches is supported by the GLA by checking that the glName matches
a glName stored on the GLA. a glName stored on the GLA.
2.b.1 - If the glName is not supported by the GLA, the GLA MUST 2.b.1 - If the glName is not supported by the GLA, the GLA MUST
return a response indicating return a response indicating cMCStatusInfoEx with
glFailInfo.errorCode.invalidGLName. cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of
invalidGLName.
2.b.2 - Else the glName is supported by the GLA, the GLA MUST 2.b.2 - Else the glName is supported by the GLA, the GLA MUST
check to see if the glMemberName is present on the GL. check to see if the glMemberName is present on the GL.
Turner 43
2.b.2.a - If the glMemberName is not present on the GL, the GLA 2.b.2.a - If the glMemberName is not present on the GL, the GLA
MUST return a response indicating MUST return a response indicating cMCStatusInfoEx with
glFailInfo.errorCode.notAMember. cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of
notAMember.
2.b.2.b - Else the glMemberName is already on the GL, the GLA MUST 2.b.2.b - Else the glMemberName is already on the GL, the GLA MUST
check how the GL is administered. check how the GL is administered.
Turner 43
2.b.2.b.1 - If the GL is closed, the GLA MUST check that the 2.b.2.b.1 - If the GL is closed, the GLA MUST check that the
registered GLO signed the request by checking that one registered GLO signed the request by checking that one
of the names in the digital signature certificate used of the names in the digital signature certificate used
to sign the request matches the registered GLO. to sign the request matches the registered GLO.
2.b.2.b.1.a - If the names do not match, the GLA MUST return a 2.b.2.b.1.a - If the names do not match, the GLA MUST return a
response indicating glFailInfo.errorCode.closed. response indicating cMCStatusInfoEx with
cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of
closedGL.
2.b.2.b.1.b - Else the names do match, the GLA MUST return a 2.b.2.b.1.b - Else the names do match, the GLA MUST return a
glSuccessInfo indicating the glName, the cMCStatusInfoEx.cMCStatus.success (2 in Figure 5).
corresponding glIdentifier, an The GLA also takes administrative actions, which are
action.actionCode.deletedMember, and beyond the scope of this document, to delete the
action.glMemberName (2 in Figure 5). The GLA also member with the GL stored on the GLA. Note that he
takes administrative actions, which are beyond the GL MUST also be rekeyed as described in section 5.
scope of this document, to delete the member with
the GL stored on the GLA. Note that he GL MUST also
be rekeyed as described in section 5.
2.b.2.b.1.b.1 - The GLA MUST apply confidentiality to the response 2.b.2.b.1.b.1 - The GLA MUST apply confidentiality to the response
by encapsulating the SignedData.PKIData in an by encapsulating the SignedData.PKIData in an
EnvelopedData if the request was encapsulated in EnvelopedData if the request was encapsulated in
an EnvelopedData (see section 3.2.1.2). an EnvelopedData (see section 3.2.1.2).
2.b.2.b.1.b.2 - The GLA MAY also optionally apply another 2.b.2.b.1.b.2 - The GLA MAY also optionally apply another
SignedData over the EnvelopedData (see section SignedData over the EnvelopedData (see section
3.2.1.2). 3.2.1.2).
2.b.2.b.2 - Else the GL is managed, the GLA MUST check that either 2.b.2.b.2 - Else the GL is managed, the GLA MUST check that either
a registered GLO or the prospective member signed the a registered GLO or the prospective member signed the
request. For GLOs, one of the names in the certificate request. For GLOs, one of the names in the certificate
used to sign the request MUST match a registered GLO. used to sign the request MUST match a registered GLO.
For the prospective member, the name in For the prospective member, the name in
glMember.glMemberName MUST match one of the names in glMember.glMemberName MUST match one of the names in
the certificate used to sign the request. the certificate used to sign the request.
2.b.2.b.2.a - If the signer is neither a registered GLO nor the 2.b.2.b.2.a - If the signer is neither a registered GLO nor the
prospective GL member, the GLA MUST return a prospective GL member, the GLA MUST return a
response indicating glFailInfo.errorCode.noSpam. response indicating cMCStatusInfoEx with
cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of
noSpam.
Turner 44
2.b.2.b.2.b - Else the signer is a registered GLO, the GLA MUST 2.b.2.b.2.b - Else the signer is a registered GLO, the GLA MUST
return a glSuccessInfo to the GLO indicating the return a cMCStatusInfoEx.cMCStatus.success (2 in
glName, the corresponding glIdentifier, an Figure 6). The GLA also takes administrative
action.actionCode.deletedMember, and actions, which are beyond the scope of this
action.glMemberName (2 in Figure 6). The GLA also document, to delete the member with the GL stored on
takes administrative actions, which are beyond the the GLA. Note that the GL will also be rekeyed as
scope of this document, to delete the member with described in section 5.
the GL stored on the GLA. Note that the GL will also
be rekeyed as described in section 5.
2.b.2.b.2.b.1 - The GLA MUST apply confidentiality to the response 2.b.2.b.2.b.1 - The GLA MUST apply confidentiality to the response
by encapsulating the SignedData.PKIData in an by encapsulating the SignedData.PKIData in an
Turner 44
EnvelopedData if the request was encapsulated in EnvelopedData if the request was encapsulated in
an EnvelopedData (see section 3.2.1.2). an EnvelopedData (see section 3.2.1.2).
2.b.2.b.2.b.2 - The GLA MAY also optionally apply another 2.b.2.b.2.b.2 - The GLA MAY also optionally apply another
SignedData over the EnvelopedData (see section SignedData over the EnvelopedData (see section
3.2.1.2). 3.2.1.2).
2.b.2.b.2.c - Else the signer is the prospective member, the GLA 2.b.2.b.2.c - Else the signer is the prospective member, the GLA
forwards the glDeleteMember request (see section forwards the glDeleteMember request (see section
3.2.3) to the GLO (B{A} in Figure 6). If there is 3.2.3) to the GLO (B{A} in Figure 6). If there is
skipping to change at line 2236 skipping to change at line 2275
2.b.2.b.3 - Else the GL is unmanaged, the GLA MUST check that 2.b.2.b.3 - Else the GL is unmanaged, the GLA MUST check that
either a registered GLO or the prospective member either a registered GLO or the prospective member
signed the request. For GLOs, one of the names in the signed the request. For GLOs, one of the names in the
certificate used to sign the request MUST match the certificate used to sign the request MUST match the
name of a registered GLO. For the prospective member, name of a registered GLO. For the prospective member,
the name in glMember.glMemberName MUST match one of the name in glMember.glMemberName MUST match one of
the names in the certificate used to sign the request. the names in the certificate used to sign the request.
2.b.2.b.3.a - If the signer is neither the GLO nor the prospective 2.b.2.b.3.a - If the signer is neither the GLO nor the prospective
member, the GLA MUST return a response indicating member, the GLA MUST return a response indicating
glFailInfo.errorCode.noSpam. cMCStatusInfoEx with cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of
noSpam.
2.b.2.b.3.b - Else the signer is either a registered GLO or the 2.b.2.b.3.b - Else the signer is either a registered GLO or the
member, the GLA MUST return a glSuccessInfo member, the GLA MUST return a
indicating the glName, the corresponding cMCStatusInfoEx.cMCStatus.success to the GLO (2 in
glIdentifier, an action.actionCode.deletedMember,
and action.glMemberName to the GLO (2 in Figure 6) Turner 45
if the GLO signed the request and to the GL member Figure 6) if the GLO signed the request and to the
(3 in Figure 6) if the GL member signed the request. GL member (3 in Figure 6) if the GL member signed
The GLA also takes administrative actions, which are the request. The GLA also takes administrative
beyond the scope of this document, to delete the actions, which are beyond the scope of this
member with the GL stored on the GLA. document, to delete the member with the GL stored on
the GLA.
2.b.2.b.3.b.1 - The GLA MUST apply confidentiality to the response 2.b.2.b.3.b.1 - The GLA MUST apply confidentiality to the response
by encapsulating the SignedData.PKIData in an by encapsulating the SignedData.PKIData in an
EnvelopedData if the request was encapsulated in EnvelopedData if the request was encapsulated in
an EnvelopedData (see section 3.2.1.2). an EnvelopedData (see section 3.2.1.2).
Turner 45
2.b.2.b.3.b.2 - The GLA MAY also optionally apply another 2.b.2.b.3.b.2 - The GLA MAY also optionally apply another
SignedData over the EnvelopedData (see section SignedData over the EnvelopedData (see section
3.2.1.2). 3.2.1.2).
3 - Upon receipt of the glSuccessInfo or glFailInfo response, the 3 - Upon receipt of the cMCStatusInfoEx response, the GLO verifies
GLO verifies the GLA's signatures. If an additional SignedData the GLA's signatures. If an additional SignedData and/or
and/or EnvelopedData encapsulates the response (see section EnvelopedData encapsulates the response (see section 3.2.1.2
3.2.1.2 or 3.2.2), the GLO MUST verify the outer signature or 3.2.2), the GLO MUST verify the outer signature and/or
and/or decrypt the outer layer prior to verifying the decrypt the outer layer prior to verifying the signature on
signature on the inner most SignedData. the inner most SignedData.
3.a - If the signatures do not verify, the GLO MUST return a 3.a - If the signatures do not verify, the GLO MUST return a
cMCStatusInfo response indicating cMCStatus.failed and response indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck. otherInfo.failInfo.badMessageCheck.
3.b - Else the signatures do verify, the GLO MUST check that one 3.b - Else the signatures do verify, the GLO MUST check that one
of the names in the certificate used to sign the response of the names in the certificate used to sign the response
matches the name of the GL. matches the name of the GL.
3.b.1 ū If the GLĘs name does not match the name present in the 3.b.1 ū If the GLĘs name does not match the name present in the
certificate used to sign the message, the GLO should not certificate used to sign the message, the GLO should not
believe the response. believe the response.
3.b.2 ū Else the GLĘs name does match the name present in the 3.b.2 ū Else the GLĘs name does match the name present in the
certificate and: certificate and:
3.b.2.a - If the signatures do verify and the response is 3.b.2.a - If the signatures do verify and the response is
glSuccessInfo, the GLO has deleted the member from the GL. cMCStatusInfoEx.cMCStatus.success, the GLO has deleted
If member was deleted from a managed list and the original the member from the GL. If member was deleted from a
request was signed by the member, the GLO MUST send a managed list and the original request was signed by the
cMCStatusInfo.cMCStatus.success to the GL member. member, the GLO MUST send a
cMCStatusInfoEx.cMCStatus.success to the GL member.
3.b.2.b - Else the GLO received a glFailInfo, for any reason, the 3.b.2.b - Else the GLO received a cMCStatusInfoEx.cMCStatus.failed
GLO may reattempt to delete the member from the GL using for any reason, the GLO may reattempt to delete the
the information provided in the glFailInfo response. member from the GL using the information provided in the
response.
4 - Upon receipt of the glSuccessInfo, glFailInfo, or cMCStatus 4 - Upon receipt of the cMCStatusInfoEx response, the prospective
response, the prospective member verifies the GLA's member verifies the GLA's signature(s) or GLOĘs signature(s).
signature(s) or GLOĘs signature(s). If an additional
SignedData and/or EnvelopedData encapsulates the response (see
section 3.2.1.2 or 3.2.2), the GLO MUST verify the outer
signature and/or decrypt the outer layer prior to verifying
the signature on the inner most SignedData.
4.a - If the signatures do not verify, the prospective member MUST Turner 46
return a cMCStatusInfo response indicating cMCStatus.failed If an additional SignedData and/or EnvelopedData encapsulates
and otherInfo.failInfo.badMessageCheck. the response (see section 3.2.1.2 or 3.2.2), the GLO MUST
verify the outer signature and/or decrypt the outer layer
prior to verifying the signature on the inner most SignedData.
4.b - Else the signatures do verify, the GL member MUST check that 4.a - Else the signatures do verify, the GL member MUST check that
one of the names in the certificate used to sign the one of the names in the certificate used to sign the
response matches the name of the GL. response matches the name of the GL.
Turner 46 4.a.1 ū If the GLĘs name does not match the name present in the
4.b.1 ū If the GLĘs name does not match the name present in the
certificate used to sign the message, the GL member should certificate used to sign the message, the GL member should
not believe the response. not believe the response.
4.b.2 ū Else the GLĘs name does match the name present in the 4.a.2 ū Else the GLĘs name does match the name present in the
certificate and: certificate and:
4.b.2.a - If the signature(s) does(do) verify, the prospective 4.a.2.a - If the signature(s) does(do) verify, the prospective
member has been deleted from the GL. member has been deleted from the GL.
4.b.2.b - Else the prospective member received a glFailInfo, for 4.a.2.b - Else the prospective member received a
any reason, the prospective member MAY reattempt to delete cMCStatusInfoEx.cMCStatus.failed for any reason, the
themselves from the GL using the information provided in prospective member MAY reattempt to delete themselves
the glFailInfo response. from the GL using the information provided in the
response.
4.4.2 Member Initiated Deletions 4.4.2 Member Initiated Deletions
The process for prospective non-member initiated glDeleteMember The process for prospective non-member initiated glDeleteMember
requests is as follows: requests is as follows:
1 - The prospective non-GL member sends a 1 - The prospective non-GL member sends a
SignedData.PKIData.controlSequence.glDeleteMember request to SignedData.PKIData.controlSequence.glDeleteMember request to
the GLA (A in Figure 6). The prospective non-GL member MUST the GLA (A in Figure 6). The prospective non-GL member MUST
include: the GL name in glName and their name in include: the GL name in glName and their name in
skipping to change at line 2349 skipping to change at line 2389
1.b - The prospective non-GL member MAY also optionally apply 1.b - The prospective non-GL member MAY also optionally apply
another SignedData over the EnvelopedData (see section another SignedData over the EnvelopedData (see section
3.2.1.2). 3.2.1.2).
2 - Upon receipt of the request, the GLA verifies the request as 2 - Upon receipt of the request, the GLA verifies the request as
per 2 in section 4.4.1. per 2 in section 4.4.1.
3 - Upon receipt of the forwarded request, the GLO verifies the 3 - Upon receipt of the forwarded request, the GLO verifies the
prospective non-memberĘs signature on the inner most prospective non-memberĘs signature on the inner most
SignedData.PKIData and the GLAĘs signature on the outer layer. SignedData.PKIData and the GLAĘs signature on the outer layer.
Turner 47
If an EnvelopedData encapsulates the inner most layer (see If an EnvelopedData encapsulates the inner most layer (see
section 3.2.1.2 or 3.2.2), the GLO MUST decrypt the outer section 3.2.1.2 or 3.2.2), the GLO MUST decrypt the outer
layer prior to verifying the signature on the inner most layer prior to verifying the signature on the inner most
SignedData. SignedData.
Note: For cases where the GL is closed and either a) a Note: For cases where the GL is closed and either a) a
prospective member sends directly to the GLO or b) the GLA has prospective member sends directly to the GLO or b) the GLA has
mistakenly forwarded the request to the GLO, the GLO should mistakenly forwarded the request to the GLO, the GLO should
first determine whether to honor the request. first determine whether to honor the request.
Turner 47
3.a - If the signatures do not verify, the GLO MUST return a 3.a - If the signatures do not verify, the GLO MUST return a
cMCStatusInfo response indicating cMCStatus.failed and cMCStatusInfoEx response indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck. otherInfo.failInfo.badMessageCheck.
3.b - Else the signatures do verify, the GLO MUST check to make 3.b - Else the signatures do verify, the GLO MUST check to make
sure one of the names in the certificates used to sign the sure one of the names in the certificates used to sign the
request matches the name in glMemberToDelete. request matches the name in glMemberToDelete.
3.b.1 - If the names do not match, the GLO MAY send a 3.b.1 - If the names do not match, the GLO MAY send a
SignedData.PKIResponse.controlSequence message back to the SignedData.PKIResponse.controlSequence message back to the
prospective member with cMCStatusInfo.cMCtatus.failed prospective member with cMCStatusInfoEx.cMCtatus.failed
indicating why the prospective member was denied in indicating why the prospective member was denied in
cMCStatusInfo.statusString. This stops people from adding cMCStatusInfoEx.statusString. This stops people from
people to GLs without their permission. adding people to GLs without their permission.
3.b.2 - Else the names do match, the GLO resubmits the 3.b.2 - Else the names do match, the GLO resubmits the
glDeleteMember request (see section 3.2.5) to the GLA (1 glDeleteMember request (see section 3.2.5) to the GLA (1
in Figure 6). The GLO MUST make sure the glMemberName is in Figure 6). The GLO MUST make sure the glMemberName is
already on the GL. The GLO MUST also generate a glRekey already on the GL. The GLO MUST also generate a glRekey
request and include it with the GLDeleteMember request request and include it with the GLDeleteMember request
(see section 4.5). (see section 4.5).
3.b.2.a - The GLO MUST apply confidentiality to the new 3.b.2.a - The GLO MUST apply confidentiality to the new
GLDeleteMember request by encapsulating the GLDeleteMember request by encapsulating the
skipping to change at line 2402 skipping to change at line 2443
4.5 Request Rekey Of GL 4.5 Request Rekey Of GL
From time to time the GL will need to be rekeyed. Some situations From time to time the GL will need to be rekeyed. Some situations
are as follows: are as follows:
- When a member is removed from a closed or managed GL. In this - When a member is removed from a closed or managed GL. In this
case, the PKIData.controlSequence containing the glDeleteMember case, the PKIData.controlSequence containing the glDeleteMember
should contain a glRekey request. should contain a glRekey request.
Turner 48
- Depending on policy, when a member is removed from an unmanaged - Depending on policy, when a member is removed from an unmanaged
GL. If the policy is to rekey the GL, the GL. If the policy is to rekey the GL, the
PKIData.controlSequence containing the glDeleteMember could also PKIData.controlSequence containing the glDeleteMember could also
contain a glRekey request or an out of bands means could be used contain a glRekey request or an out of bands means could be used
to tell the GLA to rekey the GL. Rekeying of unmanaged GLs when to tell the GLA to rekey the GL. Rekeying of unmanaged GLs when
members are deleted is not advised. members are deleted is not advised.
- When the current shared KEK has been compromised. - When the current shared KEK has been compromised.
Turner 48
- When the current shared KEK is about to expire. - When the current shared KEK is about to expire.
- If the GLO controls the GL rekey, the GLA should not assume - If the GLO controls the GL rekey, the GLA should not assume
that a new shared KEK should be distributed, but instead wait that a new shared KEK should be distributed, but instead wait
for the glRekey message. for the glRekey message.
- If the GLA controls the GL rekey, the GLA should initiate a - If the GLA controls the GL rekey, the GLA should initiate a
glKey message as specified in section 5. glKey message as specified in section 5.
If the generationCounter (see section 3.1.1) is set to a value If the generationCounter (see section 3.1.1) is set to a value
skipping to change at line 2453 skipping to change at line 2494
4.5.1 GLO Initiated Rekey Requests 4.5.1 GLO Initiated Rekey Requests
The process for GLO initiated glRekey requests is as follows: The process for GLO initiated glRekey requests is as follows:
1 - The GLO sends a SignedData.PKIData.controlSequence.glRekey 1 - The GLO sends a SignedData.PKIData.controlSequence.glRekey
request to the GLA (1 in Figure 7). The GLO MUST include the request to the GLA (1 in Figure 7). The GLO MUST include the
glName. If glAdministration and glKeyNewAttributes are omitted glName. If glAdministration and glKeyNewAttributes are omitted
then there is no change from the previously registered GL then there is no change from the previously registered GL
values for these fields. If the GLO wants to force a rekey for values for these fields. If the GLO wants to force a rekey for
Turner 49
all outstanding shared KEKs it includes the glRekeyAllGLKeys all outstanding shared KEKs it includes the glRekeyAllGLKeys
set to TRUE. set to TRUE.
1.a - The GLO MAY optionally apply confidentiality to the request 1.a - The GLO MAY optionally apply confidentiality to the request
by encapsulating the SignedData.PKIData in an EnvelopedData by encapsulating the SignedData.PKIData in an EnvelopedData
(see section 3.2.1.2). (see section 3.2.1.2).
1.b - The GLO MAY also optionally apply another SignedData over 1.b - The GLO MAY also optionally apply another SignedData over
the EnvelopedData (see section 3.2.1.2). the EnvelopedData (see section 3.2.1.2).
Turner 49
2 - Upon receipt of the request, the GLA verifies the signature on 2 - Upon receipt of the request, the GLA verifies the signature on
the inner most SignedData.PKIData. If an additional SignedData the inner most SignedData.PKIData. If an additional SignedData
and/or EnvelopedData encapsulates the request (see section and/or EnvelopedData encapsulates the request (see section
3.2.1.2 or 3.2.2), the GLA MUST verify the outer signature 3.2.1.2 or 3.2.2), the GLA MUST verify the outer signature
and/or decrypt the outer layer prior to verifying the and/or decrypt the outer layer prior to verifying the
signature on the inner most SignedData. signature on the inner most SignedData.
2.a - If the signatures do not verify, the GLA MUST return a 2.a - If the signatures do not verify, the GLA MUST return a
cMCStatusInfo response indicating cMCStatus.failed and cMCStatusInfoEx response indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck. otherInfo.failInfo.badMessageCheck.
2.b - Else the signatures do verify, the GLA MUST make sure the GL 2.b - Else the signatures do verify, the GLA MUST make sure the GL
is supported by the GLA by checking that the glName matches is supported by the GLA by checking that the glName matches
a glName stored on the GLA. a glName stored on the GLA.
2.b.1 - If the glName present does not match a GL stored on the 2.b.1 - If the glName present does not match a GL stored on the
GLA, the GLA MUST return a response indicating GLA, the GLA MUST return a response indicating
glFailInfo.errorCode.invalidGLName. cMCStatusInfoEx with cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of
invalidGLName.
2.b.2 - Else the glName present does match a GL stored on the GLA, 2.b.2 - Else the glName present does match a GL stored on the GLA,
the GLA MUST check that a registered GLO signed the the GLA MUST check that a registered GLO signed the
request by checking that one of the names in the request by checking that one of the names in the
certificate used to sign the request is a registered GLO. certificate used to sign the request is a registered GLO.
2.b.2.a - If the names do not match, the GLA MUST return a 2.b.2.a - If the names do not match, the GLA MUST return a
response indicating glFailInfo.errorCode.noGLONameMatch. response indicating cMCStatusInfoEx with
cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of
noGLONameMatch.
2.b.2.b - Else the names do match, the GLA MUST check the 2.b.2.b - Else the names do match, the GLA MUST check the
glNewKeyAttribute values. glNewKeyAttribute values.
2.b.2.b.1 - If the new value for requestedAlgorithm is not 2.b.2.b.1 - If the new value for requestedAlgorithm is not
supported, the GLA MUST return a response indicating supported, the GLA MUST return a response indicating
glFailInfo.errorCode.unsupportedAlgorithm cMCStatusInfoEx with cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of
unsupportedAlgorithm
Turner 50
2.b.2.b.2 - Else the new value duration is not supportable, 2.b.2.b.2 - Else the new value duration is not supportable,
determining this is beyond the scope this document, determining this is beyond the scope this document,
the GLA MUST return a response indicating the GLA MUST return a response indicating
glFailInfo.errorCode.unsupportedDuration. cMCStatusInfoEx with cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of
unsupportedDuration.
2.b.2.b.3 - Else the GL is not supportable for other reasons, 2.b.2.b.3 - Else the GL is not supportable for other reasons,
which the GLA does not wish to disclose, the GLA MUST which the GLA does not wish to disclose, the GLA MUST
return a response indicating return a response indicating cMCStatusInfoEx with
glFailInfo.errorCode.unspecified. cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of
unspecified.
2.b.2.b.4 - Else the new requestedAlgorithm and duration are 2.b.2.b.4 - Else the new requestedAlgorithm and duration are
supportable or the glNewKeyAttributes was omitted, the supportable or the glNewKeyAttributes was omitted, the
GLA MUST return a glSuccessInfo to the GLO indicating GLA MUST return a cMCStatusInfoEx.cMCStatus.success (2
the glName, the new glIdentifier, and an in Figure 7). The GLA also uses the glKey message to
action.actionCode.rekeyedGL (2 in Figure 7). The GLA distribute the rekey shared KEK (see section 5).
also uses the glKey message to distribute the rekey
shared KEK (see section 5).
Turner 50
2.b.2.b.4.a - The GLA MUST apply confidentiality to response by 2.b.2.b.4.a - The GLA MUST apply confidentiality to response by
encapsulating the SignedData.PKIData in an encapsulating the SignedData.PKIData in an
EnvelopedData if the request was encapsulated in an EnvelopedData if the request was encapsulated in an
EnvelopedData (see section 3.2.1.2). EnvelopedData (see section 3.2.1.2).
2.b.2.b.4.b - The GLA MAY also optionally apply another SignedData 2.b.2.b.4.b - The GLA MAY also optionally apply another SignedData
over the EnvelopedData (see section 3.2.1.2). over the EnvelopedData (see section 3.2.1.2).
3 - Upon receipt of the glSuccessInfo or glFailInfo response, the 3 - Upon receipt of the cMCStatusInfoEx response, the GLO verifies
GLO verifies the GLA's signature(s). If an additional the GLA's signature(s). If an additional SignedData and/or
SignedData and/or EnvelopedData encapsulates the forwarded EnvelopedData encapsulates the forwarded response (see section
response (see section 3.2.1.2 or 3.2.2), the GLO MUST verify 3.2.1.2 or 3.2.2), the GLO MUST verify the outer signature
the outer signature and/or decrypt the forwarded response and/or decrypt the forwarded response prior to verifying the
prior to verifying the signature on the inner most SignedData. signature on the inner most SignedData.
3.a - If the signatures do not verify, the GLO MUST return a
cMCStatusInfo response indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck.
3.b - Else the signatures do verify, the GLO MUST check that one 3.a - Else the signatures do verify, the GLO MUST check that one
of the names in the certificate used to sign the response of the names in the certificate used to sign the response
matches the name of the GL. matches the name of the GL.
3.b.1 ū If the GLĘs name does not match the name present in the 3.a.1 ū If the GLĘs name does not match the name present in the
certificate used to sign the message, the GLO should not certificate used to sign the message, the GLO should not
believe the response. believe the response.
3.b.2 ū Else the GLĘs name does match the name present in the 3.a.2 ū Else the GLĘs name does match the name present in the
certificate and: certificate and:
3.b.2.a - If the signatures verifies and the response is 3.a.2.a - If the signatures verifies and the response is
glSuccessInfo, the GLO has successfully rekeyed the GL. cMCStatusInfoEx.cMCStatus.success, the GLO has
successfully rekeyed the GL.
3.b.2.b - Else the GLO received a glFailInfo, for any reason, the Turner 51
GLO may reattempt to rekey the GL using the information 3.a.2.b - Else the GLO received a cMCStatusInfoEx.cMCStatus.failed
provided in the glFailInfo response. for any reason, the GLO may reattempt to rekey the GL
using the information provided in the response.
4.5.2 GLA Initiated Rekey Requests 4.5.2 GLA Initiated Rekey Requests
If the GLA is in charge of rekeying the GL the GLA will If the GLA is in charge of rekeying the GL the GLA will
automatically issue a glKey message (see section 5). In addition the automatically issue a glKey message (see section 5). In addition the
GLA will generate a glSuccessInfo to indicate to the GL that a GLA will generate a cMCStatusInfoEx to indicate to the GL that a
successful rekey has occurred. The process for GLA initiated rekey successful rekey has occurred. The process for GLA initiated rekey
is as follows: is as follows:
1 - The GLA MUST generate for all GLOs a 1 - The GLA MUST generate for all GLOs a
SignedData.PKIData.controlSequence.glSuccessInfo indicating SignedData.PKIData.controlSequence.cMCStatusInfoEx.cMCStatus.s
the glName, the new glIdentifier, and actionCode.rekeyedGL (A uccess (A in Figure 7).
in Figure 7). glMemberName and glOwnerName are omitted.
Turner 51
1.a - The GLA MAY optionally apply confidentiality to the request 1.a - The GLA MAY optionally apply confidentiality to the request
by encapsulating the SignedData.PKIData in an EnvelopedData by encapsulating the SignedData.PKIData in an EnvelopedData
(see section 3.2.1.2). (see section 3.2.1.2).
1.b - The GLA MAY also optionally apply another SignedData over 1.b - The GLA MAY also optionally apply another SignedData over
the EnvelopedData (see section 3.2.1.2). the EnvelopedData (see section 3.2.1.2).
2 - Upon receipt of the glSuccessInfo response, the GLO verifies 2 - Upon receipt of the cMCStatusInfoEx.cMCStatus.success
the GLA's signature(s). If an additional SignedData and/or response, the GLO verifies the GLA's signature(s). If an
EnvelopedData encapsulates the forwarded response (see section additional SignedData and/or EnvelopedData encapsulates the
3.2.1.2 or 3.2.2), the GLO MUST verify the outer signature forwarded response (see section 3.2.1.2 or 3.2.2), the GLO
and/or decrypt the outer layer prior to verifying the MUST verify the outer signature and/or decrypt the outer layer
signature on the inner most SignedData. prior to verifying the signature on the inner most SignedData.
2.a - If the signatures do not verify, the GLO MUST return a
cMCStatusInfo response indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck.
2.b - Else the signatures do verify, the GLO MUST check that one 2.a - Else the signatures do verify, the GLO MUST check that one
of the names in the certificate used to sign the response of the names in the certificate used to sign the response
matches the name of the GL. matches the name of the GL.
2.b.1 ū If the GLĘs name does not match the name present in the 2.a.1 ū If the GLĘs name does not match the name present in the
certificate used to sign the message, the GLO should not certificate used to sign the message, the GLO should not
believe the response. believe the response.
2.b.2 ū Else the GLĘs name does match the name present in the 2.a.2 ū Else the GLĘs name does match the name present in the
certificate and and the response is glSuccessInfo, the GLO certificate and and the response is
knows the GLA has successfully rekeyed the GL. cMCStatusInfoEx.cMCStatus.success, the GLO knows the GLA
has successfully rekeyed the GL.
4.6 Change GLO 4.6 Change GLO
Management of managed and closed GLs can become difficult for one Management of managed and closed GLs can become difficult for one
GLO if the GL membership grows large. To support distributing the GLO if the GL membership grows large. To support distributing the
workload, GLAs support having GLs be managed by multiple GLOs. The workload, GLAs support having GLs be managed by multiple GLOs. The
glAddOwner and glRemoveOwner messages are designed to support adding glAddOwner and glRemoveOwner messages are designed to support adding
and removing registered GLOs. Figure 8 depicts the protocol and removing registered GLOs. Figure 8 depicts the protocol
Turner 52
interactions to send glAddOwner and glRemoveOwner messages and the interactions to send glAddOwner and glRemoveOwner messages and the
resulting response messages. resulting response messages.
+-----+ 1 2 +-----+ +-----+ 1 2 +-----+
| GLA | <-------> | GLO | | GLA | <-------> | GLO |
+-----+ +-----+ +-----+ +-----+
Figure 8 - GLO Add & Delete Owners Figure 8 - GLO Add & Delete Owners
The process for glAddOwner and glDeleteOwner is as follows: The process for glAddOwner and glDeleteOwner is as follows:
1 - The GLO sends a SignedData.PKIData.controlSequence.glAddOwner 1 - The GLO sends a SignedData.PKIData.controlSequence.glAddOwner
or glRemoveOwner request to the GLA (1 in Figure 8). The GLO or glRemoveOwner request to the GLA (1 in Figure 8). The GLO
Turner 52
MUST include: the GL name in glName, the GLOĘs name in MUST include: the GL name in glName, the GLOĘs name in
glOwnerName, and the GLOĘs address in glOwnerAddress. glOwnerName, and the GLOĘs address in glOwnerAddress.
1.a - The GLO MAY optionally apply confidentiality to the request 1.a - The GLO MAY optionally apply confidentiality to the request
by encapsulating the SignedData.PKIData in an EnvelopedData by encapsulating the SignedData.PKIData in an EnvelopedData
(see section 3.2.1.2). (see section 3.2.1.2).
1.b - The GLO MAY also optionally apply another SignedData over 1.b - The GLO MAY also optionally apply another SignedData over
the EnvelopedData (see section 3.2.1.2). the EnvelopedData (see section 3.2.1.2).
2 - Upon receipt of the glAddOwner or glRemoveOwner request, the 2 - Upon receipt of the glAddOwner or glRemoveOwner request, the
GLA verifies the GLO's signature(s). If an additional GLA verifies the GLO's signature(s). If an additional
SignedData and/or EnvelopedData encapsulates the request (see SignedData and/or EnvelopedData encapsulates the request (see
section 3.2.1.2 or 3.2.2), the GLA MUST verify the outer section 3.2.1.2 or 3.2.2), the GLA MUST verify the outer
signature and/or decrypt the outer layer prior to verifying signature and/or decrypt the outer layer prior to verifying
the signature on the inner most SignedData. the signature on the inner most SignedData.
2.a - If the signatures do not verify, the GLA MUST return a 2.a - If the signatures do not verify, the GLA MUST return a
cMCStatusInfo response indicating cMCStatus.failed and cMCStatusInfoEx response indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck. otherInfo.failInfo.badMessageCheck.
2.b - Else the signatures do verify, the GLA MUST make sure the GL 2.b - Else the signatures do verify, the GLA MUST make sure the GL
is supported by checking that the glName matches a glName is supported by checking that the glName matches a glName
stored on the GLA. stored on the GLA.
2.b.1 - If the glName is not supported by the GLA, the GLA MUST 2.b.1 - If the glName is not supported by the GLA, the GLA MUST
return a response indicating return a response indicating cMCStatusInfoEx with
glFailInfo.errorCode.invalidGLName. cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of
invalidGLName.
2.b.2 - Else the glName is supported by the GLA, the GLA MUST 2.b.2 - Else the glName is supported by the GLA, the GLA MUST
ensure a registered GLO signed the glAddOwner or ensure a registered GLO signed the glAddOwner or
glRemoveOwner request by checking that one of the names glRemoveOwner request by checking that one of the names
present in the digital signature certificate used to sign present in the digital signature certificate used to sign
the glAddOwner or glDeleteOwner request matches the name the glAddOwner or glDeleteOwner request matches the name
of a registered GLO. of a registered GLO.
Turner 53
2.b.2.a - If the names do not match, the GLA MUST return a 2.b.2.a - If the names do not match, the GLA MUST return a
response indicating glFailInfo.errorCode.noGLONameMatch. response indicating cMCStatusInfoEx with
cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of
noGLONameMatch.
2.b.2.b - Else the names do match, the GLA MUST return a 2.b.2.b - Else the names do match, the GLA MUST return a
glSuccessInfo indicating the glName, the corresponding cMCStatusInfoEx.cMCStatus.success (2 in Figure 4). The
glIdentifier (for glAddOwner), an
action.actionCode.addedGLO or removedGLO, and the
respective GLO name in glOwnerName (2 in Figure 4). The
GLA MUST also take administrative actions to associate GLA MUST also take administrative actions to associate
the new glOwnerName with the GL in the case of the new glOwnerName with the GL in the case of
glAddOwner or to disassociate the old glOwnerName with glAddOwner or to disassociate the old glOwnerName with
the GL in the cased of glRemoveOwner. the GL in the cased of glRemoveOwner.
2.b.2.b.1 - The GLA MUST apply confidentiality to the response by 2.b.2.b.1 - The GLA MUST apply confidentiality to the response by
encapsulating the SignedData.PKIResponse in an encapsulating the SignedData.PKIResponse in an
Turner 53
EnvelopedData if the request was encapsulated in an EnvelopedData if the request was encapsulated in an
EnvelopedData (see section 3.2.1.2). EnvelopedData (see section 3.2.1.2).
2.b.2.b.2 - The GLA MAY also optionally apply another SignedData 2.b.2.b.2 - The GLA MAY also optionally apply another SignedData
over the EnvelopedData (see section 3.2.1.2). over the EnvelopedData (see section 3.2.1.2).
3 - Upon receipt of the glSuccessInfo or glFailInfo response, the 3 - Upon receipt of the cMCStatusInfoEx response, the GLO verifies
GLO verifies the GLA's signature(s). If an additional the GLA's signature(s). If an additional SignedData and/or
SignedData and/or EnvelopedData encapsulates the response (see EnvelopedData encapsulates the response (see section 3.2.1.2
section 3.2.1.2 or 3.2.2), the GLO MUST verify the outer or 3.2.2), the GLO MUST verify the outer signature and/or
signature and/or decrypt the outer layer prior to verifying decrypt the outer layer prior to verifying the signature on
the signature on the inner most SignedData. the inner most SignedData.
3.a - If the signatures do not verify, the GLO MUST return a
cMCStatusInfo response indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck.
3.b - Else the signatures do verify, the GLO MUST check that one 3.a - Else the signatures do verify, the GLO MUST check that one
of the names in the certificate used to sign the response of the names in the certificate used to sign the response
matches the name of the GL. matches the name of the GL.
3.b.1 ū If the GLĘs name does not match the name present in the 3.a.1 ū If the GLĘs name does not match the name present in the
certificate used to sign the message, the GLO should not certificate used to sign the message, the GLO should not
believe the response. believe the response.
3.b.2 ū Else the GLĘs name does match the name present in the 3.a.2 ū Else the GLĘs name does match the name present in the
certificate and: certificate and:
3.b.2.a - If the signatures do verify and the response was 3.a.2.a - If the signatures do verify and the response was
glSuccessInfo, the GLO has successfully added or removed cMCStatusInfoEx.cMCStatus.success, the GLO has
the GLO. successfully added or removed the GLO.
3.b.2.b - Else the signatures do verify and the response was 3.a.2.b - Else the signatures do verify and the response was
glFailInfo, the GLO MAY reattempt to add or delete the GLO cMCStatusInfoEx.cMCStatus.failed for any reason, the GLO
using the information provided in the glFailInfo response. MAY reattempt to add or delete the GLO using the
information provided in the response.
Turner 54
4.7 Indicate KEK Compromise 4.7 Indicate KEK Compromise
The will be times when the shared KEK is compromised. GL members and The will be times when the shared KEK is compromised. GL members and
GLOs use glkCompromise to tell the GLA that the shared KEK has been GLOs use glkCompromise to tell the GLA that the shared KEK has been
compromised. Figure 9 depicts the protocol interactions for GL Key compromised. Figure 9 depicts the protocol interactions for GL Key
Compromise. Compromise.
Turner 54
+-----+ 2{1} 4 +----------+ +-----+ 2{1} 4 +----------+
| GLO | <----------+ +-------> | Member 1 | | GLO | <----------+ +-------> | Member 1 |
+-----+ 5,3{1} | | +----------+ +-----+ 5,3{1} | | +----------+
+-----+ <----------+ | 4 +----------+ +-----+ <----------+ | 4 +----------+
| GLA | 1 +-------> | ... | | GLA | 1 +-------> | ... |
+-----+ <---------------+ +----------+ +-----+ <---------------+ +----------+
| 4 +----------+ | 4 +----------+
+-------> | Member n | +-------> | Member n |
+----------+ +----------+
skipping to change at line 2756 skipping to change at line 2799
over the EnvelopedData (see section 3.2.1.2). over the EnvelopedData (see section 3.2.1.2).
2 - Upon receipt of the glkCompromise request, the GLA verifies 2 - Upon receipt of the glkCompromise request, the GLA verifies
the GL member's signature(s). If an additional SignedData the GL member's signature(s). If an additional SignedData
and/or EnvelopedData encapsulates the request (see section and/or EnvelopedData encapsulates the request (see section
3.2.1.2 or 3.2.2), the GLA MUST verify the outer signature 3.2.1.2 or 3.2.2), the GLA MUST verify the outer signature
and/or decrypt the outer layer prior to verifying the and/or decrypt the outer layer prior to verifying the
signature on the inner most SignedData. signature on the inner most SignedData.
2.a - If the signatures do not verify, the GLA MUST return a 2.a - If the signatures do not verify, the GLA MUST return a
cMCStatusInfo response indicating cMCStatus.failed and cMCStatusInfoEx response indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck. otherInfo.failInfo.badMessageCheck.
2.b - Else the signatures do verify, the GLA MUST make sure the GL 2.b - Else the signatures do verify, the GLA MUST make sure the GL
is supported by checking that the indicated GL name matches is supported by checking that the indicated GL name matches
a glName stored on the GLA. a glName stored on the GLA.
Turner 55
2.b.1 - If the glName is not supported by the GLA, the GLA MUST 2.b.1 - If the glName is not supported by the GLA, the GLA MUST
return a response indicating return a response indicating cMCStatusInfoEx with
glFailInfo.errorCode.invalidGLName. cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of
invalidGLName.
2.b.2 - Else the glName is supported by the GLA, the GLA MUST 2.b.2 - Else the glName is supported by the GLA, the GLA MUST
check who signed the request. For GLOs, one of the names check who signed the request. For GLOs, one of the names
Turner 55
in the certificate used to sign the request MUST match a in the certificate used to sign the request MUST match a
registered GLO. For the prospective member, the name in registered GLO. For the prospective member, the name in
glMember.glMemberName MUST match one of the names in the glMember.glMemberName MUST match one of the names in the
certificate used to sign the request. certificate used to sign the request.
2.b.2.a - If the GLO signed the request, the GLA MUST generate a 2.b.2.a - If the GLO signed the request, the GLA MUST generate a
glKey message as described in section 5 to rekey the GL glKey message as described in section 5 to rekey the GL
(4 in Figure 9). (4 in Figure 9).
2.b.2.b - Else anyone else signed the request, the GLA MUST 2.b.2.b - Else anyone else signed the request, the GLA MUST
skipping to change at line 2814 skipping to change at line 2858
1.a.2 - The GLO MAY also optionally apply another SignedData over 1.a.2 - The GLO MAY also optionally apply another SignedData over
the EnvelopedData (see section 3.2.1.2). the EnvelopedData (see section 3.2.1.2).
1.b - Verifies the GLAĘs and GL memberĘs signatures on the 1.b - Verifies the GLAĘs and GL memberĘs signatures on the
forwarded glkCompromise message. If an additional SignedData forwarded glkCompromise message. If an additional SignedData
and/or EnvelopedData encapsulates the request (see section and/or EnvelopedData encapsulates the request (see section
3.2.1.2 or 3.2.2), the GLO MUST verify the outer signature 3.2.1.2 or 3.2.2), the GLO MUST verify the outer signature
and/or decrypt the outer layer prior to verifying the and/or decrypt the outer layer prior to verifying the
signature on the inner most SignedData. signature on the inner most SignedData.
Turner 56
1.b.1 - If the signatures do not verify, the GLO MUST return a 1.b.1 - If the signatures do not verify, the GLO MUST return a
cMCStatusInfo response indicating cMCStatus.failed and cMCStatusInfoEx response indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck. otherInfo.failInfo.badMessageCheck.
1.b.1.a - If the signatures do verify, the GLO MUST check the 1.b.1.a - If the signatures do verify, the GLO MUST check the
names in the certificate match the name of the signer names in the certificate match the name of the signer
(i.e., the name in the certificate used to sign the GL (i.e., the name in the certificate used to sign the GL
memberĘs request is the GL member). memberĘs request is the GL member).
Turner 56
1.b.1.a.1 ū If either name does not match, the GLO should not 1.b.1.a.1 ū If either name does not match, the GLO should not
trust the signer and it should not forward the message trust the signer and it should not forward the message
to the GLA. to the GLA.
1.b.1.a.2 ū Else the names do math, the signatures do verify, the 1.b.1.a.2 ū Else the names do match, the signatures do verify, the
GLO MUST determine whether to forward the GLO MUST determine whether to forward the
glkCompromise message back to the GLA (3{1} in Figure glkCompromise message back to the GLA (3{1} in Figure
9). Further processing by the GLA is in 2 of section 9). Further processing by the GLA is in 2 of section
4.7.1. The GLO MAY also return a response to the 4.7.1. The GLO MAY also return a response to the
prospective member with cMCStatusInfo.cMCtatus.success prospective member with
indicating that the glkCompromise message was cMCStatusInfoEx.cMCtatus.success indicating that the
successfully received. glkCompromise message was successfully received.
4.8 Request KEK Refresh 4.8 Request KEK Refresh
There will be times when GL members have misplaced their shared KEK. There will be times when GL members have misplaced their shared KEK.
The shared KEK is not compromised and a rekey of the entire GL is The shared KEK is not compromised and a rekey of the entire GL is
not necessary. GL members use the glkRefresh message to request that not necessary. GL members use the glkRefresh message to request that
the shared KEK(s) be redistributed to them. Figure 10 depicts the the shared KEK(s) be redistributed to them. Figure 10 depicts the
protocol interactions for GL Key Refresh. protocol interactions for GL Key Refresh.
+-----+ 1 2 +----------+ +-----+ 1 2 +----------+
skipping to change at line 2865 skipping to change at line 2909
GLA (1 in Figure 10). The GL member MUST include name of the GLA (1 in Figure 10). The GL member MUST include name of the
GL in GeneralName. GL in GeneralName.
1.a - The GL member MAY optionally apply confidentiality to the 1.a - The GL member MAY optionally apply confidentiality to the
request by encapsulating the SignedData.PKIData in an request by encapsulating the SignedData.PKIData in an
EnvelopedData (see section 3.2.1.2). EnvelopedData (see section 3.2.1.2).
1.b - The GL member MAY also optionally apply another SignedData 1.b - The GL member MAY also optionally apply another SignedData
over the EnvelopedData (see section 3.2.1.2). over the EnvelopedData (see section 3.2.1.2).
Turner 57
2 - Upon receipt of the glkRefresh request, the GLA verifies the 2 - Upon receipt of the glkRefresh request, the GLA verifies the
GL member's signature(s). If an additional SignedData and/or GL member's signature(s). If an additional SignedData and/or
EnvelopedData encapsulates the request (see section 3.2.1.2 or EnvelopedData encapsulates the request (see section 3.2.1.2 or
3.2.2), the GLA MUST verify the outer signature and/or decrypt 3.2.2), the GLA MUST verify the outer signature and/or decrypt
the outer layer prior to verifying the signature on the inner the outer layer prior to verifying the signature on the inner
most SignedData. most SignedData.
Turner 57
2.a - If the signatures do not verify, the GLA MUST return a 2.a - If the signatures do not verify, the GLA MUST return a
cMCStatusInfo response indicating cMCStatus.failed and cMCStatusInfoEx response indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck. otherInfo.failInfo.badMessageCheck.
2.b - Else the signatures do verify, the GLA MUST make sure the GL 2.b - Else the signatures do verify, the GLA MUST make sure the GL
is supported by checking that the GLĘs GeneralName matches a is supported by checking that the GLĘs GeneralName matches a
glName stored on the GLA. glName stored on the GLA.
2.b.1 - If the GLĘs name is not supported by the GLA, the GLA MUST 2.b.1 - If the GLĘs name is not supported by the GLA, the GLA MUST
return a response indicating return a response indicating cMCStatusInfoEx with
glFailInfo.errorCode.invalidGLName. cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of
invalidGLName.
2.b.2 - Else the glName is supported by the GLA, the GLA MUST 2.b.2 - Else the glName is supported by the GLA, the GLA MUST
ensure the GL member is on the GL. ensure the GL member is on the GL.
2.b.2.a - If the glMemberName is not present on the GL, the GLA 2.b.2.a - If the glMemberName is not present on the GL, the GLA
MUST return a response indicating MUST return a response indicating cMCStatusInfoEx with
glFailInfo.errorCode.noSpam. cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of noSpam.
2.b.2.b - Else the glMemberName is present on the GL, the GLA MUST 2.b.2.b - Else the glMemberName is present on the GL, the GLA MUST
return a glKey message (2 in Figure 10) as described in return a cMCStatusInfoEx.cMCStatus.success and a glKey
section 5. message (2 in Figure 10) as described in section 5.
4.9 GLA Query Request and Response 4.9 GLA Query Request and Response
There will be certain times when a GLO is having trouble setting up There will be certain times when a GLO is having trouble setting up
a GL because they do not know the algorithm(s) or some other a GL because they do not know the algorithm(s) or some other
characteristic that the GLA supports. There may also be times when characteristic that the GLA supports. There may also be times when
prospective GL members or GL members need to know something about prospective GL members or GL members need to know something about
the GLA (these requests are not defined in the document). The the GLA (these requests are not defined in the document). The
glaQueryRequest and glaQueryResponse message have been defined to glaQueryRequest and glaQueryResponse message have been defined to
support determining this information. Figure 11 depicts the protocol support determining this information. Figure 11 depicts the protocol
interactions for glaQueryRequest and glaQueryResponse. interactions for glaQueryRequest and glaQueryResponse.
+-----+ 1 2 +------------------+ +-----+ 1 2 +------------------+
| GLA | <-------> | GLO or GL Member | | GLA | <-------> | GLO or GL Member |
+-----+ +------------------+ +-----+ +------------------+
Figure 11 - GLA Query Request & Response Figure 11 - GLA Query Request & Response
Turner 58
The process for glaQueryRequest and glaQueryResponse is as follows: The process for glaQueryRequest and glaQueryResponse is as follows:
1 - The GLO, GL member, or prospective GL member sends a 1 - The GLO, GL member, or prospective GL member sends a
SignedData.PKIData.controlSequence.glaQueryRequest request to SignedData.PKIData.controlSequence.glaQueryRequest request to
the GLA (1 in Figure 11). The GLO, GL member, or prospective the GLA (1 in Figure 11). The GLO, GL member, or prospective
GL member indicates the information they are interested in GL member indicates the information they are interested in
receiving from the GLA. receiving from the GLA.
1.a - The GLO, GL member, or prospective GL member MAY optionally 1.a - The GLO, GL member, or prospective GL member MAY optionally
apply confidentiality to the request by encapsulating the apply confidentiality to the request by encapsulating the
Turner 58
SignedData.PKIData in an EnvelopedData (see section SignedData.PKIData in an EnvelopedData (see section
3.2.1.2). 3.2.1.2).
1.b - The GLO, GL member, or prospective GL member MAY also 1.b - The GLO, GL member, or prospective GL member MAY also
optionally apply another SignedData over the EnvelopedData optionally apply another SignedData over the EnvelopedData
(see section 3.2.1.2). (see section 3.2.1.2).
2 - Upon receipt of the glaQueryRequest, the GLA determines if it 2 - Upon receipt of the glaQueryRequest, the GLA determines if it
accepts glaQueryRequest messages. accepts glaQueryRequest messages.
2.a - If the GLA does not accept glaQueryRequest messages, the GLA 2.a - If the GLA does not accept glaQueryRequest messages, the GLA
MUST return a cMCStatusInfo response indicating MUST return a cMCStatusInfoEx response indicating
cMCStatus.noSupport and any other information in cMCStatus.noSupport and any other information in
statusString. statusString.
2.b - Else the GLA does accept GLAQueryRequests, the GLA MUST 2.b - Else the GLA does accept GLAQueryRequests, the GLA MUST
verify the GLO's, GL memberĘs, or prospective GL memberĘs verify the GLO's, GL memberĘs, or prospective GL memberĘs
signature(s). If an additional SignedData and/or signature(s). If an additional SignedData and/or
EnvelopedData encapsulates the request (see section 3.2.1.2 EnvelopedData encapsulates the request (see section 3.2.1.2
or 3.2.2), the GLA MUST verify the outer signature and/or or 3.2.2), the GLA MUST verify the outer signature and/or
decrypt the outer layer prior to verifying the signature on decrypt the outer layer prior to verifying the signature on
the inner most SignedData. the inner most SignedData.
2.b.1 - If the signatures do not verify, the GLA MUST return a 2.b.1 - If the signatures do not verify, the GLA MUST return a
cMCStatusInfo response indicating cMCStatus.failed and cMCStatusInfoEx response indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck. otherInfo.failInfo.badMessageCheck.
2.b.2 - Else the signatures do verify, the GLA MUST return a 2.b.2 - Else the signatures do verify, the GLA MUST return a
glaQueryResponse (2 in Figure 11) with the correct glaQueryResponse (2 in Figure 11) with the correct
response if the glaRequestType is supported or return a response if the glaRequestType is supported or return a
cMCStatusInfo response indicating cMCStatus.noSupport if cMCStatusInfoEx response indicating cMCStatus.noSupport if
the glaRequestType is not supported. the glaRequestType is not supported.
2.b.2.a - The GLA MUST apply confidentiality to the response by 2.b.2.a - The GLA MUST apply confidentiality to the response by
encapsulating the SignedData.PKIResponse in an encapsulating the SignedData.PKIResponse in an
EnvelopedData if the request was encapsulated in an EnvelopedData if the request was encapsulated in an
EnvelopedData (see section 3.2.1.2). EnvelopedData (see section 3.2.1.2).
2.b.2.b - The GLA MAY also optionally apply another SignedData 2.b.2.b - The GLA MAY also optionally apply another SignedData
over the EnvelopedData (see section 3.2.1.2). over the EnvelopedData (see section 3.2.1.2).
Turner 59
3 - Upon receipt of the glaQueryResponse, the GLO, GL member, or 3 - Upon receipt of the glaQueryResponse, the GLO, GL member, or
prospective GL member verifies the GLA's signature(s). If an prospective GL member verifies the GLA's signature(s). If an
additional SignedData and/or EnvelopedData encapsulates the additional SignedData and/or EnvelopedData encapsulates the
response (see section 3.2.1.2 or 3.2.2), the GLO, GL member, response (see section 3.2.1.2 or 3.2.2), the GLO, GL member,
or prospective GL member MUST verify the outer signature or prospective GL member MUST verify the outer signature
and/or decrypt the outer layer prior to verifying the and/or decrypt the outer layer prior to verifying the
signature on the inner most SignedData. signature on the inner most SignedData.
3.a - If the signatures do not verify, the GLO, GL member, or 3.a - If the signatures do not verify, the GLO, GL member, or
prospective GL member MUST return a cMCStatusInfo response prospective GL member MUST return a cMCStatusInfoEx response
Turner 59
indicating cMCStatus.failed and indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck. otherInfo.failInfo.badMessageCheck.
3.b - Else the signatures do verify, the GLO, GL member, or 3.b - Else the signatures do verify, the GLO, GL member, or
prospective GL member MUST check that one of the names in prospective GL member MUST check that one of the names in
the certificate used to sign the response matches the name the certificate used to sign the response matches the name
of the GL. of the GL.
3.b.1 ū If the GLĘs name does not match the name present in the 3.b.1 ū If the GLĘs name does not match the name present in the
certificate used to sign the message, the GLO should not certificate used to sign the message, the GLO should not
skipping to change at line 3019 skipping to change at line 3064
1 - The GLO or GLA sends a 1 - The GLO or GLA sends a
SignedData.PKIData.controlSequence.glProvideCert request to SignedData.PKIData.controlSequence.glProvideCert request to
the GL member. The GLO or GLA indicates the GL name in glName the GL member. The GLO or GLA indicates the GL name in glName
and the GL memberĘs name in glMemberName. and the GL memberĘs name in glMemberName.
1.a - The GLO or GLA MAY optionally apply confidentiality to the 1.a - The GLO or GLA MAY optionally apply confidentiality to the
request by encapsulating the SignedData.PKIData in an request by encapsulating the SignedData.PKIData in an
EnvelopedData (see section 3.2.1.2). If the GL memberĘs PKC EnvelopedData (see section 3.2.1.2). If the GL memberĘs PKC
has been revoked, the GLO or GLA MUST NOT use it to generate has been revoked, the GLO or GLA MUST NOT use it to generate
Turner 60
the EnvelopedData that encapsulates the glProvideCert the EnvelopedData that encapsulates the glProvideCert
request. request.
1.b - The GLO or GLA MAY also optionally apply another SignedData 1.b - The GLO or GLA MAY also optionally apply another SignedData
over the EnvelopedData (see section 3.2.1.2). over the EnvelopedData (see section 3.2.1.2).
2 - Upon receipt of the glProvideCert message, the GL member 2 - Upon receipt of the glProvideCert message, the GL member
verifies the GLOĘs or GLAĘs signature(s). If an additional verifies the GLOĘs or GLAĘs signature(s). If an additional
SignedData and/or EnvelopedData encapsulates the response (see SignedData and/or EnvelopedData encapsulates the response (see
section 3.2.1.2 or 3.2.2), the GL member MUST verify the outer section 3.2.1.2 or 3.2.2), the GL member MUST verify the outer
Turner 60
signature and/or decrypt the outer layer prior to verifying signature and/or decrypt the outer layer prior to verifying
the signature on the inner most SignedData. the signature on the inner most SignedData.
2.a - If the signatures do not verify, the GL member MUST return a 2.a - If the signatures do not verify, the GL member MUST return a
cMCStatusInfo response indicating cMCStatus.failed and cMCStatusInfoEx response indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck. otherInfo.failInfo.badMessageCheck.
2.b - Else the signatures do verify, the GL member generates a 2.b - Else the signatures do verify, the GL member generates a
Signed.PKIResponse.controlSequence.glUpdateCert that MUST Signed.PKIResponse.controlSequence.glUpdateCert that MUST
include the GL name in glName, the member's name in include the GL name in glName, the member's name in
glMember.glMemberName, their encryption certificate in glMember.glMemberName, their encryption certificate in
glMember.certificates.pKC. The GL member MAY also include glMember.certificates.pKC. The GL member MAY also include
any attribute certificates associated with their encryption any attribute certificates associated with their encryption
certificate in glMember.certificates.aC, and the certificate in glMember.certificates.aC, and the
certification path associated with their encryption and certification path associated with their encryption and
skipping to change at line 3067 skipping to change at line 3112
over the EnvelopedData (see section 3.2.1.2). over the EnvelopedData (see section 3.2.1.2).
3 - Upon receipt of the glUpdateCert message, the GLO or GLA 3 - Upon receipt of the glUpdateCert message, the GLO or GLA
verifies the GL memberĘs signature(s). If an additional verifies the GL memberĘs signature(s). If an additional
SignedData and/or EnvelopedData encapsulates the response (see SignedData and/or EnvelopedData encapsulates the response (see
section 3.2.1.2 or 3.2.2), the GL member MUST verify the outer section 3.2.1.2 or 3.2.2), the GL member MUST verify the outer
signature and/or decrypt the outer layer prior to verifying signature and/or decrypt the outer layer prior to verifying
the signature on the inner most SignedData. the signature on the inner most SignedData.
3.a - If the signatures do not verify, the GLO or GLA MUST return 3.a - If the signatures do not verify, the GLO or GLA MUST return
a cMCStatusInfo response indicating cMCStatus.failed and a cMCStatusInfoEx response indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck. otherInfo.failInfo.badMessageCheck.
3.b - Else the signatures do verify, the GLO or GLA MUST verify 3.b - Else the signatures do verify, the GLO or GLA MUST verify
the memberĘs encryption certificate. the memberĘs encryption certificate.
Turner 61
3.b.1 - If the memberĘs encryption certificate does not verify, 3.b.1 - If the memberĘs encryption certificate does not verify,
the GLO MAY return either another glProvideCert request or the GLO MAY return either another glProvideCert request or
a cMCStatusInfo with cMCStatus.failed and the reason why a cMCStatusInfoEx with cMCStatus.failed and the reason why
in cMCStatus.statusString. glProvideCert should be in cMCStatus.statusString. glProvideCert should be
returned only a certain number of times because if the GL returned only a certain number of times because if the GL
member does not have a valid certificate they will never member does not have a valid certificate they will never
be able to return one. be able to return one.
3.b.2 - Else the memberĘs encryption certificate does not verify, 3.b.2 - Else the memberĘs encryption certificate does not verify,
the GLA MAY return another glProvideCert request to the GL the GLA MAY return another glProvideCert request to the GL
member or a cMCStatusInfoEx with cMCStatus.failed and the
Turner 61
member or a cMCStatusInfo with cMCStatus.failed and the
reason why in cMCStatus.statusString to the GLO. reason why in cMCStatus.statusString to the GLO.
glProvideCert should be returned only a certain number of glProvideCert should be returned only a certain number of
times because if the GL member does not have a valid times because if the GL member does not have a valid
certificate they will never be able to return one. certificate they will never be able to return one.
3.b.3 - Else the memberĘs encryption certificate does verify, the 3.b.3 - Else the memberĘs encryption certificate does verify, the
GLO or GLA will use it in subsequent glAddMember requests GLO or GLA will use it in subsequent glAddMember requests
and glKey messages associated with the GL member. and glKey messages associated with the GL member.
4.10.2 GL Member Initiated Update Member Certificate 4.10.2 GL Member Initiated Update Member Certificate
skipping to change at line 3126 skipping to change at line 3170
1.b - The GL member MAY also optionally apply another SignedData 1.b - The GL member MAY also optionally apply another SignedData
over the EnvelopedData (see section 3.2.1.2). over the EnvelopedData (see section 3.2.1.2).
2 - Upon receipt of the glUpdateCert message, the GLA verifies the 2 - Upon receipt of the glUpdateCert message, the GLA verifies the
GL memberĘs signature(s). If an additional SignedData and/or GL memberĘs signature(s). If an additional SignedData and/or
EnvelopedData encapsulates the response (see section 3.2.1.2 EnvelopedData encapsulates the response (see section 3.2.1.2
or 3.2.2), the GLA MUST verify the outer signature and/or or 3.2.2), the GLA MUST verify the outer signature and/or
decrypt the outer layer prior to verifying the signature on decrypt the outer layer prior to verifying the signature on
the inner most SignedData. the inner most SignedData.
Turner 62
2.a - If the signatures do not verify, the GLA MUST return a 2.a - If the signatures do not verify, the GLA MUST return a
cMCStatusInfo response indicating cMCStatus.failed and cMCStatusInfoEx response indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck. otherInfo.failInfo.badMessageCheck.
2.b - Else the signatures do verify, the GLA MUST verify the 2.b - Else the signatures do verify, the GLA MUST verify the
memberĘs encryption certificate. memberĘs encryption certificate.
2.b.1 - If the memberĘs encryption certificate does not verify, 2.b.1 - If the memberĘs encryption certificate does not verify,
the GLA MAY return another glProvideCert request to the GL the GLA MAY return another glProvideCert request to the GL
member or a cMCStatusInfo with cMCStatus.failed and the member or a cMCStatusInfoEx with cMCStatus.failed and the
Turner 62
reason why in cMCStatus.statusString to the GLO. reason why in cMCStatus.statusString to the GLO.
glProvideCert should be returned only a certain number of glProvideCert should be returned only a certain number of
times because if the GL member does not have a valid times because if the GL member does not have a valid
certificate they will never be able to return one. certificate they will never be able to return one.
2.b.2 - Else the memberĘs encryption certificate does verify, the 2.b.2 - Else the memberĘs encryption certificate does verify, the
GLA will use it in subsequent glAddMember requests and GLA will use it in subsequent glAddMember requests and
glKey messages associated with the GL member. The GLA MUST glKey messages associated with the GL member. The GLA MUST
also forward the glUpdateCert message to the GLO. also forward the glUpdateCert message to the GLO.
5 Distribution Message 5 Distribution Message
The GLA uses the glKey message to distribute new, shared KEK(s) The GLA uses the glKey message to distribute new, shared KEK(s)
after receiving glAddMember, glDeleteMember (for closed and managed after receiving glAddMember, glDeleteMember (for closed and managed
GLs), glRekey, glkCompromise, or glkRefresh requests and returning a GLs), glRekey, glkCompromise, or glkRefresh requests and returning a
glSuccessInfo response for the respective request. Figure 12 depicts cMCStatusInfoEx response for the respective request. Figure 12
the protocol interactions to send out glKey messages. The procedures depicts the protocol interactions to send out glKey messages. The
defined in this section MUST be implemented. procedures defined in this section MUST be implemented.
1 +----------+ 1 +----------+
+-------> | Member 1 | +-------> | Member 1 |
| +----------+ | +----------+
+-----+ | 1 +----------+ +-----+ | 1 +----------+
| GLA | ----+-------> | ... | | GLA | ----+-------> | ... |
+-----+ | +----------+ +-----+ | +----------+
| 1 +----------+ | 1 +----------+
+-------> | Member n | +-------> | Member n |
+----------+ +----------+
skipping to change at line 3178 skipping to change at line 3221
If the GL was setup with GLKeyAttributes.recipientsNotMutuallyAware If the GL was setup with GLKeyAttributes.recipientsNotMutuallyAware
set to FALSE, a separate glKey message MUST be sent to each GL set to FALSE, a separate glKey message MUST be sent to each GL
member so as to not divulge information about the other GL members. member so as to not divulge information about the other GL members.
When the glKey message is generated as a result of a: When the glKey message is generated as a result of a:
- glAddMember request, - glAddMember request,
- glkComrpomise indication, - glkComrpomise indication,
- glkRefresh request, - glkRefresh request,
Turner 63
- glDeleteMember request with the GLĘs glAdministration set to - glDeleteMember request with the GLĘs glAdministration set to
managed or closed, managed or closed,
- glRekey request with generationCounter set to zero (0) - glRekey request with generationCounter set to zero (0)
The GLA MUST use either the kari (see section 12.3.2 of CMS [2]) or The GLA MUST use either the kari (see section 12.3.2 of CMS [2]) or
ktri (see section 12.3.1 of CMS [2]) choice in ktri (see section 12.3.1 of CMS [2]) choice in
glKey.glkWrapped.RecipientInfo to ensure only the intended glKey.glkWrapped.RecipientInfo to ensure only the intended
recipients receive the shared KEK. The GLA MUST support the ktri recipients receive the shared KEK. The GLA MUST support the ktri
choice. choice.
Turner 63
When the glKey message is generated as a result of a glRekey request When the glKey message is generated as a result of a glRekey request
with generationCounter greater than zero (0) or when the GLA with generationCounter greater than zero (0) or when the GLA
controls rekeys, the GLA MAY use the kari, ktri, or kekri (see controls rekeys, the GLA MAY use the kari, ktri, or kekri (see
section 12.3.3 of CMS [2]) in glKey.glkWrapped.RecipientInfo to section 12.3.3 of CMS [2]) in glKey.glkWrapped.RecipientInfo to
ensure only the intended recipients receive the shared KEK. The GLA ensure only the intended recipients receive the shared KEK. The GLA
MUST support the RecipientInfo.ktri choice. MUST support the RecipientInfo.ktri choice.
5.1 Distribution Process 5.1 Distribution Process
When a glKey message is generated the process is as follows: When a glKey message is generated the process is as follows:
skipping to change at line 3216 skipping to change at line 3260
provided (see section 4.10). The number of glKey messages provided (see section 4.10). The number of glKey messages
generated for the GL is described in section 3.1.16. generated for the GL is described in section 3.1.16.
1.a - The GLA MAY optionally apply another confidentiality layer 1.a - The GLA MAY optionally apply another confidentiality layer
to the message by encapsulating the SignedData.PKIData in to the message by encapsulating the SignedData.PKIData in
another EnvelopedData (see section 3.2.1.2). another EnvelopedData (see section 3.2.1.2).
1.b - The GLA MAY also optionally apply another SignedData over 1.b - The GLA MAY also optionally apply another SignedData over
the EnvelopedData.SignedData.PKIData (see section 3.2.1.2). the EnvelopedData.SignedData.PKIData (see section 3.2.1.2).
2 - Upon receipt of the message, the GL members MUST verify the 2 - Upon receipt of the glKey message, the GL members MUST verify
signature over the inner most SignedData.PKIData. If an the signature over the inner most SignedData.PKIData. If an
additional SignedData and/or EnvelopedData encapsulates the additional SignedData and/or EnvelopedData encapsulates the
message (see section 3.2.1.2 or 3.2.2), the GL Member MUST message (see section 3.2.1.2 or 3.2.2), the GL Member MUST
verify the outer signature and/or decrypt the outer layer verify the outer signature and/or decrypt the outer layer
prior to verifying the signature on the prior to verifying the signature on the
SignedData.PKIData.controlSequence.glKey. SignedData.PKIData.controlSequence.glKey.
2.a - If the signatures do not verify, the GL member MUST return a 2.a - If the signatures do not verify, the GL member MUST return a
cMCStatusInfo response indicating cMCStatus.failed and cMCStatusInfoEx response indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck. otherInfo.failInfo.badMessageCheck.
2.b - Else the signatures do verify, the GL member process the 2.b - Else the signatures do verify, the GL member process the
RecipientInfos according to CMS [2]. Once unwrapped the GL RecipientInfos according to CMS [2]. Once unwrapped the GL
Turner 64
member should store the shared KEK in a safe place. When member should store the shared KEK in a safe place. When
stored, the glName, glIdentifier, and shared KEK should be stored, the glName, glIdentifier, and shared KEK should be
associated. associated. Additionally, the GL member MUST return a
cMCStatusInfoEx indicating cMCStatus.success to tell the GLA
the key received.
6 Algorithms 6 Algorithms
This section lists the algorithms that must be implemented. This section lists the algorithms that must be implemented.
Additional algorithms that should be implemented are also included. Additional algorithms that should be implemented are also included.
Turner 64
6.1 KEK Generation Algorithm 6.1 KEK Generation Algorithm
The shared KEK MUST be generated according to the security The shared KEK MUST be generated according to the security
considerations section in CMS [2]. considerations section in AlgSpec [9].
6.2 Shared KEK Wrap Algorithm 6.2 Shared KEK Wrap Algorithm
In the mechanisms described in sections 5, the shared KEK being In the mechanisms described in sections 5, the shared KEK being
distributed in glkWrapped MUST be protected by a key of equal or distributed in glkWrapped MUST be protected by a key of equal or
greater length (i.e., if a RC2 128-bit key is being distributed a greater length (i.e., if a RC2 128-bit key is being distributed a
key of 128-bits or greater must be used to protect the key). key of 128-bits or greater must be used to protect the key).
The algorithm object identifiers included in glkWrapped are as The algorithm object identifiers included in glkWrapped are as
specified in 12.3 of CMS [2]. specified in AlgSpec [9].
6.3 Shared KEK Algorithm 6.3 Shared KEK Algorithm
The shared KEK distributed and indicated in glkAlgorithm MUST The shared KEK distributed and indicated in glkAlgorithm MUST
support the symmetric key-encryption algorithms as specified in support the symmetric key-encryption algorithms as specified in
section 12.3.3 of CMS [2] section AlgSpec [9].
7 Transport 7 Transport
SMTP [7] MUST be supported. All other transport mechanisms MAY be SMTP [10] MUST be supported. All other transport mechanisms MAY be
supported. supported.
8 Using the Group Key 8 Using the Group Key
This document was written with three specific scenarios in mind. Two This document was written with three specific scenarios in mind. Two
to support mail list agents and one for general message to support mail list agents and one for general message
distribution. Scenario 1 depicts the originator sending a public key distribution. Scenario 1 depicts the originator sending a public key
(PK) protected message to a MLA who then uses the shared KEK (S) to (PK) protected message to a MLA who then uses the shared KEK (S) to
redistribute the message to the members of the list. Scenario 2 redistribute the message to the members of the list. Scenario 2
depicts the originator sending a shared KEK protected message to a depicts the originator sending a shared KEK protected message to a
MLA who then redistributes the message to the members of the list MLA who then redistributes the message to the members of the list
Turner 65
(the MLA only adds additional recipients). Scenario 3 shows an (the MLA only adds additional recipients). Scenario 3 shows an
originator sending a shared KEK protected message to a group of originator sending a shared KEK protected message to a group of
recipients without using the MLA. recipients without using the MLA.
+----> +----> +----> +----> +----> +---->
PK +-----+ S | S +-----+ S | S | PK +-----+ S | S +-----+ S | S |
----> | MLA | --+----> ----> | MLA | --+----> ----+----> ----> | MLA | --+----> ----> | MLA | --+----> ----+---->
+-----+ | +-----+ | | +-----+ | +-----+ | |
+----> +----> +----> +----> +----> +---->
Scenario 1 Scenario 2 Scenario 3 Scenario 1 Scenario 2 Scenario 3
Turner 65
9 Security Considerations 9 Security Considerations
Only have GLOs that are trusted. Only have GLOs that are trusted.
Need to rekey closed and managed GLs if a member is deleted. Need to rekey closed and managed GLs if a member is deleted.
GL members have to store some kind of information about who GL members have to store some kind of information about who
distributed the shared KEK to them so that they can make sure distributed the shared KEK to them so that they can make sure
subsequent rekeys are originated from the same entity. subsequent rekeys are originated from the same entity.
Need to make sure you donĘt make the key size too small and duration Need to make sure you donĘt make the key size too small and duration
long because people will have more time to attack the key. long because people will have more time to attack the key.
Need to make sure you donĘt make the generationCounter to large Need to make sure you donĘt make the generationCounter to large
because people can attack the last key. If there are 14 keys because people can attack the last key. If there are 14 keys
outstanding each with a yearĘs duration attackers might be able outstanding each with a yearĘs duration attackers might be able
determine the 14th key. determine the 14th key.
Assume that two or more parties have a shared KEK, and the shared
KEK is used to encrypt a second KEK for confidential distribution to
those parties. The second KEK might be used to encrypt a third KEK;
the third KEK might be used to encrypt a fourth KEK; and so on. If
any of the KEKs in such a chain is compromised, all of the
subordinate KEKs in the chain MUST also be considered compromised.
10 References 10 References
1 Bradner, S., "The Internet Standards Process -- Revision 3", BCP 1 Bradner, S., "The Internet Standards Process -- Revision 3", BCP
9, RFC 2026, October 1996. 9, RFC 2026, October 1996.
2 Housley, R., "Cryptographic Message Syntax," RFC 2630, June 1999. 2 Housley, R., "Cryptographic Message Syntax," draft-ietf-smime-
rfc2630bis-00.txt, April 2001.
3 Myers, M., Liu, X., Schaad, J., Weinsten, J., "Certificate 3 Myers, M., Liu, X., Schaad, J., Weinsten, J., "Certificate
Management Message over CMS," draft-ietf-pkix-cmc-05.txt, July Management Message over CMS," draft-ietf-pkix-2797-bis-00.txt,
1999. April 2001.
Turner 66
4 Bradner, S., "Key words for use in RFCs to Indicate Requirement 4 Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
5 Ramsdale, B., "S/MIME Version 3 Message Specification," RFC 2633, 5 Housley, R., Ford, W., Polk, W. and D. Solo, "Internet X.509
Public Key Infrastructure: Certificate and CRL Profile", draft-
ietf-pkix-new-part1-06.txt, 8 March 2001.
6 Farrell, S., Housley, R., ōAn Internet Attribute Certificate
Profile for Authorizationö, draft-ietf-pkix-acx.509prof-06.txt,
10 January 2001.
7 Ramsdale, B., "S/MIME Version 3 Message Specification," TBD.
8 Hoffman, P., ōExtended Security Services for S/MIMEö, RFC 2634,
June 1999. June 1999.
6 Housley, R., Ford, W., Polk, W. and D. Solo, "Internet X.509 9 Housley, R., ōCryptographic Message Syntax (CMS) Algorithmsö,
Public Key Infrastructure: Certificate and CRL Profile", RFC draft-ietf-smime-cmsalg-00.txt, Apil 2001.
2459, January 1999.
7 Postel, j., "Simple Mail Transport Protocol," RFC 821, August 10 Postel, j., "Simple Mail Transport Protocol," RFC 821, August
1982. 1982.
11 Acknowledgements 11 Acknowledgements
Thanks to Russ Housley and Jim Schaad for providing much of the Thanks to Russ Housley and Jim Schaad for providing much of the
background and review required to write this draft. background and review required to write this draft.
Turner 66
12 Author's Addresses 12 Author's Addresses
Sean Turner Sean Turner
IECA, Inc. IECA, Inc.
9010 Edgepark Road 9010 Edgepark Road
Vienna, VA 22182 Vienna, VA 22182
Phone: +1.703.628.3180 Phone: +1.703.628.3180
Email: turners@ieca.com Email: turners@ieca.com
Turner 67 Turner 67
Annex A: ASN.1 Module Annex A: ASN.1 Module
SMIMESymmetricKeyDistribution SMIMESymmetricKeyDistribution
{ TBD } { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)
smime(16) modules(0) symkeydist(12) }
DEFINITIONS IMPLICIT TAGS ::= DEFINITIONS IMPLICIT TAGS ::=
BEGIN BEGIN
-- EXPORTS All -- -- EXPORTS All --
-- The types and values defined in this module are exported for use -- The types and values defined in this module are exported for use
-- in the other ASN.1 modules. Other applications may use them for -- in the other ASN.1 modules. Other applications may use them for
-- their own purposes. -- their own purposes.
IMPORTS IMPORTS
-- Directory Authentication Framework (X.509)
AlgorithmIdentifier, AttributeCertificate, Certificate,
FROM AuthenticationFramework { joint-iso-itu-t ds(5)
module(1) authenticationFramework(7) 3 }
-- PKIX Part 1 - Implicit -- PKIX Part 1 - Implicit
GeneralName GeneralName
FROM PKIX1Implicit88 {iso(1) identified-organization(3) dod(6) FROM PKIX1Implicit88 {iso(1) identified-organization(3) dod(6)
internet(1) security(5) mechanisms(5) pkix(7) id-mod(0) internet(1) security(5) mechanisms(5) pkix(7) id-mod(0)
id-pkix1-implicit-88(2)} id-pkix1-implicit(19)}
-- PKIX Part 1 - Explicit
AlgorithmIdentifier, Certificate
FROM PKIX1Explicit88 { iso(1) identified-organization(3) dod(6)
internet(1) security(5) mechanisms(5) pkix(7) id-mod(0)
id-pkix1-explicit(18) }
-- Cryptographic Message Syntax -- Cryptographic Message Syntax
RecipientInfos, id-alg-CMS3DESWrap RecipientInfos, id-alg-CMS3DESwrap, KEKIdentifier,
CertificateSet
FROM CryptographicMessageSyntax { iso(1) member-body(2) us(840) FROM CryptographicMessageSyntax { iso(1) member-body(2) us(840)
rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) modules(0) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) modules(0) cms(1)}
cms(1)};
-- Attribute Certificate Profile
AttributeCertificate FROM
PKIXAttributeCertificate { iso(1) identified-organization(3)
dod(6) internet(1) security(5) mechanisms(5) pkix(7)
id-mod(0) id-mod-attribute-cert(12)};
-- This defines the GL symmetric key distribution object identifier
-- arc.
id-skd OBJECT IDENTIFIER ::= { iso(1) member-body(2) us(840)
rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) skd(8) }
-- This defines the GL Use KEK control attribute -- This defines the GL Use KEK control attribute
id-skd-glUseKEK OBJECT IDENTIFIER ::= { id-skd 1} id-skd-glUseKEK OBJECT IDENTIFIER ::= { id-skd 1}
Turner 68
GLUseKEK ::= SEQUENCE { GLUseKEK ::= SEQUENCE {
glInfo GLInfo, glInfo GLInfo,
glOwnerInfo SEQUENCE SIZE (1..MAX) OF GLOwnerInfo, glOwnerInfo SEQUENCE SIZE (1..MAX) OF GLOwnerInfo,
glAdministration GLAdministration DEFAULT (1), glAdministration GLAdministration DEFAULT 1,
glKeyAttributes GLKeyAttributes OPTIONAL } glKeyAttributes GLKeyAttributes OPTIONAL }
GLInfo ::= SEQUENCE { GLInfo ::= SEQUENCE {
glName GeneralName, glName GeneralName,
glAddress GeneralName } glAddress GeneralName }
GLOwnerInfo ::= SEQUENCE { GLOwnerInfo ::= SEQUENCE {
glOwnerName GeneralName, glOwnerName GeneralName,
glOwnerAddress GeneralName } glOwnerAddress GeneralName,
certificates Certificates OPTIONAL }
Turner 68
GLAdministration ::= INTEGER { GLAdministration ::= INTEGER {
unmanaged (0), unmanaged (0),
managed (1), managed (1),
closed (2) } closed (2) }
GLKeyAttributes ::= SEQUENCE { GLKeyAttributes ::= SEQUENCE {
rekeyControlledByGLO [0] BOOLEAN DEFAULT FALSE, rekeyControlledByGLO [0] BOOLEAN DEFAULT FALSE,
recipientsNotMutuallyAware [1] BOOLEAN DEFAULT TRUE, recipientsNotMutuallyAware [1] BOOLEAN DEFAULT TRUE,
duration [2] INTEGER DEAULT (0), duration [2] INTEGER DEFAULT 0,
generationCounter [3] INTEGER DEFAULT (2), generationCounter [3] INTEGER DEFAULT 2,
requestedAlgorithm [4] AlgorithmIdentifier requestedAlgorithm [4] AlgorithmIdentifier
DEFAULT (id-alg-CMS3DESwrap) } DEFAULT id-alg-CMS3DESwrap }
-- This defines the Delete GL control attribute. -- This defines the Delete GL control attribute.
-- It has the simple type GeneralName. -- It has the simple type GeneralName.
id-skd-glDelete OBJECT IDENTIFIER ::= { id-skd 2} id-skd-glDelete OBJECT IDENTIFIER ::= { id-skd 2}
-- This defines the Add GL Member control attribute -- This defines the Add GL Member control attribute
id-skd-glAddMember OBJECT IDENTIFIER ::= { id-skd 3} id-skd-glAddMember OBJECT IDENTIFIER ::= { id-skd 3}
GLAddMember ::= SEQUENCE { GLAddMember ::= SEQUENCE {
glName GeneralName, glName GeneralName,
glMember GLMember } glMember GLMember }
GLMember ::= SEQUENCE { GLMember ::= SEQUENCE {
glMemberName GeneralName, glMemberName GeneralName,
glMemberAddress GeneralName OPTIONAL, glMemberAddress GeneralName OPTIONAL,
certificates Certificates OPTIONAL } certificates Certificates OPTIONAL }
Turner 69
Certificates ::= SEQUENCE { Certificates ::= SEQUENCE {
pKC Certificate OPTIONAL, pKC [0] Certificate OPTIONAL,
-- See X.509 -- See PKIX [5]
aC SEQUENCE SIZE (1.. MAX) OF aC [1] SEQUENCE SIZE (1.. MAX) OF
AttributeCertificate OPTIONAL, AttributeCertificate OPTIONAL,
-- See X.509 -- See ACPROF [6]
certificationPath CertificateSet OPTIONAL } certificationPath [2] CertificateSet OPTIONAL }
-- From CMS [2] -- From CMS [2]
CertificateSet ::= SET SIZE (1..MAX) OF CertificateChoices
CertificateChoices ::= CHOICE {
certificate Certificate,
-- See X.509
extendedCertificate [0] IMPLICIT ExtendedCertificate,
-- Obsolete
attrCert [1] IMPLICIT AttributeCertificate }
-- See X.509 and X9.57
Turner 69
-- This defines the Delete GL Member control attribute -- This defines the Delete GL Member control attribute
id-skd-glDeleteMember OBJECT IDENTIFIER ::= { id-skd 4} id-skd-glDeleteMember OBJECT IDENTIFIER ::= { id-skd 4}
GLDeleteMember ::= SEQUENCE { GLDeleteMember ::= SEQUENCE {
glName GeneralName, glName GeneralName,
glMemberToDelete GeneralName } glMemberToDelete GeneralName }
-- This defines the Delete GL Member control attribute -- This defines the Delete GL Member control attribute
skipping to change at line 3494 skipping to change at line 3561
-- This defines the GL Key Compromise control attribute. -- This defines the GL Key Compromise control attribute.
-- It has the simple type GeneralName. -- It has the simple type GeneralName.
id-skd-glKeyCompromise OBJECT IDENTIFIER ::= { id-skd 8} id-skd-glKeyCompromise OBJECT IDENTIFIER ::= { id-skd 8}
-- This defines the GL Key Refresh control attribute. -- This defines the GL Key Refresh control attribute.
id-skd-glkRefresh OBJECT IDENTIFIER ::= { id-skd 9} id-skd-glkRefresh OBJECT IDENTIFIER ::= { id-skd 9}
GLKRefresh ::= { Turner 70
GLKRefresh ::= SEQUENCE {
glName GeneralName, glName GeneralName,
dates SEQUENCE (1..MAX) OF Date } dates SEQUENCE SIZE (1..MAX) OF Date }
Date ::= { Date ::= SEQUENCE {
start GeneralizedTime, start GeneralizedTime,
end GeneralizedTime OPTIONAL } end GeneralizedTime OPTIONAL }
Turner 70
-- This defines the GLA Query Request control attribute. -- This defines the GLA Query Request control attribute.
id-skd-glaQueryRequest OBJECT IDENTIFIER ::= { id-skd X} id-skd-glaQueryRequest OBJECT IDENTIFIER ::= { id-skd 11}
GLAQueryRequest ::= SEQUENCE { GLAQueryRequest ::= SEQUENCE {
glaRequestType OBJECT IDENTIFIER, glaRequestType OBJECT IDENTIFIER,
glaRequestValue ANY DEFINED BY glaResponseType } glaRequestValue ANY DEFINED BY glaRequestType }
-- This defines the Algorithm Request
id-rt-algorithmSupported { id-tbd }
-- This defines the GLA Query Response control attribute. -- This defines the GLA Query Response control attribute.
id-skd-glaQueryResponse OBJECT IDENTIFIER ::= { id-skd X} id-skd-glaQueryResponse OBJECT IDENTIFIER ::= { id-skd 12}
GLAQueryResponse ::= SEQUENCE { GLAQueryResponse ::= SEQUENCE {
glaResponseType OBJECT IDENTIFIER, glaResponseType OBJECT IDENTIFIER,
glaResponseValue ANY DEFINED BY glaResponseType } glaResponseValue ANY DEFINED BY glaResponseType }
-- This defines the GLA Request/Response (glaRR) arc for
-- glaRequestType/glaResponseType.
id-cmc-glaRR OBJECT IDENTIFIER ::= { iso(1) identified-
organization(3) dod(6) internet(1) security(5) mechanisms(5) pkix(7)
cmc(7) glaRR(99) }
-- This defines the Algorithm Request
id-cmc-gla-skdAlgRequest OBJECT IDENTIFIER ::= { id-cmc-glaRR 1 }
-- This defines the Algorithm Response
id-cmc-gla-skdAlgResponse OBJECT IDENTIFIER ::= { id-cmc-glaRR 2 }
-- Note that the response for algorithmSupported request is the -- Note that the response for algorithmSupported request is the
-- smimeCapabilities attribute as defined in MsgSpec [5]. -- smimeCapabilities attribute as defined in MsgSpec [7].
-- This defines the control attribute to request an updated -- This defines the control attribute to request an updated
-- certificate to the GLA. -- certificate to the GLA.
id-skd-glProvideCert OBJECT IDENTIFIER ::= { id-skd X} id-skd-glProvideCert OBJECT IDENTIFIER ::= { id-skd 13}
GLManageCert ::= SEQUENCE { GLManageCert ::= SEQUENCE {
glName GeneralName, glName GeneralName,
glMember GLMember } glMember GLMember }
Turner 71
-- This defines the control attribute to return an updated -- This defines the control attribute to return an updated
-- certificate to the GLA. It has the type GLManageCert. -- certificate to the GLA. It has the type GLManageCert.
id-skd-glManageCert OBJECT IDENTIFIER ::= { id-skd X} id-skd-glManageCert OBJECT IDENTIFIER ::= { id-skd 14}
-- This defines the control attribute to distribute the GL shared -- This defines the control attribute to distribute the GL shared
-- KEK. -- KEK.
id-skd-glKey OBJECT IDENTIFIER ::= { id-skd X} id-skd-glKey OBJECT IDENTIFIER ::= { id-skd 15}
Turner 71
GLKey ::= SEQUENCE { GLKey ::= SEQUENCE {
glName GeneralName, glName GeneralName,
glIdentifier OCTET STRING, glIdentifier KEKIdentifier, -- See CMS [2]
glkWrapped RecipientInfos, -- See CMS [2] glkWrapped RecipientInfos, -- See CMS [2]
glkAlgorithm AlgorithmIdentifier, glkAlgorithm AlgorithmIdentifier,
glkNotBefore GeneralizedTime, glkNotBefore GeneralizedTime,
glkNotAfter GeneralizedTime } glkNotAfter GeneralizedTime }
-- This defines the CMC error types
id-cet-skdFailInfo OBJECT IDENTIFIER ::= { iso(1)
identified-organization(3) dod(6) internet(1) security(5)
mechanisms(5) pkix(7) cet(15) skdFailInfo(1) }
SKDFailInfo ::= INTEGER {
unspecified (0),
closedGL (1),
unsupportedDuration (2),
noGLACertificate (3),
invalidCert (4),
unsupportedAlgorithm (5),
noGLONameMatch (6),
invalidGLName (7),
nameAlreadyInUse (8),
noSpam (9),
deniedAccess (10),
alreadyAMember (11),
notAMember (12),
alreadyAnOwner (13),
notAnOwner (14) }
END -- SMIMESymmetricKeyDistribution END -- SMIMESymmetricKeyDistribution
September 2, 2001 September 2, 2001
Turner 72 Turner 72
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/