Re: [multimob] Commentson draft-deng-multimob-pmip6-requirement-01.txt

<pierrick.seite@orange-ftgroup.com> Tue, 09 December 2008 10:00 UTC

Return-Path: <multimob-bounces@ietf.org>
X-Original-To: multimob-archive@optimus.ietf.org
Delivered-To: ietfarch-multimob-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 89FEC3A6838; Tue, 9 Dec 2008 02:00:51 -0800 (PST)
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 499303A6838 for <multimob@core3.amsl.com>; Tue, 9 Dec 2008 02:00:51 -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_FR=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 tplNA4WOANg4 for <multimob@core3.amsl.com>; Tue, 9 Dec 2008 02:00:50 -0800 (PST)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com [195.101.245.15]) by core3.amsl.com (Postfix) with ESMTP id 0C3C63A63D3 for <multimob@ietf.org>; Tue, 9 Dec 2008 02:00:49 -0800 (PST)
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); Tue, 9 Dec 2008 11:00:27 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 09 Dec 2008 11:00:26 +0100
Message-ID: <DD8B8FEBBFAF9E488F63FF0F1A69EDD105592737@ftrdmel1>
In-Reply-To: <493D7E90.5010307@innovationslab.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [multimob] Commentson draft-deng-multimob-pmip6-requirement-01.txt
thread-index: AclZcL8g6EL0emShTIG2h5lxWzqQsAAcSG8w
References: <49130E13.8040805@informatik.haw-hamburg.de> <20081107.005253.179720275.asaeda@sfc.wide.ad.jp> <49131786.2030100@informatik.haw-hamburg.de> <20081107.013921.242149102.asaeda@sfc.wide.ad.jp> <49132333.3020403@informatik.haw-hamburg.de> <1d38a3350811090759n146c643jb709781328bd4c33@mail.gmail.com> <167758.33851.qm@web111413.mail.gq1.yahoo.com><493D5577.5050300@cs.uni-goettingen.de> <493D7E90.5010307@innovationslab.net>
From: pierrick.seite@orange-ftgroup.com
To: brian@innovationslab.net, niklas.neumann@cs.uni-goettingen.de
X-OriginalArrivalTime: 09 Dec 2008 10:00:27.0203 (UTC) FILETIME=[F609E930:01C959E4]
Cc: multimob@ietf.org
Subject: Re: [multimob] Commentson draft-deng-multimob-pmip6-requirement-01.txt
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/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: multimob-bounces@ietf.org
Errors-To: multimob-bounces@ietf.org

Hi all,

The requirement draft allows different multicast deployment models for PMIP. The problem is that the document is focusing also on operator requirements for IPTV deployment and it made confusion during boF meeting. So, I agree we should clarify basics and focus on the problem we are trying to solve with PMIP. A separate document, as suggested by Suresh, could help. I guess work over this document could start with Brian's threads, right?

Regards,
Pierrick

> -----Message d'origine-----
> De : multimob-bounces@ietf.org [mailto:multimob-bounces@ietf.org] De la
> part de Brian Haberman
> Envoyé : lundi 8 décembre 2008 21:08
> À : Niklas Neumann
> Cc : multimob@ietf.org
> Objet : Re: [multimob] Commentson draft-deng-multimob-pmip6-requirement-
> 01.txt
> 
> Niklas,
>       I have two take aways from the BoF held in Minneapolis.  I will
> start two separate threads on the mailing list to discuss them, but at
> the high level they are:
> 
> 1. Rather than focus on optimizations (i.e., LMA to MAG), focus on the
> basics needed to deploy multicast in the current PMIPv6 architecture.
> 
> 2. Identify whether there is interest in investigating the performance
> of IGMP/MLD over wireless networks.
> 
> Regards,
> Brian
> 
> 
> Niklas Neumann wrote:
> > Hy everybody,
> >
> > are we satisfied with the charter proposal and the problem statement? It
> > was my impression that a lot of people didn't agree with some of the
> > assumptions made there. For example, LMA vs. MAG as multicast endpoints.
> >
> > So maybe we should revise those documents and be a little more
> > conservative about the assumptions and statements made there. Something
> > along the lines of examining current multicast behavior in PMIP with the
> > goal of working on a best-practice guide or optimizations where needed.
> >
> > At least the discussion during the BOF showed, that the specifications
> > are not clear about multicast in PMIP and clarifications are needed.
> >
> > Best regards
> >   Niklas
> >
> >
> > Behcet Sarikaya wrote:
> >> Hello all,
> >>   At Multimob BoF last week it became clear that PMIPv6 requirements
> >> draft concentrated (probably) too much on the operating requirements
> >> and failed to state some simple traffic requirements.
> >>   I remember these traffic requirements were already stated in the pre
> >> BoF meeting we had in Dublin.
> >>   Any comments? Suresh?
> >>
> >> Regards,
> >>
> >> Behcet
> 
> _______________________________________________
> multimob mailing list
> multimob@ietf.org
> https://www.ietf.org/mailman/listinfo/multimob
_______________________________________________
multimob mailing list
multimob@ietf.org
https://www.ietf.org/mailman/listinfo/multimob