Subject: [bess] Review of draft-ietf-bess-l3vpn-yang-04

From: Qin Wu <[email-masked]>
Date: Thu, 23 May 2019 03:04:32 +0000

I see draft-ietf-bess-l3vpn-yang-04 is buried in the BESS mailing list discussion and a bunches of BESS drafts that wait for progressing, it is really unfortunately
Two quick comments on section 3.2.6

1.       Why route-policy is repeated in two places, one is under vpn-targets, the other is under import-from-global? Is there any rationale behind this?

2.       Why tunnel policy is defined as string? How do we support fine granularity tunnel policy control?

e.g., how to support different tunnel encapsulation?

-Qin