rfc/sp-websocket-mapping-01.xml

<?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 according to the following table:</t>

      <t>x-nanomsg-pair for NN_PAIR sockets</t>
      <t>x-nanomsg-req for NN_REQ sockets</t>
      <t>x-nanomsg-rep for NN_REP sockets</t>
      <t>x-nanomsg-pub for NN_PUB sockets</t>
      <t>x-nanomsg-sub for NN_SUB sockets</t>
      <t>x-nanomsg-surveyor for NN_SURVEYOR sockets</t>
      <t>x-nanomsg-respondent for NN_RESPONDENT sockets</t>
      <t>x-nanomsg-push for NN_PUSH sockets</t>
      <t>x-nanomsg-pull for NN_PULL sockets</t>
      <t>x-nanomsg-bus for NN_BUS sockets</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>