IETF Logo Mail Archive

Re: [RAM] Tunnelling & GigE jumbo frame size

Iljitsch van Beijnum <iljitsch@muada.com> Wed, 12 September 2007 19:37 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 1IVY1N-0003fE-8Y; Wed, 12 Sep 2007 15:37:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IVY1L-0003f0-PD for ram@iab.org; Wed, 12 Sep 2007 15:37:07 -0400
Received: from sequoia.muada.com ([83.149.65.1]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IVY1K-00006l-EG for ram@iab.org; Wed, 12 Sep 2007 15:37:07 -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 l8CJX8pD039476 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 12 Sep 2007 21:33:15 +0200 (CEST) (envelope-from iljitsch@muada.com)
In-Reply-To: <45779BAC-34BD-49ED-A924-05DF4666FCC6@extremenetworks.com>
References: <896E7873-B5D5-442E-AB33-63910A6E78BE@extremenetworks.com> <B39B869F-1148-4DC6-A308-02A125F40031@muada.com> <1CD6EB92-9167-4EAE-B372-A517572FCA4D@extremenetworks.com> <E4A2C41B-454D-49CD-852C-B95ACA007971@muada.com> <45779BAC-34BD-49ED-A924-05DF4666FCC6@extremenetworks.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <6EB2B436-9CA9-4636-802D-B2E64E3E1708@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: [RAM] Tunnelling & GigE jumbo frame size
Date: Wed, 12 Sep 2007 21:35:39 +0200
To: RJ Atkinson <rja@extremenetworks.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: ram@iab.org
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 12-sep-2007, at 20:34, RJ Atkinson wrote:

>> We need to move to a situation where the capability to use larger
>> packets is used where it exists and to the degree that it exists.

> I know of a LOT of metro SPs and ISPs and IXs that already support
> the 9180++ MTU that I outlined before

Yes, but the way IP currently works means that ALL equipment in an IP  
subnet must share the same MTU. This is not a problem in itself if  
you have a homogonous ISP network (but the fact that you need to  
enable the larger size by hand is even there) but that requirement  
makes it extremely hard to deploy larger packet sizes in many other  
environments.

>> But for the purposes of a jack up solution we just need a few  
>> dozen extra bytes to accommodate the new headers without  
>> triggering the breakage that ensues when 1500-byte packets can't  
>> be forwarded without fragmentation.

> If you believe the above, why have you been wasting everyone's time
> just now ?

Does anyone believe anything else??

I guess I should read the latest LISP draft as apparently there  
specific a jumboframe size is mentioned, and I have no idea for what  
purpose.

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

v2.23.0 | Report a Bug | By Email