Re: [Sip] question on refresh request to trigger full state notification

Dale.Worley@comcast.net Thu, 24 January 2008 02:11 UTC

Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHrZA-0004sU-FE; Wed, 23 Jan 2008 21:11:44 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1JHrZ8-0004sI-Bs for sip-confirm+ok@megatron.ietf.org; Wed, 23 Jan 2008 21:11:42 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHrZ8-0004s4-1B for sip@ietf.org; Wed, 23 Jan 2008 21:11:42 -0500
Received: from qmta01.westchester.pa.mail.comcast.net ([76.96.62.16]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JHrZ7-0002ir-JQ for sip@ietf.org; Wed, 23 Jan 2008 21:11:41 -0500
Received: from OMTA04.westchester.pa.mail.comcast.net ([76.96.62.35]) by QMTA01.westchester.pa.mail.comcast.net with comcast id gooW1Y0040ldTLk0506w00; Thu, 24 Jan 2008 02:11:41 +0000
Received: from dragon.ariadne.com ([24.34.79.42]) by OMTA04.westchester.pa.mail.comcast.net with comcast id gqBg1Y0070umElk3Q00000; Thu, 24 Jan 2008 02:11:41 +0000
X-Authority-Analysis: v=1.0 c=1 a=3H2CTWD0nD0A:10 a=eALAE6kVaKMtgLHhJ4IA:9 a=u6BMvaB65fM_PXBX6mcA:7 a=qbUOUZeun23_AF4s8Bo44_5syH8A:4 a=JfD0Fch1gWkA:10 a=8y7tGHue6YMA:10
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1]) by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id m0O2Be07027383 for <sip@ietf.org>; Wed, 23 Jan 2008 21:11:40 -0500
Received: (from worley@localhost) by dragon.ariadne.com (8.12.8/8.12.8/Submit) id m0O2BeHt027379; Wed, 23 Jan 2008 21:11:40 -0500
Date: Wed, 23 Jan 2008 21:11:40 -0500
Message-Id: <200801240211.m0O2BeHt027379@dragon.ariadne.com>
To: sip@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <378E78E5F361564BB066432F6415764B05218ED5@xmb-sjc-228.amer.cisco.com> (ramsubra@cisco.com)
Subject: Re: [Sip] question on refresh request to trigger full state notification
References: <378E78E5F361564BB066432F6415764B05218ED5@xmb-sjc-228.amer.cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org

   From: "Ramamoorthy Subramanian (ramsubra)" <ramsubra@cisco.com>

   We're implementing RFC4662 and wondering how to trigger full state
   notification. The spec says as follows.

   "Immediate notifications triggered as a result of subsequent SUBSCRIBE
   messages SHOULD include an RLMI document in which the full state is
   indicated.  The RLS SHOULD also include state information for all
   resources in the list for which the RLS has state, subject to policy
   restrictions.  This allows the subscriber to refresh their state, and
   to recover from lost notifications."

   [...] [Does] this means that the subscribe[r] should send another
   subscribe request (resubscribe) to get the full-state notification?

Yes.

Dale


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