[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Isis-wg] [rbridge] Why is MTU discovery important?
- To: "Sadler, Jonathan B." <Jonathan.Sadler at tellabs.com>
- Subject: Re: [Isis-wg] [rbridge] Why is MTU discovery important?
- From: Dave Katz <dkatz at juniper.net>
- Date: Wed, 15 Apr 2009 14:13:23 -0500
- Cc: TRILL/RBridge Working Group <rbridge at postel.org>, "Les Ginsberg \(ginsberg\)" <ginsberg at cisco.com>, sgai <sgai at cisco.com>, "isis-wg at ietf.org" <isis-wg at ietf.org>, James Carlson <james.d.carlson at Sun.COM>, Radia Perlman <Radia.Perlman at Sun.COM>
- Delivered-to: isis-wg at core3.amsl.com
- In-reply-to: <5292FFA96EC22A4386067E9DBCC0CD2B260FB31298 at EX-NAP.tellabs-west.tellabsinc.net>
- List-archive: <http://www.ietf.org/mail-archive/web/isis-wg>
- List-help: <mailto:isis-wg-request@ietf.org?subject=help>
- List-id: IETF IS-IS working group <isis-wg.ietf.org>
- List-post: <mailto:isis-wg@ietf.org>
- List-subscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
- List-unsubscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
- References: <AE36820147909644AD2A7CA014B1FB5207AA4EEE at xmb-sjc-222.amer.cisco.com> <C600B8A3.675D%sgai at cisco.com> <5292FFA96EC22A4386067E9DBCC0CD2B260FB31294 at EX-NAP.tellabs-west.tellabsinc.net>, <18917.56335.861406.673686 at gargle.gargle.HOWL> <5292FFA96EC22A4386067E9DBCC0CD2B260FB31298 at EX-NAP.tellabs-west.tellabsinc.net>
This is exactly the same problem that NLSP ran into 15 years ago
(multiple encaps with different MTUs on Ethernet media.) NLSP punted
by requiring configuration of the max LSP size (IIRC), and there is
existence proof <cough> that this is a non-starter.
--Dave
On Apr 15, 2009, at 8:21 AM, Sadler, Jonathan B. wrote:
Exactly my point. The "payload guaranteed" is different depending
on if you are looking at 802.1d or 802.1ad. A 802.1ad "1500 byte
payload" will not make it through an 802.1d switch as the 802.1d
switch considers the 802.1Q shim as part of the payload - making the
overall frame size larger than the 1500 byte max it is required to
support.
I agree there are "lax" devices out there. Needless to say, the
need for "MTU discovery" comes from those that limit MTU to the 1500
byte definition found in 802.1d.
Jonathan Sadler