[New-wg-docs] I-D Action: draft-ietf-idr-bgp-bestpath-nh-selection-00.txt

internet-drafts@ietf.org Thu, 24 September 2026 15:46 UTC

Received: by mx.ietf.org (Postfix) id 5C03444 for <new-wg-docs@ietf.org>; Thu, 24 Sep 2026 15:46:24 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ietf.org; s=mail; t=1790264784; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=iczm1SlUGlEm3lH4VuLtKJr5x9409FRv77SNiWMp7rU=; b=jH0kR13UIv7dbWVQiMNPWQRYlWQ6z8a9gQYVoKltRNjG9up1feIQSEQCq56Cmsx05+GZOd X/fVYC4lHHLJLVVOPsc6GgY1P9PytwFbQoHjHmax+VKnhx01R4gLJknfmKQXq6w1buZdz7 brnLahsPRGwGt+Na1/PzOyn5n/nCOaY=
Authentication-Results: ORIGINATING; auth=pass smtp.auth=mail2@ietf.org smtp.mailfrom=internet-drafts@ietf.org
Received: from [10.244.9.157] (gaia.k8s.ietf.org [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 0694F139C35FE for <new-wg-docs@ietf.org>; Thu, 24 Sep 2026 08:46:24 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: new-wg-docs@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.77.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <179026478394.296569.5737132630788983454@dt-datatracker-69f6c78549-jvtvd>
Date: Thu, 24 Sep 2026 08:46:23 -0700
Message-ID-Hash: CL3NP45HQ5NSOLGEXAVUNLZUWPEV4ZD7
X-Message-ID-Hash: CL3NP45HQ5NSOLGEXAVUNLZUWPEV4ZD7
X-MailFrom: internet-drafts@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.10
Subject: [New-wg-docs] I-D Action: draft-ietf-idr-bgp-bestpath-nh-selection-00.txt
List-Id: "New (-00) Working Group Documents" <new-wg-docs.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/new-wg-docs/pWNUe0g2OCRWvEa6QMeM7efb_do>
List-Archive: <https://mailarchive.ietf.org/arch/browse/new-wg-docs>
List-Help: <mailto:new-wg-docs-request@ietf.org?subject=help>
List-Owner: <mailto:new-wg-docs-owner@ietf.org>
List-Post: <mailto:new-wg-docs@ietf.org>
List-Subscribe: <mailto:new-wg-docs-join@ietf.org>
List-Unsubscribe: <mailto:new-wg-docs-leave@ietf.org>

Internet-Draft draft-ietf-idr-bgp-bestpath-nh-selection-00.txt is now
available. It is a work item of the Inter-Domain Routing (IDR) WG of the IETF.

   Title:   BGP best path next-hop selection enhancements
   Authors: Olivier Vroonen
            Jie Dong
   Name:    draft-ietf-idr-bgp-bestpath-nh-selection-00.txt
   Pages:   23
   Dates:   2026-09-24

Abstract:

   BGP [RFC4271] has originally been designed to carry IPv4 routing
   information over the Internet.  IP routing being "hop-by-hop" in
   nature, NEXT_HOP which purpose is to carry the address of the next
   router to send the IP packet to.  In BGP, the next-hop may not be a
   directly connected router, hence, when evaluating paths, a BGP
   speaker must determine if the next-hop is resolvable and, if so,
   determine the internal cost to reach it.

   The incremental use of tunneling technologies to carry traffic
   between routers (e.g.: GRE, MPLS, SR-MPLS, SRv6...) may violate the
   assumption that the address carried in the NEXT_HOP is representative
   of the actual forwarding next-hop.  These technologies decouple the
   BGP control-plane's view of the next-hop from the data-plane's actual
   forwarding endpoint.  This document describes the problems that arise
   from this decoupling.  These problems include sub-optimal path
   selection, incorrect resolvability tracking of the forwarding path
   leading to traffic drop or misrouting, and others.  This document
   specifies how BGP obtains resolvability, preference, metric, and
   tracking information from resolution of the forwarding path and uses
   those values as inputs to BGP path selection.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-bestpath-nh-selection/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-idr-bgp-bestpath-nh-selection-00.html

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts