HyBi Working Group J. Tamplin
Internet-Draft T. Yoshino
Intended status: Standards Track Google, Inc.
Expires: November 16, 2013 May 15, 2013
A Multiplexing Extension for WebSockets
draft-ietf-hybi-websocket-multiplexing-10
Abstract
The WebSocket Protocol [RFC6455] requires a new transport connection
for every WebSocket connection. This presents a scalability problem
when many clients connect to the same server, and is made worse by
having multiple clients running in different tabs of the same user
agent. This extension provides a way for separate logical WebSocket
connections to share an underlying transport connection.
Please send feedback to the hybi@ietf.org mailing list.
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 16, 2013.
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://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
Tamplin & Yoshino Expires November 16, 2013 [Page 1]
Internet-Draft A Multiplexing Extension for WebSockets May 2013
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.
Table of Contents
1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Physical Connection and Logical Channels . . . . . . . . . 3
2. Conformance Requirements . . . . . . . . . . . . . . . . . . . 4
3. Extension Negotiation . . . . . . . . . . . . . . . . . . . . 5
4. Interaction with other Extensions / Framing Mechanisms . . . . 6
4.1. Ordering Extensions . . . . . . . . . . . . . . . . . . . 6
4.1.1. Efficiency . . . . . . . . . . . . . . . . . . . . . . 6
4.1.2. Security . . . . . . . . . . . . . . . . . . . . . . . 7
5. Multiplexed Connections . . . . . . . . . . . . . . . . . . . 8
6. Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . 9
6.1. New Channel Slot . . . . . . . . . . . . . . . . . . . . . 9
6.2. Send Quota . . . . . . . . . . . . . . . . . . . . . . . . 9
7. Framing . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
8. Encapsulation . . . . . . . . . . . . . . . . . . . . . . . . 13
9. Multiplex Control Blocks . . . . . . . . . . . . . . . . . . . 15
9.1. Number Encoding in Multiplex Control Blocks . . . . . . . 16
9.2. AddChannelRequest . . . . . . . . . . . . . . . . . . . . 17
9.3. AddChannelResponse . . . . . . . . . . . . . . . . . . . . 20
9.4. FlowControl . . . . . . . . . . . . . . . . . . . . . . . 22
9.5. DropChannel . . . . . . . . . . . . . . . . . . . . . . . 23
9.5.1. Drop Reason Codes . . . . . . . . . . . . . . . . . . 24
9.6. NewChannelSlot . . . . . . . . . . . . . . . . . . . . . . 27
10. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
11. Client Behavior . . . . . . . . . . . . . . . . . . . . . . . 31
12. Buffering . . . . . . . . . . . . . . . . . . . . . . . . . . 32
13. Fairness . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
14. Proxies . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
15. Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
16. Close the Logical Channel . . . . . . . . . . . . . . . . . . 36
17. Fail the Logical Channel . . . . . . . . . . . . . . . . . . . 37
18. Fail the Physical Connection . . . . . . . . . . . . . . . . . 38
19. Operations and Events on Multiplexed Connection . . . . . . . 39
20. Security Considerations . . . . . . . . . . . . . . . . . . . 40
datatracker.ietf.org