2.7.9 Multicast Security (msec)

NOTE: This charter is a snapshot of the 65th IETF Meeting in Dallas, TX USA. It may now be out-of-date.

Last Modified: 2006-01-12

Chair(s):

Ran Canetti <canetti@watson.ibm.com>
Lakshminath Dondeti <ldondeti@qualcomm.com>

Security Area Director(s):

Russ Housley <housley@vigilsec.com>
Sam Hartman <hartmans-ietf@mit.edu>

Security Area Advisor:

Russ Housley <housley@vigilsec.com>

Mailing Lists:

General Discussion: msec@securemulticast.org
To Subscribe: msec-request@securemulticast.org
In Body: subscribe
Archive: http://six.pairlist.net/pipermail/msec/

Description of Working Group:

The purpose of the MSEC WG is to standardize protocols for securing
group communication over internets, and in particular over the global
Internet. Initial efforts will focus on scalable solutions for groups
with a single source and a very large number of recipients. Additional
emphasis will be put on groups where the data is transmitted via
IP-layer multicast routing protocols (with or without guaranteed
reliability). The developed standard will assume that each group has a
single trusted entity (the Group Controller) that sets the security
policy and controls the group membership. The standard will strive
to provide at least the following basic security guarantees:

+ Only legitimate group members will have access to current group
communication. This includes groups with highly dynamic membership.

+ Legitimate group members will be able to authenticate the source
and contents of the group communication. This includes cases where
group members do not trust each other.

An additional goal of the standard will be to protect against
denial-of-service attacks, whenever possible.

Due to the large number of one-to-many multicast applications and the
sometimes conflicting requirements these applications exhibit, it is
believed that a single protocol will be unable to meet the requirements
of all applications. Therefore, the WG will first specify a general
Reference Framework that includes a number of functional building
blocks. Each such building block will be instantiated by one or more
protocols that will be interchanable. The Reference Framework will not
only describe one-to-many multicast, but also many-to-many multicast.

In addition, as a secondary goal the MSEC WG will also focus on
distributed architectures for group key management and group policy
management, where for scalability purposes multiple trusted entities
(such as Key Distributors) are deployed in a distributed fashion. For
this purpose, the Reference Framework will not only describe
one-to-many multicast, but also many-to-many multicast.

MSEC will generate at least the following documents, which could be
considered as base documents:

1. An RFC describing the security requirements of multicast security
and
an RFC describing the MSEC Architecture.

2. An RFC describing the Group Key Management Architecture and an RFC
describing Group Policy Management Architecture in MSEC.

3. Several RFCs describing specifications for protocols that implement
source authentication, group key management and group policy
management.
As multicast security covers a broad range of issues, and therefore
touches other Working Groups in the IETF, the MSEC WG will work closely
with othersecurity-related Working Groups (e.g. IPsec, IPSP), as well
as other Working Groups which maybe considered a 'consumer' of the
technologies produced in the MSEC WG (e.g. AVT, MMUSIC) or which may
have a multicast focus (e.g. PIM, RMT, IDRM, MAGMA).

With this in mind, the MSEC WG is open to receiving new work items,
whenever it is considered appropriate to be homed in the MSEC WG. Such
drafts will be matured in conjunction with the MSEC base documents.

Goals and Milestones:

Done  Working Group Last Call on GDOI Protocol
Done  Working Group Last Call on MIKEY Protocol
Done  WG Last Call on MSEC Architecture draft
Done  WG Last Call on Group Key Management Architecture
Done  WG Last Call on DHHMAC for MIKEY
Done  WG Last Call on MSEC Security Requirements draft
Done  WG Last Call on GSAKMP
Done  WG Last Call on MSEC Policy Token
Done  WG Last call on TESLA-Intro draft
Done  WG Last call on Use of RSA/SHA-1 Signatures within ESP and AH
Done  WG Last Call on The Use of TESLA in SRTP
Done  WG Last Call on Bootstrapping TESLA
Jan 2006  WG Last Call on MIKEY-RSA-R
Feb 2006  WG Last Call on MIKEY-ECC
May 2006  WG Last Call on Multicast Extensions to IPsec
Jul 2006  WG Last Call on GKDP
Aug 2006  WG Last Call on TESLA-Spec
Sep 2006  WG re-charter for other work items or disband

Internet-Drafts:

  • draft-ietf-msec-gsakmp-sec-10.txt
  • draft-ietf-msec-mikey-dhhmac-11.txt
  • draft-ietf-msec-policy-token-sec-06.txt
  • draft-ietf-msec-newtype-keyid-05.txt
  • draft-ietf-msec-bootstrapping-tesla-03.txt
  • draft-ietf-msec-mikey-ecc-00.txt
  • draft-ietf-msec-mikey-rsa-r-02.txt
  • draft-ietf-msec-ipsec-extensions-01.txt
  • draft-ietf-msec-gkdp-01.txt

    Request For Comments:

    RFCStatusTitle
    RFC3547 PS The Group Domain of Interpretation
    RFC3740 I The Multicast Security Architecture
    RFC3830 Standard MIKEY: Multimedia Internet KEYing
    RFC4046 I Multicast Security (MSEC) Group Key Management Architecture
    RFC4082 I Timed Efficient Stream Loss-Tolerant Authentication (TESLA): Multicast Source Authentication Transform Introduction
    RFC4359 Standard The Use of RSA/SHA-1 Signatures within Encapsulating Security Payload (ESP) and Authentication Header (AH)
    RFC4383 Standard The Use of Timed Efficient Stream Loss-Tolerant Authentication (TESLA) in the Secure Real-time Transport Protocol (SRTP)

    Meeting Minutes


    Slides

    MSEC Status
    GDOI Update
    GKDP Rekeying
    MSEC IPsec extensions
    On the applicability of MIKEY modes and extensions
    MIKEY-SAML
    SRTP-EKT
    TESLA for ALC and NORM