Re: [martini] #59: Reg-Event Issues
"martini issue tracker" <trac@tools.ietf.org> Wed, 22 September 2010 23:01 UTC
Return-Path: <trac@tools.ietf.org>
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 49A123A67A3 for <martini@core3.amsl.com>; Wed, 22 Sep 2010 16:01:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.571
X-Spam-Level:
X-Spam-Status: No, score=-102.571 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 a1q6Fb0OxVrt for <martini@core3.amsl.com>; Wed, 22 Sep 2010 16:01:30 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 62AC23A6804 for <martini@ietf.org>; Wed, 22 Sep 2010 16:01:30 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OyYK6-00046w-1R; Wed, 22 Sep 2010 16:01:58 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: martini issue tracker <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: adam@nostrum.com
X-Trac-Project: martini
Date: Wed, 22 Sep 2010 23:01:58 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/59#comment:1
Message-ID: <074.04a0e2389127cb8bb8d4da832a06a2d1@tools.ietf.org>
References: <065.89830ac389df38a6864ddc9101774de2@tools.ietf.org>
X-Trac-Ticket-ID: 59
In-Reply-To: <065.89830ac389df38a6864ddc9101774de2@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: adam@nostrum.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: Re: [martini] #59: Reg-Event Issues
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
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: Wed, 22 Sep 2010 23:01:31 -0000
#59: Reg-Event Issues
-------------------------------------+--------------------------------------
Reporter: D.Hancock@… | Owner: adam@…
Type: defect | Status: closed
Priority: major | Milestone: milestone1
Component: gin | Version: 1.0
Severity: In WG Last Call | Resolution: fixed
Keywords: |
-------------------------------------+--------------------------------------
Changes (by adam@…):
* status: new => closed
* resolution: => fixed
Comment:
Issue 1 -- Good catch. Added:
If the SIP-PBX is not registered with the
SSP when a registration event subscription for a contact
that would be implicitly registered if the SIP-PBX were
registered, the the SSP SHOULD accept the subscription
and indicate that the user is not currently registered.
Once the associated SIP-PBX is registered, the SSP
SHOULD use the subcription migration mechanism defined
in RFC 3265 to migrate the subscription to the SIP-PBX.
Issue 2 -- This is out of scope for GIN or even MARTINI. The answer is
completely identical to the answer that would be given without GIN or any
MARTINI-associated mechanism.
Issue 3 -- This is a shortcoming in RFC 3680, as we are defining both
state agents and rational reasons to fork subscriptions. In fact, 3680
doesn't prohibit '''forking''' of the subscriptions -- it prevents
subscribers from establishing multiple dialogs. So I think that continuing
to fork (whether to the SSP and to the SIP-PBX or to multiple SIP-PBXes
with the same implicitly registered contact) is very much the Right Thing
To Do [tm]. What I think we need to do is allow subscribers who understand
the GIN architecture to accept multiple subscriptions if they wish to do
so. Updating the document accordingly.
--
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/59#comment:1>
martini <http://tools.ietf.org/martini/>
- [martini] #59: Reg-Event Issues martini issue tracker
- Re: [martini] #59: Reg-Event Issues martini issue tracker