gert at space.net
Mon Oct 6 15:46:49 CEST 2008
On Mon, Oct 06, 2008 at 03:39:59PM +0200, Jens Rosenboom wrote:
> On Thu, Oct 02, 2008 at 11:12:34PM +0200, Gert Doering wrote:
> > On Thu, Oct 02, 2008 at 02:16:58PM -0400, Truman Boyes wrote:
> > > This issue that you describe is not specific to IPv6, but rather is an
> > > issue with any networks that use MPLS VPNs, and do not propagate TTL.
> > Except that with IPv6 over MPLS, you can't even do TTL-propagation - how
> > is an IPv4+MPLS router to respond to an IPv6 traceroute?
> It should place the time-exceeded message into the tunnel just as
> it would do for v4 VPNs and let the egress router take care of deciding
> on the proper path back to the source. Which has the "nice" side effect
> of all hops of the tunnel seeming to be as far away as the egress
> in terms of RTT measurements.
Which isn't overly useful in figuring out *where* a given path breaks...
> Or are you talking about core routers that do not implement IPv6 at all?
As well :)
Total number of prefixes smaller than registry allocations: 128645
SpaceNet AG Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444 USt-IdNr.: DE813185279
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 305 bytes
Desc: not available
Url : http://lists.cluenet.de/pipermail/ipv6-ops/attachments/20081006/c16304b9/attachment.bin
More information about the ipv6-ops