One document matched: draft-ivov-dispatch-sdpfrag-02.xml

<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>

<!DOCTYPE rfc SYSTEM "rfc2629.dtd">

<rfc category='std' ipr='trust200902'
     docName='draft-ivov-dispatch-sdpfrag-02'>

<?rfc toc='yes' ?>
<?rfc symrefs='yes' ?>
<?rfc sortrefs='yes'?>
<?rfc iprnotified='no' ?>
<?rfc strict='yes' ?>
<?rfc compact='yes' ?>
  <front>

    <title abbrev='Trickle ICE for SIP'>
      A Session Initiation Protocol (SIP) usage for Trickle ICE
    </title>
    <author initials='E.' surname='Ivov'
            fullname='Emil Ivov'>
      <organization abbrev='Jitsi'>Jitsi</organization>
      <address>
        <postal>
          <street></street>
          <city>Strasbourg</city>
          <code>67000</code>
          <country>France</country>
        </postal>
        <phone>+33 6 72 81 15 55</phone>
        <email>emcho@jitsi.org</email>
      </address>
    </author>
    <author fullname="Adam Roach" initials="A. B." surname="Roach">
      <organization>Mozilla</organization>

      <address>
        <postal>
          <street></street>
          <city>Dallas</city>
          <region>TX</region>
          <code></code>
          <country>US</country>
        </postal>
        <email>adam@nostrum.com</email>
      </address>
    </author>
    <date />
    <abstract>
      <t>
        This document registers the application/sdpfrag Multipurpose
        Internet Mail Extensions (MIME) media type.  This type is
        similar to application/sdp, but allows certain subsets of well
        formed session descriptions, as per the Session Description
        Protocol (SDP), to be represented instead of requiring a
        complete SDP session description. The "a=candidate" lines
        that are incrementally exchanged between Trickle ICE agents are
        one example usage of the application/sdpfrag.
      </t>
    </abstract>
  </front>
  <middle>
    <section title='Introduction'>
      <t>
        The application/sdp MIME media type defined in <xref
        target="RFC4566"/> carries an entire well formed SDP session
        description. Yet, creating such a description may sometimes
        require a relatively long time as, for example, would be the
        case when the Interactive Connectivity Establishment (ICE)
        <xref target="RFC5245"/> protocol is in use and candidates need
        to be acquire in different, often time consuming methods. Some
        applications may therefore choose to use mechanisms like Trickle
        ICE <xref target="I-D.ivov-mmusic-trickle-ice"/> that would allow
        them to send initial session descriptions with only readily
        available information and then exchange candidates only when
        they become available.
      </t>
      <t>
        This document does NOT provide a mechanism to segment an SDP
        session description into multiple pieces for separate transport
        and later reassemble.
      </t>
    </section>
    <section title="Terminology">
      <t>
        The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
        NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
        "OPTIONAL" in this document are to be interpreted as described
        in <xref target="RFC2119"/>.
      </t>
    </section>
    <section title=' Definition: application/sdpfrag'
             anchor='definition'>
      <t>
        A valid application/sdpfrag part is one that could be obtained
        by starting with some valid SDP session description and deleting
        any number of lines.
      </t>
      <t>
        [TODO maybe mention that we can only do frags with the
        declarative parts of an SDP offer/answer and not with the ones
        used in negotiations.]
      </t>
      <t>
        [TODO maybe explain how attributes can be linked to an m line
        or at least say that this will be defined by usages.]
      </t>
    </section>
    <section title='Security Considerations'>
      <t>
        [TODO]
      </t>
    </section>
    <section title='Acknowledgements'>
      <t>
        [TODO]
      </t>
    </section>
  </middle>
  <back>
    <references title='Normative References'>
      <?rfc include="reference.RFC.2119"?>
      <?rfc include="reference.RFC.3264"?>
      <?rfc include="reference.RFC.4566"?>
      <?rfc include="reference.RFC.5245"?>
      <?rfc include="reference.I-D.ivov-mmusic-trickle-ice"?>
    </references>
    <references title='Informative References'>
      <?rfc include="reference.RFC.1918"?>
    </references>
  </back>
</rfc>