It is the latter, the basic BGP YANG model. ________________________________ 吴钦 Qin Mobile：+86-13914734360<tel:+86-13914734360>(Mobile Number) Email：[email protected]<mailto:[email protected]>
发件人： Susan Hares<[email protected]<mailto:[email protected]>> 收件人： Qin Wu<[email protected]<mailto:[email protected]>>;bess<[email protected]<mailto:[email protected]>> 抄送： draft-ietf-rtgwg-policy-model.all<[email protected]<mailto:[email protected]>>;draft-ietf-bess-l3vpn-yang.all<[email protected]<mailto:[email protected]>> 主题： RE: [bess] miss import and export policy within routing-policy under vpn-target 时间： 2019-07-25 15:38:29 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:[email protected]] On Behalf Of Qin Wu Sent: Thursday, July 25, 2019 2:36 PM To: [email protected] Cc: [email protected]; [email protected] 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
_______________________________________________ BESS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bess
