Re: [Bgp-autoconf] Short comparison of the different documents.

Randy Bush <randy@psg.com> Tue, 24 March 2020 23:03 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 D20263A07E2 for <bgp-autoconf@ietfa.amsl.com>; Tue, 24 Mar 2020 16:03:52 -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 pDqoxOZFMM_v for <bgp-autoconf@ietfa.amsl.com>; Tue, 24 Mar 2020 16:03:51 -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 7CBC73A07D5 for <bgp-autoconf@ietf.org>; Tue, 24 Mar 2020 16:03:51 -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 1jGsaL-0008Ms-TJ; Tue, 24 Mar 2020 23:03:50 +0000
Date: Tue, 24 Mar 2020 16:03:49 -0700
Message-ID: <m2369xz76y.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Warren Kumari <warren@kumari.net>
Cc: bgp-autoconf@ietf.org
In-Reply-To: <CAHw9_i+0rDUJOR3mAMAh9+whaKX0Koc_VaibbfX1zRzocOAvhw@mail.gmail.com>
References: <CAHw9_i+0rDUJOR3mAMAh9+whaKX0Koc_VaibbfX1zRzocOAvhw@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/15wnlx1dyLuRol-HtIs2FUprw7g>
Subject: Re: [Bgp-autoconf] Short comparison of the different documents.
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: Tue, 24 Mar 2020 23:03:53 -0000

ace,

so i have been sitting on this for a month, trying to think how to be
simple about this

draft-ymbk-lsvr-l3dl-ulpc was not directly intended for this.  it is a
layer two protocol to go with l3dl.  i think we probably want a layer
three protocol, though there are discovery issues.  btw, for loopback
peering, pass the forwarding setup in the attribute list.  though you
can discover that loopbacks are present, you re not going to discover
that loopback bgp peering is desired, and over which loopbacks (zing).

unfortunately draft-acee-idr-lldp-peer-discovery will need lldpv2 to get
reasonable pdus.  i am trying to help the lldpv2 work over in 802.1.  i
do not understand ieee processing pacing.  but if it took idr eight
yesas to change a constant 4,096 to 64k, i suspect i may not have the
patience for ieee (actually i was an ieee tag chair back in the early
'80s) :)

so i think we have some work to do.  but that's why we get the big bucks
or won.  settling the requirement parameters and limits up front is
important.  i see the extant drafts as examples and a source for ideas,
not competitors for a solution.

randy