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

[adamv0025 at netconsultings.com]

> -----Original Message-----
> From: juniper-nsp <juniper-nsp-bounces at puck.nether.net> On Behalf Of
> Saku Ytti
> Sent: Saturday, February 22, 2020 9:52 AM
> To: Jeff Haas <jhaas at juniper.net>
> Cc: Juniper NSP <juniper-nsp at puck.nether.net>
> Subject: Re: [j-nsp] Next-table, route leaking, etc.
> 
> 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'.
> 
I'll do plus one as well

adam