[IPv6]Re: Working Group Last Call for <draft-ietf-6man-pio-pflag>

Lorenzo Colitti <lorenzo@google.com> Fri, 31 May 2024 04:21 UTC

Return-Path: <lorenzo@google.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 B1F24C169433 for <ipv6@ietfa.amsl.com>; Thu, 30 May 2024 21:21:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.599
X-Spam-Level:
X-Spam-Status: No, score=-17.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RSadNz5o9mhC for <ipv6@ietfa.amsl.com>; Thu, 30 May 2024 21:21:40 -0700 (PDT)
Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 33FB6C151079 for <ipv6@ietf.org>; Thu, 30 May 2024 21:21:40 -0700 (PDT)
Received: by mail-ed1-x536.google.com with SMTP id 4fb4d7f45d1cf-57a033c2e8eso578946a12.3 for <ipv6@ietf.org>; Thu, 30 May 2024 21:21:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20230601; t=1717129298; x=1717734098; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=v/ZSrY25tSL+tXq1HAxtHWHgy8S1qQT953lVQShazQE=; b=XPTndXT+m5XASvGH2fDQORqQEDjoGLFvzVTLUa2Sdc+3CB2dl60+rpDfJCL9ufDb0q qDuR2dGh3uirshnHFoLcLiyQtgAcMyBuhWQHsZ/Q70TS53Td+kbn8aSWTU+r30aNEA0P jILrdJOENS+zUfaATPIXNOBah2531aePUFaT4Weo5MC8nMpLUdnvsUZn9GFmxAShZyiH xhYrwjg9n7ZEEkqdZkfNJxIOYei1P9AH+hnxqLFXaVDAzEJuHivqRC62gxaW7wiAKLYw k2TtTO4zTZYJf6ZV7qvEuUD9miZLzwPUh8K2qhTOH00LDuKmDBHrLuhbcC/8pLdjhvlk 1P1Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1717129298; x=1717734098; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=v/ZSrY25tSL+tXq1HAxtHWHgy8S1qQT953lVQShazQE=; b=X1FYPlV56OIp0QrOJ2dMR7g9+8AWX9EmJ4oFIozRRhBWWlToV6ctcqX+RYYyPvIX8+ fm4QB66Yxzl7MNZEnUCagZc3JP3/Dss7pTdINBu3Q/9kFC/L5RKeYpkznr+zoaEs0FuM qeOs+gRuqN/IGziOzKYSpDW6UICy0qpWUWBdF0MmkPygYYv9UdcEYGo67KHKM+zoaDD/ vkFtdm+O40ri5dUvLFKw1BG8AGOMcd4+UGn2g+AyNxHHcOJzTUavuoTr5LlzLiH9UxGo IbDZCuZJTKOkb4IhUnfE3yZ4g+N5IpSHNADQHtxijtZ59nID9SyDNt120nGiEZSqIcHG W6Ug==
X-Forwarded-Encrypted: i=1; AJvYcCVVcIHiZhvgVllikVLKU3ICKrsMTZ9twUVom42l4Vi1hC1lhUQ+hNPDEYHsR0HDZKu2dh+LPZSKRxdMOBAM
X-Gm-Message-State: AOJu0YxFRjhgg5nYuq4YfDuF2W0AKxdiCKf8f3SRo3AHO5co3Q0AspnL 8jNwACxQXY8GN8//xlxrng/KH+85sx03AGmpwaINCWpx3yw2VyZ2CRPN0AsdGZ55hInANJ0tABU njOnVO7um0V/Kr0kNzxPVjwdmrc8M7KuYJEemkUv9gon0Rg0CWURN
X-Google-Smtp-Source: AGHT+IFU4sNE9pFBUSjumaXAn6QzJLu/4H6YJoBKemO8C1zuYo6LinBrn63LNQkN+uVrRrG7Z4AZey9dd8Wuj1XIFGQ=
X-Received: by 2002:a17:906:a2da:b0:a68:44ed:613d with SMTP id a640c23a62f3a-a6844ed64dcmr31096866b.14.1717129298176; Thu, 30 May 2024 21:21:38 -0700 (PDT)
MIME-Version: 1.0
References: <18236.1717011844@obiwan.sandelman.ca> <2AD87DE1-075E-45E7-A682-8042F04EF59A@employees.org> <89dbde8c-82c9-4a2e-9cff-8d4fd2d8fbe6@gmail.com> <9E7BEA1C-4597-4142-A3AB-57211C436197@employees.org> <CAKD1Yr0iR+RZHvuquCGYfntiD+K7-PdkvGJzHLx1PLrFqJ=Z4Q@mail.gmail.com> <47BF97B8-2BEE-47CC-A965-C6BB112990AB@employees.org> <4bcfcd71-d295-433d-813f-1183c7da3cf3@gmail.com>
In-Reply-To: <4bcfcd71-d295-433d-813f-1183c7da3cf3@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 31 May 2024 13:21:22 +0900
Message-ID: <CAKD1Yr1CL_Jw4O-iETF6T1v8EL_Lj-fMi6EV=3MgPhN+M2tc8w@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000da90c80619b851ef"
Message-ID-Hash: 4GIST2SJFN6YFEFHWQBA7NCKITITFF4F
X-Message-ID-Hash: 4GIST2SJFN6YFEFHWQBA7NCKITITFF4F
X-MailFrom: lorenzo@google.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ipv6.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: 6man WG <ipv6@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [IPv6]Re: Working Group Last Call for <draft-ietf-6man-pio-pflag>
List-Id: "IPv6 Maintenance Working Group (6man)" <ipv6.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/-j_4iF-evMoPEbDOmaN-f7DJM5I>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Owner: <mailto:ipv6-owner@ietf.org>
List-Post: <mailto:ipv6@ietf.org>
List-Subscribe: <mailto:ipv6-join@ietf.org>
List-Unsubscribe: <mailto:ipv6-leave@ietf.org>

On Fri, May 31, 2024 at 12:11 PM Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> Neither of these arguments is very sound, in my view. However, I'd feel
> more at ease with pd-per-device if it *also* proposed to extend subnet
> prefixes to, say, /80 (with all the changes to IP-over-foo documents that
> would imply).


Honest question: can you explain why you think that would be better? Why is
it OK for your phone to have a /64 when it's connected to a mobile network,
but *not* OK for your phone to have a /64 when it's connected to your
enterprise wifi? Why are you so concerned about that, even though
presumably you think /64 per device in mobile networks was a good thing?

I get that /64 makes you uncomfortable (presumably due to concerns about
address wastage?) but is there actually a rational concern here about IPv6
address space usage? If there is, should we start thinking about changing
cellular networks to use prefixes longer than /64? And if not, then why
should other types of networks be more constrained?

More in general, this was debated at length when pd-per-device was being
discussed. I don't think anyone claimed (or at least, convincingly claimed)
that /64 per device would use too much space. IIRC the strongest arguments
against /64 per device were:

   1. Some RIRs at the time didn't have policies that allowed sites to get
   enough space.
   2. There were networks that had already written addressing plans and
   gotten space from RIRs and would need to renumber.

For the policy issue, I believe that only RIR was RIPE and it was fixed by
a policy change that was already in flight (to address another need) while
the debate was hapening. As for networks that had already gotten space and
would have needed to renumber, the rough consensus ended up being that
those networks could simply not adopt the model.

Also note, switching from /64 to /80 will *not* obviate the need for a P
bit. As soon as /80 is widely supported it will become the new
lowest-common-denominator. Each leaf network will only have /80, and we'll
still need a way to determine whether the network can provide each device
with its own prefix or not.

In general I don't object to trying to change the IPv6 subnet prefix length
from /64 to /80, but it's definitely not an easy change, either in terms of
backwards compatibility, or in terms of getting consensus on, or in terms
of avoiding a race to the bottom.

Cheers,
Lorenzo