[SIPForum-techwg] SIPconnect 1.1 timeline - strawman ..

[Jamie Palmer]

Rich,

I'm still working on the formal BroadSoft contribution/input/proposal -
I will probably need another week before I can send it over.  

I agree -- its good to see some lively discussion on the SIPForum-techwg
list :)  It's been pretty dormant for awhile.  Thanks to Russell for
sparking the  discussion.  I hope we can get to closure on CODECS and
Transports pretty quickly....I agree with Janne -- IMHO, UDP and G711
(and probably RFC2833) should be MUST.  In the real world, this is
what's happening.  Everything else should be a MAY -- and let the
service provider differentiate the offering with things like TLS or low
bit rate / wideband CODECs.

Hopefully this won't cause too much debate, but I do feel that
SIPConnect 1.1 does need to build on SIPConnect 1.0 rather than rewrite
it.  SIPConnect 1.0 was good, and I think it covered all the
requirements for basic trunking.  With a few exceptions - I hope we
don't have to revist too many of the same old topics that were already
addressed there.  

With SIPConnect 1.1, I'm hoping we can simply revise and extend
SIPConnect 1.0.  By "revise", I mean keep the majority of the SIPConnect
1.0 spec and language -- only modifying for clairity where needed.  By
"extend", I mean simply add more recommendations/guidelines to the
document to address some key real world issues we are seeing in the
field with SIPConnect 1.0. 

With that said, here's the key areas that I think we need to revise:

1) Section 11 (Enterprise Identities):  I would like to see this section
revised to cover the registration process.  

2) Section 12 (Enterprise URI Formatting and Addressing Rules):  I would
like to see this section revised to cover "incoming calls" and service
interactions related to Direct Inward Dialing.

3) Section 13 (Service Provider URI Formatting and Addressing Rules):  I
would like to see this section revised to cover "outgoing calls" and
service interfactions related to Direct Outward Dialing and Caller
ID/Calling Name.  

All the areas that I think we need to add are related to service
interactions...in our experience these are the areas that need to be
spelled out more clearly.  Specifically:

*	Voicemail Deposit (from the enterprise into the service provider
network)
*	Message Waiting Indication (from the service provider network to
the enterprise)
*	Transfer and Forwarding scenarios (from the enterprise into the
service provider network)

If we clarify sections 11, 12 and 13 and add these key service
interactions to the specification, I think it will address all the
issues we are seeing in the field today.

Regards,
Jamie




-----Original Message-----
From: techwg-bounces at sipforum.org [mailto:techwg-bounces at sipforum.org]
On Behalf Of Richard Shockey
Sent: Thursday, May 15, 2008 11:27 AM
To: 'SIP Forum Tech WG'
Subject: [SIPForum-techwg] SIPconnect 1.1 timeline - strawman ..


It's nice to see some general discussion on the list at this point but
I'd like to update folks on the possible time lines etc.

I'm assured that Broadsoft is preparing a contribution that should be
ready shortly.

The CableLabs folks are preparing a contribution based on their
requirements. Their plan is to take the existing 1.0 specification and
essentially redline it with their comments. Their plan is to have this
document ready on or before June 6.

I'm proposing that all initial contributions to the 1.1 effort be cut
off as of June 13. Our document editor can then mash up the initial
contributions into a 00 version for 1.1.

On that basis we can have refine the document during July and August
hopefully a have a viable specification by early October.

Does this look like a reasonable plan?

Again if there are any additional contributions folks may have ..please
submit them to me so that I can have them properly posted on to the
SIPforum web site. 


Richard Shockey
Director, Member of the Technical Staff
NeuStar
46000 Center Oak Plaza - Sterling, VA 20166 PSTN Office +1 571.434.5651
PSTN Mobile: +1 703.593.2683 <mailto:richard(at)shockey.us>
<mailto:richard.shockey(at)neustar.biz>



_______________________________________________
techwg mailing list
Send mail to: techwg at sipforum.org
Unsubscribe or edit options at:
http://sipforum.org/mailman/listinfo/techwg