moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-12-21 23:28:51 -05:00
Code Issues Releases Wiki Activity

RFC 4848

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1153 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2007-08-15 16:32:33 +00:00
parent e991543a67
commit fbfa8c1349
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
xep-0156.xml
View File

@ -97,7 +97,7 @@
<li><p>Define a &w3wsdl; definition (or other XML file format) and a canonical URL for that definition at a domain that offers XMPP services. Unfortunately, this approach requires access to the HTTP server for the domain (and quite possibly to the root directory thereof), which may be difficult for XMPP server administrators to arrange. In addition, it requires a client to retrieve the relevant file via HTTP before performing DNS lookups and XMPP connection; it would be more efficient to use recognized DNS methods since DNS lookups are already required by <cite>RFC 3920</cite>.</p></li>
<li><p>Define a way to specify alternative connection methods as part of the existing DNS SRV records (see &rfc2782;) for a domain that offers XMPP services. While this approach sounds promising, it is not feasible since the DNS SRV Target field can be used only to specify domain names and cannot be used to specify full URIs (such as the URL for an HTTP connection manager).</p></li>
<li><p>Define a way to specify alternative connection methods using the "straightforward NAPTR" (S-NAPTR) profile of the Dynamic Delegation Discovery System (see &rfc3958; and &rfc3401;). Unfortunately, S-NAPTR also does not allow inclusion of full URIs, and thus does not meet the requirements for discovery of alternative connection methods.</p></li>
<li><p>Define a way to specify alternative connection methods using the "URI-enabled NAPTR" (U-NAPTR) profile of the Dynamic Delegation Discovery System (see &unaptr;). While this is a valid approach that is worth pursuing, the authors are concerned about the deployability of such an approach given the rarity of support for DDDS and U-NAPTR, especially in client-side applications (the main focus of this specification).</p></li>
<li><p>Define a way to specify alternative connection methods using the "URI-enabled NAPTR" (U-NAPTR) profile of the Dynamic Delegation Discovery System (see &rfc4848;). While this is a valid approach that is worth pursuing, the authors are concerned about the deployability of such an approach given the rarity of support for DDDS and U-NAPTR, especially in client-side applications (the main focus of this specification).</p></li>
<li><p>Define a way to specify alternative connection methods via properly-formatted DNS TXT records (see &rfc1464;). While this approach requires an update to the DNS records for the server domain, that is usually necessary in order to establish XMPP services in the first place. Furthermore, although there are some perils to be avoided in the use of DNS TXT records (e.g., wildcards), the technology is well understood and widely deployed (e.g., it is used by the <link url='http://www.openspf.org/'>Sender Policy Framework</link> and <link url='http://www.microsoft.com/mscorp/safety/technologies/senderid/default.mspx'>SenderID</link> email server verification technologies).</p></li>
</ol>
<p>This document defines a way to encapsulate information about alternative connection methods in DNS TXT resource records. However, the authors will monitor the availability of DDDS-based systems supporting U-NAPTR, and may request deprecation of the DNS TXT methods defined in this document at some point in the future.</p>

2
xep.ent
View File

@ -475,6 +475,7 @@
<!ENTITY rfc4732 "<span class='ref'><link url='http://tools.ietf.org/html/rfc4732'>RFC 4732</link></span> <note>RFC 4732: Internet Denial-of-Service Considerations &lt;<link url='http://tools.ietf.org/html/rfc4732'>http://tools.ietf.org/html/rfc4732</link>&gt;.</note>" >
<!ENTITY rfc4733 "<span class='ref'><link url='http://tools.ietf.org/html/rfc4733'>RFC 4733</link></span> <note>RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals &lt;<link url='http://tools.ietf.org/html/rfc4733'>http://tools.ietf.org/html/rfc4733</link>&gt;.</note>" >
<!ENTITY rfc4790 "<span class='ref'><link url='http://tools.ietf.org/html/rfc4790'>RFC 4790</link></span> <note>RFC 4790: Internet Application Protocol Collation Registry &lt;<link url='http://tools.ietf.org/html/rfc4790'>http://tools.ietf.org/html/rfc4790</link>&gt;.</note>" >
<!ENTITY rfc4848 "<span class='ref'><link url='http://tools.ietf.org/html/rfc4848'>RFC 4848</link></span> <note>RFC 4848: Domain-Based Application Service Location Using URIs and the Dynamic Delegation Discovery Service (DDDS) &lt;<link url='http://tools.ietf.org/html/rfc4848'>http://tools.ietf.org/html/rfc4848</link>&gt;.</note>" >
<!ENTITY rfc4854 "<span class='ref'><link url='http://tools.ietf.org/html/rfc4854'>RFC 4854</link></span> <note>RFC 4854: A Uniform Resource Name (URN) Namespace for Extensions to the Extensible Messaging and Presence Protocol (XMPP) &lt;<link url='http://tools.ietf.org/html/rfc4854'>http://tools.ietf.org/html/rfc4854</link>&gt;.</note>" >
<!-- Internet-Drafts -->
@ -497,7 +498,6 @@
<!ENTITY sshx509 "<span class='ref'><link url='http://tools.ietf.org/html/draft-ietf-secsh-x509'>X.509 Authentication in SSH2</link></span> <note>X.509 Authentication in SSH2 &lt;<link url='http://tools.ietf.org/html/draft-ietf-secsh-x509'>http://tools.ietf.org/html/draft-ietf-secsh-x509</link>&gt;. Work in progress.</note>" >
<!ENTITY tcprobust "<span class='ref'><link url='http://tools.ietf.org/html/draft-ietf-ietf-tcpm-tcpsecure'>Improving TCP's Robustness to Blind In-Window Attacks</link></span> <note>Improving TCP's Robustness to Blind In-Window Attacks &lt;<link url='http://tools.ietf.org/html/draft-ietf-ietf-tcpm-tcpsecure'>http://tools.ietf.org/html/draft-ietf-ietf-tcpm-tcpsecure</link>&gt;. Work in progress.</note>" >
<!ENTITY turn "<span class='ref'><link url='http://tools.ietf.org/html/draft-ietf-behave-turn'>TURN</link></span> <note>Obtaining Relay Addresses from Simple Traversal Underneath NAT (STUN) &lt;<link url='http://tools.ietf.org/html/draft-ietf-behave-turn'>http://tools.ietf.org/html/draft-ietf-behave-turn</link>&gt;. Work in progress.</note>" >
<!ENTITY unaptr "<span class='ref'><link url='http://tools.ietf.org/html/draft-daigle-unaptr'>U-NAPTR</link></span> <note>Domain-based Application Service Location Using URIs and the Dynamic Delegation Discovery Service &lt;<link url='http://tools.ietf.org/html/draft-daigle-unaptr'>http://tools.ietf.org/html/draft-daigle-unaptr</link>&gt;. Work in progress.</note>" >
<!ENTITY zrtp "<span class='ref'><link url='http://tools.ietf.org/html/draft-zimmermann-avt-zrtp'>ZRTP</link></span> <note>ZRTP: Media Path Key Agreement for Secure RTP &lt;<link url='http://tools.ietf.org/html/draft-zimmermann-avt-zrtp'>http://tools.ietf.org/html/draft-zimmermann-avt-zrtp</link>&gt;. Work in progress.</note>" >
<!-- IANA registries -->