Re: [IPv6] I-D Action: draft-ietf-6man-rfc6724-update-07.txt

David Farmer <farmer@umn.edu> Fri, 05 April 2024 21:25 UTC

Return-Path: <farmer@umn.edu>
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 71003C151531 for <ipv6@ietfa.amsl.com>; Fri, 5 Apr 2024 14:25:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.396
X-Spam-Level:
X-Spam-Status: No, score=-4.396 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umn.edu
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 VrLV5RqmZW83 for <ipv6@ietfa.amsl.com>; Fri, 5 Apr 2024 14:25:40 -0700 (PDT)
Received: from mta-p6.oit.umn.edu (mta-p6.oit.umn.edu [134.84.196.206]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A542CC151097 for <ipv6@ietf.org>; Fri, 5 Apr 2024 14:25:39 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by mta-p6.oit.umn.edu (Postfix) with ESMTP id 4VBBNf6Krdz9wBNG for <ipv6@ietf.org>; Fri, 5 Apr 2024 21:25:38 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p6.oit.umn.edu ([127.0.0.1]) by localhost (mta-p6.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mJCFTkNYwEgZ for <ipv6@ietf.org>; Fri, 5 Apr 2024 16:25:38 -0500 (CDT)
Received: from mail-wr1-f70.google.com (mail-wr1-f70.google.com [209.85.221.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p6.oit.umn.edu (Postfix) with ESMTPS id 4VBBNf3LXrz9wBNC for <ipv6@ietf.org>; Fri, 5 Apr 2024 16:25:38 -0500 (CDT)
DMARC-Filter: OpenDMARC Filter v1.3.2 mta-p6.oit.umn.edu 4VBBNf3LXrz9wBNC
DKIM-Filter: OpenDKIM Filter v2.11.0 mta-p6.oit.umn.edu 4VBBNf3LXrz9wBNC
Received: by mail-wr1-f70.google.com with SMTP id ffacd0b85a97d-33ec4fb1a83so1093927f8f.2 for <ipv6@ietf.org>; Fri, 05 Apr 2024 14:25:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; t=1712352337; x=1712957137; 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=obprM8kw9f6/s62IkkHR7WTt+FCCEgaFL7gENgtgTKI=; b=MGS5xX7q10M63zSU//2jVAHlQM4XfQrlNtB59DOuYVpIRuJWNbiBU94wMJyV30ZGdy A7WVjFuFz/RXzPTKYOEpX5/qOlWrcsH3GCt7lKN6z0uQpGzTJ0SgCVUdd3Ol43DXbKUP XptQek8as+1a7idgum5nYD8bvkJDdoV2kO/mSfKJ5bsnhntV7g5Lp4TKTJcilSKT/KP4 hvtC+PqZ1ZUg1at6YMs9CzM/E8WzlwKIN1e5OPggapNTwH8Zm4JhgIgm1oAx1ZcwIUa0 +B6sGy7NX4P6JRJ6yVoK7iSFUx3NOLqqzGMWJLGDu5YNVOwImt15LG72G9d8zC2e6Qjm Pu4w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712352337; x=1712957137; 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=obprM8kw9f6/s62IkkHR7WTt+FCCEgaFL7gENgtgTKI=; b=XHCrv4GJXxdnTAj69QKO4kLB2pltezhCeAt8EaDX7nU/zeNAdTM0HHjrhRHU6YNLyC ONAQaJfuXxo7e7+E4M1VTqgrArnUd6KE1CilAmTjkxrfARqYhyLffCz/hpmasWb8eWxd p9L9BTxT6aP5vc0IMjqUhlagKIcXE6yAkHbQ8SqEOMR8nXGgj8adfPZ4UU2nUN6k38S3 3xffoEyS7jyj+5AJhmYKKkT9oSliq+GkENlePYar79VG4+r7P2/iD0SuwveKnNmMbPtL y6/FVU1ei69VUuqVNZlQBbDlw2ky+JSBpdD0vkbitgtVoZeWD6KpWPQni5g9zNh5CQ2m WJHQ==
X-Forwarded-Encrypted: i=1; AJvYcCWFhk0e/K6KBlqLqZKdXpYVkP/DJW6xVi+9bJrbhHzhiIdSpwmZAS1BFXOoueOdFA738T7TkW6qd9LH9lQy
X-Gm-Message-State: AOJu0YzuKxtEhkOqt1Tqv4RXq3/Nz9NH4fvRRE8TrCHSo+gArBThYFFA QxTHW7Ov8ixQS+Z653n84BRBO2hqB3mXiwbnmP5/osv8ii2ztogU8PrH7IKUBdNQot5+EMVR0zx eB9ZR6Rb6fn+3kEuhtAXMkzmi3xini+eIN1IAxuD4wXW8cnioSm0CTfQgzWMm35kjiwf1ZCD/h/ Ky/mptdDQboo7zTy8bpY6OUrzm8Wpc
X-Received: by 2002:adf:fac6:0:b0:33e:7aff:a3a0 with SMTP id a6-20020adffac6000000b0033e7affa3a0mr1519494wrs.71.1712352336786; Fri, 05 Apr 2024 14:25:36 -0700 (PDT)
X-Google-Smtp-Source: AGHT+IH/bnVveY1U56xZHOrEfd0ss9hQguYciOgoXri1GMWUZC6jWDNgPxcBff8vaVnck9ixJvHHURhpcO/MaMkXn0I=
X-Received: by 2002:adf:fac6:0:b0:33e:7aff:a3a0 with SMTP id a6-20020adffac6000000b0033e7affa3a0mr1519483wrs.71.1712352336369; Fri, 05 Apr 2024 14:25:36 -0700 (PDT)
MIME-Version: 1.0
References: <171225751716.18509.12521562864612372012@ietfa.amsl.com> <a4063219-1cd5-4e06-bf42-b0ffebd2b419@gmail.com> <CAN-Dau3VrqfRR+4Eee7TOS1L2RAWbfWv87_QJH_u5gzVU1Av7g@mail.gmail.com> <CAPt1N1nq9V4H9kq+hf4YO-T6OUdYMv8Vmsd3Vpqf264Jm7mrKg@mail.gmail.com> <CAN-Dau3nh50j6qB2WryL1tM2ktwSntDKX72v8O-_fzNRnu_C4Q@mail.gmail.com> <a1a1d964-949c-48e4-bb6c-462a81402871@gmail.com> <CAN-Dau1izfpYR=jH2DbRmf+h+LWOmACQxa-WeuW_o0ABbsJmPw@mail.gmail.com> <992c1d6d-9143-419d-bf9a-dd6419df962f@gmail.com>
In-Reply-To: <992c1d6d-9143-419d-bf9a-dd6419df962f@gmail.com>
From: David Farmer <farmer@umn.edu>
Date: Fri, 05 Apr 2024 16:25:20 -0500
Message-ID: <CAN-Dau2MHVYO_EpcQq5+gw-UhGVtDs9rCN6d_h_k7ydPFazKNQ@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Ted Lemon <mellon@fugue.com>, ipv6@ietf.org
Content-Type: multipart/alternative; boundary="000000000000bd75e70615601883"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/w7fXYTxnr_-3AieJrx97x0vKIpU>
Subject: Re: [IPv6] I-D Action: draft-ietf-6man-rfc6724-update-07.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.39
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, 05 Apr 2024 21:25:45 -0000

On Fri, Apr 5, 2024 at 3:55 PM Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 06-Apr-24 09:15, David Farmer wrote:
> > On Fri, Apr 5, 2024 at 2:37 PM Brian E Carpenter <
> brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> wrote:
> >
> >     On 06-Apr-24 07:15, David Farmer wrote:
> >      > On Fri, Apr 5, 2024 at 9:30 AM Ted Lemon <mellon@fugue.com
> <mailto:mellon@fugue.com> <mailto:mellon@fugue.com <mailto:
> mellon@fugue.com>>> wrote:
> >     ...
> >      >     If constrained devices already support the policy table, I do
> not think this additional work is onerous.
> >      >
> >      >
> >      > How would the "known-local" ULA prefixes be populated if not
> dynamically updated from PIOs and RIOs?
> >
> >     By the simple fact that a host actually has a ULA. This is the
> approach I used in three different userland hacks:
> >
> >     https://github.com/becarpenter/misc/blob/main/enable_ula.py <
> https://github.com/becarpenter/misc/blob/main/enable_ula.py>
> >     https://github.com/becarpenter/misc/blob/main/gai_wrap.py <
> https://github.com/becarpenter/misc/blob/main/gai_wrap.py>
> >     https://github.com/becarpenter/getapr/ <
> https://github.com/becarpenter/getapr/>
> >
> >          Brian
> >
> >
> > That will work for a single ULA network, but how does that work when you
> merge ULA networks, as discussed in section 4.2 of RFC4193? Do all hosts
> have to get an address from the other network(s) to know they are local?
> Somehow, the host needs to know the other ULA networks to treat it as
> local; otherwise, effectively, you can't merge ULA networks as RFC4193
> promises. I envision that coming from ROIs. If not ROIs, what?
>
> Those would be rather strange RIOs, because they would announce a prefix
> that is in use in some other part of the network, not on the current LAN.
> In other words, RIOs with A=L=0 (as envisaged by RFC 8028, for a different
> purpose).
>
> I'm not disagreeing with you, but simply observing that in the simple
> case, we don't need to explictly rely on RIOs.
>

You are confusing RIOs and PIOs. PIOs have A and L flags, not RIOs. But
yes, I believe PIOs with A=L=0 should also be included.

Thanks

-- 
===============================================
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================