Re: [RRG] Re: [RAM] Tunneling overheads and fragmentation

Iljitsch van Beijnum <iljitsch@muada.com> Tue, 11 September 2007 21:51 UTC

Return-path: <ram-bounces@iab.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IVDdl-000699-RD; Tue, 11 Sep 2007 17:51:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IVDdk-00065o-VB for ram@iab.org; Tue, 11 Sep 2007 17:51:24 -0400
Received: from sequoia.muada.com ([83.149.65.1]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IVDdj-0008AO-Kx for ram@iab.org; Tue, 11 Sep 2007 17:51:24 -0400
Received: from [82.192.90.28] (nirrti.muada.com [82.192.90.28]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id l8BLlPmx019806 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 11 Sep 2007 23:47:25 +0200 (CEST) (envelope-from iljitsch@muada.com)
In-Reply-To: <186FA279-5A25-4F50-8CBA-57CD9FDAA925@cisco.com>
References: <469F7673.6070702@firstpr.com.au> <20070720140433.GA69215@Space.Net> <46A21AD6.2060501@firstpr.com.au> <0857530C-5C9D-4D29-ACAB-16A99CBFD929@muada.com> <46E6992D.2090501@firstpr.com.au> <46E6F514.1030206@gmail.com> <DCE587FE-A4E1-48AB-B378-44A163E2C227@muada.com> <186FA279-5A25-4F50-8CBA-57CD9FDAA925@cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <A1E7B28B-17AD-42EB-8CBB-743B9558A359@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: [RRG] Re: [RAM] Tunneling overheads and fragmentation
Date: Tue, 11 Sep 2007 23:49:55 +0200
To: Dino Farinacci <dino@cisco.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: RAM Mailing List <ram@iab.org>, Robin Whittle <rw@firstpr.com.au>
X-BeenThere: ram@iab.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing and Addressing Mailing List <ram.iab.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ram>
List-Post: <mailto:ram@iab.org>
List-Help: <mailto:ram-request@iab.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=subscribe>
Errors-To: ram-bounces@iab.org

On 11-sep-2007, at 23:41, Dino Farinacci wrote:

>> Granted, this is a fairly old box in a small network, but I don't  
>> see anyone seriously claiming that ALL ISP networks support  
>> packets larger than 1500 bytes on ALL their internal links (and  
>> also on inter-ISP links).

> I did a survey about a month ago and it is true. I will yield to  
> those folks who responded to me to protect their privacy. ;-)

> But the main gist was:

> o We are going to 9K MTUs on all our internal links.
> o Where we don't have 9K MTUs, we use 4470.
> o Virtually no one runs ISP links at 1500.

That's good news, because then we can apparently treat anyone using  
1500 as an exception that can be dealt with operationally rather than  
something that must be addressed in the protocol.

But what about inter-ISP links? I'm assuming this isn't a big issue  
for high capacity private peering, but here in Europe a lot of  
peering happens over exchanges, which obviously use equipment that  
can easily handle larger packets, but so many people are on a big fat  
shared subnet that it's a given at someone will bring down the lowest  
common denominator to 1500.

_______________________________________________
RAM mailing list
RAM@iab.org
https://www1.ietf.org/mailman/listinfo/ram