Re: <draft-ietf-6man-rfc4291bis-09.txt>

神明達哉 <jinmei@wide.ad.jp> Fri, 07 July 2017 17:40 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 0C01F1317B6 for <ipv6@ietfa.amsl.com>; Fri, 7 Jul 2017 10:40:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level:
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 RyxSBdyjBm25 for <ipv6@ietfa.amsl.com>; Fri, 7 Jul 2017 10:40:18 -0700 (PDT)
Received: from mail-qt0-x22b.google.com (mail-qt0-x22b.google.com [IPv6:2607:f8b0:400d:c0d::22b]) (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 68B501317B2 for <ipv6@ietf.org>; Fri, 7 Jul 2017 10:40:18 -0700 (PDT)
Received: by mail-qt0-x22b.google.com with SMTP id r30so32862690qtc.0 for <ipv6@ietf.org>; Fri, 07 Jul 2017 10:40:18 -0700 (PDT)
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=P7v60CupnhGZMMpCzJd3o5oYGwy3n672MSekoNO55UU=; b=UMHLEeFjecOQB+cvtw3+m70IagIV4GtT/oTe+V1P7XOgXeVA8l5X4AI2MV+hjthiKr CWPyHMzjgLtq5vTzVXh8RXQbxxvnVGM2Pb88chswjBV3H946D0i1B48sOaug3TAcifxG CTO5+cBeJvo612hxAImSPrnnAqLX2Q9u55WrJQDUBinUAi7lolv2eLcnNUPYVGqVaO4J hk4xKeoaHy04Qb7V6pRtfCzwxSUAwCN477qjQB819uYr6KuDDFWvi8STBKVxhcEHcYRc MK+hhpoKqOd1Ubhc9NmroRYr2zC7AGz5mcON5NPxIzz4zVG3noe/EaErDmHIXahkiqu/ u3Ag==
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=P7v60CupnhGZMMpCzJd3o5oYGwy3n672MSekoNO55UU=; b=eGWt2GtaU8MdxFvRLqQ3Ci5o8LXLM9Huk6FAIFDYY7uRGiZFrcTp3Onyf+lbk9G5Rb SxPAeGBYXiZyMTMb7THfII37vK9A27FE9IwmX1hzbQ0L2XkfUfMWMYmDkGhrFNsmVWkB HzDGm5WhXrlqZYAO6nnzbeJ3nXvSLIKFZL0B32yUguX9ui7OlV3KMQbxjvHxnIKfESGB T+okzufmY2l61Woz7eOJLE7qVkqJLJ6vVhNO1rtMHZKaZbxQto7sZTN02Pqf+Kz2GH4/ ng23RMabky2TnxZ2zxW2oyKN9n7+kr0zn3taGsAfnvtgU/kL7LMEjbq3LfDBrgRDF1xK HMvg==
X-Gm-Message-State: AKS2vOwGUBCacIP6dhiLKvk5Zsj8XWcbUdfRHsayBjnYfgCmEs/UZ/Wg 3dI3OqOtvusGgcSjA57Dm6JL4iiTVw==
X-Received: by 10.237.43.35 with SMTP id p32mr66029298qtd.86.1499449217116; Fri, 07 Jul 2017 10:40:17 -0700 (PDT)
MIME-Version: 1.0
Sender: jinmei.tatuya@gmail.com
Received: by 10.237.60.44 with HTTP; Fri, 7 Jul 2017 10:40:16 -0700 (PDT)
In-Reply-To: <CAO42Z2xOsa2jb5UqXGoO=tLegfi8Mo0s54S8sfaOKu53gvuamw@mail.gmail.com>
References: <20150804195752.5065.13523.idtracker@ietfa.amsl.com> <5AB14F48-2799-4A86-830D-E8A89CCADAAC@gmail.com> <CAN-Dau0O6hrxmWiWa7yPNDkq7Dz_m1y8wA7bYx_1wYuTpM0ruw@mail.gmail.com> <D691C19D-F3D8-4487-8641-DBA7A8DF8A3E@gmail.com> <CAN-Dau39LbQ4Lpx-ULxUuSmeL+zgQsRU5861SUvr6vesB5-uUw@mail.gmail.com> <CAO42Z2xOsa2jb5UqXGoO=tLegfi8Mo0s54S8sfaOKu53gvuamw@mail.gmail.com>
From: 神明達哉 <jinmei@wide.ad.jp>
Date: Fri, 07 Jul 2017 10:40:16 -0700
X-Google-Sender-Auth: 6P5avEhjMQ3euQzRMm-aLucEJe8
Message-ID: <CAJE_bqeSr9c0nzsxdrxspqDYspyrhBHpkYHN9teaTD1O-qTUZQ@mail.gmail.com>
Subject: Re: <draft-ietf-6man-rfc4291bis-09.txt>
To: Mark Smith <markzzzsmith@gmail.com>
Cc: David Farmer <farmer@umn.edu>, IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/RfxI5JqdVkoUDODkK9c4dAcFA9U>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 07 Jul 2017 17:40:20 -0000

At Fri, 7 Jul 2017 10:09:46 +1000,
Mark Smith <markzzzsmith@gmail.com> wrote:

> > As long as the others that who were insisting that the statement "IIDs MUST
> > be 64" means that subnets must be 64 bits for both address generation and
> > on-link determination are satisfied that this is not the case for on-link
> > determination based on what has been added to section 2.1, then I could live
> > without this.
>
> I'm confused by this and have been on the occasions it has been
> discussed. I also don't understand why it matters and is related to
> the on-link property of a subnet prefix.
[...]
> So to me an "on-link prefix" is a subnet-prefix that hosts will
> attempt to send directly to across the link they're attached to,
> indicated to the host by RA PIOs, ICMP redirects or manual
> configuration on the host (per RFC5942). What you and others are
> describing as an "on-link prefix" sounds like something different to
> that.

I can't speak for others, but I believe David's understanding of
"on-link prefix" is consistent with yours.  My interpretation of his
comment is that the current (09) text of rfc4291bis could be
misunderstood regarding this point as follows:

A. According to Section 2.4.1. IIDs are 64 bit long (with some exceptions)
B. Based on this, and according to the format of Section 2.4, subnet
   prefixes are also 64 bit long (with some exceptions)
C. Some readers might jump to the conclusion from A and B that this
   64-bit subnet prefix is used by hosts "to send directly to across
   the link they're attached to", i.e., this prefix is used as an
   "on-link prefix".  Of course, this conclusion is wrong, not least
   as clarified in RFC5942.

Some people (probably including you) don't see the possibility of this
misunderstanding, and some others still think the misunderstanding is
possible.  Personally, I tend to agree with the latter group of people
- I still feel the current text is not crystal clear and could be
misunderstood by fresh readers.  On the other hand I also tend to
agree with Brian in that the wordsmith period of this doc is now over
(and it's more productive to complete this task as long as we can
agree on the high-level content).  So I'd rather move on at this
point.

--
JINMEI, Tatuya