IETF Logo Mail Archive

Re: [rtcweb] Requirements for SRTP profile?

Peter Thatcher <pthatcher@google.com> Fri, 14 April 2017 17:02 UTC

Return-Path: <pthatcher@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 B5435129514 for <rtcweb@ietfa.amsl.com>; Fri, 14 Apr 2017 10:02:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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_LOW=-0.7, 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 IihXZgPM9p-R for <rtcweb@ietfa.amsl.com>; Fri, 14 Apr 2017 10:02:44 -0700 (PDT)
Received: from mail-io0-x22f.google.com (mail-io0-x22f.google.com [IPv6:2607:f8b0:4001:c06::22f]) (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 5748512946C for <rtcweb@ietf.org>; Fri, 14 Apr 2017 10:02:44 -0700 (PDT)
Received: by mail-io0-x22f.google.com with SMTP id r16so113575011ioi.2 for <rtcweb@ietf.org>; Fri, 14 Apr 2017 10:02:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=ZkUAtPrDmtzQs/ocFIDhJhFXrhdqWoepCiekrhHlzWs=; b=ClGDYhPr96ajbqcAJ+6J1cIKHH1qbwPMK9rqLHVvMQNP6wImeOqy60LNSk0gMccpPX A3fy3i9Y4SsljBNfd/hSWJPwAX6Zn2Cv5l5uMSGRngpKm8lqTKiclz2A5w1wHYi2Fud6 AVhqMFsgL71XbTDde/lGlvQWxESvGu+GdocfzwZQDSAmXsUsxb3HcC9nVJ/obLviK99Q mDSTT4eVeLM3olkymt9Az3q6ArSXVdmdnU3ONkkA8eURomaGhOdFVv/ecSsNfao6DXFT lsS6Esny4GUEUnKhlMdJqq9mnau46DRfhJC6SCRsO12ejKgh0D/eGksub9XOA12/HGV4 ewCg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=ZkUAtPrDmtzQs/ocFIDhJhFXrhdqWoepCiekrhHlzWs=; b=g9xLUlyFTxIolbPevC/1QI0GdNFkQpNxQt6uw47dhk2EBxosyGpO7+cZ/5FC6+mSOu u1y4TBq/3UGZR3yxfLYQ46tEtLuzPNi9XGzK5uCZqa3moaFvo9ahlibgqLQUpiiKneA5 vFSD0bdswcMdhbSo1ts1zx6I5c/1dkgPitTRvfW8grpgBiHbg7u+pAbbyzY31l7wCgW5 Tj/UI4M5bKyNUrmOoY0zAMSvlDgtSfpypnLCQEXA0r3s3l+MrXWjMtN4+HsZL9GcR/hT Su3j0T45C4GDu9TTRa+5ap+UZdEvGvvzVdQxRjWt+oAKvB3Vi+wXkphDz3ChU0jKrz4D +WVg==
X-Gm-Message-State: AN3rC/5PtvQwXMefj/V5fMmcebqWnOWfUyWuEPZPPAoe/rIOQgMgAtE/ esRcWU9rmrJAYzqFrNwvJkMf9nUOtd0mM/c=
X-Received: by 10.36.111.207 with SMTP id x198mr35522087itb.26.1492189363602; Fri, 14 Apr 2017 10:02:43 -0700 (PDT)
MIME-Version: 1.0
References: <CAK35n0YCxt1oVAOt-+6x5UYt2wxrR-k0sfSqPhXHk9xYJW3_ZA@mail.gmail.com>
In-Reply-To: <CAK35n0YCxt1oVAOt-+6x5UYt2wxrR-k0sfSqPhXHk9xYJW3_ZA@mail.gmail.com>
From: Peter Thatcher <pthatcher@google.com>
Date: Fri, 14 Apr 2017 17:02:32 +0000
Message-ID: <CAJrXDUG5GUdeGbASs8wD_oA27hM2B+MYWDaDdXP7eoYA1H48hQ@mail.gmail.com>
To: Taylor Brandstetter <deadbeef@google.com>, RTCWeb IETF <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="001a11452ec8f4f9a1054d2368e6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/2eGp1iINM9WchnSRtV4rwTZLthk>
Subject: Re: [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 17:02:46 -0000

Yes, I believe that is correct.

On Fri, Apr 14, 2017 at 8:46 AM Taylor Brandstetter <deadbeef@google.com>
wrote:

> 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 mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>

v2.23.0 | Report a Bug | By Email