[rtcweb] Requirements for SRTP profile?
Taylor Brandstetter <deadbeef@google.com> Fri, 14 April 2017 15:46 UTC
Return-Path: <deadbeef@google.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9B6A1273E2 for <rtcweb@ietfa.amsl.com>; Fri, 14 Apr 2017 08:46:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
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 Ts65lF9td91S for <rtcweb@ietfa.amsl.com>; Fri, 14 Apr 2017 08:46:36 -0700 (PDT)
Received: from mail-qt0-x22e.google.com (mail-qt0-x22e.google.com [IPv6:2607:f8b0:400d:c0d::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0BB5F1289B0 for <rtcweb@ietf.org>; Fri, 14 Apr 2017 08:46:35 -0700 (PDT)
Received: by mail-qt0-x22e.google.com with SMTP id n46so67349890qta.2 for <rtcweb@ietf.org>; Fri, 14 Apr 2017 08:46:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=+BotWdMC9vy2D9Uk1hsJCs0P7wJLFX6YCk+EFqytbQM=; b=IjZ6bEQbzEAGG9dBwaqJ3Eq7ZI/Hk4XP0hA5E96EYx7oBkPGv7dpdgbABous/lgv3W UvuNSTcEU6FkV+QdNMCuRk2vs6NLovuq7/Xnd6bkNneFVoAeRIfi4llOifwbmLy+xubX IeiBl3y2TOjjfoDfezOO6OGE0firR4lDonKLhyp7ea6qqSzjkinuPK47XBtk1To9e2iA nC6OJG5/zTMaqyVUyJLKLcbjK8oYuiG+R9nVoLlr2Qe8Sm0nzUK23ltAe19z2bup20DQ PKmkBlgM7pSFaktg2ot1+hzYxZ9XLfPabDJpJ0Y4ERne07Pgl8csvaKKFFRCtYk7t+R5 o7EQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=+BotWdMC9vy2D9Uk1hsJCs0P7wJLFX6YCk+EFqytbQM=; b=L4HymMnHX/X6YwEx+o7Mmz5FB37FX9LO/9Kvuimm95o/GkrI4VsRYv/nTt676iH6MW WBWhEEdK5zVNZlfSjECwop06vBt6s7ZANBtftppkA8FrOSYYRQlROZilszH+GUwTEPuo CfaQ54kMQeOJWfUM5wCPjSXTJhj8rbReKwznSlHFCT7ZF61ItWDTZfLMcyQFNOZMp1Ks nNCZNyjOtnLjlk89jEu510BBI0O9WKtryeGrZhb3aiOPgYGtskMDhPjjiL2k4K3I+lXJ jc9DYXZ4q+qRo9cClNZV6TcgSs8ggg0aacjPBwF013A9MABnGtoX31ucJaG/COJXqa3J voYQ==
X-Gm-Message-State: AN3rC/6+WhsXG0QhWnj9sNJx7JHfo0fbDfvyVeHqHNTthg2bVN5pNAs0 wiwPC+DbHpp6cOTPGhVf4rr4vpR5op31147Adw==
X-Received: by 10.200.33.245 with SMTP id 50mr7452246qtz.64.1492184793976; Fri, 14 Apr 2017 08:46:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.12.154.209 with HTTP; Fri, 14 Apr 2017 08:46:33 -0700 (PDT)
From: Taylor Brandstetter <deadbeef@google.com>
Date: Fri, 14 Apr 2017 08:46:33 -0700
Message-ID: <CAK35n0YCxt1oVAOt-+6x5UYt2wxrR-k0sfSqPhXHk9xYJW3_ZA@mail.gmail.com>
To: RTCWeb IETF <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="001a11402e0e95dfc4054d2258b2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/iuckW34OQb1BZzjh5rg3vXpky7k>
Subject: [rtcweb] Requirements for SRTP profile?
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Apr 2017 15:46:38 -0000
Chrome has been offering the "SRTP_AES128_CM_HMAC_SHA1_32" profile for some time (in the interest of saving a few bytes per packet), and I'm trying to figure out if this is acceptable or not. security-arch <https://tools.ietf.org/html/draft-ietf-rtcweb-security-arch-12> says the following: - "implementations MUST NOT negotiate cipher suites with NULL encryption modes" - "The DTLS-SRTP protection profile SRTP_AES128_CM_HMAC_SHA1_80 MUST be supported for SRTP" Unless I'm overlooking something, this seems to indicate that offering "SRTP_AES128_CM_HMAC_SHA1_32" *is* acceptable, as long as "SRTP_AES128_CM_HMAC_SHA1_80" is offered as well. Is my interpretation correct?
- [rtcweb] Requirements for SRTP profile? Taylor Brandstetter
- Re: [rtcweb] Requirements for SRTP profile? Peter Thatcher