IETF Logo Mail Archive

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

Anne van Kesteren <annevk@annevk.nl> Thu, 22 June 2017 16:29 UTC

Return-Path: <annevk@annevk.nl>
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 33B46129AEA; Thu, 22 Jun 2017 09:29:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.52
X-Spam-Level:
X-Spam-Status: No, score=-1.52 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=annevk.nl
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 lb09w-o9k-ED; Thu, 22 Jun 2017 09:29:10 -0700 (PDT)
Received: from homiemail-a14.g.dreamhost.com (homie.mail.dreamhost.com [208.97.132.208]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F761129AE7; Thu, 22 Jun 2017 09:29:09 -0700 (PDT)
Received: from homiemail-a14.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a14.g.dreamhost.com (Postfix) with ESMTP id 6B42339207F; Thu, 22 Jun 2017 09:29:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=annevk.nl; h=mime-version :in-reply-to:references:from:date:message-id:subject:to:cc: content-type; s=annevk.nl; bh=METoWYvKO85ms7Deb3JFmGd8WDs=; b=Q0 ykebSE9QyJpC9HKGrVMF1GCs9d2HmJGzwDmFvLFeW7OMcVn47UtCpa1YMu8X7acz sTphgKeFmksL/9yrTQA3Q80qIdsWi073nKz2XnvOwXRdJkExSeubsXce1C7/v/Qc D9uOLBcnzGPS8d4xev31sMByEglQxYJaFjI5jXkbE=
Received: from mail-yb0-f174.google.com (mail-yb0-f174.google.com [209.85.213.174]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: annevk@annevk.nl) by homiemail-a14.g.dreamhost.com (Postfix) with ESMTPSA id 4AE02392075; Thu, 22 Jun 2017 09:29:09 -0700 (PDT)
Received: by mail-yb0-f174.google.com with SMTP id f192so6257467yba.2; Thu, 22 Jun 2017 09:29:09 -0700 (PDT)
X-Gm-Message-State: AKS2vOyUgY4howhlj5mOgfOXZZhyZQAlbYTrU1ZRn2DSLXDFaTaemcxc ORZr/okEupr3KghSQnYQbCX2N5ywDg==
X-Received: by 10.37.175.17 with SMTP id a17mr2493729ybh.9.1498148948568; Thu, 22 Jun 2017 09:29:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.216.81 with HTTP; Thu, 22 Jun 2017 09:29:08 -0700 (PDT)
In-Reply-To: <594A9557.9080707@isode.com>
References: <594A9557.9080707@isode.com>
From: Anne van Kesteren <annevk@annevk.nl>
Date: Thu, 22 Jun 2017 18:29:08 +0200
X-Gmail-Original-Message-ID: <CADnb78i6wHw+u-Y5JfGpNuODxx30kUB8mcWuK1VDDL6VBTiQ1w@mail.gmail.com>
Message-ID: <CADnb78i6wHw+u-Y5JfGpNuODxx30kUB8mcWuK1VDDL6VBTiQ1w@mail.gmail.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Cc: dispatch@ietf.org, "hybi@ietf.org" <hybi@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hybi/2zbphVqvpgZ6mwU-NTzLaw6UgLs>
Subject: Re: [hybi] 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: Thu, 22 Jun 2017 16:29:15 -0000

On Wed, Jun 21, 2017 at 5:48 PM, Alexey Melnikov
<alexey.melnikov@isode.com> wrote:
> RFC 5785 defined a path prefix, "/.well-known/", that can be used by
> well-known URIs, specifically for the "http" and "https" URI schemes.
> Other URI schemes like "coap" also opted-in into using .well-known.
>
> RFC 6455 defined WebSocket protocol and "ws"/"wss" URI schemes. It
> hasn't however opted-in into using the .well-known registry defined by
> RFC 5785. draft-bormann-hybi-ws-wk-00 is fixing this deficiency.

In practice (and in the specification that supersedes parts of the
RFC) the scheme in use is already http/https:

  https://fetch.spec.whatwg.org/#websocket-protocol


-- 
https://annevankesteren.nl/

v2.23.0 | Report a Bug | By Email