Re: [multimob] draft-ietf-multimob-pmipv6-source-06

[Behcet Sarikaya <[e-mail]>]

Hi Thomas,
See inline.

Regards,

Behcet

On Mon, Jan 6, 2014 at 12:24 PM, Thomas C. Schmidt <
[e-mail]> wrote:

> Hi Behcet,
>
>
> On 06.01.2014 18:32, Behcet Sarikaya wrote:
>
>  I don't know about others (Dirk and Sebastian) but I would like to see a
>> reply to my review.
>>
>>
> Dirk and Sebastian had only few straight-forward editorials/typos ...
> which have been just corrected.
>
> Regarding your review, please see inline:
>
> On 24.10.2013 22:49, Behcet Sarikaya wrote:>
>
>>
>> Here are my comments on this draft. You can take it as part of WGLC
>> comments. WGLC will be issued shortly.
>>
>> abstract and introduction
>> selective route optimization schemes - add using multicast tree mobility
>> anchor or multicast capable LMA
>>
>>
> Details of the schemes are already part of the introduction (incl. various
> refs). For the sake of conciseness of the abstract, we would prefer to
> stick to the abstract summary "selective route optimization schemes",
> instead of naming all approaches individually.
>
>  Figs 1 & 2  - change their placement and reformat, this may lead to the
>> whole figure in one page
>>
>>
> Thanks - done.
>
>  Sec. 3.2.2 - to enable multicast data
>>     transition from an MN  - replace transition with transmission?
>>
>>
> Thanks - done.
>
>  Sec. 3.2.3.1 sending
>>     PIM registers to the RP - this is explained in Sec. 4.3.2, add pointer
>>
>> RPF (Reverse Path Forwarding) - Reverse Path Forwarding (RPF)
>>
>> BIDIR PIM - BIDIR-PIM
>>
>>
> Thanks - all done.
>
>  Sec. 3.2.4
>> the multicast
>>     routing information base (MRIB) of the MAG - I thought this was not
>> possible? later on seems to be clarified in Sec. 4.3 & 4.4 (I mean
>> according to our face-to-face conversations in the past?)
>>
>>
> In this draft, we describe the setting of an MRIB in agreement with the
> topology of the access network. Like a unicast RIB, an MRIB can of course
> always express a regular, topology-oriented routing according to
> destination addresses in IP headers.
>
> Our discussions, which also took place on the mailing list earlier and in
> WG meetings, were concerned with policy-based PMIP routing according to
> source addresses. This cannot be expressed in a regular MRIB.
>
>
Where did you get this from? Any references?



> However, we are not talking about policy routing here in the draft, so no
> conflict.
>
>  Sec. 3.2.5
>> There is no mechanism to suppress upstream
>>        forwarding in the absence of receivers. - this is solved in Sec.
>> 5, add a pointer to the section that brings some solution
>>
>>
> Thanks, done.
>
>  Sec. 4.3 4.4 & Fig. 3 (b)
>>   see comment above on PIM at MAG
>>
>>  Thanks - done,
>
>  Sec. 4.3.6 should be subsection  of 4.3.5?
>>
>>
> No, as Section 4.3.5 is about PIM-SSM, and Section 4.3.5 discusses an
> orthogonal aspect (Handover Optimization) for both, PIM-SM and PIM-SSM.
>
>  Sec. 5.3 Operations at the Multicast Sender - the operation described
>> here is not performed by the MN which is the multicast source/sender, so
>> clarify
>>
>> same in Sec. 5.4. Operations at the Multicast Listener
>>
>>
> Thanks - both done.
>
>  Sec. 5.4
>> ASM with IGMPv3/MLDv2  - why not have this discussion in the first case,
>> i.e. ASM with IGMPv2/MLDv1?
>>
>>
> The first itemization is about ASM with IGMPv2/MLDv1 - it's on the
> previous page, so may be you overlooked.
>
>  Fig. 1 caption is too long - shorten it and carry the text to Sec. 3.1.
>>
>>
> Thanks, done.
>
>  In the abstract,
>> This document describes the support of mobile multicast senders - This
>> document describes an experimental protocol to support mobile multicast
>> senders
>>
>>
> Thanks, also done ... even though I missed to correct a preposition ...
> it's already corrected for the next version.
>
> Best regards,
>
> Thomas
>
>
>
>>     On 25.11.2013 18:38, Behcet Sarikaya wrote:
>>
>>         Dear all,
>>
>>         WGLC on
>>         draft-ietf-multimob-pmipv6-__source-06
>>
>>
>>         has ended.
>>
>>
>>         The authors, please submit your revised version.
>>
>>         Regards,
>>
>>         Behcet
>>
>>
>>         _________________________________________________
>>         multimob mailing list
>>         [e-mail] <mailto:[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] <tel:%2B49-40-42875-8452> °
>>     ° http://www.informatik.haw-__hamburg.de/~schmidt
>>     <http://www.informatik.haw-hamburg.de/~schmidt>    Fax:
>>     [phone] <tel:%2B49-40-42875-8409> °
>>     _________________________________________________
>>     multimob mailing list
>>     [e-mail] <mailto:[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    Fax: [phone]°
>