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

Michael Procter <michael@voip.co.uk> Wed, 19 August 2009 13:47 UTC

Return-Path: <michael@voip.co.uk>
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 7C1C73A6F88 for <sipcore@core3.amsl.com>; Wed, 19 Aug 2009 06:47:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 BVqYKmppRyAh for <sipcore@core3.amsl.com>; Wed, 19 Aug 2009 06:47:55 -0700 (PDT)
Received: from na3sys009aog112.obsmtp.com (na3sys009aog112.obsmtp.com [74.125.149.207]) by core3.amsl.com (Postfix) with SMTP id 3A9BF3A6EA4 for <sipcore@ietf.org>; Wed, 19 Aug 2009 06:47:55 -0700 (PDT)
Received: from source ([209.85.219.214]) by na3sys009aob112.postini.com ([74.125.148.12]) with SMTP ID DSNKSowCiGI/bcxtF/biQoPQVKwp+f9YpYCz@postini.com; Wed, 19 Aug 2009 06:48:01 PDT
Received: by ewy10 with SMTP id 10so6921926ewy.13 for <sipcore@ietf.org>; Wed, 19 Aug 2009 06:47:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.87.12 with SMTP id x12mr1584787wee.48.1250689671479; Wed, 19 Aug 2009 06:47:51 -0700 (PDT)
In-Reply-To: <4A8B0001.8000909@nostrum.com>
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>
Date: Wed, 19 Aug 2009 14:47:51 +0100
Message-ID: <a2ef85430908190647x6f43307at262088cb77108220@mail.gmail.com>
From: Michael Procter <michael@voip.co.uk>
To: Adam Roach <adam@nostrum.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
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 13:47:56 -0000

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)?

Michael