<references title="Informative References">
    <reference anchor="RFC2629">
        <front>
            <title>Writing I-Ds and RFCs using XML</title>
            <author initials="M" surname="Rose" fullname="Marshall T. Rose">
                <organization>Invisible Worlds, Inc.</organization>
                <address>
                    <postal>
                        <street>660 York Street</street>
                        <city>San Francisco</city>
                        <region>CA</region><code>94110</code>
                        <country>US</country>
                    </postal>
                    <phone>+1 415 695 3975</phone>
                    <email>mrose@not.invisible.net</email>
                    <uri>http://invisible.net/</uri>
                </address>
            </author>
            <date year="1999" month="June"/>
            <area>General</area>
            <keyword>RFC</keyword>
            <keyword>Request for Comments</keyword>
            <keyword>I-D</keyword>
            <keyword>Internet-Draft</keyword>
            <keyword>XML</keyword>
            <keyword>Extensible Markup Language</keyword>
            <abstract>
                <t>This memo presents a technique for using XML (Extensible Markup Language) as a source format for documents in the Internet-Drafts (I-Ds) and Request for Comments (RFC) series.</t>
            </abstract>
        </front>
        <seriesInfo name="RFC" value="2629"/>
        <format type="TXT" octets="48677" target="http://www.rfc-editor.org/rfc/rfc2629.txt"/>
        <format type="HTML" octets="71741" target="http://xml.resource.org/public/rfc/html/rfc2629.html"/>
        <format type="XML" octets="53481" target="http://xml.resource.org/public/rfc/xml/rfc2629.xml"/>
    </reference> 
    <reference anchor="RFC3552">
        <front>
        <title>Guidelines for Writing RFC Text on Security Considerations</title>
        <author initials="E." surname="Rescorla" fullname="E. Rescorla">
            <organization/>
        </author>
        <author initials="B." surname="Korver" fullname="B. Korver">
            <organization/>
        </author>
        <date year="2003" month="July"/>
        <abstract>
            <t>All RFCs are required to have a Security Considerations section.  Historically, such sections have been relatively weak.  This document provides guidelines to RFC authors on how to write a good Security Considerations section.  This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
            </t>
        </abstract>
        </front>
        <seriesInfo name="BCP" value="72"/>
        <seriesInfo name="RFC" value="3552"/>
        <format type="TXT" octets="110393" target="http://www.rfc-editor.org/rfc/rfc3552.txt"/>
    </reference> 
    <reference anchor="I-D.ietf-avt-rtcp-port-for-ssm">
        <front>
            <title>RTP Control Protocol (RTCP) Port for Source-Specific Multicast (SSM) Sessions</title>
            <author initials="A" surname="Begen" fullname="Ali Begen">
                <organization/>
            </author>
            <date month="December" day="15" year="2010"/>
            <abstract>
                <t>The Session Description Protocol (SDP) has an attribute that allows RTP applications to specify an address and a port associated with the RTP Control Protocol (RTCP) traffic.  In RTP-based source-specific multicast (SSM) sessions, the same attribute is used to designate the address and the RTCP port of the Feedback Target in the SDP description.  However, the RTCP port associated with the SSM session itself cannot be specified by the same attribute to avoid ambiguity, and thus, is required to be derived from the "m=" line of the media description.  Deriving the RTCP port from the "m=" line imposes an unnecessary restriction.  This document removes this restriction by introducing a new SDP attribute.</t>
            </abstract>
        </front>
        <seriesInfo name="Internet-Draft" value="draft-ietf-avt-rtcp-port-for-ssm-04"/>
        <format type="TXT" target="http://www.ietf.org/internet-drafts/draft-ietf-avt-rtcp-port-for-ssm-04.txt"/>
    </reference> 
    <reference anchor='W3C.REC-voicexml20-20040316'
	       target='http://www.w3.org/TR/2004/REC-voicexml20-20040316'>
       <front>
	  <title>Voice Extensible Markup Language (VoiceXML) Version 2.0</title>
	  <author initials='K.' surname='Rehor' fullname='Ken Rehor'>
	     <organization />
	  </author>
	  <author initials='J.' surname='Ferrans' fullname='Jim Ferrans'>
	     <organization />
	  </author>
	  <author initials='S.' surname='Tryphonas' fullname='Steph Tryphonas'>
	     <organization />
	  </author>
	  <author initials='A.' surname='Hunt' fullname='Andrew Hunt'>
	     <organization />
	  </author>
	  <author initials='D. C.' surname='Burnett' fullname='Daniel C. Burnett'>
	     <organization />
	  </author>
	  <author initials='B.' surname='Lucas' fullname='Bruce Lucas'>
	     <organization />
	  </author>
	  <author initials='S.' surname='McGlashan' fullname='Scott McGlashan'>
	     <organization />
	  </author>
	  <author initials='B.' surname='Porter' fullname='Brad Porter'>
	     <organization />
	  </author>
	  <author initials='P.' surname='Danielsen' fullname='Peter Danielsen'>
	     <organization />
	  </author>
	  <author initials='J.' surname='Carter' fullname='Jerry Carter'>
	     <organization />
	  </author>
	  <date month='March' day='16' year='2004' />
       </front>

       <seriesInfo name='World Wide Web Consortium Recommendation' value='REC-voicexml20-20040316' />
       <format type='HTML' target='http://www.w3.org/TR/2004/REC-voicexml20-20040316' />
    </reference>
    <reference anchor='RFC3424'>
       <front>
	  <title>IAB Considerations for UNilateral Self-Address Fixing (UNSAF) Across Network Address Translation</title>
	  <author initials='L.' surname='Daigle' fullname='L. Daigle'>
	     <organization /></author>
	  <author>
	     <organization>IAB</organization></author>
	  <date year='2002' month='November' />
	  <abstract>
	     <t>As a result of the nature of Network Address Translation (NAT) Middleboxes, communicating endpoints that are separated by one or more NATs do not know how to refer to themselves using addresses that are valid in the addressing realms of their (current and future) peers.  Various proposals have been made for "UNilateral Self-Address Fixing (UNSAF)" processes.  These are processes whereby some originating endpoint attempts to determine or fix the address (and port) by which it is known to another endpoint - e.g., to be able to use address data in the protocol exchange, or to advertise a public address from which it will receive connections.  This document outlines the reasons for which these proposals can be considered at best as short term fixes to specific problems and the specific issues to be carefully evaluated before creating an UNSAF proposal.  This memo provides information for the Internet community.</t></abstract></front>
	  <seriesInfo name='RFC' value='3424' />
	  <format type='TXT' octets='18165' target='http://www.rfc-editor.org/rfc/rfc3424.txt' />
    </reference>
    <reference anchor='Erratum3657' quote-title="false">
       <front>
	  <title>RFC Errata, Erratum 3657, RFC 2978</title>
       <date/>
       <abstract/>
       <seriesInfo name='RFC Errata' value='3657' />
       </front>
    </reference>
      <reference anchor="INITIALS">
	<?rfc multiple-initials="no"?>
        <front>
          <title>All initial sets, no PI</title>
          <author initials="J" surname="Doe"><organization/></author>
          <author initials="A." surname="Doe"><organization/></author>
          <author initials="B D" surname="Doe"><organization/></author>
          <author initials="C. D." surname="Doe"><organization/></author>
          <author initials="D.D." surname="Doe"><organization/></author>
          <author initials="" surname="Doe"><organization/></author>
          <author initials="E D." surname="Doe"><organization/></author>
          <author initials="F.D" surname="Doe"><organization/></author>
          <author initials="G. D" surname="Doe"><organization/></author>
          <date year="2015" month="may"/>
          <abstract><t>This is a fun document.</t></abstract>
        </front>
        <seriesInfo name='RFC' value='7539'/>
        <seriesInfo name='DOI' value='10.17487/RFC7539'/>
      </reference>

      <reference anchor="INITIALS-PI">
	<?rfc multiple-initials="yes"?>
        <front>
          <title>All initial sets, with PI</title>
          <author initials="J" surname="Doe"><organization/></author>
          <author initials="A." surname="Doe"><organization/></author>
          <author initials="B D" surname="Doe"><organization/></author>
          <author initials="C. D." surname="Doe"><organization/></author>
          <author initials="D.D." surname="Doe"><organization/></author>
          <author initials="" surname="Doe"><organization/></author>
          <author initials="E D." surname="Doe"><organization/></author>
          <author initials="F.D" surname="Doe"><organization/></author>
          <author initials="G. D" surname="Doe"><organization/></author>
          <date year="2015" month="may"/>
          <abstract><t>This is a fun document.</t></abstract>
        </front>
        <seriesInfo name='RFC' value='7539'/>
        <seriesInfo name='DOI' value='10.17487/RFC7539'/>
      </reference>

      <reference anchor="INITIALS2">
	<?rfc multiple-initials="yes"?>
        <front>
          <title>Lots of authors</title>
          <author initials="J. D." surname="Doe"><organization/></author>
          <author initials="A" surname="Doe"><organization/></author>
          <date year="2015" month="may"/>
          <abstract><t>This is a fun document.</t></abstract>
        </front>
        <seriesInfo name='RFC' value='7539'/>
        <seriesInfo name='DOI' value='10.17487/RFC7539'/>
          </reference>
          
      <reference anchor="INITIALS3">
        <front>
          <title>Lots of authors</title>
          <author initials="J. D." surname="Doe"><organization/></author>
          <author initials="B. D." surname="Doe"><organization/></author>
          <date year="2015" month="may"/>
          <abstract><t>This is a fun document.</t></abstract>
        </front>
        <seriesInfo name='RFC' value='7539'/>
        <seriesInfo name='DOI' value='10.17487/RFC7539'/>
      </reference>

      <reference anchor="INITIALS4">
        <front>
          <title>Lots of authors</title>
          <author initials="J. D." surname="Doe"><organization/></author>
          <author initials="" surname="Doe"><organization/></author>
          <date year="2015" month="may"/>
          <abstract><t>This is a fun document.</t></abstract>
        </front>
        <seriesInfo name='RFC' value='7539'/>
        <seriesInfo name='DOI' value='10.17487/RFC7539'/>
      </reference>
      <reference anchor="SDO-3GPP" target="http://www.3gpp.org/">
        <front>
          <title>3GPP Home Page</title>
          <author/>
          <date/>
        </front>
      </reference>
</references>
