Re: [Idr] [Lsvr] Issue 2: Auto-configuration Requirements - draft-xu-idr-neighbor-autodiscovery-requirements

Randy Bush <> Mon, 10 June 2019 22:36 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A9EE912004A; Mon, 10 Jun 2019 15:36:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id uVhNmcdAGF7J; Mon, 10 Jun 2019 15:36:02 -0700 (PDT)
Received: from ( [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 07025120025; Mon, 10 Jun 2019 15:36:02 -0700 (PDT)
Received: from localhost ([] by with esmtp (Exim 4.90_1) (envelope-from <>) id 1haStU-0003cZ-0z; Mon, 10 Jun 2019 22:36:00 +0000
Date: Mon, 10 Jun 2019 15:35:59 -0700
Message-ID: <>
From: Randy Bush <>
To: Robert Raszuk <>
Cc: Interminable Discussion Room <>,
In-Reply-To: <>
References: <020201d51fc2$e8b748e0$ba25daa0$> <> <>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/26.2 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: <>
Subject: Re: [Idr] [Lsvr] Issue 2: Auto-configuration Requirements - draft-xu-idr-neighbor-autodiscovery-requirements
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 10 Jun 2019 22:36:05 -0000

> BGP is opaque to all of this. It just by mistake happens to be overused
> today also here, but this will be fixed with time.

build an extensible protocol and the resume builders will come.  one of
my favority postel quotes

    It's perfectly appropriate to be upset.  I thought of it in a
    slightly different way--like a space that we were exploring and, in
    the early days, we figured out this consistent path through the
    space: IP, TCP, and so on.  What's been happening over the last few
    years is that the IETF is filling the rest of the space with every
    alternative approach, not necessarily any better.  Every possible
    alternative is now being written down.  And it's not useful.

and, if we look at dns, it does not get fixed over time.  the best we
get is the rate of embellisment slows.