Re: [Tls-reg-review] [IANA #1113784] General Request for Assignment (tls-extensiontype-values)

Yoav Nir <ynir.ietf@gmail.com> Sat, 23 June 2018 09:26 UTC

Return-Path: <ynir.ietf@gmail.com>
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 DD34D130E03 for <tls-reg-review@ietfa.amsl.com>; Sat, 23 Jun 2018 02:26:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 0KvVjVAJNTvN for <tls-reg-review@ietfa.amsl.com>; Sat, 23 Jun 2018 02:25:59 -0700 (PDT)
Received: from mail-wr0-x234.google.com (mail-wr0-x234.google.com [IPv6:2a00:1450:400c:c0c::234]) (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 5A379130DC6 for <tls-reg-review@ietf.org>; Sat, 23 Jun 2018 02:25:59 -0700 (PDT)
Received: by mail-wr0-x234.google.com with SMTP id o12-v6so8856247wrm.12 for <tls-reg-review@ietf.org>; Sat, 23 Jun 2018 02:25:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=rFvJMUblZLnQ1GY674JsB9WSdZaiGXz98Awx/cSUDH0=; b=jt5pO3f9PxwX7na33aasnxFhvLefiT9umoRWatpAeHl0zGDj1rFSyvldomw58pxqwY S7qdAQgaezeIMWLN938daBWMKD/x1Yko169qmbLaPdNUYtSYHOmq0ERZVXSv3b60NYhg oO2uXc9Z6ytCqkwBACfGhaBop5cTy1iKtckF4YCnC6u+2RqdxUEozMegfm469OQVlnWr bgGxZ7JxZKUpuCGptJFwm5Hyf+YHRdJ0xUedTk4vL8nj/A4P4TUUZQO0xU/zBxU4A/sr faJFYy6/SVn9Bb4RYon5ZNMRTnRoBAtWrYL11dQSCIz77n+nBTRTLIUOG/vvvbCeSvWq +hyA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=rFvJMUblZLnQ1GY674JsB9WSdZaiGXz98Awx/cSUDH0=; b=a0NViEBWNifsB6IDwt5Ws75yqpNenzyTVYgcsIf6bDEIIyDALXee70i7Sf7AEqWqj4 VsT75XBxdkxWLlneeIBGLEb0ql2LTwI430iMLQPNodhyoXws9SYcf0j57wLJtwp5yWKj M97g8dmvAGBclpK7YIkeiebubVb6p92B1IXOQ5OKyo5oSq8ZzVx2zWZTFJ8q5BDDrCKA 2N7x/RMBdemILzZayDrhRz1js2N6brtWu7WAOXecJ0YWXqoUZ0m7juLE57FspOyLJYgu 4YpsBlv7nuH1rIloPaqG5p+fC18K/lAU0TXMnkdm/8vxdmST9B6BhCjj7o4IO0g/Vr5a 7VqA==
X-Gm-Message-State: APt69E0ELAQqsIZd8eOgI3S+sVBHx3Uej9rahRpEOnXgQP1uYQF9bIuM KGxgs6VQrHTGky2GHhjy8HN4FwRM
X-Google-Smtp-Source: AAOMgpeRyoDLrit3L3EcsJ8UZ1F1fZayuy00rdlLZAVD5Xiyifwz++Eapz/kYDLyJQeh9cxJnGm21Q==
X-Received: by 2002:adf:ad38:: with SMTP id p53-v6mr3273626wrc.10.1529745957861; Sat, 23 Jun 2018 02:25:57 -0700 (PDT)
Received: from [192.168.1.17] ([46.120.57.147]) by smtp.gmail.com with ESMTPSA id n12-v6sm5713058wro.13.2018.06.23.02.25.55 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 23 Jun 2018 02:25:56 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <A4DDDAC6-3628-4969-8B52-D6A4157A96A1@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_1EE67F42-16ED-41EA-9788-C5AE5B30F733"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\))
Date: Sat, 23 Jun 2018 12:25:53 +0300
In-Reply-To: <rt-4.2.9-2880-1529713069-1524.1113784-9-0@icann.org>
Cc: yoav@yoav.ws, ilya@igvita.com, mbishop@evequefou.be, tls-reg-review@ietf.org
To: iana-prot-param-comment@iana.org
References: <RT-Ticket-1113784@icann.org> <201806141727.w5EHRaT3013598@ppa5.dc.icann.org> <rt-4.2.9-18679-1529011992-591.1113784-6-0@icann.org> <SN6PR08MB39491BDB1095AA271ADB05C9DA750@SN6PR08MB3949.namprd08.prod.outlook.com> <rt-4.2.9-13018-1529700115-314.1113784-9-0@icann.org> <rt-4.2.9-2880-1529713069-1524.1113784-9-0@icann.org>
X-Mailer: Apple Mail (2.3445.8.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls-reg-review/p5FFy-fEpEXR_pwh_bfXDUEvHAw>
Subject: Re: [Tls-reg-review] [IANA #1113784] General Request for Assignment (tls-extensiontype-values)
X-BeenThere: tls-reg-review@ietf.org
X-Mailman-Version: 2.1.26
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://www.ietf.org/mailman/private/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: Sat, 23 Jun 2018 09:26:02 -0000

Hi, Amanda.

I haven’t seen the original email, and can’t find it in my inbox.

Anyway, the assignments seem fine to me.

Rich?  Nick?

Yoav

> On 23 Jun 2018, at 3:17, Amanda Baber via RT <iana-prot-param-comment@iana.org> wrote:
> 
> Hi Mike,
> 
> Our understanding is that the review period for TLS requests is three weeks:
> 
> https://tools.ietf.org/html/draft-ietf-tls-iana-registry-updates-05#section-18
> 
> I can confirm that the message below was received by the mailing list.
> 
> Best regards,
> 
> Amanda Baber
> Lead IANA Services Specialist
> 
> On Fri Jun 22 20:41:55 2018, mbishop@evequefou.be wrote:
>> I haven't seen any follow-up e-mails regarding this.  Is there any
>> other information required in order to add this registration?  For
>> additional reference, https://github.com/w3c/resource-
>> timing/issues/122 and
>> https://bugs.chromium.org/p/chromium/issues/detail?id=780640#c6 are
>> the issues where this gap in the registry is causing questions.
>> 
>> -----Original Message-----
>> From: Amanda Baber via RT [mailto:iana-prot-param@iana.org]
>> Sent: Thursday, June 14, 2018 2:33 PM
>> To: Mike Bishop <mbishop@evequefou.be>
>> Subject: [IANA #1113784] General Request for Assignment (tls-
>> extensiontype-values_
>> 
>> Dear Mike,
>> 
>> Thank you for contacting us. We've sent this on to the new team of
>> IESG-designated experts. The Application-Layer Protocol Negotiation
>> (ALPN) Protocol IDs registry will be updated soon to include a link to
>> recently-approved document draft-ietf-tls-iana-registry-updates, which
>> provides new instructions for submitting registration requests for
>> some of the TLS registries. Specifically, in the future, new requests
>> should be sent to a mailing list (rather than IANA) for a three-week
>> review period. The experts will then contact us if they approve a
>> registration.
>> 
>> Best regards,
>> 
>> Amanda Baber
>> Lead IANA Services Specialist
>> 
>> On Thu Jun 14 17:27:37 2018, mbishop@evequefou.be wrote:
>>> 
>>> Contact Name:
>>> Mike Bishop
>>> 
>>> Contact Email:
>>> mbishop@evequefou.be
>>> 
>>> Type of Assignment:
>>> Registration of "http/0.9" and "http/1.0" tokens (both protocols are
>>> defined by https://tools.ietf.org/html/rfc1945)
>>> 
>>> Registry:
>>> Application-Layer Protocol Negotiation (ALPN) Protocol ID
>>> 
>>> Description:
>>> These legacy protocols are used in testing and by older server
>>> implementations and these tokens are already used in certain cases.
>>> The W3C resource-timing specification uses the ALPN registry as a
>>> reference for possible protocol values, and there has been some
>>> confusion caused by the fact that these tokens aren't actually
>>> registered.
>>> 
>>> It would simplify the community's life if these tokens, already in de
>>> facto use, were actually registered and had an appropriate
>>> specification reference.
>>> 
>>> Additional Info:
>>> http://www.iana.org/go/rfc7301
>> 
>> 
>> 
> 
> 
> 
> _______________________________________________
> tls-reg-review mailing list
> tls-reg-review@ietf.org
> https://www.ietf.org/mailman/listinfo/tls-reg-review