IETF Logo Mail Archive

Re: [sipcore] 3265bis Open Issue: Timer N and Resubscribes

Adam Roach <adam@nostrum.com> Wed, 19 August 2009 14:32 UTC

Return-Path: <adam@nostrum.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DD19F3A6A82 for <sipcore@core3.amsl.com>; Wed, 19 Aug 2009 07:32:32 -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 FOjh-9Fy2BtC for <sipcore@core3.amsl.com>; Wed, 19 Aug 2009 07:32:32 -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 C5BE43A6908 for <sipcore@ietf.org>; Wed, 19 Aug 2009 07:32:31 -0700 (PDT)
Received: from hydra-3.local (ppp-70-249-149-101.dsl.rcsntx.swbell.net [70.249.149.101]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id n7JEWSa1063033 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 19 Aug 2009 09:32:33 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <4A8C0CFC.8090102@nostrum.com>
Date: Wed, 19 Aug 2009 09:32:28 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605)
MIME-Version: 1.0
To: Michael Procter <michael@voip.co.uk>
References: <4A85CECC.3020401@nostrum.com> <XFE-SJC-211K9VPRfLC0000816a@xfe-sjc-211.amer.cisco.com> <4A8AD5F7.9080608@nostrum.com> <XFE-SJC-212JXrRjbDt00000377@xfe-sjc-212.amer.cisco.com> <4A8B0001.8000909@nostrum.com> <a2ef85430908190647x6f43307at262088cb77108220@mail.gmail.com>
In-Reply-To: <a2ef85430908190647x6f43307at262088cb77108220@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 70.249.149.101 is authenticated by a trusted mechanism)
Cc: SIPCORE <sipcore@ietf.org>
Subject: Re: [sipcore] 3265bis Open Issue: Timer N and Resubscribes
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Aug 2009 14:32:32 -0000

Michael Procter wrote:
> 2009/8/18 Adam Roach <adam@nostrum.com>:
>   
>> Keep in mind that the scenario I described was an attempt to find a
>> plausible set of circumstances in which the SUBSCRIBE 200 would reliably
>> arrive at a subscriber, but in which the NOTIFY would consistently fail to
>> do so. And, in this case, I would argue that the proper behavior is to drop
>> the subscription (since it's never going to recover).
>>
>> Unless we can come up with some other plausible scenario that leads us to a
>> different conclusion, I would think this is the correct answer in general.
>>     
>
> Doesn't this lead to an unfortunate interaction with
> draft-ietf-sipcore-subnot-etags-02, in particular section 6.3
> (Suppressing NOTIFY Requests)?
>
>   

We should definitely include text that indicates that the subscriber 
doesn't run Timer N when it doesn't expect a NOTIFY -- such as when they 
receive a 204 response to an in-dialog SUBSCRIBE.

/a

v2.23.0 | Report a Bug | By Email