[60604] in North American Network Operators' Group
Re: MPLS ICMP Extensions
daemon@ATHENA.MIT.EDU (Leo Bicknell)
Thu Aug 14 14:40:03 2003
Date: Thu, 14 Aug 2003 14:39:40 -0400
From: Leo Bicknell <bicknell@ufp.org>
To: nanog@merit.edu
Mail-Followup-To: nanog@merit.edu
In-Reply-To: <7CD4CD9D537C294D9ED9E5CE2F019106AF678A@MAILSERV.linc2icn.net>
Errors-To: owner-nanog-outgoing@merit.edu
--3MwIy2ne0vdjdPXF
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
In a message written on Thu, Aug 14, 2003 at 01:21:28PM -0500, Mike Bernico=
wrote:
> Maybe I'm wrong, but I thought that the extended MPLS info only showed
> up when the trace was started on a PE or P router. Is that right? =20
I did the traceroute from a router with _NO_ mpls commands turned on,
and it's on a network that uses _NO_ mpls today.
Basically from reading the draft if the router that generates the ICMP
unreachable received the packet with an MPLS label, it adds the MPLS
info to the returned data. As long as your traceroute can parse/show
it (so far I've only confirmed Juniper can do it), it will be displayed
to the world.
--=20
Leo Bicknell - bicknell@ufp.org - CCIE 3440
PGP keys at http://www.ufp.org/~bicknell/
Read TMBG List - tmbg-list-request@tmbg.org, www.tmbg.org
--3MwIy2ne0vdjdPXF
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)
iD8DBQE/O9drNh6mMG5yMTYRAkqdAJ4iHoLVH5aJaxQUvE4Ux4YG2n++uACfQQbQ
9faplzv7QTA+djL15ImBcfk=
=mjO4
-----END PGP SIGNATURE-----
--3MwIy2ne0vdjdPXF--
