[bess] Re: [Idr] Re: Some comments on carrying bandwidth in BGP, and also on draft-xu-idr-fare-04 (was Re: Working Group Last Call on draft-ietf-bess-ebgp-dmz)
Nick Hilliard <nick@foobar.org> Wed, 27 May 2026 13:28 UTC
Return-Path: <nick@foobar.org>
X-Original-To: bess@mail2.ietf.org
Delivered-To: bess@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id D7EB2F5EF6FA; Wed, 27 May 2026 06:28:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1779888519; bh=wPRCZ6naBjWzCJiKtDXaVZA9oDb96gYWbtrtlk+GmaQ=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=RRnUbVBSAgbeBq6OIY8IrLMq4P/kP3RiglVjlO5J4cxrISnYCZ45fl6Ta4OeIet2S AjqRYIUYFDsdyWUlRX8/LihyT/mO1mJkrFGMoIWVDwidUD3KM9s0JgrboLnVanrFLZ VTMwCEHSVzll25zdawE2sxj2deCjx2vJ4CBtIRbg=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -5.822
X-Spam-Level:
X-Spam-Status: No, score=-5.822 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-1.624, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=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 rvxCHTOvbdFy; Wed, 27 May 2026 06:28:39 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [46.182.8.5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 4F92EF5EF6F5; Wed, 27 May 2026 06:28:39 -0700 (PDT)
Received: from cupcake.localdomain (unknown [89.101.195.154]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.netability.ie (Postfix) with ESMTPSA id B080D9CE6C; Wed, 27 May 2026 14:28:37 +0100 (IST)
To: Jeffrey Haas <jhaas@pfrc.org>
References: <PAXP251MB0009AA94992A8F42E38CA63E813F2@PAXP251MB0009.EURP251.PROD.OUTLOOK.COM> <62F583D5-D130-4FCF-ABC0-C3077349B97E@pfrc.org> <PAXP251MB0009380D93F5995B3D4F4EC381012@PAXP251MB0009.EURP251.PROD.OUTLOOK.COM> <0f512bf0-0816-40c7-b00e-a7468a3f0cff@pfrc.org>
From: Nick Hilliard <nick@foobar.org>
Message-ID: <9c3ad688-f415-7bf3-30da-e2e836a4c722@foobar.org>
Date: Wed, 27 May 2026 14:28:33 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 26.5; rv:52.0) Gecko/20100101 PostboxApp/7.0.65
MIME-Version: 1.0
In-Reply-To: <0f512bf0-0816-40c7-b00e-a7468a3f0cff@pfrc.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Message-ID-Hash: O6DZRAWU3JQP6QB5EI2ESIGWEFOUV5EL
X-Message-ID-Hash: O6DZRAWU3JQP6QB5EI2ESIGWEFOUV5EL
X-MailFrom: nick@foobar.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-bess.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Tiger Xu <xuxiaohu_ietf@hotmail.com>, BESS <bess@ietf.org>, "idr@ietf. org" <idr@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [bess] Re: [Idr] Re: Some comments on carrying bandwidth in BGP, and also on draft-xu-idr-fare-04 (was Re: Working Group Last Call on draft-ietf-bess-ebgp-dmz)
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/QWgya9-0b_RGc0F2m9SkSkJbf1M>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Owner: <mailto:bess-owner@ietf.org>
List-Post: <mailto:bess@ietf.org>
List-Subscribe: <mailto:bess-join@ietf.org>
List-Unsubscribe: <mailto:bess-leave@ietf.org>
Jeffrey Haas wrote on 27/05/2026 14:01: > Thanks. While the intention of many of these "walled garden" features > is that "this can't possibly leak", we are regularly seeing things > leak. See also the discussion on community cleanup in the other thread > for things that aren't expected to leak. The default expectation in the operational community is that things will leak in bgp. The concept of "there is no such risk" does not exist in this context. Nick
- [bess] Re: Working Group Last Call on draft-ietf-… Tiger Xu
- [bess] Re: [Idr] Working Group Last Call on draft… Jeffrey Haas
- [bess] Some comments on carrying bandwidth in BGP… Jeffrey Haas
- [bess] Re: [Idr] Re: Working Group Last Call on d… Aijun Wang
- [bess] Re: Some comments on carrying bandwidth in… Tiger Xu
- [bess] Re: [Idr] Working Group Last Call on draft… Jeffrey Haas
- [bess] Re: Some comments on carrying bandwidth in… Jeffrey Haas
- [bess] 答复: [Idr] Working Group Last Call on draft… Tiger Xu
- [bess] Re: [Idr] Re: Some comments on carrying ba… Nick Hilliard
- [bess] Re: [Idr] Working Group Last Call on draft… slitkows.ietf