[j-nsp] Next-table, route leaking, etc.

[Nathan Ward]

> On 22/02/2020, at 10:52 PM, Saku Ytti <saku at ytti.fi> wrote:
> 
> On Sat, 22 Feb 2020 at 00:26, Jeff Haas <jhaas at juniper.net> wrote:
> 
>> The problem and example in the thread were past the ability of my brain to follow this round.
>> That said, there's some amount of plumbing that can permit a route that's been imported into a VRF to locally resolve vs. the local VRF tables rather than share the fate of its primary route.
>> This plumbing isn't generally exposed at this time.  Magic words "independent resolution".  Just in case that fits the ER. :-)
> 
> Ooh, very good news. Nathan, can you please talk to your account team
> about this and get formal ER going? I'm happy to 'me too' my account
> team, once you have the ER number. And Jeff's work is made whole lot
> easier when he can go 'customers are asking this’.

Sounds great - will see what I can get going tomorrow.

--
Nathan Ward