Re: [AVTCORE] Suite B Profile for DTLS-SRTP Internet-Draft

Glen Zorn <gwz@net-zen.net> Wed, 01 June 2011 10:56 UTC

Return-Path: <gwz@net-zen.net>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FE88E0784 for <avt@ietfa.amsl.com>; Wed, 1 Jun 2011 03:56:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MaUqAoUBcICc for <avt@ietfa.amsl.com>; Wed, 1 Jun 2011 03:56:12 -0700 (PDT)
Received: from smtpauth23.prod.mesa1.secureserver.net (smtpauth23.prod.mesa1.secureserver.net [64.202.165.47]) by ietfa.amsl.com (Postfix) with SMTP id 94CA5E0703 for <avt@ietf.org>; Wed, 1 Jun 2011 03:56:12 -0700 (PDT)
Received: (qmail 17127 invoked from network); 1 Jun 2011 10:56:12 -0000
Received: from unknown (115.87.116.114) by smtpauth23.prod.mesa1.secureserver.net (64.202.165.47) with ESMTP; 01 Jun 2011 10:56:11 -0000
Message-ID: <4DE61AC4.10009@net-zen.net>
Date: Wed, 01 Jun 2011 17:56:04 +0700
From: Glen Zorn <gwz@net-zen.net>
Organization: Network Zen
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
References: <4FD125153A070D45BC87645D3B880288025A13CACB@IMCMBX3.MITRE.ORG> <4DE4AC77.9050501@ericsson.com>
In-Reply-To: <4DE4AC77.9050501@ericsson.com>
X-Enigmail-Version: 1.1.1
Content-Type: multipart/mixed; boundary="------------060101020100030403060503"
Cc: "avt@ietf.org" <avt@ietf.org>, "kmigoe@nsa.gov" <kmigoe@nsa.gov>
Subject: Re: [AVTCORE] Suite B Profile for DTLS-SRTP Internet-Draft
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jun 2011 10:56:13 -0000

On 5/31/2011 3:53 PM, Magnus Westerlund wrote:

> Hi,
> 
> If I understand this document correctly there are actually three pieces
> to it:
> 
> - The SuiteB Crypto algorithms for SRTP
> - The SuiteB specific DTLS-SRTP procedures
> - Registration of DTLS-SRTP protection profiles
> 
> Thus in light of this document and also the ARIA SRTP registration I
> think we should discuss how to handle SRTP crypto algorithms and their
> connection to the keying mechanisms.
> 
> SRTP has at least three different IETF define ways to be keyed:
> - DTLS-SRTP [RFC5764]
> - MIKEY [3830]
> - Security Descriptions [RFC 4568]
> 
> And to my understanding they are all used somewhere.
> 
>>From my perspective as WG chair I wonder if shouldn't require anyone
> that creates a new crypto suit for SRTP to also create the suite
> profiles / identifiers for all of these three keying mechanisms?
> 
> Opinions?

I think that that is wholly unnecessary; however, if the WG wants to do
so, I have no problem with doing it.

...