IETF Logo Mail Archive

Re: [Idr] Part 2 of CAR/CT Adoption call (7/6 to 7/20) - Adoption of draft-dskc-bess-bgp-car-05.txt and draft-kaliraj-idr-bgp-classful-transport-planes-17.txt

Robert Raszuk <robert@raszuk.net> Tue, 19 July 2022 19:40 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 A184FC13C51B for <idr@ietfa.amsl.com>; Tue, 19 Jul 2022 12:40:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.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_DNSWL_HI=-5, 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=ham 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 m6i6-2nlgaqG for <idr@ietfa.amsl.com>; Tue, 19 Jul 2022 12:40:10 -0700 (PDT)
Received: from mail-lf1-x132.google.com (mail-lf1-x132.google.com [IPv6:2a00:1450:4864:20::132]) (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 DBBB9C157B59 for <idr@ietf.org>; Tue, 19 Jul 2022 12:40:10 -0700 (PDT)
Received: by mail-lf1-x132.google.com with SMTP id d12so26605048lfq.12 for <idr@ietf.org>; Tue, 19 Jul 2022 12:40:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=cgQlcTITXE2zZg031DRn3t3hA4nZ5WwagIPfIIX4p2w=; b=GcjYhAvVcZY/C8ww8Ej8MuwJAfBtJqHZMGbZsH7D2kWhyOC4goPqQ5aUkKiacLxHHY vu05bfPoMlJZlyu2x04jiV9jJR6sQP5FoBrNr4MLIsPNw2UJasrVnGWJhB8rIstOg8OQ n91qhu5r2vdtq9E2qdjbfNkGqKpGNc+7tWQ5ckfW8jGZRJ5NyxHKJO9AN5HCstnqJIi8 NURVRk5BZHexGxa4zUraid7iVFm9+SwWEKoKmOavYkh7BCI9ZNt/orGQ2JLWrga/4F8x T9GsUXK05PumjvyeNkdvoakaDtHp82MJRE8YBr8326BHaguU/ekhAzw0KP6Cin31DAGZ 2oLg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=cgQlcTITXE2zZg031DRn3t3hA4nZ5WwagIPfIIX4p2w=; b=rZhzRw0MFsySGi6K19+/Lh/Iw8P9EaIMfzh9jQ9PgEbgRaAI6rltrjnR+W+OCT7wfQ 4DfLDInZIAj+ZQ7AzTZwfVSot5Fh+4eFsc8YeKB2jC77Ujo0khAd8tRmV8j0yC60oUtZ RcHeJy5QqMRdTse2rzq2HCnPx6BEkwXP//dJJF5yVZRD5YKrQpd4j4MNaSTEHp/Od56Y tmzzQMyFnVx745UbYhZcp5nctLrMVThlYZT698JJGY9UIKW9nAIe+duJIswAytKCZOlI r+5zDbfWp6Zl8t/VDDXlFAbWMuxHj46nckoE9tWRRXc8vuYsrYPm6HvC2tNaURJGWKj+ fHfQ==
X-Gm-Message-State: AJIora/4myCpYjOqFrMwbnGLK+SVPp89CA+41l28j0/aYcjmsQlVu6fO kUq4BxO1YyO8+6FlU0WzYzako9U3dXF6nWXWIzvvmE9jV1Q=
X-Google-Smtp-Source: AGRyM1tWaVNBJVlAnVjsfJEemwM2h/VO8m4etC7y9Qauwg/oe5woVQP7CDA1gnH6Jhx1OZzpHVgOBSiWDrzlM3mRxMw=
X-Received: by 2002:a05:6512:2204:b0:489:fd91:89ea with SMTP id h4-20020a056512220400b00489fd9189eamr19114009lfu.593.1658259609036; Tue, 19 Jul 2022 12:40:09 -0700 (PDT)
MIME-Version: 1.0
References: <BYAPR08MB48725C453611F6A21F255295B3809@BYAPR08MB4872.namprd08.prod.outlook.com> <CAH6gdPw_iBYaLkasdkhmWj1ATT2_O-u5+0JgM5MNzctMnPODuA@mail.gmail.com> <PH0PR05MB774961C3E008B7512F1AF83FB98F9@PH0PR05MB7749.namprd05.prod.outlook.com> <CAH6gdPwiVgGPTbGn645zTYBzZdGnJLuXruw8Z8dtkK+OYQvPgQ@mail.gmail.com> <SJ0PR05MB86329812CA40A2A6454D89E2A28F9@SJ0PR05MB8632.namprd05.prod.outlook.com>
In-Reply-To: <SJ0PR05MB86329812CA40A2A6454D89E2A28F9@SJ0PR05MB8632.namprd05.prod.outlook.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Tue, 19 Jul 2022 21:39:57 +0200
Message-ID: <CAOj+MMG2n2NB4CV74opD15VfFfrosYmqPNGN_a2MZK2Mu-wWzw@mail.gmail.com>
To: Kaliraj Vairavakkalai <kaliraj=40juniper.net@dmarc.ietf.org>
Cc: Ketan Talaulikar <ketant.ietf@gmail.com>, Srihari Sangli <ssangli@juniper.net>, Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f1410e05e42da6a0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/mg3k6GRT6WLsLpQclV8cO57NHSY>
Subject: Re: [Idr] Part 2 of CAR/CT Adoption call (7/6 to 7/20) - Adoption of draft-dskc-bess-bgp-car-05.txt and draft-kaliraj-idr-bgp-classful-transport-planes-17.txt
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: Tue, 19 Jul 2022 19:40:14 -0000

Hello Kaliraj,

I think you have stated it very well below.

BGP-CT follows RFC-8277.

So tell me why the new forwarding paradigm needs to be glued to MPLS for
years to come ?

What if customers do not use MPLS for forwarding or are in the process of
migration away from it ?

Why put a burden on them about the notion of labels in what we all agree
data plane agnostic signalling ?

Kind regards,
Robert


On Tue, Jul 19, 2022 at 7:10 PM Kaliraj Vairavakkalai <kaliraj=
40juniper.net@dmarc.ietf.org> wrote:

> Ketan, to answer you question below,
>
>
>
> BGP-CT follows RFC-8277 which is an existing standard. And proposes the
>
> MNH-attribute (
> https://datatracker.ietf.org/doc/html/draft-kaliraj-idr-multinexthop-attribute-02
> )
>
> that carries label in an attribute, for future scoping.
>
>
>
> Just a seamless transition from where BGP is today, to where we want it to
> be in future.
>
>
>
> We want the ‘future mechanism’ to work for existing families, in similar
> manner.
>
> So there is no reason not to follow RFC-8277 today. And that is also why
> we should not carry
>
> these forwarding information in NLRI of new families.
>
>
>
> Thanks
>
> Kaliraj
>
>
>

v2.23.0 | Report a Bug | By Email