<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:12pt"><div id="yiv1192043617"><div><div style="color:#000;background-color:#fff;font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:12pt;"><pre id="yiv1192043617yui_3_13_0_rc_1_1_1381441300162_2677">Hi Rudra, Nachi.<br><br>Glad to see this discussion on the mailing list! The ExtraRoute routes are fairly<br>limited and it would be great to be able to store more complete routing<br>information in Neutron. I've submitted a blueprint proposing expanding ExtraRoute<br>parameters to include more information (extended-route-params). But it still<br>has a problem where routes are stored in a list and are not indexed. So an update<br>could be painful.<br><br>Could you share what attributes would you like to see in your RIB API?<br><br>Thanks!<br>Artem<br><br>P.S.
I'm OpenStack newbie, looking forward to learning from and working with you!<br><br>>Hi Rudra
>
>ExtraRoute bp was designed for adding some "extra" routing for the router.
>The spec is very handy for simple and small use cases.
>However it won't fit large use cases, because it takes all route in a Json List.
># It means we need to send full route for updating.
>
>As Salvatore suggests, we need to keep backward compatibility.
>so, IMO, we should create Routing table extension.
>
>I'm thinking about this in the context of L3VPN (MPLS) extension.
>My Idea is to have a RIB API in the Neutron.
>For vpnv4 routes it may have RT or RDs.
>
>Best
>Nachi
</pre></div></div></div></div></body></html>