The key wording is 'everyone who has the option'. A large number of people are dealing with legacy circuits and gear. To be fair most of those legacy circuits are on legacy gear. Most companies would rather do hacks than spend a lot of money. And providers that have you locked to a long term contract won't do anything for you at all.
LR Mack McBride Network Architect -----Original Message----- From: Nick Hilliard [mailto:[email protected]] Sent: Monday, February 11, 2013 3:46 PM To: Aaron Cc: Mack McBride; Cisco NSP Subject: Re: [c-nsp] ip tcp adjust-mss On 11/02/2013 21:44, Aaron wrote: > Disagree, it is not a common practice. > You should make your MTU large enough. practically everyone who has the option and a modicum of common sense does this. There's no reason to make your core MTU small and constrain yourself packet overhead limitations when it's a tiny amount of effort to make it large on day 1. Nick > On Mon, Feb 11, 2013 at 3:54 PM, Mack McBride <[email protected]>wrote: > >> This is very common practice and practically everyone does it. >> Usually if you have your own backbone you enlarge the backbone packet >> size though. >> Sometimes that isn't an option due to provider switches in the path. >> >> LR Mack McBride >> Network Architect >> >> -----Original Message----- >> From: [email protected] [mailto: >> [email protected]] On Behalf Of Eric A Louie >> Sent: Monday, February 11, 2013 12:56 PM >> To: Cisco NSP >> Subject: [c-nsp] ip tcp adjust-mss >> >> I just put in this command on my upstream interfaces to help my mpls >> network pass traffic - that is, my effort to eliminate fragmentation >> in my backbone. >> >> Is anyone else using this method of "mtu control"? I need some >> support - my CEO is asking why I have to do this, and who else does >> it, and is it a common practice, etc, so I'm looking for evidence, >> more than just "The Cisco TAC told me to do it". >> >> thanks >> >> Much appreciated, Eric >> _______________________________________________ >> cisco-nsp mailing list [email protected] >> https://puck.nether.net/mailman/listinfo/cisco-nsp >> archive at http://puck.nether.net/pipermail/cisco-nsp/ >> >> _______________________________________________ >> cisco-nsp mailing list [email protected] >> https://puck.nether.net/mailman/listinfo/cisco-nsp >> archive at http://puck.nether.net/pipermail/cisco-nsp/ >> > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
