Re: [multimob] Comments on draft-deng-multimob-pmip6-requirement-01.txt
"Hui Deng" <denghui02@gmail.com> Sat, 01 November 2008 03:08 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 E19803A6805; Fri, 31 Oct 2008 20:08:20 -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 1E89D3A6805 for <multimob@core3.amsl.com>; Fri, 31 Oct 2008 20:08:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.319
X-Spam-Level:
X-Spam-Status: No, score=-1.319 tagged_above=-999 required=5 tests=[AWL=1.279, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 L-+s9CEmc2Yc for <multimob@core3.amsl.com>; Fri, 31 Oct 2008 20:08:18 -0700 (PDT)
Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.188]) by core3.amsl.com (Postfix) with ESMTP id 30C313A67AD for <multimob@ietf.org>; Fri, 31 Oct 2008 20:08:17 -0700 (PDT)
Received: by nf-out-0910.google.com with SMTP id b11so733733nfh.39 for <multimob@ietf.org>; Fri, 31 Oct 2008 20:08:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=adGgi+QUAY4OxLGM+FUS0w4oNHAdJfD4I/NFRrrkKLI=; b=cLtgCb/kIsejveYCLHaui7Ds6KRcwu/hungOXL/IMDeMCh1cyhQ3eZKT1oI+Yxvikd 0py0Zz0RhJ6jb9GpIcLDHGWCqqxk8M/3EFVMZE8/8lsm3+8uEj9oC9kPExiI1mvJbQcx ugtvtgtIj0jwcNKQv9NEBh24SeWuNCm88bQCU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=QLhCF0+1+SgTHVespoKR4tGFGIYiJWfqti5xfIVm7JncwGHBpmV7YKHN6dK5NXq25M 3ssTecC2TBaAh8ugFCX64QuT19iN2KRlCGDDj6dCoaEBjSveXNFxopVUjreJ79AQT5RQ y5QD1AvQx0ue/01x7305ORpyKtXG2ZMxCUUl4=
Received: by 10.210.89.4 with SMTP id m4mr9843943ebb.107.1225508895024; Fri, 31 Oct 2008 20:08:15 -0700 (PDT)
Received: by 10.210.109.14 with HTTP; Fri, 31 Oct 2008 20:08:14 -0700 (PDT)
Message-ID: <1d38a3350810312008x377ea91aw2739355335d2a207@mail.gmail.com>
Date: Sat, 01 Nov 2008 11:08:14 +0800
From: Hui Deng <denghui02@gmail.com>
To: "Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de>
In-Reply-To: <4900E5A0.9050306@informatik.haw-hamburg.de>
MIME-Version: 1.0
References: <352065.68132.qm@web38808.mail.mud.yahoo.com> <4900E5A0.9050306@informatik.haw-hamburg.de>
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-Type: multipart/mixed; boundary="===============0569847639=="
Sender: multimob-bounces@ietf.org
Errors-To: multimob-bounces@ietf.org
Hi, Thomas, I agree this scenario works for some deployment, but question here is whether we need extend any pmip6 protocol to support this scenario? thanks -Hui 2008/10/24 Thomas C. Schmidt <schmidt@informatik.haw-hamburg.de> > 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