[Sip] Extension mobility in SIP
"Anisha Kumar" <anisha.kumar@nestgroup.net> Thu, 31 January 2008 04:32 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 1JKR61-00048h-VQ; Wed, 30 Jan 2008 23:32:17 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1JKR61-00048Y-1P for sip-confirm+ok@megatron.ietf.org; Wed, 30 Jan 2008 23:32:17 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JKR60-00048Q-LV for sip@ietf.org; Wed, 30 Jan 2008 23:32:16 -0500
Received: from nestgroup.net ([203.200.157.75] helo=mx-01.nestgroup.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JKR5w-0002XX-4B for sip@ietf.org; Wed, 30 Jan 2008 23:32:16 -0500
Received: from MAIL-TVM.tvm.nestgroup.net ([192.168.192.74]) by mx-01.nestgroup.net (8.13.1/8.13.1) with ESMTP id m0V4bO4s032671 for <sip@ietf.org>; Thu, 31 Jan 2008 10:09:42 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 31 Jan 2008 10:00:29 +0530
Message-ID: <9A1299C7A40D7447A108107E951450CA05ACF56E@MAIL-TVM.tvm.nestgroup.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Extension mobility in SIP
Thread-Index: AchjwgIqke7WRnoZRqOX7UhW6r/qoA==
From: Anisha Kumar <anisha.kumar@nestgroup.net>
To: sip@ietf.org
X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE autolearn=failed version=3.0.4
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on MX-01
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Subject: [Sip] Extension mobility in SIP
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="===============0410490703=="
Errors-To: sip-bounces@ietf.org
Hi , Is there a separate RFC for the implementation of extension mobility in SIP Uas ? If not, is it possible to achieve that ? Please provide your valuable suggestions and feedbacks. Thanks & Regards, Anisha
_______________________________________________ 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
- Re: [Sip] Extension mobility in SIP Dean Willis
- Re: [Sip] Extension mobility in SIP James M. Polk
- [Sip] Extension mobility in SIP Anisha Kumar
- RE: [Sip] Extension mobility in SIP Anisha Kumar
- Re: [Sip] Extension mobility in SIP Paul Kyzivat
- RE: [Sip] Extension mobility in SIP Steve Langstaff
- Re: [Sip] Extension mobility in SIP Paul Kyzivat