Re: [multimob] Comment on draft-asaeda-multimob-pmip6-extension-07

Hitoshi Asaeda <asaeda@sfc.wide.ad.jp> Mon, 12 December 2011 09:26 UTC

Return-Path: <asaeda@sfc.wide.ad.jp>
X-Original-To: multimob@ietfa.amsl.com
Delivered-To: multimob@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7C9221F8A97 for <multimob@ietfa.amsl.com>; Mon, 12 Dec 2011 01:26:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.096
X-Spam-Level:
X-Spam-Status: No, score=-99.096 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RELAY_IS_203=0.994, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZrSRRtzBsN+Q for <multimob@ietfa.amsl.com>; Mon, 12 Dec 2011 01:26:56 -0800 (PST)
Received: from mail.sfc.wide.ad.jp (shonan.sfc.wide.ad.jp [203.178.142.130]) by ietfa.amsl.com (Postfix) with ESMTP id 12D1421F8A7E for <multimob@ietf.org>; Mon, 12 Dec 2011 01:26:56 -0800 (PST)
Received: from localhost (dhcp-143-200.sfc.wide.ad.jp [203.178.143.200]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 4D7A5278079; Mon, 12 Dec 2011 18:26:53 +0900 (JST)
Date: Mon, 12 Dec 2011 18:26:51 +0900
Message-Id: <20111212.182651.233678588.asaeda@sfc.wide.ad.jp>
To: sijeon79@gmail.com
From: Hitoshi Asaeda <asaeda@sfc.wide.ad.jp>
In-Reply-To: <CALhCTOGLip14U3Kkm31xOPtoYbYtch93FN8Q1qDbvCgo1Ha=2g@mail.gmail.com>
References: <CALhCTOGLip14U3Kkm31xOPtoYbYtch93FN8Q1qDbvCgo1Ha=2g@mail.gmail.com>
X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Cc: multimob@ietf.org
Subject: Re: [multimob] Comment on draft-asaeda-multimob-pmip6-extension-07
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Mon, 12 Dec 2011 09:26:56 -0000

Hi Seil,

>> PIM-SM does not need to use PMIP policy routing at all.
>> Some MRIB entries are copied from MAG's RIB, other MRIB entries are
>> separately configured if needed. The MRIB entries may use M-Tunnel
>> established between MAG and LMA.
> 
> O.K. If my understainding is correct, your PIM-SM idea is based on not
> "PMIP tunnel" but "M-Tunnel" between MAG and LMA to choose one LMA using
> RPF algorithm.

If LMA is not an upstream router in MAG's RIB but if it should be in
MAG's MRIB, M-Tunnel is used to attach.

> And "M-Tunnel" information is in MAG's RIB.

Precisely, "M-Tunnel information is in MAG's MRIB".

> And if then, the upstream router of MAG has nothing to be an LMA, it can be
> another dedicated server for multicast support because it does not use PMIP
> tunnel. So, your idea appear to me as one of specific PIM-SM application
> method over dedicated multicast architecture.

I don't understand what "dedicated server" and "dedicated multicast
architecture" mean.

Let's see the case of direct routing.
If operator thinks streams for some group (or source) prefixes do not
need to go through LMA (as they are direct routing), MAG enabling
PIM-SM simply forwards PIM join messages to its adjacent multicast
router without M-Tunnel and can get the streams natively.

Regards,
--
Hitoshi Asaeda