[bess] miss import and export policy within routing-policy under vpn-target
Qin Wu <bill.wu@huawei.com> Thu, 25 July 2019 18:35 UTC
Return-Path: <bill.wu@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 B2983120198; Thu, 25 Jul 2019 11:35:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 DRaGWW6axlbb; Thu, 25 Jul 2019 11:35:54 -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 AD26A120191; Thu, 25 Jul 2019 11:35:54 -0700 (PDT)
Received: from LHREML712-CAH.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id A53ECF2E5B4257859575; Thu, 25 Jul 2019 19:35:52 +0100 (IST)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by LHREML712-CAH.china.huawei.com (10.201.108.35) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 25 Jul 2019 19:35:52 +0100
Received: from NKGEML513-MBS.china.huawei.com ([169.254.2.207]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0439.000; Fri, 26 Jul 2019 02:35:46 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "bess@ietf.org" <bess@ietf.org>
CC: "draft-ietf-bess-l3vpn-yang.all@ietf.org" <draft-ietf-bess-l3vpn-yang.all@ietf.org>, "draft-ietf-rtgwg-policy-model.all@ietf.org" <draft-ietf-rtgwg-policy-model.all@ietf.org>
Thread-Topic: miss import and export policy within routing-policy under vpn-target
Thread-Index: AdVDF2H6C7EH71AMQwqDvCcaSCaxtg==
Date: Thu, 25 Jul 2019 18:35:45 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABAA883AED2@nkgeml513-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.124.95.60]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABAA883AED2nkgeml513mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/G8bhp1VGhDsIPtUOnJFvrXRSPH0>
Subject: [bess] miss import and export policy within routing-policy under vpn-target
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, 25 Jul 2019 18:35:57 -0000
Hi, folks: When I walk through draft-ietf-bess-l3vpn-yang draft today, I see what is missing in routing policy model is import and export policy parameter, the grouping apply-policy defined in routing policy yang model which supports import and export policy is not used in the BGP model, So I am wondering why we not add import and export policy and take out routing policy leafref. Also I am wondering whether all the vendors support import-from-global and export-to-global, if the answer is no, I am wondering if we should add if-feature for import-from-global and export-to-global and take them completely out. -Qin