Re: [Bgp-autoconf] Move forward with bgp autoconf requirements and design principle
"Dongjie (Jimmy)" <jie.dong@huawei.com> Thu, 09 July 2020 16:44 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 226493A0D8A for <bgp-autoconf@ietfa.amsl.com>; Thu, 9 Jul 2020 09:44:53 -0700 (PDT)
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, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 7HAsbRxvEviT for <bgp-autoconf@ietfa.amsl.com>; Thu, 9 Jul 2020 09:44:49 -0700 (PDT)
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 3F0153A0D85 for <bgp-autoconf@ietf.org>; Thu, 9 Jul 2020 09:44:49 -0700 (PDT)
Received: from lhreml708-chm.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 564DB3EDBD320C0080DD for <bgp-autoconf@ietf.org>; Thu, 9 Jul 2020 17:44:46 +0100 (IST)
Received: from dggeme753-chm.china.huawei.com (10.3.19.99) by lhreml708-chm.china.huawei.com (10.201.108.57) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Thu, 9 Jul 2020 17:44:44 +0100
Received: from dggeme754-chm.china.huawei.com (10.3.19.100) by dggeme753-chm.china.huawei.com (10.3.19.99) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Fri, 10 Jul 2020 00:44:42 +0800
Received: from dggeme754-chm.china.huawei.com ([10.6.80.77]) by dggeme754-chm.china.huawei.com ([10.6.80.77]) with mapi id 15.01.1913.007; Fri, 10 Jul 2020 00:44:42 +0800
From: "Dongjie (Jimmy)" <jie.dong@huawei.com>
To: "bgp-autoconf@ietf.org" <bgp-autoconf@ietf.org>
Thread-Topic: [Bgp-autoconf] Move forward with bgp autoconf requirements and design principle
Thread-Index: AdYpNA7kwObJ16uITyuAVIK7h4Vm9gKzzrMAAHHqx7AG0+8CMACHB9YAAAzuS4AAdAyyEP//qDmAgACB4wD//oN78A==
Date: Thu, 09 Jul 2020 16:44:42 +0000
Message-ID: <23becae1ecb1499ab1e6de65bd054c2b@huawei.com>
References: <0d8841f4daf143439a237c91333744e4@huawei.com> <m2tv0172cl.wl-randy@psg.com> <6e6dca9ffe9b41839419715e1608ddef@huawei.com> <8d21cc950f784675a0f52fdf22f546e5@huawei.com> <CAOj+MME75tzRUm2PasSWfxSvEcO3tUix2fPHT=jm8wOjgXa0Hw@mail.gmail.com> <m2pn98ej2e.wl-randy@psg.com> <d5303a4df7834cbb9ed3c09831332b65@huawei.com>, <ef565f58-c871-49ef-95c2-66cd5da62164@Spark> <78c33d9e-5e62-4619-a199-4de94ce6aae5.xiaohu.xxh@alibaba-inc.com>
In-Reply-To: <78c33d9e-5e62-4619-a199-4de94ce6aae5.xiaohu.xxh@alibaba-inc.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.217.2]
Content-Type: multipart/mixed; boundary="_004_23becae1ecb1499ab1e6de65bd054c2bhuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bgp-autoconf/KUtDnXv1HcaoyzorVi77_J1bCBk>
Subject: Re: [Bgp-autoconf] Move forward with bgp autoconf requirements and design principle
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, 09 Jul 2020 16:44:53 -0000
Hi all, As promised please find attached an updated version of the draft. I changed the draft title a little bit to better reflect the content and purpose. Thanks again to Randy for his effort on the initial version. The design principles are listed in section 4 for further discussion. Some description about the candidate approaches draft-xu and draft-raszuk are added. The rest are some editorial changes. Please review this document and provide your comments and suggestions, proposing text would be better. Note that the authorship and contributor of the design team document would be based on the contribution. Although it may be quite challenging to get the draft ready before the submission cut-off, depending on the progress we made, perhaps we could have an -00 version first, then have it further revised before the meeting. Many thanks, Jie From: 徐小虎(义先) [mailto:xiaohu.xxh@alibaba-inc.com] Sent: Thursday, July 9, 2020 9:47 AM To: Bgp-autoconf <bgp-autoconf-bounces@ietf.org>; Randy Bush <randy@psg.com>; Robert Raszuk <robert@raszuk.net>; Dongjie (Jimmy) <jie.dong@huawei.com> Cc: bgp-autoconf@ietf.org Subject: Re: [Bgp-autoconf] Move forward with bgp autoconf requirements and design principle +1 ------------------------------------------------------------------ From:Jeff Tantsura <jefftant.ietf@gmail.com<mailto:jefftant.ietf@gmail.com>> Send Time:2020年7月9日(星期四) 02:02 To:Randy Bush <randy@psg.com<mailto:randy@psg.com>>; Robert Raszuk <robert@raszuk.net<mailto:robert@raszuk.net>>; Dongjie (Jimmy) <jie.dong@huawei.com<mailto:jie.dong@huawei.com>> Cc:bgp-autoconf@ietf.org <bgp-autoconf@ietf.org<mailto:bgp-autoconf@ietf.org>> Subject:Re: [Bgp-autoconf] Move forward with bgp autoconf requirements and design principle Jie, Sounds good, I don’t really see any convergence yet, so unbiased summary would be a great start Cheers, Jeff On Jul 8, 2020, 8:47 AM -0700, Dongjie (Jimmy) <jie.dong@huawei.com<mailto:jie.dong@huawei.com>>, wrote: Hi Randy and all, It is good we agreed on the scope of this document is DC. Certainly in the design team we can analyze and discuss the difference between the design for DC and WAN, my understanding is the details about it does not belong to this document. Coming back to the preparation of the draft deliverable, in addition to revising the existing text in the draft, my suggestion is to also add some brief description about each candidate solution regarding the functions, extensibility, etc., this may be similar to what was presented in the slides to the WG in last IETF meeting. I will work on some text and provide an update tomorrow. Any contribution to this is welcome. As for the design principle (including which layer the protocol should be based on and the interaction with BGP), if we cannot reach agreement before the meeting, probably we could provide a summary of the considerations first, and ask for some feedbacks from the WG. Thoughts? Best regards, Jie -----Original Message----- From: Randy Bush [mailto:randy@psg.com] Sent: Monday, July 6, 2020 11:53 PM To: Robert Raszuk <robert@raszuk.net<mailto:robert@raszuk.net>> Cc: Dongjie (Jimmy) <jie.dong@huawei.com<mailto:jie.dong@huawei.com>>; bgp-autoconf@ietf.org<mailto:bgp-autoconf@ietf.org> Subject: Re: [Bgp-autoconf] Move forward with bgp autoconf requirements and design principle The draft in question specifically adds WAN auto conf. that was certainly not the intent; and it's not really there in the words.. on the other hand, if we should keep an eye on the WAN as we design the LAN, we should be aware of choices which might unnecessarily restriict ourselves next year. Then the L3 peer auto discovery is just deferred to draft-ietf-lsvr-l3dl also not intended. i did ask for your help stitching multicast in, and you declined. perhaps you have time now. However reading thorough draft-ietf-lsvr-l3dl it is clear that it is not applicable to WAN. it is not applicable to many things :) as i said at the beginning, i do not think l3dl is really a serious candidate here. otoh, we would be silly if we did not keep an eye to see if there are lessons to be learned from it. [ fwiw, i think the scalability added to lsoe to become l3dl was not worth the complexity. but that is a discussion for another universe ] randy -- Bgp-autoconf mailing list Bgp-autoconf@ietf.org<mailto:Bgp-autoconf@ietf.org> https://www.ietf.org/mailman/listinfo/bgp-autoconf
- [Bgp-autoconf] Move forward with bgp autoconf req… Dongjie (Jimmy)
- Re: [Bgp-autoconf] Move forward with bgp autoconf… Randy Bush
- Re: [Bgp-autoconf] Move forward with bgp autoconf… 徐小虎(义先)
- Re: [Bgp-autoconf] Move forward with bgp autoconf… Dongjie (Jimmy)
- Re: [Bgp-autoconf] Move forward with bgp autoconf… Dongjie (Jimmy)
- Re: [Bgp-autoconf] Move forward with bgp autoconf… Robert Raszuk
- [Bgp-autoconf] 回复: Move forward with bgp autoconf… 徐小虎(义先)
- Re: [Bgp-autoconf] Move forward with bgp autoconf… Dongjie (Jimmy)
- Re: [Bgp-autoconf] 回复: Move forward with bgp auto… Dongjie (Jimmy)
- Re: [Bgp-autoconf] Move forward with bgp autoconf… Robert Raszuk
- Re: [Bgp-autoconf] Move forward with bgp autoconf… Dongjie (Jimmy)
- Re: [Bgp-autoconf] Move forward with bgp autoconf… Robert Raszuk
- Re: [Bgp-autoconf] Move forward with bgp autoconf… Randy Bush
- Re: [Bgp-autoconf] Move forward with bgp autoconf… Dongjie (Jimmy)
- Re: [Bgp-autoconf] Move forward with bgp autoconf… Jeff Tantsura
- Re: [Bgp-autoconf] Move forward with bgp autoconf… 徐小虎(义先)
- Re: [Bgp-autoconf] Move forward with bgp autoconf… Dongjie (Jimmy)
- Re: [Bgp-autoconf] Move forward with bgp autoconf… Warren Kumari
- Re: [Bgp-autoconf] Move forward with bgp autoconf… Dongjie (Jimmy)
- Re: [Bgp-autoconf] Move forward with bgp autoconf… Warren Kumari
- Re: [Bgp-autoconf] Move forward with bgp autoconf… Dongjie (Jimmy)