IETF Logo Mail Archive

Re: [TLS] I-D Action: draft-ietf-tls-ticketrequests-02.txt

Rob Sayre <sayrer@gmail.com> Thu, 03 October 2019 03:08 UTC

Return-Path: <sayrer@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 EF81F120073 for <tls@ietfa.amsl.com>; Wed, 2 Oct 2019 20:08:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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] 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 NVjCUHgLrk82 for <tls@ietfa.amsl.com>; Wed, 2 Oct 2019 20:08:16 -0700 (PDT)
Received: from mail-io1-xd33.google.com (mail-io1-xd33.google.com [IPv6:2607:f8b0:4864:20::d33]) (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 45FFD12006F for <tls@ietf.org>; Wed, 2 Oct 2019 20:08:16 -0700 (PDT)
Received: by mail-io1-xd33.google.com with SMTP id n197so2108003iod.9 for <tls@ietf.org>; Wed, 02 Oct 2019 20:08:16 -0700 (PDT)
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=OQthgOGOesEj/VkobG+IAwSyldG1iVI5n+l+nJCIxmw=; b=Zb9vxAkGV012SJk3FzgePJ63wz3mP030GGpiB/lEaMxr18EKDVuwdyOFYvDifAknGq w9tmStTQ0watwazlDu8TJVKjOrYbhzcxTxnnq2wXijPxsWf/TuOnDqGNnLrJuQ2RYtDT FR1j2ux4SQ0Yv3QmHwoErEsJTrN8oEgr+aUmuYeQagyUI8rWWlg7meL1lQ59zMW4ux0O j4jRan9ceG03a2xlcXdPiU8YZgvrIs2xeXyL0fQXz+0aVF1ThRoA/jFBBSLvA+G3E05P ow00CQTHSLodpSY/E7ug12VFoLdiiosypgGZAAl1t852YlvhkoyheiPqF36WdMM4airJ C66A==
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=OQthgOGOesEj/VkobG+IAwSyldG1iVI5n+l+nJCIxmw=; b=bUXa0Ln4ECloH0e9digCvJNWkWPtmc7T/yTz+o3TitY6Eau2BfKhDj7S8yArfYXG9V 1L1DvCl72Vk/bmpz6wSRfLT3VNBEZZE+xociteQWtK+fnNpYQ0XlXvvHLm/aJkH1XkaD HfOyYb4HIFM487BXeoUZOz9dhCEXqrN/vQIkMxzM0sPUHt9+ZMLW3xKRiXE82OqqlRlq obnIX1EplM9T8bFd6p9177EaWtSfwQwcWJ8hwpDaTi9nH3lcO7UY0pzkSaWc/iRKQkDL qWZibVOMRauBUm5IAvdvj6D7c+NK1GGJqqu2Dyc3+16EQ1zm0KWpMrr5zLK7hYIieDnM U+nw==
X-Gm-Message-State: APjAAAUj6MAiAgPcN2bh2NwZWy/eRnqifN+RmmLQyVFRWwX2daWrg1tA dnw9wFg2GdHFvwY8P0z3nLrfQ7qYSrnbyT5013c=
X-Google-Smtp-Source: APXvYqx3BO+OG6eOySTzK2i6dxbs7EJo+JAQX9qhT5YiCkOpYEZ/YScGSzMv0XGueV+O1UKsH4RRbvnEaJ119O4B6MU=
X-Received: by 2002:a6b:2c07:: with SMTP id s7mr6504420ios.254.1570072095287; Wed, 02 Oct 2019 20:08:15 -0700 (PDT)
MIME-Version: 1.0
References: <156962803631.24993.3421537129925787732@ietfa.amsl.com> <1971068.D9yiD15FoS@pintsize.usersys.redhat.com> <851aded9-70a7-4a9a-abd5-b75f98f86baf@www.fastmail.com> <1708345.JU3unZtj4k@pintsize.usersys.redhat.com> <350020eb-c43b-4941-93e9-06ea9a0cacc3@www.fastmail.com> <CADZyTkm-MRF_ucy-_crC5SeTYZ9=VdPuF+TL5fLkU1gbb=7rfQ@mail.gmail.com> <945ac286-bb40-4a41-8612-3183f28b68e5@www.fastmail.com>
In-Reply-To: <945ac286-bb40-4a41-8612-3183f28b68e5@www.fastmail.com>
From: Rob Sayre <sayrer@gmail.com>
Date: Thu, 3 Oct 2019 10:08:02 +0700
Message-ID: <CAChr6Sx9smPR+paGUbXnrKN0TbRo0U5pnikRS3wDiMdhAq5Tdw@mail.gmail.com>
To: Christopher Wood <caw@heapingbits.net>
Cc: Daniel Migault <daniel.migault@ericsson.com>, "TLS@ietf.org" <tls@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000082edb80593f8e544"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/4Rc5GnuC-5f0W5TRFW-Ohm8GoFw>
Subject: Re: [TLS] I-D Action: draft-ietf-tls-ticketrequests-02.txt
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, 03 Oct 2019 03:08:18 -0000

On Thu, Oct 3, 2019 at 3:54 AM Christopher Wood <caw@heapingbits.net> wrote:

>
> > I understand the meaning of count is the higher limit of ticket and the
> > server can provides any tickets between 0 and count. If that is
> > correct, this could be clearly stated and indication to chose an
> > appropriated value for each cases may be provided.
>
> The document states this:
>
>    A supporting server MAY vend TicketRequestContents.count
>    NewSessionTicket messages to a requesting client, and SHOULD NOT send
>    more than TicketRequestContents.count NewSessionTicket messages to a
>    requesting client.
>
> Is this not sufficient clear? If not, how can it be improved?
>

RFC2119 "SHOULD/SHOULD NOT" requirements are usually clearer with some
examples of "valid reasons in particular circumstances to ignore a
particular item" [RFC2119]. Otherwise, those requirements can be cryptic,
and perhaps better-described by MAY or MUST language.

thanks,
Rob

v2.8.10 | Report a Bug | By Email