[Idr] I-D Action: draft-ietf-idr-sr-policy-metric-01.txt

internet-drafts@ietf.org Mon, 17 June 2024 02:34 UTC

Return-Path: <internet-drafts@ietf.org>
X-Original-To: idr@ietf.org
Delivered-To: idr@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E4265C1CAF53; Sun, 16 Jun 2024 19:34:59 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.15.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <171859169991.45872.12987430506072623214@ietfa.amsl.com>
Date: Sun, 16 Jun 2024 19:34:59 -0700
X-MailFrom: internet-drafts@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-idr.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.9rc4
Reply-To: idr@ietf.org
Subject: [Idr] I-D Action: draft-ietf-idr-sr-policy-metric-01.txt
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/oadrWHohyb_wTo57g-uuL-YbbmQ>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Owner: <mailto:idr-owner@ietf.org>
List-Post: <mailto:idr@ietf.org>
List-Subscribe: <mailto:idr-join@ietf.org>
List-Unsubscribe: <mailto:idr-leave@ietf.org>

Internet-Draft draft-ietf-idr-sr-policy-metric-01.txt is now available. It is
a work item of the Inter-Domain Routing (IDR) WG of the IETF.

   Title:   BGP SR Policy Extensions for metric
   Authors: Ka Zhang
            Jie Dong
            Ketan Talaulikar
   Name:    draft-ietf-idr-sr-policy-metric-01.txt
   Pages:   8
   Dates:   2024-06-16


   SR Policy candidate paths can be represented in BGP UPDATE messages.
   BGP can then be used to propagate the SR Policy candidate paths to
   the headend nodes in the network.  After SR Policy is installed on
   the ingress node, the packets can be steered into SR Policy through
   route selection.  Therefore, route selection may be performed on the
   ingress node of the SR Policy.  If there are multiple routes to the
   same destination, the route selection node can select routes based on
   the local policy.  The local policy may use the IGP metric of the
   selected path, which is the IGP Metric of the SR Policy.  Thus the
   BGP UPDATE message needs to carry the metric of each segment list of
   the SR Policy Candidate Path, which can be used in path selection of

The IETF datatracker status page for this Internet-Draft is:

There is also an HTMLized version available at:

A diff from the previous version is available at:

Internet-Drafts are also available by rsync at: