Re: [**EXTERNAL**] Re: the race to the bottom problem

Brian E Carpenter <brian.e.carpenter@gmail.com> Sun, 08 November 2020 22:05 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 589A73A0E80 for <ipv6@ietfa.amsl.com>; Sun, 8 Nov 2020 14:05:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, 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 VZr-v-BpYmBP for <ipv6@ietfa.amsl.com>; Sun, 8 Nov 2020 14:05:17 -0800 (PST)
Received: from mail-pl1-x62a.google.com (mail-pl1-x62a.google.com [IPv6:2607:f8b0:4864:20::62a]) (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 F307A3A0E7C for <ipv6@ietf.org>; Sun, 8 Nov 2020 14:05:16 -0800 (PST)
Received: by mail-pl1-x62a.google.com with SMTP id t22so3595558plr.9 for <ipv6@ietf.org>; Sun, 08 Nov 2020 14:05:16 -0800 (PST)
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=urz8QU6yC//x09qp4KLjNaTHAXVmsdlpaLKT/ijI+g4=; b=G8YYQG1ucwWhRqqXSa9+xU9jj/4n++S2WLDXDprIxrclcfien0jH9959zIfhc82bfz BUkd8QIIpzS9QLSAkRq6xPgiztTwX1YP2gYbWs+f0gYkNp1f9PpgtzgCXvUWssA+a5sA p8UaWpjS6w8X+0xOVFSsUAE2A/LxkI9cCTSAhfjlYVNc2uG3ngu1hRaKFW5ADHA6Dust ru117FAX/xMyKyhPvzHHyMrUAyNtN+c+1OVhXshbRr+CgtWjhaXNODn78d4x8SSeKMHJ oAT2NfcTZuibgsep1PJmuUig8m4MtiLjhYx9ARB1to93GL1HdSaNUiugOFpgu16lw/Yr BNvQ==
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=urz8QU6yC//x09qp4KLjNaTHAXVmsdlpaLKT/ijI+g4=; b=SdrqNMAJqnEf4Br8k7dPks8f1S98VfbHbI3QAf49pON9Cl4bshhGRw+JisrCZbORsD bcdeud7ibFxUphrzGaI3KKwjj1Sei71NU4nFNqVE1gA/K/ILUI4eOiTqkACsVOvrg6hp fFmozsb9YascEP7Sl0A/XjlwkdbDC+DKWx20+MvaJd0KM4eoP8B4e+l4DxUQLqsMzvlL TTw85Bffm5Fmx3TvpmHFqcWrJ+EmJVNLX5IIUh8QYqbZtCMaLcwNW5oVWJtC4udHE8PI HnSTVA9ImcF6VbNRGeEfYLHk4qDj52eH4CDMtOm11LD7nSXoTRFTXuFfpZ6dkYdnN1cz BWvQ==
X-Gm-Message-State: AOAM530ROf+YrjMVGUUmA75WW1GNuWI6Y87ijoRyVz3j7W3LkzamjNwx h8L/9evvzDpEMIIIO0uQlE5aTcxolfztHg==
X-Google-Smtp-Source: ABdhPJxGZ75Qrl+nciNC3jtK6QccSomiOKkQy1fjU6B11wBskRis0MTP6R6GdFVjC9GL9DCDvbs7DQ==
X-Received: by 2002:a17:902:ec03:b029:d7:c7c2:145a with SMTP id l3-20020a170902ec03b02900d7c7c2145amr8593871pld.33.1604873116041; Sun, 08 Nov 2020 14:05:16 -0800 (PST)
Received: from [192.168.178.20] ([151.210.130.0]) by smtp.gmail.com with ESMTPSA id f16sm7903574pgk.48.2020.11.08.14.05.13 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 08 Nov 2020 14:05:15 -0800 (PST)
Subject: Re: [**EXTERNAL**] Re: the race to the bottom problem
To: Nick Hilliard <nick@foobar.org>
Cc: 'IPv6 List' <ipv6@ietf.org>
References: <160409741426.1448.16934303750885888002@ietfa.amsl.com> <CABNhwV1zoZpZNjb54rEys4+49H3vpebZW2g9JbO1_58eR+WnQg@mail.gmail.com> <CABNhwV3L7kz=cWu8s3X=djVf4MCwewzbEgx09TWaKzCULCjYUQ@mail.gmail.com> <9A9CE8E7-3552-4FD8-A50E-1BDCA2CB813F@employees.org> <CABNhwV0LxM7EuKo2wNtVacjewsVqdhrmSiVBmB_EL-mqJYdU3A@mail.gmail.com> <CD9F9F09-2CBC-4A72-99C0-4A9A470357ED@employees.org> <9e787ed0-a221-e413-e030-ac2553dffc8e@gmail.com> <a21c9447-730b-e2c0-81f6-46deda57f507@gmail.com> <f4635fa9-45ca-f7ec-40a2-41764e1ca74f@si6networks.com> <905bcc26-a223-53d0-6675-c35579b9a8be@gmail.com> <AAE75F7F-F8DF-4B7F-9C50-3D6C91544997@ciena.com> <2b59b2de-3597-8d35-374d-75e9b10d4d83@gmail.com> <21BC970D-8708-4090-A984-02E6E1305B94@gmail.com> <25099A60-8685-4226-8328-AA87376B62D2@ciena.com> <SN6PR02MB4512023A8418FA3BFA79F412C3EB0@SN6PR02MB4512.namprd02.prod.outlook.com> <8bc14b7a-9b4c-6f03-4e11-4fe02947fd31@gmail.com> <321718b8-41c4-8b85-6c0e-7d7cfeea6784@foobar.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <e1b7bce4-7361-1e81-3496-ea47453d8285@gmail.com>
Date: Mon, 09 Nov 2020 11:05:12 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <321718b8-41c4-8b85-6c0e-7d7cfeea6784@foobar.org>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/oj6El6RYDsZdgS7PpVyFuNXj0dc>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 08 Nov 2020 22:05:18 -0000

On 09-Nov-20 10:45, Nick Hilliard wrote:
> Brian E Carpenter wrote on 08/11/2020 21:35:
>> Just get 3GPP to change its /64 rule in accordance with RFC6177 and I
>> suspect that this entire problem will go away.
> 
> can we shine the light on the other side of this statement?
> 
> Is the IETF beholden to 3GPP to the extent that it feels hidebound to 
> maintain /64 as a generic autoconfiguration boundary for all ipv6 access 
> mechanisms in perpetuity?

That's the wrong question. It's 3GPP that created a problem. We are stuck with it, but that doesn't mean we should quietly concede.

During the RFC4291bis Wars I argued that we should separate the /64 boundary for SLAAC as a parameter, rather than as a constant in the addressing architecture. So no, not in perpetuity, especially if we move out of the 2000::/3 address space. However, the privacy arguments are fairly strong for not going beyond /80, I think, at any time in the future.

   Brian