Return-Path: X-Original-To: mmusic@ietfa.amsl.com Delivered-To: mmusic@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5336721F8716 for ; Mon, 17 Sep 2012 09:47:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.198 X-Spam-Level: X-Spam-Status: No, score=-10.198 tagged_above=-999 required=5 tests=[AWL=0.400, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id roON+hc-KGC2 for ; Mon, 17 Sep 2012 09:47:17 -0700 (PDT) Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 041C821F8714 for ; Mon, 17 Sep 2012 09:47:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=14221; q=dns/txt; s=iport; t=1347900437; x=1349110037; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=XBWyehhoFQtoRY1hK1M+o3hDY1bi7tisy5kccYDjhXg=; b=XS+bxdM3i7bDDSr7uqC/HTY6v1ZtTxIQ8XGmeL5UdBsLRUW02bpcn4S2 78p6VXkFAeZ5rxPEHm8hxdt1E44Sqv4wUZvlN4gWk0B3mS17Pnf7AqOA/ MdXVYeG4YQ5ufw///2Eh1tfBJpLYVSJ+zlrv8ABuIoKPx5Csi5amyTs0i I=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgcFAMZTV1CtJV2b/2dsb2JhbABEgkuoFYhTAYhjgQeCIAEBAQMBAQEBDwEaQQQFAgUHAgICAQgOAwQBAQEKHQcbDAsUCQgCBA4FCAEZh1gGC5pcn3MEix2GCGADlnaKBYMfgWmBLoE4ghc X-IronPort-AV: E=Sophos; i="4.80,437,1344211200"; d="scan'208,217"; a="119396244" Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-9.cisco.com with ESMTP; 17 Sep 2012 16:47:16 +0000 Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id q8HGlGG7003499 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 17 Sep 2012 16:47:16 GMT Received: from xmb-rcd-x10.cisco.com ([169.254.15.216]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.02.0318.001; Mon, 17 Sep 2012 11:47:16 -0500 From: "Tirumaleswar Reddy (tireddy)" To: Emil Ivov Thread-Topic: [MMUSIC] New Version Notification for draft-wing-mmusic-ice-mobility-01.txt Thread-Index: AQHNY6F+/LEFvCvLC0CLcDi4fxclSZcx8gqQgAAM1pCAVrIoAP//1knQ Date: Mon, 17 Sep 2012 16:47:15 +0000 Message-ID: <913383AAA69FF945B8F946018B75898A147AA88C@xmb-rcd-x10.cisco.com> References: <913383AAA69FF945B8F946018B75898A052D666F@xmb-rcd-x10.cisco.com> <5051A76A.7090606@jitsi.org> In-Reply-To: <5051A76A.7090606@jitsi.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [173.39.29.37] x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19188.004 x-tm-as-result: No--26.863400-8.000000-31 x-tm-as-user-approved-sender: No x-tm-as-user-blocked-sender: No Content-Type: multipart/alternative; boundary="_000_913383AAA69FF945B8F946018B75898A147AA88Cxmbrcdx10ciscoc_" MIME-Version: 1.0 Cc: "Prashanth Patil \(praspati\)" , "mmusic@ietf.org" , "Dan Wing \(dwing\)" Subject: Re: [MMUSIC] New Version Notification for draft-wing-mmusic-ice-mobility-01.txt X-BeenThere: mmusic@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Multiparty Multimedia Session Control Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Sep 2012 16:47:18 -0000 --_000_913383AAA69FF945B8F946018B75898A147AA88Cxmbrcdx10ciscoc_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Emil - Thanks for the comments. we are in the process of updating the draft - We are planning to add the high-lighted sentence in Introduction, please le= t us know if you have any further comments. Although ICE does allow an "ICE restart", this is done by sending a re-INVI= TE which goes over the SIP signaling path. The SIP signaling path is often = slower than the media path (which needs to be recovered as quickly as possi= ble), consumes an extra half round trip, and incurs an additional delay if = the mobility event forces the endpoint to re-connect with its SIP proxy. Wh= en a device changes its IP address, it is necessary for it to re-establish = connectivity with its SIP proxy, which can be performed in parallel with th= e steps described in this document. This document describes how mobility is= performed entirely in the media path, without the additional delay of re-e= stablishing SIP connectivity, issuing a new offer/answer, or the complicati= ons of multiple SIP offers. This document considers re-establishing bi-dire= ctional media the most critical aspect of a successful mobility event, and = its efforts are towards meeting that goal. We will also added the following text at the end of section 3.1 The Mobile device would also in parallel re-establish connection with the S= IP proxy and if the ICE connectivity checks in the previous steps are not s= uccessful then issues new offer/answer and restarts ICE. --Tiru. > -----Original Message----- > From: Emil Ivov [mailto:emcho@jitsi.org] > Sent: Thursday, September 13, 2012 2:59 PM > To: Tirumaleswar Reddy (tireddy) > Cc: mmusic@ietf.org > Subject: Re: [MMUSIC] New Version Notification for draft-wing-mmusic-ice- > mobility-01.txt > > Hey Tiru, > > One thing that I think this document is not very clear about is its > relationship to standard mobility handling (i.e. through ICE restart). > > As far as I can see, ICE restart is only mentioned when describing its > inefficiency. > > You did confirm in Vancouver that ICE Mobility is only meant as an > optimisation that would only take place until the ICE restart completes > but I don't see it anywhere in the text. Or am I missing something? > > Cheers, > Emil > > On 20.07.12, 13:36, Tirumaleswar Reddy (tireddy) wrote: > > Hi all, > > > > Dan, Prashanth and I have submitted a draft that explains how > > endpoint mobility can be achieved using ICE. Two mechanisms are > > shown, one where both endpoints support ICE and another where only > > one endpoint supports ICE. When only one endpoint supports ICE, a > > TURN server provides mobility. > > > > http://www.ietf.org/internet-drafts/draft-wing-mmusic-ice-mobility-01.t= xt > > > > Please let know your comments. If time permits we'd present the > > draft in Vancouver. > > > > Regards, Tiru. > > > >> -----Original Message----- From: Tirumaleswar Reddy (tireddy) Sent: > >> Friday, July 20, 2012 3:18 PM To: mmusic@ietf.org Subject: FW: New > >> Version Notification for draft-wing-mmusic-ice- mobility-01.txt > >> > >> -----Original Message----- From: internet-drafts@ietf.org > >> [mailto:internet-drafts@ietf.org] Sent: Tuesday, July 17, 2012 3:52 > >> AM To: Dan Wing (dwing) Cc: Prashanth Patil (praspati); > >> Tirumaleswar Reddy (tireddy) Subject: New Version Notification for > >> draft-wing-mmusic-ice-mobility- 01.txt > >> > >> > >> A new version of I-D, draft-wing-mmusic-ice-mobility-01.txt has > >> been successfully submitted by Dan Wing and posted to the IETF > >> repository. > >> > >> Filename: draft-wing-mmusic-ice-mobility Revision: 01 Title: > >> Mobility with ICE (MICE) Creation date: 2012-07-16 WG ID: > >> Individual Submission Number of pages: 12 URL: > >> http://www.ietf.org/internet-drafts/draft-wing-mmusic- > >> ice-mobility-01.txt Status: > >> http://datatracker.ietf.org/doc/draft-wing-mmusic-ice- mobility > >> Htmlized: http://tools.ietf.org/html/draft-wing-mmusic-ice- > >> mobility-01 Diff: > >> http://tools.ietf.org/rfcdiff?url2=3Ddraft-wing-mmusic- > >> ice-mobility-01 > >> > >> Abstract: This specification describes how endpoint mobility can be > >> achieved using ICE. Two mechanisms are shown, one where both > >> endpoints support ICE and another where only one endpoint supports > >> ICE. > >> > >> > >> > >> > >> The IETF Secretariat > > _______________________________________________ mmusic mailing list > > mmusic@ietf.org https://www.ietf.org/mailman/li= stinfo/mmusic > > > > -- > Emil Ivov, Ph.D. 67000 Strasbourg, > Project Lead France > Jitsi > emcho@jitsi.org PHONE: +33= .1.77.62.43.30 > http://jitsi.org FAX: +33.1.77.62.47.31 --_000_913383AAA69FF945B8F946018B75898A147AA88Cxmbrcdx10ciscoc_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Hi Emil -
 
Thanks for the comments. we are in the process of updating the draft -=
 
We are planning to add the high-lighted sentence in Introduction, plea= se let us know if you have any further comments.
 
Although ICE does allow an "ICE restart", this is done by se= nding a re-INVITE which goes over the SIP signaling path. The SIP signaling= path is often slower than the media path (which needs to be recovered as q= uickly as possible), consumes an extra half round trip, and incurs an additional delay if the mobility event forces the= endpoint to re-connect with its SIP proxy. When a device changes its IP= address, it is necessary for it to re-establish connectivity with its SIP = proxy, which can be performed in parallel with the steps described in this document. This document descr= ibes how mobility is performed entirely in the media path, without the addi= tional delay of re-establishing SIP connectivity, issuing a new offer/answe= r, or the complications of multiple SIP offers. This document considers re-establishing bi-directional media th= e most critical aspect of a successful mobility event, and its efforts are = towards meeting that goal.
 
We will also added the following text at the end of section 3.1
 
The Mobile device would also in parallel re-establish connection wi= th the SIP proxy and if the ICE connectivity checks in the previous steps a= re not successful then issues new offer/answer and restarts ICE.
 
--Tiru.
 
> -----Original Message-----
> From: Emil Ivov [mailto:emcho@= jitsi.org]
> Sent: Thursday, September 13, 2012 2:59 PM
> To: Tirumaleswar Reddy (tireddy)
> Cc: mmusic@ietf.org
> Subject: Re: [MMUSIC] New Version Notification for draft-wing-mmu= sic-ice-
> mobility-01.txt
>
> Hey Tiru,
>
> One thing that I think this document is not very clear about is i= ts
> relationship to standard mobility handling (i.e. through ICE rest= art).
>
> As far as I can see, ICE restart is only mentioned when describin= g its
> inefficiency.
>
> You did confirm in Vancouver that ICE Mobility is only meant as a= n
> optimisation that would only take place until the ICE restart com= pletes
> but I don't see it anywhere in the text. Or am I missing somethin= g?
>
> Cheers,
> Emil
>
> On 20.07.12, 13:36, Tirumaleswar Reddy (tireddy) wrote:
> > Hi all,
> >
> > Dan, Prashanth and I have submitted a draft that explains ho= w
> > endpoint mobility can be achieved using ICE.  Two mecha= nisms are
> > shown, one where both endpoints support ICE and another wher= e only
> > one endpoint supports ICE. When only one endpoint supports I= CE, a
> > TURN server provides mobility.
> >
> >
> >  Please let know your comments. If time permits we'd pr= esent the
> > draft in Vancouver.
> >
> > Regards, Tiru.
> >
> >> -----Original Message----- From: Tirumaleswar Reddy (tir= eddy) Sent:
> >> Friday, July 20, 2012 3:18 PM To: mmusic@ietf.org Subject= : FW: New
> >> Version Notification for draft-wing-mmusic-ice- mobility= -01.txt
> >>
> >> -----Original Message----- From: internet-drafts@ietf.org
> >> [mailto:internet-drafts@ietf.org] Sent:= Tuesday, July 17, 2012 3:52
> >> AM To: Dan Wing (dwing) Cc: Prashanth Patil (praspati);<= /div>
> >> Tirumaleswar Reddy (tireddy) Subject: New Version Notifi= cation for
> >> draft-wing-mmusic-ice-mobility- 01.txt
> >>
> >>
> >> A new version of I-D, draft-wing-mmusic-ice-mobility-01.= txt has
> >> been successfully submitted by Dan Wing and posted to th= e IETF
> >> repository.
> >>
> >> Filename:   draft-wing-mmusic-ice-mobility Rev= ision:         01 Title:
> >> Mobility with ICE (MICE) Creation date:   = ;  2012-07-16 WG ID:
> >> Individual Submission Number of pages: 12 URL:
> >> ice-mobility-01.txt Status:
> >> Htmlized:        http://tools.ietf.org/html/draft-wing-mmusic-ice-
> >> mobility-01 Diff:
> >> ice-mobility-01
> >>
> >> Abstract: This specification describes how endpoint mobi= lity can be
> >> achieved using ICE.  Two mechanisms are shown, one = where both
> >> endpoints support ICE and another where only one endpoin= t supports
> >> ICE.
> >>
> >>
> >>
> >>
> >> The IETF Secretariat
> > _______________________________________________ mmusic maili= ng list
> >
>
> --
> Emil Ivov, Ph.D.        &= nbsp;           &nbs= p;  67000 Strasbourg,
> Project Lead         = ;            &n= bsp;     France
> Jitsi
> emcho@= jitsi.org        &nb= sp;            =    PHONE: +33.1.77.62.43.30
> http://jitsi= .org         &n= bsp;            = ; FAX:   +33.1.77.62.47.31
 
 --_000_913383AAA69FF945B8F946018B75898A147AA88Cxmbrcdx10ciscoc_--