Re: [Tls-reg-review] Adopting tls-flags

Benjamin Kaduk <kaduk@mit.edu> Fri, 19 March 2021 20:39 UTC

Return-Path: <kaduk@mit.edu>
X-Original-To: tls-reg-review@ietfa.amsl.com
Delivered-To: tls-reg-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8E0B3A0EDA; Fri, 19 Mar 2021 13:39:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level:
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 L74wl3rPak20; Fri, 19 Mar 2021 13:39:10 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1AD363A0ED7; Fri, 19 Mar 2021 13:39:09 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 12JKcx45016515 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 19 Mar 2021 16:39:04 -0400
Date: Fri, 19 Mar 2021 13:38:59 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Christopher Wood <caw@heapingbits.net>
Cc: Victor Vasiliev <vasilvv@google.com>, "tls-reg-review@ietf.org" <tls-reg-review@ietf.org>, draft-ietf-tls-cross-sni-resumption@ietf.org, TLS Chairs <tls-chairs@ietf.org>
Message-ID: <20210319203859.GF79563@kduck.mit.edu>
References: <1241c65d-6c9c-4935-920f-5ae56babcd7e@www.fastmail.com> <CAAZdMadAGa=X5+ktAUjr-=fvxrpQwRfERHbpR4+6KfXeiWxAGw@mail.gmail.com> <7fb3a536-6716-4f55-82ed-2c4b96669166@www.fastmail.com> <b1a39bbf-23b8-472c-9565-20479ee7b262@www.fastmail.com> <CAAZdMad7A3fJG9GyNrXgSnsnC-wHN5_V4wpaOqWwAtUGzWtbsw@mail.gmail.com> <1f78ab86-8e27-4d8a-b670-b1a5d6432eb0@www.fastmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <1f78ab86-8e27-4d8a-b670-b1a5d6432eb0@www.fastmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls-reg-review/pdTdet00Wry7tW-fggCmAmqaGMY>
Subject: Re: [Tls-reg-review] Adopting tls-flags
X-BeenThere: tls-reg-review@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: TLS REVIEW <tls-reg-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls-reg-review>, <mailto:tls-reg-review-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls-reg-review/>
List-Post: <mailto:tls-reg-review@ietf.org>
List-Help: <mailto:tls-reg-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls-reg-review>, <mailto:tls-reg-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Mar 2021 20:39:12 -0000

The draft that creates the registry owns the initial registry contents
until the registry itself is created.

So, just put the value in the draft's source, and try to avoid re-using a
number for different things during the draft's time as a draft.

-Ben

On Fri, Mar 19, 2021 at 01:26:10PM -0700, Christopher Wood wrote:
> + tls-reg-review
> 
> Good question! Since this is a new registry, I don't see any problem with grabbing 1 to populate it. The registry experts may have a better answer though.
> 
> Best,
> Chris
> 
> On Thu, Mar 18, 2021, at 5:06 PM, Victor Vasiliev wrote:
> > Do I actually get to just use 1, or do I need to ask you to do the 
> > early allocation process?
> > 
> > On Tue, Mar 16, 2021 at 9:50 PM Christopher Wood <caw@heapingbits.net> wrote:
> > > Friendly bump!
> > > 
> > > On Mon, Mar 1, 2021, at 7:52 AM, Christopher Wood wrote:
> > > > Hi Victor,
> > > > 
> > > > On Mon, Mar 1, 2021, at 7:39 AM, Victor Vasiliev wrote:
> > > > > Hi Chris,
> > > > > 
> > > > > This makes sense.  I will update the draft some time after the upcoming 
> > > > > IETF.  Do you want to just add a codepoint reserved for cross-domain 
> > > > > resumption into the draft, or how does that work?
> > > > 
> > > > Good question. I suspect your draft would just add, in the IANA 
> > > > considerations section, something like this:
> > > > 
> > > > ~~~
> > > > This document requests that IANA create a new entry in "TLS Flags" 
> > > > registry with the following parameters:
> > > > 
> > > > - Value: 1
> > > > - Flag Name: "cross_sni_resumption" (or whatever you want to name it)
> > > > - Message: NewSessionTicket
> > > > - Recommended: Y
> > > > - Reference: This document
> > > > ~~~
> > > > 
> > > > (See https://tools.ietf.org/html/draft-ietf-tls-tlsflags-04#section-4)
> > > > 
> > > > > 
> > > > > (sorry for late response, just noticed the part about the draft  submission deadline)
> > > > 
> > > > No problem!
> > > > 
> > > > Best,
> > > > Chris
> > > >
> 
> _______________________________________________
> tls-reg-review mailing list
> tls-reg-review@ietf.org
> https://www.ietf.org/mailman/listinfo/tls-reg-review