Re: [multimob] Comments on draft-deng-multimob-pmip6-requirement-01.txt
"Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de> Thu, 23 October 2008 20:57 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 EAE153A6A11; Thu, 23 Oct 2008 13:57:59 -0700 (PDT)
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 148B03A6955 for <multimob@core3.amsl.com>; Thu, 23 Oct 2008 13:57:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.116
X-Spam-Level:
X-Spam-Status: No, score=-2.116 tagged_above=-999 required=5 tests=[AWL=0.133, BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 EHnYJuSnCRCo for <multimob@core3.amsl.com>; Thu, 23 Oct 2008 13:57:58 -0700 (PDT)
Received: from mail2.rz.fhtw-berlin.de (mail2.rz.fhtw-berlin.de [141.45.10.102]) by core3.amsl.com (Postfix) with ESMTP id 1E0873A676A for <multimob@ietf.org>; Thu, 23 Oct 2008 13:57:58 -0700 (PDT)
Envelope-to: multimob@ietf.org
Received: from e178173070.adsl.alicedsl.de ([85.178.173.70] helo=[192.168.178.20]) by mail2.rz.fhtw-berlin.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from <schmidt@informatik.haw-hamburg.de>) id 1Kt7H3-000EZl-2O; Thu, 23 Oct 2008 22:59:17 +0200
Message-ID: <4900E5A0.9050306@informatik.haw-hamburg.de>
Date: Thu, 23 Oct 2008 22:59:12 +0200
From: "Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Behcet Sarikaya <sarikaya@ieee.org>
References: <352065.68132.qm@web38808.mail.mud.yahoo.com>
In-Reply-To: <352065.68132.qm@web38808.mail.mud.yahoo.com>
Cc: multimob@ietf.org
Subject: Re: [multimob] Comments on 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-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: multimob-bounces@ietf.org
Errors-To: multimob-bounces@ietf.org
Hi Behcet, Behcet Sarikaya wrote: > [thomas] RFC5213 does not address multicast routing (that's why we are > discussing it). The scenario described in fig 2 is *not* addressing > mobile multicast senders, > > [behcet] Then I think the text and figure on the local routing is not > needed because local routing in PMIPv6 refers to the routing of packets > coming from the uplink and as you said this would be multicast sender > situation which you left out in the requirements draft. > [thomas] This is a misunderstanding: Fig 2 does *not* refer to sender mobility. > but a typical content distribution setting as > for instance used in a provider-centric IPTV service. This means, a > provider issues multicast streams from within his network domain, aiming > at an efficient way to preserve (his own) network resources. > > From the minimal perspective of RFC5213 (unicast routing) there is no > efficient way to do this. That's why we are trying to identify protocol > extensions that smoothly cooperate with RFC 5213. > > [behcet] The situation you are talking about could become valid if route > optimization is used with PMIPv6. In that case the content server in > between MAG and LMA would send directly to MAG. If route optimization is > not used then all traffic goes through LMA-MAG tunnel. Route > optimization for PMIPv6 is some future work, there are drafts but we > don't know if the standardization will go ahead. > Route optimization with multicasting is even more complicated problem. > If you wish to state some requirements for this very complicated case > please go ahead. [thomas] Hmm, I'm not trying to add complicated requirements. This is the overview about possible scenarios. We're all just trying to think of a reasonable scope to address and solve the problem (so does the recent pmip6-extension-draft ... see also the last mail from Hitoshi). If multicast on PMIPv6 is supposed to serve as a solution for large-scale content distribution (like in IPTV applications), then we should not just propose to tunnel all traffic from one LMA to the MAGs. That's a bitter pill for those who have to pay for the infrastructure. Best regards, Thomas -- ° Prof. Dr. Thomas C. Schmidt ° HAW Hamburg, Dept. Informatik ° University of Applied Sciences ° Berliner Tor 7, D 20099 Hamburg, Germany ° Fon: +49-40-42875-8452, Fax: -8409 ° http://www.informatik.haw-hamburg.de/~schmidt _______________________________________________ multimob mailing list multimob@ietf.org https://www.ietf.org/mailman/listinfo/multimob
- [multimob] Comments on draft-deng-multimob-pmip6-… Behcet Sarikaya
- Re: [multimob] Comments on draft-deng-multimob-pm… Thomas C. Schmidt
- Re: [multimob] Comments on draft-deng-multimob-pm… Behcet Sarikaya
- Re: [multimob] Comments on draft-deng-multimob-pm… Thomas C. Schmidt
- Re: [multimob] Comments on draft-deng-multimob-pm… Behcet Sarikaya
- Re: [multimob] Comments on draft-deng-multimob-pm… Thomas C. Schmidt
- [multimob] Comments on draft-deng-multimob-pmip6-… John.zhao
- Re: [multimob] Comments on draft-deng-multimob-pm… Hui Deng
- Re: [multimob] Comments on draft-deng-multimob-pm… Hui Deng
- Re: [multimob] Comments on draft-deng-multimob-pm… Hitoshi Asaeda
- Re: [multimob] Comments on draft-deng-multimob-pm… Hitoshi Asaeda
- Re: [multimob] Comments on draft-deng-multimob-pm… Thomas C. Schmidt
- Re: [multimob] Comments on draft-deng-multimob-pm… John.zhao
- Re: [multimob] Comments on draft-deng-multimob-pm… Hui Deng
- Re: [multimob] Comments on draft-deng-multimob-pm… John.zhao
- Re: [multimob] Comments ondraft-deng-multimob-pmi… von Hugo, Dirk
- Re: [multimob] Comments ondraft-deng-multimob-pmi… John.zhao
- Re: [multimob] Comments ondraft-deng-multimob-pmi… von Hugo, Dirk
- Re: [multimob] Comments ondraft-deng-multimob-pmi… John.zhao
- Re: [multimob] Comments ondraft-deng-multimob-pmi… pierrick.seite
- Re: [multimob] Comments ondraft-deng-multimob-pmi… Thomas C. Schmidt
- Re: [multimob] Comments ondraft-deng-multimob-pmi… von Hugo, Dirk
- Re: [multimob] Comments ondraft-deng-multimob-pmi… Hitoshi Asaeda
- Re: [multimob] Comments ondraft-deng-multimob-pmi… Hitoshi Asaeda
- Re: [multimob] Comments ondraft-deng-multimob-pmi… Thomas C. Schmidt
- Re: [multimob] Comments ondraft-deng-multimob-pmi… Hitoshi Asaeda
- Re: [multimob] Comments ondraft-deng-multimob-pmi… Thomas C. Schmidt
- Re: [multimob] Comments ondraft-deng-multimob-pmi… John.zhao
- Re: [multimob] Comments on draft-deng-multimob-pm… Hui Deng
- Re: [multimob] Comments ondraft-deng-multimob-pmi… Hui Deng
- Re: [multimob] Comments ondraft-deng-multimob-pmi… Hui Deng
- Re: [multimob] Comments ondraft-deng-multimob-pmi… Thomas C. Schmidt
- [multimob] Comments on draft-deng-multimob-pmip6-… Behcet Sarikaya
- Re: [multimob] Comments ondraft-deng-multimob-pmi… von Hugo, Dirk
- Re: [multimob] Comments on draft-deng-multimob-pm… Suresh Krishnan
- Re: [multimob] Comments on draft-deng-multimob-pm… Niklas Neumann
- Re: [multimob] Comments on draft-deng-multimob-pm… Brian Haberman
- Re: [multimob] Commentson draft-deng-multimob-pmi… pierrick.seite
- Re: [multimob] Commentson draft-deng-multimob-pmi… Hui Deng