Skip to main content

Well-Known URIs for the WebSocket Protocol
RFC 8307

Revision differences

Document history

Date Rev. By Action
2018-01-02
00 (System)
Received changes through RFC Editor sync (created alias RFC 8307, changed title to 'Well-Known URIs for the WebSocket Protocol', changed abstract to 'RFC 5785 …
Received changes through RFC Editor sync (created alias RFC 8307, changed title to 'Well-Known URIs for the WebSocket Protocol', changed abstract to '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.', changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2018-01-02, changed IESG state to RFC Published, created updates relation between draft-bormann-hybi-ws-wk and RFC 6455)
2018-01-02
00 (System) RFC published
2017-12-21
00 (System) RFC Editor state changed to AUTH48-DONE from AUTH48
2017-12-20
00 (System) RFC Editor state changed to AUTH48 from EDIT
2017-11-15
00 (System) IANA Action state changed to No IC from In Progress
2017-11-15
00 (System) RFC Editor state changed to EDIT
2017-11-15
00 (System) IESG state changed to RFC Ed Queue from Approved-announcement sent
2017-11-15
00 (System) Announcement was received by RFC Editor
2017-11-14
00 (System) IANA Action state changed to In Progress
2017-11-14
00 Cindy Morgan IESG state changed to Approved-announcement sent from IESG Evaluation::AD Followup
2017-11-14
00 Cindy Morgan IESG has approved the document
2017-11-14
00 Cindy Morgan Closed "Approve" ballot
2017-11-14
00 Eric Rescorla [Ballot Position Update] Position for Eric Rescorla has been changed to No Objection from Discuss
2017-08-03
00 Amy Vezza IESG state changed to IESG Evaluation::AD Followup from IESG Evaluation
2017-08-02
00 Ben Campbell [Ballot Position Update] New position, No Objection, has been recorded for Ben Campbell
2017-08-02
00 Alia Atlas [Ballot Position Update] New position, No Objection, has been recorded for Alia Atlas
2017-08-02
00 Kathleen Moriarty [Ballot Position Update] New position, No Objection, has been recorded for Kathleen Moriarty
2017-08-02
00 Deborah Brungard [Ballot Position Update] New position, No Objection, has been recorded for Deborah Brungard
2017-08-02
00 Spencer Dawkins [Ballot Position Update] New position, No Objection, has been recorded for Spencer Dawkins
2017-08-02
00 Suresh Krishnan [Ballot Position Update] New position, No Objection, has been recorded for Suresh Krishnan
2017-08-01
00 Terry Manderson [Ballot Position Update] New position, No Objection, has been recorded for Terry Manderson
2017-08-01
00 Eric Rescorla
[Ballot discuss]
Document: draft-bormann-hybi-ws-wk-00.txt

  It has always been possible to form "ws" and "wss" URIs in such a way
  that they map to …
[Ballot discuss]
Document: draft-bormann-hybi-ws-wk-00.txt

  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], so no new security considerations about this
  are created by now formally making the well-known URI mechanism
  available for "ws" and "wss", as well.
 
  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.

I'm not sure I am persuaded by this. The issue is that clients assume
that these URIs have elevated privilege, so if it's not the case
that WebSockets servers behave this way, we can't retroactively declare
it. Can you explain in more detail why you think this is safe?
2017-08-01
00 Eric Rescorla [Ballot Position Update] New position, Discuss, has been recorded for Eric Rescorla
2017-07-31
00 Adam Roach [Ballot Position Update] New position, No Objection, has been recorded for Adam Roach
2017-07-31
00 Alvaro Retana [Ballot Position Update] New position, No Objection, has been recorded for Alvaro Retana
2017-07-31
00 Mirja Kühlewind [Ballot Position Update] New position, No Objection, has been recorded for Mirja Kühlewind
2017-07-29
00 Warren Kumari [Ballot comment]
Please see Dan Romascanu's OpsDir review for a typo / nit.
2017-07-29
00 Warren Kumari [Ballot Position Update] New position, No Objection, has been recorded for Warren Kumari
2017-07-25
00 Alexey Melnikov Ballot has been issued
2017-07-25
00 Alexey Melnikov [Ballot Position Update] New position, Yes, has been recorded for Alexey Melnikov
2017-07-25
00 Alexey Melnikov Created "Approve" ballot
2017-07-25
00 Alexey Melnikov Ballot writeup was changed
2017-07-21
00 Alexey Melnikov IESG state changed to IESG Evaluation from Waiting for Writeup
2017-07-19
00 (System) IESG state changed to Waiting for Writeup from In Last Call
2017-07-06
00 (System) IANA Review state changed to IANA OK - No Actions Needed from IANA - Review Needed
2017-07-06
00 Sabrina Tanamal
(Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs:

The IANA Services Operator has reviewed draft-bormann-hybi-ws-wk-00.txt, which is currently in Last Call, and has the following comments:

We …
(Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs:

The IANA Services Operator has reviewed draft-bormann-hybi-ws-wk-00.txt, which is currently in Last Call, and has the following comments:

We understand that this document doesn't require any registry actions.

While it's often helpful for a document's IANA Considerations section to remain in place upon publication even if there are no actions, if the authors strongly prefer to remove it, we do not object.

If this assessment is not accurate, please respond as soon as possible.

Thank you,

Sabrina Tanamal
IANA Services Specialist
PTI
2017-07-03
00 Alexey Melnikov Placed on agenda for telechat - 2017-08-03
2017-07-03
00 Alexey Melnikov Changed consensus to Yes from Unknown
2017-07-03
00 Francis Dupont Request for Last Call review by GENART Completed: Ready. Reviewer: Francis Dupont.
2017-06-30
00 Rich Salz Request for Last Call review by SECDIR Completed: Ready. Reviewer: Rich Salz. Sent review to list.
2017-06-26
00 Dan Romascanu Request for Last Call review by OPSDIR Completed: Ready. Reviewer: Dan Romascanu. Sent review to list.
2017-06-24
00 Tero Kivinen Request for Last Call review by SECDIR is assigned to Rich Salz
2017-06-24
00 Tero Kivinen Request for Last Call review by SECDIR is assigned to Rich Salz
2017-06-24
00 Gunter Van de Velde Request for Last Call review by OPSDIR is assigned to Dan Romascanu
2017-06-24
00 Gunter Van de Velde Request for Last Call review by OPSDIR is assigned to Dan Romascanu
2017-06-22
00 Jean Mahoney Request for Last Call review by GENART is assigned to Francis Dupont
2017-06-22
00 Jean Mahoney Request for Last Call review by GENART is assigned to Francis Dupont
2017-06-21
00 Amy Vezza IANA Review state changed to IANA - Review Needed
2017-06-21
00 Amy Vezza
The following Last Call announcement was sent out:

From: The IESG
To: IETF-Announce
CC: alexey.melnikov@isode.com, draft-bormann-hybi-ws-wk@ietf.org
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (Well-known URIs …
The following Last Call announcement was sent out:

From: The IESG
To: IETF-Announce
CC: alexey.melnikov@isode.com, draft-bormann-hybi-ws-wk@ietf.org
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (Well-known URIs for the WebSocket Protocol) to Proposed Standard


The IESG has received a request from an individual submitter to consider the
following document: - 'Well-known URIs for the WebSocket Protocol'
  as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2017-07-19. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

Abstract


  RFC 5785 defines a path prefix, "/.well-known/", that can be used by
  well-known URIs, specifically 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.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-bormann-hybi-ws-wk/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-bormann-hybi-ws-wk/ballot/


No IPR declarations have been submitted directly on this I-D.




2017-06-21
00 Amy Vezza IESG state changed to In Last Call from Last Call Requested
2017-06-21
00 Alexey Melnikov Last call was requested
2017-06-21
00 Alexey Melnikov Last call announcement was generated
2017-06-21
00 Alexey Melnikov Ballot approval text was generated
2017-06-21
00 Alexey Melnikov Ballot writeup was generated
2017-06-21
00 Alexey Melnikov IESG state changed to Last Call Requested from AD Evaluation
2017-06-21
00 Alexey Melnikov IESG state changed to AD Evaluation from Publication Requested
2017-06-21
00 Alexey Melnikov IESG state changed to Publication Requested from AD is watching
2017-05-11
00 Alexey Melnikov Assigned to Applications and Real-Time Area
2017-05-11
00 Alexey Melnikov Responsible AD changed to Alexey Melnikov
2017-05-11
00 Alexey Melnikov Intended Status changed to Proposed Standard
2017-05-11
00 Alexey Melnikov IESG process started in state AD is watching
2017-05-11
00 Alexey Melnikov Stream changed to IETF from None
2017-05-11
00 Carsten Bormann New version available: draft-bormann-hybi-ws-wk-00.txt
2017-05-11
00 (System) New version approved
2017-05-11
00 Carsten Bormann Request for posting confirmation emailed  to submitter and authors: Carsten Bormann
2017-05-11
00 Carsten Bormann Uploaded new revision