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

Yoav Nir <ynir.ietf@gmail.com> Fri, 18 October 2019 18:36 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 1B0D41208E5 for <tls-reg-review@ietfa.amsl.com>; Fri, 18 Oct 2019 11:36:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 HvVZE9MUdBZi for <tls-reg-review@ietfa.amsl.com>; Fri, 18 Oct 2019 11:36:36 -0700 (PDT)
Received: from mail-wr1-x42a.google.com (mail-wr1-x42a.google.com [IPv6:2a00:1450:4864:20::42a]) (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 251951208F1 for <tls-reg-review@ietf.org>; Fri, 18 Oct 2019 11:36:36 -0700 (PDT)
Received: by mail-wr1-x42a.google.com with SMTP id n14so7264410wrw.9 for <tls-reg-review@ietf.org>; Fri, 18 Oct 2019 11:36:36 -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=BMS10+6mOCE8qeTyPFXpbtoIR8xdxN/3GXI0O9llyIM=; b=URu1ULGRCdccfdYD3I7GJn1qh/yYqQe5NVNCe8J5c/11Ej+oCGSUkG9Bn5AsJmNrbY jsJ+rgR/N0wj2ZfqHO2YjdKPQo1o0Y4dcSHBpJklo9TtADbtuR5U0+gTnuJBoc/QZQBt yZSzjFyROgYMvwPK1rdFcO1nT/K/uYW+SxwxhcgtztxoaK4+j9fiZKvaM9e4aEiPVzVI JV4Nhr5Wcumm+HGB3sWaPoFmaH0E78Rw65K+ElRdZTtfVEabGWiknanCnPUOCLtPPJdj C6F0ieZ3d2sd0mS/TiBKX+TVN0O+ppSrSsG4JkOX+TqBXTLCj8Grcc006BJmpvPB+ext m2Tg==
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=BMS10+6mOCE8qeTyPFXpbtoIR8xdxN/3GXI0O9llyIM=; b=JiETWWWayBL8yXP1VQ0Lt76S9cr5O+HXm1S6j96udRnkXUCKZJBD5xaFAmSxfooA0a C0V0fxrAZGZTa4iVnTEBUq5Dxp8GN8bQDF4MybFLrbS04xaOFwjyV/QDLL7nf3mgQcXw WOMHybMveXem3qLcvr7qMsi0tu2EuzSv58mBJmD9DbCsAKcBVwIVmR+oARCMAyoR8Lsx +YSUDzacSrWn6zLrbfOuydaJzD4sLkmhBU9OYNscSTrKP0AZPHGZnR4xOkbLBUyM88Oj VtzbP6RksI7M5q6ijr7shS1iuH5rdIsiVF1KjhUA2ovzhP2r6zTogKCzF+R7c+W6SrsC 1CJA==
X-Gm-Message-State: APjAAAXO/wYf/Jk0JYvuptwbk2V9rHyvST74Q8k18+5WwtsIpPmqj8Qg 0J4pYSDAG1eKY9TR/tStq8p/pNqS
X-Google-Smtp-Source: APXvYqwJN0V22mVG9M5azX2gpz2gPmBEmhpc0pEre5cv4075cm9YZUxeH9fPOc1v2yQ2KhpKu8UVsQ==
X-Received: by 2002:adf:cd88:: with SMTP id q8mr9613191wrj.223.1571423794639; Fri, 18 Oct 2019 11:36:34 -0700 (PDT)
Received: from [192.168.1.12] ([46.120.57.147]) by smtp.gmail.com with ESMTPSA id y19sm5961606wmi.13.2019.10.18.11.36.32 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 18 Oct 2019 11:36:33 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <B8780BD9-84F3-41ED-9EDD-C94F122BB3DE@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_9287FFDC-57B2-44D7-9CC0-41B309A4C07B"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3594.4.19\))
Date: Fri, 18 Oct 2019 21:36:30 +0300
In-Reply-To: <50D9DBC7-2A06-4479-90D5-D3CEA2BD857F@amazon.com>
Cc: "Lee, Alexandra" <alexanl@amazon.com>, "Sharfin, Jared" <sharfinj@amazon.com>, "Gochenaur, Drew" <gochenau@amazon.com>
To: "Thakar, Eeshan" <thakar@amazon.com>, "tls-reg-review@ietf.org" <tls-reg-review@ietf.org>
References: <237DADD1-883D-47C3-88D4-3B39D9843CBC@amazon.com> <73904165-C904-455B-B681-488F7EE676C2@gmail.com> <50D9DBC7-2A06-4479-90D5-D3CEA2BD857F@amazon.com>
X-Mailer: Apple Mail (2.3594.4.19)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls-reg-review/0HXDm6RIdTPwIdLssoo9mnP0H5o>
Subject: Re: [Tls-reg-review] [UNVERIFIED SENDER] Request to Register Value in TLS ALPN Registry
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, 18 Oct 2019 18:36:39 -0000

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> 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://aws.amazon.com/blogs/iot/mqtt-with-tls-client-authentication-on-port-443-why-it-is-useful-and-how-it-works/>
>  
> From: Yoav Nir <ynir.ietf@gmail.com>
> Date: Saturday, August 10, 2019 at 2:08 AM
> To: "Thakar, Eeshan" <thakar@amazon.com>
> Cc: "tls-reg-review@ietf.org" <tls-reg-review@ietf.org>, "Lee, Alexandra" <alexanl@amazon.com>, "Sharfin, Jared" <sharfinj@amazon.com>, "Gochenaur, Drew" <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 <http://public.dhe.ibm.com/software/dw/webservices/ws-mqtt/mqtt-v3r1.html>
>> [2] MQTT 3.1.1 Specification: http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/csprd02/mqtt-v3.1.1-csprd02.html <http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/csprd02/mqtt-v3.1.1-csprd02.html>
>> [3] MQTT 5.0 Specification: 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>
>>  
>  
> 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