Re: draft-bourbaki-6man-classless-ipv6-00

神明達哉 <jinmei@wide.ad.jp> Mon, 12 June 2017 17:53 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 0CB41129564 for <ipv6@ietfa.amsl.com>; Mon, 12 Jun 2017 10:53:46 -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 AEq1M5t9z7lp for <ipv6@ietfa.amsl.com>; Mon, 12 Jun 2017 10:53:44 -0700 (PDT)
Received: from mail-qt0-x230.google.com (mail-qt0-x230.google.com [IPv6:2607:f8b0:400d:c0d::230]) (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 AD39512952E for <ipv6@ietf.org>; Mon, 12 Jun 2017 10:53:44 -0700 (PDT)
Received: by mail-qt0-x230.google.com with SMTP id u19so135783923qta.3 for <ipv6@ietf.org>; Mon, 12 Jun 2017 10:53:44 -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=2sdxKC6f1Xs3J1hLgftpRUiXb0lbP6Q4A35IvYxhQSE=; b=uRB+bz3ijtA22XSuPZfisIXi9985OLIXQwhvCZsWJvpM/blLGnV3Tv0IgpBAif+VIJ YQn5YTTgNXZDU4/iewahZD+bVBMPDB/5PwMetNPk+xHcyxSxhHfzYe86ZedG93LEwcYP ldAV2Tj9ZWaAOFS7M/Ax892B70Nd7u7162jemHTbMP6zuvz6iGBVR8op2m20PUIlqJkR 5OHDHOH9i2t9VJBc9bIyNrXKVnnXWT0suNvQdkIgNeF6yfOB/QPveEIuFPl22tLMsJmQ IZBz4vL18hmUwrjSWnq0ejNxL0SNC6tDhjpQnKGl38AibTWdWKrY3olCejqqfuQ1yZQ0 PZtg==
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=2sdxKC6f1Xs3J1hLgftpRUiXb0lbP6Q4A35IvYxhQSE=; b=lpMyHOFt18GyrSXXwzFfYhwD3MTlLAGB4XNqy5u5FPgCzPU0JX+nHACNZrFVT4yDse B2/AVpefeBLhbvM8HwNsPTwEgRBQDsZ+oDjDuP1jpLj7OyuEIp1DPbc9zKvbbHblD1vK XP+okfY/DThWcYX6OWJgqDrvuY858dfSFw5Cul/gLTJ3/fvn8XUnvHTkPPXur7AhDBzR ziVF19Fvm9lItC5GczfsDGL0XsjpOLAC2vEGta/geEMOc4tlx+pH+UW2QlqaGjDyQZ8Q x40ASiTh8kX9C0D50xWrSaHoTbYli+S+bA7lMSDRePTtLVMj73DikuV3avGCPT9BnZ2F uCIQ==
X-Gm-Message-State: AKS2vOyZ9PTtNg7dIHBNsKcM+5bY7lDmJL8BJ4wfeTQic8azczt5XS+i 3IYhXxnDnotIMtvdcxVeakdBIgSmVQ==
X-Received: by 10.200.57.228 with SMTP id v91mr15544180qte.116.1497290023755; Mon, 12 Jun 2017 10:53:43 -0700 (PDT)
MIME-Version: 1.0
Sender: jinmei.tatuya@gmail.com
Received: by 10.237.60.53 with HTTP; Mon, 12 Jun 2017 10:53:42 -0700 (PDT)
In-Reply-To: <DD7E7E11-7561-466E-91A1-787B72230B3D@gmail.com>
References: <20170602141112.x64nleqclygz7dwd@Vurt.local> <20170602141259.GD30896@gir.theapt.org> <CAKD1Yr0DtQYvCYLQexhXe_nhb5rjeyhnB4bCveqyO5Xbuwdg1A@mail.gmail.com> <CAKFn1SEdjhsQ3tKPZdbdfF4ArDzw-FZfjQT68gV55Fc-5vzBvw@mail.gmail.com> <CAKD1Yr3ppM0UF8HoN8PgS7F0iEmK26ebiuJK=tkAdZnuLWpkZg@mail.gmail.com> <CAKFn1SHASt34ihJmGN0iRFQQzLTMspZfxXHgBjBatXXcRYF4cw@mail.gmail.com> <20170604093119.nt733rb3ymmjssww@Vurt.local> <m1dHTLx-0000DcC@stereo.hq.phicoh.net> <CAKD1Yr0ZZwRar6D-2bkXBKPYehqqW99+BMtDOjyovR8WDXKzxw@mail.gmail.com> <CAD6AjGTjikAWutcenW8qn7OW8kPM9c_x_yDUy5vQxJmXKL85dg@mail.gmail.com> <91c3c0f4-eb8b-cdf7-b9c9-7d1eecb7fe64@gmail.com> <CAKD1Yr0_WR_TB+OC0U1Qt2h6WzUp9EGvrqC1ZKW2mwFeBd3bCQ@mail.gmail.com> <4021a559-5b6d-b3fb-19cd-afbe9041e8f2@gmail.com> <CAKD1Yr1wmY3O9Uxe=KRxzCidpyhn3e0zSnikY0K6LK9ue4OzwA@mail.gmail.com> <71c7286c-0e86-5dbe-f9c2-7d473d1de728@gmail.com> <CAKD1Yr3SUOPd+5H66WPc2ikxauVWVG2ZBjFTHoFOQPCEYTBdiA@mail.gmail.com> <4B891D4C-96E7-42F4-9A38-EBA7B3466BE0@employees.org> <CAN-Dau38xD0oZ-0xe3K=VYgwAU25z6ySp7BgMj8HQ2iG96AoRA@mail.gmail.com> <DD7E7E11-7561-466E-91A1-787B72230B3D@gmail.com>
From: 神明達哉 <jinmei@wide.ad.jp>
Date: Mon, 12 Jun 2017 10:53:42 -0700
X-Google-Sender-Auth: 8MK-Pw47CmTWG-PrHWbo6EyoPkg
Message-ID: <CAJE_bqdRrTZoA1cS_xi6oujPyJFBW+ydgdLWjWac4g+yqe6FEw@mail.gmail.com>
Subject: Re: draft-bourbaki-6man-classless-ipv6-00
To: Fred Baker <fredbaker.ietf@gmail.com>
Cc: David Farmer <farmer@umn.edu>, 6man WG <ipv6@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/kS4lf8ZN4n-nUvaLRI5kKENJGzE>
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: Mon, 12 Jun 2017 17:53:46 -0000

At Sat, 10 Jun 2017 13:44:34 -0700,
Fred Baker <fredbaker.ietf@gmail.com> wrote:

> The only place it makes sense to me to talk about a specific length
> for an IID is with SLAAC; if a network is allocating addresses
> manually or using DHCP, they are in control and can do whatever they
> like - I dare you to stop them. But the IID is the part that is
> never a prefix - the last N bits of a /128, and by convention 64
> bits.

I'm afraid this is not really a correct description of the current
specification (if you're actually proposing to change the current
specifications on this, it would be more helpful if you could clarify
it's a proposal, not an explanation of the current spec).  It's
subtle, but I suspect this subtlety is part of the controversy we've
seen that should actually be unnecessary to have.

If the address is manually configured or configured using DHCPv6 with
some "prefix", that prefix is actually an on-link prefix and has
nothing to do with IID.  The IID length would still be defined by the
link-type specification, and since that should be consistent with the
addressing architecture, it *must* be 64 bits in practice.  But that
doesn't matter for actual operation - when the address is configured
manually or using DHCPv6, only on-link prefix matters in the actual
host behavior, and it can have an arbitrary length.

--
JINMEI, Tatuya