IETF Logo Mail Archive

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

"Christopher Wood" <caw@heapingbits.net> Thu, 03 October 2019 03:19 UTC

Return-Path: <caw@heapingbits.net>
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 AA6FF12007A for <tls@ietfa.amsl.com>; Wed, 2 Oct 2019 20:19:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 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_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=heapingbits.net header.b=hvPYN+vp; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=ZgU+ThVK
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 FTi7HH6i-ss9 for <tls@ietfa.amsl.com>; Wed, 2 Oct 2019 20:19:04 -0700 (PDT)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BBFAD120073 for <tls@ietf.org>; Wed, 2 Oct 2019 20:19:04 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 010E35B5; Wed, 2 Oct 2019 23:19:03 -0400 (EDT)
Received: from imap4 ([10.202.2.54]) by compute6.internal (MEProxy); Wed, 02 Oct 2019 23:19:04 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heapingbits.net; h=mime-version:message-id:in-reply-to:references:date:from:to :cc:subject:content-type; s=fm2; bh=5nXi9eY1bgJNQGca33xfqvokWRg1 208wEo/TAlJcdTQ=; b=hvPYN+vpjKlMvPlAfvK1kNYz6QQS+k8hpsDNjZMdc/14 ZghIvngRGNlLBvCiB9C6zt51dcIETCK4KQGQUbHm4cgL/vbP1+hCv+/KDTUcI5sl WUT3pPECYDPEzS0HzmOYCZmTR4AUoHiml53q2lxarggYEMkXYs6er3tVGTjRhG0K ExTy5iWDkRv9D9yjQ9CRw/WQvT47F+XXOMZdcl/h0HvKJUYocAwL3BNd7QUGIGWl b2cYcCJKLDBhfxRcoaC4ufmX7LbF4Ao/TFZX+GiY8fJVRf/FabvfT34MbvHr9UA5 gkoqgLOwmAm/n3dAl8e6p3VSObNJUy+tuIrsQwT8hw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=5nXi9e Y1bgJNQGca33xfqvokWRg1208wEo/TAlJcdTQ=; b=ZgU+ThVKC7x+3lBJQ08sW7 DFHf3+5oipQDmiIoSjR2UroDaCoGi/e4nWVcA6Yvlcjglf92DxlLsDxOl9Qunll3 KeUbCcDaMXky9DJBcH3URuxVCro62g9pK/XOMxeJBomZyF8dwRNQ7nUqAMmUMiCg ReXyfwV7Bj5Bvkzr3nBDRj8EXBU6lWdk7NL9U+LHEw997BByEzukTpinfdm59tCS tpbsI8aG+/6sgl91nrdMUy+oVEVArpgVQQIn4pKUPzTfpWRZYgDH8zeuewJqWpvK 7nsybqPX7iRTjVPWX+RyjD2USiB/dd7FcUlmtu8D7gYbOW/5+/T4oo73beNvhJhg ==
X-ME-Sender: <xms:p2iVXRtyxrSwD1meETh3AESiWBjHbrtH9_FN2-fsbERwJjPqOjZqsw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrgeejgdeikecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtsehttdertderredtnecuhfhrohhmpedfvehhrhhi shhtohhphhgvrhcuhghoohgufdcuoegtrgifsehhvggrphhinhhgsghithhsrdhnvghtqe enucfrrghrrghmpehmrghilhhfrhhomheptggrfieshhgvrghpihhnghgsihhtshdrnhgv thenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:p2iVXevMC39s1LLAq3YsJR-5bGFuN-qUXqvOPEbJBWSW7_Hayc5k-g> <xmx:p2iVXfxOcCYEK1QcbYjyxQmuYYiQK-2vz6NgFd1RuRNCIkkNUt8Nzg> <xmx:p2iVXcgSF6yLN6lkKngVuuqf6EmzueFqdqRWT7mDegAB7xIjoucuCA> <xmx:p2iVXfifJsH_Rp_D0OZbOBafUp18EM80o6Z60IZvjz5n0v4epvfzDw>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 21EA23C00A1; Wed, 2 Oct 2019 23:19:03 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-359-g64bf1af-fmstable-20191002v2
Mime-Version: 1.0
Message-Id: <16d1473c-8ee9-4007-b71e-eef38134d331@www.fastmail.com>
In-Reply-To: <CAChr6Sx9smPR+paGUbXnrKN0TbRo0U5pnikRS3wDiMdhAq5Tdw@mail.gmail.com>
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> <CAChr6Sx9smPR+paGUbXnrKN0TbRo0U5pnikRS3wDiMdhAq5Tdw@mail.gmail.com>
Date: Wed, 02 Oct 2019 20:18:42 -0700
From: Christopher Wood <caw@heapingbits.net>
To: Rob Sayre <sayrer@gmail.com>
Cc: Daniel Migault <daniel.migault@ericsson.com>, "TLS@ietf.org" <tls@ietf.org>
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/GfpKv1H4XjG6dsU4qJQnEKl_Q5A>
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:19:07 -0000

On Wed, Oct 2, 2019, at 8:08 PM, Rob Sayre wrote:
> 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.

I understand, though I'm not sure more text is needed here. If you disagree, can you please suggest text to make it more clear?

Thanks,
Chris

v2.23.0 | Report a Bug | By Email