{"@attributes":{"ipr":"full3978","number":"4622","category":"std","docName":"RFC 4622"},"front":{"title":"Internationalized Resource Identifiers (IRIs) and Uniform Resource Identifiers (URIs) for the Extensible Messaging and Presence Protocol (XMPP)","author":{"@attributes":{"initials":"P.","surname":"Saint-Andre","fullname":"Peter Saint-Andre"},"organization":"Jabber Software Foundation","address":{"email":"stpeter@jabber.org","uri":"xmpp:stpeter@jabber.org"}},"date":{"@attributes":{"year":"2006","month":"July"}},"area":"Applications","keyword":["Extensible Messaging and Presence Protocol","XMPP","Internationalized Resource Identifier","IRI","Uniform Resource Identifier","URI"],"abstract":{"t":"This document defines the use of Internationalized Resource Identifiers (IRIs) and Uniform Resource Identifiers (URIs) in identifying or interacting with entities that can communicate via the Extensible Messaging and Presence Protocol (XMPP)."}},"middle":{"section":[{"@attributes":{"title":"Introduction","anchor":"intro"},"t":["The Extensible Messaging and Presence Protocol (XMPP) is a streaming XML technology that enables any two entities on a network to exchange well-defined but extensible XML elements (called \"XML stanzas\") at a rate close to real time.","As specified in , entity addresses as used in communications over an XMPP network must not be prepended with a Uniform Resource Identifier (URI) scheme (as specified in ).  However, applications external to an XMPP network may need to identify XMPP entities either as URIs or, in a more modern fashion, as Internationalized Resource Identifiers (IRIs; see ).  Examples of such external applications include databases that need to store XMPP addresses and non-native user agents such as web browsers and calendaring applications that provide interfaces to XMPP services.","The format for an XMPP address is defined in .  Such an address may contain nearly any  character and must adhere to various profiles of .  The result is that an XMPP address is fully internationalizable and is very close to being an IRI without a scheme.  However, given that there is no freestanding registry of IRI schemes, it is necessary to define XMPP identifiers primarily as URIs rather than as IRIs, and to register an XMPP URI scheme instead of an IRI scheme.  Therefore, this document does the following:",{"list":{"@attributes":{"style":"symbols"},"t":["Specifies how to identify XMPP entities as IRIs or URIs.","Specifies how to interact with XMPP entities as IRIs or URIs.","Formally defines the syntax for XMPP IRIs and URIs.","Specifies how to transform XMPP IRIs into URIs and vice-versa.","Registers the xmpp URI scheme."]}}],"section":{"@attributes":{"title":"Terminology","anchor":"intro-terms"},"t":["This document inherits terminology from , , and .","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 ."]}},{"@attributes":{"title":"Use of XMPP IRIs and URIs","anchor":"use"},"section":[{"@attributes":{"title":"Rationale","anchor":"use-rationale"},"t":["As described in , instant messaging and presence applications of XMPP must handle im: and pres: URIs (as specified by  and ).  However, there are many other applications of XMPP (including network management, workflow systems, generic publish-subscribe, remote procedure calls, content syndication, gaming, and middleware), and these applications do not implement instant messaging and presence semantics.  Neither does a generic XMPP entity implement the semantics of any existing URI scheme, such as the http:, ftp:, or mailto: scheme.  Therefore, it is appropriate to define a new URI scheme that makes it possible to identify or interact with any XMPP entity (not just instant messaging and presence entities) as an IRI or URI.","XMPP IRIs and URIs are defined for use by non-native interfaces and applications, and primarily for the purpose of identification rather than of interaction (on the latter distinction, see Section 1.2.2 of ).  In order to ensure interoperability on XMPP networks, when data is routed to an XMPP entity (e.g., when an XMPP address is contained in the 'to' or 'from' attribute of an XML stanza) or an XMPP entity is otherwise identified in standard XMPP protocol elements, the entity MUST be addressed as <[node@]domain[\/resource]> (i.e., without a prepended scheme), where the \"node identifier\", \"domain identifier\", and \"resource identifier\" portions of an XMPP address conform to the definitions provided in Section 3 of .","Note: For historical reasons, the term \"resource identifier\" is used in XMPP to refer to the optional portion of an XMPP address that follows the domain identifier and the \"\/\" separator character (for details, refer to Section 3.4 of ); this use of the term \"resource identifier\" is not to be confused with the meanings of \"resource\" and \"identifier\" provided in Section 1.1 of ."]},{"@attributes":{"title":"Form","anchor":"use-form"},"t":["As described in , an XMPP address used natively on an XMPP network is a string of Unicode characters that (1) conforms to a certain set of  profiles and  restrictions, (2) follows a certain set of syntax rules, and (3) is encoded as .  The form of such an address can be represented using Augmented Backus-Naur Form () as:","In this context, the \"node\" and \"resource\" rules rely on distinct profiles of , and the \"domain\" rule relies on the concept of an internationalized domain name as described in .  (Note: There is no need to refer to punycode in the IRI syntax itself, since any punycode representation would occur only inside an XMPP application in order to represent internationalized domain names. However, it is the responsibility of the processing application to convert  syntax into  syntax before addressing XML stanzas to the specified entity on an XMPP network.)","Naturally, in order to be converted into an IRI or URI, an XMPP address must be prepended with a scheme (specifically, the xmpp scheme) and may also need to undergo transformations that adhere to the rules defined in  and .  Furthermore, in order to enable more advanced interaction with an XMPP entity rather than simple identification, it is desirable to take advantage of additional aspects of URI syntax and semantics, such as authority components, query components, and fragment identifier components.","Therefore, the ABNF syntax for an XMPP IRI is defined as shown below using Augmented Backus-Naur Form specified by , where the \"ifragment\", \"ihost\", and \"iunreserved\" rules are defined in , the \"pct-encoded\" rule is defined in , and DQUOTE is defined in :","However, the foregoing syntax is not appropriate for inclusion in the registration of the xmpp URI scheme, since the IANA recognizes only URI schemes and not IRI schemes.  Therefore, the ABNF syntax for an XMPP URI rather than for IRI is defined as shown in  of this document (see below under \"IANA Registration\").  If it is necessary to convert the IRI syntax into URI syntax, an application MUST adhere to the mapping procedure specified in Section 3.1 of .","The following is an example of a basic XMPP IRI\/URI used for purposes of identifying a node associated with an XMPP server:","Descriptions of the various components of an XMPP IRI\/URI are provided in the following sections."],"figure":[{"artwork":{}},{"artwork":{}},{"artwork":{}}]},{"@attributes":{"title":"Authority Component","anchor":"use-authority"},"t":["As explained in  of this document, in the absence of an authority component, the processing application would authenticate as a configured user at a configured XMPP server.  That is, the authority component section is unnecessary and should be ignored if the processing application has been configured with a set of default credentials.","In accordance with Section 3.2 of RFC 3986, the authority component is preceded by a double slash (\"\/\/\") and is terminated by the next slash (\"\/\"), question mark (\"?\"), or number sign (\"#\") character, or by the end of the IRI\/URI.  As explained more fully in  of this document, the presence of an authority component signals the processing application to authenticate as the node@domain specified in the authority component rather than as a configured node@domain (see the Security Considerations section of this document regarding authentication).  (While it is unlikely that the authority component will be included in most XMPP IRIs or URIs, the scheme allows for its inclusion, if appropriate.)  Thus, the following XMPP IRI\/URI indicates to authenticate as \"guest@example.com\":","Note well that this is quite different from the following XMPP IRI\/URI, which identifies a node \"guest@example.com\" but does not signal the processing application to authenticate as that node:","Similarly, using a possible query component of \"?message\" to trigger an interface for sending a message, the following XMPP IRI\/URI signals the processing application to authenticate as \"guest@example.com\" and to send a message to \"support@example.com\":","By contrast, the following XMPP IRI\/URI signals the processing application to authenticate as its configured default account and to send a message to \"support@example.com\":"],"figure":[{"artwork":{}},{"artwork":{}},{"artwork":{}},{"artwork":{}}]},{"@attributes":{"title":"Path Component","anchor":"use-path"},"t":["The path component of an XMPP IRI\/URI identifies an XMPP address or specifies the XMPP address to which an XML stanza shall be directed at the end of IRI\/URI processing.","For example, the following XMPP IRI\/URI identifies a node associated with an XMPP server:","The following XMPP IRI\/URI identifies a node associated with an XMPP server along with a particular XMPP resource identifier associated with that node:","Inclusion of a node is optional in XMPP addresses, so the following XMPP IRI\/URI simply identifies an XMPP server:"],"figure":[{"artwork":{}},{"artwork":{}},{"artwork":{}}]},{"@attributes":{"title":"Query Component","anchor":"use-query"},"t":["There are many potential use cases for encapsulating information in the query component of an XMPP IRI\/URI; examples include but are not limited to:",{"list":{"@attributes":{"style":"symbols"},"t":["sending an XMPP message stanza (see ),","adding a roster item (see ),","sending a presence subscription (see ),","probing for current presence information (see ),","triggering a remote procedure call (see ),","discovering the identity or capabilities of another entity (see ),","joining an XMPP-based text chat room (see ),","interacting with publish-subscribe channels (see ),","providing a SOAP interface (see ), and","registering with another entity (see )."]}},"Many of these potential use cases are application specific, and the full range of such applications cannot be foreseen in advance given the continued expansion in XMPP development; however, there is agreement within the Jabber\/XMPP developer community that all the uses envisioned to date can be encapsulated via a \"query type\", optionally supplemented by one or more \"key-value\" pairs (this is similar to the \"application\/x-www-form-urlencoded\" MIME type described in ).","As an example, an XMPP IRI\/URI intended to launch an interface for sending a message to the XMPP entity \"example-node@example.com\" might be represented as follows:","Similarly, an XMPP IRI\/URI intended to launch an interface for sending a message to the XMPP entity \"example-node@example.com\" with a particular subject might be represented as follows:","If the processing application does not understand query components or the specified query type, it MUST ignore the query component and treat the IRI\/URI as consisting of, for example, <xmpp:example-node@example.com> rather than <xmpp:example-node@example.com?query>.  If the processing application does not understand a particular key within the query component, it MUST ignore that key and its associated value.","As noted, there exist many kinds of XMPP applications (both actual and potential), and such applications may define query types and keys for use in the query component portion of XMPP URIs.  The Jabber Registrar function (see ) of the Jabber Software Foundation maintains a registry of such query types and keys at <http:\/\/www.jabber.org\/registrar\/querytypes.html>.  To help ensure interoperability, any application using the formats defined in this document SHOULD submit any associated query types and keys to that registry in accordance with the procedures specified in ."],"figure":[{"artwork":{}},{"artwork":{}}]},{"@attributes":{"title":"Fragment Identifier Component","anchor":"use-frag"},"t":"As stated in Section 3.5 of , \"The fragment identifier component of a URI allows indirect identification of a secondary resource by reference to a primary resource and additional identifying information.\"  Because the resource identified by an XMPP IRI\/URI does not make available any media type (see ) and therefore (in the terminology of ) no representation exists at an XMPP resource, the semantics of the fragment identifier component in XMPP IRIs\/URIs are to be \"considered unknown and, effectively, unconstrained\" (ibid.).  Particular XMPP applications MAY make use of the fragment identifier component for their own purposes.  However, if a processing application does not understand fragment identifier components or the syntax of a particular fragment identifier component included in an XMPP IRI\/URI, it MUST ignore the fragment identifier component."},{"@attributes":{"title":"Generation of XMPP IRIs\/URIs","anchor":"use-gen"},"section":[{"@attributes":{"title":"Generation Method","anchor":"use-gen-method"},"t":["In order to form an XMPP IRI from an XMPP node identifier, domain identifier, and resource identifier, the generating application MUST first ensure that the XMPP address conforms to the rules specified in , including application of the relevant ; it MUST then concatenate the following:",{"list":{"@attributes":{"style":"numbers"},"t":["The \"xmpp\" scheme and the \":\" character","Optionally (if an authority component is to be included before the node identifier), the characters \"\/\/\", an authority component of the form node@domain, and the character \"\/\".","Optionally (if the XMPP address contained an XMPP \"node identifier\"), a string of Unicode characters that conforms to the \"inodeid\" rule, followed by the \"@\" character.","A string of Unicode characters that conforms to the \"ihost\" rule.","Optionally (if the XMPP address contained an XMPP \"resource identifier\"), the character \"\/\" and a string of Unicode characters that conforms to the \"iresid\" rule.","Optionally (if a query component is to be included), the \"?\" character and query component.","Optionally (if a fragment identifier component is to be included), the \"#\" character and fragment identifier component."]}},"In order to form an XMPP URI from the resulting IRI, an application MUST adhere to the mapping procedure specified in Section 3.1 of ."]},{"@attributes":{"title":"Generation Notes","anchor":"use-gen-notes"},"t":["Certain characters are allowed in the node identifier, domain identifier, and resource identifier portions of a native XMPP address but prohibited by the \"inodeid\", \"ihost\", and \"iresid\" rules of an XMPP IRI.  Specifically, the \"#\" and \"?\" characters are allowed in node identifiers, and the \"\/\", \"?\", \"#\", and \"@\" characters are allowed in resource identifiers, but these characters are used as delimiters in XMPP IRIs.  In addition, the \" \" ( space) character is allowed in resource identifiers but prohibited in IRIs.  Therefore, all the foregoing characters MUST be percent-encoded when transforming an XMPP address into an XMPP IRI.","Consider the following nasty node in an XMPP address:","That address would be transformed into the following XMPP IRI:","Consider the following repulsive resource in an XMPP address (split into two lines for layout purposes):","That address would be transformed into the following XMPP IRI (split into two lines for layout purposes):","Furthermore, virtually any character outside the  range is allowed in an XMPP address and therefore also in an XMPP IRI, but URI syntax forbids such characters directly and specifies that such characters MUST be percent-encoded.  In order to determine the URI associated with an XMPP IRI, an application MUST adhere to the mapping procedure specified in Section 3.1 of ."],"figure":[{"artwork":{}},{"artwork":{}},{"artwork":{}},{"artwork":{}}]},{"@attributes":{"title":"Generation Example","anchor":"use-gen-example"},"t":["Consider the following XMPP address:","Note: The string \"&#x159;\" stands for the Unicode character LATIN SMALL LETTER R WITH CARON, and the string \"&#x10D;\" stands for the Unicode character LATIN SMALL LETTER C WITH CARON, following the \"XML Notation\" used in  to represent characters that cannot be rendered in ASCII-only documents (note also that these characters are represented in their stringprep canonical form).  The '<' and '>' characters are not part of the address itself but are provided to set off the address for legibility.  For those who do not read Czech, this example could be Anglicized as \"george@czech-lands.example\/In Prague\".","In accordance with the process specified above, the generating application would do the following to generate a valid XMPP IRI from this address:",{"list":{"@attributes":{"style":"numbers"},"t":["Ensure that the XMPP address conforms to the rules specified in , including application of the relevant  profiles and encoding as a  string.","Concatenate the following:\n              \n            "]}},"The result is this XMPP IRI:","In order to generate a valid XMPP URI from the foregoing IRI, the application MUST adhere to the procedure specified in Section 3.1 of , resulting in the following URI:"],"figure":[{"artwork":{}},{"artwork":{}},{"artwork":{}}]}]},{"@attributes":{"title":"Processing of XMPP IRIs\/URIs","anchor":"use-proc"},"section":[{"@attributes":{"title":"Processing Method","anchor":"use-proc-method"},"t":["If a processing application is presented with an XMPP URI and not with an XMPP IRI, it MUST first convert the URI into an IRI by following the procedure specified in Section 3.2 of .","In order to decompose an XMPP IRI for interaction with the entity it identifies, a processing application MUST separate:",{"list":{"@attributes":{"style":"numbers"},"t":["The \"xmpp\" scheme and the \":\" character.","The authority component, if included (the string of Unicode characters between the \"\/\/\" characters and the next \"\/\" character, the \"?\" character, the \"#\" character, or the end of the IRI).","A string of Unicode characters that represents an XMPP address as transformed in accordance with the \"inodeid\", \"ihost\", and \"iresid\" rules.","Optionally the query component, if included, using the \"?\" character as a separator.","Optionally the fragment identifier component, if included, using the \"#\" character as a separator."]}},"At this point, the processing application MUST ensure that the resulting XMPP address conforms to the rules specified in , including application of the relevant .  The processing application then would either (1) complete further XMPP handling itself or (2) invoke a helper application to complete XMPP handling; such XMPP handling would most likely consist of the following steps:",{"list":{"@attributes":{"style":"numbers"},"t":["If not already connected to an XMPP server, connect either as the user specified in the authority component or as the configured user at the configured XMPP server, normally by adhering to the XMPP connection procedures defined in .  (Note: The processing application SHOULD ignore the authority component if it has been configured with a set of default credentials.)","Optionally, determine the nature of the intended recipient (e.g., via ).","Optionally, present an appropriate interface to a user based on the nature of the intended recipient and\/or the contents of the query component.","Generate an XMPP stanza that translates any user or application inputs into their corresponding XMPP equivalents.","Send the XMPP stanza via the authenticated server connection for delivery to the intended recipient."]}}]},{"@attributes":{"title":"Processing Notes","anchor":"use-proc-notes"},"t":["It may help implementors to note that the first two steps of \"further XMPP handling\", as described at the end of , are similar to HTTP authentication (), while the next three steps are similar to the handling of mailto: URIs ().","As noted in  of this document, certain characters are allowed in the node identifier, domain identifier, and resource identifier portions of a native XMPP address but prohibited by the \"inodeid\", \"ihost\", and \"iresid\" rules of an XMPP IRI.  The percent-encoded octets corresponding to these characters in XMPP IRIs MUST be transformed into the characters allowed in XMPP addresses when processing an XMPP IRI for interaction with the represented XMPP entity.","Consider the following nasty node in an XMPP IRI:","That IRI would be transformed into the following XMPP address:","Consider the following repulsive resource in an XMPP IRI (split into two lines for layout purposes):","That IRI would be transformed into the following XMPP address (split into two lines for layout purposes):"],"figure":[{"artwork":{}},{"artwork":{}},{"artwork":{}},{"artwork":{}}]},{"@attributes":{"title":"Processing Example","anchor":"use-proc-example"},"t":["Consider the XMPP URI that resulted from the previous example:","In order to generate a valid XMPP IRI from that URI, the application MUST adhere to the procedure specified in Section 3.2 of , resulting in the following IRI:","In accordance with the process specified above, the processing application would remove the \"xmpp\" scheme and \":\" character to extract the XMPP address from this XMPP IRI, converting any percent-encoded octets from the \"inodeid\", \"ihost\", and \"iresid\" rules into their character equivalents (e.g., \"%20\" into the space character).","The result is this XMPP address:"],"figure":[{"artwork":{}},{"artwork":{}},{"artwork":{}}]}]},{"@attributes":{"title":"Internationalization","anchor":"use-i18n"},"t":"Because XMPP addresses are  strings and because octets outside the  range within XMPP addresses can be easily converted to percent-encoded octets, XMPP addresses are designed to work well with Internationalized Resource Identifiers ().  In particular, with the exceptions of stringprep verification, the conversion of syntax-relevant  characters (e.g., \"?\"), and the conversion of percent-encoded octets from the \"inodeid\", \"ihost\", and \"iresid\" rules into their character equivalents (e.g., \"%20\" into the  space character), an XMPP IRI can be constructed directly by prepending the \"xmpp\" scheme and \":\" character to an XMPP address.  Furthermore, an XMPP IRI can be converted into URI syntax by adhering to the procedure specified in Section 3.1 of , and an XMPP URI can be converted into IRI syntax by adhering to the procedure specified in Section 3.2 of , thus ensuring interoperability with applications that are able to process URIs but unable to process IRIs."}]},{"@attributes":{"title":"IANA Registration of xmpp URI Scheme","anchor":"reg"},"t":"In accordance with , this section provides the information required to register the xmpp URI scheme.","section":[{"@attributes":{"title":"URI Scheme Name","anchor":"reg-name"},"t":"xmpp"},{"@attributes":{"title":"Status","anchor":"reg-status"},"t":"permanent"},{"@attributes":{"title":"URI Scheme Syntax","anchor":"reg-syntax"},"t":"The syntax for an xmpp URI is defined below using Augmented Backus-Naur Form as specified by , where the \"fragment\", \"host\", \"pct-encoded\", and \"unreserved\" rules are defined in  and DQUOTE is defined in :","figure":{"artwork":{}}},{"@attributes":{"title":"URI Scheme Semantics","anchor":"reg-semantics"},"t":"The xmpp URI scheme identifies entities that natively communicate using the Extensible Messaging and Presence Protocol (XMPP), and is mainly used for identification rather than for resource location.  However, if an application that processes an xmpp URI enables interaction with the XMPP address identified by the URI, it MUST follow the methodology defined in Section 2 of RFC 4622, Use of XMPP IRIs and URIs, to reconstruct the encapsulated XMPP address, connect to an appropriate XMPP server, and send an appropriate XMPP \"stanza\" (XML fragment) to the XMPP address.  (Note: There is no MIME type associated with the xmpp URI scheme.)"},{"@attributes":{"title":"Encoding Considerations","anchor":"reg-encoding"},"t":"In addition to XMPP URIs, there will also be XMPP Internationalized Resource Identifiers (IRIs).  Prior to converting an Extensible Messaging and Presence Protocol (XMPP) address into an IRI (and in accordance with ), the XMPP address must be represented as  by the generating application (e.g., by transforming an application's internal representation of the address as a UTF-16 string into a UTF-8 string), and the UTF-8 string must then be prepended with the \"xmpp\" scheme and \":\" character.  However, because an XMPP URI must contain only  characters, the UTF-8 string of an XMPP IRI must be transformed into URI syntax by adhering to the procedure specified in RFC 3987."},{"@attributes":{"title":"Applications\/Protocols That Use This URI Scheme Name","anchor":"reg-apps"},"t":"The xmpp URI scheme is intended to be used by interfaces to an XMPP network from non-native user agents, such as web browsers, as well as by non-native applications that need to identify XMPP entities as full URIs or IRIs."},{"@attributes":{"title":"Interoperability Considerations","anchor":"reg-interop"},"t":"There are no known interoperability concerns related to use of the xmpp URI scheme.  In order to help ensure interoperability, the Jabber Registrar function of the Jabber Software Foundation maintains a registry of query types and keys that can be used in the query components of XMPP URIs and IRIs, located at <http:\/\/www.jabber.org\/registrar\/querytypes.html>."},{"@attributes":{"title":"Security Considerations","anchor":"reg-sec"},"t":"See Section 5 of RFC 4622, Security Considerations."},{"@attributes":{"title":"Contact","anchor":"reg-contact"},"t":"Peter Saint-Andre [mailto:stpeter@jabber.org, xmpp:stpeter@jabber.org]"},{"@attributes":{"title":"Author\/Change Controller","anchor":"reg-control"},"t":"This scheme is registered under the IETF tree.  As such, the IETF maintains change control."},{"@attributes":{"title":"References","anchor":"reg-refs"},"t":{"xref":{"@attributes":{"target":"XMPP-CORE"}}}}]},{"@attributes":{"title":"IANA Considerations","anchor":"iana"},"t":"This document registers a URI scheme.  The registration template can be found in  of this document.  In order to help ensure interoperability, the Jabber Registrar function of the Jabber Software Foundation maintains a registry of query types and keys that can be used in the query components of XMPP URIs and IRIs, located at <http:\/\/www.jabber.org\/registrar\/querytypes.html>."},{"@attributes":{"title":"Security Considerations","anchor":"sec"},"t":"Providing an interface to XMPP services from non-native applications introduces new security concerns.  The security considerations discussed in , , and  apply to XMPP IRIs, and the security considerations discussed in  and  apply to XMPP URIs.  In accordance with Section 2.7 of  and Section 7 of , particular security considerations are specified in the following sections.","section":[{"@attributes":{"title":"Reliability and Consistency","anchor":"sec-reliable"},"t":["Given that XMPP addresses of the form node@domain.tld are typically created via registration at an XMPP server or provisioned by an administrator of such a server, it is possible that such addresses may also be unregistered or deprovisioned.  Therefore, the XMPP IRI\/URI that identifies such an XMPP address may not reliably and consistently be associated with the same principal, account owner, application, or device.","XMPP addresses of the form node@domain.tld\/resource are typically even more ephemeral (since a given XMPP resource identifier is typically associated with a particular, temporary session of an XMPP client at an XMPP server).  Therefore, the XMPP IRI\/URI that identifies such an XMPP address probably will not reliably and consistently be associated with the same session.  However, the procedures specified in Section 10 of  effectively eliminate any potential confusion that might be introduced by the lack of reliability and consistency for the XMPP IRI\/URI that identifies such an XMPP address.","XMPP addresses of the form domain.tld are typically long-lived XMPP servers or associated services; although naturally it is possible for server or service administrators to de-commission the server or service at any time, typically the IRIs\/URIs that identify such servers or services are the most reliable and consistent of XMPP IRIs\/URIs.","XMPP addresses of the form domain.tld\/resource are not yet common on XMPP networks; however, the reliability and consistency of XMPP IRIs\/URIs that identify such XMPP addresses would likely fall somewhere between those that identify XMPP addresses of the form domain.tld and those that identify XMPP addresses of the form node@domain.tld."]},{"@attributes":{"title":"Malicious Construction","anchor":"sec-construction"},"t":"Malicious construction of XMPP IRIs\/URIs is made less likely by the prohibition on port numbers in XMPP IRIs\/URIs (since port numbers are to be discovered using  records, as specified in )."},{"@attributes":{"title":"Back-End Transcoding","anchor":"sec-transcoding"},"t":"Because the base XMPP protocol is designed to implement the exchange of messages and presence information and not the retrieval of files or invocation of similar system functions, it is deemed unlikely that the use of XMPP IRIs\/URIs would result in harmful dereferencing.  However, if an XMPP protocol extension defines methods for information retrieval, it MUST define appropriate controls over access to that information.  In addition, XMPP servers SHOULD NOT natively parse XMPP IRIs\/URIs but instead SHOULD accept only the XML wire protocol specified in  and any desired extensions thereto."},{"@attributes":{"title":"Sensitive Information","anchor":"sec-information"},"t":["The ability to interact with XMPP entities via a web browser or other non-native application may expose sensitive information (such as support for particular XMPP application protocol extensions) and thereby make it possible to launch attacks that are not possible or that are unlikely on a native XMPP network.  Due care must be taken in deciding what information is appropriate for representation in XMPP IRIs or URIs.","In particular, advertising XMPP IRIs\/URIs in publicly accessible locations (e.g., on websites) may make it easier for malicious users to harvest XMPP addresses from the authority and path components of XMPP IRIs\/URIs and therefore to send unsolicited bulk communications to the users or applications represented by those addresses.  Due care should be taken in balancing the benefits of open information exchange against the potential costs of unwanted communications.","To help prevent leaking of sensitive information, passwords and other user credentials are forbidden in the authority component of XMPP IRIs\/URIs; in fact they are not needed, since the fact that authentication in XMPP occurs via  makes it possible to use the SASL ANONYMOUS mechanism, if desired."]},{"@attributes":{"title":"Semantic Attacks","anchor":"sec-semantic"},"t":"Despite the existence of non-hierarchical URI schemes such as , by association human users may expect all URIs to include the \"\/\/\" characters after the scheme name and \":\" character.  However, in XMPP IRIs\/URIs, the \"\/\/\" characters precede the authority component rather than the path component.  Thus, xmpp:\/\/guest@example.com indicates to authenticate as \"guest@example.com\", whereas xmpp:guest@example.com identifies the node \"guest@example.com\".  Processing applications MUST clearly differentiate between these forms, and user agents SHOULD discourage human users from including the \"\/\/\" characters in XMPP IRIs\/URIs since use of the authority component is envisioned to be helpful only in specialized scenarios, not more generally."},{"@attributes":{"title":"Spoofing","anchor":"sec-spoofing"},"t":"The ability to include effectively the full range of Unicode characters in an XMPP IRI may make it easier to execute certain forms of address mimicking (also called \"spoofing\").  However, XMPP IRIs are no different from other IRIs in this regard, and applications that will present XMPP IRIs to human users must adhere to best practices regarding address mimicking in order to help prevent attacks that result from spoofed addresses (e.g., the phenomenon known as \"phishing\").  For details, refer to the Security Considerations of ."}]}]},"back":{"references":[{"@attributes":{"title":"Normative References"},"reference":[{"@attributes":{"anchor":"ABNF"},"front":{"title":"Augmented BNF for Syntax Specifications: ABNF","author":[{"@attributes":{"initials":"D.","surname":"Crocker","fullname":"D. Crocker"},"organization":{}},{"@attributes":{"initials":"P.","surname":"Overell","fullname":"P. Overell"},"organization":{}}],"date":{"@attributes":{"year":"2005","month":"October"}}},"seriesInfo":{"@attributes":{"name":"RFC","value":"4234"}},"format":{"@attributes":{"type":"TXT","octets":"26351","target":"ftp:\/\/ftp.isi.edu\/in-notes\/rfc4234.txt"}}},{"@attributes":{"anchor":"IRI"},"front":{"title":"Internationalized Resource Identifiers (IRIs)","author":[{"@attributes":{"initials":"M.","surname":"Duerst","fullname":"M. Duerst"},"organization":{}},{"@attributes":{"initials":"M.","surname":"Suignard","fullname":"M. Suignard"},"organization":{}}],"date":{"@attributes":{"year":"2005","month":"January"}}},"seriesInfo":{"@attributes":{"name":"RFC","value":"3987"}},"format":{"@attributes":{"type":"TXT","octets":"111190","target":"ftp:\/\/ftp.isi.edu\/in-notes\/rfc3987.txt"}}},{"@attributes":{"anchor":"TERMS"},"front":{"title":"Key words for use in RFCs to Indicate Requirement Levels","author":{"@attributes":{"initials":"S.","surname":"Bradner","fullname":"Scott Bradner"},"organization":"Harvard University","address":{"postal":{"street":["1350 Mass.  Ave.","Cambridge","MA 02138"]},"phone":"- +1 617 495 3864","email":"-"}},"date":{"@attributes":{"month":"March","year":"1997"}},"area":"General","keyword":"keyword","abstract":{"t":["In many standards track documents several words are used to signify the requirements in the specification.  These words are often capitalized.  This document defines these words as they should be interpreted in IETF documents.  Authors who follow these guidelines should incorporate this phrase near the beginning of their document:\n              \n            ","Note that the force of these words is modified by the requirement level of the document in which they are used."]}},"seriesInfo":[{"@attributes":{"name":"BCP","value":"14"}},{"@attributes":{"name":"RFC","value":"2119"}}]},{"@attributes":{"anchor":"URI"},"front":{"title":"Uniform Resource Identifier (URI): Generic Syntax","author":[{"@attributes":{"initials":"T.","surname":"Berners-Lee","fullname":"T. Berners-Lee"},"organization":{}},{"@attributes":{"initials":"R.","surname":"Fielding","fullname":"R. Fielding"},"organization":{}},{"@attributes":{"initials":"L.","surname":"Masinter","fullname":"L. Masinter"},"organization":{}}],"date":{"@attributes":{"year":"2005","month":"January"}}},"seriesInfo":[{"@attributes":{"name":"STD","value":"66"}},{"@attributes":{"name":"RFC","value":"3986"}}],"format":{"@attributes":{"type":"TXT","octets":"141811","target":"ftp:\/\/ftp.isi.edu\/in-notes\/rfc3986.txt"}}},{"@attributes":{"anchor":"XMPP-CORE"},"front":{"title":"Extensible Messaging and Presence Protocol (XMPP): Core","author":{"@attributes":{"initials":"P.","surname":"Saint-Andre","fullname":"P.  Saint-Andre"},"organization":"Jabber Software Foundation"},"date":{"@attributes":{"year":"2004","month":"October"}}},"seriesInfo":{"@attributes":{"name":"RFC","value":"3920"}},"format":{"@attributes":{"type":"TXT","octets":"194313","target":"ftp:\/\/ftp.isi.edu\/in-notes\/rfc3920.txt"}}}]},{"@attributes":{"title":"Informative References"},"reference":[{"@attributes":{"anchor":"CPIM"},"front":{"title":"Common Profile for Instant Messaging (CPIM)","author":{"@attributes":{"initials":"J.","surname":"Peterson","fullname":"J.  Peterson"},"organization":{}},"date":{"@attributes":{"year":"2004","month":"August"}}},"seriesInfo":{"@attributes":{"name":"RFC","value":"3860"}},"format":{"@attributes":{"type":"TXT","octets":"26486","target":"ftp:\/\/ftp.isi.edu\/in-notes\/rfc3860.txt"}}},{"@attributes":{"anchor":"CPP"},"front":{"title":"Common Profile for Presence (CPP)","author":{"@attributes":{"initials":"J.","surname":"Peterson","fullname":"J.  Peterson"},"organization":{}},"date":{"@attributes":{"year":"2004","month":"August"}}},"seriesInfo":{"@attributes":{"name":"RFC","value":"3859"}},"format":{"@attributes":{"type":"TXT","octets":"30537","target":"ftp:\/\/ftp.isi.edu\/in-notes\/rfc3859.txt"}}},{"@attributes":{"anchor":"DNS-SRV"},"front":{"title":"A DNS RR for specifying the location of services (DNS SRV)","author":[{"@attributes":{"initials":"A.","surname":"Gulbrandsen","fullname":"Arnt Gulbrandsen"},"organization":"Troll Tech","address":{"postal":{"street":"Waldemar Thranes gate 98B","city":"Oslo","region":{},"code":"N-0175","country":"NO"},"phone":"+47 22 806390","facsimile":"+47 22 806380","email":"arnt@troll.no"}},{"@attributes":{"initials":"P.","surname":"Vixie","fullname":"Paul Vixie"},"organization":"Internet Software Consortium","address":{"postal":{"street":"950 Charter Street","city":"Redwood City","region":"CA","code":"94063","country":"US"},"phone":"+1 650 779 7001"}},{"@attributes":{"initials":"L.","surname":"Esibov","fullname":"Levon Esibov"},"organization":"Microsoft Corporation","address":{"postal":{"street":"One Microsoft Way","city":"Redmond","region":"WA","code":"98052","country":"US"},"email":"levone@microsoft.com"}}],"date":{"@attributes":{"month":"February","year":"2000"}},"abstract":{"t":"This document describes a DNS RR which specifies the location of the\n   server(s) for a specific protocol and domain."}},"seriesInfo":{"@attributes":{"name":"RFC","value":"2782"}},"format":{"@attributes":{"type":"TXT","octets":"24013","target":"ftp:\/\/ftp.isi.edu\/in-notes\/rfc2782.txt"}}},{"@attributes":{"anchor":"HTML"},"front":{"title":"HTML 4.0 Specification","author":{"@attributes":{"initials":"D","surname":"Raggett","fullname":"David Raggett"},"organization":{}},"date":{"@attributes":{"month":"April","day":"24","year":"1998"}}},"seriesInfo":{"@attributes":{"name":"W3C REC","value":"REC-html40-19980424"}},"format":{"@attributes":{"type":"HTML","target":"http:\/\/www.w3.org\/TR\/1998\/REC-html40-19980424"}}},{"@attributes":{"anchor":"HTTP-AUTH"},"front":{"title":"HTTP Authentication: Basic and Digest Access Authentication","author":[{"@attributes":{"initials":"J.","surname":"Franks","fullname":"John Franks"},"organization":"Northwestern University, Department of Mathematics","address":{"postal":{"street":"Northwestern University","city":"Evanston","region":"IL","code":"60208-2730","country":"USA"},"email":"john@math.nwu.edu"}},{"@attributes":{"initials":"P.M.","surname":"Hallam-Baker","fullname":"Phillip M.  Hallam-Baker"},"organization":"Verisign Inc.","address":{"postal":{"street":["301 Edgewater Place","Suite 210"],"city":"Wakefield","region":"MA","code":"01880","country":"USA"},"email":"pbaker@verisign.com"}},{"@attributes":{"initials":"J.L.","surname":"Hostetler","fullname":"Jeffery L.  Hostetler"},"organization":"AbiSource, Inc.","address":{"postal":{"street":"6 Dunlap Court","city":"Savoy","region":"IL","code":"61874","country":"USA"},"email":"jeff@AbiSource.com"}},{"@attributes":{"initials":"S.D.","surname":"Lawrence","fullname":"Scott D.  Lawrence"},"organization":"Agranat Systems, Inc.","address":{"postal":{"street":["5 Clocktower Place","Suite 400"],"city":"Maynard","region":"MA","code":"01754","country":"USA"},"email":"lawrence@agranat.com"}},{"@attributes":{"initials":"P.J.","surname":"Leach","fullname":"Paul J.  Leach"},"organization":"Microsoft Corporation","address":{"postal":{"street":"1 Microsoft Way","city":"Redmond","region":"WA","code":"98052","country":"USA"},"email":"paulle@microsoft.com"}},{"@attributes":{"initials":"A.","surname":"Luotonen","fullname":"Ari Luotonen"},"organization":"Netscape Communications Corporation","address":{"postal":{"street":"501 East Middlefield Road","city":"Mountain View","region":"CA","code":"94043","country":"USA"}}},{"@attributes":{"initials":"L.","surname":"Stewart","fullname":"Lawrence C.  Stewart"},"organization":"Open Market, Inc.","address":{"postal":{"street":"215 First Street","city":"Cambridge","region":"MA","code":"02142","country":"USA"},"email":"stewart@OpenMarket.com"}}],"date":{"@attributes":{"year":"1999","month":"June"}},"abstract":{"t":["\n   \"HTTP\/1.0\", includes the specification for a Basic Access\n   Authentication scheme.  This scheme is not considered to be a secure\n   method of user authentication (unless used in conjunction with some\n   external secure system such as SSL ), as the user name and\n   password are passed over the network as cleartext.\n      ","\n   This document also provides the specification for HTTP's\n   authentication framework, the original Basic authentication scheme\n   and a scheme based on cryptographic hashes, referred to as \"Digest\n   Access Authentication\".  It is therefore also intended to serve as a\n   replacement for RFC 2069 .  Some optional elements specified by\n   RFC 2069 have been removed from this specification due to problems\n   found since its publication; other new elements have been added for\n   compatibility, those new elements have been made optional, but are\n   strongly recommended.\n      ","\n   Like Basic, Digest access authentication verifies that both parties\n   to a communication know a shared secret (a password); unlike Basic,\n   this verification can be done without sending the password in the\n   clear, which is Basic's biggest weakness.  As with most other\n   authentication protocols, the greatest sources of risks are usually\n   found not in the core protocol itself but in policies and procedures\n   surrounding its use.\n    "]}},"seriesInfo":{"@attributes":{"name":"RFC","value":"2617"}},"format":[{"@attributes":{"type":"TXT","octets":"77638","target":"ftp:\/\/ftp.isi.edu\/in-notes\/rfc2617.txt"}},{"@attributes":{"type":"HTML","octets":"100323","target":"http:\/\/xml.resource.org\/public\/rfc\/html\/rfc2617.html"}},{"@attributes":{"type":"XML","octets":"85507","target":"http:\/\/xml.resource.org\/public\/rfc\/xml\/rfc2617.xml"}}]},{"@attributes":{"anchor":"IDNA"},"front":{"title":"Internationalizing Domain Names in Applications (IDNA)","author":[{"@attributes":{"initials":"P.","surname":"Faltstrom","fullname":"P.  Faltstrom"},"organization":{}},{"@attributes":{"initials":"P.","surname":"Hoffman","fullname":"P.  Hoffman"},"organization":{}},{"@attributes":{"initials":"A.","surname":"Costello","fullname":"A.  Costello"},"organization":{}}],"date":{"@attributes":{"month":"March","year":"2003"}}},"seriesInfo":{"@attributes":{"name":"RFC","value":"3490"}},"format":{"@attributes":{"type":"TXT","octets":"51943","target":"ftp:\/\/ftp.isi.edu\/in-notes\/rfc3490.txt"}}},{"@attributes":{"anchor":"JEP-0009"},"front":{"title":"Jabber-RPC","author":{"@attributes":{"initials":"D.","surname":"Adams","fullname":"DJ Adams"},"organization":{},"address":{"email":"dj.adams@pobox.com"}},"date":{"@attributes":{"day":"09","month":"February","year":"2006"}}},"seriesInfo":{"@attributes":{"name":"JSF JEP","value":"0009"}},"format":{"@attributes":{"type":"HTML","target":"http:\/\/www.jabber.org\/jeps\/jep-0009.html"}}},{"@attributes":{"anchor":"JEP-0030"},"front":{"title":"Service Discovery","author":[{"@attributes":{"initials":"J.","surname":"Hildebrand","fullname":"Joe Hildebrand"},"organization":{},"address":{"email":"jhildebrand@jabber.com"}},{"@attributes":{"initials":"P.","surname":"Millard","fullname":"Peter Millard"},"organization":{},"address":{"email":"pgmillard@jabber.org"}},{"@attributes":{"initials":"R.","surname":"Eatmon","fullname":"Ryan Eatmon"},"organization":{},"address":{"email":"reatmon@jabber.org"}},{"@attributes":{"initials":"P.","surname":"Saint-Andre","fullname":"Peter Saint-Andre"},"organization":{},"address":{"email":"stpeter@jabber.org"}}],"date":{"@attributes":{"day":"24","month":"January","year":"2006"}}},"seriesInfo":{"@attributes":{"name":"JSF JEP","value":"0030"}},"format":{"@attributes":{"type":"HTML","target":"http:\/\/www.jabber.org\/jeps\/jep-0030.html"}}},{"@attributes":{"anchor":"JEP-0045"},"front":{"title":"Multi-User Chat","author":{"@attributes":{"initials":"P.","surname":"Saint-Andre","fullname":"Peter Saint-Andre"},"organization":{},"address":{"email":"stpeter@jabber.org"}},"date":{"@attributes":{"day":"08","month":"September","year":"2005"}}},"seriesInfo":{"@attributes":{"name":"JSF JEP","value":"0045"}},"format":{"@attributes":{"type":"HTML","target":"http:\/\/www.jabber.org\/jeps\/jep-0045.html"}}},{"@attributes":{"anchor":"JEP-0053"},"front":{"title":"Jabber Registrar","author":{"@attributes":{"initials":"P.","surname":"Saint-Andre","fullname":"Peter Saint-Andre"},"organization":{},"address":{"email":"stpeter@jabber.org"}},"date":{"@attributes":{"day":"20","month":"May","year":"2004"}}},"seriesInfo":{"@attributes":{"name":"JSF JEP","value":"0053"}},"format":{"@attributes":{"type":"HTML","target":"http:\/\/www.jabber.org\/jeps\/jep-0053.html"}}},{"@attributes":{"anchor":"JEP-0060"},"front":{"title":"Publish-Subscribe","author":[{"@attributes":{"initials":"P.","surname":"Millard","fullname":"Peter Millard"},"organization":{},"address":{"email":"pgmillard@jabber.org"}},{"@attributes":{"initials":"P.","surname":"Saint-Andre","fullname":"Peter Saint-Andre"},"organization":{},"address":{"email":"stpeter@jabber.org"}},{"@attributes":{"initials":"R.","surname":"Meijer","fullname":"Ralph Meijer"},"organization":{},"address":{"email":"ralphm@ik.nu"}}],"date":{"@attributes":{"day":"03","month":"March","year":"2005"}}},"seriesInfo":{"@attributes":{"name":"JSF JEP","value":"0060"}},"format":{"@attributes":{"type":"HTML","target":"http:\/\/www.jabber.org\/jeps\/jep-0060.html"}}},{"@attributes":{"anchor":"JEP-0072"},"front":{"title":"SOAP Over XMPP","author":[{"@attributes":{"initials":"F.","surname":"Forno","fullname":"Fabio Forno"},"organization":{},"address":{"email":"fabio.forno@polito.it"}},{"@attributes":{"initials":"P.","surname":"Saint-Andre","fullname":"Peter Saint-Andre"},"organization":{},"address":{"email":"stpeter@jabber.org"}}],"date":{"@attributes":{"day":"14","month":"December","year":"2005"}}},"seriesInfo":{"@attributes":{"name":"JSF JEP","value":"0072"}},"format":{"@attributes":{"type":"HTML","target":"http:\/\/www.jabber.org\/jeps\/jep-0072.html"}}},{"@attributes":{"anchor":"JEP-0077"},"front":{"title":"In-Band Registration","author":{"@attributes":{"initials":"P.","surname":"Saint-Andre","fullname":"Peter Saint-Andre"},"organization":{},"address":{"email":"stpeter@jabber.org"}},"date":{"@attributes":{"day":"24","month":"January","year":"2006"}}},"seriesInfo":{"@attributes":{"name":"JSF JEP","value":"0077"}},"format":{"@attributes":{"type":"HTML","target":"http:\/\/www.jabber.org\/jeps\/jep-0077.html"}}},{"@attributes":{"anchor":"JEP-0147"},"front":{"title":"XMPP IRI\/URI Query Components","author":{"@attributes":{"initials":"P.","surname":"Saint-Andre","fullname":"Peter Saint-Andre"},"organization":{},"address":{"email":"stpeter@jabber.org"}},"date":{"@attributes":{"day":"23","month":"March","year":"2006"}}},"seriesInfo":{"@attributes":{"name":"JSF JEP","value":"0147"}},"format":{"@attributes":{"type":"HTML","target":"http:\/\/www.jabber.org\/jeps\/jep-0147.html"}}},{"@attributes":{"anchor":"MAILTO"},"front":{"title":"The mailto URL scheme","author":[{"@attributes":{"initials":"P.E.","surname":"Hoffman","fullname":"Paul E.  Hoffman"},"organization":"Internet Mail Consortium","address":{"postal":{"street":["127 Segre Place","Santa Cruz","CA  95060"],"country":"USA"},"email":"phoffman@imc.org"}},{"@attributes":{"initials":"L.","surname":"Masinter","fullname":"Larry Masinter"},"organization":"Xerox Corporation","address":{"postal":{"street":["3333 Coyote Hill Road","Palo Alto","CA 94304"],"country":"USA"},"email":"masinter@parc.xerox.com"}},{"@attributes":{"initials":"J.","surname":"Zawinski","fullname":"Jamie Zawinski"},"organization":"Netscape Communications Corp.","address":{"postal":{"street":["501 East Middlefield Road","Mountain View","CA 94043"],"country":"USA"},"email":"jwz@netscape.com"}}],"date":{"@attributes":{"month":"July","year":"1998"}},"area":"Applications","keyword":["mailto","mail","uniform resource locator","URL"],"abstract":{"t":"\n   This document defines the format of Uniform Resource Locators (URL)\n   for designating electronic mail addresses.  It is one of a suite of\n   documents which replace RFC 1738, 'Uniform Resource Locators', and\n   RFC 1808, 'Relative Uniform Resource Locators'.  The syntax of\n   'mailto' URLs from RFC 1738 is extended to allow creation of more RFC\n   822 messages by allowing the URL to express additional header and\n   body fields.\n"}},"seriesInfo":{"@attributes":{"name":"RFC","value":"2368"}},"format":[{"@attributes":{"type":"TXT","octets":"16502","target":"ftp:\/\/ftp.isi.edu\/in-notes\/rfc2368.txt"}},{"@attributes":{"type":"HTML","octets":"30859","target":"http:\/\/xml.resource.org\/public\/rfc\/html\/rfc2368.html"}},{"@attributes":{"type":"XML","octets":"17329","target":"http:\/\/xml.resource.org\/public\/rfc\/xml\/rfc2368.xml"}}]},{"@attributes":{"anchor":"MIME"},"front":{"title":"Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types","author":[{"@attributes":{"initials":"N.","surname":"Freed","fullname":"Ned Freed"},"organization":"Innosoft International, Inc.","address":{"postal":{"street":"1050 East Garvey Avenue South","city":"West Covina","region":"CA","code":"91790","country":"US"},"phone":"+1 818 919 3600","facsimile":"+1 818 919 3614","email":"ned@innosoft.com"}},{"@attributes":{"initials":"N.","surname":"Borenstein","fullname":"Nathaniel S.  Borenstein"},"organization":"First Virtual Holdings","address":{"postal":{"street":"25 Washington Avenue","city":"Morristown","region":"NJ","code":"07960","country":"US"},"phone":"+1 201 540 8967","facsimile":"+1 201 993 3032","email":"nsb@nsb.fv.com"}}],"date":{"@attributes":{"year":"1996","month":"November"}},"abstract":{"t":["STD 11, RFC 822 defines a message representation protocol specifying considerable detail about US-ASCII message headers, but which leaves the message content, or message body, as flat US-ASCII text.  This set of documents, collectively called the Multipurpose Internet Mail Extensions, or MIME, redefines the format of messages to allow for","(1)   textual message bodies in character sets other than US-ASCII,","(2)   an extensible set of different formats for non-textual message bodies,","(3)   multi-part message bodies, and","(4)   textual header information in character sets other than US-ASCII.","These documents are based on earlier work documented in RFC 934, STD 11 and RFC 1049, but extends and revises them.  Because RFC 822 said so little about message bodies, these documents are largely orthogonal to (rather than a revision of) RFC 822.","The initial document in this set, RFC 2045, specifies the various headers used to describe the structure of MIME messages.  This second document defines the general structure of the MIME media typing sytem and defines an initial set of media types.  The third document, RFC 2047, describes extensions to RFC 822 to allow non-US-ASCII text data in Internet mail header fields.  The fourth document, RFC 2048, specifies various IANA registration procedures for MIME-related facilities.  The fifth and final document, RFC 2049, describes MIME\n   conformance criteria as well as providing some illustrative examples of MIME message formats, acknowledgements, and the bibliography.","These documents are revisions of RFCs 1521 and 1522, which themselves were revisions of RFCs 1341 and 1342.  An appendix in RFC 2049 describes differences and changes from previous versions."]}},"seriesInfo":{"@attributes":{"name":"RFC","value":"2046"}},"format":{"@attributes":{"type":"TXT","octets":"105854","target":"ftp:\/\/ftp.isi.edu\/in-notes\/rfc2046.txt"}}},{"@attributes":{"anchor":"SASL"},"front":{"title":"Simple Authentication and Security Layer (SASL)","author":{"@attributes":{"initials":"J.G.","surname":"Myers","fullname":"John G. Myers"},"organization":"Netscape Communications","address":{"postal":{"street":["501 E. Middlefield Road","Mail Stop MV-029","Mountain View","CA 94043-4042"]},"email":"jgmyers@netscape.com"}},"date":{"@attributes":{"month":"October","year":"1997"}},"area":"Security","keyword":["authentication","security"]},"seriesInfo":{"@attributes":{"name":"RFC","value":"2222"}},"format":[{"@attributes":{"type":"TXT","octets":"35010","target":"ftp:\/\/ftp.isi.edu\/in-notes\/rfc2222.txt"}},{"@attributes":{"type":"HTML","octets":"47275","target":"http:\/\/xml.resource.org\/public\/rfc\/html\/rfc2222.html"}},{"@attributes":{"type":"XML","octets":"33815","target":"http:\/\/xml.resource.org\/public\/rfc\/xml\/rfc2222.xml"}}]},{"@attributes":{"anchor":"STRINGPREP"},"front":{"title":"Preparation of Internationalized Strings (\"STRINGPREP\")","author":[{"@attributes":{"initials":"P.","surname":"Hoffman","fullname":"P.  Hoffman"},"organization":{}},{"@attributes":{"initials":"M.","surname":"Blanchet","fullname":"M.  Blanchet"},"organization":{}}],"date":{"@attributes":{"month":"December","year":"2002"}}},"seriesInfo":{"@attributes":{"name":"RFC","value":"3454"}},"format":{"@attributes":{"type":"TXT","octets":"138684","target":"ftp:\/\/ftp.isi.edu\/in-notes\/rfc3454.txt"}}},{"@attributes":{"anchor":"UNICODE"},"front":{"title":"The Unicode Standard, Version 3.2.0","author":{"organization":"The Unicode Consortium"},"date":{"@attributes":{"year":"2000"}}},"annotation":"\n    The Unicode Standard, Version 3.2.0 is defined by The Unicode Standard, Version 3.0 (Reading, MA, Addison-Wesley, 2000. ISBN 0-201-61633-5), as amended by the Unicode Standard Annex #27: Unicode 3.1 (http:\/\/www.unicode.org\/reports\/tr27\/) and by the Unicode Standard Annex #28: Unicode 3.2 (http:\/\/www.unicode.org\/reports\/tr28\/).\n  "},{"@attributes":{"anchor":"URI-SCHEMES"},"front":{"title":"Guidelines and Registration Procedures for New URI Schemes","author":[{"@attributes":{"initials":"T.","surname":"Hansen","fullname":"Tony Hansen"},"organization":"AT&T Laboratories","address":{"postal":{"street":"200 Laurel Ave.","city":"Middletown","region":"NJ","code":"07748","country":"US"},"email":"tony+urireg@maillennium.att.com"}},{"@attributes":{"initials":"T.","surname":"Hardie","fullname":"Ted Hardie"},"organization":"Qualcomm, Inc.","address":{"postal":{"street":"675 Campbell Technology Parkway","city":"Campbell","region":"CA","country":"US"},"email":"hardie@qualcomm.com"}},{"@attributes":{"initials":"L.","surname":"Masinter","fullname":"Larry Masinter"},"organization":"Adobe Systems","address":{"postal":{"street":"345 Park Ave","city":"San Jose","region":"CA","code":"95110","country":"US"},"email":"LMM@acm.org"}}],"date":{"@attributes":{"month":"February","year":"2006"}},"abstract":{"t":"This document provides guidelines and recommendations for the definition of Uniform Resource Identifier (URI) schemes.  It also updates the process and IANA registry for URI schemes.  It obsoletes both RFC 2717 and RFC 2718."}},"seriesInfo":{"@attributes":{"name":"RFC","value":"4395"}},"format":{"@attributes":{"type":"TXT","octets":"31933","target":"ftp:\/\/ftp.isi.edu\/in-notes\/rfc4395.txt"}}},{"@attributes":{"anchor":"US-ASCII"},"front":{"title":"Coded Character Set - 7-bit American Standard Code for Information Interchange","author":{"organization":"American National Standards Institute"},"date":{"@attributes":{"month":"","year":"1986"}}},"seriesInfo":{"@attributes":{"name":"ANSI","value":"X3.4"}}},{"@attributes":{"anchor":"UTF-8"},"front":{"title":"UTF-8, a transformation format of ISO 10646","author":{"@attributes":{"initials":"F.","surname":"Yergeau","fullname":"F.  Yergeau"},"organization":{}},"date":{"@attributes":{"month":"November","year":"2003"}}},"seriesInfo":[{"@attributes":{"name":"STD","value":"63"}},{"@attributes":{"name":"RFC","value":"3629"}}],"format":{"@attributes":{"type":"TXT","octets":"33856","target":"ftp:\/\/ftp.isi.edu\/in-notes\/rfc3629.txt"}}},{"@attributes":{"anchor":"XMPP-IM"},"front":{"title":"Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence","author":{"@attributes":{"initials":"P.","surname":"Saint-Andre","fullname":"P.  Saint-Andre"},"organization":"Jabber Software Foundation"},"date":{"@attributes":{"year":"2004","month":"October"}}},"seriesInfo":{"@attributes":{"name":"RFC","value":"3921"}},"format":{"@attributes":{"type":"TXT","octets":"217527","target":"ftp:\/\/ftp.isi.edu\/in-notes\/rfc3921.txt"}}}]}]}}