IETF Logo Mail Archive

[Tls-reg-review] [IANA #1113784] General Request for Assignment (tls-extensiontype-values_

"Amanda Baber via RT" <iana-prot-param-comment@iana.org> Thu, 14 June 2018 21:30 UTC

Return-Path: <iana-shared@icann.org>
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 6E58F130E3B for <tls-reg-review@ietfa.amsl.com>; Thu, 14 Jun 2018 14:30:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.93
X-Spam-Level:
X-Spam-Status: No, score=-2.93 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_MED=-2.3, 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 y9t-2t-iY9Fd for <tls-reg-review@ietfa.amsl.com>; Thu, 14 Jun 2018 14:30:33 -0700 (PDT)
Received: from smtp01.icann.org (smtp01.icann.org [192.0.46.81]) (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 CDC1C12D949 for <tls-reg-review@ietf.org>; Thu, 14 Jun 2018 14:30:33 -0700 (PDT)
Received: from request3.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp01.icann.org (Postfix) with ESMTP id 16F58E121E for <tls-reg-review@ietf.org>; Thu, 14 Jun 2018 21:30:33 +0000 (UTC)
Received: by request3.lax.icann.org (Postfix, from userid 48) id D4038C205CC; Thu, 14 Jun 2018 21:30:32 +0000 (UTC)
RT-Owner: amanda.baber
From: Amanda Baber via RT <iana-prot-param-comment@iana.org>
Reply-To: iana-prot-param-comment@iana.org
In-Reply-To: <201806141727.w5EHRaT3013598@ppa5.dc.icann.org>
References: <RT-Ticket-1113784@icann.org> <201806141727.w5EHRaT3013598@ppa5.dc.icann.org>
Message-ID: <rt-4.2.9-18679-1529011832-1543.1113784-9-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #1113784
X-Managed-BY: RT 4.2.9 (http://www.bestpractical.com/rt/)
X-RT-Originator: amanda.baber@icann.org
CC: tls-reg-review@ietf.org
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Thu, 14 Jun 2018 21:30:32 +0000
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls-reg-review/qPJoANoNuLhIZDBJ1b5nlOjzo-c>
Subject: [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
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: Thu, 14 Jun 2018 21:30:35 -0000

Dear TLS experts, 

We're forwarding a request for two Application-Layer Protocol Negotiation (ALPN) Protocol ID registrations on behalf of the requester, as the registry itself doesn't yet link to its new registration instructions. 

We understand that this request will undergo a three-week review before an expert contacts us to let us know whether it's been approved (whereas ordinarily if the request had not been made through us, an expert would contact us only to notify us of an approval). 

If these are approved, please provide the Identification Sequences for the new registrations. 

The link to the new registration instructions will be added to the registry pending the draft-ietf-tls-iana-registry-updates authors' approval of a draft version of the updated registries. 

***

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

***

Best regards,

Amanda Baber
Lead IANA Services Specialist

v2.23.0 | Report a Bug | By Email