[Sipconnectit] First Pass at a Charter for SIPconnect Interoperability Certification [SC-IT] Task Group
D.Hancock at CableLabs.com
Fri Mar 23 15:33:52 EDT 2012
Richard - please see inline [dch2] below...
From: Richard Shockey [mailto:richard at shockey.us]
Sent: Wednesday, March 21, 2012 11:02 AM
To: David Hancock; sipconnectit at sipforum.org
Subject: RE: [Sipconnectit] First Pass at a Charter for SIPconnect Interoperability Certification [SC-IT] Task Group
[dch] Is the above ratification date for SC1.0 correct? I thought it was much earlier that March 2011.
[RS> ] Good catch .. youre right it was Jan 2008
With the ratification of SIPconect 1.1 various elements of the industry indicated a preference for a more robust, stringent and formalized process for compliance with the specification including, but not limited to, a formalized and independently verifiable compliance/certification testing process.
The goal of the SIPconnect Interoperability Certification Task Group is to develop appropriate test plans and conformance tools to enable vendors to verify compliance with SIPconnect 1.1.
The Task group may seek to alter or amend SIPconnect 1.1 if it is in the consensus opinion of the Task Group that aspects of the existing specification are unclear, do not promote interoperability or need updating due to underlying changes in the standards. Any amendment of the SIPconnect 1.1 specification is subject to approval by the SIPforum Board of Directors.
The Task group will pay close attention to conformance and interoperability to NENA i3 specifications for E 911 emergency services.
The SIPForum Board of Directors and its Executive Director will independently develop a separate business plans for the use of a "SIPconnect Certified" branding program including requirements, logo usage, funding options and dispute resolution. The SC-IT Task Group is expected to provide ongoing input to this process.
SIPForum Technical Working Group Director: Spencer Dawkins
Proposed [SC-IT] Chairs
Alan Johnston - Avaya
Robert Kinder - Cox
Document Editor Jim Swan - UNH-IOL
Goals and Milestones
1. Immediately review existing test plans from with a view towards merger of all know[RS> ] n documents into a single comprehensive plan.
2. Have preliminary test plans ready for community review on or about June 25
3. Plan Interoperability test event to be held 3rd Quarter of 2012 with special attention not to conflict with SIPForum SIPit.
4. Review Results of test event with goal of finalizing test plans and SIP Forum Board ratification of plans Q4 2012 or Q1 2013 at latest.
[dch] The above list is good through the first interop. Wondering if we should add some specific items to this list around the SC1.1 compliance program, such as .... 5. develop a SC1.1 Compliance Test Plan (possibly using interop test plan as a base), 6. select/develop a SC1.1 compliance test platform ready for the initiation of a SC1.1 Compliance program in early 2013, and
[RS> ] You are welcome to rework these.. text is always welcome. :)
[dch2] On first reading item-4 above, I assumed that it was referring to the *interop* test plan as opposed to a *compliance* test plan. But on re-reading the whole charter I see that the first paragraph doesn't really distinguish between interop vs. conformance, but instead simply says the group will ultimately develop a conformance test plan to verify compliance with SC1.1. Here's the specific sentence...
"The goal of the SIPconnect Interoperability Certification Task Group is to develop appropriate test plans and
conformance tools to enable vendors to verify compliance with SIPconnect 1.1."
Therefore, assuming that item-4 is referring to the body of work comprising interop/conformance test plans, I think we're covered, and so I withdraw my comment.
7. define a branding program for indicating product/network compliance with SC1.1.
[RS> ] I think I covered the branding program in the last paragraph. That IMHO is going to be a separate TG where we are going to need a lot more input.
Chairman of the Board of Directors SIP Forum
PSTN Mobile: +1 703.593.2683
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SIPconnectIT