draft-ietf-avtcore-srtp-aes-gcm-08.txt   draft-ietf-avtcore-srtp-aes-gcm-09.txt 
Network Working Group D. McGrew Network Working Group D. McGrew
Internet Draft Cisco Systems, Inc. Internet Draft Cisco Systems, Inc.
Intended Status: Standards Track K. Igoe Intended Status: Standards Track K. Igoe
Expires: February 27, 2014 National Security Agency Expires: March 03, 2014 National Security Agency
August 26, 2013 August 30, 2013
AES-GCM and AES-CCM Authenticated Encryption in Secure RTP (SRTP) AES-GCM and AES-CCM Authenticated Encryption in Secure RTP (SRTP)
draft-ietf-avtcore-srtp-aes-gcm-08 draft-ietf-avtcore-srtp-aes-gcm-09
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current. Drafts is at http://datatracker.ietf.org/drafts/current.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents 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."
This Internet-Draft will expire on February 27, 2014. This Internet-Draft will expire on March 03, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 23, line 46 skipping to change at page 23, line 46
| 16 | 2^98 tries | 2^108 tries | 2^118 tries | | 16 | 2^98 tries | 2^108 tries | 2^118 tries |
+=================+============+=============+==============+ +=================+============+=============+==============+
Table 15: Probability of a compromise occurring for a given Table 15: Probability of a compromise occurring for a given
number of forgery attempts and tag size. number of forgery attempts and tag size.
15. IANA Considerations 15. IANA Considerations
15.1. SDES 15.1. SDES
Session description [RFC4568] defines SRTP "crypto suites". A crypto SDP Security Descriptions [RFC4568] defines SRTP "crypto suites". A
suite corresponds to a particular AEAD algorithm in SRTP. In order crypto suite corresponds to a particular AEAD algorithm in SRTP. In
to allow SDP to signal the use of the algorithms defined in this order to allow SDP to signal the use of the algorithms defined in
document, IANA will register the following crypto suites into the this document, IANA will register the following crypto suites into
subregistry for SRTP crypto suites under Session Description Protocol the "SRTP Crypto Suite Registrations" subregistry of the "Session
(SDP) Parameters: Description Protocol (SDP) Parameters" registry.
srtp-crypto-suite-ext = "AEAD_AES_128_GCM" / srtp-crypto-suite-ext = "AEAD_AES_128_GCM" /
"AEAD_AES_256_GCM" / "AEAD_AES_256_GCM" /
"AEAD_AES_128_GCM_8" / "AEAD_AES_128_GCM_8" /
"AEAD_AES_256_GCM_8" / "AEAD_AES_256_GCM_8" /
"AEAD_AES_128_GCM_12" / "AEAD_AES_128_GCM_12" /
"AEAD_AES_256_GCM_12" / "AEAD_AES_256_GCM_12" /
"AEAD_AES_128_CCM" / "AEAD_AES_128_CCM" /
"AEAD_AES_256_CCM" / "AEAD_AES_256_CCM" /
"AEAD_AES_128_CCM_8" / "AEAD_AES_128_CCM_8" /
skipping to change at page 27, line 33 skipping to change at page 27, line 33
auth_function, auth_key_length, or auth_tag_length because all of auth_function, auth_key_length, or auth_tag_length because all of
these profiles use AEAD algorithms, and thus do not use a separate these profiles use AEAD algorithms, and thus do not use a separate
auth_function, auth_key, or auth_tag. The term aead_auth_tag_length auth_function, auth_key, or auth_tag. The term aead_auth_tag_length
is used to emphasize that this refers to the authentication tag is used to emphasize that this refers to the authentication tag
provided by the AEAD algorithm and that this tag is not located in provided by the AEAD algorithm and that this tag is not located in
the authentication tag field provided by SRTP/SRTCP. the authentication tag field provided by SRTP/SRTCP.
15.3. MIKEY 15.3. MIKEY
In accordance with "MIKEY: Multimedia Internet KEYing" [RFC3830], In accordance with "MIKEY: Multimedia Internet KEYing" [RFC3830],
IANA maintains several Payload Name Spaces under Multimedia Internet IANA maintains several subregitries under "Multimedia Internet KEYing
KEYing (MIKEY). This document requires additions to two of the lists (MIKEY) Payload Name Spaces". This document requires additions to
maintained under MIKEY Security Protocol Parameters. two of the MIKEY subregistries. lists maintained under "MIKEY
Security Protocol Parameters".
On the SRTP policy Type/Value list (derived from Table 6.10.1.a of In the "MIKEY Security Protocol Parameters" subregistry we request
[RFC3830]) we request the following addition: the following addition:
Type | Meaning | Possible values Type | Meaning | Possible values
---------------------------------------------------------------- ----------------------------------------------------------------
TBD | AEAD authentication tag length | 8, 12, or 16 (in octets) TBD | AEAD authentication tag length | 8, 12, or 16 (in octets)
On the Encryption Algorithm List (derived from Table 6.10.1.b of In the "Encryption Algorithm" subregistry (derived from Table
[RFC3830]) we request the following additions: 6.10.1.b of [RFC3830]) we request the following additions:
SRTP encr alg. | Value | Default Session Encr. Key Length SRTP encr alg. | Value | Default Session Encr. Key Length
----------------------------------------------------------- -----------------------------------------------------------
AES-CCM | TBD | 16 octets AES-CCM | TBD | 16 octets
AES-GCM | TBD | 16 octets AES-GCM | TBD | 16 octets
The SRTP encryption algorithm, session encryption key length, and The SRTP encryption algorithm, session encryption key length, and
AEAD authentication tag values received from MIKEY fully determine AEAD authentication tag values received from MIKEY fully determine
the AEAD algorithm (e.g., AEAD_AES_256_GCM_8). The exact mapping is the AEAD algorithm (e.g., AEAD_AES_256_GCM_8). The exact mapping is
described in section 16. described in section 16.
15.4. AEAD registry 15.4. AEAD registry
We request that IANA make the following additions to the AEAD We request that IANA make the following additions to the IANA
registry: "Authenticated Encryption with Associated Data (AEAD) Parameters"
page's registry for "AEAD Algorithms":
AEAD_AES_128_CCM_12 = TBD AEAD_AES_128_CCM_12 = TBD
AEAD_AES_256_CCM_12 = TBD AEAD_AES_256_CCM_12 = TBD
16. Parameters for use with MIKEY 16. Parameters for use with MIKEY
MIKEY specifies the algorithm family separately from the key length MIKEY specifies the algorithm family separately from the key length
(which is specified by the Session Encryption key length ) and the (which is specified by the Session Encryption key length ) and the
authentication tag length (specified by AEAD Auth. tag length). authentication tag length (specified by AEAD Auth. tag length).
 End of changes. 8 change blocks. 
19 lines changed or deleted 21 lines changed or added

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