IETF Logo Mail Archive

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

Dino Farinacci <dino@cisco.com> Thu, 13 September 2007 01:58 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 1IVdyO-000369-Em; Wed, 12 Sep 2007 21:58:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IVdyM-0002zQ-S4 for ram@iab.org; Wed, 12 Sep 2007 21:58:26 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IVdyL-0007BP-Kw for ram@iab.org; Wed, 12 Sep 2007 21:58:26 -0400
X-IronPort-AV: E=Sophos;i="4.20,247,1186383600"; d="scan'208";a="217142672"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-6.cisco.com with ESMTP; 12 Sep 2007 18:58:21 -0700
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l8D1wKqK009154; Wed, 12 Sep 2007 18:58:21 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id l8D1wE3A028678; Thu, 13 Sep 2007 01:58:20 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 12 Sep 2007 18:58:17 -0700
Received: from [171.71.55.174] ([171.71.55.174]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 12 Sep 2007 18:58:17 -0700
In-Reply-To: <20070912200837.GS69215@Space.Net>
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> <4FC2075B-2E11-4C0F-A5CC-0ABAB75E826C@cisco.com> <20070912200837.GS69215@Space.Net>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <10EE8715-0232-43A7-9919-F50836F4FAE5@cisco.com>
Content-Transfer-Encoding: 7bit
From: Dino Farinacci <dino@cisco.com>
Subject: Re: [RRG] Re: [RAM] Tunneling overheads and fragmentation
Date: Wed, 12 Sep 2007 18:58:18 -0700
To: Gert Doering <gert@Space.Net>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 13 Sep 2007 01:58:17.0193 (UTC) FILETIME=[8D47F590:01C7F5A9]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=785; t=1189648701; x=1190512701; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dino@cisco.com; z=From:=20Dino=20Farinacci=20<dino@cisco.com> |Subject:=20Re=3A=20[RRG]=20Re=3A=20[RAM]=20Tunneling=20overheads=20and=2 0fragmentation |Sender:=20; bh=vkely71AvtEKu+o9hxLtNjstJCkcvrTV33ZkrMg+ots=; b=CxDzJ++qHEZdvZ2qrcDqHC8JJje9B+yW8otDis92QmXDeXYH2V0xoN6wm0+jWAtV2BeS1tCd zpkEdI1dLPOnTuZPxFs51CzsHNN4n3tklgsYyY0mjUwfdGv/wHCe1xev;
Authentication-Results: sj-dkim-2; header.From=dino@cisco.com; dkim=pass (si g from cisco.com/sjdkim2002 verified; );
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: Robin Whittle <rw@firstpr.com.au>, RAM Mailing List <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

> So there is no way our network could run on a MTU of 4470 or even
> higher any time soon.

Then you don't deploy ITRs or you deploy fragmenting-ITRs.

> [..]
>>    In practice, this is not really a problem.  Hosts typically do not
>>    originate IP packets larger than 1500 bytes.  And second, a survey
>>    has been taken (from a list of ISPs, see Acknowledgement section)
>>    where nearly all ISP link MTUs are either 4470 bytes or support
>>    Ethernet jumbo frames of 9000 bytes.  Therefore, we don't  
>> anticipate
>>    any problems with prepending additional headers.
>
> This is handwaving, and not a good basis for research work.

You are right, we are trying to make a decision and are doing  
engineering now past the research stage.   ;-)

Dino



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

v2.23.0 | Report a Bug | By Email