IETF Logo Mail Archive

Re: [Bgp-autoconf] A conference call in next week to discuss BGP autoconf requirements?

"Randy Bush" <randy@psg.com> Mon, 24 February 2020 20:14 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 CF9323A1250 for <bgp-autoconf@ietfa.amsl.com>; Mon, 24 Feb 2020 12:14:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 CeZ64DwIdFdX for <bgp-autoconf@ietfa.amsl.com>; Mon, 24 Feb 2020 12:14:40 -0800 (PST)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) (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 D6DFE3A0EB8 for <bgp-autoconf@ietf.org>; Mon, 24 Feb 2020 12:14:40 -0800 (PST)
Received: from [198.180.150.2] (helo=mail.rg.net) by psg.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93 (FreeBSD)) (envelope-from <randy@psg.com>) id 1j6K7k-000EY7-GF; Mon, 24 Feb 2020 20:14:40 +0000
Received: from 162-195-241-81.lightspeed.sntcca.sbcglobal.net ([162.195.241.81] helo=[192.168.56.1]) by mail.rg.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from <randy@psg.com>) id 1j6K7j-0003RY-GB; Mon, 24 Feb 2020 20:14:39 +0000
From: "Randy Bush" <randy@psg.com>
To: "Robert Raszuk" <robert@raszuk.net>
Cc: bgp-autoconf@ietf.org
Date: Mon, 24 Feb 2020 12:14:38 -0800
X-Mailer: MailMate (1.13.1r5671)
Message-ID: <50C2C01B-FA66-4217-9E92-8EBBCC52E27C@psg.com>
In-Reply-To: <CAOj+MMEQSMinStu_w6cuTHFUw-qOLyv7r6VEbvem1ezS1GubhQ@mail.gmail.com>
References: <70e313e9faec408b85c6b29cff0be23f@huawei.com> <CAOj+MMG2wLNf-1sD+RbTCxocFsPViASr47vy-6TZCeFOhjTSmw@mail.gmail.com> <a674af06587440d4b2143961084680cd@huawei.com> <CAOj+MMFhbXOUmEnQs7WHJWAhkY3A--KVs3sUM4jHu9sMTEQznw@mail.gmail.com> <d29ee4053a8046049381874b6aa28134@huawei.com> <CAOj+MMG2RGT_fQfh+tty654L6x88qRrr83NJRi5UOXV_bEWZqw@mail.gmail.com> <m2blpnzs8t.wl-randy@psg.com> <CAOj+MMGVUDBQ9AGLPuSGSiQ9ni-r+j=NbnYTWxw=Xv+53Ls0vg@mail.gmail.com> <9D154F94-E6FB-4400-BD45-A96D34FBA2EE@psg.com> <CAOj+MMEQSMinStu_w6cuTHFUw-qOLyv7r6VEbvem1ezS1GubhQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/bgp-autoconf/zz3XN4olr23S7zqTVAecKKQpsCU>
Subject: Re: [Bgp-autoconf] A conference call in next week to discuss BGP autoconf requirements?
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, 24 Feb 2020 20:14:42 -0000

etherpad is not owned by a mega, and we have one already

v2.8.7 | Report a Bug | By Email