Re: [GROW] draft-raszuk-diverse-bgp-path-dist-01 working group document

Shane Amante <shane@castlepoint.net> Sun, 28 March 2010 18:23 UTC

Return-Path: <shane@castlepoint.net>
X-Original-To: grow@core3.amsl.com
Delivered-To: grow@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AEB4D3A6820 for <grow@core3.amsl.com>; Sun, 28 Mar 2010 11:23:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.262
X-Spam-Level:
X-Spam-Status: No, score=-0.262 tagged_above=-999 required=5 tests=[AWL=-1.207, BAYES_40=-0.185, DNS_FROM_OPENWHOIS=1.13]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zzAvMj5S7e8J for <grow@core3.amsl.com>; Sun, 28 Mar 2010 11:23:30 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by core3.amsl.com (Postfix) with ESMTP id 917273A65A6 for <grow@ietf.org>; Sun, 28 Mar 2010 11:23:28 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0) id B587C268674; Sun, 28 Mar 2010 12:23:54 -0600 (MDT)
Received: from mbpw.castlepoint.net (71.215.81.125 [71.215.81.125]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; Sun, 28 Mar 2010 12:23:54 -0600 (MDT) (envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=71.215.81.125; client-port=52967; client-dnsfail=71.215.81.125: name server failure; syn-fingerprint=65535:56:1:64:M1452,N,W1,N,N,T,S; data-bytes=0
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset="us-ascii"
From: Shane Amante <shane@castlepoint.net>
In-Reply-To: <002101cacc62$acbcdc00$06369400$@com>
Date: Sun, 28 Mar 2010 12:23:39 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <8165662D-8415-4071-B655-F336FB173AF6@castlepoint.net>
References: <002101cacc62$acbcdc00$06369400$@com>
To: Peter Schoenmaker <pds@lugs.com>
X-Mailer: Apple Mail (2.1077)
Cc: grow@ietf.org
Subject: Re: [GROW] draft-raszuk-diverse-bgp-path-dist-01 working group document
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Mar 2010 18:23:31 -0000

On Mar 25, 2010, at 15:32 MDT, Peter Schoenmaker wrote:
> Hello,
> 
> At the Stockholm IETF Robert Raszuk presented the draft on distribution of
> diverse BGP paths.  The question was put at the session on whether to adopt
> this document as working group document.
> 
> I would like to get the feedback of the list on if we should adopt this
> document.

Support/Yes.

I will add that it would be nice to briefly consider the operational implications of "accidentally" crossing route-reflector planes in a future version of this document.  Specifically, in the case of co-located route-reflector planes on /existing/ RR's, in my understanding the only thing keeping the first/primary plane separate from the secondary/backup plane is use of separate Loopback addresses on the iBGP sessions.  Thus, it is quite likely that an operator may get those mixed up when establishing iBGP session's for the first & second control planes.  A potentially simple, but effective, existing method to keep them separate is for operators to use different TCP MD5 passwords on iBGP sessions for the first, second, third, etc. sessions in order to ensure consistency of the control plane sessions.  This should still keep things in the realm of using existing, widely deployed tools with no modifications to existing code.  FWIW, I would be happy to contribute text if the authors and/or WG agree with the above approach.

-shane