Re: [multimob] WG adoption call on draft-zuniga-multimob-pmipv6-ropt

[seil jeon <[e-mail]>]

Hi Thomas,

Please see inline.

Regards,

Seil Jeon

2011/12/11 Thomas C. Schmidt <[e-mail]>

> Hi Seil,
>
>
> On 10.12.2011 02:15, seil jeon wrote:
>
>
> But when the MAG is connected with several LMAs including PIM-SM, MRIB
>> SHOULD get information from PMIP routing table but "MAG's RIB doesn't
>> reflect PMIP routing" (Thomas and Hitoshi agreed it).
>>
>>
> the "problem" that causes these repeated errors in reasoning here on the
> list is the following (quoting Sri):
>
>
>  1. PMIP routing is not ordinary routing, but policy-based.
>     This means, it is not based on the destination address, but
>     on policy filters, in this case *source* addresses.
>
>  2. The consequence is: You cannot write PMIP routing rules in a regular
> routing table.
>
>  3. Because you cannot write PMIP routing in *one* normal RIB, you also
> cannot built a (PIM-SM) MRIB from it.
>     (And this is the reality-check for Hitoshi: he will see that he cannot
> write an MRIB in this case ...).
>
>
In general, there is no big deal about this. The fuzz is only that
draft-asaeda-multimob-pmip6-**extension-07 is built upon an error from
misunderstanding PMIP routing ...
=> My intention was to clarify the differences between you and Hitoshi.
Now, I think the issue is getting more clear.


Your problem of draft http://tools.ietf.org/id/**
draft-zuniga-multimob-pmipv6-**ropt-01.txt<http://tools.ietf.org/id/draft-zuniga-multimob-pmipv6-ropt-01.txt>is
a different one. You need to describe deployment of direct routing
(e.g,
PIM) at a MAG that runs PMIP routing (including tunnel interfaces) and
normal routing in the access network (the non-PMIP case). You should
explain this in your draft so well that readers can understand and
successfully deploy. In the current version you just say "turn on PIM" ...
and that's not all, I guess.

 => Yes, definitely. As I told it in the previous list, it will be added
explicitly and arrange two solutions with consistence of written style.



> Best,
>
> Thomas
>
>  2011/12/10 Thomas C. Schmidt <[e-mail]-**hamburg.de<[e-mail]>
>> <mailto:schmidt@informatik.**haw-hamburg.de<[e-mail]>>>
>>
>>
>>
>>    Hitoshi,
>>
>>
>>    On 09.12.2011 03:42, Hitoshi Asaeda wrote:
>>
>>            Then Sri stepped in and explained the same thing again: The MAG
>>            performs policy-based routing according to policy filters, not
>>            according to a regular RIB.
>>
>>
>>        Then we should ask you one thing.
>>        Why your source mobility draft introduces PIM-SM and Bidir PIM
>>        on MAG?
>>
>>        In Section 5, your source mobility draft says;
>>
>>        "a multicast routing protocol such as PIM-SM [RFC4601] or BIDIR-PIM
>>            [RFC5015] deployed at the MAGs."
>>
>>
>>    We are considering the direct mcast routing deployment (not
>>    following PMIP) - for receivers, this is the solution of Seil. There
>>    is no problem with it.
>>
>>    Your proposal under debate is: Use PIM-SM on PMIP tunnels and in
>>    concordance with PMIP routing, which is a completely different story.
>>
>>    However, to resolve the debate, there is a very simple reality-check:
>>
>>      For a basic PMIP scenario (MAG with 2 LMA uplinks and MNs
>>    associated to either LMA), please just write down *one* PIM-SM
>>    multicast routing table that accounts for PMIP routing and works for
>>    all MNs attached to the MAG.
>>
>>      If you can do so correctly, you have proved that your approach is
>>    feasible.
>>
>>    Thanks,
>>
>>    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:
>>    [phone] °
>>    ° http://www.informatik.haw-__**hamburg.de/~schmidt<http://www.informatik.haw-__hamburg.de/~schmidt>
>>    <http://www.informatik.haw-**hamburg.de/~schmidt<http://www.informatik.haw-hamburg.de/~schmidt>>
>>    Fax:
>>    [phone] °
>>
>>    ______________________________**___________________
>>    multimob mailing list
>>    [e-mail] <mailto:[e-mail]>
>>    https://www.ietf.org/mailman/_**_listinfo/multimob<https://www.ietf.org/mailman/__listinfo/multimob>
>>    <https://www.ietf.org/mailman/**listinfo/multimob<https://www.ietf.org/mailman/listinfo/multimob>>
>>
>>
>>
>>
>>
>>
>> ______________________________**_________________
>> multimob mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/**listinfo/multimob<https://www.ietf.org/mailman/listinfo/multimob>
>>
>
> --
>
> 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: [phone]
> °
> ° http://www.informatik.haw-**hamburg.de/~schmidt<http://www.informatik.haw-hamburg.de/~schmidt>   Fax: [phone] °
>