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

Dino Farinacci <dino@cisco.com> Tue, 11 September 2007 21:53 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 1IVDgA-00008m-Ev; Tue, 11 Sep 2007 17:53:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IVDg9-00008f-27 for ram@iab.org; Tue, 11 Sep 2007 17:53:53 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IVDg7-0008CL-E0 for ram@iab.org; Tue, 11 Sep 2007 17:53:53 -0400
X-IronPort-AV: E=Sophos;i="4.20,240,1186372800"; d="scan'208";a="131671564"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 11 Sep 2007 17:53:48 -0400
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l8BLrpFW025082; Tue, 11 Sep 2007 17:53:51 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l8BLroE0023470; Tue, 11 Sep 2007 21:53:50 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 11 Sep 2007 17:53:50 -0400
Received: from [192.168.0.3] ([10.82.241.129]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 11 Sep 2007 17:53:49 -0400
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: <4FC2075B-2E11-4C0F-A5CC-0ABAB75E826C@cisco.com>
Content-Transfer-Encoding: 7bit
From: Dino Farinacci <dino@cisco.com>
Subject: Re: [RRG] Re: [RAM] Tunneling overheads and fragmentation
Date: Tue, 11 Sep 2007 14:53:50 -0700
To: Dino Farinacci <dino@cisco.com>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 11 Sep 2007 21:53:49.0865 (UTC) FILETIME=[3C759190:01C7F4BE]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1533; t=1189547631; x=1190411631; c=relaxed/simple; s=rtpdkim1001; 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 |To:=20Dino=20Farinacci=20<dino@cisco.com>; bh=KH4MuXMnmqQqTgchhFIBXgN8hEA6QYgT5Ahip86N2s8=; b=oErcNVAn7hpUBikoKW2D5Ohl3iBk5PGVkFHkkJW1a8X6CeVOPixZ+lRYQmSg1X8RBCK9Vzhr mjqhm/yyLEOVfc2ehacjTWZgejJhOZvy87LS52FIz/J9aq6FAfNnKdGA;
Authentication-Results: rtp-dkim-1; header.From=dino@cisco.com; dkim=pass (s ig from cisco.com/rtpdkim1001 verified; );
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
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

>> 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.

And hence why I put this paragraph (the second one below) in section  
5 of draft-farinacci-lisp-03.txt to reflect Brian Carpenter's comment  
on the subject:

-----

    Since additional tunnel headers are prepended, the packet becomes
    larger and in theory can exceed the MTU of any link traversed from
    the ITR to the ETR.  It is recommended, in IPv4 that packets do not
    get fragmented as they are encapsulated by the ITR.  Instead, the
    packet is dropped and an ICMP Too Big message is returned to the
    source.

    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.

-----

Dino

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