HC2VPP-232 - Secondary table lookup support

Ietf models now contains case table-lookup to be able to define
lookup to secondary table. It must be separated to dedicated case
as combining secondary-vrf and other next hop types(simple,multi,special)
does not make sense, its either you define lookup to table,
or you specify next hop of some kind.

This patch works properly only for write,
as read is affected by VPP-994/VPP-995.
Read at this state can detect that route is using table lookup,
but can't detect table that is used for that lookup.

Also, HC2VPP-237 must be done in future

Change-Id: Ia6976b35c6c1712d8add60beea7b0edbc4536974
Signed-off-by: Jan Srnicek <jsrnicek@cisco.com>

1 files changed, 25 insertions, 0 deletions

diff --git a/routing/routing-api/src/main/yang/vpp-routing-table-lookup@2017-09-17.yang b/routing/routing-api/src/main/yang/vpp-routing-table-lookup@2017-09-17.yang
new file mode 100644
index 000000000..9ae77501b
--- /dev/null
+++ b/routing/routing-api/src/main/yang/vpp-routing-table-lookup@2017-09-17.yang
@@ -0,0 +1,25 @@
+module vpp-routing-table-lookup {
+
+    namespace "urn:ietf:params:xml:ns:yang:vpp-routing-table-lookup";
+    prefix "vpp-routing";
+    description "General extensions for routes to be able to use VPP table lookup option";
+
+    revision 2017-09-17 {
+        description "Initial revision";
+    }
+
+    import vpp-routing {
+        prefix "vpp-r";
+    }
+
+    grouping table-lookup-case-params {
+        leaf secondary-vrf{
+           type vpp-r:vni-reference;
+           mandatory true;
+           description "Secondary vrf used to lookup in";
+        }
+        // uses special deaggregation address every time : 0.0.0.0
+    }
+
+    //TODO - HONEYCOMB-398/HC2VPP-237 - move table lookup case here
+}
\ No newline at end of file