[rbridge] Hop Count processing
sgai at cisco.com
Sat May 9 08:17:49 PDT 2009
We ABSOLUTELY need to be able to support a "TRILL traceroute".
Manageability and troubleshooting are mandatory requirements of any
On 5/9/09 7:48 AM, "Joe Touch" <touch at ISI.EDU> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Dinesh G Dutt wrote:
>> I'd like to modify the hop count processing in section 3.6 (of draft 12)
>> slightly. The advantages of this alignment are:
>> - Make it possible to implement something like L2 traceroute
> Bad idea. Keep in mind that this isn't L2 anything; it'd be *trill*.
> Even then, it seems nonsensical to support on 802 networks.
>> - Align it with what is done in other protocols such as IP and MPLS
>> for development and operational simplicity.
>> - Not forward a frame that will be dropped by the next hop.
> How do you know it won't be accepted by the next hop?
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> -----END PGP SIGNATURE-----
> rbridge mailing list
> rbridge at postel.org
More information about the rbridge