[SIPForum-techwg] SIPconnect/1.1 v03 onlist - section 7 supportfor registration

[Brian Lindsay]

Hi,
 
   However, there may be network equipment that is designed/used
exclusively to support the large PBX market and a pure peering/trunking
model. Is it not reasonable to meet all the requirements to support that
market segment and be SIP Connect 1.1 "compliant"?
 
   A Service Provider can of course choose to deploy whatever equipment
they require to support their target market: Products that support both
modes or a combination of equipment if they need both the "static" /
"dynamic" models, or equipment that just supports one mode if that is
all they require.
 
  Regards
      Brian


________________________________

	From: techwg-bounces at sipforum.org
[mailto:techwg-bounces at sipforum.org] On Behalf Of Johnston, Alan B
(Alan)
	Sent: Thursday, February 05, 2009 6:31 PM
	To: Spencer Dawkins; Chris Gatch; techwg at sipforum.org
	Subject: Re: [SIPForum-techwg] SIPconnect/1.1 v03 onlist -
section 7 supportfor registration
	
	

	Normally, for interop, the server MUST support both and the
clients MUST support one.  In this case, I'd say the Service Provider
MUST support both methods, and the PBX MUST support static and SHOULD
support registration (or even better Theo's new proposal) if they
support dynamic IP addresses without DNS.

	 

	Thanks,
	Alan

	 

	
________________________________


	From: techwg-bounces at sipforum.org
[mailto:techwg-bounces at sipforum.org] On Behalf Of Spencer Dawkins
	Sent: Thursday, February 05, 2009 5:15 PM
	To: Chris Gatch; techwg at sipforum.org
	Subject: Re: [SIPForum-techwg] SIPconnect/1.1 v03 onlist -
section 7 supportfor registration

	 

	OK, is this what we're saying?

	 

	SIP-PBXes MUST support both Registration and Static Modes.
SP-SSEs MUST support Static mode.

	 

	SP-SSEs providing service to SIP-PBXes that use dynamic IP
addresses SHOULD support Registration mode.

	 

	Thanks,

	 

	Spencer

		----- Original Message ----- 

		From: Chris Gatch <mailto:Chris.Gatch at cbeyond.net>  

		To: Spencer Dawkins <mailto:spencer at wonderhamster.org>
; techwg at sipforum.org 

		Sent: Wednesday, February 04, 2009 2:31 PM

		Subject: RE: [SIPForum-techwg] SIPconnect/1.1 v03 onlist
- section 7 support for registration

		 

		I like the idea of saying that the PBX MUST support both
operating modes, and the Service Provider MUST support at least one
method, preferably both.  We can then provide guidance that says
Registration mode is recommended when the PBX has a dynamic IP and
static is recommended otherwise.  

		 

		I reach this idea because it is probably not practical
to require all SPs to support static mode b/c the administrative
overhead of collecting and provisioning data about customer device IP
addresses would be operationally prohibitive at scale.  At the same
time, it's not necessary to force them to support registration mode
either.  This wouldn't make sense for a service providers targeting
large enterprises in environments where the value of registration is
minimal.  

		 

		The negative with this approach is there are undoubtedly
a few very large PBXs about which the manufacturer could argue
registration is unnecessary overhead b/c their customers won't use that
mode.  I can understand this point of view, but I'm left with the
reality that something must be required of both PBX and SP SSE to have
interoperability.  The brings me right back to needing support for BOTH
methods on the PBX to achieve interoperability in the broad sense.

		 

		Finally, I think a survey of the PBX space would find a
large majority of all SIP capable PBXs already support both modes.

		 

		Chris

		 

		 

		 

		 

		From: techwg-bounces at sipforum.org
[mailto:techwg-bounces at sipforum.org] On Behalf Of Spencer Dawkins
		Sent: Wednesday, February 04, 2009 10:28 AM
		To: techwg at sipforum.org
		Subject: [SIPForum-techwg] SIPconnect/1.1 v03 onlist -
section 7 support for registration

		 

		(Just a word of administrivia - we had some topics at
last Friday's telechat that we said needed to be discussed onlist - I'll
be posting a few of these today)

		 

		Current text in Section 7 says:

		 

		The required support for each mode is shown in Table 1.

		 

Mode

Registration

Static

SIP-PBX

MUST support

MAY support

SP-SSE

MUST support

MUST support

		Table 1: Required Support for SIPconnect/1.1 Modes

		 

		Spencer: Alan has challenged Registration at MUST level
for all SIP-PBXes, regardless of size. His concern makes sense to me.
Comments? Need to discuss onlist (did not come to consensus on telechat)
on next telechat.

		 

		Obviously, we didn't come to agreement on last Friday's
telechat, and we've been discussing onlist, but I wanted to put the
discussions in terms of the current text.

		 

		From the editor's perspective, what's in question is the
MUST for the SIP-PBX to support Registration mode. Our choices are MUST,
SHOULD (probably with an escape hatch based on size), and MAY.

		 

		What should Table 1 say in this cell?
		
		Thanks,

		 

		SPencer

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://sipforum.org/pipermail/techwg/attachments/20090205/191ac9da/attachment-0001.html