Re: [Idr] Mirja Kühlewind's No Objection on draft-ietf-idr-ix-bgp-route-server-11: (with COMMENT)

Jeffrey Haas <jhaas@pfrc.org> Mon, 20 June 2016 13:05 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 6F02F12D0B3 for <idr@ietfa.amsl.com>; Mon, 20 Jun 2016 06:05:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.328
X-Spam-Level:
X-Spam-Status: No, score=-3.328 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, 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 TamHUCspqVIR for <idr@ietfa.amsl.com>; Mon, 20 Jun 2016 06:05:10 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 7DF4312B05C for <idr@ietf.org>; Mon, 20 Jun 2016 06:05:10 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 00CAA1E1DF; Mon, 20 Jun 2016 09:11:12 -0400 (EDT)
Date: Mon, 20 Jun 2016 09:11:12 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Randy Bush <randy@psg.com>
Message-ID: <20160620131112.GE2950@pfrc.org>
References: <0DE7AB8E-4CFD-44C5-898F-47F48B542599@kuehlewind.net> <575F2704.3050509@foobar.org> <m237ogo5w1.wl%randy@psg.com> <CAL9jLaaCa9aUOw0HUfyrt05GTYL+yGZum1M=3_4r_E0nx4PqJg@mail.gmail.com> <A65A6088-433D-4200-B098-B2FFEB0A45CD@psg.com> <CAL9jLabgF=h9wSg4GoDoJiT76HcKK2DhpJv=ZxLws7LSs8RN3g@mail.gmail.com> <575FD94E.8030606@foobar.org> <m2inxckqr8.wl%randy@psg.com> <575FF3B9.3080501@foobar.org> <m2ziqnk8b1.wl%randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <m2ziqnk8b1.wl%randy@psg.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/DVBRanSm4fMq6uN09-tD1_nYTvk>
Cc: idr wg <idr@ietf.org>, Mirja Kuehlewind <ietf@kuehlewind.net>
Subject: Re: [Idr] =?iso-8859-1?q?Mirja_K=FChlewind=27s_No_Objection_on_draft-?= =?iso-8859-1?q?ietf-idr-ix-bgp-route-server-11=3A_=28with_COMMENT=29?=
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
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: Mon, 20 Jun 2016 13:05:11 -0000

On Wed, Jun 15, 2016 at 02:08:02AM +0900, Randy Bush wrote:
> > Does the proposed wording work for you?
> > 
> >> While it is technically possible to operate a route server which
> >> prepends its own AS to the AS_PATH, it is not recommended to do so
> >> because creating an undesirably longer AS_PATH may adversely affect
> >> the resulting network topology between the route server clients.
> 
> i suspect that the AD is competent to speak for herself.  but imiho this
> misses her point, why is the SHOULD not a MUST?  this says why it might
> be a MUST.  why allow the loophole?  i admit my example was baroque.

I am somewhat late in chiming in on this thread, but I'm also supportive of
making this a MUST.

If you're intending to inject your AS number into the path, then you're
acting as a standard BGP speaker, not a Route Server.

If the intent of the text in the current internet-draft is to leave wiggle
room for a device operating as a RS to also act as a standard BGP speaker
without RS functionality, I think that's unnecessary.

-- Jeff