Re: [Idr] WGLC is for "BGP Router Capabilities Attribute” [was: Re: WG LC for draft-ietf-idr-entropy-09 (8/29 to 9/12/2023)]
Robert Raszuk <robert@raszuk.net> Thu, 07 September 2023 20:02 UTC
Return-Path: <robert@raszuk.net>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 296F0C15154A for <idr@ietfa.amsl.com>; Thu, 7 Sep 2023 13:02:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=raszuk.net
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 qL6-AwhaLd5k for <idr@ietfa.amsl.com>; Thu, 7 Sep 2023 13:02:27 -0700 (PDT)
Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com [IPv6:2a00:1450:4864:20::136]) (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 072C0C1516EA for <idr@ietf.org>; Thu, 7 Sep 2023 13:02:26 -0700 (PDT)
Received: by mail-lf1-x136.google.com with SMTP id 2adb3069b0e04-4ff09632194so2271769e87.2 for <idr@ietf.org>; Thu, 07 Sep 2023 13:02:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; t=1694116945; x=1694721745; 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=WnegkTQkmqe2tjOev6FSgYSzQ2iPKPXdR/czM+u9fsw=; b=TqNRVVj97W867XqoKb/eDcQ5QCtUoYzyVp5ibFPLg+GfmvJweVSANKivA9ot1o5JLn 8VdChPZc9jJJUjJGg2pm44qz4S6NtcsHpXqm4FwjBhNfKMEsf4ciHJsg8BoBoHgaV84a xWnx6BuzHfJW0LPh00J6GNwnvZJeqwLNNbYkDr0QPlEI+OJWLINZTcty0nJtnNkSomQu T6u12XtbDI+GCqBV0+5C9CoyBhixZ3mv8MCcovEB0KTyZhD83eX1Nb6N5+MbOkGsZ0Pv 9wOwLvU0bCNhwaIgd0dF0s14qejrfiWYho+jhsreUXNE2rw7L+tXx87tc7usDBKAyubG 8+pg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1694116945; x=1694721745; 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=WnegkTQkmqe2tjOev6FSgYSzQ2iPKPXdR/czM+u9fsw=; b=XUIeSYpSNR1Vp51k7SRJPdUL4h6EzPD24E3ldiiHS4OTBh7hvWUN0BqafyLn/ywzku 5PK8pWQVxe7wd1x1B8GSxqH07JSJGs5n7ioDKcOuS7Fq+QUPPdVEIAmtxcAX7BZ1ggqm +zU430VK/aUDhIH0D0w/5cIDzz+FRzLVqctFllH5u/JCaji1XOqV8AxKQHplJieQQxbh CB52YjoNJcnFVBlomlzgkL4cC41WgNrVmWJ3h9xc2rDe7P5S2zjjEYzKTbGcZ1KP9D2b JI6k9dMvMMAHD3X9ULypfYHS+y6SXibtXmvfGxGl3uUw6wrD0dxOIiPgTLWxCSdz3+Dv w1/w==
X-Gm-Message-State: AOJu0YxrgqWPu0V1f6qC0JpktxHS09GhQiC97eta1fyqBZ0SA50XiEpZ d70P+fbLLp3NPjrwpE9Hlc3sTH4bs9GBsHs7Vw3asIKW0NVhxHCF
X-Google-Smtp-Source: AGHT+IE67hNLmvQTpbHg6LUdFuEpgpemM/NRhLNEimPNyfv2j7XHCymJRkl6kwxPhW/ZMdakehx4xEbRFTGtjzdYF4Y=
X-Received: by 2002:a05:6512:3e1b:b0:500:7a23:720b with SMTP id i27-20020a0565123e1b00b005007a23720bmr424503lfv.55.1694116944616; Thu, 07 Sep 2023 13:02:24 -0700 (PDT)
MIME-Version: 1.0
References: <BYAPR08MB48722A08FBACCBE523079846B3E7A@BYAPR08MB4872.namprd08.prod.outlook.com> <F75A6C76-D18C-4308-832B-BB6B14241C08@juniper.net> <EA75C4F9-0F37-4CE2-9761-6A5629A2A3F8@pfrc.org>
In-Reply-To: <EA75C4F9-0F37-4CE2-9761-6A5629A2A3F8@pfrc.org>
From: Robert Raszuk <robert@raszuk.net>
Date: Thu, 07 Sep 2023 22:02:13 +0200
Message-ID: <CAOj+MMGcGXguGM+1_WU5Tn9e+L7C0u0DfLf2Z6f0-a_MKZM9zQ@mail.gmail.com>
To: Jeffrey Haas <jhaas@pfrc.org>
Cc: John Scudder <jgs=40juniper.net@dmarc.ietf.org>, "idr@ietf.org" <idr@ietf.org>, Sue Hares <shares@ndzh.com>
Content-Type: multipart/alternative; boundary="000000000000b13a3b0604ca56f7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/-rtanBksq2ngzuaULXfkSCsC8DY>
Subject: Re: [Idr] WGLC is for "BGP Router Capabilities Attribute” [was: Re: WG LC for draft-ietf-idr-entropy-09 (8/29 to 9/12/2023)]
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2023 20:02:31 -0000
Hi Jeff, Speaking as an individual contributor, I also think next-hop-capabilit(ies) > better reflects the proposal. > IMHO it would be the preferred title and name of the draft. But then we have the (multi) next hop attribute coming up as well. Shouldn't that work be combined ? That said, I think painting each service route with the same attribute(s) is a bit wasteful design at best. It does seem to me like sooner or later we would benefit from separate next hop state/description SAFI especially for the applications which use BGP recursion and resolve BGP service routes via another BGP AF (example BGP-LU), but even if the next hop reachability is carried in IGPs as we do not want to pollute IGP link state flooding too much. Thx, R. > On Sep 7, 2023, at 2:35 PM, John Scudder <jgs=40juniper.net@dmarc.ietf.org> > wrote: > > > > Hi All, > > > > Robert Raszuk pointed out [1] that the draft filename > (draft-ietf-idr-entropy) doesn’t clearly reflect the title and scope of the > spec — the title is "BGP Router Capabilities Attribute”, and indeed the > ELCv3/Entropy Label Capability is only one example of a capability the RCA > can contain. > > > > As a reminder, we ended up with this filename because the draft is a > merger of draft-ietf-idr-next-hop-capability and > draft-ietf-idr-entropy-label, and that was the one we picked to merge down > to. In retrospect maybe we should have merged down to > draft-ietf-idr-next-hop-capability instead, or even picked a third, new, > filename. > > > > I’ve adjusted the subject line to spotlight this fact, because Robert > expressed concern that WG participants might not realize what the WGLC is > about, and I promised [2] to follow up. > > > > Thanks, > > > > —John > > > > [1] > https://mailarchive.ietf.org/arch/msg/idr/lEabkTb0VjymshotgF8Ej29vVkM/ > > [2] > https://mailarchive.ietf.org/arch/msg/idr/5XchsuIzrj5Hb4a8Ju2zG7jI_kM/ > > > > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://www.ietf.org/mailman/listinfo/idr >
- [Idr] WG LC for draft-ietf-idr-entropy-09 (8/29 t… Susan Hares
- Re: [Idr] WG LC for draft-ietf-idr-entropy-09 (8/… bruno.decraene
- Re: [Idr] WG LC for draft-ietf-idr-entropy-09 (8/… John Scudder
- Re: [Idr] WG LC for draft-ietf-idr-entropy-09 (8/… bruno.decraene
- Re: [Idr] WG LC for draft-ietf-idr-entropy-09 (8/… Randy Bush
- Re: [Idr] WG LC for draft-ietf-idr-entropy-09 (8/… John Scudder
- Re: [Idr] WG LC for draft-ietf-idr-entropy-09 (8/… Randy Bush
- Re: [Idr] WG LC for draft-ietf-idr-entropy-09 (8/… Satya Mohanty (satyamoh)
- Re: [Idr] WG LC for draft-ietf-idr-entropy-09 (8/… Susan Hares
- Re: [Idr] WG LC for draft-ietf-idr-entropy-09 (8/… James Uttaro
- Re: [Idr] WG LC for draft-ietf-idr-entropy-09 (8/… Wim Henderickx (Nokia)
- Re: [Idr] WG LC for draft-ietf-idr-entropy-09 (8/… Wen, Bin
- Re: [Idr] WG LC for draft-ietf-idr-entropy-09 (8/… Kevin Wang
- Re: [Idr] WG LC for draft-ietf-idr-entropy-09 (8/… bruno.decraene
- Re: [Idr] WG LC for draft-ietf-idr-entropy-09 (8/… Krzysztof Szarkowicz
- Re: [Idr] WG LC for draft-ietf-idr-entropy-09 (8/… Robert Raszuk
- Re: [Idr] WG LC for draft-ietf-idr-entropy-09 (8/… John Scudder
- Re: [Idr] WG LC for draft-ietf-idr-entropy-09 (8/… Robert Raszuk
- Re: [Idr] WG LC for draft-ietf-idr-entropy-09 (8/… bruno.decraene
- Re: [Idr] WG LC for draft-ietf-idr-entropy-09 (8/… Robert Raszuk
- Re: [Idr] WG LC for draft-ietf-idr-entropy-09 (8/… John Scudder
- [Idr] WGLC is for "BGP Router Capabilities Attrib… John Scudder
- Re: [Idr] WG LC for draft-ietf-idr-entropy-09 (8/… Robert Raszuk
- Re: [Idr] WGLC is for "BGP Router Capabilities At… Jeffrey Haas
- Re: [Idr] WGLC is for "BGP Router Capabilities At… Robert Raszuk
- Re: [Idr] WG LC for draft-ietf-idr-entropy-09 (8/… John Scudder
- Re: [Idr] WGLC is for "BGP Router Capabilities At… John Scudder
- Re: [Idr] WGLC is for "BGP Router Capabilities At… Jeffrey Haas
- Re: [Idr] WGLC is for "BGP Router Capabilities At… Susan Hares
- Re: [Idr] WGLC is for "BGP Router Capabilities At… Job Snijders
- Re: [Idr] WGLC is for "BGP Router Capabilities At… Jeffrey Haas
- Re: [Idr] WGLC is for "BGP Router Capabilities At… Robert Raszuk
- Re: [Idr] WGLC is for "BGP Router Capabilities At… Susan Hares
- Re: [Idr] WGLC is for "BGP Router Capabilities At… Robert Raszuk
- Re: [Idr] WGLC is for "BGP Router Capabilities At… Susan Hares
- Re: [Idr] WG LC for draft-ietf-idr-entropy-09 (8/… Gyan Mishra
- Re: [Idr] WG LC for draft-ietf-idr-entropy-09 (8/… Gyan Mishra
- Re: [Idr] WGLC is for "BGP Router Capabilities At… tom petch
- Re: [Idr] WG LC for draft-ietf-idr-entropy-09 (8/… Robert Raszuk
- Re: [Idr] WGLC is for "BGP Router Capabilities At… Susan Hares
- Re: [Idr] WGLC is for "BGP Router Capabilities At… Jeffrey Haas
- Re: [Idr] WGLC is for "BGP Router Capabilities At… Robert Raszuk
- Re: [Idr] WGLC is for "BGP Router Capabilities At… Robert Raszuk
- Re: [Idr] WG LC for draft-ietf-idr-entropy-09 (8/… Gyan Mishra
- Re: [Idr] WG LC for draft-ietf-idr-entropy-09 (8/… Robert Raszuk
- Re: [Idr] WGLC is for "BGP Router Capabilities At… bruno.decraene
- Re: [Idr] WGLC is for "BGP Router Capabilities At… John Scudder
- Re: [Idr] WGLC is for "BGP Router Capabilities At… Linda Dunbar
- Re: [Idr] WGLC is for "BGP Router Capabilities At… John Scudder
- Re: [Idr] WGLC is for "BGP Router Capabilities At… Robert Raszuk
- Re: [Idr] WGLC is for "BGP Router Capabilities At… John Scudder
- Re: [Idr] WGLC is for "BGP Router Capabilities At… Randy Bush
- Re: [Idr] WGLC is for "BGP Router Capabilities At… Jeffrey Haas
- Re: [Idr] WGLC is for "BGP Router Capabilities At… Jeffrey Haas
- Re: [Idr] WGLC is for "BGP Router Capabilities At… Randy Bush
- Re: [Idr] WGLC is for "BGP Router Capabilities At… John Scudder
- Re: [Idr] WGLC is for "BGP Router Capabilities At… Ketan Talaulikar
- Re: [Idr] WGLC is for "BGP Router Capabilities At… John Scudder
- Re: [Idr] WGLC is for "BGP Router Capabilities At… Ketan Talaulikar
- Re: [Idr] WGLC is for "BGP Router Capabilities At… Kaliraj Vairavakkalai
- Re: [Idr] WGLC is for "BGP Router Capabilities At… Robert Raszuk
- Re: [Idr] WGLC is for "BGP Router Capabilities At… John Scudder
- Re: [Idr] WGLC is for "BGP Router Capabilities At… John Scudder
- Re: [Idr] WGLC is for "BGP Router Capabilities At… Kaliraj Vairavakkalai
- Re: [Idr] WGLC is for "BGP Router Capabilities At… Robert Raszuk
- Re: [Idr] WGLC is for "BGP Router Capabilities At… John Scudder
- Re: [Idr] WGLC is for "BGP Router Capabilities At… John Scudder