[spring] Re: [Idr] S-BFD for SR-TE policies advertised by BGP?
Robert Raszuk <robert@raszuk.net> Fri, 08 August 2025 16:30 UTC
Return-Path: <robert@raszuk.net>
X-Original-To: spring@mail2.ietf.org
Delivered-To: spring@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id EE0D251C359B for <spring@mail2.ietf.org>; Fri, 8 Aug 2025 09:30:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=raszuk.net
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 bHuBrGM0iKPu for <spring@mail2.ietf.org>; Fri, 8 Aug 2025 09:30:58 -0700 (PDT)
Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com [IPv6:2a00:1450:4864:20::52c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 7FC6451C358A for <spring@ietf.org>; Fri, 8 Aug 2025 09:30:58 -0700 (PDT)
Received: by mail-ed1-x52c.google.com with SMTP id 4fb4d7f45d1cf-61580eb7995so4926878a12.0 for <spring@ietf.org>; Fri, 08 Aug 2025 09:30:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; t=1754670657; x=1755275457; 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=OZHf4H279p/QyVT2uPFdVWmAP7Uum5cYjeIT38RBV6w=; b=EPXC8gPbmrIMAxcOtwiHKk78jHpkVNLdoFq8EJq19cYKXiOlYGxBeN2zJCtWGhOt8+ VQS1RREw9BXsXCn6x9eTrFHBSFmIXERiA75n0xYkqNxl1R7Uij4bhJf5xoHA6yQ2S9yU g/vIlEMJVRgR2VsnffjmhwAJaYyDvd5wZFrgljlbO08TKAuGAqC0ElUMCBGcK1os3Xno rTbH/EmY4CO5ijs+y9JGVBJtaOvT8/qATCYeCBp6X+xFNUqxDG/VyDRCHnderK5KR76Q lfvSbmg06ZDqVoJxbFl+/FLovQxxdzvRQ+4Ai/klbMeR49Wp/T0aeV8wkkSw2V6QgVH2 tLBw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1754670657; x=1755275457; 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=OZHf4H279p/QyVT2uPFdVWmAP7Uum5cYjeIT38RBV6w=; b=G7Lr3i4wWwzzJzHbfMjeg55HRTqzTe5uwlrHyfAk891dkU7iw69lpVfWo5Yc+EzG+r KntDba+mfm6Ic39x1y5Npes1Ox8LZ2FSV0TVYcBcL6p1j4+pe3STsedsar2DbEieneaR y9fJTD5tgJRegg8VqyT94aSu7SGeymBQ1jDLDA9IrKX8P0zVj+mKSfsL2eXWolkjn0y3 A5LWoAEslfjdAyiNsZ2EJ71UF0C58HeJvwgLf3EUijm2nbwFeQ3/qbL1XXbM9bkDP3rh Efc1hVOdgKJDxbvQxVZbAD7RHj4weu5Gh4BWiB9SCF6pk8kvPG8LS4LQ4IrjbXMOHiRc z/CQ==
X-Forwarded-Encrypted: i=1; AJvYcCXSUvL4oQBI5baqW9MYKAGpTK16bHzycln2ofjhg5JlOtyVvgsitGLQnTqtkVnj0dCX2SHXrl8=@ietf.org
X-Gm-Message-State: AOJu0YzyRt9PIklNn6vV3pSZDpeE+a3Bx9oE8tqK21qkc4ZP/NiHWpZZ xu6Nf0jdGFqvQMir6AIpj/n1M5Dp5aRfWJul8LLMTAEKED9O5VuiOrfKD+pAHDlfiU2hnf7CIWn 1ovKZzvaedkV1rFj2p5EepBS3AluTwpK+vW7cVc7d+g==
X-Gm-Gg: ASbGncvdZFTlr4y0Kzbec7GbktUpUrYmLJLC5fFfyib85f6BMcjOa9UfRxXtXnaC3Mx Y+gU/RhevFen3DK41mmG5SFiyfbkLemiY3/WZLrJezIoKNLgBqI4d4eio9TSKhzbGtujmR+chfQ fg9+eS1o8UHXWFlGQXodPHvRMD/GWz+IxT23aV25bTrCcHf3VywFF0vXsuus5cIL7/wTQEKxZxy tYsW1E=
X-Google-Smtp-Source: AGHT+IEyzpvhddVw2hc6WU5RLVQ0dF68yUYmLU9UQsBpOCQfjX4zYntjrM2uAR+1ysUh2qUBPrg6K5xkVy3yIlmZEJ4=
X-Received: by 2002:aa7:d84e:0:b0:614:f9f8:7806 with SMTP id 4fb4d7f45d1cf-617b38f07aemr4871590a12.13.1754670656890; Fri, 08 Aug 2025 09:30:56 -0700 (PDT)
MIME-Version: 1.0
References: <CAEBHQ-MbJKm+UWNCTe27bCzhzRNej3YEOdW=y83LdSTqdoQtgg@mail.gmail.com>
In-Reply-To: <CAEBHQ-MbJKm+UWNCTe27bCzhzRNej3YEOdW=y83LdSTqdoQtgg@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Fri, 08 Aug 2025 18:30:45 +0200
X-Gm-Features: Ac12FXyRglkRiEewvVvX8M9E_Sx1Emw8XwPDHB-o9QFYQTmjsGKG-MwGcl8mGig
Message-ID: <CAOj+MMH6nFc25kX7gw+Oo35dbk2YVF2PGLamO65Ph6sfdPqvnw@mail.gmail.com>
To: Dmytro Shypovalov <dmytro@vegvisir.ie>, SPRING WG <spring@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000033b7eb063bdd19f8"
Message-ID-Hash: W6YTPKT4LJWZGMG3NMBO6ATP6DV72HLW
X-Message-ID-Hash: W6YTPKT4LJWZGMG3NMBO6ATP6DV72HLW
X-MailFrom: robert@raszuk.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-spring.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: idr@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [spring] Re: [Idr] S-BFD for SR-TE policies advertised by BGP?
List-Id: "Source Packet Routing in NetworkinG (SPRING)" <spring.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/cKAyhe7FQuMh-j3xBqRVDFnh7Vg>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Owner: <mailto:spring-owner@ietf.org>
List-Post: <mailto:spring@ietf.org>
List-Subscribe: <mailto:spring-join@ietf.org>
List-Unsubscribe: <mailto:spring-leave@ietf.org>
Hi, Valid question, but much more for SPRING WG (cc-ed) - how to signal desire for OAM in dynamically pushed SR policies or if not signalling it explicitly how to associate dynamically pushed SR policy with specific set of OAM actions. As you can see from SPRING WG list there are lots of documents on segment routing OAM for both MPLS and IPv6 data planes. I would not just pick S-BFD but solve this for all possible types of probes types in the unified way. Thx, Robert On Fri, Aug 8, 2025 at 4:16 PM Dmytro Shypovalov <dmytro@vegvisir.ie> wrote: > Dear IDR WG, > > I am a developer of an SR-TE controller, and my customer asked for this. > > I don't see any mention of BFD in draft-ietf-idr-sr-policy-safi, and > neither in the PCEP draft (I know, it's a different WG). Anyway BGP SR-TE > is the preferred method for my customer. > > Router implementations support S-BFD for locally configured policies, but > my understanding is that there no TLV to communicate to the router that > S-BFD is desired for this policy. > > Was this discussed at some point in the WG and discarded for some reason? > Were there any requests from operators? I think it's not a big change to > add a new TLV to the draft. > > Regards, > Dmytro > _______________________________________________ > Idr mailing list -- idr@ietf.org > To unsubscribe send an email to idr-leave@ietf.org >
- [spring] Re: [Idr] S-BFD for SR-TE policies adver… Robert Raszuk