[AVTCORE] Scope of EKT

John Mattsson <john.mattsson@ericsson.com> Mon, 23 March 2015 13:20 UTC

Return-Path: <john.mattsson@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E11E41A8A4A for <avt@ietfa.amsl.com>; Mon, 23 Mar 2015 06:20:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZU3u16TEbluV for <avt@ietfa.amsl.com>; Mon, 23 Mar 2015 06:20:56 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 87B5E1A8A4D for <avt@ietf.org>; Mon, 23 Mar 2015 06:20:56 -0700 (PDT)
X-AuditID: c1b4fb30-f79996d000006ebb-29-55101336966d
Received: from ESESSHC012.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 82.57.28347.63310155; Mon, 23 Mar 2015 14:20:54 +0100 (CET)
Received: from ESESSMB307.ericsson.se ([169.254.7.133]) by ESESSHC012.ericsson.se ([153.88.183.54]) with mapi id 14.03.0210.002; Mon, 23 Mar 2015 14:20:53 +0100
From: John Mattsson <john.mattsson@ericsson.com>
To: IETF AVTCore WG <avt@ietf.org>
Thread-Topic: Scope of EKT
Thread-Index: AQHQZWwwuheBTu72ukik17vz7duwLw==
Date: Mon, 23 Mar 2015 13:20:53 +0000
Message-ID: <F919A74C-AE66-4EC6-9C5D-5575D49B1E3A@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.150]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1633960644471943AFF374F210642823@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrMLMWRmVeSWpSXmKPExsUyM+Jvja6ZsECowadePYuXPSvZHRg9liz5 yRTAGMVlk5Kak1mWWqRvl8CVcfn4DraCN2wVa76eZW1g3MbaxcjOISFgItFs2cXICWSJSVy4 t56ti5GLQ0jgCKPEtpN3WEESQgJLGCW2zA0HsdkEDCTm7mlgA7FFBJQkdkzaxgxiCwuISmxd 2s8EEZeSaN3VAhTnALL1JD7sAmtlEVCVWP74GliYV8BeYvtHsCmMQGu/n1oD1sksIC5x68l8 JohzBCSW7DnPDGGLSrx8/I8VwlaSWLH9EiNEvY7Egt2f2CBsa4kJj+9AxbUlli18DdbLKyAo cXLmE5YJjCKzkKyYhaR9FpL2WUjaZyFpX8DIuopRtDi1OCk33chIL7UoM7m4OD9PLy+1ZBMj MBYObvltsIPx5XPHQ4wCHIxKPLwbGvlDhVgTy4orcw8xSnOwKInz2hkfChESSE8sSc1OTS1I LYovKs1JLT7EyMTBKdXAqCKmPoOZff4rQZenK6MXr7RSWeTiM/1y0/58mYaF9isePLn0/Ox3 WcXzTXyxYT2+Z26pC38KeuV4N2q/g73o0/jcq8znVyd0f6rdI5z9Iy2uVFAk33/xWdZVzZHu 88NFDDa6PT0kanCiO3xXu92qtCmuxw9YCWr9mhgjlVwq1s9tPoHt1IwJSizFGYmGWsxFxYkA vjHFAGYCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/xQzAU7iJR4kZGSN4Y9CTikcr30A>
Subject: [AVTCORE] Scope of EKT
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 23 Mar 2015 13:20:58 -0000

Hi,

When the work on EKT started, e2e secure conferencing was not in scope. In draft-jones-avtcore-private-media-framework-01 Cisco (authors of the EKT draft) is proposing to use EKT for the e2e secure conferencing use case. Several changes to EKT is also proposed:

- The position of the EKT field is changed from last in packet to before the authentication tag.

- A change to EKT such that the ROC is transmitted in the clear.

- An extension of EKT in order to negotiate the SRTP Protection Profile used for end-to-end encryption and authentication.

- An extension of EKT in order to send the participant identifier.

Without commenting on the specific changes, I agree that EKT is a good match for the e2e secure conferencing case and I support widening the scope of EKT to include this.

What does the group think?

Cheers,
John