-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le 01/11/2013 06:32, Mark Tinka a écrit : > On Thursday, October 31, 2013 10:38:18 PM Michael Hallgren > wrote: > >> I apologize for not having followed this thread in >> detail, but generally we've avoided to allow >> iBGP route reflectors to manipulate a fair amont of >> attributes in out policies... Now, this being >> in an Internet routing context, your VP* needs may be >> different? For my culture, please let >> know. > > Modifying or updating communities on outbound sessions on > route reflectors is routine. If you're referring to other > BGP attributes, perhaps. Yes, maybe I was using a sledge hammer (promoting conservativeness). If it's ``good'' or ``bad'' to rewrite communities in this way, may depend on how you then use them.
> > > When running NG-MVPN on Juniper's, I had to rewrite the > communities that NG-MVPN's set on ingress or egress PE > routers because the routes that were reflected to Cisco > routers that didn't understand these communities - at the > time - meant they could not route unicast correctly within > the l3vpn's that carried the NG-MVPN traffic. Rewriting the > community (really, making it conform more to what Cisco > could understand) was a tricky, sneaky fix that worked. Which sounds like an example of (forced to but yet) ``good'' to me. Cheers, mh > > > IOS XE and IOS XR now have very good support for NG-MVPN's, > but I haven't checked how it would respond to such an issue > these days. Suffice it to say, that was IOS, then. > > Mark. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJzaosACgkQZNZ/rrgsqafgJQCfVbY0IEro1Z5PvFGEsobsSPqu YxwAoJK4fvObBW/tuzD57KIdF9V/mFtp =JEoA -----END PGP SIGNATURE----- _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp