Internet Engineering Task Force (IETF)                        C. Bormann
Request for Comments: 8307                       Universitaet Bremen TZI
Updates: 6455                                               January 2018
Category: Standards Track
ISSN: 2070-1721
        
Internet Engineering Task Force (IETF)                        C. Bormann
Request for Comments: 8307                       Universitaet Bremen TZI
Updates: 6455                                               January 2018
Category: Standards Track
ISSN: 2070-1721

Well-Known URIs for the WebSocket Protocol

WebSocket协议的著名URI

Abstract

摘要

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.

RFC 5785定义了一个路径前缀“/.well-known/”，该前缀可由知名URI使用。它是专门为“http”和“https”URI方案定义的。本备忘录正式更新了RFC6455，它定义了为WebSocket协议定义的URI方案，以将这些众所周知的URI的使用扩展到这些URI方案。

Status of This Memo

关于下段备忘

This is an Internet Standards Track document.

这是一份互联网标准跟踪文件。

This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841.

本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关互联网标准的更多信息，请参见RFC 7841第2节。

Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc8307.

有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问https://www.rfc-editor.org/info/rfc8307.

Copyright Notice

版权公告

Copyright (c) 2018 IETF Trust and the persons identified as the document authors. All rights reserved.

版权所有（c）2018 IETF信托基金和确定为文件作者的人员。版权所有。

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(https://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。

Table of Contents

目录 

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   2
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   2
   4.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     4.1.  Normative References  . . . . . . . . . . . . . . . . . .   3
     4.2.  Informative References  . . . . . . . . . . . . . . . . .   3
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   3
        
   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   2
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   2
   4.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     4.1.  Normative References  . . . . . . . . . . . . . . . . . .   3
     4.2.  Informative References  . . . . . . . . . . . . . . . . .   3
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   3
1. Introduction
1. 介绍

[RFC5785] defines a path prefix, "/.well-known", that can be used by well-known URIs. It also contains an IANA registry for URI suffixes to be used with this path prefix for forming well-known URIs.

[RFC5785]定义了一个路径前缀“/.well-known”，该前缀可由知名URI使用。它还包含一个用于URI后缀的IANA注册表，该后缀将与此路径前缀一起用于形成众所周知的URI。

In [RFC5785], this mechanism is specifically defined for the "http" and "https" URI schemes (now defined in [RFC7230]). Other URI schemes such as "coap" and "coaps" [RFC7252] have since picked up this mechanism, sharing the registry of URI suffixes with that for HTTP(S).

在[RFC5785]中，这个机制是专门为“http”和“https”URI方案定义的（现在在[RFC7230]中定义）。其他URI方案，如“coap”和“coap”[RFC7252]已经采用了这种机制，将URI后缀的注册中心与HTTP（S）的注册中心共享。

[RFC6455], which defines the URI schemes defined for the WebSocket Protocol, "ws" and "wss", does not define the use of well-known URIs for these URI schemes.

[RFC6455]定义了为WebSocket协议“ws”和“wss”定义的URI方案，但没有定义对这些URI方案使用众所周知的URI。

The present memo formally updates [RFC6455] to extend the use of [RFC5785] well-known URIs to the URI schemes "ws" and "wss".

本备忘录正式更新了[RFC6455]，将[RFC5785]著名URI的使用扩展到URI方案“ws”和“wss”。

Well-known URIs for "ws" and "wss" share the registry for URI suffixes established by [RFC5785]; no change is necessitated by the present memo in the registry or its IANA considerations.

“ws”和“wss”的著名URI共享[RFC5785]建立的URI后缀的注册表；注册处的当前备忘录或IANA考虑事项无需更改。

2. IANA Considerations
2. IANA考虑

This document does not require any IANA actions.

本文件不要求IANA采取任何行动。

3. Security Considerations
3. 安全考虑

The Security Considerations of [RFC5785] apply and need to be considered for all well-known URIs.

[RFC5785]的安全注意事项适用于所有已知的URI，并且需要考虑这些URI。

It has always been possible to form "ws" and "wss" URIs in such a way that they map to well-known HTTP(S) URIs when using the procedure in Section 4 of [RFC6455]; no new security considerations are created by now formally making the well-known URI mechanism available for "ws" and "wss".

在使用[RFC6455]第4节中的程序时，始终可以以这样的方式形成“ws”和“wss”URI，即它们映射到众所周知的HTTP（S）URI；现在正式为“ws”和“wss”提供众所周知的URI机制并没有带来新的安全考虑。

However, with well-known URIs becoming available for the WebSocket Protocol, applications that want to define well-known URI suffixes specifically for WebSocket use also need to consider whether the resources becoming available under the equivalent HTTP(S) URI formed by Section 4 of [RFC6455] pose any information disclosure or other security considerations.

然而，随着为WebSocket Protocol提供的已知URI，想要定义专门用于WebSoCult的URI后缀的应用程序还需要考虑资源是否在[RFC645 5]第4节所形成的等效HTTP（S）URI下可用。提出任何信息披露或其他安全考虑。

4. References
4. 工具书类
4.1. Normative References
4.1. 规范性引用文件

[RFC5785] Nottingham, M. and E. Hammer-Lahav, "Defining Well-Known Uniform Resource Identifiers (URIs)", RFC 5785, DOI 10.17487/RFC5785, April 2010, <https://www.rfc-editor.org/info/rfc5785>.

[RFC5785]诺丁汉，M.和E.Hammer Lahav，“定义众所周知的统一资源标识符（URI）”，RFC 5785，DOI 10.17487/RFC5785，2010年4月<https://www.rfc-editor.org/info/rfc5785>.

[RFC6455] Fette, I. and A. Melnikov, "The WebSocket Protocol", RFC 6455, DOI 10.17487/RFC6455, December 2011, <https://www.rfc-editor.org/info/rfc6455>.

[RFC6455]Fette，I.和A.Melnikov，“WebSocket协议”，RFC 6455，DOI 10.17487/RFC6455，2011年12月<https://www.rfc-editor.org/info/rfc6455>.

4.2. Informative References
4.2. 资料性引用

[RFC7230] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing", RFC 7230, DOI 10.17487/RFC7230, June 2014, <https://www.rfc-editor.org/info/rfc7230>.

[RFC7230]Fielding，R.，Ed.和J.Reschke，Ed.，“超文本传输协议（HTTP/1.1）：消息语法和路由”，RFC 7230，DOI 10.17487/RFC7230，2014年6月<https://www.rfc-editor.org/info/rfc7230>.

[RFC7252] Shelby, Z., Hartke, K., and C. Bormann, "The Constrained Application Protocol (CoAP)", RFC 7252, DOI 10.17487/RFC7252, June 2014, <https://www.rfc-editor.org/info/rfc7252>.

[RFC7252]Shelby，Z.，Hartke，K.，和C.Bormann，“受限应用协议（CoAP）”，RFC 7252，DOI 10.17487/RFC7252，2014年6月<https://www.rfc-editor.org/info/rfc7252>.

Author's Address

作者地址

Carsten Bormann Universitaet Bremen TZI Postfach 330440 Bremen D-28359 Germany

卡斯滕·鲍曼大学不来梅邮政学院330440不来梅D-28359德国 

   Phone: +49-421-218-63921
   Email: cabo@tzi.org
        
   Phone: +49-421-218-63921
   Email: cabo@tzi.org