[SIPForum-techwg] Avaya Contribution for SIPconnect 1.1

[Richard Shockey]

Thank you Adam for a reality check... your note goes to my general concerns
about IMPLEMENTABLE specification.

No one wants to artificially restrict the scope of 1.1. I'll admit that the
scope of this work was made deliberately ambiguous since we had heard
concerns about 1.0 for some time but it was unclear as to what specifically
needed to be fixed. 

My early point, echoed here by Adam, at adding MUST here and there has
unintended consequences for service providers wanting to go to market.

-----Original Message-----
From: techwg-bounces at sipforum.org [mailto:techwg-bounces at sipforum.org] On
Behalf Of Uzelac, Adam
Sent: Tuesday, June 10, 2008 9:44 AM
To: techwg at sipforum.org
Subject: Re: [SIPForum-techwg] Avaya Contribution for SIPconnect 1.1

Some thoughts from one SP here...

> > [JRE] This just highlights the fact that we need to be clear on the 
> > scope of 1.1 - is it just for PSTN access (as 1.0 appears 
> to be) or is 
> > it indeed for SIP-SIP cases too? In the latter case end-to-end 
> > transparency of SDP, different media, etc. becomes a lot more 
> > important.
> > 

I completely agree with Mr. Elwell with regards to the ambiguous nature
of the scope of 1.1.  The abstract of 1.0 states clearly the following:
"This document outlines an interface specification that enables direct
IP Peering between a SIP-enabled Service Provider network and a
SIP-enabled Enterprise Network for the purpose of originating and/or
terminating calls from the PSTN."

With that in mind, there are SIP-enabled SPs that have hundreds of
gateways deployed throughout the world for PSTN access, and though
code/hardware to support SRTP/TLS/etc may be available, upgrading an
infrastructure of that size is a 12+ month exercise (at a minimum) that
also involves significant CAPEX.  Forcing the issue sometimes (more
often than not) has unintended consequences - for instance B2BUAs that
are built to transcode, mediate, etc.  It's a fact of the industry more
than an endorsement.

Adam


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