[SIPForum-techwg] Focus on simple PSTN?

[Hadriel Kaplan]

Hey Eric,
Comments inline...

> -----Original Message-----
> From: techwg-bounces at sipforum.org [mailto:techwg-bounces at sipforum.org] On
> Behalf Of Eric Burger
>
> Speaking as an individual:
> PLEASE take a look at Section 2.1.2 of:
> http://www.ietf.org/internet-drafts/draft-iab-protocol-success-03.txt
>
> We don't want to take any steps backward.  For example, we don't want
> to do the 3GPP thing of making protocol "profiles" that make it hard
> or impossible to interoperate with non-walled-garden SIP devices.

I am not sure what you mean by that.  Do you mean you don't think we should create profiles?  Or that the profiles we create shouldn't require things which are not already commonly used?  Or that the profiles we create shouldn't restrict us to a specific set of behaviors?


> However, we do want people to be able to easily adopt the profile.
> Part of that is some level of backward compatibility and ease of
> deployment.  Do note that there is a limit of backward compatibility.
> For example, if many devices out there support TCP, and most of the
> typical devices found at the enterprise support TCP or are easily
> upgradable to support TCP, then I would see no problem of mandating
> TCP.  We don't need to support 10-year-old (or 10-year-old mindset)
> UDP-only, RFC 2543 devices.  <just my vote>

I agree we shouldn't need to support RFC2543 devices.  That is an orthogonal issue with supporting UDP, imo.

I think there is a distinction between what a vendor needs to support to be able to claim compliance, and what a service provider or Enterprise has to support/enable to claim compliance.  Those are very different beasts.

In terms of creating PICS Proforma compliance checklists, the value for a SIP-Connect spec is different for those two meanings.  For the vendor support case, the value is that an Enterprise or Service Provider can know what they're buying/deploying can be used for SIP Trunking services of this type.  I think we're all on that page.  I don't think there is much debate that any vendor claiming compliance to SIP-Connect must support TCP. (at least the vendors at the SSP-Enterprise transport connection points)  They must also support UDP.  Otherwise they will severely limit their usefulness to the people buying them.

-hadriel