Hi,
Right, obviously one can filter using as path, extcommunity, etc. on the control plane. As another side note I don't think currently cannot filter on VPNv4 address (you can filter with the part after the RD) but that might have changed since last time I had to play with this. I was referring to the fact that the ASBR doesn't check incoming labels at all if the interface is in the global table and thus it'll accept pretty much any valid label (or stack of labels) on the data plane for forwarding. ;) With option D are you referring to draft-kulmala? Are you using it anywhere? Kaj > From: Daniel Holme <[email protected]> > Date: Thu, 10 Sep 2009 00:57:51 -0700 > To: Kaj Niemi <[email protected]>, Bryan Bartik <[email protected]>, Jo Knight > <[email protected]> > Cc: <[email protected]>, Francisco <[email protected]>, > <[email protected]> > Subject: RE: [OSL | CCIE_SP] Inter-AS VPN Option B and send-label > > As a side note you can filter between AS when using option B, you just > have to filter the BGP extended RT community. So, you do have some > granular filtering available to you. > > Just to confuse you all, option D has been developed which is a mixture > of A & B, but maybe you should read about that after you've finished > your lab studies :-)
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
