updating missing/broken references

This commit is contained in:
Matthew A. Miller 2016-01-20 10:00:42 -07:00
parent 40548a53f0
commit f496bcda0e
3 changed files with 17 additions and 2 deletions

View File

@ -25,6 +25,12 @@
<shortname>ssn</shortname>
&ianpaterson;
&stpeter;
<revision>
<version>1.2</version>
<date>2016-01-20</date>
<initials>XEP Editor (mam)</initials>
<remark><p>Update missing 'xmppsipim' reference to RFC 7572.</p></remark>
</revision>
<revision>
<version>1.2</version>
<date>2008-01-14</date>
@ -666,7 +672,7 @@ PENDING o---------------+
<p>However, the receiving party MAY assume that the other client will <em>not</em> be able to continue the session. <note>In general, if a party is not subscribing to the other party's presence then it will never assume the other party is is unable to continue a session.</note> In that case it MUST explicitly terminate the session (see <link url='#terminate'>Terminating a Session</link>) -- since its assumption could be incorrect. If after terminating the session the receiving party later receives available presence (i.e., a &PRESENCE; stanza with no 'type' attribute) from that same resource or another resource associated with the other party and the receiving party desires to restart the session, then it MUST initiate a new session (including a newly-generated ThreadID) with the other party. It MUST NOT renegotiate parameters for the terminated session. (Note: This is consistent with the handling of chat states as specified in <cite>XEP-0085</cite>.)</p>
</section2>
<section2 topic='Mapping to SIP' anchor='impl-sip'>
<p>When mapping instant messaging flows to SIP, implementations SHOULD adhere to &xmppsipim;.</p>
<p>When mapping instant messaging flows to SIP, implementations SHOULD adhere to &rfc7572;.</p>
<p>In addition, the following mappings apply to chat session negotiation:</p>
<ul>
<li>Initiation of a negotiated chat session maps to the semantics of the SIP INVITE method.</li>

View File

@ -21,6 +21,12 @@
<supersededby/>
<shortname>NOT_YET_ASSIGNED</shortname>
&stpeter;
<revision>
<version>0.1.1</version>
<date>2016-01-20</date>
<initials>XEP Editor (mam)</initials>
<remark><p>Updated missing 'ice-tcp' reference to RFC 6544.</p></remark>
</revision>
<revision>
<version>0.1</version>
<date>2008-06-18</date>
@ -42,7 +48,7 @@
<li>Two endpoints want to enforce end-to-end encryption</li>
<li>Two endpoints want to send a high volume of XMPP traffic but the intermediate servers enforce rate limits</li>
</ul>
<p>The first scenario is addressed by &xep0174;. The second and third scenarios are addressed by &xep0247;. Both of those technologies result in the establishment of a direct or mediated connection between two endpoints, such as a direct TCP connection, a bytestream through SOCKS5 (&xep0065;) or XMPP itself (&xep0047;), or other future transport methods such as &ice-tcp;.</p>
<p>The first scenario is addressed by &xep0174;. The second and third scenarios are addressed by &xep0247;. Both of those technologies result in the establishment of a direct or mediated connection between two endpoints, such as a direct TCP connection, a bytestream through SOCKS5 (&xep0065;) or XMPP itself (&xep0047;), or other future transport methods such as &rfc6544;.</p>
<p>Once two endpoints have opened a direct or mediated connection, they can establish an XML stream over that connection for end-to-end "("e2e") communication. We call this an "e2e stream".</p>
</section1>

View File

@ -566,6 +566,7 @@ THE SOFTWARE.
<!ENTITY rfc4571 "<span class='ref'><link url='http://tools.ietf.org/html/rfc4571'>RFC 4571</link></span> <note>RFC 4571: Framing Real-time Transport Protocol (RTP) and RTP Control Protocol (RTCP) Packets over Connection-Oriented Transport &lt;<link url='http://tools.ietf.org/html/rfc4571'>http://tools.ietf.org/html/rfc4571</link>&gt;.</note>" >
<!ENTITY rfc4572 "<span class='ref'><link url='http://tools.ietf.org/html/rfc4572'>RFC 4572</link></span> <note>RFC 4572: Connection-Oriented Media Transport over the Transport Layer Security (TLS) Protocol in the Session Description Protocol (SDP) &lt;<link url='http://tools.ietf.org/html/rfc4572'>http://tools.ietf.org/html/rfc4572</link>&gt;.</note>" >
<!ENTITY rfc4575 "<span class='ref'><link url='http://tools.ietf.org/html/rfc4575'>RFC 4575</link></span> <note>RFC 4575: A Session Initiation Protocol (SIP) Event Package for Conference State &lt;<link url='http://tools.ietf.org/html/rfc4575'>http://tools.ietf.org/html/rfc4575</link>&gt;.</note>" >
<!ENTITY rfc4579 "<span class='ref'><link url='http://tools.ietf.org/html/rfc4579'>RFC 4579</link></span> <note>RFC 4579: Session Initiation Protocol (SIP) Call Control - Conferencing for User Agents &lt;<link url='http://tools.ietf.org/html/rfc4579'>http://tools.ietf.org/html/rfc4579</link>&gt;.</note>" >
<!ENTITY rfc4585 "<span class='ref'><link url='http://tools.ietf.org/html/rfc4585'>RFC 4585</link></span> <note>RFC 4585: Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF) &lt;<link url='http://tools.ietf.org/html/rfc4585'>http://tools.ietf.org/html/rfc4585</link>&gt;.</note>" >
<!ENTITY rfc4616 "<span class='ref'><link url='http://tools.ietf.org/html/rfc4616'>RFC 4616</link></span> <note>RFC 4616: The PLAIN Simple Authentication and Security Layer (SASL) Mechanism &lt;<link url='http://tools.ietf.org/html/rfc4616'>http://tools.ietf.org/html/rfc4616</link>&gt;.</note>" >
<!ENTITY rfc4622 "<span class='ref'><link url='http://tools.ietf.org/html/rfc4622'>RFC 4622</link></span> <note>RFC 4622: Internationalized Resource Identifiers (IRIs) and Uniform Resource Identifiers (URIs) for the Extensible Messaging and Presence Protocol (XMPP) &lt;<link url='http://tools.ietf.org/html/rfc4622'>http://tools.ietf.org/html/rfc4622</link>&gt;.</note>" >
@ -640,6 +641,7 @@ THE SOFTWARE.
<!ENTITY rfc6763 "<span class='ref'><link url='http://tools.ietf.org/html/rfc6763'>RFC 6763</link></span> <note>RFC 6763: DNS-Based Service Discovery &lt;<link url='http://tools.ietf.org/html/rfc6763'>http://tools.ietf.org/html/rfc6763</link>&gt;.</note>" >
<!ENTITY rfc6920 "<span class='ref'><link url='http://tools.ietf.org/html/rfc6920'>RFC 6920</link></span> <note>RFC 6920: Naming Things with Hashes &lt;<link url='http://tools.ietf.org/html/rfc6920'>http://tools.ietf.org/html/rfc6920</link>&gt;.</note>" >
<!ENTITY rfc7081 "<span class='ref'><link url='http://tools.ietf.org/html/rfc7081'>RFC 7081</link></span> <note>RFC 7081: CUSAX: Combined Use of the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP) &lt;<link url='http://tools.ietf.org/html/rfc7081'>http://tools.ietf.org/html/rfc7081</link>&gt;.</note>" >
<!ENTITY rfc7572 "<span class='ref'><link url='http://tools.ietf.org/html/rfc7572'>RFC 7572</link></span> <note>RFC 7572: Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Instant Messaging &lt;<link url='http://tools.ietf.org/html/rfc7572'>http://tools.ietf.org/html/rfc7572</link>&gt;.</note>" >
<!ENTITY rfc7622 "<span class='ref'><link url='http://tools.ietf.org/html/rfc7622'>RFC 7622</link></span> <note>RFC 7622: Extensible Messaging and Presence Protocol (XMPP): Address Format &lt;<link url='http://tools.ietf.org/html/rfc7622'>http://tools.ietf.org/html/rfc7622</link>&gt;.</note>" >
<!-- Internet-Drafts -->
@ -697,6 +699,7 @@ THE SOFTWARE.
<!ENTITY ianaslp "<span class='ref'><link url='http://www.iana.org/assignments/svrloc-templates.htm'>
IANA Service Location Protocol, Version 2 (SLPv2) Templates</link></span> <note>IANA registry of parameters related to the Service Location Protocol templates &lt;<link url='http://www.iana.org/assignments/svrloc-templates.htm'>http://www.iana.org/assignments/svrloc-templates.htm</link>&gt;.</note>" >
<!ENTITY ianassh "<span class='ref'><link url='http://www.iana.org/assignments/ssh-parameters'>IANA Secure Shell Protocol Parameters Registry</link></span> <note>IANA registry of parameters related to secure shell &lt;<link url='http://www.iana.org/assignments/ssh-parameters'>http://www.iana.org/assignments/ssh-parameters</link>&gt;.</note>" >
<!ENTITY stox-media "<span class='ref'><link url='https://tools.ietf.org/html/draft-ietf-stox-media'>Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Media Sessions</link></span> <note>Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Media Sessions &lt;<link url='https://tools.ietf.org/html/draft-ietf-stox-media'>https://tools.ietf.org/html/draft-ietf-stox-media</link>&gt;.</note>" >
<!-- IETF XMPP Specs -->