IETF Logo Mail Archive

Re: [Idr] BGP-LS and the like ...

Randy Bush <randy@psg.com> Thu, 21 June 2018 17:22 UTC

Return-Path: <randy@psg.com>
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 4EBEC130E9F for <idr@ietfa.amsl.com>; Thu, 21 Jun 2018 10:22:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 tTLLpZ8VmXC6 for <idr@ietfa.amsl.com>; Thu, 21 Jun 2018 10:22:33 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BEF0A130E8A for <idr@ietf.org>; Thu, 21 Jun 2018 10:22:30 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1fW3Hv-0001bY-Ot; Thu, 21 Jun 2018 17:22:27 +0000
Date: Thu, 21 Jun 2018 10:22:27 -0700
Message-ID: <m2tvpwyrzg.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Robert Raszuk <robert@raszuk.net>
Cc: Interminable Discussion Room <idr@ietf.org>
In-Reply-To: <CA+b+ERnS+b-OatPY+cnGX74Z+9yqF2AckgXAFnt1=osqELrdJA@mail.gmail.com>
References: <CA+b+ERnS+b-OatPY+cnGX74Z+9yqF2AckgXAFnt1=osqELrdJA@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/25.3 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/8Vg1-I2utvS9etMv-8BZ3HuqS8w>
Subject: Re: [Idr] BGP-LS and the like ...
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.26
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: Thu, 21 Jun 2018 17:22:35 -0000

> while maintaining previous opinion on BGP-LS in general the most what
> bothers me with this is the granularity of BGP machinery awarness of
> "stuff" it is subject to carry.
> 
> If we continue for every new IGP extension or SR policy extension see
> a corresponding BGP draft in order to carry it in BGP where do we end
> up in few months or years from now ?

no proof of termination and unbounded feature chase.  welcome to the
ietf, where this is a career extending feature.

> I am starting to have a feeling that this non core routing information
> transport over BGP is simply getting out of hand :) And of course many
> will correctly say that this started with introduction of
> multiprotocol extensions to BGP followed by original 2547 - but it
> seems that this trend is growing exponentially now.

i always thought all that stuff should have used dns instead

randy, who gave up whining about this long ago

v2.23.0 | Report a Bug | By Email