HI Tarique what type of TCC are you talking about ? VLAN -TCC ?
I guess it depends on how JKING wants to do his VLAN mapping, from what I remember VLAN-CCC only supports one type of TPID, whereas vlan-rewrite can support all 3 types of the TPID. now don't ask what the 3 TPID 0x8... are as I don't remember :-p I personnaly wasn't aware you could do vlan rewrite directly on the TCC config, I always believed you still needed to configure the input-vlan-map additionally to the TCC config. If true, then I guess we never stop learning, if not then it is added config for nothing, Can anyone confirm this ? thanks Furthermore, if the choice is between the two, I would use VLAN rewrite as it is a bit more flexibility, such as the option to have CE-PE on one end sending native packet and tagging only on when the packet reaches the PE interface (via native-vlan-id options) and the other end can have the vlan being forwarded to the CE. On 2 June 2010 17:36, Tarique A. Nalkhande - BMC < [email protected]> wrote: > > TCC is the way to go.. > > TCC is supported in CCC, draft-Kompella, and draft-Martini based VPNs to > allow for interworking between dissimilar access technologies (or differing > VLAN IDs, which are normally required to be the same at both ends of a L2 > VPN). > > Feel free to unicast, if you need anything more specific. > > Goodwill, > Tarique A.N > > > > > -----Original Message----- > From: [email protected] [mailto: > [email protected]] On Behalf Of Bj?rn Tore Paulen > Sent: Tuesday, June 01, 2010 9:53 PM > To: Jking T > Cc: [email protected] > Subject: Re: [j-nsp] Vlan Rewrite - Non IQ PICs (MX) > > Jking T skrev: > > So there we are, no vlan rewrite for point-to-point L2VPN, kompella > without IQ. > "Kompella without IQ".. Not sure if Kireeti would approve... ;-) > > /BT > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > > ------Disclaimer- This email and any files transmitted with are classified > as confidential unless otherwise specified. This e-mail is intended solely > for the use of the individual or entity to whom this e-mail is addressed. If > you have received this email by mistake, please notify the sender and delete > this e-mail immediately and permanently. Although measures were taken to > free this e-mail and its attachments from any malicious code infection, it > is the responsibility of the recipient to check this email and any > attachments for the presence of such infection. The use of EEC(Mobily) > e-mail service is limited for EEC(Mobily) business use only. > > > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
