Re: I-D Action: draft-ietf-6man-multicast-addr-arch-update-03.txt

神明達哉 <jinmei@wide.ad.jp> Thu, 13 February 2014 19:55 UTC

Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0FA11A0409 for <ipv6@ietfa.amsl.com>; Thu, 13 Feb 2014 11:55:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.922
X-Spam-Level: *
X-Spam-Status: No, score=1.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=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 iclEcDnEOGy2 for <ipv6@ietfa.amsl.com>; Thu, 13 Feb 2014 11:55:21 -0800 (PST)
Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id F03EE1A0406 for <ipv6@ietf.org>; Thu, 13 Feb 2014 11:55:20 -0800 (PST)
Received: by mail-we0-f180.google.com with SMTP id u57so7924161wes.39 for <ipv6@ietf.org>; Thu, 13 Feb 2014 11:55:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=F9bj7dHKv8IPcuwRytEIlcowy4fSkygNs4V6aGNuvj0=; b=fXB0m/By1noYZGoo2ajpE3HZjx2jAJqJEdKlL9JWDK2WXn+yrCDDjXPfl0gT3zrGON 52sFvxKoglh7XnRSxSISYWq9SJ3xojypyewtdQ4hH2nHQuWfwMx9Hnj7ozNZZ43x4RAu 1sVEVgPMdY93EMt5L45C/tePTPALdkZM/8E5MAppGUYEyDq1jBq/q+tPs6qwE2X5ZXkQ N+zgHabuxYAC5Gsmkz70xZ6mcgRmFXDagUMCioMzTzgKOaG6rDPzhXTKSUzkWioTXdbE x1ZV2FL6RxzHn9qKnE7noy+JWit6cgs6T0QIeqYu/ok9DMamivNjmua4Al+dLGD0sTnj ICPg==
MIME-Version: 1.0
X-Received: by 10.180.72.239 with SMTP id g15mr7890468wiv.45.1392321318513; Thu, 13 Feb 2014 11:55:18 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.120.167 with HTTP; Thu, 13 Feb 2014 11:55:18 -0800 (PST)
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36F4C31E952@PUEXCB1B.nanterre.francetelecom.fr>
References: <20140213085149.4433.65554.idtracker@ietfa.amsl.com> <94C682931C08B048B7A8645303FDC9F36F4C31E952@PUEXCB1B.nanterre.francetelecom.fr>
Date: Thu, 13 Feb 2014 11:55:18 -0800
X-Google-Sender-Auth: zXBP_fiB7wyzFa6DHxdDi5sAddo
Message-ID: <CAJE_bqenDbtQ7R+05qqeJ7syfRCa9+QEUw4ojxV2khtnXBcyfw@mail.gmail.com>
Subject: Re: I-D Action: draft-ietf-6man-multicast-addr-arch-update-03.txt
From: 神明達哉 <jinmei@wide.ad.jp>
To: mohamed.boucadair@orange.com
Content-Type: text/plain; charset="ISO-8859-1"
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/fFs9NMkiT-YrQXtTvNyVEM5RGdE
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Feb 2014 19:55:22 -0000

At Thu, 13 Feb 2014 09:59:02 +0100,
<mohamed.boucadair@orange.com> wrote:

> This new version integrates the comments received during the WGLC. The changes are mainly editorial.
>
> Jouni/Tatuya can you please double check the new version and let us know if the modifs solve your concerns? Thank you in advance.

This point in my original comment doesn't seem to be fully addressed:

- In the NEW format of Section 4.2, this sentence may need to be
  revisited:

      In this case, the last 4
      bits of the previously reserved field are interpreted as embedding
      the RP interface ID, as specified in this memo.

In 03, the corresponding part is

   [..] When the
   R-bit is set, the last 4 bits of the previously reserved field are
   interpreted as embedding the RP interface ID, as specified in this memo.

but it doesn't address my concern since the point is "the previously
reserved" can be ambiguous.

I also noticed this (weak) suggestion wasn't adopted:

: Ah, okay.  Maybe it's a distraction, but I'd consider adding a
: "TERMINOLOGY" section or something, where we clarify the point (i.e.,
: the draft generally follows RFC 5952 to represent IPv6 addresses
: except in citation of already published documents).  But I'd leave it
: to you.

If ignoring it was your intent, that's fine.  I'm pointing it out just
in case it's overlooked.

--
JINMEI, Tatuya