draft-ietf-smime-symkeydist-09.txt   draft-ietf-smime-symkeydist-10.txt 
SMIME Working Group S. Turner, IECA
Intended Status: Standard Track
Expires: July 28, 2008
SMIME Working Group S. Turner
Internet Draft IECA
Document: draft-ietf-smime-symkeydist-09.txt January 2003
CMS Symmetric Key Management and Distribution CMS Symmetric Key Management and Distribution
draft-ietf-smime-symkeydist-10.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with By submitting this Internet-Draft, each author represents that any
all provisions of Section 10 of RFC2026. applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
This document is an Internet-Draft. Internet-Drafts are working Internet-Drafts are working documents of the Internet Engineering
documents of the Internet Engineering Task Force (IETF), its areas, Task Force (IETF), its areas, and its working groups. Note that
and its working groups. Note that other groups may also distribute other groups may also distribute working documents as Internet-
working documents as Internet-Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six months
months and may be updated, replaced, or obsoleted by other documents and may be updated, replaced, or obsoleted by other documents at any
at any time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html
This draft is being discussed on the 'ietf-smime' mailing list. To This Internet-Draft will expire on July 28, 2008.
subscribe, send a message to ietf-smime-request@imc.org with the
single word subscribe in the body of the message. There is a Web Copyright Notice
site for the mailing list at <http://www.imc.org/ietf-smime/>.
Copyright (C) The IETF Trust (2008).
Abstract Abstract
This document describes a mechanism to manage (i.e., setup, This document describes a mechanism to manage (i.e., setup,
distribute, and rekey) keys used with symmetric cryptographic distribute, and rekey) keys used with symmetric cryptographic
algorithms. Also defined herein is a mechanism to organize users algorithms. Also defined herein is a mechanism to organize users into
into groups to support distribution of encrypted content using groups to support distribution of encrypted content using symmetric
symmetric cryptographic algorithms. The mechanism uses the cryptographic algorithms. The mechanism uses the Cryptographic
Cryptographic Message Syntax (CMS) protocol [CMS] and Certificate Message Syntax (CMS) protocol [CMS] and Certificate Management
Management Message over CMS (CMC) protocol [CMC] to manage the Message over CMS (CMC) protocol [CMC] to manage the symmetric keys.
symmetric keys. Any member of the group can then later use this Any member of the group can then later use this distributed shared
distributed shared key to decrypt other CMS encrypted objects with key to decrypt other CMS encrypted objects with the symmetric key.
the symmetric key. This mechanism has been developed to support
S/MIME Mail List Agents (MLAs).
Turner 1 This mechanism has been developed to support S/MIME Mail List Agents
And Distribution (MLAs).
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 [STDWORDS]. document are to be interpreted as described in [RFC2119].
1 INTRODUCTION.....................................................3
1.1 APPLICABILITY TO E-MAIL........................................4
1.2 APPLICABILITY TO REPOSITORIES..................................4
1.3 USING THE GROUP KEY............................................4
2 ARCHITECTURE.....................................................5
3 PROTOCOL INTERACTIONS............................................6
3.1 CONTROL ATTRIBUTES.............................................8
3.1.1 GL USE KEK...................................................9
3.1.2 DELETE GL...................................................13
3.1.3 ADD GL MEMBER...............................................13
3.1.4 DELETE GL MEMBER............................................14
3.1.5 REKEY GL....................................................15
3.1.6 ADD GL OWNER................................................15
3.1.7 REMOVE GL OWNER.............................................16
3.1.8 GL KEY COMPROMISE...........................................16
3.1.9 GL KEY REFRESH..............................................16
3.1.10 GLA QUERY REQUEST AND RESPONSE.............................17
3.1.10.1 GLA QUERY REQUEST........................................17
3.1.10.2 GLA QUERY RESPONSE.......................................17
3.1.10.3 REQUEST AND RESPONSE TYPES...............................18
3.1.12 PROVIDE CERT...............................................18
3.1.13 UPDATE CERT................................................19
3.1.14 GL KEY.....................................................20
3.2 USE OF CMC, CMS, AND PKIX.....................................21
3.2.1 PROTECTION LAYERS...........................................22
3.2.1.1 MINIMUM PROTECTION........................................22
3.2.1.2 ADDITIONAL PROTECTION.....................................22
3.2.2 COMBINING REQUESTS AND RESPONSES............................23
3.2.3 GLA GENERATED MESSAGES......................................24
3.2.4 CMC CONTROL ATTRIBUTES AND CMS SIGNED ATTRIBUTES............25
3.2.4.1 USING CMCSTATUSINFOEXT....................................25
3.2.4.2 USING TRANSACTIONID.......................................28
3.2.4.3 USING NONCES AND SIGNINGTIME..............................28
3.2.4.4 CMC AND CMS ATTRIBUTE SUPPORT REQUIREMENTS................29
3.2.5 RESUBMITTED GL MEMBER MESSAGES..............................29
3.2.6 PKIX CERTIFICATE AND CRL PROFILE............................29
4 ADMINISTRATIVE MESSAGES.........................................30
4.1 ASSIGN KEK TO GL..............................................30
4.2 DELETE GL FROM GLA............................................33
4.3 ADD MEMBERS TO GL.............................................36
4.3.1 GLO INITIATED ADDITIONS.....................................37
4.3.2 PROSPECTIVE MEMBER INITIATED ADDITIONS......................43
4.4 DELETE MEMBERS FROM GL........................................45
4.4.1 GLO INITIATED DELETIONS.....................................46
4.4.2 MEMBER INITIATED DELETIONS..................................51
4.5 REQUEST REKEY OF GL...........................................53
Turner Expires July 2003 2 Table of Contents
And Distribution
4.5.1 GLO INITIATED REKEY REQUESTS................................54 1. Introduction...................................................3
4.5.2 GLA INITIATED REKEY REQUESTS................................56 1.1. Applicability to E-mail...................................4
4.6 CHANGE GLO....................................................57 1.2. Applicability to Repositories.............................5
4.7 INDICATE KEK COMPROMISE.......................................60 1.3. Using the Group Key.......................................5
4.7.1 GL MEMBER INITIATED KEK COMPROMISE MESSAGE..................60 2. Architecture...................................................5
4.7.2 GLO INITIATED KEK COMPROMISE MESSAGE........................61 3. Protocol Interactions..........................................7
4.8 REQUEST KEK REFRESH...........................................63 3.1. Control Attributes........................................8
4.9 GLA QUERY REQUEST AND RESPONSE................................64 3.1.1. GL USE KEK..........................................10
4.10 UPDATE MEMBER CERTIFICATE....................................66 3.1.2. Delete GL...........................................13
4.10.1 GLO AND GLA INITIATED UPDATE MEMBER CERTIFICATE............67 3.1.3. Add GL Member.......................................14
4.10.2 GL MEMBER INITIATED UPDATE MEMBER CERTIFICATE..............69 3.1.4. Delete GL Member....................................15
5 DISTRIBUTION MESSAGE............................................70 3.1.5. Rekey GL............................................15
5.1 DISTRIBUTION PROCESS..........................................71 3.1.6. Add GL Owner........................................16
6 ALGORITHMS......................................................72 3.1.7. Remove GL Owner.....................................17
6.1 KEK GENERATION ALGORITHM......................................72 3.1.8. GL Key Compromise...................................17
6.2 SHARED KEK WRAP ALGORITHM.....................................72 3.1.9. GL Key Refresh......................................17
6.3 SHARED KEK ALGORITHM..........................................72 3.1.10. GLA Query Request and Response.....................18
7 MESSAGE TRANSPORT...............................................73 3.1.10.1. GLA Query Request.............................18
8 SECURITY CONSIDERATIONS.........................................73 3.1.10.2. GLA Query Response............................18
9 REFERENCES......................................................74 3.1.10.3. Request and Response Types....................19
9.1 INFORMATIVE...................................................74 3.1.11. Provide Cert.......................................19
9.1 NORMATIVE.....................................................74 3.1.12. Update Cert........................................20
10 ACKNOWLEDGEMENTS...............................................75 3.1.13. GL Key.............................................21
11 AUTHOR'S ADDRESSES.............................................75 3.2. Use of CMC, CMS, and PKIX................................23
ANNEX A: ASN.1 MODULE.............................................76 3.2.1. Protection Layers...................................23
3.2.1.1. Minimum Protection.............................23
3.2.1.2. Additional Protection..........................24
3.2.2. Combining Requests and Responses....................25
3.2.3. GLA Generated Messages..............................26
3.2.4. CMC Control Attributes and CMS Signed Attributes....27
3.2.4.1. Using cMCStatusInfoExt.........................27
3.2.4.2. Using transactionId............................30
3.2.4.3. Using nonces and signingTime...................30
3.2.4.4. CMC and CMS Attribute Support Requirements.....31
3.2.5. Resubmitted GL Member Messages......................31
3.2.6. PKIX Certificate and CRL Profile....................32
4. Administrative Messages.......................................32
4.1. Assign KEK To GL.........................................32
4.2. Delete GL From GLA.......................................36
4.3. Add Members To GL........................................38
4.3.1. GLO Initiated Additions.............................40
4.3.2. Prospective Member Initiated Additions..............46
4.4. Delete Members From GL...................................49
4.4.1. GLO Initiated Deletions.............................50
4.4.2. Member Initiated Deletions..........................55
4.5. Request Rekey Of GL......................................57
4.5.1. GLO Initiated Rekey Requests........................58
4.5.2. GLA Initiated Rekey Requests........................61
4.6. Change GLO...............................................62
4.7. Indicate KEK Compromise..................................64
4.7.1. GL Member Initiated KEK Compromise Message..........65
4.7.2. GLO Initiated KEK Compromise Message................66
4.8. Request KEK Refresh......................................67
4.9. GLA Query Request and Response...........................69
4.10. Update Member Certificate...............................71
4.10.1. GLO and GLA Initiated Update Member Certificate....72
4.10.2. GL Member Initiated Update Member Certificate......74
5. Distribution Message..........................................75
5.1. Distribution Process.....................................76
6. Algorithms....................................................78
6.1. KEK Generation Algorithm.................................78
6.2. Shared KEK Wrap Algorithm................................78
6.3. Shared KEK Algorithm.....................................78
7. Message Transport.............................................78
8. Security Considerations.......................................78
9. IANA Considerations...........................................80
10. Acknowledgements.............................................80
11. References...................................................80
11.1. Normative References....................................80
11.2. Informative References..................................81
12. ASN.1 Module.................................................81
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 [MSG]), users require a mechanism to distribute (e.g., S/MIME [MSG]), 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
There are essentially two ways to encrypt the data for recipients: are essentially two ways to encrypt the data for recipients: using
using asymmetric algorithms with public key certificates (PKCs) or asymmetric algorithms with public key certificates (PKCs) or
symmetric algorithms with symmetric keys. symmetric algorithms with symmetric keys.
With asymmetric algorithms, the originator forms an originator- With asymmetric algorithms, the originator forms an originator-
determined content-encryption key (CEK) and encrypts the content, determined content-encryption key (CEK) and encrypts the content,
using a symmetric algorithm. Then, using an asymmetric algorithm and using a symmetric algorithm. Then, using an asymmetric algorithm and
the recipient's PKCs, the originator generates per-recipient the recipient's PKCs, the originator generates per-recipient
information that either (a) encrypts the CEK for a particular information that either (a) encrypts the CEK for a particular
recipient (ktri RecipientInfo CHOICE), or (b) transfers sufficient recipient (ktri RecipientInfo CHOICE), or (b) transfers sufficient
parameters to enable a particular recipient to independently parameters to enable a particular recipient to independently generate
generate the same KEK (kari RecipientInfo CHOICE). If the group is the same KEK (kari RecipientInfo CHOICE). If the group is large,
large, processing of the per-recipient information may take quite processing of the per-recipient information may take quite some time,
some time, not to mention the time required to collect and validate not to mention the time required to collect and validate the PKCs for
the PKCs for each of the recipients. Each recipient identifies its each of the recipients. Each recipient identifies its per-recipient
per-recipient information and uses the private key associated with information and uses the private key associated with the public key
the public key of its PKC to decrypt the CEK and hence gain access of its PKC to decrypt the CEK and hence gain access to the encrypted
to the encrypted content. content.
Turner Expires July 2003 3
And Distribution
With symmetric algorithms, the origination process is slightly With symmetric algorithms, the origination process is slightly
different. Instead of using PKCs, the originator uses a previously different. Instead of using PKCs, the originator uses a previously
distributed secret key-encryption key (KEK) to encrypt the CEK distributed secret key-encryption key (KEK) to encrypt the CEK (kekri
(kekri RecipientInfo CHOICE). Only one copy of the encrypted CEK is RecipientInfo CHOICE). Only one copy of the encrypted CEK is required
required because all the recipients already have the shared KEK because all the recipients already have the shared KEK needed to
needed to decrypt the CEK and hence gain access to the encrypted decrypt the CEK and hence gain access to the encrypted content.
content.
The techniques to protect the shared KEK are beyond the scope of The techniques to protect the shared KEK are beyond the scope of this
this document. Only the members of the list and the key manager document. Only the members of the list and the key manager should
should have the KEK in order to maintain confidentiality. Access have the KEK in order to maintain confidentiality. Access control to
control to the information protected by the KEK is determined by the the information protected by the KEK is determined by the entity that
entity that encrypts the information, as all members of the group encrypts the information, as all members of the group have access. If
have access. If the entity that is performing the encryption wants the entity that is performing the encryption wants to ensure some
to ensure some subset of the group does not gain access to the subset of the group does not gain access to the information either a
information either a different KEK should be used (shared only with different KEK should be used (shared only with this smaller group) or
this smaller group) or asymmetric algorithms should be used. asymmetric algorithms should be used.
1.1 Applicability to E-mail 1.1. Applicability to E-mail
One primary audience for this distribution mechanism is e-mail. One primary audience for this distribution mechanism is e-mail.
Distribution lists, sometimes referred to as mail lists, support the Distribution lists, sometimes referred to as mail lists, support the
distribution of messages to recipients subscribed to the mail list. distribution of messages to recipients subscribed to the mail list.
There are two models for how the mail list can be used. If the There are two models for how the mail list can be used. If the
originator is a member of the mail list, the originator sends originator is a member of the mail list, the originator sends
messages encrypted with the shared KEK to the mail list (e.g., messages encrypted with the shared KEK to the mail list (e.g.,
listserv or majordomo) and the message is distributed to the mail listserv or majordomo) and the message is distributed to the mail
list members. If the originator is not a member of the mail list list members. If the originator is not a member of the mail list
(does not have the shared KEK), the originator sends the message (does not have the shared KEK), the originator sends the message
(encrypted for the MLA) to the mail list agent (MLA), and then the (encrypted for the MLA) to the mail list agent (MLA), and then the
MLA uses the shared KEK to encrypt the message for the members. In MLA uses the shared KEK to encrypt the message for the members. In
either case the recipients of the mail list use the previously either case the recipients of the mail list use the previously
distributed-shared KEK to decrypt the message. distributed-shared KEK to decrypt the message.
1.2 Applicability to Repositories 1.2. Applicability to Repositories
Objects can also be distributed via a repository (e.g., Lightweight Objects can also be distributed via a repository (e.g., Lightweight
Directory Protocol (LDAP) servers, X.500 Directory System Agents Directory Protocol (LDAP) servers, X.500 Directory System Agents
(DSAs), Web-based servers). If an object is stored in a repository (DSAs), Web-based servers). If an object is stored in a repository
encrypted with a symmetric key algorithm, anyone with the shared KEK encrypted with a symmetric key algorithm, anyone with the shared KEK
and access to that object can then decrypt that object. The and access to that object can then decrypt that object. The encrypted
encrypted object and the encrypted, shared KEK can be stored in the object and the encrypted, shared KEK can be stored in the repository.
repository.
1.3 Using the Group Key 1.3. 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
supporting mail list agents and one for general message supporting mail list agents and one for general message distribution.
distribution. Scenario 1 depicts the originator sending a public key Scenario 1 depicts the originator sending a public key (PK) protected
message to a MLA who then uses the shared KEK(s) to redistribute the
Turner Expires July 2003 4 message to the members of the list. Scenario 2 depicts the originator
And Distribution sending a shared KEK protected message to a MLA who then
redistributes the message to the members of the list (the MLA only
(PK) protected message to a MLA who then uses the shared KEK(s) to adds additional recipients). The key used by the originator could
redistribute the message to the members of the list. Scenario 2 either be a key shared amongst all recipients or just between the
depicts the originator sending a shared KEK protected message to a member and the MLA. Note that if the originator use a key shared only
MLA who then redistributes the message to the members of the list with the MLA, then the MLA will need to decrypt the message and
(the MLA only adds additional recipients). The key used by the rencrypt the message for the list recipients. Scenario 3 shows an
originator could either be a key shared amongst all recipients or originator sending a shared KEK protected message to a group of
just between the member and the MLA. Note that if the originator use recipients without an intermediate MLA.
a key shared only with the MLA, then the MLA will need to decrypt
the message and rencrypt the message for the list recipients.
Scenario 3 shows an originator sending a shared KEK protected
message to a group of recipients without an intermediate 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
2 Architecture 2. Architecture
Figure 1 depicts the architecture to support symmetric key Figure 1 depicts the architecture to support symmetric key
distribution. The Group List Agent (GLA) supports two distinct distribution. The Group List Agent (GLA) supports two distinct
functions with two different agents: functions with two different agents:
- The Key Management Agent (KMA) which is responsible for - The Key Management Agent (KMA) which is responsible for generating
generating the shared KEKs. the shared KEKs.
- The Group Management Agent (GMA) which is responsible for - The Group Management Agent (GMA) which is responsible for managing
managing the Group List (GL) to which the shared KEKs are the Group List (GL) to which the shared KEKs are distributed.
distributed.
+----------------------------------------------+ +----------------------------------------------+
| Group List Agent | +-------+ | Group List Agent | +-------+
| +------------+ + -----------------------+ | | Group | | +------------+ + -----------------------+ | | Group |
| | Key | | Group Management Agent | |<-->| List | | | Key | | Group Management Agent | |<-->| List |
| | Management |<-->| +------------+ | | | Owner | | | Management |<-->| +------------+ | | | Owner |
| | Agent | | | Group List | | | +-------+ | | Agent | | | Group List | | | +-------+
| +------------+ | +------------+ | | | +------------+ | +------------+ | |
| | / | \ | | | | / | \ | |
| +------------------------+ | | +------------------------+ |
+----------------------------------------------+ +----------------------------------------------+
/ | \ / | \
/ | \ / | \
+----------+ +---------+ +----------+ +----------+ +---------+ +----------+
| Member 1 | | ... | | Member n | | Member 1 | | ... | | Member n |
+----------+ +---------+ +----------+ +----------+ +---------+ +----------+
Figure 1 - Key Distribution Architecture Figure 1 - Key Distribution Architecture
Turner Expires July 2003 5
And Distribution
A GLA may support multiple KMAs. A GLA in general supports only one A GLA may support multiple KMAs. A GLA in general supports only one
GMA, but the GMA may support multiple GLs. Multiple KMAs may support GMA, but the GMA may support multiple GLs. Multiple KMAs may support
a GMA in the same fashion as GLAs support multiple KMAs. Assigning a a GMA in the same fashion as GLAs support multiple KMAs. Assigning a
particular KMA to a GL is beyond the scope of this document. particular KMA to a GL is beyond the scope of this document.
Modeling real world GL implementations shows that there are very Modeling real world GL implementations shows that there are very
restrictive GLs, where a human determines GL membership, and very restrictive GLs, where a human determines GL membership, and very
open GLs, where there are no restrictions on GL membership. To open GLs, where there are no restrictions on GL membership. To
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
mechanism for managed lists is beyond the scope of this document. for managed lists is beyond the scope of this document.
Note: If the distribution for the list is performed by an entity Note: If the distribution for the list is performed by an entity
other than the originator (e.g., an MLA distributing a mail other than the originator (e.g., an MLA distributing a mail message),
message), this entity can also enforce access control rules. this entity can also enforce access control rules.
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 to the entities who 'own' the GL and who are allowed to make changes to 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 also set up lists GLO(s) may or may not be GL members. GLO(s) may also set up lists
that are closed, where the GLO solely determines GL membership. that are closed, where the GLO solely determines GL membership.
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
or they could be supported by two different entities. If two they could be supported by two different entities. If two entities
entities are used, they could be located on one or two platforms. are used, they could be located on one or two platforms. There is
There is however a close relationship between the KMA and GMA however a close relationship between the KMA and GMA functions. If
functions. If the GMA stores all information pertaining to the GLs the GMA stores all information pertaining to the GLs and the KMA
and the KMA merely generates keys, a corrupted GMA could cause merely generates keys, a corrupted GMA could cause havoc. To protect
havoc. To protect against a corrupted GMA, the KMA would be forced against a corrupted GMA, the KMA would be forced to double check the
to double check the requests it receives to ensure the GMA did not requests it receives to ensure the GMA did not tamper with them.
tamper with them. These duplicative checks blur the functionality of These duplicative checks blur the functionality of the two components
the two components together. For this reason, the interactions together. For this reason, the interactions between the KMA and GMA
between the KMA and GMA are beyond the scope of this document. are beyond the scope of this document.
Proprietary mechanisms may be used to separate the functions by Proprietary mechanisms may be used to separate the functions by
strengthening the trust relationship between the two entities. strengthening the trust relationship between the two entities.
Henceforth, the distinction between the two agents is not discussed Henceforth, the distinction between the two agents is not discussed
further; the term GLA will be used to address both functions. It further; the term GLA will be used to address both functions. It
should be noted that corrupt GLA can always cause havoc. should be noted 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
manage GLs; however, this document does not address securing these manage GLs; however, this document does not address securing these
mechanisms, as they are not standardized. Instead, it defines mechanisms, as they are not standardized. Instead, it defines
protocol interactions, as depicted in Figure 2, used by the GL protocol interactions, as depicted in Figure 2, used by the GL
members, GLA, and GLO(s) to manage GLs and distribute shared KEKs. members, GLA, and GLO(s) to manage GLs and distribute shared KEKs.
The interactions have been divided into administration messages and The interactions have been divided into administration messages and
Turner Expires July 2003 6
And Distribution
distribution messages. The administrative messages are the request distribution messages. The administrative messages are the request
and response messages needed to setup the GL, delete the GL, add and response messages needed to setup the GL, delete the GL, add
members to the GL, delete members of the GL, request a group rekey, members to the GL, delete members of the GL, request a group rekey,
add owners to the GL, remove owners of the GL, indicate a group key add owners to the GL, remove owners of the GL, indicate a group key
compromise, refresh a group key, interrogate the GLA, and update compromise, refresh a group key, interrogate the GLA, and update
member's and owner's public key certificates. The distribution member's and owner's public key certificates. The distribution
messages are the messages that distribute the shared KEKs. The messages are the messages that distribute the shared KEKs. The
following sections describe the ASN.1 for both the administration following sections describe the ASN.1 for both the administration and
and distribution messages. Section 4 describes how to use the distribution messages. Section 4 describes how to use the
administration messages, and section 5 describes how to use the administration messages, and section 5 describes how to use the
distribution messages. distribution messages.
+-----+ +----------+ +-----+ +----------+
| GLO | <---+ +----> | Member 1 | | GLO | <---+ +----> | Member 1 |
+-----+ | | +----------+ +-----+ | | +----------+
| | | |
+-----+ <------+ | +----------+ +-----+ <------+ | +----------+
| GLA | <-------------+----> | ... | | GLA | <-------------+----> | ... |
+-----+ | +----------+ +-----+ | +----------+
| |
| +----------+ | +----------+
+----> | Member n | +----> | Member n |
+----------+ +----------+
Figure 2 - Protocol Interactions Figure 2 - Protocol Interactions
Turner Expires July 2003 7 3.1. Control Attributes
And Distribution
3.1 Control Attributes
To avoid creating an entirely new protocol, the Certificate To avoid creating an entirely new protocol, the Certificate
Management Messages over CMS (CMC) protocol was chosen as the Management Messages over CMS (CMC) protocol was chosen as the
foundation of this protocol. The main reason for the choice was the foundation of this protocol. The main reason for the choice was the
layering aspect provided by CMC where one or more control attributes layering aspect provided by CMC where one or more control attributes
are included in message, protected with CMS, to request or respond are included in message, protected with CMS, to request or respond to
to a desired action. The CMC PKIData structure is used for requests, a desired action. The CMC PKIData structure is used for requests, and
and the CMC ResponseBody structure is used for responses. The the CMC PKIResponse structure is used for responses. The content-
content-types PKIData and PKIResponse are then encapsulated in CMS's 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
section 3.2). The following are the control attributes defined in 3.2). The following are the control attributes defined in this
this document: 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
skipping to change at line 380 skipping to change at page 9, line 4
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
glaQueryRequest id-skd 11 GLAQueryRequest glaQueryRequest id-skd 11 GLAQueryRequest
glaQueryResponse id-skd 12 GLAQueryResponse glaQueryResponse id-skd 12 GLAQueryResponse
glProvideCert id-skd 13 GLManageCert glProvideCert id-skd 13 GLManageCert
glUpdateCert id-skd 14 GLManageCert glUpdateCert id-skd 14 GLManageCert
glKey id-skd 15 GLKey glKey id-skd 15 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, and F for following meanings: O for originate, R for receive, and F for
forward. There are three types of implementations: GLOs, GLAs, and forward. There are three types of implementations: GLOs, GLAs, and GL
GL members. The GLO is an optional component hence all GLO O and GLO members. The GLO is an optional component hence all GLO O and GLO R
R messages are optional, and GLA F messages are optional. The first messages are optional, and GLA F messages are optional. The first
table includes messages that conformant implementions MUST support. table includes messages that conformant implementions MUST support.
The second table includes messages that MAY be implemented. The The second table includes messages that MAY be implemented. The
second table should be interpreted as follows: if the control second table should be interpreted as follows: if the control
attribute is implemented by a component then it must be implemented attribute is implemented by a component then it must be implemented
as indicated. For example, if a GLA is implemented that supports the as indicated. For example, if a GLA is implemented that supports the
glAddMember control attribute, then it MUST support receiving the glAddMember control attribute, then it MUST support receiving the
glAddMember message. Note that "-" means not applicable. glAddMember message. Note that "-" means not applicable.
Turner Expires July 2003 8
And Distribution
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
Optional Optional
skipping to change at line 430 skipping to change at page 10, line 5
MAY - | - SHOULD - | MAY - | glaQueryRequest MAY - | - SHOULD - | MAY - | glaQueryRequest
- MAY | SHOULD - - | - MAY | glaQueryResponse - MAY | SHOULD - - | - MAY | glaQueryResponse
glaQueryResponse and gloResponse are carried in the CMC PKIResponse glaQueryResponse and gloResponse are carried in the CMC PKIResponse
content-type, all other control attributes are carried in the CMC content-type, all other control attributes are carried in the CMC
PKIData content-type. The exception is glUpdateCert which can be PKIData content-type. The exception is glUpdateCert which can be
carried in either PKIData or PKIResponse. carried in either PKIData or PKIResponse.
Success and failure messages use CMC (see section 3.2.4). Success and failure messages use CMC (see section 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
control attribute has the syntax GLUseKEK: attribute has 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 Expires July 2003 9
And Distribution
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 } certificate Certificates OPTIONAL }
Certificates ::= SEQUENCE { Certificates ::= SEQUENCE {
skipping to change at line 475 skipping to change at page 11, line 4
CertificateSet ::= SET SIZE (1..MAX) OF CertificateChoices CertificateSet ::= SET SIZE (1..MAX) OF CertificateChoices
-- CertificateChoices supports X.509 public key certificates in -- CertificateChoices supports X.509 public key certificates in
-- certificates and v2 attribute certificates in v2AttrCert. -- certificates and v2 attribute certificates in v2AttrCert.
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 DEFAULT 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-aes128-wrap } }
The fields in GLUseKEK have the following meaning: The fields in GLUseKEK have the following meaning:
- glInfo indicates the name of the GL in glName and the address of - glInfo indicates the name of the GL in glName and the address of
the GL in glAddress. The glName and glAddress can be the same, the GL in glAddress. The glName and glAddress can be the same,
but this is not always the case. Both the name and address MUST but this is not always the case. Both the name and address MUST
be unique for a given GLA. be unique for a given GLA.
- glOwnerInfo indicates: - glOwnerInfo indicates:
- glOwnerName indicates the name of the owner of the GL. One of -- glOwnerName indicates the name of the owner of the GL. One of
the names in glOwnerName MUST match one of the names in the the names in glOwnerName MUST match one of the names in the
certificate (either the subject distinguished name or one of certificate (either the subject distinguished name or one of
Turner Expires July 2003 10
And Distribution
the subject alternative names) used to sign this the subject alternative names) used to sign this
SignedData.PKIData creating the GL (i.e., the immediate SignedData.PKIData creating the GL (i.e., the immediate
signer). signer).
- glOwnerAddress indicates the address of the owner of the GL. -- glOwnerAddress indicates the address of the owner of the GL.
- certificates MAY be included. It contains the following three -- certificates MAY be included. It contains the following three
fields: fields:
- certificates.pKC includes the encryption certificate for the --- certificates.pKC includes the encryption certificate for
GLO. It will be used to encrypt responses for the GLO. the GLO. It will be used to encrypt responses for the
GLO.
- certificates.aC MAY be included to convey any attribute
certificate (see [ACPROF]) associated with the encryption
certificate of the GLO included in certificates.pKC.
- certificates.certPath MAY also be included to convey --- certificates.aC MAY be included to convey any attribute
certificates that might aid the recipient in constructing certificate (see [ACPROF]) associated with the
valid certification paths for the certificate provided in encryption certificate of the GLO included in
certificates.pKC and the attribute certificates provided in certificates.pKC.
certificates.aC. Theses certificates are optional because
they might already be included elsewhere in the message
(e.g., in the outer CMS layer).
- glAdministration indicates how the GL ought to be administered. --- certificates.certPath MAY also be included to convey
The default is for the list to be managed. Three values are certificates that might aid the recipient in
supported for glAdministration: constructing valid certification paths for the
certificate provided in certificates.pKC and the
attribute certificates provided in certificates.aC.
Theses certificates are optional because they might
already be included elsewhere in the message (e.g., in
the outer CMS layer).
- Unmanaged - When the GLO sets glAdministration to unmanaged, -- glAdministration indicates how the GL ought to be
it is allowing prospective members to request addition and administered. The default is for the list to be managed.
deletion from the GL without GLO intervention. Three values are supported for glAdministration:
- Managed - When the GLO sets glAdministration to managed, it is --- Unmanaged - When the GLO sets glAdministration to
allowing prospective members to request addition and deletion unmanaged, it is allowing prospective members to
from the GL, but the request is redirected by the GLA to GLO request addition and deletion from the GL without GLO
for review. The GLO makes the determination as to whether to intervention.
honor the request.
- Closed - When the GLO sets glAdministration to closed, it is --- Managed - When the GLO sets glAdministration to managed,
not allowing prospective members to request addition or it is allowing prospective members to request addition
deletion from the GL. The GLA will only accept glAddMember and and deletion from the GL, but the request is redirected
glDeleteMember requests from the GLO. by the GLA to GLO for review. The GLO makes the
determination as to whether to honor the request.
- glKeyAttributes indicates the attributes the GLO wants the GLA --- Closed - When the GLO sets glAdministration to closed,
to assign to the shared KEK. If this field is omitted, GL rekeys it is not allowing prospective members to request
will be controlled by the GLA, the recipients are allowed to addition or deletion from the GL. The GLA will only
know about one another, the algorithm will be Triple-DES (see accept glAddMember and glDeleteMember requests from the
paragrpah 7), the shared KEK will be valid for a calendar month GLO.
(i.e., first of the month until the last day of the month), and
two shared KEKs will be distributed initially. The fields in
glKeyAttributes have the following meaning:
Turner Expires July 2003 11 -- glKeyAttributes indicates the attributes the GLO wants the
And Distribution GLA to assign to the shared KEK. If this field is omitted,
GL rekeys will be controlled by the GLA, the recipients are
allowed to know about one another, the algorithm will be
Triple-DES (see 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 two shared KEKs will be
distributed initially. The fields in glKeyAttributes have
the following meaning:
- rekeyControlledByGLO indicates whether the GL rekey messages --- rekeyControlledByGLO indicates whether the GL rekey
will be generated by the GLO or by the GLA. The default is for messages will be generated by the GLO or by the GLA.
the GLA to control rekeys. If GL rekey is controlled by the The default is for the GLA to control rekeys. If GL
GLA, the GL will continue to be rekeyed until the GLO deletes rekey is controlled by the GLA, the GL will continue to
the GL or changes the GL rekey to be GLO controlled. be rekeyed until the GLO deletes the GL or changes the
GL rekey to be GLO controlled.
- recipientsNotMutuallyAware indicates that the GLO wants the --- recipientsNotMutuallyAware indicates that the GLO wants
GLA to distribute the shared KEK individually for each of the the GLA to distribute the shared KEK individually for
GL members (i.e., a separate glKey message is sent to each each of the GL members (i.e., a separate glKey message
recipient). The default is for separate glKey message not to is sent to each recipient). The default is for separate
be required. glKey message not to be required.
NOTE: This supports lists where one member does not know the NOTE: This supports lists where one member does not
identities of the other members. For example, a list is know the identities of the other members. For example,
configured granting submit permissions to only one member. All a list is configured granting submit permissions to
other members are 'listening.' The security policy of the list only one member. All other members are 'listening.' The
does not allow the members to know who else is on the list. If security policy of the list does not allow the members
a glKey is constructed for all of the GL members, information to know who else is on the list. If a glKey is
about each of the members may be derived from the information constructed for all of the GL members, information
in RecipientInfos. To make sure the glkey message does not about each of the members may be derived from the
divulge information about the other recipients, a separate information in RecipientInfos. To make sure the glkey
glKey message would be sent to each GL member. message does not divulge information about the other
recipients, a separate glKey message would be sent to
each GL member.
- duration indicates the length of time (in days) during which --- duration indicates the length of time (in days) during
the shared KEK is considered valid. The value zero (0) which the shared KEK is considered valid. The value
indicates that the shared KEK is valid for a calendar month in zero (0) indicates that the shared KEK is valid for a
the UTC Zulu time zone. For example if the duration is zero calendar month in the UTC Zulu time zone. For example
(0), if the GL shared KEK is requested on July 24, the first if the duration is zero (0), if the GL shared KEK is
key will be valid until the end of July and the next key will requested on July 24, the first key will be valid until
be valid for the entire month of August. If the value is not the end of July and the next key will be valid for the
zero (0), the shared KEK will be valid for the number of days entire month of August. If the value is not zero (0),
indicated by the value. For example, if the value of duration the shared KEK will be valid for the number of days
is seven (7) and the shared KEK is requested on Monday but not indicated by the value. For example, if the value of
generated until Tuesday (2359); the shared KEKs will be valid duration is seven (7) and the shared KEK is requested
from Tuesday (2359) to Tuesday (2359). The exact time of the on Monday but not generated until Tuesday (2359); the
day is determined when the key is generated. shared KEKs will be valid from Tuesday (2359) to
Tuesday (2359). The exact time of the 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
the GLA to distribute. To ensure uninterrupted function of the wants the GLA to distribute. To ensure uninterrupted
GL two (2) shared KEKs at a minimum MUST be initially function of the GL two (2) shared KEKs at a minimum
distributed. The second shared KEK is distributed with the MUST be initially distributed. The second shared KEK is
first shared KEK, so that when the first shared KEK is no distributed with the first shared KEK, so that when the
longer valid the second key can be used. If the GLA controls first shared KEK is no longer valid the second key can
rekey then it also indicates the number of shared KEKs the GLO be used. If the GLA controls rekey then it also
wants outstanding at any one time. See sections 4.5 and 5 for indicates the number of shared KEKs the GLO 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
the GLO wants the GLA to use with the shared KEK. The parameters the GLO wants the GLA to use with the shared
parameters are conveyed via the SMIMECapabilities attribute KEK. The parameters are conveyed via the
(see [MSG]). See section 6 for more on algorithms. SMIMECapabilities attribute (see [MSG]). See section 6
for more on algorithms.
Turner Expires July 2003 12
And Distribution
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 has the syntax GeneralName. The glDelete glDelete control attribute has the syntax GeneralName. The glDelete
message MUST be signed by the GLO. The name of the GL to be deleted message MUST be signed by the GLO. The name of the GL to be deleted
is included in GeneralName: is included in GeneralName:
DeleteGL ::= GeneralName DeleteGL ::= GeneralName
3.1.3 Add GL Member 3.1.3. Add GL Member
GLOs use the glAddMember to request addition of new members, and GLOs use the glAddMember to request addition of new members, and
prospective GL members use the glAddMember to request their own prospective GL members use the glAddMember to request their own
addition to the GL. The glAddMember message MUST be signed by either addition to the GL. The glAddMember message MUST be signed by either
the GLO or the prospective GL member. The glAddMember control the GLO or the prospective GL member. The glAddMember control
attribute has the syntax GLAddMember: attribute has 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 {
pKC [0] Certificate OPTIONAL,
-- See [PROFILE]
aC [1] SEQUENCE SIZE (1.. MAX) OF
AttributeCertificate OPTIONAL,
-- See [ACPROF]
certPath [2] CertificateSet OPTIONAL }
-- From [CMS]
-- CertificateSet and CertificateChoices are included only
-- for illustrative purposes as they are imported from [CMS].
CertificateSet ::= SET SIZE (1..MAX) OF CertificateChoices
-- CertificateChoices supports X.509 public key certificates in
-- certificates and v2 attribute certificates in v2AttrCert.
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
be added. added.
- glMember indicates the particulars for the GL member. Both of
the following fields must be unique for a given GL:
Turner Expires July 2003 13 - glMember indicates the particulars for the GL member. Both of the
And Distribution 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.
- certificates MUST be included. It contains the following three -- certificates MUST be included. It contains the following three
fields: fields:
- certificates.pKC includes the member's encryption --- certificates.pKC includes the member's encryption
certificate. It will be used, at least initially, to encrypt certificate. It will be used, at least initially, to
the shared KEK for that member. If the message is generated encrypt the shared KEK for that member. If the message is
by a prospective GL member, the pKC MUST be included. If the generated by a prospective GL member, the pKC MUST be
message is generated by a GLO, the pKC SHOULD be included. included. If the message is generated by a GLO, the pKC
SHOULD be included.
- certificates.aC MAY be included to convey any attribute --- certificates.aC MAY be included to convey any attribute
certificate (see [ACPROF]) associated with the member's certificate (see [ACPROF]) associated with the member's
encryption certificate. encryption certificate.
- certificates.certPath MAY also be included to convey --- certificates.certPath MAY also be included to convey
certificates that might aid the recipient in constructing certificates that might aid the recipient in constructing
valid certification paths for the certificate provided in valid certification paths for the certificate provided in
certificates.pKC and the attribute certificates provided in certificates.pKC and the attribute certificates provided
certificates.aC. These certificates are optional because in certificates.aC. These certificates are optional
they might already be included elsewhere in the message because they might already be included elsewhere in the
(e.g., in the outer CMS layer). message (e.g., in the outer CMS layer).
3.1.4 Delete GL Member 3.1.4. Delete GL Member
GLOs use the glDeleteMember to request deletion of GL members, and GLOs use the glDeleteMember to request deletion of GL members, and GL
GL members use the glDeleteMember to request their own removal from members use the glDeleteMember to request their own removal from the
the GL. The glDeleteMember message MUST be signed by either the GLO GL. The glDeleteMember message MUST be signed by either the GLO or
or the GL member. The glDeleteMember control attribute has the the GL member. The glDeleteMember control attribute has the syntax
syntax GLDeleteMember: 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 or address of the member to - glMemberToDelete indicates the name or address of the member to
be deleted. be deleted.
Turner Expires July 2003 14 3.1.5. Rekey GL
And Distribution
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 has the syntax be signed by the GLO. The glRekey control attribute has the syntax
GLRekey: GLRekey:
GLRekey ::= SEQUENCE { GLRekey ::= SEQUENCE {
glName GeneralName, glName GeneralName,
glAdministration GLAdministration OPTIONAL, glAdministration GLAdministration OPTIONAL,
glNewKeyAttributes GLNewKeyAttributes OPTIONAL, glNewKeyAttributes GLNewKeyAttributes OPTIONAL,
glRekeyAllGLKeys BOOLEAN OPTIONAL } glRekeyAllGLKeys BOOLEAN OPTIONAL }
skipping to change at line 755 skipping to change at page 16, line 31
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 keys GLO wishes to use, the duration of the key, and how many keys
will be issued. The field is only included if there is a change will be issued. The field is only included if there is a change
from the previously registered glKeyAttributes. from the previously registered glKeyAttributes.
- 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.
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 by a administer the GL. The glAddOwner message MUST be signed by a
registered GLO. The glAddOwner control attribute has the syntax registered GLO. The glAddOwner control attribute has the syntax
GLOwnerAdministration: GLOwnerAdministration:
GLOwnerAdministration ::= SEQUENCE { GLOwnerAdministration ::= SEQUENCE {
glName GeneralName, glName GeneralName,
glOwnerInfo GLOwnerInfo } glOwnerInfo GLOwnerInfo }
Turner Expires July 2003 15
And Distribution
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, address, and certificates of the - glOwnerInfo indicates the name, address, and certificates of the
new GLO. As this message includes names of new GLOs, the new GLO. As this message includes names of new GLOs, the
certificates.pKC MUST be included, and it MUST include the certificates.pKC MUST be included, and it MUST include the
encryption certificate of the new GLO. encryption certificate of the new GLO.
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
registered GLO. The glRemoveOwner control attribute has the syntax GLO. The glRemoveOwner control attribute has the syntax
GLOwnerAdministration: 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. The certificates field SHOULD be omitted, as it will be removed. The certificates field SHOULD be omitted, as it will be
ignored. 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
KEK possessed has been compromised. The glKeyCompromise control possessed has been compromised. The glKeyCompromise control attribute
attribute has the syntax GeneralName. This message is always has the syntax GeneralName. This message is always redirected by the
redirected by the GLA to the GLO for further action. The GLA to the GLO for further action. The glkCompromise MAY be included
glkCompromise MAY be included in an EnvelopedData generated with the in an EnvelopedData generated with the compromised shared KEK. The
compromised shared KEK. The name of the GL to which the compromised name of the GL to which the compromised key is associated with is
key is associated with is placed in GeneralName: placed in GeneralName:
GLKCompromise ::= GeneralName GLKCompromise ::= GeneralName
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 has the redistributed to them. The glkRefresh control attribute has the
syntax GLKRefresh. syntax GLKRefresh.
Turner Expires July 2003 16
And Distribution
GLKRefresh ::= SEQUENCE { GLKRefresh ::= SEQUENCE {
glName GeneralName, glName GeneralName,
dates SEQUENCE SIZE (1..MAX) OF Date } dates SEQUENCE SIZE (1..MAX) OF Date }
Date ::= SEQUENCE { 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
wants shared KEKs. 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 start field indicates the first date the GL member wants and the
end field indicates the last date. The end date MAY be omitted end field indicates the last date. The end date MAY be omitted
to indicate the GL member wants all keys from the specified to indicate the GL member wants all keys from the specified
start date to the current date. Note that a procedural mechanism start date to the current date. Note that a procedural mechanism
is needed to restrict users from accessing messages that they is needed to restrict users from accessing messages that they
are not allowed to access. are not allowed to access.
3.1.10 GLA Query Request and Response 3.1.10. GLA Query Request and Response
There are situations where GLOs and GL members may need to determine 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 some information from the GLA about the GL. GLOs and GL members use
the glaQueryRequest, defined in section 3.1.10.1, to request the glaQueryRequest, defined in section 3.1.10.1, to request
information and GLAs use the glaQueryResponse, defined in section information and GLAs use the glaQueryResponse, defined in section
3.1.10.2, to return the requested information. Section 3.1.10.3 3.1.10.2, to return the requested information. Section 3.1.10.3
includes one request and response type and value; others may be includes one request and response type and value; others may be
defined in additional documents. defined in additional documents.
3.1.10.1 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 has the syntax about the GLA. The glaQueryRequest control attribute has the syntax
GLAQueryRequest: GLAQueryRequest:
GLAQueryRequest ::= SEQUENCE { GLAQueryRequest ::= SEQUENCE {
glaRequestType OBJECT IDENTIFIER, glaRequestType OBJECT IDENTIFIER,
glaRequestValue ANY DEFINED BY glaRequestType } glaRequestValue ANY DEFINED BY glaRequestType }
3.1.10.2 GLA Query Response 3.1.10.2. GLA Query Response
GLAs return the glaQueryResponse after receiving a GLAQueryRequest. GLAs 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 has the syntax GLAQueryResponse: control attribute has the syntax GLAQueryResponse:
Turner Expires July 2003 17
And Distribution
GLAQueryResponse ::= SEQUENCE { GLAQueryResponse ::= SEQUENCE {
glaResponseType OBJECT IDENTIFIER, glaResponseType OBJECT IDENTIFIER,
glaResponseValue ANY DEFINED BY glaResponseType } glaResponseValue ANY DEFINED BY glaResponseType }
3.1.10.3 Request and Response Types 3.1.10.3. Request and Response Types
Request and Responses are registered as a pair under the following Request and Responses are registered as a pair under the following
object identifier arc: object identifier arc:
id-cmc-glaRR OBJECT IDENTIFIER ::= { id-cmc 99 } id-cmc-glaRR OBJECT IDENTIFIER ::= { id-cmc 99 }
This document defines one request/response pair for GL members and This document defines one request/response pair for GL members and
GLOs to query the GLA for the list of algorithm it supports. The GLOs to query the GLA for the list of algorithm it supports. The
following object identifier (OID) is included in the glaQueryType following object identifier (OID) is included in the glaQueryType
field: field:
id-cmc-gla-skdAlgRequest OBJECT IDENTIFIER ::={ id-cmc-glaRR 1 } id-cmc-gla-skdAlgRequest OBJECT IDENTIFIER ::={ id-cmc-glaRR 1 }
SKDAlgRequest ::= NULL SKDAlgRequest ::= NULL
If the GLA supports GLAQueryRequest and GLAQueryResponse messages, If the GLA supports GLAQueryRequest and GLAQueryResponse messages,
the GLA may return the following OID in the glaQueryType field: the GLA may return the following OID in the glaQueryType field:
id-cmc-gla-skdAlgResponse OBJECT IDENTIFIER ::= { id-cmc-glaRR 2 } id-cmc-gla-skdAlgResponse OBJECT IDENTIFIER ::= { id-cmc-glaRR 2 }
The glaQueryValue has the form of the smimeCapabilities attributes The glaQueryValue has the form of the smimeCapabilities attributes as
as defined in [MSG]. defined in [MSG].
3.1.12 Provide Cert 3.1.11. Provide Cert
GLAs and GLOs use the glProvideCert to request that a GL member GLAs and GLOs use the glProvideCert to request that a GL member
provide an updated or new encryption certificate. The glProvideCert provide an updated or new encryption certificate. The glProvideCert
message MUST be signed by either GLA or GLO. If the GL member's PKC message 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 has been 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 has the syntax GLManageCert: glProvideCert control attribute has the syntax GLManageCert:
GLManageCert ::= SEQUENCE { GLManageCert ::= SEQUENCE {
glName GeneralName, glName GeneralName,
glMember GLMember } glMember GLMember }
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 is to be associated. certificate is to 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.
Turner Expires July 2003 18
And Distribution
- 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.
3.1.13 Update Cert 3.1.12. Update Cert
GL members and GLOs use the glUpdateCert to provide a new GL members and GLOs use the glUpdateCert to provide a new certificate
certificate for the GL. GL members can generate an unsolicited for the GL. GL members can generate an unsolicited glUpdateCert or
glUpdateCert or generate a response glUpdateCert as a result of generate a response glUpdateCert as a result of receiveing a
receiveing a glProvideCert message. GL members MUST sign the glProvideCert message. GL members MUST sign the glUpdateCert. If the
glUpdateCert. If the GL member's encryption certificate has been GL member's encryption certificate has been revoked, the GL member
revoked, the GL member MUST NOT use it to generate the EnvelopedData MUST NOT use it to generate the EnvelopedData that encapsulates the
that encapsulates the glUpdateCert request or response. The glUpdateCert request or response. The glUpdateCert control attribute
glUpdateCert control attribute has the syntax GLManageCert: has the syntax GLManageCert:
GLManageCert ::= SEQUENCE { GLManageCert ::= SEQUENCE {
glName GeneralName, glName GeneralName,
glMember GLMember } glMember GLMember }
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 the particulars for the GL member: - glMember indicates the 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 MAY be omitted if the GLManageCert message is -- certificates MAY be omitted if the GLManageCert message is
sent to request the GL member's certificate; otherwise, it sent to request the GL member's certificate; otherwise, it
MUST be included. It includes the following three fields: MUST be 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 certificate that will be used to encrypt the shared KEK
that member. for that member.
- certificates.aC MAY be included to convey one or more --- certificates.aC MAY be included to convey one or more
attribute certificate associated with the member's attribute certificate associated with the member's
encryption certificate. encryption certificate.
- certificates.certPath MAY also be included to convey --- certificates.certPath MAY also be included to convey
certificates that might aid the recipient in constructing certificates that might aid the recipient in
valid certification paths for the certificate provided in constructing valid certification paths for the
certificates.pKC and the attribute certificates provided in certificate provided in certificates.pKC and the
certificates.aC. These certificates is optional because they attribute certificates provided in certificates.aC.
These certificates is optional because they might
Turner Expires July 2003 19 already be included elsewhere in the message (e.g., in
And Distribution
might already be included elsewhere in the message (e.g., in
the outer CMS layer). the outer CMS layer).
3.1.14 GL Key 3.1.13. GL Key
The GLA uses the glKey to distribute the shared KEK. The glKey The GLA uses the glKey to distribute the shared KEK. The glKey
message MUST be signed by the GLA. The glKey control attribute has message MUST be signed by the GLA. The glKey control attribute has
the syntax GLKey: the syntax GLKey:
GLKey ::= SEQUENCE { GLKey ::= SEQUENCE {
glName GeneralName, glName GeneralName,
glIdentifier KEKIdentifier, -- See [CMS] glIdentifier KEKIdentifier, -- See [CMS]
glkWrapped RecipientInfos, -- See [CMS] glkWrapped RecipientInfos, -- See [CMS]
glkAlgorithm AlgorithmIdentifier, glkAlgorithm AlgorithmIdentifier,
skipping to change at line 1025 skipping to change at page 22, line 10
- glkAlgorithm identifies the algorithm the shared KEK is used - glkAlgorithm identifies the algorithm the shared KEK is used
with. Since no encrypted data content is being conveyed at this with. Since no encrypted data content is being conveyed at this
point, the parameters encoded with the algorithm should be the point, the parameters encoded with the algorithm should be the
structure defined for smimeCapabilities rather than encrypted structure defined for smimeCapabilities rather than encrypted
content. 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 in considered valid. GeneralizedTime values MUST be expressed in
UTC (Zulu) and MUST include seconds (i.e., times are UTC (Zulu) and MUST include seconds (i.e., times are
Turner Expires July 2003 20
And Distribution
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 in considered invalid. GeneralizedTime values MUST be expressed in
UTC (Zulu) and MUST include seconds (i.e., times are UTC (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.
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
TRUE. For each recipient, you want to generate a message that TRUE. 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 the requested number of glKey messages. - The GLA MUST generate the requested number of glKey messages. The
The value in glUseKEK.glKeyAttributes.generationCounter value in glUseKEK.glKeyAttributes.generationCounter indicates
indicates the number of glKey messages requested. the number of glKey messages requested.
If the glKey message is in response to a glRekey message: If the glKey message is in response to a glRekey message:
- The GLA MUST generate separate glKey messages for each recipient - The GLA MUST generate separate glKey messages for each recipient
if glRekey.glNewKeyAttributes.recipientsNotMutuallyAware is set if glRekey.glNewKeyAttributes.recipientsNotMutuallyAware is set
to TRUE. to TRUE.
- The GLA MUST generate the requested number of glKey messages. - The GLA MUST generate the requested number of glKey messages. The
The value in glUseKEK.glKeyAttributes.generationCounter value in glUseKEK.glKeyAttributes.generationCounter indicates
indicates the number of glKey messages requested. the number of glKey messages requested.
- The GLA MUST generate one glKey messagefor each outstanding - The GLA MUST generate one glKey messagefor each outstanding
shared KEKs for the GL when glRekeyAllGLKeys is set to TRUE. shared KEKs for the GL when glRekeyAllGLKeys is set to TRUE.
If the glKey message was not in response to a glRekey or glUseKEK If the glKey message was not in response to a glRekey or glUseKEK
(e.g., where the GLA controls rekey): (e.g., where the GLA controls rekey):
- The GLA MUST generate separate glKey messages for each recipient - The GLA MUST generate separate glKey messages for each recipient
when glUseKEK.glNewKeyAttributes.recipientsNotMutuallyAware that when glUseKEK.glNewKeyAttributes.recipientsNotMutuallyAware that
set up the GL was set to TRUE. set up the GL was set to TRUE.
- The GLA MAY generate glKey messages prior to the duration on the - The GLA MAY generate glKey messages prior to the duration on the
last outstanding shared KEK expiring, where the number of glKey last outstanding shared KEK expiring, where the number of glKey
messages generated is generationCounter minus one (1). Other messages generated is generationCounter minus one (1). Other
distribution mechanisms can also be supported to support this distribution mechanisms can also be supported to support this
functionality. functionality.
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 the PKIX The following sections outline the use of CMC, CMS, and the PKIX
certificate and CRL profile. certificate and CRL profile.
Turner Expires July 2003 21 3.2.1. Protection Layers
And Distribution
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 in this document. control attributes defined in this document.
Note: There are multiple ways to encapsulate SignedData and Note: There are multiple ways to encapsulate SignedData and
EnvelopedData. The first is to use a MIME wrapper around each EnvelopedData. The first is to use a MIME wrapper around each
ContentInfo, as specified in [MSG]. The second is to not use a MIME ContentInfo, as specified in [MSG]. The second is to not use a MIME
wrapper around each ContentInfo, as specified in Transporting S/MIME wrapper around each ContentInfo, as specified in Transporting S/MIME
Objects in X.400 [X400TRANS]. Objects in X.400 [X400TRANS].
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
depiction of the minimum wrappings: of the minimum wrappings:
Minimum Protection Minimum Protection
------------------ ------------------
SignedData SignedData
PKIData or PKIResponse PKIData or PKIResponse
controlSequence controlSequence
Prior to taking any action on any request or response SignedData(s) Prior to taking any action on any request or response SignedData(s)
MUST be processed according to [CMS]. MUST be processed according to [CMS].
3.2.1.2 Additional Protection 3.2.1.2. Additional Protection
An additional EnvelopedData MAY also be used to provide An additional EnvelopedData MAY also be used to provide
confidentiality of the request and response. An additional confidentiality of the request and response. An additional SignedData
SignedData MAY also be added to provide authentication and integrity MAY also be added to provide authentication and integrity of the
of the encapsulated EnvelopedData. The following is a depiction of encapsulated EnvelopedData. The following is a depiction of the
the optional additional wrappings: optional additional wrappings:
Authentication and Integrity Authentication and Integrity
Confidentiality Protection of Confidentiality Protection Confidentiality Protection 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 is encrypted, the confidentiality of the If an incoming message is 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]. If a SignedData is added over an processed as specified in [CMS]. If a SignedData is added over an
Turner Expires July 2003 22
And Distribution
EnvelopedData, a ContentHints attribute SHOULD be added. See EnvelopedData, a ContentHints attribute SHOULD be added. See
paragraph 2.9 of Extended Security Services for S/MIME [ESS]. paragraph 2.9 of Extended Security Services for S/MIME [ESS].
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 include the GLA as a recipient. If the GLA EnvelopedData MUST include the GLA as a recipient. If the GLA
forwards the GL member request to the GLO, then the GLA MUST decrypt forwards the GL member request to the GLO, then the GLA MUST decrypt
the EnvelopedData content, strip the confidentiality layer, and the EnvelopedData content, strip the confidentiality layer, and apply
apply its own confidentiality layer as an EnvelopedData with the GLO its own confidentiality layer as an EnvelopedData with the GLO as a
as a recipient. recipient.
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
different GLs. That is, requests corresponding to two different GLs different GLs. That is, requests corresponding to two different GLs
are included in different cmsSequences. The following is a diagram are 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
and PKIResponse: PKIResponse:
Multiple Request and Response Multiple Request and Response
Request Response Request Response
------- -------- ------- --------
SignedData SignedData SignedData SignedData
PKIData PKIResponse PKIData PKIResponse
cmsSequence cmsSequence cmsSequence cmsSequence
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 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 Expires July 2003 23 When applying confidentiality to multiple requests and responses, all
And Distribution of the requests/response MAY be included in one EnvelopedData.
When applying confidentiality to multiple requests and responses,
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
skipping to change at line 1213 skipping to change at page 26, line 40
--------------------------- ---------------------------
glUseKEK & glDeleteMember glUseKEK & glDeleteMember
glUseKEK & glRekey glUseKEK & glRekey
glUseKEK & glDelete glUseKEK & glDelete
glDelete & glAddMember glDelete & glAddMember
glDelete & glDeleteMember glDelete & glDeleteMember
glDelete & glRekey glDelete & glRekey
glDelete & glAddOwner glDelete & glAddOwner
glDelete & glRemoveOwner glDelete & glRemoveOwner
To avoid unnecessary errors, certain requests and responses SHOULD To avoid unnecessary errors, certain requests and responses SHOULD be
be processed prior to others. The following is the priority of processed prior to others. The following is the priority of message
message processing, if not listed it is an implementation decision processing, if not listed it is an implementation decision as to
as to which to process first: glUseKEK before glAddMember, glRekey which to process first: glUseKEK before glAddMember, glRekey before
before glAddMember, and glDeleteMember before glRekey. Note that glAddMember, and glDeleteMember before glRekey. Note that there is a
there is a processing priority but it does not imply an ordering processing priority but it does not imply an ordering within the
within the content. content.
3.2.3 GLA Generated Messages 3.2.3. GLA Generated Messages
When the GLA generates a success or fail message, it generates one When the GLA generates a success or fail message, it generates one
for each request. SKDFailInfo values of unsupportedDuration, for each request. SKDFailInfo values of unsupportedDuration,
Turner Expires July 2003 24
And Distribution
unsupportedDeliveryMethod, unsupportedAlgorithm, noGLONameMatch, unsupportedDeliveryMethod, unsupportedAlgorithm, noGLONameMatch,
nameAlreadyInUse, alreadyAnOwner, notAnOwner are not returned to GL nameAlreadyInUse, alreadyAnOwner, notAnOwner are not returned to GL
members. members.
If GLKeyAttributes.recipientsNotMutuallyAware is set to TRUE, a If GLKeyAttributes.recipientsNotMutuallyAware is set to TRUE, a
separate PKIResponse.cMCStatusInfoExt and PKIData.glKey MUST be separate PKIResponse.cMCStatusInfoExt and PKIData.glKey MUST be
generated for each recipient. However, it is valid to send one generated for each recipient. However, it is valid to send one
message with multiple attributes to the same recipient. message with multiple attributes to the same recipient.
If the GL has multiple GLOs, the GLA MUST send cMCStatusInfoExt If the GL has multiple GLOs, the GLA MUST send cMCStatusInfoExt
skipping to change at line 1256 skipping to change at page 27, line 31
GLA Forwarded Requests GLA Forwarded Requests
---------------------- ----------------------
SignedData SignedData
PKIData PKIData
cmsSequence cmsSequence
SignedData SignedData
PKIData PKIData
controlSequence controlSequence
3.2.4 CMC Control Attributes and CMS Signed Attributes 3.2.4. CMC Control Attributes and CMS Signed Attributes
CMC carries control attributes as CMS signed attributes. These CMC carries control attributes as CMS signed attributes. These
attributes are defined in [CMC] and [CMS]. Some of these attributes attributes are defined in [CMC] and [CMS]. Some of these attributes
are REQUIRED; others are OPTIONAL. The required attributes are as are REQUIRED; others are OPTIONAL. The required attributes are as
follows: cMCStatusInfoExt transactionId, senderNonce, follows: cMCStatusInfoExt transactionId, senderNonce, recipientNonce,
recipientNonce, queryPending, and signingTime. Other attributes can queryPending, and signingTime. Other attributes can also be used;
also be used; however, their use is beyond the scope of this however, their use is beyond the scope of this document. The
document. The following sections specify requirements in addition to following sections specify requirements in addition to those already
those already specified in [CMC] and [CMS]. specified in [CMC] and [CMS].
3.2.4.1 Using cMCStatusInfoExt 3.2.4.1. Using cMCStatusInfoExt
cMCStatusInfoExt is used by GLAs to indicate to GLOs and GL members cMCStatusInfoExt is used by GLAs to indicate to GLOs and GL members
that a request was unsuccessful. Two classes of failure codes are that a request was unsuccessful. Two classes of failure codes are
used within this document. Errors from the CMCFailInfo list, found used within this document. Errors from the CMCFailInfo list, found in
in section 5.1.4 of CMC, are encoded as defined in CMC. Error codes section 5.1.4 of CMC, are encoded as defined in CMC. Error codes
defined in this document are encoded using the ExtendedFailInfo defined in this document are encoded using the ExtendedFailInfo field
field of the cmcStatusInfoExt structure. If the same failure code of the cmcStatusInfoExt structure. If the same failure code applies
applies to multiple commands, a single cmcStatusInfoExt structure to multiple commands, a single cmcStatusInfoExt structure can be used
can be used with multiple items in cMCStatusInfoExt.bodyList. The with multiple items in cMCStatusInfoExt.bodyList. The GLA MAY also
GLA MAY also return other pertinent information in statusString. The return other pertinent information in statusString. The SKDFailInfo
SKDFailInfo object identifier and value are: object identifier and value are:
Turner Expires July 2003 25
And Distribution
id-cet-skdFailInfo OBJECT IDENTIFIER ::= { iso(1) id-cet-skdFailInfo OBJECT IDENTIFIER ::= { iso(1)
identified-organization(3) dod(6) internet(1) security(5) identified-organization(3) dod(6) internet(1) security(5)
mechanisms(5) pkix(7) cet(15) skdFailInfo(1) } mechanisms(5) pkix(7) cet(15) skdFailInfo(1) }
SKDFailInfo ::= INTEGER { SKDFailInfo ::= INTEGER {
unspecified (0), unspecified (0),
closedGL (1), closedGL (1),
unsupportedDuration (2), unsupportedDuration (2),
noGLACertificate (3), noGLACertificate (3),
skipping to change at line 1313 skipping to change at page 28, line 38
The values have the following meaning: The values have the following meaning:
- unspecified indicates that the GLA is unable or unwilling to - unspecified indicates that the GLA is unable or unwilling to
perform the requested action and does not want to indicate the perform the requested action and does not want to indicate the
reason. reason.
- closedGL indicates that members can only be added or deleted by - closedGL indicates that members can only be added or deleted by
the GLO. the GLO.
- unsupportedDuration indicates the GLA does not support - unsupportedDuration indicates the GLA does not support generating
generating keys that are valid for the requested duration. keys that are valid for the requested duration.
- noGLACertificate indicates that the GLA does not have a valid - noGLACertificate indicates that the GLA does not have a valid
certificate. certificate.
- invalidCert indicates the member's encryption certificate was - invalidCert indicates the member's encryption certificate was not
not verifiable (i.e., signature did not validate, certificate's verifiable (i.e., signature did not validate, certificate's
serial number present on a CRL, expired, etc.). serial number present on a CRL, expired, etc.).
- unsupportedAlgorithm indicates the GLA does not support the - unsupportedAlgorithm indicates the GLA does not support the
requested algorithm. requested algorithm.
- noGLONameMatch indicates that one of the names in the - noGLONameMatch indicates that one of the names in the certificate
certificate used to sign a request does not match the name of a used to sign a request does not match the name of a registered
registered GLO. GLO.
- invalidGLName indicates the GLA does not support the glName - invalidGLName indicates the GLA does not support the glName
present in the request. present in the request.
Turner Expires July 2003 26
And Distribution
- nameAlreadyInUse indicates the glName is already assigned on the - nameAlreadyInUse indicates the glName is already assigned on the
GLA. GLA.
- noSpam indicates the prospective GL member did not sign the - noSpam indicates the prospective GL member did not sign the
request (i.e., if the name in glMember.glMemberName does not request (i.e., if the name in glMember.glMemberName does not
match one of the names (either the subject distinguished name or match one of the names (either the subject distinguished name or
one of the subject alternative names) in the certificate used to one of the subject alternative names) in the certificate used to
sign the request). sign the request).
- alreadyAMember indicates the prospective GL member is already a - alreadyAMember indicates the prospective GL member is already a
skipping to change at line 1363 skipping to change at page 29, line 39
- notAnOwner indicates the prospective GLO to be deleted is not - notAnOwner indicates the prospective GLO to be deleted is not
presently a GLO. presently a GLO.
cMCStatusInfoExt is used by GLAs to indicate to GLOs and GL members cMCStatusInfoExt is used by GLAs to indicate to GLOs and GL members
that a request was successfully completed. If the request was that a request was successfully completed. If the request was
successful, the GLA returns a cMCStatusInfoExt response with successful, the GLA returns a cMCStatusInfoExt response with
cMCStatus.success and optionally other pertinent information in cMCStatus.success and optionally other pertinent information in
statusString. statusString.
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
uses cMCStatusInfoExt to indicate the success or failure of the cMCStatusInfoExt to indicate the success or failure of the request.
request. If the request is allowed, cMCStatus.success is returned If the request is allowed, cMCStatus.success is returned and
and statusString is optionally returned to convey additional statusString is optionally returned to convey additional information.
information. If the request is denied, cMCStatus.failed is returned If the request is denied, cMCStatus.failed is returned and
and statusString is optionally returned to convey additional statusString is optionally returned to convey additional information.
information. Additionally, the appropriate SKDFailInfo can be Additionally, the appropriate SKDFailInfo can be included in
included in cMCStatusInfoExt.extendedFailInfo. cMCStatusInfoExt.extendedFailInfo.
cMCStatusInfoExt is used by GLOs, GLAs, and GL members to indicate cMCStatusInfoExt is used by GLOs, GLAs, and GL members to indicate
that signature verification failed. If the signature failed to that signature verification failed. If the signature failed to verify
verify over any control attibute except a cMCStatusInfoExt, a over any control attibute except a cMCStatusInfoExt, a
cMCStatusInfoExt control attribute MUST be returned indicating cMCStatusInfoExt 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
bodyList value is the bodyPartId value from the request or response. value is the bodyPartId value from the request or response. GLOs and
GLOs and GL members who receive cMCStatusInfoExt messages whose GL members who receive cMCStatusInfoExt messages whose signatures are
signatures are invalid SHOULD generate a new request to avoid invalid SHOULD generate a new request to avoid badMessageCheck
badMessageCheck message loops. message loops.
cMCStatusInfoExt is also used by GLOs and GLAs to indicate that a cMCStatusInfoExt 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 cMCStatusInfoExt be processed immediately by the GLA or GLO, the cMCStatusInfoExt
control attribute MUST be returned indicating cMCStatus.pending and control attribute MUST be returned indicating cMCStatus.pending and
Turner Expires July 2003 27
And Distribution
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
cMCStatusInfoExt indicating query pending. cMCStatusInfoExt indicating query pending.
cMCStatusInfoExt is also used by GLAs to indicate that a cMCStatusInfoExt 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 cMCStatusInfoExt control attribute MUST be returned supported, the cMCStatusInfoExt 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.
cMCStatusInfoExt is also used by GL members, GLOs, and GLAs to cMCStatusInfoExt is also used by GL members, GLOs, and GLAs to
indicate that the signingTime (see section 3.2.4.3) is not close indicate that the signingTime (see section 3.2.4.3) is not close
enough to the locally specified time. If the local time is not close enough to the locally specified time. If the local time is not close
enough to the time specified in signingTime, a cMCStatus.failed and enough to the time specified in signingTime, a cMCStatus.failed and
otherInfo.failInfo.badTime MAY be returned. otherInfo.failInfo.badTime MAY be returned.
3.2.4.2 Using transactionId 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
additional transactionId in the outer PKIData, when the GLO transactionId in the outer PKIData, when the GLO generates a
generates a cMCStatusInfoExt response it generates one for the GLA cMCStatusInfoExt response it generates one for the GLA with the GLA's
with the GLA's transactionId and one for the GL member with the GL transactionId and one for the GL member with the GL member's
member's transactionId. transactionId.
3.2.4.3 Using nonces and signingTime 3.2.4.3. Using nonces and signingTime
The use of nonces (see section 5.6 of [CMC]) and an indication of The use of nonces (see section 5.6 of [CMC]) and an indication of
when the message was signed (see section 11.3 of [CMS]) can be used when the message was signed (see section 11.3 of [CMS]) can be used
to provide application-level replay prevention. to provide application-level replay prevention.
To protect the GL, all messages MUST include the signingTime To protect the GL, all messages MUST include the signingTime
attribute. Message originators and recipients can then use the time attribute. Message originators and recipients can then use the time
provided in this attribute to determine whether they have previously provided in this attribute to determine whether they have previously
received the message. received the message.
If the originating message includes a senderNonce, the response to If the originating message includes a senderNonce, the response to
the message MUST include the received senderNonce value as the the message MUST include the received senderNonce value as the
recipientNonce and a new value as the senderNonce value in the recipientNonce and a new value as the senderNonce value in the
response. response.
If a GLA aggragates multiple messages together or forwards a message If a GLA aggragates multiple messages together or forwards a message
to a GLO, the GLA MAY optionally generate a new nonce value and to a GLO, the GLA MAY 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
Turner Expires July 2003 28
And Distribution
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.
For these attributes it is necessary to maintain state information For these attributes it is necessary to maintain state information on
on exchanges to compare one result to another. The time period for exchanges to compare one result to another. The time period for which
which this information is maintained in a local policy. this information is maintained in a local policy.
3.2.4.4 CMC and CMS Attribute Support Requirements 3.2.4.4. CMC and CMS Attribute Support Requirements
The following are the implementation requirements for CMC control The following are the implementation requirements for CMC control
attributes and CMS signed attributes for an implementation be attributes and CMS signed attributes for an implementation be
considered conformant to this specification: considered conformant to this specification:
Implementation Requirement | Implementation Requirement |
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 - | MUST MUST | cMCStatusInfoExt MUST MUST | MUST MUST - | MUST MUST | cMCStatusInfoExt
MAY MAY | MUST MUST - | MAY MAY | transactionId MAY MAY | MUST MUST - | MAY MAY | transactionId
MAY MAY | MUST MUST - | MAY MAY | senderNonce MAY MAY | MUST MUST - | MAY MAY | senderNonce
MAY MAY | MUST MUST - | MAY MAY | recepientNonce MAY MAY | MUST MUST - | MAY MAY | recepientNonce
MUST MUST | MUST MUST - | MUST MUST | SKDFailInfo MUST MUST | MUST MUST - | MUST MUST | SKDFailInfo
MUST MUST | MUST MUST - | MUST MUST | signingTime MUST MUST | MUST MUST - | MUST MUST | signingTime
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
containing the GL member request(s) as a cmsSequence item. If the the GL member request(s) as a cmsSequence item. If the GLO approves
GLO approves the request it can either add a new layer of wrapping the request it can either add a new layer of wrapping and send it
and send it back to the GLA or create a new message and send it to back to the GLA or create a new message and send it to the GLA. (Note
the GLA. (Note in this case there are now 3 layers of PKIData in this case there are now 3 layers of PKIData messages with
messages with appropriate signing layers.) appropriate signing layers.)
3.2.6 PKIX Certificate and CRL Profile 3.2.6. PKIX Certificate and CRL Profile
Signatures, certificates, and CRLs are verified according to the Signatures, certificates, and CRLs are verified according to the PKIX
PKIX profile [PROFILE]. profile [PROFILE].
Name matching is performed according to the PKIX profile [PROFILE]. Name matching is performed according to the PKIX profile [PROFILE].
All distinguished name forms must follow the UTF8String convention All distinguished name forms must follow the UTF8String convention
noted in the PKIX profile [PROFILE]. noted in the PKIX profile [PROFILE].
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
the GL member's certificate. GL member's certificate.
Turner Expires July 2003 29
And Distribution
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 request and to manage a GL. The following sections describe each request and
response message combination in detail. The procedures defined in response message combination in detail. The procedures defined in
this section are not prescriptive. this section are not prescriptive.
4.1 Assign KEK To GL 4.1. Assign KEK To GL
Prior to generating a group key, a GL needs to be setup and a shared Prior to generating a group key, a GL needs to be setup and a shared
KEK assigned to the GL. Figure 3 depicts the protocol interactions KEK assigned to the GL. Figure 3 depicts the protocol interactions to
to setup and assign a shared KEK. Note that error messages are not setup and assign a shared KEK. Note that error messages are not
depicted in Figure 3. Additionally, behavior for the optional depicted in Figure 3. Additionally, behavior for the optional
transactionId, senderNonce, and recipientNonce CMC control transactionId, senderNonce, and recipientNonce CMC control attributes
attributes is not addressed in these procedures. is not addressed in these procedures.
+-----+ 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
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
should be sent to each recipient in should be sent to each recipient in recipientsNotMutuallyAware,
recipientsNotMutuallyAware, the requested algorithm to be used the requested algorithm to be used with the shared KEK in
with the shared KEK in requestedAlgorithm, the duration of the requestedAlgorithm, the duration of the shared KEK, and how
shared KEK, and how many shared KEKs should be initially many shared KEKs should be initially distributed in
distributed in generationCounter. The GLO MUST also include generationCounter. The GLO MUST also include the signingTime
the signingTime attribute with this request. attribute with this request.
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 indicates the same glName in the glAddMember request The GLO indicates the same glName in the glAddMember request
as in glUseKEK.glInfo.glName. Further glAddMember procedures as in glUseKEK.glInfo.glName. Further glAddMember procedures
are covered in section 4.3. are covered in section 4.3.
1.b - The GLO can apply confidentiality to the request by 1.b - The GLO can apply confidentiality to the request by
encapsulating the SignedData.PKIData in an EnvelopedData encapsulating the SignedData.PKIData in an EnvelopedData
(see section 3.2.1.2). (see section 3.2.1.2).
Turner Expires July 2003 30 1.c - The GLO can also optionally apply another SignedData over the
And Distribution EnvelopedData (see section 3.2.1.2).
1.c - The GLO can also optionally apply another SignedData over
the EnvelopedData (see section 3.2.1.2).
2 - Upon receipt of the request, the GLA checks the signingTime 2 - Upon receipt of the request, the GLA checks the signingTime and
and verifies the signature on the inner most verifies the signature on the inner most SignedData.PKIData. If
SignedData.PKIData. If an additional SignedData and/or an additional SignedData and/or EnvelopedData encapsulates the
EnvelopedData encapsulates the request (see sections 3.2.1.2 request (see sections 3.2.1.2 and 3.2.2), the GLA verifies the
and 3.2.2), the GLA verifies the outer signature(s) and/or outer signature(s) and/or decrypt the outer layer(s) prior to
decrypt the outer layer(s) prior to verifying the signature on verifying the signature on the inner most SignedData.
the inner most SignedData.
2.a - If the signingTime attribute value is not within the locally 2.a - If the signingTime attribute value is not within the locally
accepted time window, the GLA MAY return a response accepted time window, the GLA MAY return a response
indicating cMCStatus.failed and otherInfo.failInfo.badTime indicating cMCStatus.failed and otherInfo.failInfo.badTime
and a signingTime attribute. and a signingTime attribute.
2.b - Else if signature processing continues and if the signatures 2.b - Else if signature processing continues and if the signatures
do not verify, the GLA returns a cMCStatusInfoExt response do not verify, the GLA returns a cMCStatusInfoExt response
indicating cMCStatus.failed and indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck. Additionally, a otherInfo.failInfo.badMessageCheck. Additionally, a
signingTime attribute is included with the response. signingTime attribute is included with the response.
2.c Else if the signatures do verify but the GLA does not have a 2.c - Else if the signatures do verify but the GLA does not have a
valid certificate, the GLA returns a cMCStatusInfoExt with valid certificate, the GLA returns a cMCStatusInfoExt with
cMCStatus.failed and otherInfo.extendedFailInfo.SKDFailInfo cMCStatus.failed and otherInfo.extendedFailInfo.SKDFailInfo
value of noValidGLACertificate. Additionally, a signingTime value of noValidGLACertificate. Additionally, a signingTime
attribute is included with the response. Instead of attribute is included with the response. Instead of
immediately returning the error code, the GLA attempts to immediately returning the error code, the GLA attempts to
get a certificate, possibly using [CMC]. get a certificate, possibly using [CMC].
2.d - Else the signatures are valid and the GLA does have a valid 2.d - Else the signatures are valid and the GLA does have a valid
certificate, the GLA checks that one of the names in the certificate, the GLA checks 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.d.1 - If the names do not match, the GLA returns a response 2.d.1 - If the names do not match, the GLA returns a response
indicating cMCStatusInfoExt with cMCStatus.failed and indicating cMCStatusInfoExt with cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of otherInfo.extendedFailInfo.SKDFailInfo value of
noGLONameMatch. Additionally, a signingTime attribute is noGLONameMatch. Additionally, a signingTime attribute is
included with the response. included with the response.
2.d.2 - Else if the names all match, the GLA checks that the 2.d.2 - Else if the names all match, the GLA checks that the glName
glName and glAddress is not already in use. The GLA also and glAddress is not already in use. The GLA also checks
checks any glAddMember included within the controlSequence any glAddMember included within the controlSequence with
with this glUseKEK. Further processing of the glAddMember this glUseKEK. Further processing of the glAddMember is
is covered in section 4.3. covered in section 4.3.
2.d.2.a - If the glName is already in use the GLA returns a 2.d.2.a - If the glName is already in use the GLA returns a
response indicating cMCStatusInfoExt with response indicating cMCStatusInfoExt with
cMCStatus.failed and cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of otherInfo.extendedFailInfo.SKDFailInfo value of
Turner Expires July 2003 31
And Distribution
nameAlreadyInUse. Additionally, a signingTime attribute nameAlreadyInUse. Additionally, a signingTime attribute
is included with the response. is included with the response.
2.d.2.b - Else if the requestedAlgorithm is not supported, the GLA 2.d.2.b - Else if the requestedAlgorithm is not supported, the GLA
returns a response indicating cMCStatusInfoExt with returns a response indicating cMCStatusInfoExt with
cMCStatus.failed and cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of otherInfo.extendedFailInfo.SKDFailInfo value of
unsupportedAlgorithm. Additionally, a signingTime unsupportedAlgorithm. Additionally, a signingTime
attribute is included with the response. attribute is included with the response.
skipping to change at line 1634 skipping to change at page 35, line 8
which the GLA does not wish to disclose, the GLA returns which the GLA does not wish to disclose, the GLA returns
a response indicating cMCStatusInfoExt with a response indicating cMCStatusInfoExt with
cMCStatus.failed and cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of otherInfo.extendedFailInfo.SKDFailInfo value of
unspecified. Additionally, a signingTime attribute is unspecified. Additionally, a signingTime attribute is
included with the response. included with the response.
2.d.2.e - Else if the glName is not already in use, the duration 2.d.2.e - Else if the glName is not already in use, the duration
can be supported, and the requestedAlgorithm is can be supported, and the requestedAlgorithm is
supported, the GLA MUST return a cMCStatusInfoExt supported, the GLA MUST return a cMCStatusInfoExt
indicating cMCStatus.success and a signingTime indicating cMCStatus.success and a signingTime attribute.
attribute. (2 in Figure 3). The GLA also takes (2 in Figure 3). The GLA also takes administrative
administrative actions, which are beyond the scope of actions, which are beyond the scope of this document, to
this document, to store the glName, glAddress, store the glName, glAddress, glKeyAttributes,
glKeyAttributes, glOwnerName, and glOwnerAddress. The glOwnerName, and glOwnerAddress. The GLA also sends a
GLA also sends a glKey message as described in section glKey message as described in section 5.
5.
2.d.2.e.1 - The GLA can apply confidentiality to the response by 2.d.2.e.1 - The GLA can 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.d.2.e.2 - The GLA can also optionally apply another SignedData 2.d.2.e.2 - The GLA can 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 cMCStatusInfoExt responses, the GLO checks 3 - Upon receipt of the cMCStatusInfoExt responses, the GLO checks
the signingTime and verifies the GLA signature(s). If an the signingTime and verifies the GLA 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 verifies the response (see section 3.2.1.2 or 3.2.2), the GLO verifies the
outer signature and/or decrypt the outer layer prior to outer signature and/or decrypt the outer layer prior to
verifying the signature on the inner most SignedData. verifying the signature on the inner most SignedData.
Turner Expires July 2003 32
And Distribution
3.a - If the signingTime attribute value is not within the locally 3.a - If the signingTime attribute value is not within the locally
accepted time window, the GLO MAY return a response accepted time window, the GLO MAY return a response
indicating cMCStatus.failed and otherInfo.failInfo.badTime indicating cMCStatus.failed and otherInfo.failInfo.badTime
and a signingTime attribute. and a signingTime attribute.
3.b - Else if signature processing continues and if the signatures 3.b - Else if signature processing continues and if the signatures
do verify, the GLO MUST check that one of the names in the do verify, the GLO MUST check that one of the names in the
certificate used to sign the response matches the name of certificate used to sign the response matches the name of
the GL. the GL.
skipping to change at line 1688 skipping to change at page 36, line 12
cMCStatusInfoExt indicating cMCStatus.success, the GLO cMCStatusInfoExt indicating cMCStatus.success, the GLO
has successfully created the GL. has successfully created the GL.
3.b.2.b - Else if the signatures are valid and the response is 3.b.2.b - Else if the signatures are valid and the response is
cMCStatusInfoExt.cMCStatus.failed with any reason, the cMCStatusInfoExt.cMCStatus.failed with any reason, the
GLO can reattempt to create the GL using the information GLO can reattempt to create the GL using the information
provided in the response. The GLO can also use the provided in the response. The GLO can also use the
glaQueryRequest to determine the algorithms and other glaQueryRequest to determine the algorithms and other
characteristics supported by the GLA (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.
needed. In this case, the GLO deletes the GL. Figure 4 depicts that In this case, the GLO deletes the GL. Figure 4 depicts that protocol
protocol interactions to delete a GL. Note that behavior for the interactions to delete a GL. Note that behavior for the optional
optional transactionId, senderNonce, and recipientNonce CMC control transactionId, senderNonce, and recipientNonce CMC control attributes
attributes is not addressed in these procedures. is not addressed in these procedures.
+-----+ 1 2 +-----+ +-----+ 1 2 +-----+
| GLA | <-------> | GLO | | GLA | <-------> | GLO |
+-----+ +-----+ +-----+ +-----+
Figure 4 - Delete Group List Figure 4 - Delete Group List
The process is as follows: The process is as follows:
1 - The GLO is responsible for requesting the deletion of the GL. 1 - The GLO is responsible for requesting the deletion of the GL.
The GLO sends a SignedData.PKIData.controlSequence.glDelete The GLO sends a SignedData.PKIData.controlSequence.glDelete
request to the GLA (1 in Figure 4). The name of the GL to be request to the GLA (1 in Figure 4). The name of the GL to be
deleted is included in GeneralName. The GLO MUST also include deleted is included in GeneralName. The GLO MUST also include
the signingTime attribute and can also include a transactionId the signingTime attribute and can also include a transactionId
and senderNonce attributes. and senderNonce attributes.
Turner Expires July 2003 33
And Distribution
1.a - The GLO can optionally apply confidentiality to the request 1.a - The GLO can 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 optionally apply another SignedData over the 1.b - The GLO MAY optionally apply another SignedData over the
EnvelopedData (see section 3.2.1.2). EnvelopedData (see section 3.2.1.2).
2 - Upon receipt of the request the GLA checks the signingTime and 2 - Upon receipt of the request the GLA checks the signingTime and
verifies the signature on the inner most SignedData.PKIData. verifies the signature on the inner most SignedData.PKIData. If
If an additional SignedData and/or EnvelopedData encapsulates an additional SignedData and/or EnvelopedData encapsulates the
the request (see section 3.2.1.2 or 3.2.2), the GLA verifies request (see section 3.2.1.2 or 3.2.2), the GLA verifies the
the outer signature and/or decrypt the outer layer prior to outer signature and/or decrypt the outer layer prior to
verifying the signature on the inner most SignedData. verifying the signature on the inner most SignedData.
2.a - If the signingTime attribute value is not within the locally 2.a - If the signingTime attribute value is not within the locally
accepted time window, the GLA MAY return a response accepted time window, the GLA MAY return a response
indicating cMCStatus.failed and otherInfo.failInfo.badTime indicating cMCStatus.failed and otherInfo.failInfo.badTime
and a signingTime attribute. and a signingTime attribute.
2.b - Else if signature processing continues and if the signatures 2.b - Else if signature processing continues and if the signatures
cannot be verified, the GLA returns a cMCStatusInfoExt cannot be verified, the GLA returns a cMCStatusInfoExt
response indicating cMCStatus.failed and response indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck. Additionally, a otherInfo.failInfo.badMessageCheck. Additionally, a
signingTime attribute is included with the response. signingTime attribute is included with the response.
2.c - Else if the signatures verify, the GLA makes sure the GL is 2.c - Else if the signatures verify, the GLA makes sure the GL is
supported by checking the name of the GL matches a glName supported by checking the name of the GL matches a glName
stored on the GLA. stored on the GLA.
2.c.1 - If the glName is not supported by the GLA, the GLA returns 2.c.1 - If the glName is not supported by the GLA, the GLA returns
a response indicating cMCStatusInfoExt with a response indicating cMCStatusInfoExt with
cMCStatus.failed and cMCStatus.failed and otherInfo.extendedFailInfo.SKDFailInfo
otherInfo.extendedFailInfo.SKDFailInfo value of value of invalidGLName. Additionally, a signingTime
invalidGLName. Additionally, a signingTime attribute is attribute is included with the response.
included with the response.
2.c.2 - Else if the glName is supported by the GLA, the GLA 2.c.2 - Else if the glName is supported by the GLA, the GLA ensures
ensures a registered GLO signed the glDelete request by a registered GLO signed the glDelete request by checking if
checking if one of the names present in the digital one of the names present in the digital signature
signature certificate used to sign the glDelete request certificate used to sign the glDelete request matches a
matches a registered GLO. registered GLO.
2.c.2.a - If the names do not match, the GLA returns a response 2.c.2.a - If the names do not match, the GLA returns a response
indicating cMCStatusInfoExt with cMCStatus.failed and indicating cMCStatusInfoExt with cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of otherInfo.extendedFailInfo.SKDFailInfo value of
noGLONameMatch. Additionally, a signingTime attribute is noGLONameMatch. Additionally, a signingTime attribute is
included with the response. included with the response.
2.c.2.b - Else if the names do match, but the GL cannot be deleted 2.c.2.b - Else if the names do match, but the GL cannot be deleted
for other reasons, which the GLA does not wish to for other reasons, which the GLA does not wish to
disclose, the GLA returns a response indicating disclose, the GLA returns a response indicating
Turner Expires July 2003 34
And Distribution
cMCStatusInfoExt with cMCStatus.failed and cMCStatusInfoExt with cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of otherInfo.extendedFailInfo.SKDFailInfo value of
unspecified. Additionally, a signingTime attribute is unspecified. Additionally, a signingTime attribute is
included with the response. Actions beyond the scope of included with the response. Actions beyond the scope of
this document must then be taken to delete the GL from this document must then be taken to delete the GL from
the GLA. the GLA.
2.c.2.c - Else if the names do match, the GLA returns a 2.c.2.c - Else if the names do match, the GLA returns a
cMCStatusInfoExt indicating cMCStatus.success and a cMCStatusInfoExt indicating cMCStatus.success and a
signingTime attribute (2 in Figure 4). The GLA ought not signingTime attribute (2 in Figure 4). The GLA ought not
skipping to change at line 1807 skipping to change at page 38, line 30
3.a - If the signingTime attribute value is not within the locally 3.a - If the signingTime attribute value is not within the locally
accepted time window, the GLO MAY return a response accepted time window, the GLO MAY return a response
indicating cMCStatus.failed and otherInfo.failInfo.badTime indicating cMCStatus.failed and otherInfo.failInfo.badTime
and a signingTime attribute. and a signingTime attribute.
3.b - Else if signature processing continues and if the signatures 3.b - Else if signature processing continues and if the signatures
verify, the GLO checks that one of the names in the verify, the GLO checks that one of the names in the
certificate used to sign the response matches the name of certificate used to sign the response matches the name of
the GL. the GL.
3.b.1 If the name of the GL does not match the name present in 3.b.1 - If the name of the GL does not match the name present in
the certificate used to sign the message, the GLO should the certificate used to sign the message, the GLO should
not believe the response. not believe the response.
3.b.2 Else if the name of the GL does match the name present in 3.b.2 - Else if the name of the GL does match the name present in
the certificate and: the certificate and:
3.b.2.a - If the signatures verify and the response was 3.b.2.a - If the signatures verify and the response was
cMCStatusInfoExt indicating cMCStatus.success, the GLO cMCStatusInfoExt indicating cMCStatus.success, the GLO
has successfully deleted the GL. has successfully deleted the GL.
3.b.2.b - Else if the signatures do verify and the response was 3.b.2.b - Else if the signatures do verify and the response was
cMCStatusInfoExt.cMCStatus.failed with any reason, the cMCStatusInfoExt.cMCStatus.failed with any reason, the
Turner Expires July 2003 35
And Distribution
GLO can reattempt to delete the GL using the information GLO can reattempt to delete the GL using the information
provided in the response. 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
the prospective members to the GLO for review. Where there are prospective members to the GLO for review. Where there are multiple
multiple GLOs for a GL, which GLO the request is forwarded to is GLOs for a GL, which GLO the request is forwarded to is beyond the
beyond the scope of this document. The GLO reviews the request and scope of this document. The GLO reviews the request and either
either rejects it or submits a reformed request to the GLA. In the rejects it or submits a reformed request to the GLA. In the closed
closed case, the GLA will not accept requests from prospective case, the GLA will not accept requests from prospective members. The
members. The following sections describe the processing for the following sections describe the processing for the GLO(s), GLA, and
GLO(s), GLA, and prospective GL members depending on where the prospective GL members depending on where the glAddMeber request
glAddMeber request originated, either from a GLO or from prospective originated, either from a GLO or from prospective members. Figure 5
members. Figure 5 depicts the protocol interactions for the three depicts the protocol interactions for the three options. Note that
options. Note that the error messages are not depicted. the error messages are not depicted. Additionally, note that behavior
Additionally, note that behavior for the optional transactionId, for the optional transactionId, senderNonce, and recipientNonce CMC
senderNonce, and recipientNonce CMC control attributes is not control attributes is not addressed in these procedures.
addressed in these procedures.
+-----+ 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 |
+----------+ +----------+
Figure 5 - Member Addition Figure 5 - Member Addition
An important decision that needs to be made on a group by group An important decision that needs to be made on a group by group basis
basis is whether to rekey the group every time a new member is is whether to rekey the group every time a new member is added.
added. Typically, unmanaged GLs should not be rekeyed when a new Typically, unmanaged GLs should not be rekeyed when a new member is
member is added, as the overhead associated with rekeying the group added, as the overhead associated with rekeying the group becomes
becomes prohibitive, as the group becomes large. However, managed prohibitive, as the group becomes large. However, managed and closed
and closed GLs can be rekeyed to maintain the confidentiality of the GLs can be rekeyed to maintain the confidentiality of the traffic
traffic sent by group members. An option to rekeying managed or sent by group members. An option to rekeying managed or closed GLs
closed GLs when a member is added is to generate a new GL with a when a member is added is to generate a new GL with a different group
key. Group rekeying is discussed in sections 4.5 and 5.
Turner Expires July 2003 36
And Distribution
different group key. Group rekeying is discussed in sections 4.5 and
5.
4.3.1 GLO Initiated Additions 4.3.1. GLO Initiated Additions
The process for GLO initiated glAddMember requests is as follows: The process for GLO initiated glAddMember 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
to be added (this may be done through an out of bands means). be added (this may be done through an out of bands means). The
The GLO then sends a SignedData.PKIData.controlSequence with a GLO then sends a SignedData.PKIData.controlSequence with a
separate glAddMember request for each member to the GLA (1 in separate glAddMember request for each member to the GLA (1 in
Figure 5). The GLO includes: the GL name in glName, the Figure 5). The GLO includes: 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
in glMember.glMemberAddress, and the member's encryption glMember.glMemberAddress, and the member's encryption
certificate in glMember.certificates.pKC. The GLO can also certificate in glMember.certificates.pKC. The GLO can also
include any attribute certificates associated with the include any attribute certificates associated with the member's
member's encryption certificate in glMember.certificates.aC, encryption certificate in glMember.certificates.aC, and the
and the certification path associated with the member's certification path associated with the member's encryption and
encryption and attribute certificates in attribute certificates in glMember.certificates.certPath. The
glMember.certificates.certPath. The GLO MUST also include the GLO MUST also include the signingTime attribute with this
signingTime attribute with this request. request.
1.a - The GLO can optionally apply confidentiality to the request 1.a - The GLO can 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 can also optionally apply another SignedData over 1.b - The GLO can also optionally apply another SignedData over the
the EnvelopedData (see section 3.2.1.2). EnvelopedData (see section 3.2.1.2).
2 - Upon receipt of the request, the GLA checks the signingTime 2 - Upon receipt of the request, the GLA checks the signingTime and
and verifies the signature on the inner most verifies the signature on the inner most SignedData.PKIData. If
SignedData.PKIData. If an additional SignedData and/or an additional SignedData and/or EnvelopedData encapsulates the
EnvelopedData encapsulates the request (see section 3.2.1.2 or request (see section 3.2.1.2 or 3.2.2), the GLA verifies the
3.2.2), the GLA verifies the outer signature and/or decrypt outer signature and/or decrypt the outer layer prior to
the outer layer prior to verifying the signature on the inner verifying the signature on the inner most SignedData.
most SignedData.
2.a - If the signingTime attribute value is not within the locally 2.a - If the signingTime attribute value is not within the locally
accepted time window, the GLA MAY return a response accepted time window, the GLA MAY return a response
indicating cMCStatus.failed and otherInfo.failInfo.badTime indicating cMCStatus.failed and otherInfo.failInfo.badTime
and a signingTime attribute. and a signingTime attribute.
2.b - Else if signature processing continues and if the signatures 2.b - Else if signature processing continues and if the signatures
cannot be verified, the GLA returns a cMCStatusInfoExt cannot be verified, the GLA returns a cMCStatusInfoExt
response indicating cMCStatus.failed and response indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck. Additionally, a otherInfo.failInfo.badMessageCheck. Additionally, a
signingTime attribute is included with the response. signingTime attribute is included with the response.
2.c - Else if the signatures verify, the glAddMember request is 2.c - Else if the signatures 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
Turner Expires July 2003 37
And Distribution
completed the GLA returns a cMCStatusInfoExt indicating completed the GLA returns a cMCStatusInfoExt indicating
cMCStatus.success and a signingTime attribute (2 in Figure cMCStatus.success and a signingTime attribute (2 in Figure
5). 5).
2.c.1 - The GLA can apply confidentiality to the response by 2.c.1 - The GLA can apply confidentiality to the response by
encapsulating the SignedData.PKIData in an EnvelopedData encapsulating the SignedData.PKIData in an EnvelopedData if
if the request was encapsulated in an EnvelopedData (see the request was encapsulated in an EnvelopedData (see
section 3.2.1.2). section 3.2.1.2).
2.c.2 - The GLA can also optionally apply another SignedData over 2.c.2 - The GLA can also optionally apply another SignedData over
the EnvelopedData (see section 3.2.1.2). the EnvelopedData (see section 3.2.1.2).
2.d - Else if the signatures verify and the GLAddMember request is 2.d - Else if the signatures 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 makes sure the GL is supported by checking that the the GLA makes sure the GL is supported by checking that the
glName matches a glName stored on the GLA. glName matches a glName stored on the GLA.
2.d.1 - If the glName is not supported by the GLA, the GLA returns 2.d.1 - If the glName is not supported by the GLA, the GLA returns
a response indicating cMCStatusInfoExt with a response indicating cMCStatusInfoExt with
cMCStatus.failed and cMCStatus.failed and otherInfo.extendedFailInfo.SKDFailInfo
otherInfo.extendedFailInfo.SKDFailInfo value of value of invalidGLName. Additionally, a signingTime
invalidGLName. Additionally, a signingTime attribute is attribute is included with the response.
included with the response.
2.d.2 - Else if the glName is supported by the GLA, the GLA checks 2.d.2 - Else if the glName is supported by the GLA, the GLA checks
to see if the glMemberName is present on the GL. to see if the glMemberName is present on the GL.
2.d.2.a - If the glMemberName is present on the GL, the GLA 2.d.2.a - If the glMemberName is present on the GL, the GLA returns
returns a response indicating cMCStatusInfoExt with a response indicating cMCStatusInfoExt with
cMCStatus.failed and cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of otherInfo.extendedFailInfo.SKDFailInfo value of
alreadyAMember. Additionally, a signingTime attribute is alreadyAMember. Additionally, a signingTime attribute is
included with the response. included with the response.
2.d.2.b - Else if the glMemberName is not present on the GL, the 2.d.2.b - Else if the glMemberName is not present on the GL, the
GLA checks how the GL is administered. GLA checks how the GL is administered.
2.d.2.b.1 - If the GL is closed, the GLA checks that a registered 2.d.2.b.1 - If the GL is closed, the GLA checks that a registered
GLO signed the request by checking that one of the GLO signed the request by checking that one of the
names in the digital signature certificate used to names in the digital signature certificate used to
sign the request matches a registered GLO. sign the request matches a registered GLO.
2.d.2.b.1.a - If the names do not match, the GLA returns a 2.d.2.b.1.a - If the names do not match, the GLA returns a response
response indicating cMCStatusInfoExt with indicating cMCStatusInfoExt with cMCStatus.failed and
cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of otherInfo.extendedFailInfo.SKDFailInfo value of
noGLONameMatch. Additionally, a signingTime noGLONameMatch. Additionally, a signingTime attribute
attribute is included with the response. is included with the response.
2.d.2.b.1.b - Else if the names match, the GLA verifies the 2.d.2.b.1.b - Else if the names match, the GLA verifies the
member's encryption certificate. member's encryption certificate.
Turner Expires July 2003 38
And Distribution
2.d.2.b.1.b.1 - If the member's encryption certificate cannot be 2.d.2.b.1.b.1 - If the member's encryption certificate cannot be
verified, the GLA can return a response indicating verified, the GLA can return a response indicating
cMCStatusInfoExt with cMCStatus.failed and cMCStatusInfoExt with cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of otherInfo.extendedFailInfo.SKDFailInfo value of
invalidCert to the GLO. Additionally, a invalidCert to the GLO. Additionally, a
signingTime attribute is included with the signingTime attribute is included with the
response. If the GLA does not return a response. If the GLA does not return a
cMCStatusInfoExt.cMCStatus.failed response, the cMCStatusInfoExt.cMCStatus.failed response, the
GLA issues a glProvideCert request (see section GLA issues a glProvideCert request (see section
4.10). 4.10).
skipping to change at line 2019 skipping to change at page 42, line 38
2.d.2.b.1.b.2.a - The GLA applies confidentiality to the response 2.d.2.b.1.b.2.a - The GLA applies 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.d.2.b.1.b.2.b - The GLA can also optionally apply another 2.d.2.b.1.b.2.b - The GLA can 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.d.2.b.2 - Else if the GL is managed, the GLA checks that either 2.d.2.b.2 - Else if the GL is managed, the GLA checks that either a
a registered GLO or the prospective member signed the 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 needs to match a registered used to sign the request needs to match a registered
GLO. For the prospective member, the name in GLO. For the prospective member, the name in
glMember.glMemberName needs to match one of the names glMember.glMemberName needs to match one of the names
in the certificate used to sign the request. in the certificate used to sign the request.
2.d.2.b.2.a - If the signer is neither a registered GLO nor the 2.d.2.b.2.a - If the signer is neither a registered GLO nor the
prospective GL member, the GLA returns a response prospective GL member, the GLA returns a response
indicating cMCStatusInfoExt with cMCStatus.failed indicating cMCStatusInfoExt with cMCStatus.failed and
and otherInfo.extendedFailInfo.SKDFailInfo value of otherInfo.extendedFailInfo.SKDFailInfo value of
noSpam. Additionally, a signingTime attribute is noSpam. Additionally, a signingTime attribute is
included with the response. included with the response.
2.d.2.b.2.b - Else if the signer is a registered GLO, the GLA 2.d.2.b.2.b - Else if the signer is a registered GLO, the GLA
verifies the member's encryption certificate. verifies the member's encryption certificate.
2.d.2.b.2.b.1 - If the member's certificate cannot be verified, 2.d.2.b.2.b.1 - If the member's certificate cannot be verified, the
the GLA can return a response indicating GLA can return a response indicating
cMCStatusInfoExt with cMCStatus.failed and cMCStatusInfoExt with cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of otherInfo.extendedFailInfo.SKDFailInfo value of
Turner Expires July 2003 39
And Distribution
invalidCert. Additionally, a signingTime attribute invalidCert. Additionally, a signingTime attribute
is included with the response. If the GLA does not is included with the response. If the GLA does not
return a cMCStatus.failed response, the GLA MUST return a cMCStatus.failed response, the GLA MUST
issue a glProvideCert request (see section 4.10). issue a glProvideCert request (see section 4.10).
2.d.2.b.2.b.2 - Else if the member's certificate verifies, the GLA 2.d.2.b.2.b.2 - Else if the member's certificate verifies, the GLA
MUST return a cMCStatusInfoExt indicating MUST return a cMCStatusInfoExt indicating
cMCStatus.success and a signingTime attribute to cMCStatus.success and a signingTime attribute to
the GLO (2 in Figure 5). The GLA also takes the GLO (2 in Figure 5). The GLA also takes
administrative actions, which are beyond the scope administrative actions, which are beyond the scope
skipping to change at line 2071 skipping to change at page 43, line 38
2.d.2.b.2.b.2.a - The GLA applies confidentiality to the response 2.d.2.b.2.b.2.a - The GLA applies 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.d.2.b.2.b.2.b - The GLA can also optionally apply another 2.d.2.b.2.b.2.b - The GLA can 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.d.2.b.2.c - Else if the signer is the prospective member, the 2.d.2.b.2.c - Else if the signer is the prospective member, the GLA
GLA forwards the glAddMember request (see section forwards 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.
2.d.2.b.2.c.1 - The GLA applies confidentiality to the forwarded 2.d.2.b.2.c.1 - The GLA applies confidentiality to the forwarded
request by encapsulating the SignedData.PKIData in request by encapsulating the SignedData.PKIData in
an EnvelopedData if the original request was an EnvelopedData if the original request was
encapsulated in an EnvelopedData (see section encapsulated in an EnvelopedData (see section
3.2.1.2). 3.2.1.2).
2.d.2.b.2.c.2 - The GLA can also optionally apply another 2.d.2.b.2.c.2 - The GLA can 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.d.2.b.3 - Else if the GL is unmanaged, the GLA checks that 2.d.2.b.3 - Else if the GL is unmanaged, the GLA checks that either
either a registered GLO or the prospective member a registered GLO or the prospective member signed the
signed the request. For GLOs, one of the names in the request. For GLOs, one of the names in the certificate
certificate used to sign the request needs tp match used to sign the request needs tp match the name of a
the name of a registered GLO. For the prospective registered GLO. For the prospective member, the name
member, the name in glMember.glMemberName needs to in glMember.glMemberName needs to match one of the
names in the certificate used to sign the request.
Turner Expires July 2003 40
And Distribution
match one of the names in the certificate used to sign
the request.
2.d.2.b.3.a - If the signer is neither a registered GLO nor the 2.d.2.b.3.a - If the signer is neither a registered GLO nor the
prospective member, the GLA returns a response prospective member, the GLA returns a response
indicating cMCStatusInfoExt with cMCStatus.failed indicating cMCStatusInfoExt with cMCStatus.failed and
and otherInfo.extendedFailInfo.SKDFailInfo value of otherInfo.extendedFailInfo.SKDFailInfo value of
noSpam. Additionally, a signingTime attribute is noSpam. Additionally, a signingTime attribute is
included with the response. included with the response.
2.d.2.b.3.b - Else if the signer is either a registered GLO or the 2.d.2.b.3.b - Else if the signer is either a registered GLO or the
prospective member, the GLA verifies the member's prospective member, the GLA verifies the member's
encryption certificate. encryption certificate.
2.d.2.b.3.b.1 - If the member's certificate cannot be verified, 2.d.2.b.3.b.1 - If the member's certificate cannot be verified, the
the GLA can return a response indicating GLA can return a response indicating
cMCStatusInfoExt with cMCStatus.failed and cMCStatusInfoExt with cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of otherInfo.extendedFailInfo.SKDFailInfo value of
invalidCert and a signingTime attribute to either invalidCert and a signingTime attribute to either
the GLO or the prospective member depending on the GLO or the prospective member depending on
where the request originated. If the GLA does not where the request originated. If the GLA does not
return a cMCStatus.failed response, the GLA issues return a cMCStatus.failed response, the GLA issues
a glProvideCert request (see section 4.10) to a glProvideCert request (see section 4.10) to
either the GLO or prospective member depending on either the GLO or prospective member depending on
where the request originated. where the request originated.
skipping to change at line 2151 skipping to change at page 45, line 18
an EnvelopedData (see section 3.2.1.2). an EnvelopedData (see section 3.2.1.2).
2.d.2.b.3.b.2.b - The GLA can also optionally apply another 2.d.2.b.3.b.2.b - The GLA can 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 cMCStatusInfoExt response, the GLO checks 3 - Upon receipt of the cMCStatusInfoExt response, the GLO checks
the signingTime and verifies the GLA signature(s). If an the signingTime and verifies the GLA 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 verifies the response (see section 3.2.1.2 or 3.2.2), the GLO verifies the
Turner Expires July 2003 41
And Distribution
outer signature and/or decrypt the outer layer prior to outer signature and/or decrypt the outer layer prior to
verifying the signature on the inner most SignedData. verifying the signature on the inner most SignedData.
3.a - If the signingTime attribute value is not within the locally 3.a - If the signingTime attribute value is not within the locally
accepted time window, the GLO MAY return a response accepted time window, the GLO MAY return a response
indicating cMCStatus.failed and otherInfo.failInfo.badTime indicating cMCStatus.failed and otherInfo.failInfo.badTime
and a signingTime attribute. and a signingTime attribute.
3.b - Else if signature processing continues and if the signatures 3.b - Else if signature processing continues and if the signatures
verify, the GLO checks that one of the names in the verify, the GLO checks that one of the names in the
certificate used to sign the response matches the name of certificate used to sign the response matches the name of
the GL. the GL.
3.b.1 If the name of the GL does not match the name present in 3.b.1 - If the name of the GL does not match the name present in
the certificate used to sign the message, the GLO should the certificate used to sign the message, the GLO should
not believe the response. not believe the response.
3.b.2 Else if the name of the GL matches the name present in the 3.b.2 - Else if the name of the GL matches the name present in the
certificate and: certificate and:
3.b.2.a - If the signatures verify and the response is 3.b.2.a - If the signatures verify and the response is
cMCStatusInfoExt indicating cMCStatus.success, the GLA cMCStatusInfoExt indicating cMCStatus.success, the GLA
has added the member to the GL. If member was added to a has added the member to the GL. If member was added to a
managed list and the original request was signed by the managed list and the original request was signed by the
member, the GLO sends a member, the GLO sends a
cMCStatusInfoExt.cMCStatus.success and a signingTime cMCStatusInfoExt.cMCStatus.success and a signingTime
attribute to the GL member. attribute to the GL member.
3.b.2.b - Else if the GLO received a 3.b.2.b - Else if the GLO received a
cMCStatusInfoExt.cMCStatus.failed with any reason, the cMCStatusInfoExt.cMCStatus.failed with any reason, the
GLO can reattempt to add the member to the GL using the GLO can reattempt to add the member to the GL using the
information provided in the response. information provided in the response.
4 - Upon receipt of the cMCStatusInfoExt response, the prospective 4 - Upon receipt of the cMCStatusInfoExt response, the prospective
member checks the signingTime and verifies the GLA signatures member checks the signingTime and verifies the GLA signatures
or GLO signatures. If an additional SignedData and/or or GLO signatures. 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
or 3.2.2), the GLO verifies the outer signature and/or decrypt 3.2.2), the GLO verifies the outer signature and/or decrypt the
the outer layer prior to verifying the signature on the inner outer layer prior to verifying the signature on the inner most
most SignedData. SignedData.
4.a - If the signingTime attribute value is not within the locally 4.a - If the signingTime attribute value is not within the locally
accepted time window, the prospective member MAY return a accepted time window, the prospective member MAY return a
response indicating cMCStatus.failed and response indicating cMCStatus.failed and
otherInfo.failInfo.badTime and a signingTime attribute. otherInfo.failInfo.badTime and a signingTime attribute.
4.b - Else if signature processing continues and if the signatures 4.b - Else if signature processing continues and if the signatures
verify, the GL member checks that one of the names in the verify, the GL member checks that one of the names in the
certificate used to sign the response matches the name of certificate used to sign the response matches the name of
the GL. the GL.
Turner Expires July 2003 42
And Distribution
4.b.1 - If the name of the GL does not match the name present in 4.b.1 - If the name of the GL does not match the name present in
the certificate used to sign the message, the GL member the certificate used to sign the message, the GL member
should not believe the response. should not believe the response.
4.b.2 Else if the name of the GL matches the name present in the 4.b.2 - Else if the name of the GL matches the name present in the
certificate and: certificate and:
4.b.2.a - If the signatures verify, the prospective member has 4.b.2.a - If the signatures verify, the prospective member has been
been added to the GL. added to the GL.
4.b.2.b - Else if the prospective member received a 4.b.2.b - Else if the prospective member received a
cMCStatusInfoExt.cMCStatus.failed, for any reason, the cMCStatusInfoExt.cMCStatus.failed, for any reason, the
prospective member MAY reattempt to add themselves to prospective member MAY reattempt to add themselves to the
the GL using the information provided in the response. GL using the information provided in the response.
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 includes: the GLA (A in Figure 5). The prospective GL member includes: the GL
GL name in glName, their name in glMember.glMemberName, their name in glName, their name in glMember.glMemberName, their
address in glMember.glMemberAddress, and their encryption address in glMember.glMemberAddress, and their encryption
certificate in glMember.certificates.pKC. The prospective GL certificate in glMember.certificates.pKC. The prospective GL
member can also include any attribute certificates associated member can also include any attribute certificates associated
with their encryption certificate in glMember.certificates.aC, with their encryption certificate in glMember.certificates.aC,
and the certification path associated with their encryption and the certification path associated with their encryption and
and attribute certificates in glMember.certificates.certPath. attribute certificates in glMember.certificates.certPath. The
The prosepective member MUST also include the signingTime prosepective member MUST also include the signingTime attribute
attribute with this request. with this request.
1.a - The prospective GL member can optionally apply 1.a - The prospective GL member can optionally apply
confidentiality to the request by encapsulating the confidentiality to the request by encapsulating the
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 prospective GL member MAY optionally apply another 1.b - The prospective GL member MAY optionally apply another
SignedData over the EnvelopedData (see section 3.2.1.2). SignedData over the EnvelopedData (see section 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.3.1. per 2 in section 4.3.1.
3 - Upon receipt of the forwarded request, the GLO checks the 3 - Upon receipt of the forwarded request, the GLO checks the
signingTime and verifies the prospective GL member signature signingTime and verifies the prospective GL member signature on
on the inner most SignedData.PKIData and the GLA signature on the inner most SignedData.PKIData and the GLA signature on the
the outer layer. If an EnvelopedData encapsulates the inner outer layer. If an EnvelopedData encapsulates the inner most
most layer (see section 3.2.1.2 or 3.2.2), the GLO decrypts layer (see section 3.2.1.2 or 3.2.2), the GLO decrypts the
the outer layer prior to verifying the signature on the inner outer layer prior to verifying the signature on the inner most
most SignedData. SignedData.
Turner Expires July 2003 43
And Distribution
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 signingTime attribute value is not within the locally 3.a - If the signingTime attribute value is not within the locally
accepted time window, the GLO MAY return a response accepted time window, the GLO MAY return a response
indicating cMCStatus.failed and otherInfo.failInfo.badTime. indicating cMCStatus.failed and otherInfo.failInfo.badTime.
skipping to change at line 2287 skipping to change at page 47, line 50
3.b.1 - If the names do not match, the GLO sends a 3.b.1 - If the names do not match, the GLO sends a
SignedData.PKIResponse.controlSequence message back to the SignedData.PKIResponse.controlSequence message back to the
prospective member with cMCStatusInfoExt.cMCStatus.failed prospective member with cMCStatusInfoExt.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. Additionally, a people to GLs without their permission. Additionally, a
signingTime attribute is included with the response. signingTime attribute is included with the response.
3.b.2 - Else if the names match, the GLO determines whether the 3.b.2 - Else if the names 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
is beyond the scope of this document; however, the GLO beyond the scope of this document; however, the GLO should
should check to see that the glMember.glMemberName is not check to see that the glMember.glMemberName is not already
already on the GL. on the GL.
3.b.2.a - If the GLO determines the prospective member is not 3.b.2.a - If the GLO determines the prospective member is not
allowed to join the GL, the GLO can return a allowed to join the GL, the GLO can return a
SignedData.PKIResponse.controlSequence message back to SignedData.PKIResponse.controlSequence message back to
the prospective member with the prospective member with
cMCStatusInfoExt.cMCtatus.failed indicating why the cMCStatusInfoExt.cMCtatus.failed indicating why the
prospective member was denied in cMCStatus.statusString. prospective member was denied in cMCStatus.statusString.
Additionally, a signingTime attribute is included with Additionally, a signingTime attribute is included with
the response. the response.
3.b.2.b - Else if GLO determines the prospective member is allowed 3.b.2.b - Else if GLO determines the prospective member is allowed
to join the GL, the GLO verifies the member's encryption to join the GL, the GLO verifies the member's encryption
certificate. certificate.
3.b.2.b.1 - If the member's certificate cannot be verified, the 3.b.2.b.1 - If the member's certificate cannot be verified, the GLO
GLO returns a SignedData.PKIResponse.controlSequence returns a SignedData.PKIResponse.controlSequence back
back to the prospective member with to the prospective member with
cMCStatusInfoExt.cMCtatus.failed indicating that the cMCStatusInfoExt.cMCtatus.failed indicating that the
member's encryption certificate did not verify in member's encryption certificate did not verify in
cMCStatus.statusString. Additionally, a signingTime cMCStatus.statusString. Additionally, a signingTime
attribute is included with the response. If the GLO attribute is included with the response. If the GLO
does not return a cMCStatusInfoExt response, the GLO does not return a cMCStatusInfoExt response, the GLO
sends a sends a
SignedData.PKIData.controlSequence.glProvideCert SignedData.PKIData.controlSequence.glProvideCert
Turner Expires July 2003 44
And Distribution
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 if the member's certificate verifies, the GLO 3.b.2.b.2 - Else if the member's certificate verifies, 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 applies confidentiality to the new 3.b.2.b.2.a - The GLO applies 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 initial
initial request was encapsulated in an EnvelopedData request was encapsulated in an EnvelopedData (see
(see section 3.2.1.2). section 3.2.1.2).
3.b.2.b.2.b - The GLO can also optionally apply another SignedData 3.b.2.b.2.b - The GLO can 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.
4.4 Delete Members From GL 4.4. Delete Members From GL
To delete members from GLs, either the GLO or members to be removed To delete members from GLs, either the GLO or members to be removed
use the glDeleteMember request. The GLA processes GLO and members use the glDeleteMember request. The GLA processes GLO and members
requesting their own removal make requests differently. The GLO can requesting their own removal make requests differently. The GLO can
submit the request at any time to delete members from the GL, and submit the request at any time to delete members from the GL, and the
the GLA, once it has verified the request came from a registered GLA, once it has verified the request came from a registered GLO,
GLO, should delete the member. If a member sends the request, the should delete the member. If a member sends the request, the GLA
GLA needs to determine how the GL is administered. When the GLO needs to determine how the GL is administered. When the GLO initially
initially configured the GL, they set the GL to be unmanaged, configured the GL, they set the GL to be unmanaged, managed, or
managed, or closed (see section 3.1.1). In the unmanaged case, the closed (see section 3.1.1). In the unmanaged case, the GLA merely
GLA merely processes the member's request. For the managed case, the processes the member's request. For the managed case, the GLA
GLA forwards the requests from the member to the GLO for review. forwards the requests from the member to the GLO for review. Where
Where there are multiple GLOs for a GL, which GLO the request is there are multiple GLOs for a GL, which GLO the request is forwarded
forwarded to is beyond the scope of this document. The GLO reviews to is beyond the scope of this document. The GLO reviews the request
the request and either rejects it or submits a reformed request to and either rejects it or submits a reformed request to the GLA. In
the GLA. In the closed case, the GLA will not accept requests from the closed case, the GLA will not accept requests from members. The
members. The following sections describe the processing for the following sections describe the processing for the GLO(s), GLA, and
GLO(s), GLA, and GL members depending on where the request GL members depending on where the request originated, either from a
originated, either from a GLO or from members wanting to be removed. GLO or from members wanting to be removed. Figure 6 depicts the
Figure 6 depicts the protocol interactions for the three options. protocol interactions for the three options. Note that the error
Note that the error messages are not depicted. Additionally, messages are not depicted. Additionally, behavior for the optional
behavior for the optional transactionId, senderNonce, and transactionId, senderNonce, and recipientNonce CMC control attributes
recipientNonce CMC control attributes is not addressed in these is not addressed in these procedures.
procedures.
Turner Expires July 2003 45
And Distribution
+-----+ 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 |
+----------+ +----------+
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
and will continue to receive rekeys. For unmanaged lists, there is will continue to receive rekeys. For unmanaged lists, there is no
no point to a group rekey because there is no guarantee that the point to a group rekey because there is no guarantee that the member
member requesting to be removed has not already added themselves requesting to be removed has not already added themselves back on the
back on the GL under a different name. For managed and closed GLs, GL under a different name. For managed and closed GLs, the GLO needs
the GLO needs to take steps to ensure the member being deleted is to take steps to ensure the member being deleted is not on the GL
not on the GL twice. After ensuring this, managed and closed GLs can twice. After ensuring this, managed and closed GLs can be rekeyed to
be rekeyed to maintain the confidentiality of the traffic sent by maintain the confidentiality of the traffic sent by group members. If
group members. If the GLO is sure the member has been deleted the the GLO is sure the member has been deleted the group rekey mechanism
group rekey mechanism can be used to distribute the new key (see can be used to distribute the new key (see sections 4.5 and 5).
sections 4.5 and 5).
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
to be deleted (this can be done through an out of bands be deleted (this can be done through an out of bands means).
means). The GLO then sends a The GLO then sends a SignedData.PKIData.controlSequence with a
SignedData.PKIData.controlSequence with a separate separate glDeleteMember request for each member to the GLA (1
glDeleteMember request for each member to the GLA (1 in Figure in Figure 6). The GLO MUST include: the GL name in glName and
6). The GLO MUST include: the GL name in glName and the the member's name in glMemberToDelete. If the GL from which the
member's name in glMemberToDelete. If the GL from which the member is being deleted in a closed or managed GL, the GLO MUST
member is being deleted in a closed or managed GL, the GLO also generate a glRekey request and include it with the
MUST also generate a glRekey request and include it with the
glDeletemember request (see section 4.5). The GLO MUST also glDeletemember request (see section 4.5). The GLO MUST also
include the signingTime attribute with this request. include the signingTime attribute with this request.
1.a - The GLO can optionally apply confidentiality to the request 1.a - The GLO can 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 can also optionally apply another SignedData over 1.b - The GLO can also optionally apply another SignedData over the
the EnvelopedData (see section 3.2.1.2). EnvelopedData (see section 3.2.1.2).
Turner Expires July 2003 46
And Distribution
2 - Upon receipt of the request, the GLA checks the signingTime 2 - Upon receipt of the request, the GLA checks the signingTime
attribute and verifies the signature on the inner most attribute and verifies the signature on the inner most
SignedData.PKIData. If an additional SignedData and/or SignedData.PKIData. 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 verifies the outer signature and/or decrypt 3.2.2), the GLA verifies the outer signature and/or decrypt the
the outer layer prior to verifying the signature on the inner outer layer prior to verifying the signature on the inner most
most SignedData. SignedData.
2.a - If the signingTime attribute value is not within the locally 2.a - If the signingTime attribute value is not within the locally
accepted time window, the GLA MAY return a response accepted time window, the GLA MAY return a response
indicating cMCStatus.failed and otherInfo.failInfo.badTime indicating cMCStatus.failed and otherInfo.failInfo.badTime
and a signingTime attribute. and a signingTime attribute.
2.b - Else if signature processing continues and if the signatures 2.b - Else if signature processing continues and if the signatures
cannot be verified, the GLA returns a cMCStatusInfoExt cannot be verified, the GLA returns a cMCStatusInfoExt
response indicating cMCStatus.failed and response indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck. Additionally, a otherInfo.failInfo.badMessageCheck. Additionally, a
signingTime attribute is included with the response. signingTime attribute is included with the response.
2.c - Else if the signatures verify, the GLA makes sure the GL is 2.c - Else if the signatures verify, the GLA makes sure the GL is
supported by the GLA by checking that the glName matches a supported by the GLA by checking that the glName matches a
glName stored on the GLA. glName stored on the GLA.
2.c.1 - If the glName is not supported by the GLA, the GLA returns 2.c.1 - If the glName is not supported by the GLA, the GLA returns
a response indicating cMCStatusInfoExt with a response indicating cMCStatusInfoExt with
cMCStatus.failed and cMCStatus.failed and otherInfo.extendedFailInfo.SKDFailInfo
otherInfo.extendedFailInfo.SKDFailInfo value of value of invalidGLName. Additionally, a signingTime
invalidGLName. Additionally, a signingTime attribute is attribute is included with the response.
included with the response.
2.c.2 - Else if the glName is supported by the GLA, the GLA checks 2.c.2 - Else if the glName is supported by the GLA, the GLA checks
to see if the glMemberName is present on the GL. to see if the glMemberName is present on the GL.
2.c.2.a - If the glMemberName is not present on the GL, the GLA 2.c.2.a - If the glMemberName is not present on the GL, the GLA
returns a response indicating cMCStatusInfoExt with returns a response indicating cMCStatusInfoExt with
cMCStatus.failed and cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of otherInfo.extendedFailInfo.SKDFailInfo value of
notAMember. Additionally, a signingTime attribute is notAMember. Additionally, a signingTime attribute is
included with the response. included with the response.
2.c.2.b - Else if the glMemberName is already on the GL, the GLA 2.c.2.b - Else if the glMemberName is already on the GL, the GLA
checks how the GL is administered. checks how the GL is administered.
2.c.2.b.1 - If the GL is closed, the GLA checks that the 2.c.2.b.1 - If the GL is closed, the GLA checks that the registered
registered GLO signed the request by checking that one GLO signed the request by checking that one of the
of the names in the digital signature certificate used names in the digital signature certificate used to sign
to sign the request matches the registered GLO. the request matches the registered GLO.
2.c.2.b.1.a - If the names do not match, the GLA returns a 2.c.2.b.1.a - If the names do not match, the GLA returns a response
response indicating cMCStatusInfoExt with indicating cMCStatusInfoExt with cMCStatus.failed and
cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of otherInfo.extendedFailInfo.SKDFailInfo value of
Turner Expires July 2003 47
And Distribution
closedGL. Additionally, a signingTime attribute is closedGL. Additionally, a signingTime attribute is
included with the response. included with the response.
2.c.2.b.1.b - Else if the names do match, the GLA returns a 2.c.2.b.1.b - Else if the names do match, the GLA returns a
cMCStatusInfoExt.cMCStatus.success and a signingTime cMCStatusInfoExt.cMCStatus.success and a signingTime
attribute (2 in Figure 5). The GLA also takes attribute (2 in Figure 5). The GLA also takes
administrative actions, which are beyond the scope administrative actions, which are beyond the scope of
of this document, to delete the member with the GL this document, to delete the member with the GL
stored on the GLA. Note that he GL also needs to be stored on the GLA. Note that he GL also needs to be
rekeyed as described in section 5. rekeyed as described in section 5.
2.c.2.b.1.b.1 - The GLA applies confidentiality to the response by 2.c.2.b.1.b.1 - The GLA applies confidentiality to the response by
encapsulating the SignedData.PKIData in an 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.c.2.b.1.b.2 - The GLA can also optionally apply another 2.c.2.b.1.b.2 - The GLA can 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 if the GL is managed, the GLA checks that either 2.c.2.b.2 - Else if the GL is managed, the GLA checks that either a
a registered GLO or the prospective member signed the 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 needs to match a registered used to sign the request needs to match a registered
GLO. For the prospective member, the name in GLO. For the prospective member, the name in
glMember.glMemberName needs to match one of the names glMember.glMemberName needs to match one of the names
in the certificate used to sign the request. in 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 returns a response prospective GL member, the GLA returns a response
indicating cMCStatusInfoExt with cMCStatus.failed indicating cMCStatusInfoExt with cMCStatus.failed and
and otherInfo.extendedFailInfo.SKDFailInfo value of otherInfo.extendedFailInfo.SKDFailInfo value of
noSpam. Additionally, a signingTime attribute is noSpam. Additionally, a signingTime attribute is
included with the response. included with the response.
2.c.2.b.2.b - Else if the signer is a registered GLO, the GLA 2.c.2.b.2.b - Else if the signer is a registered GLO, the GLA
returns a cMCStatusInfoExt.cMCStatus.success and a returns a cMCStatusInfoExt.cMCStatus.success and a
signingTime attribute(2 in Figure 6). The GLA also signingTime attribute(2 in Figure 6). The GLA also
takes administrative actions, which are beyond the takes administrative actions, which are beyond the
scope of this document, to delete the member with scope of this document, to delete the member with the
the GL stored on the GLA. Note that the GL will also GL stored on the GLA. Note that the GL will also be
be rekeyed as described in section 5. rekeyed as described in section 5.
2.c.2.b.2.b.1 - The GLA applies confidentiality to the response by 2.c.2.b.2.b.1 - The GLA applies confidentiality to the response by
encapsulating the SignedData.PKIData in an 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.c.2.b.2.b.2 - The GLA can also optionally apply another 2.c.2.b.2.b.2 - The GLA can also optionally apply another
SignedData over the EnvelopedData (see section SignedData over the EnvelopedData (see section
3.2.1.2). 3.2.1.2).
Turner Expires July 2003 48 2.c.2.b.2.c - Else if the signer is the prospective member, the GLA
And Distribution forwards the glDeleteMember request (see section
2.c.2.b.2.c - Else if the signer is the prospective member, the
GLA 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
more than one registered GLO, the GLO to which the more than one registered GLO, the GLO to which the
request is forwarded to is beyond the scope of this request is forwarded to is beyond the scope of this
document. Further processing of the forwarded document. Further processing of the forwarded request
request by GLOs is addressed in 3 of section 4.4.2. by GLOs is addressed in 3 of section 4.4.2.
2.c.2.b.2.c.1 - The GLA applies confidentiality to the forwarded 2.c.2.b.2.c.1 - The GLA applies confidentiality to the forwarded
request by encapsulating the SignedData.PKIData in request by encapsulating the SignedData.PKIData in an
an EnvelopedData if the request was encapsulated EnvelopedData if the request was encapsulated in an
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 can also optionally apply another 2.c.2.b.2.c.2 - The GLA can 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 if the GL is unmanaged, the GLA checks that 2.c.2.b.3 - Else if the GL is unmanaged, the GLA checks that either
either a registered GLO or the prospective member a registered GLO or the prospective member signed the
signed the request. For GLOs, one of the names in the request. For GLOs, one of the names in the certificate
certificate used to sign the request needs to match used to sign the request needs to match the name of a
the name of a registered GLO. For the prospective registered GLO. For the prospective member, the name
member, the name in glMember.glMemberName needs to in glMember.glMemberName needs to match one of the
match one of the names in the certificate used to sign names in the certificate used to sign the request.
the request.
2.c.2.b.3.a - If the signer is neither the GLO nor the prospective 2.c.2.b.3.a - If the signer is neither the GLO nor the prospective
member, the GLA returns a response indicating member, the GLA returns a response indicating
cMCStatusInfoExt with cMCStatus.failed and cMCStatusInfoExt with cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of otherInfo.extendedFailInfo.SKDFailInfo value of
noSpam. Additionally, a signingTime attribute is noSpam. Additionally, a signingTime attribute is
included with the response. included with the response.
2.c.2.b.3.b - Else if the signer is either a registered GLO or the 2.c.2.b.3.b - Else if the signer is either a registered GLO or the
member, the GLA returns a member, the GLA returns a
cMCStatusInfoExt.cMCStatus.success and a signingTime cMCStatusInfoExt.cMCStatus.success and a signingTime
attribute to the GLO (2 in Figure 6) if the GLO attribute to the GLO (2 in Figure 6) if the GLO
signed the request and to the GL member (3 in Figure signed the request and to the GL member (3 in Figure
6) if the GL member signed the request. The GLA also 6) if the GL member signed the request. The GLA also
takes administrative actions, which are beyond the takes administrative actions, which are beyond the
scope of this document, to delete the member with scope of this document, to delete the member with the
the GL stored on the GLA. GL stored on the GLA.
2.c.2.b.3.b.1 - The GLA applies confidentiality to the response by 2.c.2.b.3.b.1 - The GLA applies confidentiality to the response by
encapsulating the SignedData.PKIData in an 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.c.2.b.3.b.2 - The GLA can also optionally apply another 2.c.2.b.3.b.2 - The GLA can also optionally apply another
SignedData over the EnvelopedData (see section SignedData over the EnvelopedData (see section
3.2.1.2). 3.2.1.2).
Turner Expires July 2003 49
And Distribution
3 - Upon receipt of the cMCStatusInfoExt response, the GLO checks 3 - Upon receipt of the cMCStatusInfoExt response, the GLO checks
the signingTime and verifies the GLA signatures. If an the signingTime and verifies the GLA signatures. 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 verifies the response (see section 3.2.1.2 or 3.2.2), the GLO verifies the
outer signature and/or decrypt the outer layer prior to outer signature and/or decrypt the outer layer prior to
verifying the signature on the inner most SignedData. verifying the signature on the inner most SignedData.
3.a - If the signingTime attribute value is not within the locally 3.a - If the signingTime attribute value is not within the locally
accepted time window, the GLO MAY return a response accepted time window, the GLO MAY return a response
indicating cMCStatus.failed and otherInfo.failInfo.badTime indicating cMCStatus.failed and otherInfo.failInfo.badTime
and a signingTime attribute. and a signingTime attribute.
3.b - Else if signature processing continues and if the signatures 3.b - Else if signature processing continues and if the signatures
do verify, the GLO checks that one of the names in the do verify, the GLO checks that one of the names in the
certificate used to sign the response matches the name of certificate used to sign the response matches the name of
the GL. the GL.
3.b.1 If the name of the GL does not match the name present in 3.b.1 - If the name of the GL does not match the name present in
the certificate used to sign the message, the GLO should the certificate used to sign the message, the GLO should
not believe the response. not believe the response.
3.b.2 Else if the name of the GL matches the name present in the 3.b.2 - Else if the name of the GL matches the name present in the
certificate and: certificate and:
3.b.2.a - If the signatures verify and the response is 3.b.2.a - If the signatures verify and the response is
cMCStatusInfoExt.cMCStatus.success, the GLO has deleted cMCStatusInfoExt.cMCStatus.success, the GLO has deleted
the member from the GL. If member was deleted from a the member from the GL. If member was deleted from a
managed list and the original request was signed by the managed list and the original request was signed by the
member, the GLO sends a member, the GLO sends a
cMCStatusInfoExt.cMCStatus.success and a signingTime cMCStatusInfoExt.cMCStatus.success and a signingTime
attribute to the GL member. attribute to the GL member.
3.b.2.b - Else if the GLO received a 3.b.2.b - Else if the GLO received a
cMCStatusInfoExt.cMCStatus.failed with any reason, the cMCStatusInfoExt.cMCStatus.failed with any reason, the
GLO may reattempt to delete the member from the GL using GLO may reattempt to delete the member from the GL using
the information provided in the response. the information provided in the response.
4 - Upon receipt of the cMCStatusInfoExt response, the member 4 - Upon receipt of the cMCStatusInfoExt response, the member
checks the signingTime and verifies the GLA signature(s) or checks the signingTime and verifies the GLA signature(s) or GLO
GLO signature(s). If an additional SignedData and/or signature(s). If an additional SignedData and/or EnvelopedData
EnvelopedData encapsulates the response (see section 3.2.1.2 encapsulates the response (see section 3.2.1.2 or 3.2.2), the
or 3.2.2), the GLO verifies the outer signature and/or decrypt GLO verifies the outer signature and/or decrypt the outer layer
the outer layer prior to verifying the signature on the inner prior to verifying the signature on the inner most SignedData.
most SignedData.
4.b - If the signingTime attribute value is not within the locally 4.a - If the signingTime attribute value is not within the locally
accepted time window, the prospective member MAY return a accepted time window, the prospective member MAY return a
response indicating cMCStatus.failed and response indicating cMCStatus.failed and
otherInfo.failInfo.badTime and a signingTime attribute. otherInfo.failInfo.badTime and a signingTime attribute.
4.b - Else if signature processing continues and if the signatures 4.b - Else if signature processing continues and if the signatures
verify, the GL member checks that one of the names in the verify, the GL member checks that one of the names in the
Turner Expires July 2003 50
And Distribution
certificate used to sign the response matches the name of certificate used to sign the response matches the name of
the GL. the GL.
4.b.1 If the name of the GL does not match the name present in 4.b.1 - If the name of the GL does not match the name present in
the certificate used to sign the message, the GL member the certificate used to sign the message, the GL member
should not believe the response. should not believe the response.
4.b.2 Else if the name of the GL matches the name present in the 4.b.2 - Else if the name of the GL matches the name present in the
certificate and: certificate and:
4.b.2.a - If the signature(s) verify, the member has been deleted 4.b.2.a - If the signature(s) verify, the member has been deleted
from the GL. from the GL.
4.b.2.b - Else if the member received a 4.b.2.b - Else if the member received a
cMCStatusInfoExt.cMCStatus.failed with any reason, the cMCStatusInfoExt.cMCStatus.failed with any reason, the
member can reattempt to delete themselves from the GL member can reattempt to delete themselves from the GL
using the information provided in the response. using the information provided in the response.
4.4.2 Member Initiated Deletions 4.4.2. Member Initiated Deletions
The process for member initiated deletion of their own membership The process for member initiated deletion of their own membership
using the glDeleteMember requests is as follows: using the glDeleteMember requests is as follows:
1 - The member sends a 1 - The member sends a
SignedData.PKIData.controlSequence.glDeleteMember request to SignedData.PKIData.controlSequence.glDeleteMember request to
the GLA (A in Figure 6). The member includes: the name of the the GLA (A in Figure 6). The member includes: the name of the
GL in glName and their own name in glMemberToDelete. The GL GL in glName and their own name in glMemberToDelete. The GL
member MUST also include the signingTime attribute with this member MUST also include the signingTime attribute with this
request. request.
skipping to change at line 2682 skipping to change at page 55, line 43
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 member can also optionally apply another SignedData over 1.b - The member can 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 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 checks the 3 - Upon receipt of the forwarded request, the GLO checks the
signingTime and verifies the member signature on the inner signingTime and verifies the member signature on the inner most
most SignedData.PKIData and the GLA signature on the outer SignedData.PKIData and the GLA signature on the outer layer. If
layer. If an EnvelopedData encapsulates the inner most layer an EnvelopedData encapsulates the inner most layer (see section
(see section 3.2.1.2 or 3.2.2), the GLO decrypts the outer 3.2.1.2 or 3.2.2), the GLO decrypts the outer layer prior to
layer prior to verifying the signature on the inner most verifying the signature on the inner most SignedData. Note: For
SignedData. cases where the GL is closed and either (a) a prospective
member sends directly to the GLO or (b) the GLA has mistakenly
Note: For cases where the GL is closed and either (a) a forwarded the request to the GLO, the GLO should first
prospective member sends directly to the GLO or (b) the GLA determine whether to honor the request.
Turner Expires July 2003 51
And Distribution
has mistakenly forwarded the request to the GLO, the GLO
should first determine whether to honor the request.
3.a - If the signingTime attribute value is not within the locally 3.a - If the signingTime attribute value is not within the locally
accepted time window, the GLO MAY return a response accepted time window, the GLO MAY return a response
indicating cMCStatus.failed and otherInfo.failInfo.badTime indicating cMCStatus.failed and otherInfo.failInfo.badTime
and a signingTime attribute. and a signingTime attribute.
3.b - Else if signature processing continues if the signatures 3.b - Else if signature processing continues if the signatures
cannot be verified, the GLO returns a cMCStatusInfoExt cannot be verified, the GLO returns a cMCStatusInfoExt
response indicating cMCStatus.failed and response indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck and a signingTime otherInfo.failInfo.badMessageCheck and a signingTime
skipping to change at line 2723 skipping to change at page 56, line 30
3.c.1 - If the names match, the GLO sends a 3.c.1 - If the names match, the GLO sends a
SignedData.PKIResponse.controlSequence message back to the SignedData.PKIResponse.controlSequence message back to the
prospective member with cMCStatusInfoExt.cMCtatus.failed prospective member with cMCStatusInfoExt.cMCtatus.failed
indicating why the prospective member was denied in indicating why the prospective member was denied in
cMCStatusInfoExt.statusString. This stops people from cMCStatusInfoExt.statusString. This stops people from
adding people to GLs without their permission. adding people to GLs without their permission.
Additionally, a signingTime attribute is included with the Additionally, a signingTime attribute is included with the
response. response.
3.c.2 - Else if the names match, the GLO resubmits the 3.c.2 - Else if the names 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
in Figure 6). The GLO makes sure the glMemberName is Figure 6). The GLO makes sure the glMemberName is already
already on the GL. The GLO also generates a glRekey on the GL. The GLO also generates a glRekey request and
request and include it with the GLDeleteMember request include it with the GLDeleteMember request (see section
(see section 4.5). 4.5).
3.c.2.a - The GLO applies confidentiality to the new 3.c.2.a - The GLO applies confidentiality to the new GLDeleteMember
GLDeleteMember request by encapsulating the request by encapsulating the SignedData.PKIData in an
SignedData.PKIData in an EnvelopedData if the initial EnvelopedData if the initial request was encapsulated in
request was encapsulated in an EnvelopedData (see an EnvelopedData (see section 3.2.1.2).
section 3.2.1.2).
3.c.2.b - The GLO can also optionally apply another SignedData 3.c.2.b - The GLO can also optionally apply another SignedData over
over the EnvelopedData (see section 3.2.1.2). the EnvelopedData (see section 3.2.1.2).
4 - Further processing is as in 2 of section 4.4.1. 4 - Further processing is as in 2 of section 4.4.1.
Turner Expires July 2003 52 4.5. Request Rekey Of GL
And Distribution
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
follow: follow:
- 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
ought to contain a glRekey request. ought to contain a glRekey request.
- 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
skipping to change at line 2777 skipping to change at page 57, line 39
- 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
greater than one (1) and the GLO controls the GL rekey, the GLO may greater than one (1) and the GLO controls the GL rekey, the GLO may
generate a glRekey any time before the last shared KEK has expired. generate a glRekey any time before the last shared KEK has expired.
To be on the safe side, the GLO ought to request a rekey one (1) To be on the safe side, the GLO ought to request a rekey one (1)
duration before the last shared KEK expires. duration before the last shared KEK expires.
The GLA and GLO are the only entities allowed to initiate a GL The GLA and GLO are the only entities allowed to initiate a GL rekey.
rekey. The GLO indicated whether they are going to control rekeys or The GLO indicated whether they are going to control rekeys or whether
whether the GLA is going to control rekeys when they assigned the the GLA is going to control rekeys when they assigned the shared KEK
shared KEK to GL (see section 3.1.1). The GLO initiates a GL rekey to GL (see section 3.1.1). The GLO initiates a GL rekey at any time.
at any time. The GLA can be configured to automatically rekey the GL The GLA can be configured to automatically rekey the GL prior to the
prior to the expiration of the shared KEK (the length of time before expiration of the shared KEK (the length of time before the
the expiration is an implementation decision). The GLA can also expiration is an implementation decision). The GLA can also
automatically rekey GLs that have been compromised, but this is automatically rekey GLs that have been compromised, but this is
covered in section 5. Figure 7 depicts the protocol interactions to covered in section 5. Figure 7 depicts the protocol interactions to
request a GL rekey. Note that error messages are not depicted. request a GL rekey. Note that error messages are not depicted.
Additionally, behavior for the optional transactionId, senderNonce, Additionally, behavior for the optional transactionId, senderNonce,
and recipientNonce CMC control attributes is not addressed in these and recipientNonce CMC control attributes is not addressed in these
procedures. procedures.
+-----+ 1 2,A +-----+ +-----+ 1 2,A +-----+
| GLA | <-------> | GLO | | GLA | <-------> | GLO |
+-----+ +-----+ +-----+ +-----+
Turner Expires July 2003 53
And Distribution
Figure 7 - GL Rekey Request Figure 7 - GL Rekey Request
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 includes the request to the GLA (1 in Figure 7). The GLO includes 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
all outstanding shared KEKs it includes the glRekeyAllGLKeys all outstanding shared KEKs it includes the glRekeyAllGLKeys
set to TRUE. The GLO MUST also include a signingTime attribute set to TRUE. The GLO MUST also include a signingTime attribute
is included with this request. is included with this request.
1.a - The GLO can optionally apply confidentiality to the request 1.a - The GLO can 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 can also optionally apply another SignedData over 1.b - The GLO can also optionally apply another SignedData over the
the EnvelopedData (see section 3.2.1.2). EnvelopedData (see section 3.2.1.2).
2 - Upon receipt of the request, the GLA checks the signingTime 2 - Upon receipt of the request, the GLA checks the signingTime and
and verifies the signature on the inner most verifies the signature on the inner most SignedData.PKIData. If
SignedData.PKIData. If an additional SignedData and/or an additional SignedData and/or EnvelopedData encapsulates the
EnvelopedData encapsulates the request (see section 3.2.1.2 or request (see section 3.2.1.2 or 3.2.2), the GLA verifies the
3.2.2), the GLA verifies the outer signature and/or decrypt outer signature and/or decrypt the outer layer prior to
the outer layer prior to verifying the signature on the inner verifying the signature on the inner most SignedData.
most SignedData.
2.a - If the signingTime attribute value is not within the locally 2.a - If the signingTime attribute value is not within the locally
accepted time window, the GLA MAY return a response accepted time window, the GLA MAY return a response
indicating cMCStatus.failed and otherInfo.failInfo.badTime indicating cMCStatus.failed and otherInfo.failInfo.badTime
and a signingTime attribute. and a signingTime attribute.
2.c - Else if signature processing continues and if the signatures 2.b - Else if signature processing continues and if the signatures
do not verify, the GLA returns a cMCStatusInfoExt response do not verify, the GLA returns a cMCStatusInfoExt response
indicating cMCStatus.failed and indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck. Additionally, a otherInfo.failInfo.badMessageCheck. Additionally, a
signingTime attribute is included with the response. signingTime attribute is included with the response.
2.c - Else if the signatures do verify, the GLA makes sure the GL 2.c - Else if the signatures do verify, the GLA makes 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.c.1 - If the glName present does not match a GL stored on the 2.c.1 - If the glName present does not match a GL stored on the
GLA, the GLA returns a response indicating GLA, the GLA returns a response indicating cMCStatusInfoExt
cMCStatusInfoExt with cMCStatus.failed and with cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of otherInfo.extendedFailInfo.SKDFailInfo value of
invalidGLName. Additionally, a signingTime attribute is invalidGLName. Additionally, a signingTime attribute is
included with the response. included with the response.
Turner Expires July 2003 54
And Distribution
2.c.2 - Else if the glName present matches a GL stored on the GLA, 2.c.2 - Else if the glName present matches a GL stored on the GLA,
the GLA checks that a registered GLO signed the request by the GLA checks that a registered GLO signed the request by
checking that one of the names in the certificate used to checking that one of the names in the certificate used to
sign the request is a registered GLO. sign the request is a registered GLO.
2.c.2.a - If the names do not match, the GLA returns a response 2.c.2.a - If the names do not match, the GLA returns a response
indicating cMCStatusInfoExt with cMCStatus.failed and indicating cMCStatusInfoExt with cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of otherInfo.extendedFailInfo.SKDFailInfo value of
noGLONameMatch. Additionally, a signingTime attribute is noGLONameMatch. Additionally, a signingTime attribute is
included with the response. included with the response.
skipping to change at line 2905 skipping to change at page 60, line 16
KEK (see section 5). KEK (see section 5).
2.c.2.b.4.a - The GLA applies confidentiality to response by 2.c.2.b.4.a - The GLA applies 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.c.2.b.4.b - The GLA can also optionally apply another SignedData 2.c.2.b.4.b - The GLA can also optionally apply another SignedData
over the EnvelopedData (see section 3.2.1.2). over the EnvelopedData (see section 3.2.1.2).
Turner Expires July 2003 55
And Distribution
3 - Upon receipt of the cMCStatusInfoExt response, the GLO checks 3 - Upon receipt of the cMCStatusInfoExt response, the GLO checks
the signingTime and verifies the GLA signature(s). If an the signingTime and verifies the GLA signature(s). If an
additional SignedData and/or EnvelopedData encapsulates the additional SignedData and/or EnvelopedData encapsulates the
forwarded response (see section 3.2.1.2 or 3.2.2), the GLO forwarded response (see section 3.2.1.2 or 3.2.2), the GLO
verifies the outer signature and/or decrypt the forwarded verifies the outer signature and/or decrypt the forwarded
response prior to verifying the signature on the inner most response prior to verifying the signature on the inner most
SignedData. SignedData.
3.a - If the signingTime attribute value is not within the locally 3.a - If the signingTime attribute value is not within the locally
accepted time window, the GLA MAY return a response accepted time window, the GLA MAY return a response
skipping to change at line 2942 skipping to change at page 61, line 5
3.b.2.a - If the signatures verify and the response is 3.b.2.a - If the signatures verify and the response is
cMCStatusInfoExt.cMCStatus.success, the GLO has cMCStatusInfoExt.cMCStatus.success, the GLO has
successfully rekeyed the GL. successfully rekeyed the GL.
3.b.2.b - Else if the GLO received a 3.b.2.b - Else if the GLO received a
cMCStatusInfoExt.cMCStatus.failed with any reason, the cMCStatusInfoExt.cMCStatus.failed with any reason, the
GLO can reattempt to rekey the GL using the information GLO can reattempt to rekey the GL using the information
provided in the response. 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
automatically issue a glKey message (see section 5). In addition the issue a glKey message (see section 5). In addition the GLA will
GLA will generate a cMCStatusInfoExt to indicate to the GL that a generate a cMCStatusInfoExt to indicate to the GL that a successful
successful rekey has occurred. The process for GLA initiated rekey rekey has occurred. The process for GLA initiated rekey is as
is as follows: follows:
1 - The GLA generates for all GLOs a 1 - The GLA generates for all GLOs a
SignedData.PKIData.controlSequence.cMCStatusInfoExt.cMCStatus. SignedData.PKIData.controlSequence.cMCStatusInfoExt.cMCStatus.
success and includes a signingTime attribute (A in Figure 7). success and includes a signingTime attribute (A in Figure 7).
1.a - The GLA can optionally apply confidentiality to the request 1.a - The GLA can 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).
Turner Expires July 2003 56 1.b - The GLA can also optionally apply another SignedData over the
And Distribution EnvelopedData (see section 3.2.1.2).
1.b - The GLA can also optionally apply another SignedData over
the EnvelopedData (see section 3.2.1.2).
2 - Upon receipt of the cMCStatusInfoExt.cMCStatus.success 2 - Upon receipt of the cMCStatusInfoExt.cMCStatus.success
response, the GLO checks the signingTime and verifies the GLA response, the GLO checks the signingTime and verifies the GLA
signature(s). If an additional SignedData and/or EnvelopedData signature(s). If an additional SignedData and/or EnvelopedData
encapsulates the forwarded response (see section 3.2.1.2 or encapsulates the forwarded response (see section 3.2.1.2 or
3.2.2), the GLO MUST verify the outer signature and/or decrypt 3.2.2), the GLO 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.
2.a - If the signingTime attribute value is not within the locally 2.a - If the signingTime attribute value is not within the locally
accepted time window, the GLO MAY return a response accepted time window, the GLO MAY return a response
indicating cMCStatus.failed and otherInfo.failInfo.badTime indicating cMCStatus.failed and otherInfo.failInfo.badTime
and a signingTime attribute. and a signingTime attribute.
2.b - Else if signature processing continues and if the signatures 2.b - Else if signature processing continues and if the signatures
verify, the GLO checks that one of the names in the verify, the GLO checks that one of the names in the
certificate used to sign the response matches the name of certificate used to sign the response matches the name of
the GL. the GL.
2.b.1 - If the name of the GL does not match the name present in 2.b.1 - If the name of the GL does not match the name present in
the certificate used to sign the message, the GLO ought the certificate used to sign the message, the GLO ought not
not believe the response. believe the response.
2.b.2 - Else if the name of the GL does match the name present in 2.b.2 - Else if the name of the GL does match the name present in
the certificate and and the response is the certificate and and the response is
cMCStatusInfoExt.cMCStatus.success, the GLO knows the GLA cMCStatusInfoExt.cMCStatus.success, the GLO knows the GLA
has successfully rekeyed the GL. 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
GLO if the GL membership grows large. To support distributing the 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
interactions to send glAddOwner and glRemoveOwner messages and the interactions to send glAddOwner and glRemoveOwner messages and the
resulting response messages. Note that error messages are not shown. resulting response messages. Note that error messages are not shown.
Additionally, behavior for the optional transactionId, senderNonce, Additionally, behavior for the optional transactionId, senderNonce,
and recipientNonce CMC control attributes is not addressed in these and recipientNonce CMC control attributes is not addressed in these
procedures. procedures.
+-----+ 1 2 +-----+ +-----+ 1 2 +-----+
| GLA | <-------> | GLO | | GLA | <-------> | GLO |
+-----+ +-----+ +-----+ +-----+
Figure 8 - GLO Add & Delete Owners Figure 8 - GLO Add & Delete Owners
Turner Expires July 2003 57
And Distribution
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
includes: the GL name in glName, the name and address of the includes: the GL name in glName, the name and address of the
GLO in glOwnerName and glOwnerAddress, respectively. The GLO GLO in glOwnerName and glOwnerAddress, respectively. The GLO
MUST also include the signingTime attribute with this request. MUST also include the signingTime attribute with this request.
1.a - The GLO can optionally apply confidentiality to the request 1.a - The GLO can 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 can also optionally apply another SignedData over 1.b - The GLO can also optionally apply another SignedData over the
the EnvelopedData (see section 3.2.1.2). 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 checks the signingTime and verifies the GLO signature(s). GLA checks the signingTime and verifies the GLO signature(s).
If an additional SignedData and/or EnvelopedData encapsulates If an additional SignedData and/or EnvelopedData encapsulates
the request (see section 3.2.1.2 or 3.2.2), the GLA verifies the request (see section 3.2.1.2 or 3.2.2), the GLA verifies
the outer signature and/or decrypt the outer layer prior to the outer signature and/or decrypt the outer layer prior to
verifying the signature on the inner most SignedData. verifying the signature on the inner most SignedData.
2.a - If the signingTime attribute value is not within the locally 2.a - If the signingTime attribute value is not within the locally
accepted time window, the GLA MAY return a response accepted time window, the GLA MAY return a response
skipping to change at line 3052 skipping to change at page 63, line 17
indicating cMCStatus.failed and indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck. Additionally, a otherInfo.failInfo.badMessageCheck. Additionally, a
signingTime attribute is included with the response. signingTime attribute is included with the response.
2.c - Else if the signatures verify, the GLA makes sure the GL is 2.c - Else if the signatures verify, the GLA makes sure the GL is
supported by checking that the glName matches a glName supported by checking that the glName matches a glName
stored on the GLA. stored on the GLA.
2.c.1 - If the glName is not supported by the GLA, the GLA returns 2.c.1 - If the glName is not supported by the GLA, the GLA returns
a response indicating cMCStatusInfoExt with a response indicating cMCStatusInfoExt with
cMCStatus.failed and cMCStatus.failed and otherInfo.extendedFailInfo.SKDFailInfo
otherInfo.extendedFailInfo.SKDFailInfo value of value of invalidGLName. Additionally, a signingTime
invalidGLName. Additionally, a signingTime attribute is attribute is included with the response.
included with the response.
2.c.2 - Else if the glName is supported by the GLA, the GLA
ensures a registered GLO signed the glAddOwner or
glRemoveOwner request by checking that one of the names
present in the digital signature certificate used to sign
the glAddOwner or glDeleteOwner request matches the name
of a registered GLO.
Turner Expires July 2003 58 2.c.2 - Else if the glName is supported by the GLA, the GLA ensures
And Distribution a registered GLO signed the glAddOwner or glRemoveOwner
request by checking that one of the names present in the
digital signature certificate used to sign the glAddOwner
or glDeleteOwner request matches the name of a registered
GLO.
2.c.2.a - If the names do not match, the GLA returns a response 2.c.2.a - If the names do not match, the GLA returns a response
indicating cMCStatusInfoExt with cMCStatus.failed and indicating cMCStatusInfoExt with cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of otherInfo.extendedFailInfo.SKDFailInfo value of
noGLONameMatch. Additionally, a signingTime attribute is noGLONameMatch. Additionally, a signingTime attribute is
included with the response. included with the response.
2.c.2.b - Else if the names match, the GLA returns a 2.c.2.b - Else if the names match, the GLA returns a
cMCStatusInfoExt.cMCStatus.success and a signingTime cMCStatusInfoExt.cMCStatus.success and a signingTime
attribute (2 in Figure 4). The GLA also takes attribute (2 in Figure 4). The GLA also takes
skipping to change at line 3106 skipping to change at page 64, line 19
3.a - If the signingTime attribute value is not within the locally 3.a - If the signingTime attribute value is not within the locally
accepted time window, the GLO MAY return a response accepted time window, the GLO MAY return a response
indicating cMCStatus.failed and otherInfo.failInfo.badTime indicating cMCStatus.failed and otherInfo.failInfo.badTime
and a signingTime attribute. and a signingTime attribute.
3.b - Else if signature processing continues and if the signatures 3.b - Else if signature processing continues and if the signatures
verify, the GLO checks that one of the names in the verify, the GLO checks that one of the names in the
certificate used to sign the response matches the name of certificate used to sign the response matches the name of
the GL. the GL.
3.b.1 If the name of GL does not match the name present in the 3.b.1 - If the name of GL 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 if the name of the GL does match the name present in 3.b.2 - Else if the name of the GL does match the name present in
the certificate and: the certificate and:
3.b.2.a - If the signatures verify and the response was 3.b.2.a - If the signatures verify and the response was
cMCStatusInfoExt.cMCStatus.success, the GLO has cMCStatusInfoExt.cMCStatus.success, the GLO has
successfully added or removed the GLO. successfully added or removed the GLO.
3.b.2.b - Else if the signatures verify and the response was 3.b.2.b - Else if the signatures verify and the response was
cMCStatusInfoExt.cMCStatus.failed with any reason, the cMCStatusInfoExt.cMCStatus.failed with any reason, the
Turner Expires July 2003 59
And Distribution
GLO can reattempt to add or delete the GLO using the GLO can reattempt to add or delete the GLO using the
information provided in the response. information provided in the response.
4.7 Indicate KEK Compromise 4.7. Indicate KEK Compromise
There will be times when the shared KEK is compromised. GL members There will be times when the shared KEK is compromised. GL members
and GLOs use glkCompromise to tell the GLA that the shared KEK has and GLOs use glkCompromise to tell the GLA that the shared KEK has
been compromised. Figure 9 depicts the protocol interactions for GL been compromised. Figure 9 depicts the protocol interactions for GL
Key Compromise. Note that error messages are not shown. Key Compromise. Note that error messages are not shown. Additionally,
Additionally, behavior for the optional transactionId, senderNonce, behavior for the optional transactionId, senderNonce, and
and recipientNonce CMC control attributes is not addressed in these recipientNonce CMC control attributes is not addressed in these
procedures. procedures.
+-----+ 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 |
+----------+ +----------+
Figure 9 - GL Key Compromise Figure 9 - GL Key Compromise
4.7.1 GL Member Initiated KEK Compromise Message 4.7.1. GL Member Initiated KEK Compromise Message
The process for GL member initiated glkCompromise messages is as The process for GL member initiated glkCompromise messages is as
follows: follows:
1 - The GL member sends a 1 - The GL member sends a
SignedData.PKIData.controlSequence.glkCompromise request to SignedData.PKIData.controlSequence.glkCompromise request to the
the GLA (1 in Figure 9). The GL member includes the name of GLA (1 in Figure 9). The GL member includes the name of the GL
the GL in GeneralName. The GL member MUST also include the in GeneralName. The GL member MUST also include the signingTime
signingTime attribute with this request. attribute with this request.
1.a - The GL member can optionally apply confidentiality to the 1.a - The GL member can 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). The glkCompromise can EnvelopedData (see section 3.2.1.2). The glkCompromise can
be included in an EnvelopedData generated with the be included in an EnvelopedData generated with the
compromised shared KEK. compromised shared KEK.
1.b - The GL member can also optionally apply another SignedData 1.b - The GL member can 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 glkCompromise request, the GLA checks the 2 - Upon receipt of the glkCompromise request, the GLA checks the
signingTime and verifies the GL member signature(s). If an signingTime and verifies the GL member signature(s). If an
additional SignedData and/or EnvelopedData encapsulates the additional SignedData and/or EnvelopedData encapsulates the
request (see section 3.2.1.2 or 3.2.2), the GLA verifies the request (see section 3.2.1.2 or 3.2.2), the GLA verifies the
outer signature and/or decrypt the outer layer prior to outer signature and/or decrypt the outer layer prior to
verifying the signature on the inner most SignedData. verifying the signature on the inner most SignedData.
Turner Expires July 2003 60
And Distribution
2.a - If the signingTime attribute value is not within the locally 2.a - If the signingTime attribute value is not within the locally
accepted time window, the GLA MAY return a response accepted time window, the GLA MAY return a response
indicating cMCStatus.failed and otherInfo.failInfo.badTime indicating cMCStatus.failed and otherInfo.failInfo.badTime
and a signingTime attribute. and a signingTime attribute.
2.b - Else if signature processing continues and if the signatures 2.b - Else if signature processing continues and if the signatures
cannotbe verified, the GLA returns a cMCStatusInfoExt cannotbe verified, the GLA returns a cMCStatusInfoExt
response indicating cMCStatus.failed and response indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck. Additionally, a otherInfo.failInfo.badMessageCheck. Additionally, a
signingTime attribute is included with the response. signingTime attribute is included with the response.
2.c - Else if the signatures verify, the GLA makes sure the GL is 2.c - Else if the signatures verify, the GLA makes sure the GL is
supported by checking that the indicated GL name matches a supported by checking that the indicated GL name matches a
glName stored on the GLA. glName stored on the GLA.
2.c.1 - If the glName is not supported by the GLA, the GLA returns 2.c.1 - If the glName is not supported by the GLA, the GLA returns
a response indicating cMCStatusInfoExt with a response indicating cMCStatusInfoExt with
cMCStatus.failed and cMCStatus.failed and otherInfo.extendedFailInfo.SKDFailInfo
otherInfo.extendedFailInfo.SKDFailInfo value of value of invalidGLName. Additionally, a signingTime
invalidGLName. Additionally, a signingTime attribute is attribute is included with the response.
included with the response.
2.c.2 - Else if the glName is supported by the GLA, the GLA checks 2.c.2 - Else if the glName is supported by the GLA, the GLA checks
who signed the request. For GLOs, one of the names in the who signed the request. For GLOs, one of the names in the
certificate used to sign the request needs to match a certificate used to sign the request needs to match a
registered GLO. For the member, the name in registered GLO. For the member, the name in
glMember.glMemberName needs to match one of the names in glMember.glMemberName needs to match one of the names in
the certificate used to sign the request. the certificate used to sign the request.
2.c.2.a - If the GLO signed the request, the GLA generates a glKey 2.c.2.a - If the GLO signed the request, the GLA generates a glKey
message as described in section 5 to rekey the GL (4 in message as described in section 5 to rekey the GL (4 in
Figure 9). Figure 9).
2.c.2.b - Else if someone other than the GLO signed the request, 2.c.2.b - Else if someone other than the GLO signed the request,
the GLA forwards the glkCompromise message (see section the GLA forwards the glkCompromise message (see section
3.2.3) to the GLO (2{1} in Figure 9). If there is more 3.2.3) to the GLO (2{1} in Figure 9). If there is more
than one GLO, to which GLO the request is forwarded is than one GLO, to which GLO the request is forwarded is
beyond the scope of this document. Further processing by beyond the scope of this document. Further processing by
the GLO is discussed in section 4.7.2. the GLO is discussed in section 4.7.2.
4.7.2 GLO Initiated KEK Compromise Message 4.7.2. GLO Initiated KEK Compromise Message
The process for GLO initiated glkCompromise messages is as follows: The process for GLO initiated glkCompromise messages is as follows:
1 - The GLO either: 1 - The GLO either:
1.a - Generates the glkCompromise message itself by sending a 1.a - Generates the glkCompromise message itself by sending a
SignedData.PKIData.controlSequence.glkCompromise request to SignedData.PKIData.controlSequence.glkCompromise request to
the GLA (5 in Figure 9). The GLO includes the name of the GL the GLA (5 in Figure 9). The GLO includes the name of the GL
Turner Expires July 2003 61
And Distribution
in GeneralName. The GLO MUST also include a signingTime in GeneralName. The GLO MUST also include a signingTime
attribute with this request. attribute with this request.
1.a.1 - The GLO can optionally apply confidentiality to the 1.a.1 - The GLO can optionally apply confidentiality to the request
request by encapsulating the SignedData.PKIData in an by encapsulating the SignedData.PKIData in an EnvelopedData
EnvelopedData (see section 3.2.1.2). The glkCompromise can (see section 3.2.1.2). The glkCompromise can be included in
be included in an EnvelopedData generated with the an EnvelopedData generated with the compromised shared KEK.
compromised shared KEK.
1.a.2 - The GLO can also optionally apply another SignedData over 1.a.2 - The GLO can also optionally apply another SignedData over
the EnvelopedData (see section 3.2.1.2). the EnvelopedData (see section 3.2.1.2).
1.b Otherwise, checks the signingTime and verifies the GLA and 1.b - Otherwise, checks the signingTime and verifies the GLA and GL
GL member signatures on the forwarded glkCompromise message. member signatures on the forwarded glkCompromise message. If
If an additional SignedData and/or EnvelopedData an additional SignedData and/or EnvelopedData encapsulates
encapsulates the request (see section 3.2.1.2 or 3.2.2), the the request (see section 3.2.1.2 or 3.2.2), the GLO verifies
GLO verifies the outer signature and/or decrypt the outer the outer signature and/or decrypt the outer layer prior to
layer prior to verifying the signature on the inner most verifying the signature on the inner most SignedData.
SignedData.
1.b.1 - If the signingTime attribute value is not within the 1.b.1 - If the signingTime attribute value is not within the
locally accepted time window, the GLO MAY return a locally accepted time window, the GLO MAY return a response
response indicating cMCStatus.failed and indicating cMCStatus.failed and otherInfo.failInfo.badTime
otherInfo.failInfo.badTime and a signingTime attribute. and a signingTime attribute.
1.b.2 - Else if signature processing continues and if the 1.b.2 - Else if signature processing continues and if the
signatures cannot be verified, the GLO returns a signatures cannot be verified, the GLO returns a
cMCStatusInfoExt response indicating cMCStatus.failed and cMCStatusInfoExt response indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck. Additionally, a otherInfo.failInfo.badMessageCheck. Additionally, a
signingTime attribute is included with the response. signingTime attribute is included with the response.
1.b.2.a - If the signatures verify, the GLO checks the names in 1.b.2.a - If the signatures verify, the GLO checks the names in the
the certificate match the name of the signer (i.e., the certificate match the name of the signer (i.e., the name
name in the certificate used to sign the GL member's in the certificate used to sign the GL member's request
request is the GL member). is the GL member).
1.b.2.a.1 If either name does not match, the GLO ought not trust 1.b.2.a.1 - If either name does not match, the GLO ought not trust
the signer and it ought not forward the message to the the signer and it ought not forward the message to the
GLA. GLA.
1.b.2.a.2 Else if the names match and the signatures verify, the 1.b.2.a.2 - Else if the names match and the signatures verify, the
GLO determines whether to forward the glkCompromise GLO determines whether to forward the glkCompromise
message back to the GLA (3{1} in Figure 9). Further message back to the GLA (3{1} in Figure 9). Further
processing by the GLA is in 2 of section 4.7.1. The processing by the GLA is in 2 of section 4.7.1. The
GLO can also return a response to the prospective GLO can also return a response to the prospective
member with cMCStatusInfoExt.cMCtatus.success member with cMCStatusInfoExt.cMCtatus.success
indicating that the glkCompromise message was indicating that the glkCompromise message was
successfully received. successfully received.
Turner Expires July 2003 62 4.8. Request KEK Refresh
And Distribution
4.8 Request KEK Refresh
There will be times when GL members have unrecoverably lost their There will be times when GL members have unrecoverably lost their
shared KEK. The shared KEK is not compromised and a rekey of the shared KEK. The shared KEK is not compromised and a rekey of the
entire GL is not necessary. GL members use the glkRefresh message to entire GL is not necessary. GL members use the glkRefresh message to
request that the shared KEK(s) be redistributed to them. Figure 10 request that the shared KEK(s) be redistributed to them. Figure 10
depicts the protocol interactions for GL Key Refresh. Note that depicts the protocol interactions for GL Key Refresh. Note that error
error messages are not shown. Additionally, behavior for the messages are not shown. Additionally, behavior for the optional
optional transactionId, senderNonce, and recipientNonce CMC control transactionId, senderNonce, and recipientNonce CMC control attributes
attributes is not addressed in these procedures. is not addressed in these procedures.
+-----+ 1 2 +----------+ +-----+ 1 2 +----------+
| GLA | <-----------> | Member | | GLA | <-----------> | Member |
+-----+ +----------+ +-----+ +----------+
Figure 10 - GL KEK Refresh Figure 10 - GL KEK Refresh
The process for glkRefresh is as follows: The process for glkRefresh is as follows:
1 - The GL member sends a 1 - The GL member sends a
skipping to change at line 3333 skipping to change at page 68, line 46
accepted time window, the GLA MAY return a response accepted time window, the GLA MAY return a response
indicating cMCStatus.failed and otherInfo.failInfo.badTime indicating cMCStatus.failed and otherInfo.failInfo.badTime
and a signingTime attribute. and a signingTime attribute.
2.b - Else if signature processing continues and if the signatures 2.b - Else if signature processing continues and if the signatures
cannot be verified, the GLA returns a cMCStatusInfoExt cannot be verified, the GLA returns a cMCStatusInfoExt
response indicating cMCStatus.failed and response indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck. Additionally, a otherInfo.failInfo.badMessageCheck. Additionally, a
signingTime attribute is included with the response. signingTime attribute is included with the response.
Turner Expires July 2003 63
And Distribution
2.c - Else if the signatures verify, the GLA makes sure the GL is 2.c - Else if the signatures verify, the GLA makes sure the GL is
supported by checking that the GLGeneralName matches a supported by checking that the GLGeneralName matches a
glName stored on the GLA. glName stored on the GLA.
2.c.1 - If the name of the GL is not supported by the GLA, the GLA 2.c.1 - If the name of the GL is not supported by the GLA, the GLA
returns a response indicating cMCStatusInfoExt with returns a response indicating cMCStatusInfoExt with
cMCStatus.failed and cMCStatus.failed and otherInfo.extendedFailInfo.SKDFailInfo
otherInfo.extendedFailInfo.SKDFailInfo value of value of invalidGLName. Additionally, a signingTime
invalidGLName. Additionally, a signingTime attribute is attribute is included with the response.
included with the response.
2.c.2 - Else if the glName is supported by the GLA, the GLA 2.c.2 - Else if the glName is supported by the GLA, the GLA ensures
ensures the GL member is on the GL. the GL member is on the GL.
2.c.2.a - If the glMemberName is not present on the GL, the GLA 2.c.2.a - If the glMemberName is not present on the GL, the GLA
returns a response indicating cMCStatusInfoExt with returns a response indicating cMCStatusInfoExt with
cMCStatus.failed and cMCStatus.failed and
otherInfo.extendedFailInfo.SKDFailInfo value of noSpam. otherInfo.extendedFailInfo.SKDFailInfo value of noSpam.
Additionally, a signingTime attribute is included with Additionally, a signingTime attribute is included with
the response. the response.
2.c.2.b - Else if the glMemberName is present on the GL, the GLA 2.c.2.b - Else if the glMemberName is present on the GL, the GLA
returns a cMCStatusInfoExt.cMCStatus.success, a returns a cMCStatusInfoExt.cMCStatus.success, a
signingTime attribute, and a glKey message (2 in Figure signingTime attribute, and a glKey message (2 in Figure
10) as described in section 5. 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
a GL because they do not know the algorithm(s) or some other GL because they do not know the algorithm(s) or some other
characteristic that the GLA supports. There can also be times when characteristic that the GLA supports. There can 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
the GLA (these requests are not defined in the document). 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. Note error interactions for glaQueryRequest and glaQueryResponse. Note error
messages are not shown. Additionally, behavior for the optional messages are not shown. Additionally, behavior for the optional
transactionId, senderNonce, and recipientNonce CMC control transactionId, senderNonce, and recipientNonce CMC control attributes
attributes is not addressed in these procedures. is not addressed in these procedures.
+-----+ 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
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 GL
Turner Expires July 2003 64 member indicates the information they are interested in
And Distribution
the GLA (1 in Figure 11). The GLO, GL member, or prospective
GL member indicates the information they are interested in
receiving from the GLA. Additionally, a signingTime attribute receiving from the GLA. Additionally, a signingTime attribute
is included with this request. is included with this request.
1.a - The GLO, GL member, or prospective GL member can optionally 1.a - The GLO, GL member, or prospective GL member can optionally
apply confidentiality to the request by encapsulating the apply confidentiality to the request by encapsulating the
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 can also 1.b - The GLO, GL member, or prospective GL member can also
optionally apply another SignedData over the EnvelopedData optionally apply another SignedData over the EnvelopedData
skipping to change at line 3421 skipping to change at page 70, line 33
2.b - Else if the GLA does accept GLAQueryRequests, the GLA checks 2.b - Else if the GLA does accept GLAQueryRequests, the GLA checks
the signingTime and verifies the GLO, GL member, or the signingTime and verifies the GLO, GL member, or
prospective GL member signature(s). If an additional prospective GL member signature(s). If an additional
SignedData and/or EnvelopedData encapsulates the request SignedData and/or EnvelopedData encapsulates the request
(see section 3.2.1.2 or 3.2.2), the GLA verifies the outer (see section 3.2.1.2 or 3.2.2), the GLA verifies 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.b.1 - If the signingTime attribute value is not within the 2.b.1 - If the signingTime attribute value is not within the
locally accepted time window, the GLA MAY return a locally accepted time window, the GLA MAY return a response
response indicating cMCStatus.failed and indicating cMCStatus.failed and otherInfo.failInfo.badTime
otherInfo.failInfo.badTime and a signingTime attribute. and a signingTime attribute.
2.b.2 - Else if the signature processing continues and if the 2.b.2 - Else if the signature processing continues and if the
signatures cannot be verified, the GLA returns a signatures cannot be verified, the GLA returns a
cMCStatusInfoExt response indicating cMCStatus.failed and cMCStatusInfoExt response indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck. Additionally, a otherInfo.failInfo.badMessageCheck. Additionally, a
signingTime attribute is included with the response. signingTime attribute is included with the response.
2.b.3 - Else if the signatures verify, the GLA returns a 2.b.3 - Else if the signatures verify, the GLA returns a
glaQueryResponse (2 in Figure 11) with the correct glaQueryResponse (2 in Figure 11) with the correct response
response if the glaRequestType is supported or return a if the glaRequestType is supported or return a
cMCStatusInfoExt response indicating cMCStatus.noSupport cMCStatusInfoExt response indicating cMCStatus.noSupport if
if the glaRequestType is not supported. Additionally, a the glaRequestType is not supported. Additionally, a
signingTime attribute is included with the response. signingTime attribute is included with the response.
2.b.3.a - The GLA applies confidentiality to the response by 2.b.3.a - The GLA applies 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).
Turner Expires July 2003 65 2.b.3.b - The GLA can also optionally apply another SignedData over
And Distribution the EnvelopedData (see section 3.2.1.2).
2.b.3.b - The GLA can also optionally apply another SignedData
over the EnvelopedData (see section 3.2.1.2).
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 checks the signingTime and verifies the prospective GL member checks the signingTime and verifies the
GLA signature(s). If an additional SignedData and/or GLA 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
or 3.2.2), the GLO, GL member, or prospective GL member 3.2.2), the GLO, GL member, or prospective GL member verifies
verifies the outer signature and/or decrypt the outer layer the outer signature and/or decrypt the outer layer prior to
prior to verifying the signature on the inner most SignedData. verifying the signature on the inner most SignedData.
3.a - If the signingTime attribute value is not within the locally 3.a - If the signingTime attribute value is not within the locally
accepted time window, the GLO, GL member, or prospective GL accepted time window, the GLO, GL member, or prospective GL
member MAY return a response indicating cMCStatus.failed and member MAY return a response indicating cMCStatus.failed and
otherInfo.failInfo.badTime and a signingTime attribute. otherInfo.failInfo.badTime and a signingTime attribute.
3.b - Else if signature processing continues and if the signatures 3.b - Else if signature processing continues and if the signatures
do not verify, the GLO, GL member, or prospective GL member do not verify, the GLO, GL member, or prospective GL member
returns a cMCStatusInfoExt response indicating returns a cMCStatusInfoExt response indicating
cMCStatus.failed and otherInfo.failInfo.badMessageCheck. cMCStatus.failed and otherInfo.failInfo.badMessageCheck.
Additionally, a signingTime attribute is included with the Additionally, a signingTime attribute is included with the
response. response.
3.c - Else if the signatures verify, then the GLO, GL member, or 3.c - Else if the signatures verify, then the GLO, GL member, or
prospective GL member checks that one of the names in the prospective GL member checks that one of the names in the
certificate used to sign the response matches the name of certificate used to sign the response matches the name of
the GL. the GL.
3.c.1 If the name of the GL does not match the name present in 3.c.1 - If the name of the GL does not match the name present in
the certificate used to sign the message, the GLO ought the certificate used to sign the message, the GLO ought not
not believe the response. believe the response.
3.c.2 - Else if the name of the GL matches the name present in the 3.c.2 - Else if the name of the GL matches the name present in the
certificate and the response was glaQueryResponse, then certificate and the response was glaQueryResponse, then the
the GLO, GL member, or prospective GL member may use the GLO, GL member, or prospective GL member may use the
information contained therein. information contained therein.
4.10 Update Member Certificate 4.10. Update Member Certificate
When the GLO generates a glAddMember request, when the GLA generates When the GLO generates a glAddMember request, when the GLA generates
a glKey message, or when the GLA processes a glAddMember there can a glKey message, or when the GLA processes a glAddMember there can be
be instances when GL member's certificate has expired or is invalid. instances when GL member's certificate has expired or is invalid. In
In these instances the GLO or GLA may request that the GL member these instances the GLO or GLA may request that the GL member provide
provide a new certificate to avoid the GLA from being unable to a new certificate to avoid the GLA from being unable to generate a
generate a glKey message for the GL member. There might also be glKey message for the GL member. There might also be times when the
times when the GL member knows their certificate is about to expire GL member knows their certificate is about to expire or has been
or has been revoked and they will not be able to receive GL rekeys. revoked and they will not be able to receive GL rekeys. Behavior for
Behavior for the optional transactionId, senderNonce, and the optional transactionId, senderNonce, and recipientNonce CMC
recipientNonce CMC control attributes is not addressed in these control attributes is not addressed in these procedures.
procedures.
Turner Expires July 2003 66
And Distribution
4.10.1 GLO and GLA Initiated Update Member Certificate 4.10.1. GLO and GLA Initiated Update Member Certificate
The process for GLO initiated glUpdateCert is as follows: The process for GLO initiated glUpdateCert is as follows:
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
the GL member. The GLO or GLA indicates the GL name in glName GL member. The GLO or GLA indicates the GL name in glName and
and the GL member name in glMemberName. Additionally, a the GL member name in glMemberName. Additionally, a signingTime
signingTime attribute is included with this request. attribute is included with this request.
1.a - The GLO or GLA can optionally apply confidentiality to the 1.a - The GLO or GLA can 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 ought not use it to has been revoked, the GLO or GLA ought not use it to
generate the EnvelopedData that encapsulates the generate the EnvelopedData that encapsulates the
glProvideCert request. glProvideCert request.
1.b - The GLO or GLA can also optionally apply another SignedData 1.b - The GLO or GLA can 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 checks
checks the signingTime and verifies the GLO or GLA the signingTime and verifies the GLO or GLA signature(s). If an
signature(s). If an additional SignedData and/or EnvelopedData additional SignedData and/or EnvelopedData encapsulates the
encapsulates the response (see section 3.2.1.2 or 3.2.2), the response (see section 3.2.1.2 or 3.2.2), the GL member verifies
GL member verifies the outer signature and/or decrypt the the outer signature and/or decrypt the outer layer prior to
outer layer prior to verifying the signature on the inner most verifying the signature on the inner most SignedData.
SignedData.
2.a - If the signingTime attribute value is not within the locally 2.a - If the signingTime attribute value is not within the locally
accepted time window, the GL member MAY return a response accepted time window, the GL member MAY return a response
indicating cMCStatus.failed and otherInfo.failInfo.badTime indicating cMCStatus.failed and otherInfo.failInfo.badTime
and a signingTime attribute. and a signingTime attribute.
2.b - Else if signature processing continues and if the signatures 2.b - Else if signature processing continues and if the signatures
cannot be verified, the GL member returns a cMCStatusInfoExt cannot be verified, the GL member returns a cMCStatusInfoExt
response indicating cMCStatus.failed and response indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck. Additionally, a otherInfo.failInfo.badMessageCheck. Additionally, a
skipping to change at line 3551 skipping to change at page 73, line 17
includes the GL name in glName, the member name in includes the GL name in glName, the member name in
glMember.glMemberName, their encryption certificate in glMember.glMemberName, their encryption certificate in
glMember.certificates.pKC. The GL member can also include glMember.certificates.pKC. The GL member can 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
attribute certificates in glMember.certificates.certPath. attribute certificates in glMember.certificates.certPath.
Additionally, a signingTime attribute is included with the Additionally, a signingTime attribute is included with the
response. response.
Turner Expires July 2003 67
And Distribution
2.c.1 - The GL member can optionally apply confidentiality to the 2.c.1 - The GL member can optionally apply confidentiality to the
request by encapsulating the SignedData.PKIResponse in an request by encapsulating the SignedData.PKIResponse in an
EnvelopedData (see section 3.2.1.2). If the GL member's EnvelopedData (see section 3.2.1.2). If the GL member's PKC
PKC has been revoked, the GL member ought not use it to has been revoked, the GL member ought not use it to
generate the EnvelopedData that encapsulates the generate the EnvelopedData that encapsulates the
glProvideCert request. glProvideCert request.
2.c.2 - The GL member can also optionally apply another SignedData 2.c.2 - The GL member can 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 glUpdateCert message, the GLO or GLA 3 - Upon receipt of the glUpdateCert message, the GLO or GLA checks
checks the signingTime and verifies the GL member the signingTime and verifies the GL member signature(s). If an
signature(s). If an additional SignedData and/or EnvelopedData additional SignedData and/or EnvelopedData encapsulates the
encapsulates the response (see section 3.2.1.2 or 3.2.2), the response (see section 3.2.1.2 or 3.2.2), the GL member verifies
GL member verifies the outer signature and/or decrypt the the outer signature and/or decrypt the outer layer prior to
outer layer prior to verifying the signature on the inner most verifying the signature on the inner most SignedData.
SignedData.
3.a - If the signingTime attribute value is not within the locally 3.a - If the signingTime attribute value is not within the locally
accepted time window, the GLO or GLA MAY return a response accepted time window, the GLO or GLA MAY return a response
indicating cMCStatus.failed and otherInfo.failInfo.badTime indicating cMCStatus.failed and otherInfo.failInfo.badTime
and a signingTime attribute. and a signingTime attribute.
3.b - Else if signature processing continues and if the signatures 3.b - Else if signature processing continues and if the signatures
cannot be verified, the GLO or GLA returns a cannot be verified, the GLO or GLA returns a
cMCStatusInfoExt response indicating cMCStatus.failed and cMCStatusInfoExt response indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck. Additionally, a otherInfo.failInfo.badMessageCheck. Additionally, a
signingTime attribute is included with the response. signingTime attribute is included with the response.
3.c - Else if the signatures verify, the GLO or GLA verifies the 3.c - Else if the signatures verify, the GLO or GLA verifies the
member's encryption certificate. member's encryption certificate.
3.c.1 - If the member's encryption certificate cannot be verified, 3.c.1 - If the member's encryption certificate cannot be verified,
the GLO returns either another glProvideCert request or a the GLO returns either another glProvideCert request or a
cMCStatusInfoExt with cMCStatus.failed and the reason why cMCStatusInfoExt with cMCStatus.failed and the reason why
in cMCStatus.statusString. glProvideCert should be in cMCStatus.statusString. glProvideCert should be returned
returned only a certain number of times because if the GL only a certain number of times because if the GL member
member does not have a valid certificate they will never does not have a valid certificate they will never be able
be able to return one. Additionally, a signingTime to return one. Additionally, a signingTime attribute is
attribute is included with either response. included with either response.
3.c.2 - Else if the member's encryption certificate cannot be 3.c.2 - Else if the member's encryption certificate cannot be
verified, the GLA returns another glProvideCert request to verified, the GLA returns another glProvideCert request to
the GL member or a cMCStatusInfoExt with cMCStatus.failed the GL member or a cMCStatusInfoExt with cMCStatus.failed
and the reason why in cMCStatus.statusString to the GLO. and the 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.
Additionally, a signingTime attribute is included with the Additionally, a signingTime attribute is included with the
response. response.
Turner Expires July 2003 68
And Distribution
3.c.3 - Else if the member's encryption certificate verifies, the 3.c.3 - Else if the member's encryption certificate verifies, 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
The process for an unsolicited GL member glUpdateCert is as follows: The process for an unsolicited GL member glUpdateCert is as follows:
1 - The GL member sends a 1 - The GL member sends a
Signed.PKIData.controlSequence.glUpdateCert that includes the Signed.PKIData.controlSequence.glUpdateCert that includes the
GL name in glName, the member name in glMember.glMemberName, GL name in glName, the member name in glMember.glMemberName,
their encryption certificate in glMember.certificates.pKC. The their encryption certificate in glMember.certificates.pKC. The
GL member can also include any attribute certificates GL member can also include any attribute certificates
associated with their encryption certificate in associated with their encryption certificate in
glMember.certificates.aC, and the certification path glMember.certificates.aC, and the certification path associated
associated with their encryption and attribute certificates in with their encryption and attribute certificates in
glMember.certificates.certPath. The GL member MUST also glMember.certificates.certPath. The GL member MUST also include
include a signingTime attribute with this request. a signingTime attribute with this request.
1.a - The GL member can optionally apply confidentiality to the 1.a - The GL member can 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 ought not use it to has been revoked, the GLO or GLA ought not use it to
generate the EnvelopedData that encapsulates the generate the EnvelopedData that encapsulates the
glProvideCert request. glProvideCert request.
1.b - The GL member can also optionally apply another SignedData 1.b - The GL member can also optionally apply another SignedData
over the EnvelopedData (see section 3.2.1.2). over the EnvelopedData (see section 3.2.1.2).
skipping to change at line 3659 skipping to change at page 75, line 23
2.b - Else if signature processing continues and if the signatures 2.b - Else if signature processing continues and if the signatures
cannot be verified, the GLA returns a cMCStatusInfoExt cannot be verified, the GLA returns a cMCStatusInfoExt
response indicating cMCStatus.failed and response indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck. otherInfo.failInfo.badMessageCheck.
2.c - Else if the signatures verify, the GLA verifies the member's 2.c - Else if the signatures verify, the GLA verifies the member's
encryption certificate. encryption certificate.
2.c.1 - If the member's encryption certificate cannot be verified, 2.c.1 - If the member's encryption certificate cannot be verified,
the GLA returns another glProvideCert request to the GL the GLA returns another glProvideCert request to the GL
Turner Expires July 2003 69
And Distribution
member or a cMCStatusInfoExt with cMCStatus.failed and the member or a cMCStatusInfoExt with cMCStatus.failed and the
reason why in cMCStatus.statusString to the GLO. reason why in cMCStatus.statusString to the GLO.
glProvideCert ought not be returned indefinitely; if the glProvideCert ought not be returned indefinitely; if the
GL member does not have a valid certificate they will GL member does not have a valid certificate they will never
never be able to return one. Additionally, a signingTime be able to return one. Additionally, a signingTime
attribute is included with the response. attribute is included with the response.
2.c.2 - Else if the member's encryption certificate verifies, the 2.c.2 - Else if the member's encryption certificate verifies, 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 also glKey messages associated with the GL member. The GLA also
forwards the glUpdateCert message to the GLO. forwards 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
after receiving glAddMember, glDeleteMember (for closed and managed receiving glAddMember, glDeleteMember (for closed and managed GLs),
GLs), glRekey, glkCompromise, or glkRefresh requests and returning a glRekey, glkCompromise, or glkRefresh requests and returning a
cMCStatusInfoExt response for the respective request. Figure 12 cMCStatusInfoExt response for the respective request. Figure 12
depicts the protocol interactions to send out glKey messages. Unlike depicts the protocol interactions to send out glKey messages. Unlike
the procedures defined for the administrative messages, the the procedures defined for the administrative messages, the
procedures defined in this section MUST be implemented by GLAs for procedures defined in this section MUST be implemented by GLAs for
origination and by GL members on reception. Note that error messages origination and by GL members on reception. Note that error messages
are not shown. Additionally, behavior for the optional are not shown. Additionally, behavior for the optional transactionId,
transactionId, senderNonce, and recipientNonce CMC control senderNonce, and recipientNonce CMC control attributes is not
attributes is not addressed in these procedures. addressed in these procedures.
1 +----------+ 1 +----------+
+-------> | Member 1 | +-------> | Member 1 |
| +----------+ | +----------+
+-----+ | 1 +----------+ +-----+ | 1 +----------+
| GLA | ----+-------> | ... | | GLA | ----+-------> | ... |
+-----+ | +----------+ +-----+ | +----------+
| 1 +----------+ | 1 +----------+
+-------> | Member n | +-------> | Member n |
+----------+ +----------+
skipping to change at line 3708 skipping to change at page 76, line 24
Figure 12 - GL Key Distribution Figure 12 - GL Key Distribution
If the GL was setup with GLKeyAttributes.recipientsNotMutuallyAware If the GL was setup with GLKeyAttributes.recipientsNotMutuallyAware
set to TRUE, a separate glKey message MUST be sent to each GL member set to TRUE, a separate glKey message MUST be sent to each GL member
so as to not divulge information about the other GL members. 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,
- glDeleteMember request with the GL's glAdministration set to - glDeleteMember request with the GL's glAdministration set to
managed or closed, and managed or closed, and
- glRekey request with generationCounter set to zero (0).
Turner Expires July 2003 70 - glRekey request with generationCounter set to zero (0).
And Distribution
The GLA MUST use either the kari (see section 12.3.2 of [CMS]) or The GLA MUST use either the kari (see section 12.3.2 of [CMS]) or
ktri (see section 12.3.1 of [CMS]) choice in ktri (see section 12.3.1 of [CMS]) choice in
glKey.glkWrapped.RecipientInfo to ensure only the intended glKey.glkWrapped.RecipientInfo to ensure only the intended recipients
recipients receive the shared KEK. The GLA MUST support the ktri receive the shared KEK. The GLA MUST support the ktri choice.
choice.
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
controls rekeys, the GLA MAY use the kari, ktri, or kekri (see rekeys, the GLA MAY use the kari, ktri, or kekri (see section 12.3.3
section 12.3.3 of [CMS]) in glKey.glkWrapped.RecipientInfo to ensure of [CMS]) in glKey.glkWrapped.RecipientInfo to ensure only the
only the intended recipients receive the shared KEK. The GLA MUST intended recipients receive the shared KEK. The GLA MUST support the
support the RecipientInfo.ktri choice. 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:
1 - The GLA MUST send a SignedData.PKIData.controlSequence.glKey 1 - The GLA MUST send a SignedData.PKIData.controlSequence.glKey to
to each member by including: glName, glIdentifier, glkWrapped, each member by including: glName, glIdentifier, glkWrapped,
glkAlgorithm, glkNotBefore, and glkNotAfter. If the GLA can glkAlgorithm, glkNotBefore, and glkNotAfter. If the GLA can not
not generate a glKey message for the GL member because the GL generate a glKey message for the GL member because the GL
member's PKC has expired or is otherwise invalid, the GLA MAY member's PKC has expired or is otherwise invalid, the GLA MAY
send a glUpdateCert to the GL member requesting a new send a glUpdateCert to the GL member requesting a new
certificate be provided (see section 4.10). The number of certificate be provided (see section 4.10). The number of glKey
glKey messages generated for the GL is described in section messages generated for the GL is described in section 3.1.16.
3.1.16. Additionally, a signingTime attribute is included with Additionally, a signingTime attribute is included with the
the distribution message(s). distribution message(s).
1.a - The GLA MAY optionally apply another confidentiality layer 1.a - The GLA MAY optionally apply another confidentiality layer to
to the message by encapsulating the SignedData.PKIData in 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
the EnvelopedData.SignedData.PKIData (see section 3.2.1.2). EnvelopedData.SignedData.PKIData (see section 3.2.1.2).
2 - Upon receipt of the glKey message, the GL members MUST check 2 - Upon receipt of the glKey message, the GL members MUST check
the signingTime and verify the signature over the inner most the signingTime and verify the signature over the inner most
SignedData.PKIData. If an additional SignedData and/or SignedData.PKIData. If an additional SignedData and/or
EnvelopedData encapsulates the message (see section 3.2.1.2 or EnvelopedData encapsulates the message (see section 3.2.1.2 or
3.2.2), the GL Member MUST verify the outer signature and/or 3.2.2), the GL Member 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
the SignedData.PKIData.controlSequence.glKey. SignedData.PKIData.controlSequence.glKey.
2.a - If the signingTime attribute value is not within the locally 2.a - If the signingTime attribute value is not within the locally
accepted time window, the GLA MAY return a response accepted time window, the GLA MAY return a response
indicating cMCStatus.failed and otherInfo.failInfo.badTime indicating cMCStatus.failed and otherInfo.failInfo.badTime
and a signingTime attribute. and a signingTime attribute.
2.b - Else if signature processing continues and if the signatures 2.b - Else if signature processing continues and if the signatures
cannot be verified, the GL member MUST return a cannot be verified, the GL member MUST return a
Turner Expires July 2003 71
And Distribution
cMCStatusInfoExt response indicating cMCStatus.failed and cMCStatusInfoExt response indicating cMCStatus.failed and
otherInfo.failInfo.badMessageCheck. Additionally, a otherInfo.failInfo.badMessageCheck. Additionally, a
signingTime attribute is included with the response. signingTime attribute is included with the response.
2.c - Else if the signatures verify, the GL member process the 2.c - Else if the signatures verify, the GL member process the
RecipientInfos according to [CMS]. Once unwrapped the GL RecipientInfos according to [CMS]. Once unwrapped the GL
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. Additionally, the GL member MUST return a associated. Additionally, the GL member MUST return a
cMCStatusInfoExt indicating cMCStatus.success to tell the cMCStatusInfoExt indicating cMCStatus.success to tell the
GLA the KEK was received. GLA the KEK was 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.
Further algorithms MAY also be implemented. Further algorithms MAY also be implemented.
6.1 KEK Generation Algorithm 6.1. KEK Generation Algorithm
Implementations MUST randomly generate content-encryption keys, Implementations MUST randomly generate content-encryption keys,
message-authentication keys, initialization vectors (IVs), and message-authentication keys, initialization vectors (IVs), and
padding. Also, the generation of public/private key pairs relies on padding. Also, the generation of public/private key pairs relies on a
a random numbers. The use of inadequate pseudo-random number random numbers. The use of inadequate pseudo-random number generators
generators (PRNGs) to generate cryptographic keys can result in (PRNGs) to generate cryptographic keys can result in little or no
little or no security. An attacker may find it much easier to security. An attacker may find it much easier to reproduce the PRNG
reproduce the PRNG environment that produced the keys, searching the environment that produced the keys, searching the resulting small set
resulting small set of possibilities, rather than brute force of possibilities, rather than brute force searching the whole key
searching the whole key space. The generation of quality random space. The generation of quality random numbers is difficult. RFC
numbers is difficult. RFC 1750 [RANDOM] offers important guidance 1750 [RANDOM] offers important guidance in this area, and Appendix 3
in this area, and Appendix 3 of FIPS Pub 186 [FIPS] provides one of FIPS Pub 186 [FIPS] provides one quality PRNG technique.
quality PRNG technique.
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 an AES 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 specified
The algorithm object identifiers included in glkWrapped are as in [CMSALG] and [CMSAES].
specified in AlgSpec [CMSALG].
6.3 Shared KEK Algorithm
The shared KEK distributed and indicated in glkAlgorithm MUST 6.3. Shared KEK Algorithm
support the symmetric key-encryption algorithms as specified in
section AlgSpec [CMSALG].
Turner Expires July 2003 72 The shared KEK distributed and indicated in glkAlgorithm MUST support
And Distribution the symmetric key-encryption algorithms as specified in section
[CMSALG] and [CMSAES].
7 Message Transport 7. Message Transport
SMTP [SMTP] MUST be supported. Other transport mechanisms MAY also SMTP [SMTP] MUST be supported. Other transport mechanisms MAY also be
be supported. supported.
8 Security Considerations 8. Security Considerations
As GLOs control setting up and tearing down the GL, rekeying the GL, As GLOs control setting up and tearing down the GL, rekeying the GL,
and can control member additions and deletions, GLOs play an and can control member additions and deletions, GLOs play an
important role in the management of the GL, and only "trusted" GLOs important role in the management of the GL, and only "trusted" GLOs
should be used. should be used.
If a member is deleted or removed from a closed or a managed GL, the If a member is deleted or removed from a closed or a managed GL, the
GL needs to be rekeyed. If the GL is not rekeyed after a member is GL needs to be rekeyed. If the GL is not rekeyed after a member is
removed or deleted, the member still posses the group key and will removed or deleted, the member still posses the group key and will be
be able to continue to decrypt any messages that can be obtained. able to continue to decrypt any messages that can be obtained.
Members who store KEKs MUST associate the name of the GLA that Members who store KEKs MUST associate the name of the GLA that
distributed the key so that the members can make sure subsequent distributed the key so that the members can make sure subsequent
rekeys are originated from the same entity. rekeys are originated from the same entity.
When generating keys, care should be taken to ensure that the key When generating keys, care should be taken to ensure that the key
size is not too small and duration too long because attackers will size is not too small and duration too long because attackers will
have more time to attack the key. Key size should be selected to have more time to attack the key. Key size should be selected to
adequately protect sensitive business communications. adequately protect sensitive business communications.
GLOs and GLAs need to make sure that the generationCounter and GLOs and GLAs need to make sure that the generationCounter and
duration are not too large. For example, if the GLO indicates that duration are not too large. For example, if the GLO indicates that
the generationCounter is 14 and the duration is one year, then 14 the generationCounter is 14 and the duration is one year, then 14
keys are generated each with a validity period of a year. An keys are generated each with a validity period of a year. An attacker
attacker will have at least 13 years to attack the final key. will have at least 13 years to attack the final key.
Assume that two or more parties have a shared KEK, and the shared Assume that two or more parties have a shared KEK, and the shared KEK
KEK is used to encrypt a second KEK for confidential distribution to is used to encrypt a second KEK for confidential distribution to
those parties. The second KEK might be used to encrypt a third KEK; 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 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 any of the KEKs in such a chain is compromised, all of the subsequent
subsequent KEKs in the chain MUST also be considered compromised. KEKs in the chain MUST also be considered compromised.
An attacker can attack the group's shared KEK by attacking one An attacker can attack the group's shared KEK by attacking one
member's copy of the shared KEK or attacking multiple member's member's copy of the shared KEK or attacking multiple member's copies
copies of the shared KEK. For the attacker it may be easier to of the shared KEK. For the attacker it may be easier to either attack
either attack the group member with the weakest security protecting the group member with the weakest security protecting their copy of
their copy of the shared KEK or by attacking multiple group members. the shared KEK or by attacking multiple group members.
An aggregation of the information gathered during the attack(s) may An aggregation of the information gathered during the attack(s) may
lead to the compromise of the group's shared KEK. Mechanisms to lead to the compromise of the group's shared KEK. Mechanisms to
protect the shared KEK should be commensurate with value of the data protect the shared KEK should be commensurate with value of the data
being protected. being protected.
Turner Expires July 2003 73
And Distribution
The nonce and signingTime attributes are used to protect against The nonce and signingTime attributes are used to protect against
replay attacks. However, these provisions are only helpful if replay attacks. However, these provisions are only helpful if
entities maintain state information about the messages they have entities maintain state information about the messages they have sent
sent or received for comparison. If sufficient information is not or received for comparison. If sufficient information is not
maintained on each exchange, nonces and signingTime are not helpful. maintained on each exchange, nonces and signingTime are not helpful.
Local policy determines the amount and duration of state information Local policy determines the amount and duration of state information
that is maintained. Additionally, without a unified time source, that is maintained. Additionally, without a unified time source,
there is the possibility of clocks drifting. Local policy determines there is the possibility of clocks drifting. Local policy determines
the acceptable difference between the local time and signingTime, the acceptable difference between the local time and signingTime,
which must compensate for unsynchronized clock. Implementations MUST which must compensate for unsynchronized clock. Implementations MUST
handle messages with siginingTime attributes that indicate they were handle messages with siginingTime attributes that indicate they were
created in the future. created in the future.
9 References 9. IANA Considerations
9.1 Informative None: All identifiers are already registered. Please remove this
section prior to publication as an RFC.
[STDWORDS] Bradner, S., "Key words for use in RFCs to Indicate 10. Acknowledgements
Requirement Levels", BCP 14, RFC 2119, March 1997.
[X400TRANS] Hoffman, P., and C. Bonatti, "Transporting S/MIME Thanks to Russ Housley and Jim Schaad for providing much of the
Objects in X.400", draft-ietf-smime-x400transport-05.txt, November background and review required to write this document.
2002.
[RANDOM] Eastlake, D., Crocker, S. and J. Schiller, "Randomness 11. References
Recommendations for Security", RFC 1750, December 1994.
[FIPS] National Institute of Standards and Technology. FIPS Pub 186: 11.1. Normative References
Digital Signature Standard. 19 May 1994.
9.1 Normative [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[CMS] Housley, R., "Cryptographic Message Syntax," RFC 3369, August [CMS] Housley, R., "Cryptographic Message Syntax," RFC 3852,
2002. July 2004.
[CMC] Myers, M., Liu, X., Schaad, J., Weinsten, J., "Certificate [CMC] Myers, M., Liu, X., Schaad, J., Weinsten, J.,
Management Message over CMS," draft-ietf-pkix-2797-bis-00.txt, April "Certificate Management Message over CMS," work-in-
2001. progress, December 2007.
[PROFILE] Housley, R., Ford, W., Polk, W. and D. Solo, "Internet [PROFILE] Housley, R., Ford, W., Polk, W. and D. Solo, "Internet
X.509 Public Key Infrastructure: Certificate and CRL Profile", RFC X.509 Public Key Infrastructure: Certificate and CRL
3280, April 2002. Profile", RFC 3280, April 2002.
[ACPROF] Farrell, S., Housley, R., "An Internet Attribute [ACPROF] Farrell, S., Housley, R., "An Internet Attribute
Certificate Profile for Authorization", RFC 3281, April 2002. Certificate Profile for Authorization", RFC 3281, April
2002.
[MSG] Ramsdale, B., "S/MIME Version 3 Message Specification," RFC
2633, June 1999.
Turner Expires July 2003 74 [MSG] Ramsdale, B., "S/MIME Version 3.1 Message Specification,"
And Distribution RFC 3851, July 2004.
[ESS] Hoffman, P., "Extended Security Services for S/MIME", RFC [ESS] Hoffman, P., "Extended Security Services for S/MIME", RFC
2634, June 1999. 2634, June 1999.
[CMSALG] 11 Housley, R., "Cryptographic Message Syntax (CMS) Schaad, J., "Extended Security Services (ESS) Update:
Adding CertID Algorithm Agility", RFC 5035, August 2007.
[CMSALG] Housley, R., "Cryptographic Message Syntax (CMS)
Algorithms", RFC 3370, August 2002. Algorithms", RFC 3370, August 2002.
[SMTP] Postel, j., "Simple Mail Transport Protocol," RFC 821, August [CMSAES] Schaad, J., "Advanced Encryption Standard (AES) Encryption
1982. Algorithm in Cryptographic Message Syntax (CMS) ", RFC
3565, July 2003.
10 Acknowledgements [SMTP] Klensin, J., "Simple Mail Transport Protocol," RFC 2821,
April 2001.
Thanks to Russ Housley and Jim Schaad for providing much of the 11.2. Informative References
background and review required to write this document.
11 Author's Addresses [X400TRANS] Hoffman, P., and C. Bonatti, "Transporting S/MIME Objects
in X.400", RFC 3855, July 2004.
Sean Turner [RANDOM] Eastlake, D., Crocker, S. and J. Schiller, "Randomness
IECA, Inc. Recommendations for Security", RFC 4086, June 2005.
Phone: +1.703.628.3180
Email: turners@ieca.com
Turner Expires July 2003 75 [FIPS] National Institute of Standards and Technology. FIPS Pub
And Distribution 186-2: Digital Signature Standard. 27 January 2000.
Annex A: ASN.1 Module 12. ASN.1 Module
SMIMESymmetricKeyDistribution SMIMESymmetricKeyDistribution
{ iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9) { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)
smime(16) modules(0) symkeydist(12) } 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
-- PKIX Part 1 - Implicit -- PKIX Part 1 - Implicit
skipping to change at line 3968 skipping to change at page 81, line 45
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
-- 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(19)} id-pkix1-implicit(19)}
-- PKIX Part 1 - Explicit -- PKIX Part 1 - Explicit
AlgorithmIdentifier, Certificate AlgorithmIdentifier, Certificate
FROM PKIX1Explicit88 { iso(1) identified-organization(3) dod(6) FROM PKIX1Explicit88 { 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-explicit(18) } id-pkix1-explicit(18) }
-- Cryptographic Message Syntax -- Cryptographic Message Syntax
RecipientInfos, id-alg-CMS3DESwrap, KEKIdentifier,
CertificateSet RecipientInfos, KEKIdentifier, CertificateSet
FROM CryptographicMessageSyntax {iso(1) member-body(2) us(840)
FROM CryptographicMessageSyntax2004 {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-2001(14)} cms-2004(24) }
-- Advanced Encryption Standard (AES) with CMS
id-aes128-wrap
FROM CMSAesRsaesOaep { iso(1) member-body(2) us(840) rsadsi(113549)
pkcs(1) pkcs-9(9) smime(16) modules(0) id-mod-cms-aes(19) }
-- Attribute Certificate Profile -- Attribute Certificate Profile
AttributeCertificate FROM
PKIXAttributeCertificate { iso(1) identified-organization(3) AttributeCertificate
dod(6) internet(1) security(5) mechanisms(5) pkix(7)
id-mod(0) id-mod-attribute-cert(12)}; 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 -- This defines the GL symmetric key distribution object identifier
-- arc. -- arc.
id-skd OBJECT IDENTIFIER ::= { iso(1) member-body(2) us(840) id-skd OBJECT IDENTIFIER ::= { iso(1) member-body(2) us(840)
rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) skd(8) } 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 Expires July 2003 76
And Distribution
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 } certificates Certificates OPTIONAL }
GLAdministration ::= INTEGER { GLAdministration ::= INTEGER {
skipping to change at line 4031 skipping to change at page 83, line 24
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 DEFAULT 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-aes128-wrap } }
-- 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}
DeleteGL ::= GeneralName DeleteGL ::= GeneralName
-- 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 Expires July 2003 77
And Distribution
Certificates ::= SEQUENCE { Certificates ::= SEQUENCE {
pKC [0] Certificate OPTIONAL, pKC [0] Certificate OPTIONAL,
-- See [PROFILE] -- See [PROFILE]
aC [1] SEQUENCE SIZE (1.. MAX) OF aC [1] SEQUENCE SIZE (1.. MAX) OF
AttributeCertificate OPTIONAL, AttributeCertificate OPTIONAL,
-- See [ACPROF] -- See [ACPROF]
certPath [2] CertificateSet OPTIONAL } certPath [2] CertificateSet OPTIONAL }
-- From [CMS] -- From [CMS]
-- This defines the Delete GL Member control attribute -- This defines the Delete GL Member control attribute
skipping to change at line 4106 skipping to change at page 85, line 9
glName GeneralName, glName GeneralName,
glOwnerInfo GLOwnerInfo } glOwnerInfo GLOwnerInfo }
-- 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}
GLKCompromise ::= GeneralName GLKCompromise ::= GeneralName
Turner Expires July 2003 78
And Distribution
-- 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 ::= SEQUENCE { GLKRefresh ::= SEQUENCE {
glName GeneralName, glName GeneralName,
dates SEQUENCE SIZE (1..MAX) OF Date } dates SEQUENCE SIZE (1..MAX) OF Date }
Date ::= SEQUENCE { Date ::= SEQUENCE {
start GeneralizedTime, start GeneralizedTime,
skipping to change at line 4140 skipping to change at page 85, line 40
id-skd-glaQueryResponse OBJECT IDENTIFIER ::= { id-skd 12} 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 -- This defines the GLA Request/Response (glaRR) arc for
-- glaRequestType/glaResponseType. -- glaRequestType/glaResponseType.
id-cmc-glaRR OBJECT IDENTIFIER ::= { iso(1) identified- id-cmc-glaRR OBJECT IDENTIFIER ::= {
organization(3) dod(6) internet(1) security(5) mechanisms(5) pkix(7) iso(1) identified-organization(3) dod(6) internet(1) security(5)
cmc(7) glaRR(99) } mechanisms(5) pkix(7) cmc(7) glaRR(99) }
-- This defines the Algorithm Request -- This defines the Algorithm Request
id-cmc-gla-skdAlgRequest OBJECT IDENTIFIER ::= { id-cmc-glaRR 1 } id-cmc-gla-skdAlgRequest OBJECT IDENTIFIER ::= { id-cmc-glaRR 1 }
SKDAlgRequest ::= NULL SKDAlgRequest ::= NULL
-- This defines the Algorithm Response -- This defines the Algorithm Response
id-cmc-gla-skdAlgResponse OBJECT IDENTIFIER ::= { id-cmc-glaRR 2 } 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 [MSG]. -- smimeCapabilities attribute as defined in MsgSpec [MSG].
Turner Expires July 2003 79
And Distribution
-- 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 13} id-skd-glProvideCert OBJECT IDENTIFIER ::= { id-skd 13}
GLManageCert ::= SEQUENCE { GLManageCert ::= SEQUENCE {
glName GeneralName, glName GeneralName,
glMember GLMember } glMember GLMember }
-- This defines the control attribute to return an updated -- This defines the control attribute to return an updated
skipping to change at line 4187 skipping to change at page 86, line 35
id-skd-glKey OBJECT IDENTIFIER ::= { id-skd 15} id-skd-glKey OBJECT IDENTIFIER ::= { id-skd 15}
GLKey ::= SEQUENCE { GLKey ::= SEQUENCE {
glName GeneralName, glName GeneralName,
glIdentifier KEKIdentifier, -- See [CMS] glIdentifier KEKIdentifier, -- See [CMS]
glkWrapped RecipientInfos, -- See [CMS] glkWrapped RecipientInfos, -- See [CMS]
glkAlgorithm AlgorithmIdentifier, glkAlgorithm AlgorithmIdentifier,
glkNotBefore GeneralizedTime, glkNotBefore GeneralizedTime,
glkNotAfter GeneralizedTime } glkNotAfter GeneralizedTime }
Turner Expires July 2003 80
And Distribution
-- This defines the CMC error types -- This defines the CMC error types
id-cet-skdFailInfo OBJECT IDENTIFIER ::= { iso(1) id-cet-skdFailInfo OBJECT IDENTIFIER ::= {
identified-organization(3) dod(6) internet(1) security(5) iso(1) identified-organization(3) dod(6) internet(1) security(5)
mechanisms(5) pkix(7) cet(15) skdFailInfo(1) } mechanisms(5) pkix(7) cet(15) skdFailInfo(1) }
SKDFailInfo ::= INTEGER { SKDFailInfo ::= INTEGER {
unspecified (0), unspecified (0),
closedGL (1), closedGL (1),
unsupportedDuration (2), unsupportedDuration (2),
noGLACertificate (3), noGLACertificate (3),
invalidCert (4), invalidCert (4),
unsupportedAlgorithm (5), unsupportedAlgorithm (5),
noGLONameMatch (6), noGLONameMatch (6),
invalidGLName (7), invalidGLName (7),
nameAlreadyInUse (8), nameAlreadyInUse (8),
skipping to change at line 4215 skipping to change at page 88, line 5
nameAlreadyInUse (8), nameAlreadyInUse (8),
noSpam (9), noSpam (9),
deniedAccess (10), deniedAccess (10),
alreadyAMember (11), alreadyAMember (11),
notAMember (12), notAMember (12),
alreadyAnOwner (13), alreadyAnOwner (13),
notAnOwner (14) } notAnOwner (14) }
END -- SMIMESymmetricKeyDistribution END -- SMIMESymmetricKeyDistribution
Turner Expires July 2003 81 Author's Addresses
Sean Turner
IECA, Inc.
3057 Nutley Street, Suite 106
Fairfax, VA 22031
USA
Email: turners@ieca.com
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 386 change blocks. 
1292 lines changed or deleted 1017 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/