Re: RFC6085 update to rfc2464bis

神明達哉 <jinmei@wide.ad.jp> Tue, 10 January 2017 19:22 UTC

Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 330B612956E for <ipv6@ietfa.amsl.com>; Tue, 10 Jan 2017 11:22:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 rLWzds6Q-7vF for <ipv6@ietfa.amsl.com>; Tue, 10 Jan 2017 11:22:53 -0800 (PST)
Received: from mail-qk0-x22f.google.com (mail-qk0-x22f.google.com [IPv6:2607:f8b0:400d:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5FABE12952C for <ipv6@ietf.org>; Tue, 10 Jan 2017 11:22:53 -0800 (PST)
Received: by mail-qk0-x22f.google.com with SMTP id 11so86800736qkl.3 for <ipv6@ietf.org>; Tue, 10 Jan 2017 11:22:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=ehz/ES9osGB+HxelEGm8p8iL4P2P5LdNbl++/oOT5cI=; b=iz4ZrFaOAUiRyKpuaD7dNhWT3myT4aCGg6JoLjElZug1YiP3gk/JN5y2EZlA9m13vN cFCPRwfV2nnUBWPyLdiSE25TzuSZbm+TiiW1MRGNNR8UkLG2aMmzO8J68AgUFmAJL98c Hpj3yEAREil5lDkYYKil73uDzNykj+EHeJu3g4RO6KF89FoWGvO+RqjhVTGrv5MKNGZC jip00Iotrgh7Is/HHCplZT6gdJQvMQes2jpYuqH8AW6KZSLn2mVmRG7B8QgsovbaEm0X Rjp0JbQG4Jc0jbmMYG+F19z2OaE+7iwz3zf1hfz4uI2EjmUudpRNKo7Jx/WO/9ONXcae OsOw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=ehz/ES9osGB+HxelEGm8p8iL4P2P5LdNbl++/oOT5cI=; b=uU9xRgmMncwB9EKlDncKu7Dc2Y+cuuDsmpGhHNxKsYRiq39iNcSPAbIwX3V1MVjc29 dfGfpV/lBYp0k9W60GQe/0qN5D9xfwNFeNI+nyz375U4Ee6MB03J70tjFh+xxA2Z7zYz xfWZbr9PYxThTZo8Bd+6NxuypanIew/yP9beW9rHD81tS8d1Avqh5rpwfEndO+ylgpCf fll4F5QclYbu9wC4zcX+KGohHYcmz51dKPpZ9PMQ1ALzHrY0URUs0HcbzZ83VZkB29e2 Mp1XsLIU6CnzZgUXIIR1d0BkcDZdckXgdvqo9TCIRb8RdixNSzIUnYtEtlbaPLk8e2xA LjLQ==
X-Gm-Message-State: AIkVDXLu4eVaBkFJR1gvCJ7hmThLecM8WbfzkFAmWT5hH2jZKsg5ppOwcT5iTDyyaHUPMeMALXXGrit5iBYqMA==
X-Received: by 10.55.161.11 with SMTP id k11mr4467449qke.149.1484076172484; Tue, 10 Jan 2017 11:22:52 -0800 (PST)
MIME-Version: 1.0
Sender: jinmei.tatuya@gmail.com
Received: by 10.237.60.29 with HTTP; Tue, 10 Jan 2017 11:22:52 -0800 (PST)
In-Reply-To: <CAJE_bqc4LBxeJFupiG=P0WiXqmM2Y-pyDN9skggGPd9c_N=AbQ@mail.gmail.com>
References: <C2C9A241-BBE1-4DC1-BA9D-B6D20EF75FD6@gmail.com> <CAJE_bqc4LBxeJFupiG=P0WiXqmM2Y-pyDN9skggGPd9c_N=AbQ@mail.gmail.com>
From: 神明達哉 <jinmei@wide.ad.jp>
Date: Tue, 10 Jan 2017 11:22:52 -0800
X-Google-Sender-Auth: XuB1J_e5QFfQn7lALM7jbZNfP90
Message-ID: <CAJE_bqeGO-8TJkdCDS-tChGCsLYH8ve=pySXBcSFZG9AFcK6CQ@mail.gmail.com>
Subject: Re: RFC6085 update to rfc2464bis
To: Bob Hinden <bob.hinden@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/gNyeDToi15OvyiskYbrU4K9ua6Q>
Cc: IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 10 Jan 2017 19:22:55 -0000

On Tue, Jan 10, 2017 at 9:26 AM <jinmei@wide.ad.jp> wrote:

>>    An IPv6 multicast packet may also be mapped to a unicast Ethernet
>>    Link layer address as defined in Section 6.
>
> I think it's more helpful to refer to RFC6085 explicitly here.
> Otherwise the proposed text looks good to me.

On re-reading it more closely, I wonder whether "as defined in Section
6" may not be very appropriate.  RFC6085 intentionally left the
mapping open:

   [...]  The determination of the unicast Ethernet link-layer
   address and the construction of the outgoing IPv6 packet are out of
   scope for this document.

but I suspect it doesn't really intend to perform link-layer address
resolution using ND (which is in my understanding what "Section 6"
talks about) to determine the unicast Ethernet address.  In fact, the
address resolution itself uses a multicast IPv6 address, which is
derived from the target unicast IPv6 address.  So it would be a kind
of circular definition.

So it's probably even better to just refer to the RFC instead of
Section 6:

    An IPv6 multicast packet may also be mapped to a unicast Ethernet
    Link layer address as noted in [RFC6085].

And, for that matter, this text of Section 6 of rfc2464bis-01 now
looks a bit awkward to me:

   The procedure for mapping IPv6 unicast addresses into Ethernet link-
   layer addresses is described in [DISC].

On reading both Sections 6 and 7, this "the procedure for mapping"
could read some static mapping whereas it should actually refer to
dynamic link-layer address resolution.

I suggest revising the first paragraph from:

   The procedure for mapping IPv6 unicast addresses into Ethernet link-
   layer addresses is described in [DISC].  The Source/Target Link-layer
   Address option has the following form when the link layer is
   Ethernet.

to:

   When the link layer is Ethernet, the Ethernet address for an IPv6
   unicast address is resolved using the address resolution protocol
   as defined in [DISC].  The Source/Target Link-layer Address option
   used in that protocol has the following form.

--
JINMEI, Tatuya