IETF Logo Mail Archive

Re: [Idr] [bess] Request for IDR WG review of draft-ietf-bess-ebgp-dmz-02

Robert Raszuk <robert@raszuk.net> Mon, 26 June 2023 23: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 58B55C151991 for <idr@ietfa.amsl.com>; Mon, 26 Jun 2023 16:02:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, 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 h9TzDYNHWRR0 for <idr@ietfa.amsl.com>; Mon, 26 Jun 2023 16:02:33 -0700 (PDT)
Received: from mail-ej1-x62d.google.com (mail-ej1-x62d.google.com [IPv6:2a00:1450:4864:20::62d]) (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 4DEB7C151556 for <idr@ietf.org>; Mon, 26 Jun 2023 16:02:33 -0700 (PDT)
Received: by mail-ej1-x62d.google.com with SMTP id a640c23a62f3a-9896216338cso329053966b.3 for <idr@ietf.org>; Mon, 26 Jun 2023 16:02:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; t=1687820551; x=1690412551; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=j27y2I+heToDYxr8ovjqsBMAy3GDtcCY8zD9+X3Df30=; b=KrSNcpMEfiUvVqsYPxJ9XicUqioi18lZFn3tuDNWBLRCzyFD2vbGb+a2trR0DMV/Vs CYzX4ndD0xChZcNkSQvo7FSIm3GR5BrFdkKX+sUMWt3P32gQYfTDjKjUj6ciIngPgn7m HThjtH+iEt4a1KrWkCrEP6SqgFZQZ5k5INjsa5XfspnKpPrz+r00XUFH94Ynsb1TqIrM RBep+k0MsZebr7qNAlmz4coAWvFFKK+XmhY2bLvUFxtxusg5mWYdInYRby5elBLQtO80 wHqs25ITpaDd1h60LNj/wshf1F1KF8d3jkwAVlDtG473hkd3YKEAJzRCtFf3olFgSxWl lbNA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687820551; x=1690412551; 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=j27y2I+heToDYxr8ovjqsBMAy3GDtcCY8zD9+X3Df30=; b=h4gaSPMupefujPSVP01bZg+JyPxMP5CHGmd8ERC+4uGrdp8EH8AQRJbpZyckAh0KgT kSSFfZSBnw9HoSUufpziuA6+YG5RBeAEvYcR3hWUGqxyMQjnH/FcOeQdHy5INXFAWjse AgU8uxrP7fkn6E2kHvfx9YcAeDf7eWvRnafg9ELattV/4/jVT70ym6uVnhSc8153tCHw BzI5cvIHs0Ma4Av7BD0opuwXqkzg99peFRg8qjWeftKfdh6w3gLXozztgR8VSrUicDnL zeeUGj5PbuDUuPKJzxZD0aRE6Iw0zJpUC98yxj27OWDUO/4cK34a88xHLywbJAedAsIo Pv0w==
X-Gm-Message-State: AC+VfDz7Ois/u8t90+FG7WKO49++FpkfBkZ0MPMeoMGAGGs+8qVOyijj awl56blINj0gfQInj2WllE2EZETE9FSI5F/Vm+ganA==
X-Google-Smtp-Source: ACHHUZ7cFDUIMeG3Gwg9VES/IU9AkzfpnNwTlv1FpSg7AJMXwJjAY0fuWQ56+dTgL/+OUbOrvTlxivtm0vEKqFThAog=
X-Received: by 2002:a17:906:9b88:b0:988:91cb:afd1 with SMTP id dd8-20020a1709069b8800b0098891cbafd1mr23512429ejc.29.1687820551370; Mon, 26 Jun 2023 16:02:31 -0700 (PDT)
MIME-Version: 1.0
References: <CAMMESsySRUHZT5y=NkX6u1fdwBx9Bix9vyAo-7HRvVm6FNL2BA@mail.gmail.com> <C18ADFDA-BA6F-412A-BC49-C1AF3E5EA052@gmail.com> <CAMMESsw08D0JLSTP4qU_Ns=kx6vvkG2NxsY-Rx6EBKm23yTuaA@mail.gmail.com>
In-Reply-To: <CAMMESsw08D0JLSTP4qU_Ns=kx6vvkG2NxsY-Rx6EBKm23yTuaA@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Tue, 27 Jun 2023 01:02:20 +0200
Message-ID: <CAOj+MMHQSpSnS3wW4ur5J5+NTUzdFCSr5qce8YaC596ZfK5iGg@mail.gmail.com>
To: Alvaro Retana <aretana.ietf@gmail.com>, idr@ietf.org, bess@ietf.org
Cc: Jeff Tantsura <jefftant.ietf@gmail.com>, idr-chairs@ietf.org
Content-Type: multipart/alternative; boundary="00000000000068cada05ff105878"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/TQ5cY2ttMl0SiUYlEoX_npLpvU0>
Subject: Re: [Idr] [bess] Request for IDR WG review of draft-ietf-bess-ebgp-dmz-02
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: Mon, 26 Jun 2023 23:02:37 -0000

All,

Looking at all the drafts mentioned I do think there are actually two
different scenarios being considered and perhaps it is actually beneficial
to treat them separately.

Original draft allowed to signal link bw in situations where you peer from
different boxes. Path hiding is not an issue. Most likely such signalling
is to be done in respect to underlay.

However newer proposals aim to enhance the overlay behaviour where via one
or the other technique path hiding issue of BGP is addressed.

Inter-AS option C is also an overlay so I would recommend to think twice
before influencing base idea with this deployment scenario.

To conclude let's also realize that link bw is actually not a property of a
path as it is a property of the next hop binded to such path (how easy or
difficult it is to get to such next hop). And here I must say that the
draft Kaliraj & Minto proposed draft-kaliraj-idr-multinexthop-attribute
could possibly be used as a vehicle for its encoding.

The clear benefit for such perspective is ability to signal helper next
hops addresses with their link bw metrics possible hashing spread without
need to explode BGP with lot's of paths respectively if that is done by
add-paths or RD prepend.

Thx,
Robert


On Mon, Jun 26, 2023 at 11:44 PM Alvaro Retana <aretana.ietf@gmail.com>
wrote:

> On June 26, 2023 at 5:27:39 PM, Jeff Tantsura wrote:
>
> Jeff:
>
> > Over the last couple of years I have reached out to the authors of the
> > original draft at least twice with a request to refresh the draft and
> bring
> > the necessary changes in, without much success though.
> >
> ...
> > Note that there’s also an EVPN specific draft (standard track).
>
> That made me go look -- I found two related documents!  Are these what
> you're referring to?
>
>    https://datatracker.ietf.org/doc/html/draft-ietf-bess-weighted-hrw
>    https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-unequal-lb
>
>
> > I’d be happy to volunteer to help managing the mess ;-)
>
> I know the idr/bess-chairs are listening. ;-)
>
>
> Alvaro.
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>

v2.23.0 | Report a Bug | By Email