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

Robert Raszuk <robert@raszuk.net> Fri, 21 February 2020 22:21 UTC

Return-Path: <robert@raszuk.net>
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 377061200C1 for <bgp-autoconf@ietfa.amsl.com>; Fri, 21 Feb 2020 14:21:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=raszuk.net
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 KKsnyq3r_AWW for <bgp-autoconf@ietfa.amsl.com>; Fri, 21 Feb 2020 14:21:13 -0800 (PST)
Received: from mail-oi1-x233.google.com (mail-oi1-x233.google.com [IPv6:2607:f8b0:4864:20::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1628F12008F for <bgp-autoconf@ietf.org>; Fri, 21 Feb 2020 14:21:13 -0800 (PST)
Received: by mail-oi1-x233.google.com with SMTP id r137so3167225oie.5 for <bgp-autoconf@ietf.org>; Fri, 21 Feb 2020 14:21:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=lXYQJDzu+Lcsq7xxnj9G3YiLHfJG7N0ZMkmGWk++Vqk=; b=Nhrt+RFDTti/5lMFt9K/AnoMzXn/x2yZecyuxpF3IOy/alzbC9BD27W0lXEiBe9t72 w+5AMgIcDTi0YXWs9d0GoTWPq3IjUhQsC+XnUIca7Cfr2rhqpK/yTRsKA+qaSwzaUZVf JYj7jDV6U4D7/YmyUEvkfCeVtWimXW4nuLskbFtfBuJ18rb5paKAvwvobRhJyrRLMXGN mUFBgj/pr+QyHG/Mbg371VU6sNnO5mf160h8KB6dFiFRDks8clCNcSNqti5ytTPOV771 R7Bz4tWKb6/oUpg+MiH0fM1fXkL6Hw3r2Tu5LS+6dyyF1FessAXC1HGItneu1IJikmGF aY0w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=lXYQJDzu+Lcsq7xxnj9G3YiLHfJG7N0ZMkmGWk++Vqk=; b=nMxt+wIiDkn6n8CnHkGgWkadSa1qIoENtEn1Q1u375TNaIcQrc4le3Mm6wh+IJYdeL EEgfqAcshfWvf3u01Vv0ik3+HYHcRT8Zg1YILeT5qGiBqtOuAB0P0LjU6KzJRKYLXNhF 67uEMdswLlZGN1H0xjimmtsqqtKfsh4pUJ5luEpqyEsZdwDj7jAOod7PJTUrnaIb51Pr MokyXZtVbZcblgMqkFKMrHQVjDkfk2XekxCrv5ieuJWfGmnd16Xj2e6LgxzVm/wLVjzr xEFkWmMiFPOA23lwLnwq9HIYRx4FAPMEKsGUMM3zSYyS7SCOks941POs73D/mKpnwcSo oJkA==
X-Gm-Message-State: APjAAAXPdxPvnDA7+D4G0PWcjjD1BhzD003RPxv6FNv/6jSHqoof5KK+ LdwpbCmw348RyxuInbXWFpWJilWTWM4y5banyw6HKA==
X-Google-Smtp-Source: APXvYqzrBWUamzZ1DU0JbggwQS1/A06KeHGffWe+yWrAXwIcTrQGzWH6AlOPoIdIn8d1gB6wYaSQQDPVQSkvZIul2mI=
X-Received: by 2002:aca:c7ca:: with SMTP id x193mr3910035oif.70.1582323672352; Fri, 21 Feb 2020 14:21:12 -0800 (PST)
MIME-Version: 1.0
References: <70e313e9faec408b85c6b29cff0be23f@huawei.com>
In-Reply-To: <70e313e9faec408b85c6b29cff0be23f@huawei.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Fri, 21 Feb 2020 23:21:03 +0100
Message-ID: <CAOj+MMG2wLNf-1sD+RbTCxocFsPViASr47vy-6TZCeFOhjTSmw@mail.gmail.com>
To: "Dongjie (Jimmy)" <jie.dong@huawei.com>
Cc: "bgp-autoconf@ietf.org" <bgp-autoconf@ietf.org>, "idr-chairs@ietf.org" <idr-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006919cd059f1d704d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bgp-autoconf/ziEcw6mdTbCudWdzxDzSIHD1ECE>
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: Fri, 21 Feb 2020 22:21:17 -0000

May we have it 8:00-15:00 PST instead ?

Also what can't be discussed over email ?

Thx,
R.

On Fri, Feb 21, 2020 at 11:06 AM Dongjie (Jimmy) <jie.dong@huawei.com>
wrote:

> Dear all,
>
>
>
> The IETF 107 meeting is approaching, we need to make more progress to
> reach consensus on the requirements (for the DC case first), then we could
> review the candidate solutions about how they match the requirements.
>
>
>
> Based on the current mail list activity, it seems a conference call may
> help us to have more efficient discussion. Thus I’d suggest we arrange a
> 1-hour conference call in next week. I assume many of our team members are
> located in (UTC+8) and (UTC-8), thus a possible meeting time could be the
> 9:00 (UTC+8), which is 17:00 (UTC-8) in the previous day.
>
>
>
> Here is the doodle poll for the meeting time, I also added other potential
> time slots, please respond to it by end of this weekend, thanks.
>
>
>
> https://doodle.com/poll/6de9ei4iuubxs9ya
>
>
>
> Once the meeting time is determined, we also need some help to setup the
> meeting. I’m not sure whether we could use the WGs Webex account for the
> design team conference call, will check with the chairs. If not, I’d
> appreciate if someone could help with this. Thanks in advance.
>
>
>
> Best regards,
>
> Jie
> --
> Bgp-autoconf mailing list
> Bgp-autoconf@ietf.org
> https://www.ietf.org/mailman/listinfo/bgp-autoconf
>