IETF Logo Mail Archive

Re: [Lsvr] AD Review of draft-ietf-lsvr-bgp-spf-19

Alvaro Retana <aretana.ietf@gmail.com> Sat, 11 March 2023 11:25 UTC

Return-Path: <aretana.ietf@gmail.com>
X-Original-To: lsvr@ietfa.amsl.com
Delivered-To: lsvr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2E32C17B32B; Sat, 11 Mar 2023 03:25:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.097
X-Spam-Level:
X-Spam-Status: No, score=-6.097 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, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 zk3iUCElxmpP; Sat, 11 Mar 2023 03:25:21 -0800 (PST)
Received: from mail-pf1-x432.google.com (mail-pf1-x432.google.com [IPv6:2607:f8b0:4864:20::432]) (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 86FD5C17B327; Sat, 11 Mar 2023 03:25:21 -0800 (PST)
Received: by mail-pf1-x432.google.com with SMTP id ay18so5159844pfb.2; Sat, 11 Mar 2023 03:25:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1678533920; h=cc:to:subject:message-id:date:mime-version:references:in-reply-to :from:from:to:cc:subject:date:message-id:reply-to; bh=GI2Mq2oBw8kOVd/VwjpkU/5ZReZ9/pinxlgiFqVkJms=; b=WElBbjDbvdfMaiFzx4cz6IW/sbpkAr83UBl/QJ1mCj78zVC0g/mvn67kpsxsPy2oLI NU/TUI+sZxG6vWbJwx7j9y6OUQ7sLHasKNUydl8NUNQnjj7O7JZ5+BoHykAGxeTBTjYD OYkW6zA8V6rIw4TsBm7nEx/zVTQOxZzSv6HKxNOwSVaU4MfBG7WTkrL5PCjgVu0kCf2i ydBkY4FZYn5mBwlhmGvRmjtGbbzAEf7IKrwL3TdAS5QrjEuGifw//t3SIDMtgI/8wB60 5jjqRSBxmRvFIqreEJO4muSiUV2R0Dzj8dkDi91GeUuttnDtAgzBfyheh4mChDRzKLjO W7dg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678533920; h=cc:to:subject:message-id:date:mime-version:references:in-reply-to :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=GI2Mq2oBw8kOVd/VwjpkU/5ZReZ9/pinxlgiFqVkJms=; b=FBgrfmRff9qKVGaf+cZYL75qDlW57n0xzGjKHm8hjwjH/ase2Gc4JdC5jORBk/wYNM nbv0+V9Ihtu6lHjKTU2uc0ybZcGVcCufnKE3jYCb0GAwdrza43L2rGN/mxVNzcjxV720 DPHZEc4wrsPfjekFNMHGpfT66Vbse8quNv7vqgVAblmTnTR6209lCEzuzD+fBCJ2xhLc 8YjfKeGWXkkvMhfRbBT6vO9glYAgT/7FZlq/fy5gkkmX2lnRSMAcFjajkTKQn6T9Q7wY d0aEByqtDlb/i2YAXb2B7FzBfLI/oIkMELp9XdZ8Jka7elBza0re2B+P1EfFKo01i9bZ TPQw==
X-Gm-Message-State: AO0yUKUoLVayompQ0iq2U2d0Zj9/qEmAWdxjeJCakKOiA8bVe3u6JJ8N XbaQt+IeDwpGKrPbna3gUbM3yVSNoMwNdo9U++C8woUi
X-Google-Smtp-Source: AK7set8hlnDR/7g6kaF67m8r3AfnjvuS9AATltwj0D10Q2KBUfoYig4dLhvjAKCCBHHABhojSVb57g8F5TWtA7Lz+G4=
X-Received: by 2002:a63:7356:0:b0:507:8088:9e0d with SMTP id d22-20020a637356000000b0050780889e0dmr4023480pgn.7.1678533920490; Sat, 11 Mar 2023 03:25:20 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Sat, 11 Mar 2023 03:25:19 -0800
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <CAH6gdPz+WUMTot116bWFwxBF1RkFCg0DRfoX9Py8tdEwyQ4JBA@mail.gmail.com>
References: <CAMMESsyqvrTH70NXGBpB9DLW6VHvpyY8TSm2m_rovXoxZKPyVQ@mail.gmail.com> <7A7004BC-FD6B-4159-85D0-AEA1FB047788@gmail.com> <CAMMESsyp_7VSwE5geAKagQJ5vaJCTDmQgYwTSFr2Kfwr7Njn=A@mail.gmail.com> <CAMMESswkD0FkcmgsDjp80rcg3k9JyD7v8ZdCcn5r+WtViynHDw@mail.gmail.com> <CAMMESszyqfb9aRKd6_ajHRf0bs7GCNLY2J7aXns-G5qTgzR50A@mail.gmail.com> <CAH6gdPz+WUMTot116bWFwxBF1RkFCg0DRfoX9Py8tdEwyQ4JBA@mail.gmail.com>
MIME-Version: 1.0
Date: Sat, 11 Mar 2023 03:25:19 -0800
Message-ID: <CAMMESsxJtCFeH1i8UYwc9EdJpAb-mMD+sqQxbHwMwbPJ3ayOdA@mail.gmail.com>
To: Ketan Talaulikar <ketant.ietf@gmail.com>
Cc: draft-ietf-lsvr-bgp-spf@ietf.org, Acee Lindem <acee.ietf@gmail.com>, Victor Kuarsingh <victor@jvknet.com>, "lsvr@ietf.org" <lsvr@ietf.org>, lsvr-chairs@ietf.org
Content-Type: multipart/alternative; boundary="000000000000130b8b05f69e22ec"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsvr/1j-H-HlpuXA0wE-wtOzgVR3zCF8>
Subject: Re: [Lsvr] AD Review of draft-ietf-lsvr-bgp-spf-19
X-BeenThere: lsvr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Link State Vector Routing <lsvr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsvr>, <mailto:lsvr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsvr/>
List-Post: <mailto:lsvr@ietf.org>
List-Help: <mailto:lsvr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsvr>, <mailto:lsvr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Mar 2023 11:25:23 -0000

Hi!

Yes, that was my original suggestion too.

I don’t know.  I was thinking of the implementation (even if I don’t code!
;-)   Is it easier to always check a TLV the same way or for specific
AFI/SAFI?  In this case it may ok since BGP SPF has to do semantic checking.

I’m fine either way.

Alvaro.

On March 11, 2023 at 12:39:27 AM, Ketan Talaulikar (ketant.ietf@gmail.com)
wrote:

Hi Alvaro,

I see that BGP-SPF is a new/separate SAFI from BGP-LS and these two SAFIs
only share the TLVs. So, I don't see any issue with BGP SPF using the same
ASN TLV as BGP-LS as long as it says in the procedure that the "real" ASN
is what is encoded in the TLV.

The same goes for any other BGP-LS TLV that is used in a way by BGP-SPF
that deviates from the BGP-LS usage. Wouldn't that be a good way to go
about this?

Thanks,
Ketan


On Sat, Mar 11, 2023 at 12:44 AM Alvaro Retana <aretana.ietf@gmail.com>
wrote:

> Given Ketan’s reply in the other thread, it may be cleaner to request
> a new TLV for BGP SPF ASN.
>
> Alvaro.
>
> On March 10, 2023 at 7:02:09 AM, Alvaro Retana wrote:
>
> > 5.2. Extensions to BGP-LS
> >
> > The format of TLV 512 is defined in rfc7752bis, when used in a
> > BGP-LS-SPF NLRI the content MUST be as follows:
> >
> > Autonomous System: Opaque value (32-bit AS Number). The
> > value MUST be set to the AS Number associated with the BGP
> > process originating the link-state information.
> >
>

v2.23.0 | Report a Bug | By Email