IETF Logo Mail Archive

Re: [MMUSIC] Stephen Farrell's Discuss on draft-ietf-mmusic-4572-update-12: (with DISCUSS)

Stephen Farrell <stephen.farrell@cs.tcd.ie> Wed, 01 February 2017 08:09 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 2E555129586; Wed, 1 Feb 2017 00:09:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.499
X-Spam-Level:
X-Spam-Status: No, score=-7.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 ujIYediKM8UT; Wed, 1 Feb 2017 00:09:46 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D3CA129422; Wed, 1 Feb 2017 00:09:46 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id E557ABE2D; Wed, 1 Feb 2017 08:09:43 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IhFp1zO1UzQl; Wed, 1 Feb 2017 08:09:42 +0000 (GMT)
Received: from [10.87.48.75] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id DB1F7BE2C; Wed, 1 Feb 2017 08:09:41 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1485936582; bh=P6MVgNQR3u2QbxdZq0P7Q1Po0GkdHcRp1R+uXAppQvw=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=Z/CkN/4Wq80qCO2jDRqcuRobUAOljGU0ldTGYG+xXoPhcLAGQjN8BTk59Aan2uEL5 N0AAHfJy4b7BVQrBh+Rr09mX4+Z+DOnJEh/K2+ymkyqnPNlJsnbatqYQVun91N6qOY zbKAdREVd4HjMjkLEFuMN8EtIynndrveSnZF69lQ=
To: Eric Rescorla <ekr@rtfm.com>
References: <148587892598.2448.6982128247176255180.idtracker@ietfa.amsl.com> <CABcZeBOxqNdc1aa1mpRtriJxiv8=NnrwjYq6+=vZe6gUAs4z2w@mail.gmail.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <7d1ccbf6-a81c-1fb7-e753-281770a0b73d@cs.tcd.ie>
Date: Wed, 01 Feb 2017 08:09:41 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <CABcZeBOxqNdc1aa1mpRtriJxiv8=NnrwjYq6+=vZe6gUAs4z2w@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms040405050203090408070908"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/V3yqOIOe06j3kHE4QvwI_O4-N4c>
Cc: Flemming Andreasen <fandreas@cisco.com>, mmusic-chairs@ietf.org, draft-ietf-mmusic-4572-update@ietf.org, The IESG <iesg@ietf.org>, mmusic WG <mmusic@ietf.org>
Subject: Re: [MMUSIC] Stephen Farrell's Discuss on draft-ietf-mmusic-4572-update-12: (with DISCUSS)
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: Wed, 01 Feb 2017 08:09:48 -0000


On 01/02/17 07:18, Eric Rescorla wrote:
> On Tue, Jan 31, 2017 at 5:08 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie>
> wrote:
> 
>> Stephen Farrell has entered the following ballot position for
>> draft-ietf-mmusic-4572-update-12: Discuss
>>
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut this
>> introductory paragraph, however.)
>>
>>
>> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
>> for more information about IESG DISCUSS and COMMENT positions.
>>
>>
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-ietf-mmusic-4572-update/
>>
>>
>>
>> ----------------------------------------------------------------------
>> DISCUSS:
>> ----------------------------------------------------------------------
>>
>>
>> I've two (or 4 depending how you count:-) things
>> I'd like to check here. Should be pretty easy to
>> handle.
>>
>> (1) section 5: I'm wondering if we have the right
>> set of hash functions here. Deprecating md2 and md5
>> is great, but I have a bunch of questions about the
>> others:
>>
>> (1.1) why not also say that sha-1 MUST NOT be used
>> for new things (or similar)?
>>
>> (1.2) do you really need sha-224 and 384? I think
>> nobody uses those at all.
>>
> 
> It's certainly not correct that nobody uses SHA-384.
> 
> In fact, for TLS 1.3, you can't sign anything with P-384 without using
> SHA-384.

Fair enough. I guess some p384 will be seen in the web just
because it'll be seen as longer/stronger with tls1.3.

S

> 
> -Ekr
> 
> 
>> (1.3) I'm a bit surprised you didn't add sha3 (and
>> maybe remove sha-512 if that's not needed) Even if
>> you don't encourage use of sha3, it might be good
>> to include it in the abnf now in case it gets
>> popular.
>>
>> (2) Wouldn't it be a good plan to say that TLS
>> as-used MUST conform to BCP195? If not, why not?
>>
>>
>>
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>>
>

v2.23.0 | Report a Bug | By Email