[Sipping] SIP Handover and 3GPP Multimedia Session Continuity?
"Saverio Niccolini" <Saverio.Niccolini@nw.neclab.eu> Mon, 08 October 2007 13:17 UTC
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IesUd-0000eq-Fn; Mon, 08 Oct 2007 09:17:55 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43) id 1Iep1E-0006Tl-Tl for sipping-confirm+ok@megatron.ietf.org; Mon, 08 Oct 2007 05:35:20 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43) id 1Iep1E-0006N3-Cx for sipping@ietf.org; Mon, 08 Oct 2007 05:35:20 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IeozH-0006uE-Hc for sipping@ietf.org; Mon, 08 Oct 2007 05:33:19 -0400
Received: from smtp0.netlab.nec.de ([195.37.70.40]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IeozG-000824-VY for sipping@ietf.org; Mon, 08 Oct 2007 05:33:19 -0400
Received: from localhost (atlas1.office [127.0.0.1]) by smtp0.netlab.nec.de (Postfix) with ESMTP id 34E13280037E2; Mon, 8 Oct 2007 11:33:18 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office)
Received: from smtp0.netlab.nec.de ([127.0.0.1]) by localhost (atlas1.office [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1+Lfwyu82EPz; Mon, 8 Oct 2007 11:33:18 +0200 (CEST)
Received: from mx1.office (mx1.office [10.1.1.23]) by smtp0.netlab.nec.de (Postfix) with ESMTP id 1E3EE28000472; Mon, 8 Oct 2007 11:33:03 +0200 (CEST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 08 Oct 2007 11:32:57 +0200
Message-ID: <5F6519BF2DE0404D99B7C75607FF76FF1B1749@mx1.office>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: SIP Handover and 3GPP Multimedia Session Continuity?
Thread-Index: AcgJjjW8jeqmgkGURlK2Dd5jetxjDQ==
From: Saverio Niccolini <Saverio.Niccolini@nw.neclab.eu>
To: SIPPING LIST <sipping@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
X-TMDA-Confirmed: Mon, 08 Oct 2007 05:35:20 -0400
X-Mailman-Approved-At: Mon, 08 Oct 2007 09:17:54 -0400
Cc: Bernd Lamparter <Bernd.Lamparter@nw.neclab.eu>, Stefan Schmid <Stefan.Schmid@nw.neclab.eu>, luca.veltri@unipr.it, Andreas Kunz <Andreas.Kunz@nw.neclab.eu>
Subject: [Sipping] SIP Handover and 3GPP Multimedia Session Continuity?
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org
Dear SIPPING group, we recently submitted an update of the drafts: -- "Requirements for vertical handover of multimedia sessions using SIP" http://tools.ietf.org/html/draft-niccolini-sipping-siphandover -- "A solution for vertical handover of multimedia sessions using SIP" http://tools.ietf.org/html/draft-salsano-sipping-siphandover-solution We received some comments after submitting the last version but discussion on the mailing list was not enough to justify asking for a slot at the meeting. Why we would really like to discuss this in SIPPING? -1- we believe this solution to be ready and performing better than available ones in addressing the requirements listed -2- 3GPP started looking into the issue (refer to Multimedia Session Continuity) and if they require protocol work then IETF should have a look into that Our draft present a solution we already implemented and tested solving a real problem of a roaming mobile host equipped with multiple interfaces (what is referred to as Multimedia Session Continuity, MMSC, in 3GPP). We propose to extend the mobility support in SIP using an intermediate anchoring element (the same solution envisioned by 3GPP). For doing this we have identified extension required to the SIP signaling consisting in: -- an additional header to carry handover related information -- an additional tag to help in the identification of users at intermediate elements I would like to comment together with you on this draft, if the look is looking for intersting new WG item we really think this is something to have a look at. Thanks in advance for your comments, Saverio ============================================================ Dr. Saverio Niccolini Senior Research Staff Member NEC Europe Ltd., NEC Laboratories Europe, Network Division Kurfuerstenanlage 36, D-69115 Heidelberg Tel. +49 (0)6221 4342-118 Fax: +49 (0)6221 4342-155 e-mail: saverio.niccolini@nw.neclab.eu <-- !!! NEW ADDRESS !!! ============================================================ NEC Europe Limited Registered Office: NEC House, 1 Victoria Road, London W3 6BL Registered in England 2832014 _______________________________________________ Sipping mailing list https://www1.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] SIP Handover and 3GPP Multimedia Sessio… Saverio Niccolini
- Re: [Sipping] SIP Handover and 3GPP Multimedia Se… Paul Kyzivat
- Re: [Sipping] SIP Handover and 3GPP Multimedia Se… Stefano Salsano