Network Working Group                                               B.Natale 
Internet Draft                                         NexTone Communications 
Expires: August 28, 2006                                        February 2006 
 
 
           Requirements for SIP-based VoIP Interconnection 
              draft-natale-sip-voip-requirements-00.txt 
 
Status of this Memo 
 
   By submitting this Internet-Draft, each author represents that any 
   applicable patent or other IPR claims of which he or she is aware have 
   been or will be disclosed, and any of which he or she becomes aware 
   will be disclosed, in accordance with Section 6 of BCP 79. 
    
   Internet-Drafts are working documents of the Internet Engineering Task 
   Force (IETF), its areas, and its working groups.  Note that other 
   groups may also distribute working documents as Internet-Drafts. 
    
   Internet-Drafts are draft documents valid for a maximum of six months 
   and may be updated, replaced, or obsoleted by other documents at any 
   time.  It is inappropriate to use Internet-Drafts as reference material 
   or to cite them other than as "work in progress." 
    
   The list of current Internet-Drafts can be accessed at 
   http://www.ietf.org/ietf/1id-abstracts.txt. 
    
   The list of Internet-Draft Shadow Directories can be accessed at 
   http://www.ietf.org/shadow.html. 
    
   This Internet-Draft will expire on August 21, 2006. 
 
Copyright Notice 
 
   Copyright (C) The Internet Society (2006). 
 
Abstract 
 
   This is an initial draft for consideration by the SPEERMINT WG as a 
   candidate for the chartered work item dealing with "the minimum set of 
   requirements for SIP-based VoIP interconnection (BCP)", due in March 
   2007.  In its present form, this draft is intended solely to provide a 
   basis for WG discussion about requirements selection.  As such, it is 
   primarily structural and descriptive in nature, leaving prescriptive 
   content to later revisions driven by WG consensus. 
 
 
 
 
Natale              Expires August 28, 2006           [Page 1] 



Internet Draft  SIP-Based VoIP Peering Requirements  Feb 2006 
 
 
 
 
 
 
 
Table of Contents 
 
1. Introduction   4 
2. Terminology   5 
      2.1 VoIP Peering Architectures   5 
      2.2 Direct Peering   5 
      2.3 Interconnect Peering   6 
      2.4 Access Peering   6 
3. Requirements Catalogue   6 
      3.1 0.0000  General Requirements   6 
      3.2 0.1000  Peering Architectures   6 
      3.3 0.1100  Security   6 
      3.4 0.1200  Resiliency   6 
      3.5 0.1300  Performance   6 
      3.6 0.1400  Scalability   6 
      3.7 0.2000  Peering Agreements   6 
      3.8 0.2100  Regulatory Requirements   7 
      3.9 0.2110  Equal Access   7 
      3.10 0.2120  Lawful Intercept   7 
      3.11 0.2130  Number Portability   7 
      3.12 0.2150  PSTN Interfaces   7 
      3.13 0.2200  Traffic Exchange Facilitation   7 
      3.14 0.2300  Extensibility to New Peering Entities   7 
      3.15 0.2400  Service Independence   7 
      3.16 0.2500  Feature Transparency   7 
      3.17 0.3000  Service Discovery   7 
      3.18 0.4000  Service Location   7 
      3.19 0.5000  Signaling (SIP, RFC 3261)   7 
      3.20 0.5100  SIP Extensions   7 
      3.21 0.6000  Proxy Functions   7 
      3.22 0.7000  Addressing   7 
      3.23 0.8000  Routing (Policy-Based, Trust Relationships)   7 
      3.24 0.8100  Signaling Routing   7 
      3.25 0.8200  Media Routing   7 
      3.26 0.8300  Call Routing   7 
      3.27 0.8400  Session Routing   7 
      3.28 0.9000  Transport   7 
      3.29 1.0000  Network Architecture   7 
 
 
Natale             Expires August 28, 2006            [Page 2] 



Internet Draft  SIP-Based VoIP Peering Requirements  Feb 2006 
      3.30 1.1000  Reference Architecture   8 
      3.31 1.1100  Transport (udp, tcp, sctp)   8 
      3.32 1.1200  Addressing   8 
      3.33 1.1300  DNS (SRV) based Requirements   8 
      3.34 1.1400  Adaptive Routing   8 
      3.35 1.1500  Hairpin handling   8 
      3.36 1.1600  Forking v/s Non Forking   8 
      3.37 1.2000  Error Handling Requirements   8 
      3.38 1.2100  Interpretation of Error Codes   8 
      3.39 1.3000  Media Resources   8 
      3.40 1.3100  Codec Support   8 
      3.41 1.3200  Media Processing   8 
      3.42 1.5000  Interworking   8 
      3.43 1.5100  Caller/Callee Preferences Mismatch   8 
      3.44 1.5200  Transcoding   8 
      3.45 1.6000  Call Diversion and Forwarding   8 
      3.46 2.0000  Operations Management   8 
      3.47 2.1000  Operational Measurements   8 
      3.48 2.1100  Interconnect Performance   8 
      3.49 2.1200  Application Performance   8 
      3.50 2.1300  Customer Perception of Service Performance   8 
      3.51 2.1400  Engineering Operations Reports   8 
      3.52 2.1500  Business Operations Reports   9 
      3.53 2.1600  IP destinations   9 
      3.54 2.1610  Routes/breakouts within IP destinations   9 
      3.55 2.2000  Network and Systems Management   9 
      3.56 2.2100  Control Points   9 
      3.57 2.2200  Alarms   9 
      3.58 2.2300  Provisioning   9 
      3.59 2.2400  Centralized Management   9 
      3.60 2.2500  Distributed Management   9 
      3.61 2.3000  Session Management   9 
      3.62 2.7000  International Operations Support   9 
      3.63 2.8000  Integration with existing NOC/OSS/BSS Functions   9 
      3.64 2.9000  Legacy Peering Agreements   9 
      3.65 3.0000  Partitioning   9 
      3.66 3.1000  Segmentation/Classification of Sessions   9 
      3.67 3.2000  Segmentation/Classification of Traffic   9 
      3.68 3.3000  Numbering Plans   9 
      3.69 4.0000  Accounting   9 
      3.70 4.1000  Call Accounting   9 
      3.71 4.1100  CDR Generation   9 
      3.72 4.1200  CDR Storage   9 
      3.73 4.1300  CDR Retrieval   9 
      3.74 4.1400  CDR Streaming   10 
 
 
Natale             Expires August 28, 2006            [Page 3] 



Internet Draft  SIP-Based VoIP Peering Requirements  Feb 2006 
      3.75 4.1500  CDR Reporting   10 
      3.76 4.1600  3rd-Party CDR Support   10 
      3.77 4.2000  Session Accounting   10 
      3.78 4.3000  Billing   10 
      3.79 5.0000  SLAs   10 
      3.80 5.1000  SLA Definition   10 
      3.81 5.2000  SLA Enforcement   10 
      3.82 5.2100  DiffSrv   10 
      3.83 5.2110  Policing   10 
      3.84 5.2120  Re-marking   10 
      3.85 5.3000  Quality of Service (QoS)   10 
      3.86 5.3100  Service Quality Metrics   10 
      3.87 5.3200  Service Quality Reporting   10 
      3.88 5.4000  Call Admission Control   10 
      3.89 5.5000  Session admission control   10 
      3.90 6.0000  Security   10 
      3.91 6.1000  Prevent Denial of Service Attacks   10 
      3.92 6.1100  Prevent SPAM over Internet Telephony (SPIT)   10 
      3.93 6.1200  Prevent Service Abuse   10 
      3.94 6.1300  Prevent Service Theft   10 
      3.95 6.2000  Topology Hiding   10 
      3.96 6.3000  Service Enforcement   11 
      3.97 6.4000  Security Protocols   11 
      3.98 6.4100  Authentication   11 
      3.99 6.4200  Encryption   11 
      3.100 6.5000  Privacy Requirements   11 
      3.101 6.5100  Identity Requirements   11 
      3.102 6.5200  Subscriber Data Protection   11 
      3.103 6.6000  SDP tampering   11 
4. Requirements to Peering Architecture Mapping   11 
5. Acknowledgments   11 
6. Security Considerations   12 
7. IANA Considerations   12 
8. References   12 
      8.1 Normative References   12 
      8.2 Informational References   12 
9. Author's Addresses   12 
10. Full Copyright Statement   13 
11. Intellectual Property   13 
12. Acknowledgment   14 
 
 
1. 
  Introduction 
 

 
 
Natale             Expires August 28, 2006            [Page 4] 



Internet Draft  SIP-Based VoIP Peering Requirements  Feb 2006 
   The SPEERMINT WG addresses the use of the SIP signaling protocol to 
   enable real-time session peering between two or more administrative 
   domains over IP networks.  To achieve the kind of real-time session 
   peering intended, both signaling and media flows must be taken into 
   consideration.  While the long-term goal is to support a variety of 
   "rich media" (multimedia) applications, the initial focus is on SIP-
   based Voice over IP (VoIP). 
    
   This document defines requirements to enable SIP-based VoIP peering 
   among two or more administrative domains.  Valid peering relationships 
   exist in multiple architectures.  Section 3 outlines the collection of 
   all requirements that might individually apply to any applicable 
   peering architecture.  Section 4 presents a tabular view of subset 
   applicability in which the rows are the collection of requirements and 
   the columns are the peering architecture alternatives. 
 
2. 
  Terminology 
 
   In this document, the key words 'MUST', 'MUST NOT', 'REQUIRED',    
   'SHALL', 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'MAY', and 
   'OPTIONAL' are to be interpreted as described in RFC 2119 [RFC2119] and 
   indicate requirement levels for compliant SIP implementations. 
    
2.1 
  VoIP Peering Architectures 
 
   The taxonomy and definitions for presented in this section and used in 
   later sections of this document come from draft-bhatia-sip-peering-
   00.txt (work in progress). [1] 
    
   The following figure comes from that document and provides essential 
   reference terminology: 
 
   +---+   /~~~~~~\    /~~~~\    /~~~~~~~\    /~~~~\    /~~~~~~\   +---+ 
   | O |->(Access-O)->(Core-O)->(Interconn)->(Core-T)->(Access-T)->| T | 
   +---+   \~~~~~~/    \~~~~/    \~~~~~~~/    \~~~~/    \~~~~~~/   +---+ 
 
 
 
 
2.2 
  Direct Peering 
 
   Direct Peering is the peering between Core-O and Core-T without any 
   other VoIP SP in the middle.  It typically takes two forms depending on 
   how some part of the peering policy may be provisioned, Federation or 
   local policy. 
 
 
Natale             Expires August 28, 2006            [Page 5] 



Internet Draft  SIP-Based VoIP Peering Requirements  Feb 2006 
    
2.3 
  Interconnect Peering 
 
   In most cases this model is used when the origination SP does not 
   prefer to directly connect to a termination SP due to business reasons.  
   Interconnect SP may also be used between the access SP and the Core SP 
   due to similar reasons. 
 
2.4 
  Access Peering 
 
   Access Peering may typically be used when the subscriber roams to a 
   place the Core SP does not offer service or is using a Layer 5 aware SP 
   to connect to its Core SP (which may be an ASP or content provider). 
 
3. 
  Requirements Catalogue 
 
   Each candidate requirements is presented in a separate subsection.  In 
   addition to the subsection number, an ordered numeric requirement ID 
   and a requirement title are used to identify each requirement.  The 
   numeric requirement ID ordering is intended to convey tentative degrees 
   of both association and, where appropriate, hierarchy. 
    
   Descriptive and prescriptive text will be added in future versions of 
   this document, once the WG has reached consensus on the specific set of 
   requirements to be included. 
    
   Also, requirements statements in [2] must be reconciled with this and 
   other documents.  At present, the intended context of those 
   requirements is unclear -- i.e., intended to guide WG work or actual 
   peering operations? 
 
3.1 
  0.0000  General Requirements 
 
3.2 
  0.1000  Peering Architectures 
 
3.3 
  0.1100  Security 
 
3.4 
  0.1200  Resiliency 
 
3.5 
  0.1300  Performance 
 
3.6 
  0.1400  Scalability 
 
3.7 
  0.2000  Peering Agreements 
 
 
 
Natale             Expires August 28, 2006            [Page 6] 



Internet Draft  SIP-Based VoIP Peering Requirements  Feb 2006 
3.8 
  0.2100  Regulatory Requirements 
 
3.9 
  0.2110  Equal Access 
 
3.10 
   0.2120  Lawful Intercept 
 
3.11 
   0.2130  Number Portability 
 
3.12 
   0.2150  PSTN Interfaces 
 
3.13 
   0.2200  Traffic Exchange Facilitation 
 
3.14 
   0.2300  Extensibility to New Peering Entities 
 
3.15 
   0.2400  Service Independence 
 
3.16 
   0.2500  Feature Transparency 
 
3.17 
   0.3000  Service Discovery 
 
3.18 
   0.4000  Service Location 
 
3.19 
   0.5000  Signaling (SIP, RFC 3261) 
 
3.20 
   0.5100  SIP Extensions 
 
3.21 
   0.6000  Proxy Functions 
 
3.22 
   0.7000  Addressing 
 
3.23 
   0.8000  Routing (Policy-Based, Trust Relationships) 
 
3.24 
   0.8100  Signaling Routing 
 
3.25 
   0.8200  Media Routing 
 
3.26 
   0.8300  Call Routing 
 
3.27 
   0.8400  Session Routing 
 
3.28 
   0.9000  Transport 
 
3.29 
   1.0000  Network Architecture 
 

 
 
Natale             Expires August 28, 2006            [Page 7] 



Internet Draft  SIP-Based VoIP Peering Requirements  Feb 2006 
3.30 
   1.1000  Reference Architecture 
 
3.31 
   1.1100  Transport (udp, tcp, sctp) 
 
3.32 
   1.1200  Addressing 
 
3.33 
   1.1300  DNS (SRV) based Requirements 
 
3.34 
   1.1400  Adaptive Routing 
 
3.35 
   1.1500  Hairpin handling 
 
3.36 
   1.1600  Forking v/s Non Forking 
 
3.37 
   1.2000  Error Handling Requirements 
 
3.38 
   1.2100  Interpretation of Error Codes 
 
3.39 
   1.3000  Media Resources 
 
3.40 
   1.3100  Codec Support 
 
3.41 
   1.3200  Media Processing 
 
3.42 
   1.5000  Interworking 
 
3.43 
   1.5100  Caller/Callee Preferences Mismatch 
 
3.44 
   1.5200  Transcoding 
 
3.45 
   1.6000  Call Diversion and Forwarding 
 
3.46 
   2.0000  Operations Management 
 
3.47 
   2.1000  Operational Measurements 
 
3.48 
   2.1100  Interconnect Performance 
 
3.49 
   2.1200  Application Performance 
 
3.50 
   2.1300  Customer Perception of Service Performance 
 
3.51 
   2.1400  Engineering Operations Reports 
 

 
 
Natale             Expires August 28, 2006            [Page 8] 



Internet Draft  SIP-Based VoIP Peering Requirements  Feb 2006 
3.52 
   2.1500  Business Operations Reports 
 
3.53 
   2.1600  IP destinations 
 
3.54 
   2.1610  Routes/breakouts within IP destinations 
 
3.55 
   2.2000  Network and Systems Management 
 
3.56 
   2.2100  Control Points 
 
3.57 
   2.2200  Alarms 
 
3.58 
   2.2300  Provisioning 
 
3.59 
   2.2400  Centralized Management 
 
3.60 
   2.2500  Distributed Management 
 
3.61 
   2.3000  Session Management 
 
3.62 
   2.7000  International Operations Support 
 
3.63 
   2.8000  Integration with existing NOC/OSS/BSS Functions 
 
3.64 
   2.9000  Legacy Peering Agreements 
 
3.65 
   3.0000  Partitioning 
 
3.66 
   3.1000  Segmentation/Classification of Sessions 
 
3.67 
   3.2000  Segmentation/Classification of Traffic 
 
3.68 
   3.3000  Numbering Plans 
 
3.69 
   4.0000  Accounting 
 
3.70 
   4.1000  Call Accounting 
 
3.71 
   4.1100  CDR Generation 
 
3.72 
   4.1200  CDR Storage 
 
3.73 
   4.1300  CDR Retrieval 
 

 
 
Natale             Expires August 28, 2006            [Page 9] 



Internet Draft  SIP-Based VoIP Peering Requirements  Feb 2006 
3.74 
   4.1400  CDR Streaming 
 
3.75 
   4.1500  CDR Reporting 
 
3.76 
   4.1600  3rd-Party CDR Support 
 
3.77 
   4.2000  Session Accounting 
 
3.78 
   4.3000  Billing 
 
3.79 
   5.0000  SLAs 
 
3.80 
   5.1000  SLA Definition 
 
3.81 
   5.2000  SLA Enforcement 
 
3.82 
   5.2100  DiffSrv 
 
3.83 
   5.2110  Policing 
 
3.84 
   5.2120  Re-marking 
 
3.85 
   5.3000  Quality of Service (QoS) 
 
3.86 
   5.3100  Service Quality Metrics 
 
3.87 
   5.3200  Service Quality Reporting  
 
3.88 
   5.4000  Call Admission Control 
 
3.89 
   5.5000  Session admission control 
 
3.90 
   6.0000  Security 
 
3.91 
   6.1000  Prevent Denial of Service Attacks 
 
3.92 
   6.1100  Prevent SPAM over Internet Telephony (SPIT) 
 
3.93 
   6.1200  Prevent Service Abuse 
 
3.94 
   6.1300  Prevent Service Theft 
 
3.95 
   6.2000  Topology Hiding 
 
 
 
Natale             Expires August 28, 2006            [Page 
10] 



Internet Draft  SIP-Based VoIP Peering Requirements  Feb 2006 
3.96 
   6.3000  Service Enforcement 
 
3.97 
   6.4000  Security Protocols 
 
3.98 
   6.4100  Authentication 
 
3.99 
   6.4200  Encryption 
 
3.100 
    6.5000  Privacy Requirements 
 
3.101 
    6.5100  Identity Requirements 
 
3.102 
    6.5200  Subscriber Data Protection 
 
3.103 
    6.6000  SDP tampering 
 
 
 
 
 
 
 
 
 
 
 
 
4. 
  Requirements to Peering Architecture Mapping 
 
   In a future version of this document, this section will present an 
   ASCII-art table with the requirements listed as row headings and the 
   peering architectures listed as column headings.  Some scheme such as 
   the following (TBD by WG consensus) will be used to denote 
   applicability: 
    
   M = Mandatory 
   R = Recommended 
   O = Optional 
   X = Not applicable 
 
 
5. 
  Acknowledgments 
 

 
 
Natale             Expires August 28, 2006            [Page 
11] 



Internet Draft  SIP-Based VoIP Peering Requirements  Feb 2006 
   The eventual list will likely be long as we anticipate substantial WG 
   and (hopefully) industry input on this document before it reaches BCP 
   quality.  The relevant drafts by Dave Meyer and Medhavi Bhatia have 
   been very helpful even at this early stage. 
 
 
6. 
  Security Considerations 
 
   This document will likely not introduce any new security 
   considerations, but individual requirements will touch upon known 
   vulnerabilities and recommend solutions from existing practice. 
 
 
7. 
  IANA Considerations 
 
   This document creates no new requirements on IANA namespaces [RFC2434]. 
 
8. 
  References 
 
8.1 
  Normative References 
 
   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate 
              Requirement Levels", BCP 14, RFC 2119, March 1997 
 
8.2 
  Informational References 
 
   [RFC2434]  Narten, T. and H. Alvestrand, "Guidelines for Writing an 
              IANA Considerations Section in RFCs", BCP 26, RFC 2434, 
              October 1998. 
 
   [1]        Bhatia, M., "Requirements for Route Policy and Architecture 
              in SIP based Peering", draft-bhatia-sip-peering-00.txt 
              (work in progress), February 2006. 
 
   [2]        Meyer, D., " SPEERMINT Requirements and Terminology", 
              draft-ietf-speermint-reqs-and-terminology-01.txt (work in  
              progress), February 2006. 
 
 
9. 
  Author's Addresses 
 
   Bob Natale 
   NexTone Communications 
   101 Orchard Ridge Dr 
 
 
Natale             Expires August 28, 2006            [Page 
12] 



Internet Draft  SIP-Based VoIP Peering Requirements  Feb 2006 
   Gaithersburg MD 20878 USA 
   Email: bnatale@nextone.com 
 
10. 
  Full Copyright Statement 
 
   Copyright (C) The Internet Society (2006). 
 
   This document is subject to the rights, licenses and restrictions 
   contained in BCP 78, and except as set forth therein, the authors 
   retain all their rights. 
 
   This document and the information contained herein are provided on an 
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 
   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 
   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 
   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 
 
 
11. 
  Intellectual Property 
 
   The IETF takes no position regarding the validity or scope of any 
   Intellectual Property Rights or other rights that might be claimed to 
   pertain to the implementation or use of the technology described in 
   this document or the extent to which any license under such rights 
   might or might not be available; nor does it represent that it has 
   made any independent effort to identify any such rights.  Information 
   on the procedures with respect to rights in RFC documents can be 
   found in BCP 78 and BCP 79. 
 
   Copies of IPR disclosures made to the IETF Secretariat and any 
   assurances of licenses to be made available, or the result of an 
   attempt made to obtain a general license or permission for the use of 
   such proprietary rights by implementers or users of this 
   specification can be obtained from the IETF on-line IPR repository at 
   http://www.ietf.org/ipr. 
 
   The IETF invites any interested party to bring to its attention any 
   copyrights, patents or patent applications, or other proprietary 
   rights that may cover technology that may be required to implement 
   this standard.  Please address the information to the IETF at 
   ietf-ipr@ietf.org. 
 
 
 
Natale             Expires August 28, 2006            [Page 
13] 



Internet Draft  SIP-Based VoIP Peering Requirements  Feb 2006 
 
12. 
  Acknowledgment 
 
   Funding for the RFC Editor function is currently provided by the 
   Internet Society. 







































 
 
Natale             Expires August 28, 2006            [Page 
14]