Re: [bess] miss import and export policy within routing-policy under vpn-target

"Susan Hares" <shares@ndzh.com> Thu, 25 July 2019 19:38 UTC

Return-Path: <shares@ndzh.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 C40E71201C6; Thu, 25 Jul 2019 12:38:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.949
X-Spam-Level:
X-Spam-Status: No, score=0.949 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no 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 gox0WGBCVm09; Thu, 25 Jul 2019 12:38:19 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-100-static.hfc.comcastbusiness.net [50.245.122.100]) (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 3D7CD1201C5; Thu, 25 Jul 2019 12:38:13 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=31.133.150.194;
From: "Susan Hares" <shares@ndzh.com>
To: "'Qin Wu'" <bill.wu@huawei.com>, <bess@ietf.org>
Cc: <draft-ietf-rtgwg-policy-model.all@ietf.org>, <draft-ietf-bess-l3vpn-yang.all@ietf.org>
References: <B8F9A780D330094D99AF023C5877DABAA883AED2@nkgeml513-mbs.china.huawei.com>
In-Reply-To: <B8F9A780D330094D99AF023C5877DABAA883AED2@nkgeml513-mbs.china.huawei.com>
Date: Thu, 25 Jul 2019 15:38:09 -0400
Message-ID: <00b301d54320$7dcda020$7968e060$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00B4_01D542FE.F6BC0020"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHJqmXI2LHRmZsKJtnMGQUkWd8Zpqby6/OA
Content-Language: en-us
X-Antivirus: AVG (VPS 190725-4, 07/25/2019), Outbound message
X-Antivirus-Status: Not-Tested
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/5zyxz_xfUzogLCfa4r7NKxjbjjE>
Subject: Re: [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 19:38:21 -0000

Qin: 

 

Just to make sure I have the context, the "BGP model" is the
draft-bess-l3vpn-yang-draft or the base BGP protocol model? 

 

Sue 

 

From: BESS [mailto:bess-bounces@ietf.org] On Behalf Of Qin Wu
Sent: Thursday, July 25, 2019 2:36 PM
To: bess@ietf.org
Cc: draft-ietf-rtgwg-policy-model.all@ietf.org;
draft-ietf-bess-l3vpn-yang.all@ietf.org
Subject: [bess] miss import and export policy within routing-policy under
vpn-target

 

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