[multimob] Review of draft-ietf-multimob-fmipv6-pfmipv6-multicast-02

Behcet Sarikaya <sarikaya2012@gmail.com> Sun, 02 February 2014 23:39 UTC

Return-Path: <sarikaya2012@gmail.com>
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 707791A0009 for <multimob@ietfa.amsl.com>; Sun, 2 Feb 2014 15:39:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 wC-wb4Ufk6-M for <multimob@ietfa.amsl.com>; Sun, 2 Feb 2014 15:39:28 -0800 (PST)
Received: from mail-lb0-x22c.google.com (mail-lb0-x22c.google.com [IPv6:2a00:1450:4010:c04::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 265381A0014 for <multimob@ietf.org>; Sun, 2 Feb 2014 15:39:27 -0800 (PST)
Received: by mail-lb0-f172.google.com with SMTP id c11so4929546lbj.3 for <multimob@ietf.org>; Sun, 02 Feb 2014 15:39:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:date:message-id:subject:from:to:content-type; bh=Qn1JbjfLTuELhVOuJbUZCr68GTy0vzW2AYuaBssdxzU=; b=yBkpE/rilOgjweDunpP7QPFXZxEdY4YcyZ59t39klMy7ZuqsJDZkT/4b01CKIgglW7 QHJvyIzhNhbI+L4De1lKUSleIVQJB14sLB8iOSaHx1QfsNRDFHbEEoQlX8y2IpFjFmtC Od9U0Rzlrv0h0zbj/Tv6t6fPRQysED3BUlPjO/EPmMET+0FegN5WP16P/Okmlg63NvX6 pJUor+EoUkW17lMAcZU9ZOzxF4CpfbQuIi9FRu1+xTyCzyLBx20qV/40FxC16ktHzpFQ 2e7DysMLOWKAw3XZD3p/pAXuiwSLLTaeyJixlZ1Vryn/c7bcBGBHzrgH79CfZ7ijlv8f m+rw==
MIME-Version: 1.0
X-Received: by 10.152.42.129 with SMTP id o1mr11343324lal.19.1391384362975; Sun, 02 Feb 2014 15:39:22 -0800 (PST)
Received: by 10.114.170.193 with HTTP; Sun, 2 Feb 2014 15:39:22 -0800 (PST)
Date: Sun, 02 Feb 2014 17:39:22 -0600
Message-ID: <CAC8QAcfO9Gq6kbUt4kQOFuFQnjTgv9HC+Ps=f43j_tkwogvuNg@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: "multimob@ietf.org" <multimob@ietf.org>
Content-Type: multipart/alternative; boundary="001a11c3505cb3839d04f174eafc"
Subject: [multimob] Review of draft-ietf-multimob-fmipv6-pfmipv6-multicast-02
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: sarikaya@ieee.org
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: Sun, 02 Feb 2014 23:39:29 -0000

Dear all,

I finished my review while watching Superball 2014 :-), here it is:

- remove MIPv6 from the title

Sec. 2
In addition, the following terms are
   introduced:
   where are the terms?

Sec. 3.1
subnet link
   use on of them

when the group is
   natively received.
   What does this mean, please explain

As group membership information are
   s/are/is

Sec. 3.2
  FMIPv6 coverage is out of scope as it applies to MIPv6, so remove this
section
  Other sections may need adjustment based on this
Sec. 4.1.1
  As FMIPv6 is out of scope, this section needs to be rewritten to cover
PFMIPv6 (if any)
Section 5
  Here you may add one sentence saying that these structures can apply to
MIPv6?
Sec. 5.3
  The size of this option in 8 octets
  s/in/is

Last but not least, I think the draft finishes without a discussion of why
this solution is needed. We need some text on this. I don't know if the
reference "FMIPv6-Analysis" could be useful.

Regards,

Behcet