IETF Logo Mail Archive

Re: [martini] Announcement of MARTINI WG last Call on "Registration for Multiple Phone Numbers in the SIP"

Adam Roach <adam@nostrum.com> Sat, 24 July 2010 09:57 UTC

Return-Path: <adam@nostrum.com>
X-Original-To: martini@core3.amsl.com
Delivered-To: martini@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 967C93A681E for <martini@core3.amsl.com>; Sat, 24 Jul 2010 02:57:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BFNvNo1NYr2e for <martini@core3.amsl.com>; Sat, 24 Jul 2010 02:57:57 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 5E56D3A68B3 for <martini@ietf.org>; Sat, 24 Jul 2010 02:57:57 -0700 (PDT)
Received: from dhcp-23f3.meeting.ietf.org (dhcp-23f3.meeting.ietf.org [130.129.35.243]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o6O9wBG7071660 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 24 Jul 2010 04:58:12 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <4C4AB933.2080609@nostrum.com>
Date: Sat, 24 Jul 2010 11:58:11 +0200
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.7) Gecko/20100713 Thunderbird/3.1.1
MIME-Version: 1.0
To: David Hancock <D.Hancock@CableLabs.com>
References: <BLU137-W10550BA232377BE7913FFE93B30@phx.gbl> <76AC5FEF83F1E64491446437EA81A61F7CF4F16563@srvxchg>, <A444A0F8084434499206E78C106220CAECCCC458@MCHP058A.global-ad.net> <76AC5FEF83F1E64491446437EA81A61F7CF4B0488F@srvxchg> <4C48B090.3040206@nostrum.com> <76AC5FEF83F1E64491446437EA81A61F7CF4F166B4@srvxchg>
In-Reply-To: <76AC5FEF83F1E64491446437EA81A61F7CF4F166B4@srvxchg>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 130.129.35.243 is authenticated by a trusted mechanism)
Cc: Bernard Aboba <bernard_aboba@hotmail.com>, "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] Announcement of MARTINI WG last Call on "Registration for Multiple Phone Numbers in the SIP"
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of en-mass SIP PBX registration mechanisms <martini.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/martini>, <mailto:martini-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/martini>
List-Post: <mailto:martini@ietf.org>
List-Help: <mailto:martini-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/martini>, <mailto:martini-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Jul 2010 09:57:58 -0000

  On 7/23/10 10:56 PM, David Hancock wrote:
> Comments at the end...
>
>> -----Original Message-----
>> From: Adam Roach [mailto:adam@nostrum.com]
>>
>> ...
>>> If we take this approach where the SSP treats these SUBSCRIBEs like any
>> request to be delivered to the SIP-PBX, then what happens to reg-event
>> subscriptions to the SIP-PBX when the PBX transitions from registered to
>> not-registered? Would they simply expire?
>>
>> See RFC 3265, section 3.3.5 (or, for more clarity, rfc3265bis, section
>> 4.4.2).
>>
> [dch] Interesting.  Your idea being (I assume) that that this mechanism could be used to pass the reg-event subscription back and forth between the SSP network and the SIP-PBX, based on whether the PBX itself is registered or not.  I'm sensitive to your concern about not over-mandating what can be left to implementation. But I think an informative sentence or two on this would be very useful.

That seems reasonable.

/a

v2.23.0 | Report a Bug | By Email