Re: [TLS] Barry Leiba's Discuss on draft-ietf-tls-session-hash-05: (with DISCUSS)

Stephen Farrell <stephen.farrell@cs.tcd.ie> Sat, 16 May 2015 17:46 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE9101A8747; Sat, 16 May 2015 10:46:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.51
X-Spam-Level:
X-Spam-Status: No, score=-1.51 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] 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 C5Ip9fuKSRN5; Sat, 16 May 2015 10:46:43 -0700 (PDT)
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 9B18A1A7011; Sat, 16 May 2015 10:46:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 7954DBEFD; Sat, 16 May 2015 18:46:41 +0100 (IST)
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 gp04BKqzcxk3; Sat, 16 May 2015 18:46:39 +0100 (IST)
Received: from [10.87.48.73] (unknown [86.46.19.109]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 244F3BEF7; Sat, 16 May 2015 18:46:39 +0100 (IST)
Message-ID: <5557827E.7050601@cs.tcd.ie>
Date: Sat, 16 May 2015 18:46:38 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Karthikeyan Bhargavan <karthik.bhargavan@gmail.com>
References: <20150509225248.21800.83581.idtracker@ietfa.amsl.com> <55546240.3010902@cs.tcd.ie> <FBCB2F18-4975-45EE-9550-5D77450AB5FE@gmail.com>
In-Reply-To: <FBCB2F18-4975-45EE-9550-5D77450AB5FE@gmail.com>
OpenPGP: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/tls/Q7IOMYQ9DSqV-alS5MM-T2Djlcc>
Cc: tls@ietf.org, draft-ietf-tls-session-hash@ietf.org, The IESG <iesg@ietf.org>, draft-ietf-tls-session-hash.shepherd@ietf.org, Barry Leiba <barryleiba@computer.org>, draft-ietf-tls-session-hash.ad@ietf.org, tls-chairs@ietf.org
Subject: Re: [TLS] Barry Leiba's Discuss on draft-ietf-tls-session-hash-05: (with DISCUSS)
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 May 2015 17:46:46 -0000

Hiya,

First, I don't think there's much energy for this issue but we
should get it sorted and move on.

So, how about if we add that this updates 5246 and leave it at that?

The meaning there is that anyone who writes a new implementation
of 5246 really ought also do this too.

I don't think there's any possible harm to adding that and doing
so achieves whatever possible good effect there might be from the
addition of any "Updates" relationship.

If I hear nothing, I'll add an RFC editor note to that effect in
a few days and hopefully that'll be sufficient for Barry to clear
his discuss. (Barry, if not, please say what would work.)

Cheers,
S.

On 14/05/15 09:58, Karthikeyan Bhargavan wrote:
> The session-hash draft has roughly the same impact as RFC5746, which says:
> "Updates: 5246, 4366, 4347, 4346, 2246"
> 
> We would be happy to add this list or a subset.
> 
> Other RFCs affected by the current proposal are: rfc5929, rfc5705, rfc5746.
> 
> Should we note these in any way, other than as Informative References?
> 
> Best,
> Karthik
> 
> 
> On 14 May 2015, at 10:52, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
> 
>>
>> Folks - I note this didn't get an answer. I don't recall that the WG
>> considered it, and I'm sure if it had the conclusion could have gone
>> either way (and a random choice would have been fine too:-) but can
>> you confirm or correct me on that please? If you can do it before the
>> telechat today (by ~1400 UTC) that'd be great.
>>
>> Thanks,
>> S.
>>
>> On 09/05/15 23:52, Barry Leiba wrote:
>>> Barry Leiba has entered the following ballot position for
>>> draft-ietf-tls-session-hash-05: 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-tls-session-hash/
>>>
>>>
>>>
>>> ----------------------------------------------------------------------
>>> DISCUSS:
>>> ----------------------------------------------------------------------
>>>
>>> This is a DISCUSS purely because I want to discuss it; whatever the
>>> result is, I will be clearing the DISCUSS, and not delaying the document
>>> on this point:  The last paragraph of Section 4 makes me wonder whether
>>> this should "update" 5246.  Basically, while this is an extension (which
>>> wouldn't normally use "updates"), it's one that you're proposing as
>>> standard behavior, and not really as an extension.
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> TLS mailing list
>>> TLS@ietf.org
>>> https://www.ietf.org/mailman/listinfo/tls
>>>
>