IETF Logo Mail Archive

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

Randy Bush <randy@psg.com> Tue, 24 March 2020 22:38 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 8A25B3A0538 for <bgp-autoconf@ietfa.amsl.com>; Tue, 24 Mar 2020 15:38:01 -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 zUXd5GFPCzox for <bgp-autoconf@ietfa.amsl.com>; Tue, 24 Mar 2020 15:38:00 -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 3D8F03A0442 for <bgp-autoconf@ietf.org>; Tue, 24 Mar 2020 15:38:00 -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 1jGsBJ-0008I5-4a; Tue, 24 Mar 2020 22:37:57 +0000
Date: Tue, 24 Mar 2020 15:37:53 -0700
Message-ID: <m27dz9z8e6.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: <f465f49f53534122aaffe4d651e08467@huawei.com>
References: <b9c7b88960764dc4aa4454eac2310160@huawei.com> <m2blom1or0.wl-randy@psg.com> <f465f49f53534122aaffe4d651e08467@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/njoT5xXyWiqMu6FNCvOEFJmDkyU>
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: Tue, 24 Mar 2020 22:38:02 -0000

jimmy,

my apologies for my poor communication.  let me try with text

  Two prospective peers SHOULD be able to exchange arbitrary attributes
  to communicate things such as position or role in a topology, link
  speeds and/or loading, preferred time of day, favorite ice cream, etc.
  None of these example attributes are requirements, will be specified,
  given code points, etc. in the protocol design.  But there SHOULD be a
  protocol provision for communicating arbitrary attributes so that the
  operator may configure as needed for their environment.

hope that helps.

randy

v2.23.0 | Report a Bug | By Email