One document matched: draft-martinsen-ice-ice-timers-00.xml

<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="3"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<rfc category="info" docName="draft-martinsen-ice-ice-timers-00"
     ipr="trust200902">
  <front>
    <title abbrev="ICE Timers">ICE Timers, values and recommendations</title>
    <author fullname="Paal-Erik Martinsen" initials="P.E" surname="Martinsen">
      <organization abbrev="Cisco">Cisco Systems, Inc.</organization>
      <address>
        <postal>
          <street>Philip Pedersens Vei 22</street>
          <city>Lysaker</city>
          <region>Akershus</region>
          <code>1325</code>
          <country>Norway</country>
        </postal>
        <email>palmarti@cisco.com</email>
      </address>
    </author>
    
    <date/>

    <workgroup>ICE</workgroup>

    <abstract>
      <t>
        The ICE set of RFCs contains pacing and timer values. The
        network gear initially used to test and figure out those
        values can now safely be considered obsolete. This document
        describes the current timer values and pacing recommendations
        for the ICE RFCs.
      </t>
    </abstract>
  </front>

  <middle>
    <section anchor="introduction" title="Introduction">
      <t>
        This document describes updated ICE related timing values
        and pacing recommendations. As the world moves on and new
        knowledge is acquired it might be necessary or useful to update
        some of the timing sensitive recommendations in the ICE set of
        RFCs. Rather then updating the entire set of ICE RFCs this
        document will be updated. (How is this done? Obsolete an RFC
        and create a new one? How many bis versions can there be?)
      </t>

    </section>
    
    <section anchor="notation" title="Notational Conventions">
      <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>
      
      <t>
        This document uses terminology defined in <xref
        target="RFC5245"/>.
      </t>
    </section>

    <section anchor="timers" title="Timers">

      <t>
        How to deal with RTO vs just sending a new STUN request with a new TransID? (Implementation differences)
      </t>

    <section anchor="rto" title="RTO">
      <t>
        Since recent advancements in networking and the speed off light
        problem is no longer an issue this timer value can now be set
        to 0.
      </t>
    </section>


    <section anchor="ta" title="Ta">
      <t>
        Some nice text describing the usage and current recommended values here..
      </t>
    </section>

    </section>

    <section anchor="pacing" title="Pacing">
      <section title="Keep-Alive">

      </section>
     
      <section title="Consent">

      </section>

    </section>
    
    <section title="IANA Considerations">
      <t>
        None.
      </t>
    </section>

    <section anchor="ack" title="Acknowledgements">
      <t>
        Todo
      </t>
    </section>
    
  </middle>
  
  <back>
    <references title="Normative References">
      <?rfc include="reference.RFC.2119"?>
      <?rfc include="reference.RFC.5245"?>
       
    </references>

  </back>
</rfc>