Re: [Idr] draft-chen-bgp-redist - A Juniper Perspective
Jeffrey Haas <jhaas@pfrc.org> Sat, 21 August 2021 16:28 UTC
Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBDA03A1677; Sat, 21 Aug 2021 09:28:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wNpMcdkcBMGz; Sat, 21 Aug 2021 09:28:41 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 329253A1676; Sat, 21 Aug 2021 09:28:41 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 4F3FC1E27C; Sat, 21 Aug 2021 12:28:40 -0400 (EDT)
Date: Sat, 21 Aug 2021 12:28:40 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Jeff Tantsura <jefftant.ietf@gmail.com>
Cc: Enke Chen <enchen@paloaltonetworks.com>, idr@ietf.org, draft-chen-bgp-redist@ietf.org
Message-ID: <20210821162840.GF19054@pfrc.org>
References: <CANJ8pZ-mz8KuWBkgYjuKSRwTW2ycq2VkQKYRqnnFquPQEQ=GNg@mail.gmail.com> <5D874729-4FC1-4AD6-BD6C-BDC473B6B342@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <5D874729-4FC1-4AD6-BD6C-BDC473B6B342@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/S9g96yKlo83WEdrsNZdZVq4XOEs>
Subject: Re: [Idr] draft-chen-bgp-redist - A Juniper Perspective
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Sat, 21 Aug 2021 16:28:44 -0000
Jeff, On Fri, Aug 20, 2021 at 03:59:38PM -0700, Jeff Tantsura wrote: > Perhaps RFC5004/router-id (in densely meshed eBGP topologies) behavior deserves a good discussion as well. A topic I've discussed Sue in the past is we're in need of some documents discussing some BGP protocol intrinsics that really aren't well documented. The one you mention is an example of "your domain really needs to implement consistent route selection procedures". This is also a reminder that I have errata for RFC 5004 to file and keep forgetting to do so. -- Jeff
- [Idr] draft-chen-bgp-redist - A Juniper Perspecti… Jeffrey Haas
- Re: [Idr] draft-chen-bgp-redist - A Juniper Persp… Robert Raszuk
- Re: [Idr] draft-chen-bgp-redist - A Juniper Persp… Enke Chen
- Re: [Idr] draft-chen-bgp-redist - A Juniper Persp… Jeff Tantsura
- Re: [Idr] draft-chen-bgp-redist - A Juniper Persp… Jeffrey Haas
- Re: [Idr] draft-chen-bgp-redist - A Juniper Persp… Jeffrey Haas
- Re: [Idr] draft-chen-bgp-redist - A Juniper Persp… Jeff Tantsura