RFC 8307 on Well-Known URIs for the WebSocket Protocol

rfc-editor@rfc-editor.org Tue, 02 January 2018 23:59 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F86F12D84E for <ietf-announce@ietfa.amsl.com>; Tue, 2 Jan 2018 15:59:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 NWJ2hmYQ5-jY for <ietf-announce@ietfa.amsl.com>; Tue, 2 Jan 2018 15:59:14 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E418A12D811 for <ietf-announce@ietf.org>; Tue, 2 Jan 2018 15:58:58 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 8B49DB80DAD; Tue, 2 Jan 2018 15:58:44 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8307 on Well-Known URIs for the WebSocket Protocol
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180102235844.8B49DB80DAD@rfc-editor.org>
Date: Tue, 02 Jan 2018 15:58:44 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/3zKKJ4BJ9vKH-O9BPnMtR89qk18>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Jan 2018 23:59:16 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8307

        Title:      Well-Known URIs for the WebSocket Protocol 
        Author:     C. Bormann
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2018
        Mailbox:    cabo@tzi.org
        Pages:      3
        Characters: 5945
        Updates:    RFC 6455

        I-D Tag:    draft-bormann-hybi-ws-wk-00.txt

        URL:        https://www.rfc-editor.org/info/rfc8307

        DOI:        10.17487/RFC8307

RFC 5785 defines a path prefix, "/.well-known/", that can be used by
well-known URIs.  It was specifically defined for the "http" and
"https" URI schemes.  The present memo formally updates RFC 6455,
which defines the URI schemes defined for the WebSocket Protocol, to
extend the use of these well-known URIs to those URI schemes.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC