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

Randy Bush <randy@psg.com> Mon, 24 February 2020 19:43 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 14BD23A11F7 for <bgp-autoconf@ietfa.amsl.com>; Mon, 24 Feb 2020 11:43:02 -0800 (PST)
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 zoQIUHhcEmV2 for <bgp-autoconf@ietfa.amsl.com>; Mon, 24 Feb 2020 11:43:00 -0800 (PST)
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 CCA9C3A121E for <bgp-autoconf@ietf.org>; Mon, 24 Feb 2020 11:43:00 -0800 (PST)
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 1j6Jd5-00031P-2W; Mon, 24 Feb 2020 19:42:59 +0000
Date: Mon, 24 Feb 2020 11:42:58 -0800
Message-ID: <m2blpnzs8t.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Robert Raszuk <robert@raszuk.net>
Cc: bgp-autoconf@ietf.org
In-Reply-To: <CAOj+MMG2RGT_fQfh+tty654L6x88qRrr83NJRi5UOXV_bEWZqw@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>
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/bYqqFPW5z9_dEWO810xVLDQy9S0>
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 19:43:06 -0000

> So who exactly from those who proposed a documents in this space and is
> part of the DT based in Asia ?

i bounce back and forth, was in tokyo last week, californica this

i do congratulate the group on the longest thread i have seen in a long
time discussing a con call.  and i have at least three con calls a week
with particupants in emea, noam, and asia (and sometimes points south).

there are generally two slots which work

    UTC 22:00
    CET 23:00
    JST 07:00+1
    EST 17:00
    PST 14:00

and

    UTC 14:00
    CET 15:00
    JST 23:00
    EST 09:00
    PST 06:00

yes, someone has to suffer.  the world is round; get over it.

randy