From 722e346c92b3f7e7e41a30736df3c647be7f41b8 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Wed, 18 Jun 2008 21:47:42 +0000 Subject: [PATCH] cross-references git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@2001 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0246.xml | 4 ++-- xep-0247.xml | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/xep-0246.xml b/xep-0246.xml index e3597ffc..996c3c2b 100644 --- a/xep-0246.xml +++ b/xep-0246.xml @@ -43,8 +43,8 @@
  • Two endpoints want to enforce end-to-end encryption
  • Two endpoints want to send a high volume of XMPP traffic but the intermediate servers enforce rate limits
  • -

    The first scenario is addressed by &xep0174;. The second and third scenarios are addressed by [ProtoXEP-Jingle-XML-Streams]. 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.

    -

    Once two endpoints have such a connection, they can establish an XML stream over that connection for end-to-end "("e2e") communication. We call this an "e2e" stream.

    +

    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.

    +

    Once two endpoints have such a connection, they can establish an XML stream over that connection for end-to-end "("e2e") communication. We call this an "e2e stream".

    diff --git a/xep-0247.xml b/xep-0247.xml index a153db73..c9c7598d 100644 --- a/xep-0247.xml +++ b/xep-0247.xml @@ -18,7 +18,7 @@ XEP-0047 XEP-0065 XEP-0166 - XEP-0174 + XEP-0246 @@ -186,7 +186,7 @@ STATUS = X'00' to='alice@example.org/foo' type='result'/> ]]> -

    Now the parties start an XML stream over the negotiated bytestream, following the recommendations in XEP-0174.

    +

    Now the parties start an XML stream over the negotiated bytestream, following the recommendations in &xep0246;.