IETF Logo Mail Archive

RE: [RAM] New LISP draft available ...

"Templin, Fred L" <Fred.L.Templin@boeing.com> Wed, 25 July 2007 18:59 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 1IDm4l-0005vp-EN; Wed, 25 Jul 2007 14:59:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IDm4k-0005ve-Cq for ram@iab.org; Wed, 25 Jul 2007 14:59:10 -0400
Received: from slb-smtpout-01.boeing.com ([130.76.64.48]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDm4j-0001oY-59 for ram@iab.org; Wed, 25 Jul 2007 14:59:10 -0400
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id l6PIx7JZ010369 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 25 Jul 2007 11:59:07 -0700 (PDT)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id l6PIx6Te027428; Wed, 25 Jul 2007 13:59:06 -0500 (CDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id l6PIx10b027247; Wed, 25 Jul 2007 13:59:06 -0500 (CDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 25 Jul 2007 11:59:05 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [RAM] New LISP draft available ...
Date: Wed, 25 Jul 2007 11:58:38 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED93F@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <10CE716C-FB80-4D54-88AA-FB8262E09076@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [RAM] New LISP draft available ...
Thread-Index: AcfO6tFIUgrjLNYdS/ao+1F5sLGMpAAAk4Pw
References: <1DFBAD55-CA28-4D44-9F96-218F5F281047@cisco.com><46A3CEE9.5080008@gmail.com><FD40F969-AACC-4182-87F0-109C5556ACD1@cisco.com><46A78A95.8040500@gmail.com> <10CE716C-FB80-4D54-88AA-FB8262E09076@cisco.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Dino Farinacci" <dino@cisco.com>, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
X-OriginalArrivalTime: 25 Jul 2007 18:59:05.0827 (UTC) FILETIME=[DFA85330:01C7CEED]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: 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

> > Not really, except that the extra header (unknown to the sender)
> > will reduce the MTU and we'd like to avoid that causing 
> fragmentation.
> 
> Understand the issue and there is no reliable solution to it. All  
> tunneling protocols have this problem. But I believe in 
> practice it's  
> not a real issue. Hosts send no larger, typically than 1500 byte  
> packets and routers are now more and more on 9K MTU links.

There is also the size of the reassembly buffer to consider,
i.e., the Maximum Receive Unit (MRU). Nodes are advised to
configure an MRU at least as large as the interface MTU, but
in some cases that may only be 1500bytes.

Fred
fred.l.templin@boeing.com 

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

v2.8.7 | Report a Bug | By Email