Re: [v6ops] Updating RFC 7084

Ted Lemon <mellon@fugue.com> Fri, 18 November 2022 14:56 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFB04C14CE41 for <v6ops@ietfa.amsl.com>; Fri, 18 Nov 2022 06:56:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.896
X-Spam-Level:
X-Spam-Status: No, score=-6.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=fugue-com.20210112.gappssmtp.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 WfW68ryTe4KR for <v6ops@ietfa.amsl.com>; Fri, 18 Nov 2022 06:56:56 -0800 (PST)
Received: from mail-qt1-x829.google.com (mail-qt1-x829.google.com [IPv6:2607:f8b0:4864:20::829]) (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 9F8F0C1524BB for <v6ops@ietf.org>; Fri, 18 Nov 2022 06:56:48 -0800 (PST)
Received: by mail-qt1-x829.google.com with SMTP id l2so3223455qtq.11 for <v6ops@ietf.org>; Fri, 18 Nov 2022 06:56:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=mp/4FIoPCMFEmk8vzpxLC34b5uF0FX6Kntl4aPI4MiQ=; b=RdmTHrynTaL7ZTZSdIG06Y0rHOSAwIjitiHQBGE/VSw6OKbentdFIBfvg1y265A4co UjkmImAIYwulSH/46V4pg+2JFNdbxuBdkeikkK6hfQJy9H/DxYLo20CPAby/8Qlz2JSM /OcOcZIEB2F7kUCfnkGTFM1z9V+doFoiCWdyJHvkpeZVagyEJrpUppaUxmfIKF/2pUAV dNyaQFBCRKT09QeGGmKW3nWywBIpTjXCPkeqnh8TOz7dumTEmunWgS07m6PaGW7yZ0tw 9jhbK5WbfiiRWk1FuMdCDzA4N/A9nz8H2mthuBOFJclH7tREKW03ph0EjDNQsgnQ702w KURA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=mp/4FIoPCMFEmk8vzpxLC34b5uF0FX6Kntl4aPI4MiQ=; b=Rr0LHodJxD0pzA+pCGEjLnLl1Eo4GkPNzQIlMu+1KbWGttH40JjAXytqgBkdboMA4M wxXclC5zDDcJz3y4OH+Jg4V4mFHJJPb6Yz51cSCYrq2YLxhoCCDLf51VM1sIgbhsbvij k/kK+BjWpvS8jmnZbYYIQwfstbsKpPc8/FGmx3nf/4afOa/reLyr9XRMX+xxfEZ1Gx6q ZDQxPOhfZWsbO1/H8ICQE8nSR+goOz+cm/MaZ9wLfUTiq+cT30doPMSa1ZuMbcV16bPO xtetAdZjd+QDfsdW3L7YCB/NvIWGsgucIR1KA9vvpz0EPu20GJBd261IISF8rGZQkNxN 7aQw==
X-Gm-Message-State: ANoB5plbfkYC7N4PN6PzaxZ51/5lCl5tCrq5HiEO6X5Pfc9RCCZ7ADQL kAx1JfeOxC3enw60eGXNNfyTK7K33hWq+jIt9qhSZbCkNtjgoQ==
X-Google-Smtp-Source: AA0mqf7SuBdd24pSOJgYMybdGJ6YwxTLYqe0Ff8MNl5/hRLXNL9I/bQfqkztY+xbTKLsTVrs8vlAJ+NVOJV2Q+4w2OY=
X-Received: by 2002:ac8:745a:0:b0:3a5:ced8:6332 with SMTP id h26-20020ac8745a000000b003a5ced86332mr6748626qtr.670.1668783407705; Fri, 18 Nov 2022 06:56:47 -0800 (PST)
MIME-Version: 1.0
References: <CAJgLMKs5oYT1Eoq1Z-_3FYDVLvq6q8ecf+-g8cc1zZR5pJtJNw@mail.gmail.com>
In-Reply-To: <CAJgLMKs5oYT1Eoq1Z-_3FYDVLvq6q8ecf+-g8cc1zZR5pJtJNw@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Fri, 18 Nov 2022 09:56:11 -0500
Message-ID: <CAPt1N1mVVOs3r8+0D13_GC0tuhi7jHGwVLjuamzLgipuqPWWdQ@mail.gmail.com>
To: Timothy Winters <tim@qacafe.com>
Cc: IPv6 Operations <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000039407905edbfea59"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/4MDH-xSnuJRsiUMSMNQHa_HEZlw>
Subject: Re: [v6ops] Updating RFC 7084
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Nov 2022 14:56:58 -0000

I'll paraphrase my comment on SNAC about this, because we had a good
discussion there and I think this is actually more of a v6ops thing than a
SNAC thing (there's debate on the SNAC mailing list about whether we'd want
to do multi-homing even if the infrastructure supports it).

DHCPv6 PD assumes that the network is managed by a single entity, and so if
the network is multihomed, you can communicate with a single DHCPv6 server
and get all the information you need. There are a lot of reasons why this
is no longer correct. The first is that DHCPv6 doesn't (and can't) support
Provisioning Domains (PvDs). The second is that a very likely scenario for
a multi-homed home network (if any such scenario is at all likely!) is that
you have two CE routers connected to the same link, each of which is
advertising an RA on the link. Hosts on the link see both RAs and are
therefore multihomed.

RFC7084 doesn't talk about the PvD RA option for the simple reason that the
document that describes it was written long after 7084. Now that we have
such an option, it seems like an excellent way to indicate that the network
is multi-homed: each CE router can advertise a different PvD. How they are
defined is something we'd have to figure out, but in principle this seems
like a reasonable approach.

Why do we care? Because probably a DHCPv6 PD /client/ should be trying to
get one PD per PvD, not one PD total. A DHCPv6 PD client that doesn't do
this is only ever going to get a PD from one of the two CE routers, and
which one it gets isn't going to be deterministic. So this is a really
clear limitation for multi-homed networks in this scenario. RFC7084-bis
could clarify how this works, and I think it should. It's possible that
we'd also need a document in the DHC working group talking specifically
about the DHCPv6 PD behavior in the presence of multiple PvD RAs.

On Fri, Nov 18, 2022 at 9:47 AM Timothy Winters <tim@qacafe.com> wrote:

> Hello,
>
> I've started a draft to update RFC 7084 to support prefix delegation on
> the LAN interfaces.  The current state of IPv6 in home networks is ISP are
> assigning prefixes of appropriate sizes but they currently are under
> utilized due to the lack of prefix delegation on LAN interfaces.
>
> This draft is an attempt to add that support to the draft.
>
> https://datatracker.ietf.org/doc/draft-winters-v6ops-cpe-lan-pd/
>
> This is only an update to 7084 at the moment, there has been some
> discussion on the snac working group about leveraging this work as well.
>
> One item being discussed is this currently doesn't solve multi-homed
> networks.
>
> I welcome any feedback about the proposal.
>
> ~Tim
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>