Re: [hybi] [dispatch] Publication request for draft-bormann-hybi-ws-wk-00

Alexey Melnikov <alexey.melnikov@isode.com> Fri, 23 June 2017 10:42 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EBAD129C07; Fri, 23 Jun 2017 03:42:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.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 Npjac0IP0LFK; Fri, 23 Jun 2017 03:42:07 -0700 (PDT)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 7B7BD127180; Fri, 23 Jun 2017 03:42:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1498214526; d=isode.com; s=june2016; i=@isode.com; bh=vqXr8AEY2IPYaxf0W8a70LQF0htxKbkBr0mg3n6Ksek=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=xNhyUPuptu5SVQqmR9YsTBD0ppRCQtsfrp9ClfIA8c2aHvS2AobDx2h0phSHt9kIxOqoPj GiNRSJQl3qTEn6BM+NpW09vwe0oQzIe8E4yeaLqMfLYFiO4YIrOf/b3jK7bU6EoZRa3MUQ xyJtKPDNHR08dnAcNIMD9SEpqMuG3qE=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <WUzwfQAaZngZ@waldorf.isode.com>; Fri, 23 Jun 2017 11:42:06 +0100
To: Adam Rice <ricea@google.com>, Anne van Kesteren <annevk@annevk.nl>
Cc: dispatch@ietf.org, "hybi@ietf.org" <hybi@ietf.org>
References: <594A9557.9080707@isode.com> <CADnb78i6wHw+u-Y5JfGpNuODxx30kUB8mcWuK1VDDL6VBTiQ1w@mail.gmail.com> <1498149228.3653703.1018087584.5D4E9087@webmail.messagingengine.com> <CADnb78gy2C5Lk4RWEkTS4ew_wvOx6vEwV_pNWQkGjYrpxbH19A@mail.gmail.com> <CAHixhFrrVoLAp5YPR8SvvdnH0za-VHasmtjqwjZc4ba2yf8Ysw@mail.gmail.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <6eb360bd-0d5c-4559-85c9-99716cf846ba@isode.com>
Date: Fri, 23 Jun 2017 11:41:36 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
In-Reply-To: <CAHixhFrrVoLAp5YPR8SvvdnH0za-VHasmtjqwjZc4ba2yf8Ysw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------35A2D17180D210AF4059E5D9"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/hybi/-orDJYCYPXWIQYJOurp0z6K2Ddg>
Subject: Re: [hybi] [dispatch] Publication request for draft-bormann-hybi-ws-wk-00
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hybi/>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jun 2017 10:42:09 -0000

On 23/06/2017 11:35, Adam Rice wrote:

> On 23 June 2017 at 03:13, Anne van Kesteren <annevk@annevk.nl 
> <mailto:annevk@annevk.nl>> wrote:
>
>     The /.well-known/ thing only makes sense with respect to the WebSocket
>     handshake, no? And that's already defined to be an HTTP request. So
>     I'm not sure why any /.well-known/ things with regard to HTTP would
>     not already apply. (One of the reasons Fetch made this
>     change/clarification is to make sure HSTS, CSP, etc. would all apply
>     to WebSocket as well.)
>
>
> If understand correctly, this permits a well-known WebSocket endpoint 
> to be registered under /.well-known/, so it's not just about 
> HTTP-compatibility.

Right.
>
> I don't see any problems with the proposal, as long as it's actually 
> going to be used. Is there a list of expected use-cases somewhere?
Sections 7.3 and 7.4 of 
<https://datatracker.ietf.org/doc/draft-ietf-core-coap-tcp-tls/?include_text=1>;.