Re: [multimob] WG Adoption call ondraft-schmidt-multimob-pmipv6-mcast-deployment-04

<Dirk.von-Hugo@telekom.de> Tue, 23 February 2010 08:27 UTC

Return-Path: <Dirk.von-Hugo@telekom.de>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 844DC3A8360 for <multimob@core3.amsl.com>; Tue, 23 Feb 2010 00:27:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level:
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yH+ymWWRaEMY for <multimob@core3.amsl.com>; Tue, 23 Feb 2010 00:27:26 -0800 (PST)
Received: from tcmail33.telekom.de (tcmail33.telekom.de [194.25.30.7]) by core3.amsl.com (Postfix) with ESMTP id 0A6363A7D94 for <multimob@ietf.org>; Tue, 23 Feb 2010 00:27:25 -0800 (PST)
Received: from s4de8psaanq.blf.telekom.de (HELO S4DE8PSAANQ.mitte.t-com.de) ([10.151.180.166]) by tcmail31.telekom.de with ESMTP; 23 Feb 2010 09:29:21 +0100
Received: from S4DE8PSAAQC.mitte.t-com.de ([10.151.229.14]) by S4DE8PSAANQ.mitte.t-com.de with Microsoft SMTPSVC(6.0.3790.3959); Tue, 23 Feb 2010 09:29:22 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 23 Feb 2010 09:29:21 +0100
Message-ID: <643B0A1D1A13AB498304E0BBC802784801E4F055@S4DE8PSAAQC.mitte.t-com.de>
In-Reply-To: <865604.51728.qm@web111413.mail.gq1.yahoo.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [multimob] WG Adoption call ondraft-schmidt-multimob-pmipv6-mcast-deployment-04
Thread-Index: Acqz3jntFqWdR2uRRsWwZQkyTx6yPAAHEceQ
References: <647440.46250.qm@web111410.mail.gq1.yahoo.com><643B0A1D1A13AB498304E0BBC802784801E0C770@S4DE8PSAAQC.mitte.t-com.de><D60519DB022FFA48974A25955FFEC08C02D9A170@SAM.InterDigital.com><822998.17108.qm@web111405.mail.gq1.yahoo.com><D60519DB022FFA48974A25955FFEC08C02D9A39F@SAM.InterDigital.com> <865604.51728.qm@web111413.mail.gq1.yahoo.com>
From: Dirk.von-Hugo@telekom.de
To: sarikaya@ieee.org, JuanCarlos.Zuniga@InterDigital.com, multimob@ietf.org
X-OriginalArrivalTime: 23 Feb 2010 08:29:22.0345 (UTC) FILETIME=[4CE68190:01CAB462]
Subject: Re: [multimob] WG Adoption call ondraft-schmidt-multimob-pmipv6-mcast-deployment-04
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multimob>
List-Post: <mailto:multimob@ietf.org>
List-Help: <mailto:multimob-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Feb 2010 08:27:27 -0000

Dear Carlos, all,

Following the agreed adoption of the basic Multimob protocol we can and should revive and extend the discussion on further enhancements for protocol optimization as you suggested, Carlos. For that we have submitted the next version of the "future work" draft to exchange on potential range for those issues. Although by far not all possible topics have been covered we would like to base the design on this document.
The I-D can be found at http://www.ietf.org/internet-drafts/draft-von-hugo-multimob-future-work-01.txt

What do you think?
Please feel free to comment!

Best regards
Dirk

-----Ursprüngliche Nachricht-----
Von: multimob-bounces@ietf.org [mailto:multimob-bounces@ietf.org] Im Auftrag von Behcet Sarikaya
Gesendet: Montag, 22. Februar 2010 17:44
An: Zuniga, Juan Carlos; multimob@ietf.org
Betreff: Re: [multimob] WG Adoption call ondraft-schmidt-multimob-pmipv6-mcast-deployment-04

Sure.

--b



----- Original Message ----
> From: "Zuniga, Juan Carlos" <JuanCarlos.Zuniga@InterDigital.com>
> To: Behcet Sarikaya <sarikaya@ieee.org>; multimob@ietf.org
> Sent: Mon, February 22, 2010 10:28:46 AM
> Subject: RE: [multimob] WG Adoption call on draft-schmidt-multimob-pmipv6-mcast-deployment-04
> 
> Hi Behcet,

It is now "next week". 

While the base solution is 
> cleaned up, I guess we are ready to discuss about protocol 
> enhancements.

Do you agree?

Juan Carlos

> -----Original 
> Message-----
> From: Behcet Sarikaya [mailto:> ymailto="mailto:behcetsarikaya@yahoo.com" 
> href="mailto:behcetsarikaya@yahoo.com">behcetsarikaya@yahoo.com]
> 
> Sent: Thursday, 18 February, 2010 7:46 PM
> To: Zuniga, Juan Carlos; > ymailto="mailto:multimob@ietf.org" 
> href="mailto:multimob@ietf.org">multimob@ietf.org
> Subject: Re: 
> [multimob] WG Adoption call on draft-schmidt-multimob-
> 
> pmipv6-mcast-deployment-04
> 
> Hi Carlos,
>   This current 
> adoption call is aimed at establishing if there is
> consensus that this 
> draft is the base solution. You are saying it is.
> 
>   Let's 
> discuss other issues next week.
> 
> 
> Regards
> 
> 
> 
> ----- Original Message ----
> > From: "Zuniga, Juan 
> Carlos" <> href="mailto:JuanCarlos.Zuniga@InterDigital.com">JuanCarlos.Zuniga@InterDigital.com>
> 
> > To: Stig Venaas <> href="mailto:stig@venaas.com">stig@venaas.com>; > ymailto="mailto:sarikaya@ieee.org" 
> href="mailto:sarikaya@ieee.org">sarikaya@ieee.org;
> > ymailto="mailto:multimob@ietf.org" 
> href="mailto:multimob@ietf.org">multimob@ietf.org
> > Sent: Thu, 
> February 18, 2010 4:09:32 PM
> > Subject: RE: [multimob] WG Adoption 
> callondraft-schmidt-multimob-
> pmipv6-mcast-deployment-04
> 
> >
> > Behcet, Stig,
> 
> I'd like to understand if you 
> believe the group has reached
> > agreement that it is worth looking at 
> optimizations on top of the
> base
> > solution.
> 
> 
> It has been discussed in the list that there are scenarios
> > where 
> the solution detailed in draft-schmidt could have limitations,
> 
> for
> > instance when different MNs using different LMAs join the same 
> group.
> In such a
> > case we can save bandwidth by having a 
> dedicated multicast LMA. Also,
> another
> > advantage of a 
> dedicated LMA is to avoid the need for all LMAs to
> have 
> multicast
> > capability and connectivity.
> 
> I believe 
> that draft-schmidt is a very good
> > document and if it addresses the 
> open comments sent on the list it
> can become
> > the base 
> solution. However, I also believe that we have enough
> interest in 
> the
> > group to pursue further enhancements on top of this base 
> solution.
> 
> Please
> > let me know your views.
> 
> 
> Regards,
> 
> Juan Carlos
> 
> 
> 


      
_______________________________________________
multimob mailing list
multimob@ietf.org
https://www.ietf.org/mailman/listinfo/multimob