The use of AES-192 and AES-256 in Secure RTP
draft-ietf-avt-srtp-big-aes-01.txt

Status of this Memo

This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work in progress.”

The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt.

The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html.

This Internet-Draft will expire on January 7, 2010.

Copyright Notice

Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document.

Abstract

This memo describes the use of the Advanced Encryption Standard (AES) with 192 and 256 bit keys within the Secure RTP protocol. It defines Counter Mode encryption for SRTP and SRTCP and a new SRTP Key Derivation Function (KDF) for AES-192 and AES-256.

Table of Contents

1.  Introduction
    1.1.  Conventions Used In This Document
2.  AES-192 and AES-256 Encryption
3.  The AES_192_CM_PRF and AES_256_CM_PRF Key Derivation Functions
    3.1.  Usage Requirements
4.  Crypto Suties
5.  IANA Considerations
6.  Security Considerations
7.  Test Cases
    7.1.  AES-256-CM Test Cases
    7.2.  AES_256_CM_PRF Test Cases
    7.3.  AES-192-CM Test Cases
    7.4.  AES_192_CM_PRF Test Cases
8.  Acknowledgements
9.  References
    9.1.  Normative References
    9.2.  Informative References
§  Author's Address

1.  Introduction

This memo describes the use of the Advanced Encryption Standard (AES) [FIPS197] (, “The Advanced Encryption Standard (AES),” .) with 192 and 256 bit keys within the Secure RTP protocol [RFC3711] (Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. Norrman, “The Secure Real-time Transport Protocol (SRTP),” March 2004.). Below those block ciphers are referred to as AES-192 and AES-256, respectively, and the use of AES with a 128 bit key is referred to as AES-128. This document defines Counter Mode encryption for SRTP and SRTCP and a new SRTP Key Derivation Function for AES-192 and AES-256. It also defines new cryptosuites that use these new functions.

While AES-128 is widely regarded as more than adequately secure, some users may be motivated to adopt AES-192 or AES-256. One motivation is conformance to the Suite B profile (which requires AES-256 for the protection of TOP SECRET information) [suiteB] (, “Fact Sheet for NSA Suite B Cryptography,” .). Others may be motivated by a perceived need to purse a highly conservative security strategy; see Section 6 (Security Considerations) for more discussion of security issues.

The crypto functions defined in this document are an addition to, and not a replacement for, the crypto functions defined in [RFC3711] (Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. Norrman, “The Secure Real-time Transport Protocol (SRTP),” March 2004.).

1.1.  Conventions Used In This Document

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119] (Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” March 1997.).

2.  AES-192 and AES-256 Encryption

Section 4.1.1 of [RFC3711] (Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. Norrman, “The Secure Real-time Transport Protocol (SRTP),” March 2004.) defines AES-128 counter mode encryption, which it refers to as AES_CM. AES-192 counter mode and AES-256 counter mode are defined in a similar manner, and are denoted as AES_192_CM and AES_256_CM respectively. In both of these ciphers, the plaintext inputs to the block cipher are formed as in AES_CM, and the block cipher outputs are processed as in AES_CM. The only difference in the processing is that AES_192_CM uses AES-192, and AES_256_CM uses AES-256. Both AES_192_CM and AES_256_CM use a 112-bit salt as an input, as does AES_CM.

For the convenience of the reader, the structure of the counter blocks in SRTP counter mode encryption is illustrated in Figure 1 (AES Counter Mode. ), using the terminology from Section 4.1.1 of [RFC3711] (Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. Norrman, “The Secure Real-time Transport Protocol (SRTP),” March 2004.) . In this diagram, the symbol (+) denotes the bitwise exclusive-or operation, and the AES encrypt operation uses AES-128, AES-192, or AES-256 for AES_CM, AES_192_CM, and AES_256_CM, respectively. The field labeled b_c contains a block counter, the value of which increments once for each invocation of the "AES Encrypt" function.

one octet
 <-->
  0  1  2  3  4  5  6  7  8  9  10 11 12 13 14 15
 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
 |00|00|00|00|   SSRC    |   packet index  | b_c |---+
 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+   |
                                                     |
 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+   v
 |                  salt (k_s)             |00|00|->(+)
 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+   |
                                                     |
                                                     v
                                              +-------------+
                      encryption key (k_e) -> | AES encrypt |
                                              +-------------+
                                                     |
 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+   |
 |                keystream block                |<--+
 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+

3.  The AES_192_CM_PRF and AES_256_CM_PRF Key Derivation Functions

Section 4.3.3 of [RFC3711] (Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. Norrman, “The Secure Real-time Transport Protocol (SRTP),” March 2004.) defines AES-128 counter mode key derivation function, which it refers to as "AES-CM PRF". (That specification uses the term PRF, or pseudo-random function, interchangeably with the term "key derivation function". ) The AES-192 counter mode PRF and AES-256 counter mode PRF are defined in a similar manner, and are denoted as AES_192_CM_PRF and AES_256_CM_PRF respectively. In both of these PRFs, the plaintext inputs to the block cipher are formed as in the AES-CM PRF, and the block cipher outputs are processed as in the AES-CM PRF. The only difference in the processing is that AES_192_CM_PRF uses AES-192, and AES_256_CM_PRF uses AES-256. Both AES_192_CM_PRF and AES_256_CM_PRF use a 112-bit salt as an input, as does the AES-CM PRF.

For the convenience of the reader, the structure of the counter blocks in SRTP counter mode key derivation is illustrated in Figure 2 (The AES counter mode Key Derivation Function), using the terminology from Section 4.3.3 of [RFC3711] (Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. Norrman, “The Secure Real-time Transport Protocol (SRTP),” March 2004.). In this diagram, the symbol (+) denotes the bitwise exclusive-or operation, and the "AES Encrypt" operation uses AES-128, AES-192, or AES-256 for the "AES-CM PRF", AES_192_CM_PRF, and AES_256_CM_PRF, respectively. The field "LB" contains the 8-bit constant "label" which is provided as an input to the key derivation function (and which is distinct for each type of key generated by that function). The field labeled b_c contains a block counter, the value of which increments once for each invocation of the "AES Encrypt" function.

one octet
 <-->
  0  1  2  3  4  5  6  7  8  9  10 11 12 13 14 15
 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
 |00|00|00|00|00|00|00|LB| index DIV kdr   | b_c |---+
 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+   |
                                                     |
 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+   v
 |               master salt               |00|00|->(+)
 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+   |
                                                     |
                                                     v
                                              +-------------+
                                master key -> | AES encrypt |
                                              +-------------+
                                                     |
 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+   |
 |                   output block                |<--+
 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+

3.1.  Usage Requirements

When AES_192_CM is used for encryption, AES_192_CM SHOULD be used as the key derivation function, and AES_128_CM MUST NOT be used as the key derivation function.

When AES_256_CM is used for encryption, AES_256_CM SHOULD be used as the key derivation function. Both AES_128_CM and AES_192_CM MUST NOT be used as the key derivation function.

Rationale: it is essential that the cryptographic strength of the key derivation meets or exceeds that of the encryption method. It is natural to use the same function for both encryption and key derivation. However, it is not required to do so because it is desirable to allow these ciphers to be used with alternative key derivation functions that may be defined in the future.

4.  Crypto Suties

This section defines SRTP crypto suites that use the ciphers and key derivation functions defined in this document. These suites are registered with IANA for use with the SDP Security Descriptions attributes (Section 10.3.2.1 of [RFC4568] (Andreasen, F., Baugher, M., and D. Wing, “Session Description Protocol (SDP) Security Descriptions for Media Streams,” July 2006.)). Other SRTP key management methods that use the crypto functions defined in this document are encouraged to also use these crypto suite definitions.

5.  IANA Considerations

IANA is expected to assign the following parameters for the SDP Security Descriptions crypto suite attribute.

AES_192_CM_HMAC_SHA1_80

AES_192_CM_HMAC_SHA1_32

AES_256_CM_HMAC_SHA1_80

AES_256_CM_HMAC_SHA1_32

The cryptosuites are as defined in Section 4 (Crypto Suties).

6.  Security Considerations

AES-128 provides a level of security that is widely regarded as being more than sufficient for providing confidentiality. It is believed that the economic cost of breaking AES-128 is significantly higher than the cost of more direct approaches to violating system security, e.g. theft, bribery, wiretapping, and other forms of malfeasance.

Future advances in the state of the art of cryptanalysis could eliminate this confidence in AES-128, and motivate the use of AES-192 or AES-256. AES-192 is regarded as being secure even against some adversaries for which breaking AES-128 may be feasible. Similarly, AES-256 is regarded as being secure even against some adversaries for which it may be feasible to break AES-192. The availability of the larger key size versions of AES provides a fallback plan in case of unanticipated cryptanalytic results.

It is conjectured that AES-256 provides adequate security even against adversaries that possess the ability to construct a quantum computer that works on 256 or more quantum bits. No such computer is known to exist; its feasibility is an area of active speculation and research.

Despite the apparent sufficiency of AES-128, some users are interested in the larger AES key sizes. For some applications, the 40% increase in computational cost for AES-256 over AES-128 is a worthwhile bargain when traded for the security advantages outlined above. These applications include those with a perceived need for very high security, e.g. due to a desire for very long-term confidentiality.

As with any cipher, the conjectured security level of AES may change over time. The considerations in this section reflect the best knowledge available at the time of publication of this document.

It is desirable that AES_192_CM and AES_192_CM_PRF be used with an authentication function that uses a 192 bit key, and that AES_256_CM and AES_256_CM_PRF be used with an authentication function that uses a 256 bit key. However, this desire is not regarded as security-critical. Cryptographic authentication is resilient against future advances in cryptanalysis, since the opportunity for a forgery attack against a session closes when that session closes.

7.  Test Cases

The test cases in this section are based on Appendix B of [RFC3711] (Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. Norrman, “The Secure Real-time Transport Protocol (SRTP),” March 2004.).

7.1.  AES-256-CM Test Cases

    Keystream segment length: 1044512 octets (65282 AES blocks)
    Session Key:      57f82fe3613fd170a85ec93c40b1f092
                      2ec4cb0dc025b58272147cc438944a98
    Rollover Counter: 00000000
    Sequence Number:  0000
    SSRC:             00000000
    Session Salt:     f0f1f2f3f4f5f6f7f8f9fafbfcfd0000 (already shifted)
    Offset:           f0f1f2f3f4f5f6f7f8f9fafbfcfd0000

    Counter                            Keystream

    f0f1f2f3f4f5f6f7f8f9fafbfcfd0000   92bdd28a93c3f52511c677d08b5515a4
    f0f1f2f3f4f5f6f7f8f9fafbfcfd0001   9da71b2378a854f67050756ded165bac
    f0f1f2f3f4f5f6f7f8f9fafbfcfd0002   63c4868b7096d88421b563b8c94c9a31
    ...                                ...
    f0f1f2f3f4f5f6f7f8f9fafbfcfdfeff   cea518c90fd91ced9cbb18c078a54711
    f0f1f2f3f4f5f6f7f8f9fafbfcfdff00   b4d49c8aec7ccb7726f14f338d19d88a
    f0f1f2f3f4f5f6f7f8f9fafbfcfdff01   c6f6a4804386cf175903139119b4fbde

7.2.  AES_256_CM_PRF Test Cases

This section provides test data for the AES_256_CM_PRF key derivation function, which uses AES-256 in Counter Mode. In the following, we walk through the initial key derivation for the AES-256 Counter Mode cipher, which requires a 32 octet session encryption key and a 14 octet session salt, and the HMAC-SHA1 authentication function, which requires a 20-octet session authentication key. These values are called the cipher key, the cipher salt, and the auth key in the following. Since this is the initial key derivation and the key derivation rate is equal to zero, the value of (index DIV key_derivation_rate) is zero (actually, a six-octet string of zeros). In the following, we shorten key_derivation_rate to kdr.

The inputs to the key derivation function are the 32 octet master key and the 14 octet master salt:

      master key:  f0f04914b513f2763a1b1fa130f10e29
                   98f6f6e43e4309d1e622a0e332b9f1b6
      master salt: 3b04803de51ee7c96423ab5b78d2

We first show how the cipher key is generated. The input block for AES-256-CM is generated by exclusive-oring the master salt with the concatenation of the encryption key label 0x00 with (index DIV kdr), then padding on the right with two null octets (which implements the multiply-by-2^16 operation, see Section 4.3.3 of RFC 3711). The resulting value is then AES-256-CM- encrypted using the master key to get the cipher key.

      index DIV kdr:                 000000000000
      label:                       00
      master salt:   3b04803de51ee7c96423ab5b78d2
      -----------------------------------------------
      xor:           3b04803de51ee7c96423ab5b78d2     (x, PRF input)

      x*2^16:        3b04803de51ee7c96423ab5b78d20000 (AES-256-CM input)
      x*2^16 + 1:    3b04803de51ee7c96423ab5b78d20001 (2nd AES input)

      cipher key:    5ba1064e30ec51613cad926c5a28ef73 (1st AES output)
                     1ec7fb397f70a960653caf06554cd8c4 (2nd AES output)

Next, we show how the cipher salt is generated. The input block for AES-256-CM is generated by exclusive-oring the master salt with the concatenation of the encryption salt label. That value is padded and encrypted as above.

      index DIV kdr:                 000000000000
      label:                       02
      master salt:   3b04803de51ee7c96423ab5b78d2

      ----------------------------------------------
      xor:           3b04803de51ee7cb6423ab5b78d2     (x, PRF input)

      x*2^16:        3b04803de51ee7cb6423ab5b78d20000 (AES-256-CM input)

                     fa31791685ca444a9e07c6c64e93ae6b (AES-256 ouptut)

      cipher salt:   fa31791685ca444a9e07c6c64e93

We now show how the auth key is generated. The input block for AES-256-CM is generated as above, but using the authentication key label.

      index DIV kdr:                   000000000000
      label:                         01
      master salt:     3b04803de51ee7c96423ab5b78d2
      -----------------------------------------------
      xor:             3b04803de51ee7c86423ab5b78d2     (x, PRF input)

      x*2^16:          3b04803de51ee7c86423ab5b78d20000 (AES-256-CM in)

   Below, the AES-256 output blocks that form the auth key are shown
   on the left, while the corresponding AES-256 input blocks are shown
   on the right.  Note that the final AES-256 output is truncated to a
   four-byte length.  The final auth key is shown below.

   auth key blocks                    AES-256 input blocks
   fd9c32d39ed5fbb5a9dc96b30818454d   3b04803de51ee7c86423ab5b78d20000
   1313dc05                           3b04803de51ee7c86423ab5b78d20001

   auth key: fd9c32d39ed5fbb5a9dc96b30818454d1313dc05

7.3.  AES-192-CM Test Cases

    Keystream segment length: 1044512 octets (65282 AES blocks)
    Session Key:      eab234764e517b2d3d160d587d8c8621
                      9740f65f99b6bcf7
    Rollover Counter: 00000000
    Sequence Number:  0000
    SSRC:             00000000
    Session Salt:     f0f1f2f3f4f5f6f7f8f9fafbfcfd0000 (already shifted)
    Offset:           f0f1f2f3f4f5f6f7f8f9fafbfcfd0000

    Counter                            Keystream

    f0f1f2f3f4f5f6f7f8f9fafbfcfd0000   93853536732e0908a6cb28bd85b64776
    f0f1f2f3f4f5f6f7f8f9fafbfcfd0001   a7e18fa46613babe588100d39d7ecbdd
    f0f1f2f3f4f5f6f7f8f9fafbfcfd0002   1e39fa7aa435aa15bf5b607d44d1941d
    ...                                ...
    f0f1f2f3f4f5f6f7f8f9fafbfcfdfeff   cb82e54adb48c702633e2f757a2f4989
    f0f1f2f3f4f5f6f7f8f9fafbfcfdff00   a3b2f7e1a988b0a90bb495081f17022f
    f0f1f2f3f4f5f6f7f8f9fafbfcfdff01   3eeafd32fd6e4ee267f04e118a4b8f5b

7.4.  AES_192_CM_PRF Test Cases

This section provides test data for the AES_256_CM_PRF key derivation function, which uses AES-256 in Counter Mode. In the following, we walk through the initial key derivation for the AES-256 Counter Mode cipher, which requires a 32 octet session encryption key and a 14 octet session salt, and the HMAC-SHA1 authentication function, which requires a 20-octet session authentication key. These values are called the cipher key, the cipher salt, and the auth key in the following. Since this is the initial key derivation and the key derivation rate is equal to zero, the value of (index DIV key_derivation_rate) is zero (actually, a six-octet string of zeros). In the following, we shorten key_derivation_rate to kdr.

The inputs to the key derivation function are the 32 octet master key and the 14 octet master salt:

      master key:  73edc66c4fa15776fb57f9505c171365
                   50ffda71f3e8e5f1
      master salt: c8522f3acd4ce86d5add78edbb11

We first show how the cipher key is generated. The input block for AES-256-CM is generated by exclusive-oring the master salt with the concatenation of the encryption key label 0x00 with (index DIV kdr), then padding on the right with two null octets (which implements the multiply-by-2^16 operation, see Section 4.3.3 of RFC 3711). The resulting value is then AES-256-CM- encrypted using the master key to get the cipher key.

      index DIV kdr:                 000000000000
      label:                       00
      master salt:   c8522f3acd4ce86d5add78edbb11
      -----------------------------------------------
      xor:           c8522f3acd4ce86d5add78edbb11     (x, PRF input)

      x*2^16:        c8522f3acd4ce86d5add78edbb110000 (AES-256-CM input)
      x*2^16 + 1:    c8522f3acd4ce86d5add78edbb110001 (2nd AES input)

      cipher key:    6da8e1e082a06aa80e5cbb0661a5174a (1st AES output)
                     3b8636251d8e4c539e5923b5ddb30cd4 (2nd AES output)

Next, we show how the cipher salt is generated. The input block for AES-256-CM is generated by exclusive-oring the master salt with the concatenation of the encryption salt label. That value is padded and encrypted as above.

      index DIV kdr:                 000000000000
      label:                       02
      master salt:   c8522f3acd4ce86d5add78edbb11

      ----------------------------------------------
      xor:           c8522f3acd4ce86f5add78edbb11     (x, PRF input)

      x*2^16:        c8522f3acd4ce86f5add78edbb110000 (AES-256-CM input)

                     cf075c87408e8f8ad63fbd1ca9292eb4 (AES-256 ouptut)

      cipher salt:   cf075c87408e8f8ad63fbd1ca929

We now show how the auth key is generated. The input block for AES-256-CM is generated as above, but using the authentication key label.

      index DIV kdr:                   000000000000
      label:                         01
      master salt:     c8522f3acd4ce86d5add78edbb11
      -----------------------------------------------
      xor:             c8522f3acd4ce86c5add78edbb11     (x, PRF input)

      x*2^16:          c8522f3acd4ce86c5add78edbb110000 (AES-256-CM in)

   Below, the AES-256 output blocks that form the auth key are shown
   on the left, while the corresponding AES-256 input blocks are shown
   on the right.  Note that the final AES-256 output is truncated to a
   four-byte length.  The final auth key is shown below.

   auth key blocks                    AES-256 input blocks
   95f57950398ac4241ef5760b54bc5579   c8522f3acd4ce86c5add78edbb110000
   6ae9adf7                           c8522f3acd4ce86c5add78edbb110001

   auth key: 95f57950398ac4241ef5760b54bc55796ae9adf7

8.  Acknowledgements

Thanks are due to John Mattsson for verifying the test cases in the document, and to Bob Bell for feedback and encouragement.

9.  References

9.1. Normative References

9.2. Informative References

Author's Address