december 5, 2003fg3 report focus group 3 interoperability report to nric vi council december 5, 2003...

December 5, 2003 FG3 Report

Network Reliability and Interoperability Council

FOCUS GROUP 3Interoperability

Report to NRIC VI Council

December 5, 2003Cliff Naughton (Boeing)



MISSION

• The Committee [FG3] will prepare analyses and, where appropriate, make recommendations for improving interoperability among networks to achieve the objectives that are contained in Section 256 of the Telecommunications Act of 1996, with particular emphasis on ensuring "the ability of users and information providers to seamlessly and transparently transmit and receive information between and across telecommunications networks."



FG3 Participants

Company NameAllegiance Telecom Mark WillbornAT&T Rick CanadayATIS Jim TurnerAvici Systems Adam DunstanBITS Sam PhillipsBITS Gary RoboffBITS Heather WysonBITS (Citigroup) Dan SchutzerBoeing Cliff NaughtonBoeing Greg CarrasBoeing Mike McInnis Boeing Denis Kuwahara Boeing Monique LundgrenBoeing DNI Kent ShueyCable & Wireless Chris LiljenstolpeCisco Systems Marc LinsnerCisco Systems Art ReillyComcast Corporation Franklyn AthiasCox Communications Albert YoungCTIA (Cellular Telephone and Internet Association) Rick KemperEctel Eric YamGenuity Justin AbornHughes Network System John BorderHughes Network Systems Rod RaglandIntelsat Mark Neibert

Company NameJuniper Networks Marty SchulmanLockheed Martin - Tom KubaLucent Mike Holmes

MCI Dr. David E. (Dave) McDysanNextel Communications Iyad TaraziNokia Inc. Chris WallaceNortel Networks John JenningsQwest Communications Jamal Boudhaouia

SBC Jim LankfordSBC Percy KimbroughSBC Operations John Chapa Jr.Sprint Randall HemauerSprint Robert Dianda

VeriSign/Illuminet Robert M. WienskiVerizon Thomas R. Helmes (Tom)VoiceStream Ron BathVoiceStream Jane Builder (Alternate)



FG3 Status

• Positive, Co-operative team dynamic– Team Composition (31 members)

• Service Providers (wireline, wireless), Vendors, OEMs, Customers, Industry associations

• Methodology– Interoperability focus is Voice-over-IP networks with

circuit switched networks, both wireline and wireless– Gap analysis from published work of standards

bodies (ITU, IETF, etc.) and accepted industry practices to derive best practices and recommended areas of research



Scope of VoIP Interoperability Report

CarrierA

CarrierB

CarrierC

PSTN

IPSP A

IPSP B

IPSP C

IP Networks

Wireless/SatelliteCircuit

WirelineCircuit

DSL CableWireless/SatellitePacket

WirelinePacket

AccessNetworks

PublicTelecommunication

Services

BroadbandAccess

Voice Data VoIP

NetworkInterconnection

Voice Voice VoIP VoIPVoIPData Data Data DataData

Users




TDM

IPSP A

IPSP B

PSTN SP A

PSTN SP B

SIP/H.323 SIP/H.323Public ENUM

DNS DNSSIP/H.323 SIP/H.323

SIP/H.323VoIPQoS

VoIPQoSVoIP

QoS

SIP, SIP-T, BICC, H.323, CMSS

TDM TDMLNP

VoIP=Voice/RTP/UDP/IP

Internal toSP Interfaces

Internal toSP Interfaces

MEGACO/H.248

MEGACO/H.248

SS7

TDM

SIP/H.323

SS7

In ScopeOut of Scope

SS7

SS7

PrivateENUM

DNS

Non-ENUMPrivate

Directory

???



3. VoIP Interoperability Gap Analysis .......................................................................................... 13

3.1 Signaling Architectures.................................................................................................... 15

3.1.1 Signaling System 7 ................................................................................................ 15

3.1.2 Session Initiation Protocol ..................................................................................... 16

3.1.3 SIP to PSTN Interworking...................................................................................... 19

3.1.4 Bearer Independent Call Control ........................................................................... 22

3.1.5 H.323 to PSTN Interworking .................................................................................. 24

3.1.6 H.323 to SIP Interworking...................................................................................... 25

3.1.7 Signaling Transport................................................................................................ 26

3.1.8 Network Management Control Between Different Networks and

Applications (e.g., Wireline and Wireless) ............................................................. 27

3.2 Call Control Architectures................................................................................................ 29

3.2.1 Packet Tandem Architectures................................................................................ 29

3.2.2 PacketCablArchitectures ................................................................................. 30

3.3 Voice Over Wireless ........................................................................................................ 33




3.4 Inter-Provider Interfaces .................................................................................................. 40

3.4.1 Quality of Service................................................................................................... 40

3.4.2 Inter-Provider Usage Metering (Reciprocal Compensation).................................. 49

3.4.3 VoIP Encoding (PCM/TDM)................................................................................... 52

3.4.4 Interoperability With PSTN Station Signaling (e.g., FLASH, DTMF Digits,

Point of Sale) ......................................................................................................... 56

3.5 Directory Services............................................................................................................ 58

3.5.1 Local Number Portability, North American Numbering Plan ................................. 58

3.5.2 ENUM/DNS............................................................................................................ 61

3.6 Safety and Security ......................................................................................................... 73

3.6.1 Support of CALEA.................................................................................................. 73

3.6.2 Teletype Technology (TTY/TDD)........................................................................... 74

3.6.3 E911 VoIP Interoperability ..................................................................................... 76

3.6.4 Network Address Translation (NAT)...................................................................... 78

3.6.5 Firewalls................................................................................................................. 79




• It is evident that ENUM technology is still evolving, as is its deployment and support infrastructure. The industry is making progress on resolution of many outstanding issues. NRIC FG3 makes the following recommendations:

1. The U.S. Government should continue to encourage, support and participate in ENUM deployment at the technical interchange level.

2. The U.S. should formally opt in to the e164.arpa global public ENUM DNS domain. 3. Government and Industry should work together to assign responsibility for administration of

the subdomains of 1.e164.arpa corresponding to NANP and U.S. telephone numbers. The Tier 1 Registries for Country Code 1 should be identified, and processes for managing this data established.

4. Providers implementing alternative deployments to the e164.arpa public ENUM should insure that their deployments provide methods for maintaining the synchronization of their data with the public ENUM and the LNP database, as well as other applicable Number Portability databases in the PSTN.

5. Managers of networks containing clients which use ENUM should provision their local DNS servers with a modern DNS implementation that supports NAPTR records and DNSSEC.

6. Providers implementing authoritative DNS server for ENUM domains should provision those servers per IETF Best Current Practices (currently BCP 40 and BCP 16).

Highlights of Recommended Actions for the FCC



• Address PSTN functionality of call control protocols (SS7, SIP, SIP-T, BICC) within industry bodies such as IETF & SIP Forum

• Call control architectures such as Packet Tandem and PacketCable should be prepared to open these networks for direct interconnect to other IP networks as they evolve using standard signaling protocols

• The industry needs to evolve voice over wireless (WWAN, WLAN, satellite) that addresses a common IP platform that supports end-to-end connectivity and interoperability

• The operational and standards bodies should investigate the possibility of creating a standardized inter-domain QoS metric data interchange format. For example, the extended Real-Time Control Protocol (RTCP) from the IETF could be employed to report on loss and delay variation between service provider and/or enterprise-controlled VoIP gateways. Further work is needed for the harmonization of QoS specifications for wireline networks (e.g., in the ITU and ATIS) and those for wireless networks (e.g., 3GPP).

• It is recommended that the Standards Development Organizations (SDOs) finish their work in the area of TTY transmission on VoIP networks. This is currently

work in progress with an expectation of completion within 12 months.

Highlights of Recommended Actions for the Industry



• Questions?

FG3 Interoperability Report

december 5, 2003fg3 report focus group 3 interoperability report to nric vi council december 5, 2003...

Documents