[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Experiences with IPv6 and Routing Efficiency
- Subject: Experiences with IPv6 and Routing Efficiency
- From: mark.tinka at seacom.mu (Mark Tinka)
- Date: Sat, 18 Jan 2014 19:49:44 +0200
- In-reply-to: <CAHDzDLA=O9f7si6VZiZyr=B+HShvW0eztYPExNd7fPuhmE3-tw@mail.gmail.com>
- References: <CAHDzDLA=O9f7si6VZiZyr=B+HShvW0eztYPExNd7fPuhmE3-tw@mail.gmail.com>
On Saturday, January 18, 2014 06:09:58 AM Mukom Akong T.
wrote:
> Does anyone have any experiences or insights to share on
> how more (or less) efficient routing is with IPv6? Any
> specific thoughts with respect to how the following
> characteristics help or not with routing efficiency? -
> fixed header size
> - Extension header chain
> - flow labels in header
> - no intermediate fragmentation
> - no checksums
One thing to think about is routing efficiency.
At this time, networks that employ MPLS-TE for IPv4, and run
native IPv6, have challenges doing the same for IPv6, mostly
because it's not possible to point IPv6 traffic into MPLS-TE
tunnels built over an IPv4 control plane. If you are doing
6PE, this could be possible, but most vendors can't do the
former.
More native IPv6 control planes for MPLS (and by extension,
MPLS-TE) will mean that IPv6 traffic will travel the same
path as IPv4 traffic in MPLS-TE'd networks. When that will
be remains to be seen.
Until then, the most we can do for native IPv6 traffic is
fiddle around with IGP metrics, to obtain some kind of
reasonable TE.
Mark.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20140118/0a3271ad/attachment.bin>