IETF Logo Mail Archive

Re: [MMUSIC] 4572 update: forbid weak hashes?

Martin Thomson <martin.thomson@gmail.com> Thu, 07 April 2016 20:09 UTC

Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52BC112D0F7 for <mmusic@ietfa.amsl.com>; Thu, 7 Apr 2016 13:09:47 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 qEIB0q_3SLC8 for <mmusic@ietfa.amsl.com>; Thu, 7 Apr 2016 13:09:46 -0700 (PDT)
Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (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 E97FB12D0A8 for <mmusic@ietf.org>; Thu, 7 Apr 2016 13:09:42 -0700 (PDT)
Received: by mail-io0-x231.google.com with SMTP id o126so85173769iod.0 for <mmusic@ietf.org>; Thu, 07 Apr 2016 13:09:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=++08NCJRKmjdIdLPTci9PV2aGCm273blPGV/XGf3QSs=; b=Z6+eP+ckXnw/Aqpztv9VZ51FKqo2skYNpTz8NgxShMoa5D/vXOftFGlY9UyhEUR7Yk HNgUEhkgp2/bOedaL/P3vJZD/86wWYGvEGh5kD+Geu/lFomiorrNhCMXyPMEYfIsmsKt moXmt3tuxnmSGu76RV+qh2p/+9tbuxTlozyHOoEtrq+mqrbOowLGYhRDZ2F9aW38X7pz I8f/VVpQyQdPymWaow0OhltPaeP9H7xfzOYPLy2iDgHjymt9XhL2Cn+SgpLo9/HNMEfT 3rxLD2WCnoaAVFb+Cuwp0OYLpcdzRkAWB5TSB6eHHqv73cEq/NYyTPSqIDzofdb6FwvU bs2A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=++08NCJRKmjdIdLPTci9PV2aGCm273blPGV/XGf3QSs=; b=EgoO9t1j9is0ia70XXRM2NnqfIhUEAzzbw9gU7I9yax7eX7BJi8rQm0fQzsEvdrE2s vkFVa7tHg0uY1xtAlm9O+gxglv0qxlar7BNH4xmlClTWoPrKeV+QpvJkndIwUYRfKE41 CFM1kOIJ3Zq3OccWPAmE5CKMj0g6moy6DqQTHeyCluwXM9/M8ytXIgCy8pcS5HSL+cM7 aTv2Oi5kk7uXBiFK78TsOiz28jt9+etOrs/AGnJ09NppcviTr2/pR1lY5Cg/skPahdGc hdNLOHDiy2wxC/0dANcKnTQDD6lklZttPdcv3JuLMsV5HUElXpl7G8ha3IJj8Tizbl0D xB2w==
X-Gm-Message-State: AD7BkJLEne6fdiGILszO/58GNBjVXSGDWhw+j4SVRQWG9dJCRrvlzMb/YZSsq+hwRZuWsMd+RW2HavCq2QfNFg==
MIME-Version: 1.0
X-Received: by 10.107.166.72 with SMTP id p69mr5491876ioe.100.1460059782316; Thu, 07 Apr 2016 13:09:42 -0700 (PDT)
Received: by 10.36.43.5 with HTTP; Thu, 7 Apr 2016 13:09:42 -0700 (PDT)
In-Reply-To: <CAD5OKxsVZqOj-HG7_vN4KS+E6=mKurGew=kkRv10u=CJe6QZwQ@mail.gmail.com>
References: <4D60EE45-BECA-4A46-98EF-FF4AA482B42E@vidyo.com> <7594FB04B1934943A5C02806D1A2204B37F27B70@ESESSMB209.ericsson.se> <CABkgnnU0qwkUGLv4rkax3hbat9Fb6kXDH9TKZv3MukepN7PkmQ@mail.gmail.com> <57067AFE.9070704@alum.mit.edu> <CAD5OKxtX9HLWJJgKsG7hNJbRB1muS+fe8Pnnm=g4+=ryPyMN+A@mail.gmail.com> <5706B499.9030209@alum.mit.edu> <CAD5OKxu_Ok2Cpb6Zvim4RtOpab3UY1xMWrJtODVHiqJBR_vfJA@mail.gmail.com> <CABkgnnWS030+7xLMdbd+p0bh3805UtRB5fYkOmGuxPcdHLh-1w@mail.gmail.com> <CAD5OKxsVZqOj-HG7_vN4KS+E6=mKurGew=kkRv10u=CJe6QZwQ@mail.gmail.com>
Date: Thu, 07 Apr 2016 17:09:42 -0300
Message-ID: <CABkgnnXApcn6K0fEEgrTNCOtdPDJeWJnhkmMzm+7b2jUt1nN+A@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Roman Shpount <roman@telurix.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/2_sBx_8bCDOqYEejhHb0_EaiKKo>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] 4572 update: forbid weak hashes?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Apr 2016 20:09:47 -0000

On 7 April 2016 at 16:54, Roman Shpount <roman@telurix.com> wrote:
> Let me try to explain this again why this will not work. Consider that RTP
> and RTCP can come from two different sources (devices) which will use
> different DTLS associations for each component, use different certificates,
> and potentially support different sets of hash functions. Because of this,
> the fact that RTP device supports SHA-256 does not mean that RTCP will use
> it or support it.

How is that relevant?  If the RTCP endpoint doesn't support X, then it
uses what it can.

v2.23.0 | Report a Bug | By Email