IETF Logo Mail Archive

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

Alexey Melnikov <alexey.melnikov@isode.com> Wed, 21 June 2017 15:49 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 AC7F512EB72; Wed, 21 Jun 2017 08:49:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 n8o5ij8YUQhH; Wed, 21 Jun 2017 08:49:57 -0700 (PDT)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 04A4912EB71; Wed, 21 Jun 2017 08:48:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1498060121; d=isode.com; s=june2016; i=@isode.com; bh=EQRj0u9RvCLnA3702jqWQWFCWk5HNTx2YMVwA6PWyNw=; 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=f9rI+UFg8rZhQyA5VEmmh/G49ngA0P14sKQHJOaZuD6sZH1tfgCJE12CJKkgAltmE+nmdM s2IZ5yD3R5gUixL/6qJgGjRgZgOAFYryKqcqwl0qfz1bmcD6BItXkNT8Khdg+wncNt0qjb jbzRlqNZ8flFVtUWlKyBBisaqvP7qw0=;
Received: from [192.168.0.3] (cpc121086-nmal24-2-0-cust54.19-2.cable.virginm.net [77.97.145.55]) by statler.isode.com (submission channel) via TCP with ESMTPSA id <WUqVWAAZuXHD@statler.isode.com>; Wed, 21 Jun 2017 16:48:41 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
To: dispatch@ietf.org, "hybi@ietf.org" <hybi@ietf.org>
Message-ID: <594A9557.9080707@isode.com>
Date: Wed, 21 Jun 2017 16:48:39 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/hybi/xm53w9ktz2qR8-3IZ7HNaH-621o>
Subject: [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: Wed, 21 Jun 2017 15:49:59 -0000

Hi,

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.

I am going to start IETF LC on this document. Please send your comments
to ietf@ietf.org mailing list or reply to this email.

Thank you,
Alexey

v2.23.0 | Report a Bug | By Email