Re: [Idr] BGP autodiscovery design team

Robert Raszuk <robert@raszuk.net> Thu, 05 December 2019 22:20 UTC

Return-Path: <robert@raszuk.net>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 503EE1200EF for <idr@ietfa.amsl.com>; Thu, 5 Dec 2019 14:20:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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] 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 5OW45Yw2JKej for <idr@ietfa.amsl.com>; Thu, 5 Dec 2019 14:20:39 -0800 (PST)
Received: from mail-qt1-x829.google.com (mail-qt1-x829.google.com [IPv6:2607:f8b0:4864:20::829]) (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 2FFD4120168 for <idr@ietf.org>; Thu, 5 Dec 2019 14:20:39 -0800 (PST)
Received: by mail-qt1-x829.google.com with SMTP id k11so5139624qtm.3 for <idr@ietf.org>; Thu, 05 Dec 2019 14:20:39 -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=pvCRhpdK2wxV4aK7d1UsdI7LeGWppu/7m0XdT4RGedA=; b=Sl98JHtNvgYJxusPWcQWs3dmoVp5oDGOlljC42dTsvjcccWpA5f/SkGdfdQTAf0VQ4 r9/9JX7ph/4ZgHvCLcMIgrJTkYPlqEuV6Oe3iqs3ZpqTAN0+pOqVOHS/RIgN9dzNeq75 nyyDOJke08yIMiUBXWSJ/QQF2Y3s3KD3b3eIh+lYmzQ/HyzOksb7322tPWgsGgdiCYaC SyZDJUxx/nz1TKsr6e3hm3VyDm3znNLBSdxrFywSG2kuqSmvTGbUx/KhYJpaczqZnQpA OpvXQ4vv9ogtmti9+8R5DqHZOcoS6OTpkmONt+eaHD779+NJdWYESV57ULG5+R0jyF0F Gz0A==
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=pvCRhpdK2wxV4aK7d1UsdI7LeGWppu/7m0XdT4RGedA=; b=qFG8Arr2WZ/Rj5+ZyWkGvNa1XCyQvNZtC87DTG/Rh26Jvk9lMvYL+Udot8ojzTjNNp SQ9WtSv2ivYcWFy4IF2JkbNz5ctUBtiYIh3elmXRbdu6EZRHlnMSZxBoYkn5LMGm9nOR 2BoJrdij9A4RmZATPeCoGB60M1XS5RSLqT3CmRQUvEEWkyis6oPx7YGaqsqv/ulqUwnZ gdIxyqnbSQGa41wuSxVquTFm+xE3O+KftjteOri0I0qtfRdeRDIL9rhvV9aExQpVnL8c jCAO2lC008AFsO+18rhlurKwe0BisAqFYMso4ED+2iNRi1ujddYthFaEpN9NEeYoogZr iX4Q==
X-Gm-Message-State: APjAAAXlkZTodU9EUYdVcWMNuxs3jzcJXoyWmXFKQHMTn6MzzkVuIl9/ NdRQAHZ/hip6FlMvvpLCKjyVK0/b0m/BYcSyKpW3TEyYvSpW9A==
X-Google-Smtp-Source: APXvYqzHk1hDMUdW3SZ5Ij/MVPqYYixLOYkn4CvWiKorElVbmxr2Bu2r++OE0LTnyTPfJuQUq/giGBOiZsvg4AcEy6s=
X-Received: by 2002:ac8:37d0:: with SMTP id e16mr9911055qtc.311.1575584438135; Thu, 05 Dec 2019 14:20:38 -0800 (PST)
MIME-Version: 1.0
References: <E7E38075-54F2-4F16-97BE-EE24943B5BFE@juniper.net>
In-Reply-To: <E7E38075-54F2-4F16-97BE-EE24943B5BFE@juniper.net>
From: Robert Raszuk <robert@raszuk.net>
Date: Thu, 5 Dec 2019 23:20:30 +0100
Message-ID: <CAOj+MMFMSc=MwWXp=_Gu3YAOUW4Poq9__eq_kBGHhN34sM4mHw@mail.gmail.com>
To: John Scudder <jgs=40juniper.net@dmarc.ietf.org>
Cc: idr wg <idr@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000bfc7720598fc56f9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/TSoa4csTTwobh9LTQs_Enh9-A8I>
Subject: Re: [Idr] BGP autodiscovery design team
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Dec 2019 22:20:41 -0000

John,

>  We are in the process of forming the team and hope to announce it soon.
We have many good
> volunteers already but if you didn’t know and do want to volunteer,
please contact Sue and me.

If such design team for unscoped "BGP autodiscovery" work gets formed
please add my name to the volunteer list.

Thank you,
Robert


On Wed, Dec 4, 2019 at 8:33 PM John Scudder <jgs=
40juniper.net@dmarc.ietf.org>; wrote:

> Hi All,
>
> I realized this morning that although we announced in the last meeting
> that we’re forming this design team, we never announced it on the list.
> This is to correct that mistake. Here’s the text of the slide we presented
> at the meeting (
> https://datatracker.ietf.org/meeting/106/materials/slides-106-idr-sessa-auto-discovery-design-team-chairs-00
> ):
>
> ---
> Autodiscovery
>
> • Clear interest in WG to work on this topic.
> • No clear consensus on a specific approach.
> • Proposals (four of them) progressively closer semantically, seems likely
> convergence can happen.
> • But, important differences remain.
>         • At least: transport (L2, L3), liveness, security, maybe multihop.
> • Chairs propose to charter a design team to close on a single proposal,
> by next meeting.
>         • Might build on one of the existing drafts, might be a new draft,
> up to the design team.
>         • Emphasis on pragmatism, OK to limit applicability (for example,
> to a single administrative domain).
> • Questions? Comments? Volunteers?
> —
>
> We are in the process of forming the team and hope to announce it soon. We
> have many good volunteers already but if you didn’t know and do want to
> volunteer, please contact Sue and me.
>
> Note that the design team will not make any binding decisions: as with all
> WG work, the WG has the final word, so any output of the DT will serve as
> input to the WG as a whole. (So even if you aren’t part of the DT, that
> doesn’t mean you won’t have a chance to be part of the process.)
>
> Thanks,
>
> —John
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>