Right QOS is another thing that would need to be adjusted if native IP is introduced into MPLS only core Anyways as Saku mentioned if you are doing IPv4 natively than enabling native IPv6 makes perfect sense and if one runs BGP-free core and MPLS switching than 6PE/VPE is the natural choice
Regarding the TTL hiding it's new to me that some Customers would like to see all the MPLS hops However I guess if the network runs as supposed to the Customers wouldn't mind the missing extra hops in their traceroutes Personally I think that if the Customer has to tell you that there's something wrong with your core links than things must have gone fishy a while back(when the network was built, monitoring tools implemented or staff hired) adam -----Original Message----- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Tarko Tikan Sent: Monday, June 25, 2012 10:46 PM To: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] Basic understanding of 6PE and 6VPE hey, > If the intermediary routers are ipv6 capable don't omit placing an > ipv6 address on interfaces. 6pe should only be a stopgap until the > devices can do native. Doesn't make any sense before we have IPv6 MPLS implementation. We MPLS switch all IPv4 packets (QOS based on EXP, so we don't have to reset DSCP, being one of the reasons), for example. -- tarko _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/