IETF Logo Mail Archive

Re: [Bgp-autoconf] Kicking things off

"Dongjie (Jimmy)" <jie.dong@huawei.com> Thu, 30 January 2020 07:34 UTC

Return-Path: <jie.dong@huawei.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 E49191200C3 for <bgp-autoconf@ietfa.amsl.com>; Wed, 29 Jan 2020 23:34:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 aNwMxQOlNb94 for <bgp-autoconf@ietfa.amsl.com>; Wed, 29 Jan 2020 23:34:31 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 46CC51200D7 for <bgp-autoconf@ietf.org>; Wed, 29 Jan 2020 23:34:31 -0800 (PST)
Received: from lhreml703-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id A8CF8A91570413B15B01 for <bgp-autoconf@ietf.org>; Thu, 30 Jan 2020 07:34:27 +0000 (GMT)
Received: from nkgeml701-chm.china.huawei.com (10.98.57.156) by lhreml703-cah.china.huawei.com (10.201.108.44) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 30 Jan 2020 07:34:27 +0000
Received: from nkgeml701-chm.china.huawei.com (10.98.57.156) by nkgeml701-chm.china.huawei.com (10.98.57.156) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Thu, 30 Jan 2020 15:34:24 +0800
Received: from nkgeml701-chm.china.huawei.com ([10.98.57.156]) by nkgeml701-chm.china.huawei.com ([10.98.57.156]) with mapi id 15.01.1713.004; Thu, 30 Jan 2020 15:34:24 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: "bgp-autoconf@ietf.org" <bgp-autoconf@ietf.org>
CC: Hares Susan <shares@ndzh.com>, John Scudder <jgs=40juniper.net@dmarc.ietf.org>
Thread-Topic: Kicking things off
Thread-Index: AQHV1tpiJXV/GXwpak+wR0U8DMmRQqgCwnEQ
Date: Thu, 30 Jan 2020 07:34:24 +0000
Message-ID: <0fe7b49628b8432db430548c584ce3d9@huawei.com>
References: <8982CC48-77E8-4AC6-AF23-5875C8D93842@juniper.net>
In-Reply-To: <8982CC48-77E8-4AC6-AF23-5875C8D93842@juniper.net>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.173.211]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bgp-autoconf/GHG9zxtW6ohtzSch603Q_8vAkds>
Subject: Re: [Bgp-autoconf] Kicking things off
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: Thu, 30 Jan 2020 07:34:34 -0000

Hi all, 

Now we can get started on the list. (Thanks John!)

As mentioned in John's mail to IDR list, the design team is initially chartered to consider requirements and review the solution space (including existing proposals). And a good point raised by Robert is to firstly identify the scope of our problem space, whether our goal is to provide BGP auto-configuration for WAN, IXP, DC or for all of these cases. The scope can have some impact to the requirement. 

Thus my proposal for the discussion is:

1. Determine the problem space the design team aims to solve.

2. List the requirements for that problem space.

3. Review existing proposals, for each solution, summarize which requirements can be met, and what are the gaps (if any).

Thanks to Robert and Randy for providing the list of relevant drafts. I put them together in the following list, and also add one more draft.

draft-acee-idr-lldp-peer-discovery-06

draft-xu-idr-neighbor-autodiscovery-12

draft-ymbk-lsvr-l3dl-ulpc-02

draft-raszuk-idr-bgp-auto-session-setup-01

draft-raszuk-idr-bgp-auto-discovery-06
  draft-raszuk-idr-ibgp-auto-mesh-00 (merged)
  draft-wkumari-idr-socialite-02 (merged)

Once we have the Webex space, we could start to have regular conference calls to review the progress of our work, while it is highly recommended to have most discussion happen on the list. 

Thoughts?

Best regards,
Jie

> -----Original Message-----
> From: Bgp-autoconf [mailto:bgp-autoconf-bounces@ietf.org] On Behalf Of
> John Scudder
> Sent: Thursday, January 30, 2020 3:29 AM
> To: bgp-autoconf@ietf.org
> Cc: Hares Susan <shares@ndzh.com>
> Subject: [Bgp-autoconf] Kicking things off
> 
> Hi All,
> 
> The mailing list was the last administrative hurdle [*] so at this point I think
> we’re up and running. I’m hoping that at this point you will carry things
> forward on your own, please check in with Sue and me as desired but other
> than that I’m going to try to keep my nose out of your business.
> 
> Thanks again,
> 
> —John
> 
> [*] Having typed that I realize I also need to check in to getting you a WebEx
> space. But I don’t think that needs to hold things up.
> --
> Bgp-autoconf mailing list
> Bgp-autoconf@ietf.org
> https://www.ietf.org/mailman/listinfo/bgp-autoconf

v2.23.0 | Report a Bug | By Email