Re: I-D Action: draft-carpenter-6man-lap-00.txt

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 14 June 2018 03:36 UTC

Return-Path: <brian.e.carpenter@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 66AC2130DC1 for <ipv6@ietfa.amsl.com>; Wed, 13 Jun 2018 20:36:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 sLprhsHT_KlU for <ipv6@ietfa.amsl.com>; Wed, 13 Jun 2018 20:36:25 -0700 (PDT)
Received: from mail-pf0-x236.google.com (mail-pf0-x236.google.com [IPv6:2607:f8b0:400e:c00::236]) (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 C972612D7F8 for <ipv6@ietf.org>; Wed, 13 Jun 2018 20:36:25 -0700 (PDT)
Received: by mail-pf0-x236.google.com with SMTP id a22-v6so2486472pfo.12 for <ipv6@ietf.org>; Wed, 13 Jun 2018 20:36:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=bE4cgH+uE34VApPwi0iJo3xn5A5Nyqp/ftf671y2RmI=; b=NJt9hqfwQURM9b5JpstztN4c2Ao3OSGVYFzjAfj7wkmJ9Y1Ngbec88RUQ+4uCe4ZUB 0fBgiiijOZ37ZE25RwHNs5MYU1f5/nrQ1Rzq3Z3c1fpvUT93wO86R33mXFJBBUAoaU25 DYTvp0p/Al7sdGPMVbQkXi8cmXoZya0wGjey2c/RbNfE4TJboxyswWWOF/x9jHXLfz/e 2YDHOnn0rV1hzBgNrewi86MwPPHlvVoVxLRw2ykgvtxktUQpIkUMqTjDso/ylgyHLof6 yGb+uOcCKxAT/Sr1O7OroVCeOQsYfPtBoo/da9XzvIDMocw7Y+wdVJGx8E1Z3u4sUxUS DFtg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=bE4cgH+uE34VApPwi0iJo3xn5A5Nyqp/ftf671y2RmI=; b=nfjL1p++653Ofku7Td4lvhdWt2WzVqPFGopomh3JzbVxVylQ4OznGaYmhrw8TvGt3D gwPjL6cixl6MGPS+nGSeIMRCf7bv+HDyc0VcySxApk+azc6A7TaYkOSu6ZVwSWeXHQ3A Wl/iKE9I7yX0ys99j4VNZQDJv4a0CKWqRxFmggiRRkX+E1V8phzY16Ru1q/+8RsbtDLc wOuOqaH1wLDE/Q2UN3NTCzoSwxW1caCEoEPv6uxhr0LX4sv969fQLCX9mNMmha63Dl7P 5CR45KrVuhe5Upkjrcf0XnoH2AhO6+fAqWPbR0Wj+fkHaM7iaDzHbhe9ZiFqGIfyouqg rvEg==
X-Gm-Message-State: APt69E3C2fNuGHztOq12BUij6VqXPD5Mk5brE4tqGtohBPXH16Pzyvw1 1TIynKb/SK+32cejducfeYkcKQ==
X-Google-Smtp-Source: ADUXVKL72jPa2v1aKZqmT0/ym0AaGK/6Pl3kfp7royLLPJSOLiJ7T7aPG4skEolHeHpzO0naeQIRtQ==
X-Received: by 2002:a65:44c8:: with SMTP id g8-v6mr768515pgs.356.1528947385064; Wed, 13 Jun 2018 20:36:25 -0700 (PDT)
Received: from [192.168.178.21] ([118.148.121.80]) by smtp.gmail.com with ESMTPSA id 82-v6sm6637068pft.74.2018.06.13.20.36.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Jun 2018 20:36:24 -0700 (PDT)
Subject: Re: I-D Action: draft-carpenter-6man-lap-00.txt
To: Lorenzo Colitti <lorenzo@google.com>
Cc: Mark Smith <markzzzsmith@gmail.com>, IETF IPv6 Mailing List <ipv6@ietf.org>
References: <152885615366.31310.5115931223138267905@ietfa.amsl.com> <f7c1a7a2-5070-ce65-3086-f3a47a822d6a@gmail.com> <CAO42Z2yxNZKe4pMynLwCgVT4J3LgX8jKx-izwsDBKF_+rn4Hbw@mail.gmail.com> <c532ed66-2387-932f-ba51-d926b073fc7f@gmail.com> <CAKD1Yr1nX=VyFLZgym87EJ+z0an5k3o3ho-6MPynWqySsZ++VA@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <97c3e851-c56f-d783-d764-58cbd08ccf74@gmail.com>
Date: Thu, 14 Jun 2018 15:36:27 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr1nX=VyFLZgym87EJ+z0an5k3o3ho-6MPynWqySsZ++VA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/kgKTmquURbgP2ORPZUX95zF1lNo>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.26
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: Thu, 14 Jun 2018 03:36:28 -0000

On 14/06/2018 14:00, Lorenzo Colitti wrote:
> On Thu, Jun 14, 2018 at 10:48 AM Brian E Carpenter <
> brian.e.carpenter@gmail.com> wrote:
> 
>> I think we can discuss the "race to the bottom" and privacy arguments
>> rationally with this terminology.
>>
> 
> If the problem here is that some people think that changing the acceptable
> prefix length will cause a race to the bottom, then how does creating a
> name help? Just so that have a name to use to track progress in the race?

Two names, adding Mark Smith's SAID suggestion. And yes, having a name or
names that express that there's a decision involved (is this acceptable?)
is IMHO a way to track progress in the discussion as well as in deployment.
It's a very mild form of a thinking tool (as per Daniel Kahneman).

If somebody wants to deploy subnets with a maximum of (say) 256 IoT
nodes, and doesn't care about entropy in the IIDs because of privacy
aspects of the specific scenario, why should we care if they choose
a SAID of 8 bits?

(Why might that be a good thing? Because it would allow you to express
addresses within the subnet in 8 bits. For a constrained IoT node that might
be very important.)

That's the kind of discussion we can have with such terminology.
If we can't have that discussion, we're throwing away valuable
flexibility for the universal deployment of IPv6.

I don't think anybody is arguing against LAP=64, SAID=64 as the
general default.

    Brian