[Sip] question on refresh request to trigger full state notification
"Ramamoorthy Subramanian (ramsubra)" <ramsubra@cisco.com> Thu, 24 January 2008 00:48 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 1JHqH4-00037y-Pu; Wed, 23 Jan 2008 19:48:58 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1JHqH3-00037o-QV for sip-confirm+ok@megatron.ietf.org; Wed, 23 Jan 2008 19:48:57 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHqH3-00036m-F3 for sip@ietf.org; Wed, 23 Jan 2008 19:48:57 -0500
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JHqH2-0005Lz-Pj for sip@ietf.org; Wed, 23 Jan 2008 19:48:57 -0500
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-1.cisco.com with ESMTP; 23 Jan 2008 16:48:56 -0800
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m0O0muOH013242 for <sip@ietf.org>; Wed, 23 Jan 2008 16:48:56 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id m0O0mtJ7008199 for <sip@ietf.org>; Thu, 24 Jan 2008 00:48:56 GMT
Received: from xmb-sjc-228.amer.cisco.com ([128.107.191.125]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 23 Jan 2008 16:48:52 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 23 Jan 2008 16:48:09 -0800
Message-ID: <378E78E5F361564BB066432F6415764B05218ED5@xmb-sjc-228.amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: question on refresh request to trigger full state notification
thread-index: AcheIsnxLGDXVMJRT9GBqdD5Q44yPQ==
From: "Ramamoorthy Subramanian (ramsubra)" <ramsubra@cisco.com>
To: sip@ietf.org
X-OriginalArrivalTime: 24 Jan 2008 00:48:52.0555 (UTC) FILETIME=[E3E761B0:01C85E22]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3617; t=1201135736; x=1201999736; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=ramsubra@cisco.com; z=From:=20=22Ramamoorthy=20Subramanian=20(ramsubra)=22=20<ra msubra@cisco.com> |Subject:=20question=20on=20refresh=20request=20to=20trigge r=20full=20state=20notification |Sender:=20; bh=+BqAwlM3216OCq8YbPn6pDtg7tCuoR3YbFbEwqZqRDI=; b=OIsBGkWI5k9q0HGgSi6SV3xJFHqr8d0vv/i11x2TTZijaKExBkWNSeHLJ5 boJRV9izP3F8bXcHJceE97vIdnnyCtaN+r69itF10F+rIKlJhzGHYr1UEBpQ DZf1ZEPcgl;
Authentication-Results: sj-dkim-3; header.From=ramsubra@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; );
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc:
Subject: [Sip] question on refresh request to trigger full state notification
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>
Content-Type: multipart/mixed; boundary="===============0781331383=="
Errors-To: sip-bounces@ietf.org
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." This is not clear to me. Does this mean the subscriber needs to send a refresh request by including RLMI doc? I guess, not. According to RFC3265, I think, you cant do this. If this means that the subscribe should send another subscribe request (resubscribe) to get the full-state notification? What am I missing here? Is there a simple way to request a full-state notification by subscriber? Thanks, -rama
_______________________________________________ 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
- [Sip] question on refresh request to trigger full… Ramamoorthy Subramanian (ramsubra)
- Re: [Sip] question on refresh request to trigger … Dale.Worley