One document matched: draft-thomson-mmusic-ice-webrtc-00.xml

<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">

<?rfc strict="yes" ?>
<?rfc toc="yes"?>
<?rfc tocdepth="4"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes" ?>
<?rfc compact="yes" ?>
<?rfc subcompact="no" ?>

<rfc category="std" ipr="trust200902" docName="draft-thomson-mmusic-ice-webrtc-00">
  <front>
    <title abbrev="ICE for WebRTC">
      Using Interactive Connectivity Establishment (ICE) in Web Real-Time Communications (WebRTC)
    </title>

    <author initials="M." surname="Thomson" fullname="Martin Thomson">
      <organization>Microsoft</organization>
      <address>
        <postal>
          <street>3210 Porter Drive</street>
          <city>Palo Alto</city>
          <region>CA</region>
          <code>94304</code>
          <country>US</country>
        </postal>

        <email>martin.thomson@skype.net</email>
      </address>
    </author>

    <date year="2013"/>
    <area>RAI</area>
    <workgroup>MMUSIC</workgroup>
    <keyword>Internet-Draft</keyword>
    <keyword>ICE</keyword>
    <keyword>WebRTC</keyword>
    <keyword>RTCWEB</keyword>
    <keyword>Pacing</keyword>

    <abstract>
      <t>
        Interactive Connectivity Establishment (ICE) has been selected as the basis for
        establishing peer-to-peer UDP flows between Web Real-Time Communication (WebRTC) clients.
        The risks and complications arising from this choice are
        discussed.
      </t>
    </abstract>
  </front>

  <middle>
    <section anchor="intro" title="Introduction">
      <t>
        <xref target="RFC5245">ICE</xref> describes a process whereby peers establish a
        bi-directional UDP flow.  This process has been adopted for use in Web Real-Time
        Communications (WebRTC) for establishing flows to and from web browsers (<xref
        target="I-D.ietf-rtcweb-overview"/>).
      </t>
      <t>
        Properties of ICE are also critical to the security of WebRTC (see Section 4.2.1 of <xref
        target="I-D.ietf-rtcweb-security"/>).
      </t>
      <t>
        The design of RFC 5245 does not fully consider the threat models enabled by the web
        environment.  TBC...
      </t>

      <section anchor="terminology" title="Conventions and Terminology">
        <t>
          In cases where normative language needs to be emphasized, this document falls back on
          established shorthands for expressing interoperability requirements on implementations:
          the capitalized words "MUST", "MUST NOT", "SHOULD" and "MAY".  The meaning of these is
          described in <xref target="RFC2119"/>.
        </t>
      </section>
    </section>
    
    <section title="ICE in a Web Browser">
      <t>
        Details coming...
      </t>
    </section>
    
    <section anchor="algorithm" title="Modified ICE Algorithm">
      <t>
        Details coming...
      </t>
    </section>

    <section anchor="security" title="Security Considerations">
      <t>
        This entire document is about security.
      </t>
    </section>

    <section anchor="ack" title="Acknowledgements">
      <t>
        The bulk of the algorithm described in this document came out of a discussion with Emil Ivov
        and Pal-Erik Martinsen.  Eric Rescorla and Bernard Aboba provided some feedback on *mumble*.
      </t>
    </section>

    <!--
        <appendix title="Change Log">
        <t>[[The RFC Editor is requested to remove this section at publication.]]</t>
        <t>Changes since -0-1:
        <list style="symbols">
        <t>Document created.</t>
        </list>
        </t>
        </appendix>
    -->
  </middle>

  <back>

    <references title="Normative References">
      <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml"?>
      <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.5245.xml"?>
      <?rfc include="http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ivov-mmusic-trickle-ice.xml"?>
    </references>
    <references title="Informative References">
      <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.5389.xml"?>
      <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.5766.xml"?>
      <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.6454.xml"?>
      <?rfc include="http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-rtcweb-overview.xml"?>
      <?rfc include="http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-rtcweb-security.xml"?>
      <?rfc include="http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-rtcweb-security-arch.xml"?>
      <?rfc include="http://xml.resource.org/public/rfc/bibxml3/reference.I-D.muthu-behave-consent-freshness.xml"?>
      <?rfc include="http://xml.resource.org/public/rfc/bibxml3/reference.I-D.martinsen-mmusic-malice.xml"?>
    </references>
  </back>
</rfc>