IETF Logo Mail Archive

Re: [Bgp-autoconf] Move forward with bgp autoconf requirements and design principle

Randy Bush <randy@psg.com> Mon, 06 July 2020 15:53 UTC

Return-Path: <randy@psg.com>
X-Original-To: bgp-autoconf@ietfa.amsl.com
Delivered-To: bgp-autoconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A9463A16CA for <bgp-autoconf@ietfa.amsl.com>; Mon, 6 Jul 2020 08:53:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=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 CzrF2N0WK3Be for <bgp-autoconf@ietfa.amsl.com>; Mon, 6 Jul 2020 08:53:34 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84B6B3A16C8 for <bgp-autoconf@ietf.org>; Mon, 6 Jul 2020 08:53:34 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.90_1) (envelope-from <randy@psg.com>) id 1jsTQv-0004Wh-Sf; Mon, 06 Jul 2020 15:53:30 +0000
Date: Mon, 06 Jul 2020 08:53:29 -0700
Message-ID: <m2pn98ej2e.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Robert Raszuk <robert@raszuk.net>
Cc: "Dongjie (Jimmy)" <jie.dong@huawei.com>, "bgp-autoconf@ietf.org" <bgp-autoconf@ietf.org>
In-Reply-To: <CAOj+MME75tzRUm2PasSWfxSvEcO3tUix2fPHT=jm8wOjgXa0Hw@mail.gmail.com>
References: <0d8841f4daf143439a237c91333744e4@huawei.com> <m2tv0172cl.wl-randy@psg.com> <6e6dca9ffe9b41839419715e1608ddef@huawei.com> <8d21cc950f784675a0f52fdf22f546e5@huawei.com> <CAOj+MME75tzRUm2PasSWfxSvEcO3tUix2fPHT=jm8wOjgXa0Hw@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/26.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/bgp-autoconf/YWg407B-tNfNCoq2RR445ceDUnA>
Subject: Re: [Bgp-autoconf] Move forward with bgp autoconf requirements and design principle
X-BeenThere: bgp-autoconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP autoconfiguration design team discussion list <bgp-autoconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bgp-autoconf>, <mailto:bgp-autoconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bgp-autoconf/>
List-Post: <mailto:bgp-autoconf@ietf.org>
List-Help: <mailto:bgp-autoconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bgp-autoconf>, <mailto:bgp-autoconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jul 2020 15:53:36 -0000

> The draft in question specifically adds WAN auto conf.

that was certainly not the intent; and it's not really there in the
words.  on the other hand, if we should keep an eye on the WAN as we
design the LAN, we should be aware of choices which might unnecessarily
restriict ourselves next year.

> Then the L3 peer auto discovery is just deferred to
> draft-ietf-lsvr-l3dl

also not intended.  i did ask for your help stitching multicast in, and
you declined.  perhaps you have time now.

> However reading thorough draft-ietf-lsvr-l3dl it is clear that it is not
> applicable to WAN.

it is not applicable to many things :)

as i said at the beginning, i do not think l3dl is really a serious
candidate here.  otoh, we would be silly if we did not keep an eye to
see if there are lessons to be learned from it.

[ fwiw, i think the scalability added to lsoe to become l3dl was not
  worth the complexity.  but that is a discussion for another universe ]

randy

v2.23.0 | Report a Bug | By Email