Re: [TLS] WGLC for draft-ietf-tls-ticketrequests

David Schinazi <dschinazi.ietf@gmail.com> Thu, 21 November 2019 06:25 UTC

Return-Path: <dschinazi.ietf@gmail.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 075691200FB for <tls@ietfa.amsl.com>; Wed, 20 Nov 2019 22:25:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=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=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 mSMY2fsvfBqZ for <tls@ietfa.amsl.com>; Wed, 20 Nov 2019 22:25:11 -0800 (PST)
Received: from mail-lj1-x235.google.com (mail-lj1-x235.google.com [IPv6:2a00:1450:4864:20::235]) (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 93858120033 for <tls@ietf.org>; Wed, 20 Nov 2019 22:25:10 -0800 (PST)
Received: by mail-lj1-x235.google.com with SMTP id v8so1860106ljh.5 for <tls@ietf.org>; Wed, 20 Nov 2019 22:25:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=nddCzLXLBoqlkytDKg878gMau8hOGkHkwBhA4+JZCPE=; b=DxCyjK0kEpruqPBvviXjQlBH3c7nXp2GaQDT4NeoLdG3HqJflRfWHfJdeXxlIES7pH pEPuFa5mOyQWJgIRLtw8937A3lITp/2LLit452x2BAzykS9jOGS9zIvc/UapzU5Zmj2D B05CWuwhVKFVRpMs7zZXAMdVJOQjiLgomTGDauOQiZz6ocnA56kxkH2hLdj0hO093tpN geUGt7iz35JA6mT5xYq6iMl0gN306/xJbOUuKstAG0Al1cGWhISjxBiMMPov5ZJ0MiQ4 +31XiDYZb9Q68f4Z1If1l8+uKH+IbKWC+WOl/wvTExtpfHjxwbSeJWLOuYLvZsbSGRRW oH/w==
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:cc; bh=nddCzLXLBoqlkytDKg878gMau8hOGkHkwBhA4+JZCPE=; b=kEt7On90mYD+4zYVsDxEbU8c1ezwjiH0WA9KrqeIw20a9DmMiZjctiSceXE79hKOPp 9Z3Xi8UujhWcyyJ9u97+FKopWeYKc59+meVghmCBgnUmloKxwqyYKxqsdfZoccUag+1r wi7pjXG7MkEfhLkDCHLjGKEMipB1+QyVxc3FLgYYVven9lTDan1ncYOi83v/UnuTnSDg DiB17SUv6f8kIIZWSr5pUMY7yE93X4DLwc182uCIhWMVxxbV8lHzjJHL97N+gtX/fQz9 CBcFToUzFz+jP0jf6ALZiq4oOAv6yslxsgNOJmUXrYOXzne5dF9kTz7/YPJKEnE5roRj uqEw==
X-Gm-Message-State: APjAAAWVu6ljWAQsep55MnsRU0YKe4iP2q6jNwHo9tvOTTZZGKobR175 pxzLEANpHaD0eqBTo7XY+3B7jtoTXm64Y73oTZE=
X-Google-Smtp-Source: APXvYqytMy4E+khYaRHPqBn4JwNMo9EP/RvkuBvZ3xrAfHiOnjc5IOpgY3VKoeGH1sHr76gO0W7Shai0J06unC3qXh4=
X-Received: by 2002:a2e:9016:: with SMTP id h22mr5763644ljg.137.1574317508700; Wed, 20 Nov 2019 22:25:08 -0800 (PST)
MIME-Version: 1.0
References: <20191116103855.GQ20609@akamai.com> <20191116110425.GR34850@straasha.imrryr.org> <556d2210-4af7-b398-fbd7-eab2685d7c62@wizmail.org> <20191116210617.GS34850@straasha.imrryr.org> <20191116235952.GR20609@akamai.com> <20191117002249.GV34850@straasha.imrryr.org> <CADZyTkmaUVj=sFdgg93MuM2au0B=1M1k3yCA1XDoaAneVDmnNw@mail.gmail.com> <14690874-E301-4BC0-B385-00DEBCBA94C2@apple.com> <20191120034812.GQ34850@straasha.imrryr.org> <5FBFE820-8C53-4B32-9520-343279C1A6CC@apple.com> <20191120064819.GR34850@straasha.imrryr.org> <CAPDSy+6DFJ+OYRtYK6eEiUt1noiik4KxqrGFx0ro_RL2Mft_VA@mail.gmail.com> <67c2ed4f-ce87-4d63-87bf-c38a36c8fb70@www.fastmail.com> <CAPDSy+4NQeVpmawRAOnC=whQ6S25Lc7GZMT2syTStqEt8a7XRQ@mail.gmail.com> <CAChr6SxooRW-8hdp-JtjLVNy1jq3SDK+PK0Y=4qYyVVa_nOOTw@mail.gmail.com>
In-Reply-To: <CAChr6SxooRW-8hdp-JtjLVNy1jq3SDK+PK0Y=4qYyVVa_nOOTw@mail.gmail.com>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Thu, 21 Nov 2019 14:24:57 +0800
Message-ID: <CAPDSy+5Bes=kCi7WjbETJgBVu_TpM0n==9J7TVg0ha_4udhVvw@mail.gmail.com>
To: Rob Sayre <sayrer@gmail.com>
Cc: Martin Thomson <mt@lowentropy.net>, "TLS@ietf.org" <tls@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000deb0030597d55bf8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/M3590hKbzOODsO3y-av1ryGro_w>
Subject: Re: [TLS] WGLC for draft-ietf-tls-ticketrequests
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 21 Nov 2019 06:25:13 -0000

Hi Rob,

The SHOULD from your point (1) is there to address Daniel's concern about
IoT.
The SHOULD from (2) is indeed not required for interoperability, but
important
to ensure servers put this protection in place.

That said, I've taken your suggestion to add a comma since that is clearer.

Thanks!
David

On Thu, Nov 21, 2019 at 2:18 PM Rob Sayre <sayrer@gmail.com>; wrote:

> So, the current PR says:
>
> "Clients can use TicketRequestContents.count to indicate the number of
> tickets they would prefer to receive. Servers SHOULD NOT send more tickets
> than TicketRequestContents.count, as clients will most likely discard any
> additional tickets. Servers SHOULD additionally place a limit on the number
> of tickets they are willing to send to save resources. Therefore, the
> number of NewSessionTicket messages sent will be the minimum of the
> server's self-imposed limit and TicketRequestContents.count."
>
> I would suggest two edits to this text:
>
> 1: The second sentence can read: "If servers send more tickets than
> TicketRequestContents.count, clients will likely discard excess tickets.".
> This avoids a "SHOULD NOT" that should be a "MAY" or unmentioned.
>
> 2: The third sentence is implementation advice, not an interoperability
> requirement: "Servers SHOULD additionally place a limit on the number of
> tickets they are willing to send to save resources." I think this sentence
> should be struck, or rewritten in non-2119 English. If the editors wish to
> keep the text, I think there should be a comma after "send".
>
> These proposed edits make sense to me, because servers can't know if their
> tickets will be used successfully (network problems, unreliable clients,
> etc).
>
> thanks,
> Rob
>
>
> On Wed, Nov 20, 2019 at 9:45 PM David Schinazi <dschinazi.ietf@gmail.com>;
> wrote:
>
>> Thanks. I've updated the PR to take MT's suggestion s/SHOULD/will/.
>>
>> David
>>
>> On Thu, Nov 21, 2019 at 1:38 PM Martin Thomson <mt@lowentropy.net>; wrote:
>>
>>> On Thu, Nov 21, 2019, at 11:19, David Schinazi wrote:
>>> >  resources. Therefore, the number of NewSessionTicket messages sent
>>> >  SHOULD be the minimum of the server's self-imposed limit and
>>> >  TicketRequestContents.count.
>>>
>>> Thanks for doing this David.
>>>
>>> Friendly amendment: remove the SHOULD from this sentence (it's a
>>> consequence of the two other "SHOULD"s):
>>>
>>> Therefore, the number of NewSessionTicket messages sent will be the
>>> minimum [...]
>>>
>>> _______________________________________________
>>> TLS mailing list
>>> TLS@ietf.org
>>> https://www.ietf.org/mailman/listinfo/tls
>>>
>> _______________________________________________
>> TLS mailing list
>> TLS@ietf.org
>> https://www.ietf.org/mailman/listinfo/tls
>>
>