Re: [multimob] Direct Multicast Routing & the Deployment of PIM-SM(Juan Liu)

"Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de> Thu, 02 August 2012 02:45 UTC

Return-Path: <prvs=554f9d383=schmidt@informatik.haw-hamburg.de>
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 22EBD11E8183 for <multimob@ietfa.amsl.com>; Wed, 1 Aug 2012 19:45:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.424
X-Spam-Level:
X-Spam-Status: No, score=-100.424 tagged_above=-999 required=5 tests=[AWL=-1.825, BAYES_00=-2.599, HELO_EQ_DE=0.35, J_CHICKENPOX_34=0.6, J_CHICKENPOX_64=0.6, MIME_CHARSET_FARAWAY=2.45, 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 iP6Uv1FgkqaI for <multimob@ietfa.amsl.com>; Wed, 1 Aug 2012 19:45:43 -0700 (PDT)
Received: from mx6.haw-public.haw-hamburg.de (mx6.haw-public.haw-hamburg.de [141.22.6.3]) by ietfa.amsl.com (Postfix) with ESMTP id C53AE11E8169 for <multimob@ietf.org>; Wed, 1 Aug 2012 19:45:42 -0700 (PDT)
Received: from mailgate.informatik.haw-hamburg.de ([141.22.30.74]) by mail6.is.haw-hamburg.de with ESMTP/TLS/ADH-AES256-SHA; 02 Aug 2012 04:45:41 +0200
Received: from localhost (localhost [127.0.0.1]) by mailgate.informatik.haw-hamburg.de (Postfix) with ESMTP id 19AA2105A988; Thu, 2 Aug 2012 04:45:41 +0200 (CEST)
Received: from mailgate.informatik.haw-hamburg.de ([127.0.0.1]) by localhost (mailgate.informatik.haw-hamburg.de [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 11100-04; Thu, 2 Aug 2012 04:45:40 +0200 (CEST)
Received: from [130.129.83.194] (dhcp-53c2.meeting.ietf.org [130.129.83.194]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate.informatik.haw-hamburg.de (Postfix) with ESMTPSA id EB8E4105A984; Thu, 2 Aug 2012 04:45:39 +0200 (CEST)
Message-ID: <5019E9D4.9040608@informatik.haw-hamburg.de>
Date: Wed, 01 Aug 2012 19:45:40 -0700
From: "Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: liu.juan45@zte.com.cn
References: <OF67CCCC6C.E5FFA46D-ON48257A4E.00069465-48257A4E.000D55B4@zte.com.cn>
In-Reply-To: <OF67CCCC6C.E5FFA46D-ON48257A4E.00069465-48257A4E.000D55B4@zte.com.cn>
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: by amavisd-new at informatik.haw-hamburg.de
Cc: multimob@ietf.org
Subject: Re: [multimob] Direct Multicast Routing & the Deployment of PIM-SM(Juan Liu)
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: Thu, 02 Aug 2012 02:45:44 -0000

Hi Juan Liu,

please see inline.

On 01.08.2012 19:27, liu.juan45@zte.com.cn wrote:

>> Message: 1
>> Date: Wed, 01 Aug 2012 16:01:56 -0700
>> From: "Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de>
>> To: "multimob@ietf.org" <multimob@ietf.org>
>> Subject: [multimob] Direct Multicast Routing & the Deployment  of
>>    PIM-SM
>> Message-ID: <5019B564.30709@informatik.haw-hamburg.de>
>> Content-Type: text/plain; charset=ISO-8859-15; format=flowed
>>
>> Hi all,
>>
>> after Monday's presentation of PIM deployment options
>> (draft-ietf-multimob-pmipv6-source), there was the discussion on further
>> optimization options. In detail, the idea was raised to reach MNs  not
>> via their (permanent) HNP advertisements at the LMA, but directly  at
>> their current MAGs. The latter would require a dynamic unicast routing
>> protocol in the access network.

> In order that multicast traffic reach MNs directly via MAG-MAG tunnel not
> via LMA-MAG tunnel,MRIB can be constructed using route from the tunnel
> between MAGs(draft-liu-multimob-pmipv6-multicast-ro).

The scenario of your draft is a completely different one: If I
understood correctly, you distribute traffic in an overlay. (construct a
mesh of tunnels between MAGs, inquire routes to MNs via an LMA-based
on-demand search and then select the proper tunnel for forwarding).

This is different from what we refer to by the term "direct (or
localized) routing".

>>
>> I promised to talk to Sri about this (underlying unicast) approach.  As
>> expected, Sri emphasized that the PMIP WGs intentionally do *not*
>> consider this a working option. The reason is that node mobility
>> typically is more intense and faster than unicast routing dynamics.
>> Advertising MN's HNPs throughout the access network would cause route
>> pollution and convergence problems and quickly lead to inconsistencies.
>> For the unicast case, this is the equivalent of pushing multicast
>> mobility management into multicast routing, which we equally avoid.

> About the working option you talk with Sri,does it refer to direct 
> routing via MAGs,
> which in PMIP WG unicast routing through MAG-MAG tunnel is an acceptable 
> optimization
> options for PMIPv6 routing. Hope i'm not wrong about this.

We didn't talk about overlay solutions. We just addressed the
straight-forward deployment of dynamic unicast routing protocols like
iBGP or OSPF. So nothing was said about your draft.

Best regards,

Thomas

-- 

Prof. Dr. Thomas C. Schmidt
° Hamburg University of Applied Sciences                   Berliner Tor 7 °
° Dept. Informatik, Internet Technologies Group    20099 Hamburg, Germany °
° http://www.haw-hamburg.de/inet                   Fon: +49-40-42875-8452 °
° http://www.informatik.haw-hamburg.de/~schmidt    Fax: +49-40-42875-8409 °