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

Robert Raszuk <robert@raszuk.net> Mon, 24 February 2020 20:13 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 B4A853A1246 for <bgp-autoconf@ietfa.amsl.com>; Mon, 24 Feb 2020 12:13:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 jfZiV20kYwAo for <bgp-autoconf@ietfa.amsl.com>; Mon, 24 Feb 2020 12:13:33 -0800 (PST)
Received: from mail-oi1-x22d.google.com (mail-oi1-x22d.google.com [IPv6:2607:f8b0:4864:20::22d]) (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 4F5AE3A124A for <bgp-autoconf@ietf.org>; Mon, 24 Feb 2020 12:13:33 -0800 (PST)
Received: by mail-oi1-x22d.google.com with SMTP id b18so10215544oie.2 for <bgp-autoconf@ietf.org>; Mon, 24 Feb 2020 12:13:33 -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=u0Eqw5caeKaWSIRfCgCK+3WmKe/X89KFvK/RwJPkR/c=; b=en3kpS922eEZg7thscQEj1b++oYhJ0nxwJ+/Ouvhs4XQhCGPJXjBdtRauvzUt+7uGH gKyGWLUSzXmKC6Fq8xf8fp/WE8UzAVo48IGcdNpxzIUQ9zNgZs0CWqMEB/cCBa+VdqrK cy0oc5RqtRLfhTpryTCd18ot9lpRNozs7CohxAZdCXe8PspPZ7htlOLQnkYNOoLw9oyM A7dzLpFeMA9FJhhtgvJMWsOPmdJ+p23j1ewFG1QnYiuNHRXdbO4UqMI8InaNOIHCMVs0 vgnZ8nS8DW046JKltIILyEZHtnWMdjeh/72pa/95YT9hW4vUUC9OG0qr8h3qRbd4UzRA waWQ==
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=u0Eqw5caeKaWSIRfCgCK+3WmKe/X89KFvK/RwJPkR/c=; b=fjGikUFenWHOT0pBj8jZ9nbsZH3rI3ZegICPduCxcFhi2gNDn8O2CjhOwOrUYqnnHR e/F8BUV6osQpQGElzLXCbQKxx/FvDaSCuN5DqCYFEuSIV1gD1kTjlCrHJSfudMOgDZVM 9SMwy0DmP20XzOvuO5N73f8smVBU/zyI1CAly/41o1ws80OOjCiFUj9K7h9JFh2iv8Nx tE1rgd7sv37gHH9edLER+7lMovsuOGqc3sSMaE7hWCjmTQxV7Z9OXjPxIacxDhryTyp9 gYzStgJ5q93Pyn4OhW0GW1+Psn1h1UGq/R6nDw3Q0KOsutbt5mFyyxtjjES271aviOB9 FuDg==
X-Gm-Message-State: APjAAAXPO73DjLHyQS90QOU7UsGw9RJ1S1j0RQXU+oSTAxig0YIZlzeR pdLwLGswtuQHNaAAuiuBmU0/Tmod8cUruv6nD4mynQ==
X-Google-Smtp-Source: APXvYqwWsVxEngFBejTKHC0ZjQdZm5lAXwVTt0OSy839HEOEtBVCRlGT2ao0lGJJl7jGoCQhBoYwSnVphKdE/L9isM8=
X-Received: by 2002:aca:d985:: with SMTP id q127mr623335oig.132.1582575212517; Mon, 24 Feb 2020 12:13:32 -0800 (PST)
MIME-Version: 1.0
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>
In-Reply-To: <9D154F94-E6FB-4400-BD45-A96D34FBA2EE@psg.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Mon, 24 Feb 2020 21:13:21 +0100
Message-ID: <CAOj+MMEQSMinStu_w6cuTHFUw-qOLyv7r6VEbvem1ezS1GubhQ@mail.gmail.com>
To: Randy Bush <randy@psg.com>
Cc: bgp-autoconf@ietf.org
Content-Type: multipart/alternative; boundary="0000000000005f94e3059f5801d6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bgp-autoconf/2XeDdbfaSo1rr_WDBytwJ8ezrcA>
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:13:35 -0000

Just to clarify what I meant as far as "document" ..

It was an example of just a form of interactive whiteboard (gdocs) between
DT members. That's all.

>From my limited experience working remotely it does seem to work pretty
well.

I guess to make it seamless we could all provide a google IDs, create a
group and off we go interactive.

On Mon, Feb 24, 2020 at 9:08 PM Randy Bush <randy@psg.com> wrote:

> robert,
>
> > All times you provides are just perfect !
>
> been doing it for a few decades :(
>
> btw, those times need to be jittered if se asia and/or prc are on the
> call.  add india, and the suffering becomes serious.
>
> > PS. I still think we should prepare a bit better for such call in
> > terms of previously prepared interactive document.
>
> i do not think we are ready for any form of document.  you and i had a
> short discussion which ended up in a fairly extreme minimalist position.
> but no one else commented.  i think we need some sense of consensus on
> this before committing to a document; even such a short one.
>
> i also have to wonder that, if we can agree on a minimalist approach
> for datacenter, perhaps such minimalism would expand to a larger space.
> but i suspect this is overly optimistic.
>
> randy
>