[Idr] I-D Action: draft-ietf-idr-bgp-fwd-rr-02.txt

internet-drafts@ietf.org Sun, 17 March 2024 05:42 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 C01F7C180B48; Sat, 16 Mar 2024 22:42:31 -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
Cc: idr@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.8.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: idr@ietf.org
Message-ID: <171065415177.59997.7631576612994148063@ietfa.amsl.com>
Date: Sat, 16 Mar 2024 22:42:31 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/I5MT9UY7-k43lVW5e2k-Ar3KZJQ>
Subject: [Idr] I-D Action: draft-ietf-idr-bgp-fwd-rr-02.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Mar 2024 05:42:31 -0000

Internet-Draft draft-ietf-idr-bgp-fwd-rr-02.txt is now available. It is a work
item of the Inter-Domain Routing (IDR) WG of the IETF.

   Title:   BGP Route Reflector with Next Hop Self
   Authors: Kaliraj Vairavakkalai
            Natrajan Venkataraman
   Name:    draft-ietf-idr-bgp-fwd-rr-02.txt
   Pages:   9
   Dates:   2024-03-16

Abstract:

   The procedures in BGP Route Reflection (RR) spec RFC4456 primarily
   deal with scenarios where the RR is reflecting BGP routes with next
   hop unchanged.  In some deployments like Inter-AS Option C
   (Section 10, RFC4364), the ABRs may perform RR functionality with
   nexthop set to self.  If adequate precautions are not taken, the
   RFC4456 procedures can result in traffic forwarding loop in such
   deployments.

   This document illustrates one such looping scenario, and specifies
   approaches to minimize possiblity of traffic forwarding loop in such
   deployments.  An example with Inter-AS Option C (Section 10, RFC4364)
   deployment is used, where RR with next hop self is used at redundant
   ABRs when they re-advertise BGP transport family routes between
   multiple IGP domains.

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

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgp-fwd-rr-02

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-idr-bgp-fwd-rr-02

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