[Tls-reg-review] [IANA #1154299] Re: [UNVERIFIED SENDER] Request to Register Value in TLS ALPN Registry

"Sabrina Tanamal via RT" <iana-prot-param@iana.org> Wed, 23 October 2019 23:43 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 2BA1912001A for <tls-reg-review@ietfa.amsl.com>; Wed, 23 Oct 2019 16:43:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.95
X-Spam-Level:
X-Spam-Status: No, score=-3.95 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_MED=-2.3, 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 3qvTPrYySDZq for <tls-reg-review@ietfa.amsl.com>; Wed, 23 Oct 2019 16:43:31 -0700 (PDT)
Received: from smtp01.icann.org (smtp01.icann.org [192.0.33.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 37541120018 for <tls-reg-review@ietf.org>; Wed, 23 Oct 2019 16:43:31 -0700 (PDT)
Received: from request4.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp01.icann.org (Postfix) with ESMTP id 0EFBDE14B8; Wed, 23 Oct 2019 23:43:31 +0000 (UTC)
Received: by request4.lax.icann.org (Postfix, from userid 48) id 0ABFD20488; Wed, 23 Oct 2019 23:43:31 +0000 (UTC)
RT-Owner: sabrina.tanamal
From: "Sabrina Tanamal via RT" <iana-prot-param@iana.org>
Reply-To: iana-prot-param@iana.org
In-Reply-To: <50281700-558A-48AF-BA75-4A36E48EE334@gmail.com>
References: <RT-Ticket-1154299@icann.org> <237DADD1-883D-47C3-88D4-3B39D9843CBC@amazon.com> <73904165-C904-455B-B681-488F7EE676C2@gmail.com> <50D9DBC7-2A06-4479-90D5-D3CEA2BD857F@amazon.com> <B8780BD9-84F3-41ED-9EDD-C94F122BB3DE@gmail.com> <D8E8C333-79BA-4854-92F9-7D55C56F4CD4@akamai.com> <50281700-558A-48AF-BA75-4A36E48EE334@gmail.com>
Message-ID: <rt-4.4.3-21329-1571874210-1634.1154299-37-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #1154299
X-Managed-BY: RT 4.4.3 (http://www.bestpractical.com/rt/)
X-RT-Originator: sabrina.tanamal@icann.org
To: ynir.ietf@gmail.com
CC: tls-reg-review@ietf.org, thakar@amazon.com, sharfinj@amazon.com, rsalz@akamai.com, gochenau@amazon.com, alexanl@amazon.com
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Wed, 23 Oct 2019 23:43:30 +0000
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls-reg-review/Q4uxQIP62U8yzjDipjMo1m27UYA>
Subject: [Tls-reg-review] [IANA #1154299] Re: [UNVERIFIED SENDER] Request to Register Value in TLS ALPN Registry
X-BeenThere: tls-reg-review@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 23 Oct 2019 23:43:34 -0000

Hi all, 

We've added the following entry to the Application-Layer Protocol Negotiation (ALPN) Protocol IDs registry:

Protocol: OASIS Message Queuing Telemetry Transport (MQTT)
Identification Sequence: 0x6d 0x71 0x74 0x74 (“mqtt”)
Reference: [http://docs.oasis-open.org/mqtt/mqtt/v5.0/mqtt-v5.0.html]

Please see
https://www.iana.org/assignments/tls-extensiontype-values

Best regards, 

Sabrina Tanamal
Senior IANA Services Specialist

On Fri Oct 18 18:56:57 2019, ynir.ietf@gmail.com wrote:
> Yup, even IP.
> 
> IANA: Can you please add the following registration?
> 
> Registry name: TLS Application-Layer Protocol Negotiation (ALPN)
> Protocol IDs
> Protocol field should be “OASIS Message Queuing Telemetry Transport
> (MQTT)”
> Identification sequence should be:   0x6d 0x71 0x74 0x74 (“mqtt”)
> Reference should be this document:   http://docs.oasis-
> open.org/mqtt/mqtt/v5.0/mqtt-v5.0.html <http://docs.oasis-
> open.org/mqtt/mqtt/v5.0/mqtt-v5.0.html>
> 
> Thanks.
> 
> Yoav
> (on behalf of the TLS registry review team)
> 
> 
> > On 18 Oct 2019, at 21:44, Salz, Rich <rsalz@akamai.com> wrote:
> >
> > I’m fine with it.
> >
> > Tunneling things through HTTPS has a long history :)
> >
> > From: Yoav Nir <ynir.ietf@gmail.com>
> > Date: Friday, October 18, 2019 at 2:41 PM
> > To: "Thakar, Eeshan" <thakar@amazon.com>om>, "tls-reg-review@ietf.org"
> > <tls-reg-review@ietf.org>
> > Cc: "Lee, Alexandra" <alexanl@amazon.com>om>, "Sharfin, Jared"
> > <sharfinj@amazon.com>om>, "Gochenaur, Drew" <gochenau@amazon.com>
> > Subject: Re: [Tls-reg-review] [UNVERIFIED SENDER] Request to Register
> > Value in TLS ALPN Registry
> >
> > I think it’s fine.
> >
> > Rich?  Nick?  (we need at least two of us to agree)
> >
> > Yoav
> >
> >
> >> On 18 Oct 2019, at 20:30, Thakar, Eeshan <thakar@amazon.com
> >> <mailto:thakar@amazon.com>> wrote:
> >>
> >> Hello,
> >>
> >> Did you get a chance to review the application with the added
> >> context from my email?
> >>
> >> Thanks,
> >>
> >> Eeshan
> >>
> >> From: Thakar, Eeshan <thakar@amazon.com <mailto:thakar@amazon.com>>
> >> Sent: Monday, August 12, 2019 5:13 PM
> >> To: Yoav Nir <ynir.ietf@gmail.com <mailto:ynir.ietf@gmail.com>>
> >> Cc: tls-reg-review@ietf.org <mailto:tls-reg-review@ietf.org>; Lee,
> >> Alexandra <alexanl@amazon.com <mailto:alexanl@amazon.com>>; Sharfin,
> >> Jared <sharfinj@amazon.com <mailto:sharfinj@amazon.com>>; Gochenaur,
> >> Drew <gochenau@amazon.com <mailto:gochenau@amazon.com>>
> >> Subject: Re: [UNVERIFIED SENDER] Re: [Tls-reg-review] Request to
> >> Register Value in TLS ALPN Registry
> >>
> >> Hi Yoav,
> >>
> >> Thanks for taking a look through the request. The current
> >> implementation for the AWS IoT Gateway endpoint does support
> >> HTTP/1.1 and MQTT (3.1 and 3.1.1) on the same port (443) using ALPN
> >> (with a custom ALPN protocol id).
> >> It also supports MQTT on the IANA registered port (8883), but allows
> >> ALPN based MQTT connections on 443 to work around standard firewall
> >> configurations [1].
> >>
> >> The goal with getting the “mqtt” protocol id registered was to have
> >> a common basis for all implementers of gateways that support HTTP
> >> and MQTT (multiple cloud IoT services do so today, albeit not on the
> >> same port) to have a way to accept MQTT traffic on port 443. This is
> >> similar to how CoAP has both an ALPN registered string (“coap”) and
> >> a registered port (5684 for CoAP with TCP/TLS).
> >>
> >> Thanks,
> >>
> >> Eeshan
> >>
> >> [1]: https://aws.amazon.com/blogs/iot/mqtt-with-tls-client-
> >> authentication-on-port-443-why-it-is-useful-and-how-it-works/
> >> <https://urldefense.proofpoint.com/v2/url?u=https-
> >> 3A__aws.amazon.com_blogs_iot_mqtt-2Dwith-2Dtls-2Dclient-
> >> 2Dauthentication-2Don-2Dport-2D443-2Dwhy-2Dit-2Dis-2Duseful-2Dand-
> >> 2Dhow-2Dit-
> >> 2Dworks_&d=DwMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=4LM0GbR0h9Fvx86FtsKI-
> >> w&m=3E_UAQbU2i5rQj4oofQmA2Zn6VVJWCevYQrKZ79iWEM&s=gS3wQv9j7fykgWX5rYj3Juwi-
> >> bASrckP4DIA5dBf2Ec&e=>
> >>
> >> From: Yoav Nir <ynir.ietf@gmail.com <mailto:ynir.ietf@gmail.com>>
> >> Date: Saturday, August 10, 2019 at 2:08 AM
> >> To: "Thakar, Eeshan" <thakar@amazon.com <mailto:thakar@amazon.com>>
> >> Cc: "tls-reg-review@ietf.org <mailto:tls-reg-review@ietf.org>" <tls-
> >> reg-review@ietf.org <mailto:tls-reg-review@ietf.org>>, "Lee,
> >> Alexandra" <alexanl@amazon.com <mailto:alexanl@amazon.com>>,
> >> "Sharfin, Jared" <sharfinj@amazon.com <mailto:sharfinj@amazon.com>>,
> >> "Gochenaur, Drew" <gochenau@amazon.com <mailto:gochenau@amazon.com>>
> >> Subject: [UNVERIFIED SENDER] Re: [Tls-reg-review] Request to
> >> Register Value in TLS ALPN Registry
> >>
> >> On 9 Aug 2019, at 23:45, Thakar, Eeshan
> >> <thakar=40amazon.com@dmarc.ietf.org
> >> <mailto:thakar=40amazon.com@dmarc.ietf.org>> wrote:
> >>
> >>> Type of Assignment:
> >>> Registration of “mqtt” token
> >>>
> >>> Registry:
> >>> Application Layer Protocol Negotiation (ALPN) Protocol ID
> >>>
> >>> Description:
> >>> The mqtt protocol has the protocol version written into the first
> >>> message on a connection. The mqtt server implementations typically
> >>> understand the protocol version based on the fixed header on the
> >>> first message (connect).
> >>>
> >>> Adding this protocol id to the registry will help the community
> >>> since clients wanting to request mqtt as the protocol would have an
> >>> appropriate specification reference to use.
> >>>
> >>> Additional Info:
> >>> [1] MQTT 3.1 Specification:
> >>> http://public.dhe.ibm.com/software/dw/webservices/ws-mqtt/mqtt-
> >>> v3r1.html <https://urldefense.proofpoint.com/v2/url?u=http-
> >>> 3A__public.dhe.ibm.com_software_dw_webservices_ws-2Dmqtt_mqtt-
> >>> 2Dv3r1.html&d=DwMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=4LM0GbR0h9Fvx86FtsKI-
> >>> w&m=3E_UAQbU2i5rQj4oofQmA2Zn6VVJWCevYQrKZ79iWEM&s=cCCKZ-
> >>> lqltftwi8iSb9xnH41GIG7pDOo77inFY0LShI&e=>
> >>> [2] MQTT 3.1.1 Specification: http://docs.oasis-
> >>> open.org/mqtt/mqtt/v3.1.1/csprd02/mqtt-v3.1.1-csprd02.html
> >>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__docs.oasis-
> >>> 2Dopen.org_mqtt_mqtt_v3.1.1_csprd02_mqtt-2Dv3.1.1-
> >>> 2Dcsprd02.html&d=DwMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=4LM0GbR0h9Fvx86FtsKI-
> >>> w&m=3E_UAQbU2i5rQj4oofQmA2Zn6VVJWCevYQrKZ79iWEM&s=PmP61TQmKHzpZMhM8TNDzpcZBqp1fZ8RM7xE05_c9T8&e=>
> >>> [3] MQTT 5.0 Specification: http://docs.oasis-
> >>> open.org/mqtt/mqtt/v5.0/mqtt-v5.0.html
> >>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__docs.oasis-
> >>> 2Dopen.org_mqtt_mqtt_v5.0_mqtt-
> >>> 2Dv5.0.html&d=DwMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=4LM0GbR0h9Fvx86FtsKI-
> >>> w&m=3E_UAQbU2i5rQj4oofQmA2Zn6VVJWCevYQrKZ79iWEM&s=BEoHGVZzaCG6fp19ig2vfDpkz4rJkQhdUEVOG8EtQD0&e=>
> >>>
> >>
> >> Hi, Eeshan.
> >>
> >> I’ve looked through the linked specifications, especially the third
> >> one because it says it replaces the others.
> >>
> >> It says that TCP port 8883 is registered with IANA for MQTT over
> >> TLS, and the IANA registry confirms it.  If you have your own port,
> >> why do you need ALPN?
> >>
> >> ALPN is used to negotiate a particular service (such as HTTP) over a
> >> single port, typically 443.
> >>
> >> So if you were using a server listening on port 443 and serving both
> >> MQTT and HTTP/2 you would need that to distinguish clients that need
> >> MQTT from web browsers that need HTTP/2.
> >>
> >> The linked document does not make any mention of such a server.  Is
> >> this described elsewhere?
> >>
> >> Thanks
> >>
> >> Yoav