[Idr] I-D Action: draft-ietf-idr-sr-policy-metric-02.txt
internet-drafts@ietf.org Mon, 30 December 2024 07:37 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: idr@ietf.org
Delivered-To: idr@ietfa.amsl.com
Received: from [10.244.8.219] (unknown [104.131.183.230]) by ietfa.amsl.com (Postfix) with ESMTP id 4F228C14F61B; Sun, 29 Dec 2024 23:37:18 -0800 (PST)
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.31.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <173554423795.1003677.13814595800475379289@dt-datatracker-65f549669d-2xld9>
Date: Sun, 29 Dec 2024 23:37:17 -0800
Message-ID-Hash: XESZZ5GL7EKU5TKRIZXE7IJMEBEFQLBB
X-Message-ID-Hash: XESZZ5GL7EKU5TKRIZXE7IJMEBEFQLBB
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.9rc6
Reply-To: idr@ietf.org
Subject: [Idr] I-D Action: draft-ietf-idr-sr-policy-metric-02.txt
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/dk5Vj7GocGP8c0R-U5Rrrk32b7U>
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-02.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-02.txt
Pages: 8
Dates: 2024-12-29
Abstract:
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
routing.
The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-idr-sr-policy-metric/
There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-idr-sr-policy-metric-02
A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-idr-sr-policy-metric-02
Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts
- [Idr] I-D Action: draft-ietf-idr-sr-policy-metric… internet-drafts