<pre>Network Working Group                                      D. Malas, Ed.
Request for Comments: 5486                                     CableLabs
Category: Informational                                    D. Meyer, Ed.
                                                              March 2009


  <span class="h1">Session Peering for Multimedia Interconnect (SPEERMINT) Terminology</span>

Status of This Memo

   This memo provides information for the Internet community.  It does
   not specify an Internet standard of any kind.  Distribution of this
   memo is unlimited.

Copyright Notice

   Copyright (c) 2009 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
   Provisions Relating to IETF Documents in effect on the date of
   publication of this document (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>).
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Abstract

   This document defines the terminology that is to be used in
   describing Session PEERing for Multimedia INTerconnect (SPEERMINT).










<span class="grey">Malas &amp; Meyer                Informational                      [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc5486">RFC 5486</a>                 SPEERMINT Terminology                March 2009</span>


Table of Contents

   <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
   <a href="#section-2">2</a>. SPEERMINT Context ...............................................<a href="#page-3">3</a>
   <a href="#section-3">3</a>. General Definitions .............................................<a href="#page-4">4</a>
      <a href="#section-3.1">3.1</a>. Signaling Path Border Element ..............................<a href="#page-4">4</a>
      <a href="#section-3.2">3.2</a>. Data Path Border Element ...................................<a href="#page-4">4</a>
      <a href="#section-3.3">3.3</a>. Session Establishment Data .................................<a href="#page-4">4</a>
      <a href="#section-3.4">3.4</a>. Call Routing ...............................................<a href="#page-5">5</a>
      <a href="#section-3.5">3.5</a>. PSTN .......................................................<a href="#page-5">5</a>
      <a href="#section-3.6">3.6</a>. IP Path ....................................................<a href="#page-5">5</a>
      <a href="#section-3.7">3.7</a>. Peer Network ...............................................<a href="#page-5">5</a>
      <a href="#section-3.8">3.8</a>. Service Provider ...........................................<a href="#page-5">5</a>
      <a href="#section-3.9">3.9</a>. SIP Service Provider .......................................<a href="#page-6">6</a>
   <a href="#section-4">4</a>. Peering .........................................................<a href="#page-6">6</a>
      <a href="#section-4.1">4.1</a>. Layer 3 Peering ............................................<a href="#page-6">6</a>
      <a href="#section-4.2">4.2</a>. Layer 5 Peering ............................................<a href="#page-6">6</a>
           <a href="#section-4.2.1">4.2.1</a>. Direct Peering ......................................<a href="#page-7">7</a>
           <a href="#section-4.2.2">4.2.2</a>. Indirect Peering ....................................<a href="#page-7">7</a>
           <a href="#section-4.2.3">4.2.3</a>. On-Demand Peering ...................................<a href="#page-7">7</a>
           <a href="#section-4.2.4">4.2.4</a>. Static Peering ......................................<a href="#page-7">7</a>
      <a href="#section-4.3">4.3</a>. Functions ..................................................<a href="#page-7">7</a>
           <a href="#section-4.3.1">4.3.1</a>. Signaling Function ..................................<a href="#page-7">7</a>
           <a href="#section-4.3.2">4.3.2</a>. Media Function ......................................<a href="#page-8">8</a>
           <a href="#section-4.3.3">4.3.3</a>. Look-Up Function ....................................<a href="#page-8">8</a>
           <a href="#section-4.3.4">4.3.4</a>. Location Routing Function ...........................<a href="#page-8">8</a>
   <a href="#section-5">5</a>. Federations .....................................................<a href="#page-8">8</a>
   <a href="#section-6">6</a>. Security Considerations .........................................<a href="#page-9">9</a>
   <a href="#section-7">7</a>. Acknowledgments .................................................<a href="#page-9">9</a>
   <a href="#section-8">8</a>. Informative References .........................................<a href="#page-10">10</a>

<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>.  Introduction</span>

   The term "Voice over IP Peering" (VoIP Peering) has historically been
   used to describe a wide variety of practices pertaining to the
   interconnection of service provider networks and to the delivery of
   Session Initiation Protocol (SIP [<a href="#ref-2" title="&quot;SIP: Session Initiation Protocol&quot;">2</a>]) call termination over those
   interconnections.

   The discussion of these interconnections has at times been confused
   by the fact that the term "peering" is used in various contexts to
   describe interconnection at different levels in a protocol stack.
   Session Peering for Multimedia Interconnect focuses on how to
   identify and route real-time sessions (such as VoIP calls) at the
   session layer, and it does not (necessarily) cover the exchange of
   packet-routing data or media sessions.  In particular, "layer 5
   network" is used here to refer to the interconnection between SIP




<span class="grey">Malas &amp; Meyer                Informational                      [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc5486">RFC 5486</a>                 SPEERMINT Terminology                March 2009</span>


   servers, as opposed to interconnection at the IP layer ("layer 3").
   The term "peering" will be used throughout the remainder of the
   document for the purpose of indicating a layer 5 interconnection.

   This document introduces standard terminology for use in
   characterizing real-time session peering.  Note however, that while
   this document is primarily targeted at the VoIP peering case, the
   terminology described here is applicable to those cases in which
   service providers peer using SIP signaling (defined as SIP Service
   Providers; see <a href="#section-3.9">Section 3.9</a>) for non-voice or quasi-real-time
   communications like instant messaging.

   The remainder of this document is organized as follows: <a href="#section-2">Section 2</a>
   provides the general context for the Session PEERing for Multimedia
   INTerconnect working group (SPEERMINT).  <a href="#section-3">Section 3</a> provides the
   general definitions for real-time, SIP-based communication, with
   initial focus on the VoIP peering case, and <a href="#section-4">Section 4</a> defines the
   terminology describing the various forms of peering.  Finally,
   <a href="#section-5">Section 5</a> introduces the concept of federations.

<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>.  SPEERMINT Context</span>

   SPEERMINT provides a peering framework that leverages the building
   blocks of existing IETF-defined protocols such as SIP [<a href="#ref-2" title="&quot;SIP: Session Initiation Protocol&quot;">2</a>] and ENUM
   [<a href="#ref-4" title="&quot;The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)&quot;">4</a>].  While the SPEERMINT working group describes the use of these
   protocols in peering, it does not redefine how these protocols use
   input or output variables necessary for creating Session
   Establishment Data (SED) or the methods in which this data will be
   used during the peering process.  See <a href="#section-3.3">Section 3.3</a> for additional
   detail on SED and its principal variables such as Uniform Resource
   Identifiers (URIs) [<a href="#ref-3" title="&quot;Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI)&quot;">3</a>] and telephone numbers of E.164 numbers [<a href="#ref-5" title="&quot;The International Public Telecommunication Numbering Plan&quot;">5</a>].
   For example, while the SPEERMINT working group is not limited to the
   use of telephone numbers, an E.164 number may be used as a key in an
   E.164-to-URI mapping using ENUM.  This mapping involves looking up
   Naming Authority Pointer (NAPTR) records in the DNS, and results in a
   SIP URI.  The process for deriving this information has already been
   defined in [<a href="#ref-4" title="&quot;The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)&quot;">4</a>], but is used as a building block for SPEERMINT SED, on
   which the subsequent call routing is based.  Note that the call-
   routing step does not depend on the presence of an E.164 number.
   Indeed, the URI resulting from an ENUM query may no longer even
   contain numbers of any type.  In particular, the SIP URI can be
   advertised in various other ways, such as on a web page.

   Finally, note that the term "call" is being used here in the most
   general sense, i.e., call routing and session routing are used
   interchangeably.





<span class="grey">Malas &amp; Meyer                Informational                      [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc5486">RFC 5486</a>                 SPEERMINT Terminology                March 2009</span>


<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>.  General Definitions</span>

<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>.  Signaling Path Border Element</span>

   A signaling path border element (SBE) is located on the
   administrative border of a domain through which inter-domain session
   layer messages will flow.  It typically provides signaling functions
   such as protocol inter-working (for example, H.323 to SIP), identity
   and topology hiding, and Session Admission Control for a domain.

<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>.  Data Path Border Element</span>

   A data path border element (DBE) is located on the administrative
   border of a domain through which flows the media associated with an
   inter-domain session.  It typically provides media-related functions
   such as deep packet inspection and modification, media relay, and
   firewall-traversal support.  The DBE may be controlled by the SBE.

<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>.  Session Establishment Data</span>

   Session Establishment Data, or SED, is the data used to route a call
   to the next hop associated with the called domain's ingress point.  A
   domain's ingress point might, for example, be the location derived
   from various types of DNS records (NAPTR, SRV, or A record) [<a href="#ref-1" title="&quot;A DNS RR for specifying the location of services (DNS SRV)&quot;">1</a>] that
   resulted from the resolution of the SIP URI.

   More specifically, the SED is the set of parameters that the outgoing
   SBEs need to complete the call, and may include:

      o  A destination SIP URI

      o  A SIP proxy or ingress SBE to send the INVITE to, including:

         -  Fully Qualified Domain Name (FQDN)

         -  Port

         -  Transport Protocol (UDP [<a href="#ref-8" title="&quot;User Datagram Protocol&quot;">8</a>], TCP [<a href="#ref-9" title="&quot;DoD standard Transmission Control Protocol&quot;">9</a>], and TLS [<a href="#ref-7" title="&quot;The Transport Layer Security (TLS) Protocol Version 1.2&quot;">7</a>])

      o Security parameters, including:

         -  TLS certificate to use

         -  TLS certificate to expect

         -  TLS certificate verification setting





<span class="grey">Malas &amp; Meyer                Informational                      [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc5486">RFC 5486</a>                 SPEERMINT Terminology                March 2009</span>


      o  Optional resource control parameters such as:

         -  Limits on the total number of call initiations to a peer

         -  Limits on SIP transactions per second

<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>.  Call Routing</span>

   Call routing is the set of processes and rules used to route a call
   and any subsequent mid-dialog SIP requests to their proper (SIP)
   destination.  More generally, call routing can be thought of as the
   set of processes and rules that are used to route a real-time session
   to its termination point.

<span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>.  PSTN</span>

   The term "PSTN" refers to the Public Switched Telephone Network.  In
   particular, the PSTN refers to the collection of interconnected,
   circuit-switched, voice-oriented public telephone networks, both
   commercial and government-owned.  In general, PSTN terminals are
   addressed using E.164 numbers; however, various dial-plans (such as
   emergency services dial-plans) may not directly use E.164 numbers.

<span class="h3"><a class="selflink" id="section-3.6" href="#section-3.6">3.6</a>.  IP Path</span>

   For the purposes of this document, an IP path is defined to be a
   sequence of zero or more IP router hops.

<span class="h3"><a class="selflink" id="section-3.7" href="#section-3.7">3.7</a>.  Peer Network</span>

   This document defines a peer network as the set of SIP user agents
   (UAs) (customers) that are associated with a single administrative
   domain and can be reached via some IP path.  Note that such a peer
   network may also contain end-users who are located on the PSTN (and
   hence may also be interconnected with the PSTN) as long as they are
   also reachable via some IP path.

<span class="h3"><a class="selflink" id="section-3.8" href="#section-3.8">3.8</a>.  Service Provider</span>

   A Service Provider (SP) is defined to be an entity that provides
   layer 3 (IP) transport of SIP signaling and media packets.  Example
   services may include, but are not limited to, Ethernet Private Line
   (EPL), Frame Relay, and IP Virtual Private Network (VPN).  An example
   of this may be an Internet Service Provider (ISP).







<span class="grey">Malas &amp; Meyer                Informational                      [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc5486">RFC 5486</a>                 SPEERMINT Terminology                March 2009</span>


<span class="h3"><a class="selflink" id="section-3.9" href="#section-3.9">3.9</a>.  SIP Service Provider</span>

   A SIP Service Provider (SSP) is an entity that provides session
   services utilizing SIP signaling to its customers.  In the event that
   the SSP is also a function of the SP, it may also provide media
   streams to its customers.  Such an SSP may additionally be peered
   with other SSPs.  An SSP may also interconnect with the PSTN.  An SSP
   may also be referred to as an Internet Telephony Service Provider
   (ITSP).  While the terms ITSP and SSP are frequently used
   interchangeably, this document and other subsequent SIP peering-
   related documents should use the term SSP.  SSP more accurately
   depicts the use of SIP as the underlying layer 5 signaling protocol.

<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>.  Peering</span>

   While the precise definition of the term "peering" is the subject of
   considerable debate, peering in general refers to the negotiation of
   reciprocal interconnection arrangements, settlement-free or
   otherwise, between operationally independent service providers.

   This document distinguishes two types of peering, layer 3 peering and
   layer 5 peering, which are described below.

<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>.  Layer 3 Peering</span>

   Layer 3 peering refers to interconnection of two service providers'
   networks for the purposes of exchanging IP packets that are destined
   for one (or both) of the peer's networks.  Layer 3 peering is
   generally agnostic to the IP payload, and is frequently achieved
   using a routing protocol such as the Border Gateway Protocol (BGP)
   [<a href="#ref-6" title="&quot;A Border Gateway Protocol 4 (BGP-4)&quot;">6</a>] to exchange the required routing information.

   An alternate, perhaps more operational, definition of layer 3 peering
   is that two peers exchange only customer routes, and hence any
   traffic between peers terminates on one of the peers' networks or the
   peer's customer's network.

<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>.  Layer 5 Peering</span>

   Layer 5 (session) peering refers to interconnection of two SSPs for
   the purposes of routing real-time (or quasi-real-time) call signaling
   between their respective customers using SIP methods.  Such peering
   may be direct or indirect (see <a href="#section-4.2.1">Section 4.2.1</a> and <a href="#section-4.2.2">Section 4.2.2</a>
   below).  Note that media streams associated with this signaling (if
   any) are not constrained to follow the same set of IP paths.






<span class="grey">Malas &amp; Meyer                Informational                      [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc5486">RFC 5486</a>                 SPEERMINT Terminology                March 2009</span>


<span class="h4"><a class="selflink" id="section-4.2.1" href="#section-4.2.1">4.2.1</a>.  Direct Peering</span>

   Direct peering describes those cases in which two SSPs peer without
   using an intervening layer 5 network.

<span class="h4"><a class="selflink" id="section-4.2.2" href="#section-4.2.2">4.2.2</a>.  Indirect Peering</span>

   Indirect, or transit, peering refers to the establishment of either a
   signaling and media path or a signaling path alone via one (or more)
   layer 5 transit network(s).  In this case, it is generally required
   that a trust relationship is established between the originating SSP
   and the transit SSP on one side, and between the transit SSP and the
   termination SSP on the other side.

<span class="h4"><a class="selflink" id="section-4.2.3" href="#section-4.2.3">4.2.3</a>.  On-Demand Peering</span>

   SSPs are said to peer on-demand when they are able to exchange SIP
   traffic without any pre-association prior to the origination of a
   real-time transaction (like a SIP message) between the domains.  Any
   information that needs to be exchanged between domains in support of
   peering can be learned through a dynamic protocol mechanism.  On-
   demand peering can occur as direct or indirect.

<span class="h4"><a class="selflink" id="section-4.2.4" href="#section-4.2.4">4.2.4</a>.  Static Peering</span>

   SSPs are said to peer statically when pre-association between
   providers is required for the initiation of any real-time
   transactions (like a SIP message).  Static peering can occur as
   direct or indirect.  An example of static peering is a federation.
   Each of the peers within the federation must first agree on a common
   set of rules and guidelines for peering, thus pre-associating with
   each other prior to initiating session requests.

<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>.  Functions</span>

   The following are terms associated with the functions required for
   peering.

<span class="h4"><a class="selflink" id="section-4.3.1" href="#section-4.3.1">4.3.1</a>.  Signaling Function</span>

   The Signaling Function (SF) performs routing of SIP requests for
   establishing and maintaining calls, and to assist in the discovery or
   exchange of parameters to be used by the Media Function (MF).  The SF
   is a capability of SIP processing elements such as SIP proxies, SBEs,
   and user agents.






<span class="grey">Malas &amp; Meyer                Informational                      [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc5486">RFC 5486</a>                 SPEERMINT Terminology                March 2009</span>


<span class="h4"><a class="selflink" id="section-4.3.2" href="#section-4.3.2">4.3.2</a>.  Media Function</span>

   The Media Function (MF) performs media-related functions such as
   media transcoding and media security implementation between two SSPs.
   The MF is a capability of SIP-session-associated media end-points
   such as DBEs and user agents.

<span class="h4"><a class="selflink" id="section-4.3.3" href="#section-4.3.3">4.3.3</a>.  Look-Up Function</span>

   The Look-Up Function (LUF) determines for a given request the target
   domain to which the request should be routed.  An example of an LUF
   is an ENUM [<a href="#ref-4" title="&quot;The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)&quot;">4</a>] look-up or a SIP INVITE request to a SIP proxy
   providing redirect responses for peers.

   In some cases, some entity (usually a 3rd party or federation)
   provides peering assistance to the originating SSP by providing this
   function.  The assisting entity may provide information relating to
   direct (<a href="#section-4.2.1">Section 4.2.1</a>) or indirect (<a href="#section-4.2.2">Section 4.2.2</a>) peering as
   necessary.

<span class="h4"><a class="selflink" id="section-4.3.4" href="#section-4.3.4">4.3.4</a>.  Location Routing Function</span>

   The Location Routing Function (LRF) determines for the target domain
   of a given request the location of the SF in that domain, and
   optionally develops other SED required to route the request to that
   domain.  An example of the LRF may be applied to either example in
   <a href="#section-4.3.3">Section 4.3.3</a>.  Once the ENUM response or SIP 302 redirect is
   received with the destination's SIP URI, the LRF must derive the
   destination peer's SF from the FQDN in the domain portion of the URI.

   In some cases, some entity (usually a 3rd party or federation)
   provides peering assistance to the originating SSP by providing this
   function.  The assisting entity may provide information relating to
   direct (<a href="#section-4.2.1">Section 4.2.1</a>) or indirect (<a href="#section-4.2.2">Section 4.2.2</a>) peering as
   necessary.

<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>.  Federations</span>

   A federation is a group of SSPs that agree to exchange calls with
   each other via SIP and who agree on a set of administrative rules for
   such calls (settlement, abuse-handling, etc.) and specific rules for
   the technical details of the peering.

   The following provides examples of rules that the peers of a
   federation may agree to and enforce upon all participants:

      o  Common domain for all federation peers (e.g.,
         bob@peer1.federation.example.com)



<span class="grey">Malas &amp; Meyer                Informational                      [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc5486">RFC 5486</a>                 SPEERMINT Terminology                March 2009</span>


      o  Codec rules (e.g., all peers must use the ITU-T G.711 codec
         [<a href="#ref-10">10</a>])

      o  Authentication preference (e.g., all peers must use TLS when
         requesting to establish sessions with other peers)

      o  Transport protocol (e.g., all peers must use TCP)

      o  SIP address resolution mechanisms (e.g., all peers must use
         ENUM for resolving telephone numbers to SIP URIs)

   Finally, note that an SSP can be a member of:

      -  No federation (e.g., the SSP has only bilateral peering
         agreements)

      -  A single federation

      -  Multiple federations

   Also, an SSP can have any combination of bilateral and multilateral
   (i.e., federated) peers.

<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>.  Security Considerations</span>

   This document introduces no new security considerations.  However, it
   is important to note that session peering, as described in this
   document, has a wide variety of security issues that should be
   considered in documents addressing both protocol and use-case
   analysis.

<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>.  Acknowledgments</span>

   Many of the definitions were gleaned from detailed discussions on the
   SPEERMINT, ENUM, and SIPPING mailing lists.  Scott Brim, John Elwell,
   Mike Hammer, Eli Katz, Gaurav Kulshreshtha, Otmar Lendl, Jason
   Livingood, Alexander Mayrhofer, Jean-Francois Mule, Jonathan
   Rosenberg, David Schwartz, Richard Shockey, Henry Sinnreich, Richard
   Stastny, Hannes Tschofenig, Adam Uzelac, and Dan Wing all made
   valuable contributions to early versions of this document.  Patrik
   Faltstrom also made many insightful comments to early versions of
   this document.









<span class="grey">Malas &amp; Meyer                Informational                      [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc5486">RFC 5486</a>                 SPEERMINT Terminology                March 2009</span>


<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>.  Informative References</span>

   [<a id="ref-1">1</a>]   Gulbrandsen, A., Vixie, P., and L. Esibov, "A DNS RR for
         specifying the location of services (DNS SRV)", <a href="./rfc2782">RFC 2782</a>,
         February 2000.

   [<a id="ref-2">2</a>]   Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A.,
         Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP:
         Session Initiation Protocol", <a href="./rfc3261">RFC 3261</a>, June 2002.

   [<a id="ref-3">3</a>]   Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part
         Four: The Uniform Resource Identifiers (URI)", <a href="./rfc3404">RFC 3404</a>,
         October 2002.

   [<a id="ref-4">4</a>]   Faltstrom, P. and M. Mealling, "The E.164 to Uniform Resource
         Identifiers (URI) Dynamic Delegation Discovery System (DDDS)
         Application (ENUM)", <a href="./rfc3761">RFC 3761</a>, April 2004.

   [<a id="ref-5">5</a>]   International Telecommunications Union, "The International
         Public Telecommunication Numbering Plan", ITU-T Recommendation
         E.164, February 2005.

   [<a id="ref-6">6</a>]   Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A Border
         Gateway Protocol 4 (BGP-4)", <a href="./rfc4271">RFC 4271</a>, January 2006.

   [<a id="ref-7">7</a>]  Dierks, T. and E. Rescorla, "The Transport Layer Security (TLS)
         Protocol Version 1.2", <a href="./rfc5246">RFC 5246</a>, August 2008.

   [<a id="ref-8">8</a>]  Postel, J., "User Datagram Protocol", STD 6, <a href="./rfc768">RFC 768</a>, August
         1980.

   [<a id="ref-9">9</a>]  Postel, J., "DoD standard Transmission Control Protocol", <a href="./rfc761">RFC</a>
         <a href="./rfc761">761</a>, January 1980.

   [<a id="ref-10">10</a>]  ITU Recommendation G.711 (11/88) - Pulse code modulation (PCM)
         of voice frequencies.

Authors' Addresses

   Daryl Malas (editor)
   CableLabs
   858 Coal Creek Circle
   Louisville, CO  80027
   USA
   EMail: d.malas@cablelabs.com

   David Meyer (editor)
   EMail: dmm@1-4-5.net



Malas &amp; Meyer                Informational                     [Page 10]
</pre>