IETF Logo Mail Archive

[Gen-art] Gen-Art review of draft-ietf-multimob-pmipv6-ropt-07.txt

Alexey Melnikov <alexey.melnikov@isode.com> Tue, 16 July 2013 10:16 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79C1811E8276 for <gen-art@ietfa.amsl.com>; Tue, 16 Jul 2013 03:16:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.671
X-Spam-Level:
X-Spam-Status: No, score=-102.671 tagged_above=-999 required=5 tests=[AWL=-0.073, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 FeBIhTIDHjUp for <gen-art@ietfa.amsl.com>; Tue, 16 Jul 2013 03:16:55 -0700 (PDT)
Received: from waldorf.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id 6928121E81DF for <gen-art@ietf.org>; Tue, 16 Jul 2013 03:16:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1373969807; d=isode.com; s=selector; i=@isode.com; bh=UhmvCFExXaoVoaHR7eiSK6S6PGXj3U+AMyo+JFqpAY8=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=pjvS9Jl3/wHQfYu5J0/ZN8Q0u3bP0U/W75s7o/xd1KAstPyp0gFnzO3e6XJ8OJ8Imh1RTQ L4VXsR9aNSWkgASVqVrek66ri9A0hHa0V5bcCSZVwhQwGevRSW4vgAqez2u5rwUSsF7Fr0 vbkS/UK3ALFS5PVhEv9YZrxNFOXy+Es=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250]) by waldorf.isode.com (submission channel) via TCP with ESMTPA id <UeUdjQBjM3Qv@waldorf.isode.com>; Tue, 16 Jul 2013 11:16:47 +0100
Message-ID: <51E51DA9.8000005@isode.com>
Date: Tue, 16 Jul 2013 11:17:13 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
To: draft-ietf-multimob-pmipv6-ropt.all@tools.ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------000607020007020501030504"
Cc: gen-art@ietf.org
Subject: [Gen-art] Gen-Art review of draft-ietf-multimob-pmipv6-ropt-07.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jul 2013 10:16:56 -0000

I am the assigned Gen-ART reviewer for this draft. For background on 
Gen-ART, please see the FAQ 
at<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments 
you may receive.

Document: draft-ietf-multimob-pmipv6-ropt-07.txt

Reviewer: Alexey Melnikov

Review Date: 16 July 2013

IETF LC End Date: 3 July 2013

IESG Telechat date: 18 July 2013

Summary: Ready for publication as an Experimental RFC with some nits


Major issues: None

Minor issues:



In 5.1.2:

Dynamic IP Multicast Selector Mode Flag:

       This field indicates the subscription via MTMA/direct routing
       mode.  If the (M) flag value is set to a value of (1), it is an
       indication that the IP multicast traffic associated to the
       multicast group(s) identified by the Multicast Address Record(s)
       in this mobility option SHOULD be routed locally (subscription via
       direct routing mode).  If the (M) flag value is set to a value of
       (0), it is an indication that IP multicast traffic associated to
       the multicast group(s) identified by the Multicast Address Record
       in this mobility option(s) SHOULD be routed to the home network,
       via the MTMA (subscription via MTMA mode).  All other IP traffic
       associated with the mobile node SHOULD be managed according to a
       default policy configured at the PMIPv6 multicast domain.

The last sentence: I don't think you should use RFC 2119 SHOULD here.
I think you are saying that this document doesn't affect all other IP
traffic. So just use "is managed" instead of "SHOULD be managed".


Is IANA Considerations section clear to IANA? I suggest you add at least 
the URI for the IANA registry.
Is IANA registration policy compatible with the type of document 
(Experimental)? I can't check that, as I don't know which registry you 
are talking about.


Nits/editorial comments:


In 3.3: acronyms PBU and PBA need to be expanded on first use. They are 
expanded further down in the document.

v2.23.0 | Report a Bug | By Email