Re: [multimob] Working group last call for draft-ietf-multimob-fmipv6-pfmipv6-multicast-05

"Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de> Mon, 31 March 2014 21:57 UTC

Return-Path: <prvs=160a38399=schmidt@informatik.haw-hamburg.de>
X-Original-To: multimob@ietfa.amsl.com
Delivered-To: multimob@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 309091A08D5 for <multimob@ietfa.amsl.com>; Mon, 31 Mar 2014 14:57:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.56
X-Spam-Level:
X-Spam-Status: No, score=-1.56 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PEt9k74F0KfN for <multimob@ietfa.amsl.com>; Mon, 31 Mar 2014 14:57:40 -0700 (PDT)
Received: from mx3.haw-public.haw-hamburg.de (mx3.haw-public.haw-hamburg.de [141.22.6.2]) by ietfa.amsl.com (Postfix) with ESMTP id 8B6521A08DD for <multimob@ietf.org>; Mon, 31 Mar 2014 14:57:39 -0700 (PDT)
Received: from mailgate.informatik.haw-hamburg.de ([141.22.30.74]) by mail3.is.haw-hamburg.de with ESMTP/TLS/ADH-AES256-SHA; 31 Mar 2014 23:57:35 +0200
Received: from localhost (localhost [127.0.0.1]) by mailgate.informatik.haw-hamburg.de (Postfix) with ESMTP id 0FD4210679D7; Mon, 31 Mar 2014 23:57:35 +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 30341-09; Mon, 31 Mar 2014 23:57:34 +0200 (CEST)
Received: from [192.168.178.49] (g231227163.adsl.alicedsl.de [92.231.227.163]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mailgate.informatik.haw-hamburg.de (Postfix) with ESMTPSA id C5D7B10679CF; Mon, 31 Mar 2014 23:57:33 +0200 (CEST)
Message-ID: <5339E4CC.9040809@informatik.haw-hamburg.de>
Date: Mon, 31 Mar 2014 23:57:32 +0200
From: "Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Dirk.von-Hugo@telekom.de, stig@venaas.com, multimob@ietf.org
References: <533095B8.8080207@venaas.com> <05C81A773E48DD49B181B04BA21A342A2DE422B244@HE113484.emea1.cds.t-internal.com>
In-Reply-To: <05C81A773E48DD49B181B04BA21A342A2DE422B244@HE113484.emea1.cds.t-internal.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: by amavisd-new at informatik.haw-hamburg.de
Archived-At: http://mailarchive.ietf.org/arch/msg/multimob/gCDuSrt6r5TzwHpRhoiqWe_rAyc
Subject: Re: [multimob] Working group last call for draft-ietf-multimob-fmipv6-pfmipv6-multicast-05
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.15
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, 31 Mar 2014 21:57:43 -0000

Hi Dirk,

many thanks for carefully looking through the draft. Please see comments 
inline.

On 27.03.2014 16:30, Dirk.von-Hugo@telekom.de wrote:

> Sorry that I missed the preceding WGLC - I do think that this document is ready for publication. It has greatly improved since version 00 ;-)
>
> Though some (minor) nits came to my mind after re-reading:
>
> p.1.
> Updates: 5568 (if approved) => shouldn't be added 5949 since it does also update PFMIPv6?
>

I don't think so. The update of 5568 is with the PrRtAdv-Messages. 5949 
does not contain such things, as there is no explicit messaging between 
MAGs and the MN. Mobility Options are explicitly under the control of IANA.

> As mentioned by others for prior versions there is still mixed usage of FBack, Hack, ... and FBACK, HACK, ...
> Same for PMAG/NMAG and pMAG/nMAG.
>

Oh yes, that was in the figures ...

> p.10ff
> "Section 3.3.  Protocol Operations Specific to PFMIPv6" and Figs. 4/5 do include "PMAG (PAR)" and "NMAG (NAR)" - isn't it all about PMIP - so no relevance for AR? Otherwise I would expect a statement like that also a mixed scenario MIP/PMIP is in focus here ...
> I tried to find out whether this was explained in prior posts but didn't catch any ... sorry if I missed it!
>

Actually the terms PAR and NAR in parenthesis are used to indicate the 
correspondence with FMIP ... it does not consider mixed terms, but 
should help the reader to see that this is all about the same "abstract 
entities" here.

> p.15
> sect. 4.1.3 is on NAR, so I guess:
> of the PAR => of the NAR
>

Yes, thanks.

> the NAR joins the groups subscribed
>     for forwarding on the tunnel link. < sounds puzzling to me
> => the NAR joins the groups the MN has subscribed
>     for (which are then forwarded by PAR) via the tunnel link. < is it that what is meant?
>

Yes, thanks. This is better.

> p.21
> number of muticast records => number of multicast records
>

Thanks, fixed.

> or Section 4.2 of [RFC3376]) for the => or Section 4.2 of [RFC3376] for the
>

Thanks, fixed.

> p.23
> 5.5.  Length Considerations: Number of Records and Addresses
> I understand why the maximum number of multicast address records is 72 or sources for MLDv2 is 89 (also given in http://tools.ietf.org/html/rfc3810#section-5.1.10), but I miss a consideration of specific limitation due to 8-bit Length format in new Mobility Header Multicast Option (Fig.7).
> Have I misunderstood something or isn't there a much stricter limit for multicast address records to (512-2-4)/(4+16) < 26 (w/o source addresses) ??
>

I guess you hit a point: By bringing back length formatting to standard 
mobility options recently, we missed that this will not fill an Ethernet 
packet. I don't think this matters much, but we definitely should adjust 
the section on length considerations.

> for that multicast address to their MLDv2 (IGMPv2) equivalents
> => for that multicast address to their MLDv2 (IGMPv3) equivalents
>

Thanks, fixed.

> Hope this helps

Yes, it definitely does.

We will wait for the next days to pass the call deadline and resubmit then.

Thanks again & best regards,

Thomas


>   -----Original Message-----
> From: multimob [mailto:multimob-bounces@ietf.org] On Behalf Of Stig Venaas
> Sent: Montag, 24. März 2014 21:30
> To: multimob@ietf.org
> Subject: [multimob] Working group last call for draft-ietf-multimob-fmipv6-pfmipv6-multicast-05
>
> This is a working group last call for
> draft-ietf-multimob-fmipv6-pfmipv6-multicast-05
>
> Please state whether you think it is ready for publishing or if you believe there are issues with the document or that it is not ready for other reasons.
>
> The document has already been reviewed by several people, but it is still good to hear from the working group what you think.
>
> The last call ends one week from now on Monday March 31st.
>
> The draft is available at
> http://tools.ietf.org/html/draft-ietf-multimob-fmipv6-pfmipv6-multicast-05
>
> Stig
>
> _______________________________________________
> multimob mailing list
> multimob@ietf.org
> https://www.ietf.org/mailman/listinfo/multimob
>
> _______________________________________________
> multimob mailing list
> multimob@ietf.org
> 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: +49-40-42875-8452 °
° http://www.informatik.haw-hamburg.de/~schmidt    Fax: +49-40-42875-8409 °