1. SIP Forum Tech WG SIP Phone Task Group Initial Meeting September 8th, 2005

2. 2 Welcome!Rohan Mahy Review of SIP Forum IPR PolicyRohan Mahy Election of Task Group LeadRohan Mahy Background on Task Group ProposalFrancois Audet Reading of Approved CharterRohan Mahy Discussion of Task Group scopeTask Group Lead (as moderator) Task Group TimelineTask Group Lead AGENDA

3. 3 Greater network and cost efficiencies  Eliminate need for expensive TDM hardware  Eliminate need for dual wiring  In the Service Provider market: cheap voice service Higher quality of service  Reduce voice latency with TDM conversion no longer needed (TDM gateway removed) Increased features and functionality  Seamless calling with Internet-based SIP endpoints  End-to-End IP Feature Transparency  New SIP features −Presence −Instant messaging −Video −On-phone browser Integration with Business applications and Web services End-to-end security Benefits of SIP Phones

4. 4 There is not currently a well-defined, standard approach for interfacing SIP phones with each other, and with Enterprise SIP Servers, Gateways, and Service providers. SIP Implementations vary greatly among different SIP phone manufacturers, and among enterprises and service providers SIP is currently defined in ~28 RFCs and ~ 170 IETF Drafts SIP is also very flexible, which can lead to inconsistent implementations. Only basic interoperability is commonly possible Configuration is a significant problem Difficult to compare different feature sets Current State of Interoperability

5. 5 Basic SIP “calls”...sometimes Some SIP features (transfer/REFER) Trivial numbering plans “Closed” networks Lots of manual configuration SIP over UDP What Works Today?

6. 6 Centralized practical management and configuration of devices SIP-Related Issues Proxy and registrar addressing using FQDN MWI and Diversion support for network-based voicemail Numbering/dialing plan (especially when using private phone numbers) TCP and SRV/NAPTR often not implemented Media and Other Consideration Inconsistent methods for DTMF (pass-through or RFC 2833) Inconsistent methods of conveying QoS settings RTCP often not implemented NAT/Firewalls complicate most network designs for SIP services Security (both Signaling, Media and Key exchange) What Usually Doesn’t Work?

7. 7 Potential input documents SIP Telephony Device Requirements and Configuration  IETF SIPPING Individual draft (not working group document)  Points to lots of IETF documents (RFCs and drafts)  http://www.ietf.org/internet-drafts/draft-sinnreich-sipdev-req-07.txt http://www.ietf.org/internet-drafts/draft-sinnreich-sipdev-req-07.txt TIA or other national documents  TIA-811-A (in ballot)  Others?

8. 8 Discussion of Group Scope Issue description The deployment of SIP telephony and multimedia systems among Enterprise and in Service Provider networks of all sizes is entering a phase where SIP phones and other SIP devices are being deployed to replace traditional POTS phones and business phones for economic reasons, as well as to provide new functionality that was not possible with traditional equipment. SIP pushes a lot of the application intelligence to the edge devices such as SIP phones. This is in sharp contrast to the traditional telephony model where phones are stimulus devices controlled by a centralized PBX/Central Office. This shift makes the SIP phones one of the most important components of a SIP network. Deploying SIP phones in a live Enterprise or Service Provider environment requires phones that meet certain requirements in many areas. From a traditional telephony point of view, it is expected that the simplest SIP phones will support basic telephony features, while a high-end business telephone will support a wide range of business telephony features. Other SIP phones will support features such as video, presence and instant messaging. Certain phones will have no display capabilities, others will have a small screen, and yet other will have large color-display screens. Other phones will be SIP applications running on personal computers or PDAs. Certain phones will be mobile, others not. The variety of SIP devices offers lots of choices for Enterprises and Service Providers, but also lots of challenges. Existing SIP standards define a comprehensive set of building blocks that are currently used to achieve basic interconnection between SIP phones, or between SIP phones and SIP Gateways or SIP-enabled IP PBXs. However, the standards do not necessarily address all issues regarding SIP phones, such as configuration, feature capabilities for different business environments, and interoperability. The SIP Phone Task Group is proposed to address these issues. This task group will propose one or more SIP Forum Recommendations that define useful groups of functionality and minimum protocol support, implementation rules, and features needed for a cohesive set of functionality. These groups of functionality could be labeled to make it easier for end-user and administrators to identify phones with a specific minimum feature set consistent with the requirements for the protocol support, implementation rules, and features required for SIP Phones in an Enterprise or Service provider environment. The group will also define usage scenarios for optimizing the user experience for installing and configuring SIP Telephony Devices.

9. 9 Discussion of Group Scope Venue The issue of SIP Phones is appropriate for the SIP Forum for the following reasons: The purpose of this task group is to define configuration guidelines, feature set descriptions and interoperability guidelines using SIP; therefore, the IETF and SIP Forum are the most logical organizations to host this effort. The IETF is not appropriate for the following reasons:  The purpose of this task group is to apply existing SIP standards to its problems statement, not develop new ones.  The recommendations produced by this group will require implementation of a broad range of SIP- related RFCs.  IETF SIPPING has already chosen not to address this topic as a working group item. Many initial members of this task group are expected to be SIP Forum participants

10. 10 Discussion of Group Scope Outputs This task group will produce one or more SIP Forum recommendations that define a common set of implementation rules for SIP phone makers. The recommendation(s) will specify which standards must be supported, provide precise guidance in the areas where the standards leave gaps, and identify a baseline set of features that should be common to SIP phones of various categories. Such guidelines will not preclude the implementation of additional SIP functionality and primitives that do not conflict with the common implementation rules of the recommendation(s).

11. 11 Discussion of Group Scope Some of the specific objectives of the task group are: Specify DHCP, DNS, ENUM, Network configuration, software upgrades, configuration and management requirements Specify SIP protocol feature requirements (MWI, Caller ID, Transfer, etc.) Specify Numbering and Dialing Plan requirements Specific Presence and Instant Messaging requirements Specify Emergency, Security, QoS, Media, Codec requirements Specify NAT Traversal requirements Specify other requirements as necessary

12. 12 Discussion of Group Scope Areas that are explicitly beyond the scope of the SIP Phone Task Group are: 1.National-specific regulation 2.Layer 1-3 aspects, beyond basic configuration

13. 13 Timeline Task Group Formation Complete Initial Meeting 8 Sept 2005 - Working drafts solicited, mailing list discussion Initial Working Drafts Submitted 13 Oct 2005 Rough Consensus 1 Dec 2005 Last Call Complete 12 Jan 2005 Proposed Recommendation Submitted to TWG Chair 26 Jan 2005 Proposed Recommendation Submitted to BoD 23 Feb 2006 BoD Certification 11 May 2006

14. 14 Last Items Instructions for ParticipationTask Group Lead Questions or other concernsAll THANKS FOR PARTICIPATING!!!