Specifications

We welcome vendor participation in the continuous development of PacketCable specifications for the PeerConnect ecosystem.

The PeerConnect specifications are developed under the PacketCable vendor agreements.

The PeerConnect services make use of the PacketCable IP Interconnect specifications http://www.cablelabs.com/packetcable/specifications/packetcableIP.html

• PacketCable™ ENUM Server Provisioning Protocol (ESPP) Specification: This protocol is used by the PeerConnect Registry to distribute data to SIP-ENUM addressing servers when the Replication service is chosen between PeerConnect partners.
• PacketCable™ ENUM Server Address Resolution Specification: This specification provides ENUM server requirements for PeerConnect resolution services using the IETF SIP and ENUM protocols. It is the foundation of the CableLabs ENUM server qualification program for ensuring consistency between the data received and processed by the ENUM server and the ENUM server responses to queries.
• PacketCable™ Interconnect Guidelines Specification: This specification defines a common set of SIP interworking procedures at the peering interface between two SIP Service Provider (SSP) networks. It minimizes the SIP interworking issues between them, which reduces the time and cost to establish new SIP peering relationships.

The PeerConnect services make use of a number of IETF documents

The PeerConnect services are designed to increase interoperability between MSOs, vendor SIP implementations and third-party service providers. In order to achieve this, the PeerConnect ecosystem makes use of several Internet Engineering Task Force (IETF) documents:

• Session Peering for Multimedia Interconnect Terminology (RFC 5486): This document defines common terminology used for describing session peering. These terms allow for clarity in describing the service throughout the industry.
• Requirements for SIP-based Session Peering (RFC 6271): This document establishes the protocol requirements to enable session peering. Some of these requirements are met by the PeerConnect services.
• Session Peering for Multimedia Interconnect Architecture (draft-ietf-speermint-architecture): This document defines a peering architecture for SIP, including components, interfaces and the steps necessary to establish sessions between two SIP Service Providers (SSP).  A common architecture model increases interoperability between participants of the PeerConnect services.
• Session Peering Provisioning Protocol (draft-ietf-drinks-spprov): This document defines a standard protocol for provisioning data into a Session Data Registry, such as the PeerConnect registry. The creation of an open provisioning protocol simplifies the ability for MSOs, vendors and other service providers to participate in the PeerConnect services.
• Basic Telephony SIP End-to-End Performance Metrics (RFC 6076): This document defines a set of metrics and their usage to evaluate the performance of end-to-end SIP for telephony services.

How to participate?

As a vendor company, contact the CableLabs team for more information at peerconnect-vendors@cablelabs.com