[bess] Some question about the evpn yang

"Wanghaibo (Rainsword)" <rainsword.wang@huawei.com> Thu, 06 December 2018 06:54 UTC

Return-Path: <rainsword.wang@huawei.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FB611310B7; Wed, 5 Dec 2018 22:54:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 VAOe3tjxAO3L; Wed, 5 Dec 2018 22:54:51 -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 2A0751310B3; Wed, 5 Dec 2018 22:54:51 -0800 (PST)
Received: from lhreml703-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id A0B4492D97393; Thu, 6 Dec 2018 06:54:47 +0000 (GMT)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml703-cah.china.huawei.com (10.201.108.44) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 6 Dec 2018 06:54:48 +0000
Received: from NKGEML514-MBS.china.huawei.com ([169.254.3.129]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0415.000; Thu, 6 Dec 2018 14:54:36 +0800
From: "Wanghaibo (Rainsword)" <rainsword.wang@huawei.com>
To: "draft-ietf-bess-evpn-yang@ietf.org" <draft-ietf-bess-evpn-yang@ietf.org>
CC: "bess@ietf.org" <bess@ietf.org>
Thread-Topic: Some question about the evpn yang
Thread-Index: AdSNL8PIr51+AJpJSXm/l+HelgPB5A==
Date: Thu, 6 Dec 2018 06:54:36 +0000
Message-ID: <1E61161D6E31D849BEA887261DB609348C7A4CB3@nkgeml514-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.156.185]
Content-Type: multipart/alternative; boundary="_000_1E61161D6E31D849BEA887261DB609348C7A4CB3nkgeml514mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/FpU-6eeWQk9_T_UAPmN7F4K0fRQ>
Subject: [bess] Some question about the evpn yang
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Dec 2018 06:54:53 -0000

Dear Editors of the EVPN YANG data model draft,


1.     I have found that there are list ip-prefix-route under the evpn-instance, when will use this?
          +--rw evpn-instances
             +--rw evpn-instance* [name]

                +--ro routes

                |  +--ro ip-prefix-route*

2. According to this model, how to support EVPN vlan-aware service?


would highly appreciated your responses.

Regards,
Haibo