Re: [Sipping] draft-ietf-sipping-service-examples-15.txt: clarification

Alan Johnston <alan@sipstation.com> Tue, 07 October 2008 19:28 UTC

Return-Path: <sipping-bounces@ietf.org>
X-Original-To: sipping-archive@optimus.ietf.org
Delivered-To: ietfarch-sipping-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4AC3C3A69EB; Tue, 7 Oct 2008 12:28:50 -0700 (PDT)
X-Original-To: sipping@core3.amsl.com
Delivered-To: sipping@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BE1BE3A6A2C for <sipping@core3.amsl.com>; Tue, 7 Oct 2008 12:28:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 7FFfjKMFY+wh for <sipping@core3.amsl.com>; Tue, 7 Oct 2008 12:28:47 -0700 (PDT)
Received: from mho-02-bos.mailhop.org (mho-02-bos.mailhop.org [63.208.196.179]) by core3.amsl.com (Postfix) with ESMTP id C5B8B3A6924 for <sipping@ietf.org>; Tue, 7 Oct 2008 12:28:47 -0700 (PDT)
Received: from 71-81-68-141.dhcp.stls.mo.charter.com ([71.81.68.141] helo=alan-johnstons-powerbook-g4-17.local) by mho-02-bos.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from <alan@sipstation.com>) id 1KnIDu-000LJu-QY; Tue, 07 Oct 2008 19:27:59 +0000
X-Mail-Handler: MailHop Outbound by DynDNS
X-Originating-IP: 71.81.68.141
X-Report-Abuse-To: abuse@dyndns.com (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX18VRH8zlAAk/ik1VqYjJbhLmUPyLp0tFmI=
Message-ID: <48EBB83D.6090307@sipstation.com>
Date: Tue, 07 Oct 2008 14:27:57 -0500
From: Alan Johnston <alan@sipstation.com>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: franz.edler@inode.at
References: <9AE39E8302D649D59E8E865B353F9C41@notebook>
In-Reply-To: <9AE39E8302D649D59E8E865B353F9C41@notebook>
Cc: sipping@ietf.org
Subject: Re: [Sipping] draft-ietf-sipping-service-examples-15.txt: clarification
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/sipping>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org

Franz,

The text in RFC 4235 relating to specific dialogs applies when a filter 
or event package parameters are used to specify a particular dialog in 
the SUBSCRIBE.  In this case, that is not true - Alice has no 
information about the dialog that Bob is currently in and hence could 
not specify it in F4.

As a result the explicit termination is needed.

Thanks,
Alan


Franz Edler wrote:
> Hi all,
>
> when looking at the flows in draft-ietf-sipping-service-examples-15.txt I
> found an inconstancy in "2.17 Automatic Redial" - at least from my view.
>
> My finding:
> The explicit termination of the subscription by Alice in the end is
> unnecessary because RFC 4235 states in 3.4:
> ... when a subscriber is interested in the state of a specific dialog or
> dialogs (...). In that case, when the dialogs terminate, so too does the
> subscription.
>
> Therefore the explicit termination of the subscription is superfluous.
> What do you think?
>
> Regards
> Franz 
>
> _______________________________________________
> Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
>
>
>   

_______________________________________________
Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP