Initial version of WebSocke mapping RFC added
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
diff --git a/rfc/sp-websocket-mapping-01.txt b/rfc/sp-websocket-mapping-01.txt
new file mode 100644
index 0000000..acda895
--- /dev/null
+++ b/rfc/sp-websocket-mapping-01.txt
@@ -0,0 +1,113 @@
+
+
+
+
+Internet Engineering Task Force M. Sustrik, Ed.
+Internet-Draft
+Intended status: Informational November 13, 2014
+Expires: May 17, 2015
+
+
+ WebSocket Mapping for Scalability Protocols
+ sp-websocket-mapping-01
+
+Abstract
+
+ This document defines the WebSocket mapping for scalability
+ protocols.
+
+Status of This Memo
+
+ This Internet-Draft is submitted 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 17, 2015.
+
+Copyright Notice
+
+ Copyright (c) 2014 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
+ 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.
+
+
+
+
+
+
+Sustrik Expires May 17, 2015 [Page 1]
+
+Internet-Draft WebSocket mapping for SPs November 2014
+
+
+1. Underlying protocol
+
+ This mapping should be layered on the top of WebSocket protocol as
+ defined in RFC 6455.
+
+2. Connection initiation
+
+ Standard WebSocket handshake is done. Sec-WebSocket-Protocol field
+ MUST be set to "x-nanomsg-pair".
+
+3. Message
+
+ SP message maps directly to WebSocket message. The message can be
+ fragmented as needed. Frame boundaries are ignored by the SP layer.
+
+4. IANA Considerations
+
+ This memo includes no request to IANA.
+
+5. Security Considerations
+
+ The mapping isn't intended to provide any additional security in
+ addition to what WebSocket does. DoS concerns are addressed within
+ the specification.
+
+Author's Address
+
+ Martin Sustrik (editor)
+
+ Email: sustrik@250bpm.com
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Sustrik Expires May 17, 2015 [Page 2]
+
diff --git a/rfc/sp-websocket-mapping-01.xml b/rfc/sp-websocket-mapping-01.xml
new file mode 100644
index 0000000..574d339
--- /dev/null
+++ b/rfc/sp-websocket-mapping-01.xml
@@ -0,0 +1,71 @@
+<?xml version="1.0" encoding="US-ASCII"?>
+<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
+
+<rfc category="info" docName="sp-websocket-mapping-01">
+
+ <front>
+
+ <title abbrev="WebSocket mapping for SPs">
+ WebSocket Mapping for Scalability Protocols
+ </title>
+
+ <author fullname="Martin Sustrik" initials="M." role="editor"
+ surname="Sustrik">
+ <address>
+ <email>sustrik@250bpm.com</email>
+ </address>
+ </author>
+
+ <date month="November" year="2014" />
+
+ <area>Applications</area>
+ <workgroup>Internet Engineering Task Force</workgroup>
+
+ <keyword>WebSocket</keyword>
+ <keyword>SP</keyword>
+
+ <abstract>
+ <t>This document defines the WebSocket mapping for scalability
+ protocols.</t>
+ </abstract>
+
+ </front>
+
+ <middle>
+
+ <section title = "Underlying protocol">
+
+ <t>This mapping should be layered on the top of WebSocket protocol
+ as defined in RFC 6455.</t>
+
+ </section>
+
+ <section title = "Connection initiation">
+
+ <t>Standard WebSocket handshake is done. Sec-WebSocket-Protocol field
+ MUST be set to "x-nanomsg-pair".</t>
+
+ </section>
+
+ <section title = "Message">
+
+ <t>SP message maps directly to WebSocket message. The message can be
+ fragmented as needed. Frame boundaries are ignored by the SP
+ layer.</t>
+
+ </section>
+
+ <section anchor="IANA" title="IANA Considerations">
+ <t>This memo includes no request to IANA.</t>
+ </section>
+
+ <section anchor="Security" title="Security Considerations">
+ <t>The mapping isn't intended to provide any additional security in
+ addition to what WebSocket does. DoS concerns are addressed within
+ the specification.</t>
+ </section>
+
+ </middle>
+
+</rfc>
+
