IETF Logo Mail Archive

Re: [Bgp-autoconf] Progress report of design team on IDR virtual meeting

Randy Bush <randy@psg.com> Wed, 25 March 2020 13:15 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 588E43A0974 for <bgp-autoconf@ietfa.amsl.com>; Wed, 25 Mar 2020 06:15:17 -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 Pnqib0pZzMPu for <bgp-autoconf@ietfa.amsl.com>; Wed, 25 Mar 2020 06:15:16 -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 F0EA33A0779 for <bgp-autoconf@ietf.org>; Wed, 25 Mar 2020 06:15:15 -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 1jH5sG-00036j-89; Wed, 25 Mar 2020 13:15:12 +0000
Date: Wed, 25 Mar 2020 06:15:11 -0700
Message-ID: <m2bloky3s0.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: "Dongjie (Jimmy)" <jie.dong@huawei.com>
Cc: "bgp-autoconf@ietf.org" <bgp-autoconf@ietf.org>
In-Reply-To: <01a5724698784b3ca089f2849c245508@huawei.com>
References: <b9c7b88960764dc4aa4454eac2310160@huawei.com> <m2blom1or0.wl-randy@psg.com> <f465f49f53534122aaffe4d651e08467@huawei.com> <m27dz9z8e6.wl-randy@psg.com> <01a5724698784b3ca089f2849c245508@huawei.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/LU0t0Dess01zEFPnUFIjSYeTiSg>
Subject: Re: [Bgp-autoconf] Progress report of design team on IDR virtual meeting
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: Wed, 25 Mar 2020 13:15:18 -0000

jimmy,

> Thanks for your further clarification. Thus what you suggest is a
> generic capability to communicate arbitrary attributes according to
> the operators' need. Is my understanding correct?

yes.  i did point to how l3dl-ulpc does that.  [ not meant as an
argument to adopt l3dl ]

> Do you think such information exchange should happen in the peer
> autodiscovery/autoconf stage?

sure.  if and only if there are no predefined semantics, then it's just
some bits on the wire that the op can leverage.

randy

v2.8.7 | Report a Bug | By Email