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

"Elwell, John" <john.elwell@siemens-enterprise.com> Thu, 22 July 2010 07:26 UTC

Return-Path: <john.elwell@siemens-enterprise.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 BD4683A67B4 for <martini@core3.amsl.com>; Thu, 22 Jul 2010 00:26:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.063
X-Spam-Level:
X-Spam-Status: No, score=-3.063 tagged_above=-999 required=5 tests=[AWL=-0.464, BAYES_00=-2.599]
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 8bTddco8GLg8 for <martini@core3.amsl.com>; Thu, 22 Jul 2010 00:26:56 -0700 (PDT)
Received: from ms04.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 963133A63C9 for <martini@ietf.org>; Thu, 22 Jul 2010 00:26:56 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms04.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-932073; Thu, 22 Jul 2010 09:27:12 +0200
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx (Server) with ESMTP id D457B1EB82AB; Thu, 22 Jul 2010 09:27:12 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Thu, 22 Jul 2010 09:27:12 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: David Hancock <D.Hancock@CableLabs.com>, Bernard Aboba <bernard_aboba@hotmail.com>, "martini@ietf.org" <martini@ietf.org>
Date: Thu, 22 Jul 2010 09:27:10 +0200
Thread-Topic: [martini] Announcement of MARTINI WG last Call on "Registration for Multiple Phone Numbers in the SIP"
Thread-Index: AcsdmTvs9jjiZbQhTMWrM4rctI3xzwLi6oVgABKABLA=
Message-ID: <A444A0F8084434499206E78C106220CAECCCC458@MCHP058A.global-ad.net>
References: <BLU137-W10550BA232377BE7913FFE93B30@phx.gbl> <76AC5FEF83F1E64491446437EA81A61F7CF4F16563@srvxchg>
In-Reply-To: <76AC5FEF83F1E64491446437EA81A61F7CF4F16563@srvxchg>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Thu, 22 Jul 2010 07:26:57 -0000

 

> -----Original Message-----
> From: martini-bounces@ietf.org 
> [mailto:martini-bounces@ietf.org] On Behalf Of David Hancock
> Sent: 22 July 2010 00:51
> To: Bernard Aboba; martini@ietf.org
> Subject: Re: [martini] Announcement of MARTINI WG last Call 
> on "Registration for Multiple Phone Numbers in the SIP"
> 
> I've reviewed the document and think it is ready for 
> consideration, pending resolution of the issues described below.
> 
> These issues all have to do with subscribing to reg-event.
> 
> --------------------------------------------------------------
> Issue-1:
> Section 7.7.2 says...
>    If the SSP receives a SUBSCRIBE request for the registration event
>    package with a Request-URI that indicates a contact registered via
>    the "Bulk Number Contact" mechanism defined in this document, then
>    the SSP MUST proxy that SUBSCRIBE to the SIP-PBX in the 
> same way that
>    is would proxy an INVITE bound for that AOR, unless the SSP has and
>    can maintain a copy of complete, accurate, and up-to-date 
> information
>    from the SIP-PBX (e.g., through an active back-end subscription).
> 
> How does the SSP handle the SUBSCRIBE to reg-event for an 
> enterprise user when the SIP-PBX isn't registered? My 
> understanding of RFC3680 is that if the target user of a 
> reg-event SUBSCRIBE isn't registered, then the reg-event 
> subscriber receives a NOTIFY indicating "user not 
> registered". The subscribe dialog remains active, and if/when 
> the target user subsequently registers, the reg-event 
> subscriber receives another NOTIFY containing the 
> registration data. Would this same process be followed when 
> the reg-event subscription is to an AOR owned by the SIP-PBX, 
> and if yes, how does the SSP make that happen?
[JRE] Wouldn't the SSP return a 480 response to the SUBSCRIBE request if it can't deliver it?

John