[Idr] Re: I-D Action: draft-wang-idr-dpf-00.txt
Jeffrey Haas <jhaas@pfrc.org> Fri, 05 December 2025 18:32 UTC
Return-Path: <jhaas@pfrc.org>
X-Original-To: idr@mail2.ietf.org
Delivered-To: idr@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 50E8E9622371; Fri, 5 Dec 2025 10:32:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OWwQBIEjIekp; Fri, 5 Dec 2025 10:32:51 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by mail2.ietf.org (Postfix) with ESMTP id 2B55A962236A; Fri, 5 Dec 2025 10:32:51 -0800 (PST)
Received: from smtpclient.apple (99-188-202-8.lightspeed.livnmi.sbcglobal.net [99.188.202.8]) by slice.pfrc.org (Postfix) with ESMTPSA id 4D71F1E24F; Fri, 5 Dec 2025 13:32:49 -0500 (EST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_D821F776-ED32-440A-B0D2-39D7907D67C8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.10\))
From: Jeffrey Haas <jhaas@pfrc.org>
In-Reply-To: <CAOj+MMFAt1P3cPD2wFd_UdmCs3ncyhZt1tUcYTVu6K_qOZCsGQ@mail.gmail.com>
Date: Fri, 05 Dec 2025 13:32:48 -0500
Message-Id: <9CBC35A7-EE16-44CD-925C-F881EC8AB842@pfrc.org>
References: <176462578612.3650528.8915305565733099516@dt-datatracker-5bd94c585b-wk4l4> <CAOj+MMEw4HFJRmJ_=VhVSQCr1Sic6nrixXqFYpT3E47Mk_EaGw@mail.gmail.com> <CABNhwV2XzaTyiETsYr-STKypq9M49YnW8ekj5jTsG5==xmRX5Q@mail.gmail.com> <MW4PR84MB2092F37923BBE432BF32AECF86D8A@MW4PR84MB2092.NAMPRD84.PROD.OUTLOOK.COM> <CAOj+MMHpDy6zfSjC4nuaVwst+Bj+vcDNjz6CXkO5x6N7-Rkx6w@mail.gmail.com> <MW4PR84MB2092FDB05447EB3962527A5786D9A@MW4PR84MB2092.NAMPRD84.PROD.OUTLOOK.COM> <CAOj+MMEaAJw3Ss8osrRCVheF-k7NL9eA+5KWXeBmk5fpLaujBg@mail.gmail.com> <MW4PR84MB20928FB359828A8DA27A200286A6A@MW4PR84MB2092.NAMPRD84.PROD.OUTLOOK.COM> <CAOj+MMH=F-p4LPTas0UeB_fuE6TAhKvcjmUYgFEhv_tpqdOeBg@mail.gmail.com> <9F4EBAA8-2F37-4191-A04F-6D6861751DD6@pfrc.org> <CAOj+MMFAt1P3cPD2wFd_UdmCs3ncyhZt1tUcYTVu6K_qOZCsGQ@mail.gmail.com>
To: Robert Raszuk <robert@raszuk.net>
X-Mailer: Apple Mail (2.3696.120.41.1.10)
Message-ID-Hash: MVC3FU5TAIOUSQIORD522RVUXIHYPIVQ
X-Message-ID-Hash: MVC3FU5TAIOUSQIORD522RVUXIHYPIVQ
X-MailFrom: jhaas@pfrc.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-idr.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "Wang, Kevin" <kevin.wang@hpe.com>, "idr@ietf. org" <idr@ietf.org>, lsr <lsr@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Idr] Re: I-D Action: draft-wang-idr-dpf-00.txt
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/-IesLjaLD9CTz087onBNqYRY3ak>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Owner: <mailto:idr-owner@ietf.org>
List-Post: <mailto:idr@ietf.org>
List-Subscribe: <mailto:idr-join@ietf.org>
List-Unsubscribe: <mailto:idr-leave@ietf.org>
Robert, > On Dec 5, 2025, at 11:21 AM, Robert Raszuk <robert@raszuk.net> wrote: > > Just want to respond to one point made: > > > With your current proposal you have created a physical partitioning not logical one. > > I agree with that assessment. For the case of BGP fabrics, and likely similar overlapping cases for IGP signaled fabrics, this is likely the desired property. > > I think history taught us that hard partitioning the IP fabric is to say it softly suboptimal choice of any solution. > > And with IGPs you always run your base topology across all links and nodes. None of these things, DPF, or any of our "routes with color" fundamentally change the problem: This is just a form of multi-topology distribution. IGPs will suffer from the same considerations. The conversation then reverts to the forwarding paradigms your mechanism supports, and what the operator is willing to deploy. I'll agree with you that "all or nothing" proposals usually end up being wasteful, even if effective. This inevitably pushes us to where the conversation is currently at across multiple WGs: How do we do better about congestion under such circumstances? May we live in interesting times. I believe we've exhausted the original point about overlaps with IGP technology for the moment, and will be excluding LSR in future responses. -- Jeff
- [Idr] Fwd: I-D Action: draft-wang-idr-dpf-00.txt Robert Raszuk
- [Idr] Re: Fwd: I-D Action: draft-wang-idr-dpf-00.… Gyan Mishra
- [Idr] Re: Fwd: I-D Action: draft-wang-idr-dpf-00.… Wang, Kevin
- [Idr] Re: Fwd: I-D Action: draft-wang-idr-dpf-00.… Robert Raszuk
- [Idr] Re: Fwd: I-D Action: draft-wang-idr-dpf-00.… Wang, Kevin
- [Idr] Re: Fwd: I-D Action: draft-wang-idr-dpf-00.… Robert Raszuk
- [Idr] Re: Fwd: I-D Action: draft-wang-idr-dpf-00.… Wang, Kevin
- [Idr] Re: Fwd: I-D Action: draft-wang-idr-dpf-00.… Robert Raszuk
- [Idr] Re: [Lsr] Re: Re: Fwd: I-D Action: draft-wa… Tony Przygienda
- [Idr] Re: I-D Action: draft-wang-idr-dpf-00.txt Jeffrey Haas
- [Idr] Re: I-D Action: draft-wang-idr-dpf-00.txt Jeffrey Haas
- [Idr] Re: I-D Action: draft-wang-idr-dpf-00.txt Robert Raszuk
- [Idr] Re: I-D Action: draft-wang-idr-dpf-00.txt Jeffrey Haas
- [Idr] Re: I-D Action: draft-wang-idr-dpf-00.txt Robert Raszuk
- [Idr] Re: I-D Action: draft-wang-idr-dpf-00.txt Wang, Kevin
- [Idr] Re: I-D Action: draft-wang-idr-dpf-00.txt Robert Raszuk
- [Idr] Re: I-D Action: draft-wang-idr-dpf-00.txt Kevin Wang