RE: New Version Notification for draft-jiang-v6ops-incremental-cgn

"Templin, Fred L" <Fred.L.Templin@boeing.com> Thu, 04 June 2009 15:48 UTC

Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E24F33A6E24 for <ietfarch-v6ops-archive@core3.amsl.com>; Thu, 4 Jun 2009 08:48:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.135
X-Spam-Level:
X-Spam-Status: No, score=-5.135 tagged_above=-999 required=5 tests=[AWL=-0.640, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cv2ubCXQNXlT for <ietfarch-v6ops-archive@core3.amsl.com>; Thu, 4 Jun 2009 08:48:05 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 0550F3A6E03 for <v6ops-archive@lists.ietf.org>; Thu, 4 Jun 2009 08:48:05 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD)) (envelope-from <owner-v6ops@ops.ietf.org>) id 1MCF83-000N2v-W4 for v6ops-data0@psg.com; Thu, 04 Jun 2009 15:45:19 +0000
Received: from [130.76.64.48] (helo=slb-smtpout-01.boeing.com) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from <Fred.L.Templin@boeing.com>) id 1MCF7s-000N0y-Dg for v6ops@ops.ietf.org; Thu, 04 Jun 2009 15:45:13 +0000
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n54FiW3x015943 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 4 Jun 2009 08:44:33 -0700 (PDT)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n54FiWAA017195; Thu, 4 Jun 2009 08:44:32 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n54FiScH017044; Thu, 4 Jun 2009 08:44:32 -0700 (PDT)
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.3959); Thu, 4 Jun 2009 08:44:31 -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: New Version Notification for draft-jiang-v6ops-incremental-cgn
Date: Thu, 04 Jun 2009 08:44:16 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A10603D4B6@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <alpine.BSF.2.00.0906041701550.60110@mignon.ki.iif.hu>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: New Version Notification for draft-jiang-v6ops-incremental-cgn
Thread-Index: AcnlJYxX85VsfBLPQiquggTELqIEngAAujOA
References: <39C363776A4E8C4A94691D2BD9D1C9A105F0719F@XCH-NW-7V2.nw.nos.boeing.com> <000001c9d502$9843c980$5b0c6f0a@china.huawei.com> <39C363776A4E8C4A94691D2BD9D1C9A105F0726E@XCH-NW-7V2.nw.nos.boeing.com> <39C363776A4E8C4A94691D2BD9D1C9A105F075C2@XCH-NW-7V2.nw.nos.boeing.com><4A127FA0.6050603@free.fr> <39C363776A4E8C4A94691D2BD9D1C9A105F43989@XCH-NW-7V2.nw.nos.boeing.com> <20090519192430.GK2776@Space.Net> <474EEBD229DF754FB83D256004D021080BC9A0D9@XCH-NW-6V1.nw.nos.boeing.com> <20090520062916.GN2776@Space.Net> <4A13B880.3050407@mesh.ad.jp><f9e2d08a377.377f9e2d08a@huawei.com> <alpine.BSF.2.00.0905201623420.18643@mignon.ki.iif.hu> <4A2773E5.5010702@gmail.com> <alpine.BSF.2.00.0906041701550.60110@mignon.ki.iif.hu>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Mohacsi Janos <mohacsi@niif.hu>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: JiangSheng 66104 <shengjiang@huawei.com>, Seiichi Kawamura <kawamucho@mesh.ad.jp>, Gert Doering <gert@space.net>, "Fleischman, Eric" <eric.fleischman@boeing.com>, Re'mi Despre's <remi.despres@free.fr>, v6ops@ops.ietf.org, guoseu@huawei.com, "Russert, Steven W" <steven.w.russert@boeing.com>
X-OriginalArrivalTime: 04 Jun 2009 15:44:31.0678 (UTC) FILETIME=[5A388DE0:01C9E52B]
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

> > Do you think the draft needs to do any more than recommending to
follow
> > the recommendations in 4890? It seems as if that should be
sufficient.
> 
> This should be enough.

Regarding the 4890, there is advice in that document that I
would like to understand better. In Appendix A.2, it says:

   "If a network chooses to generate packets that are no larger than the
   Guaranteed Minimum MTU (1280 octets) and the site's links to the
   wider Internet have corresponding MTUs, Packet Too Big messages
   should not be expected at the firewall and could be dropped if they
   arrive."

But, that would seem to be in conflict with the text of
Section 5 of RFC2460, where the reader is informed that
the network can return PTB messages reporting MTU values
smaller than 1280 if a protocol translator is in the path.
The host should then react to these PTBs by inserting a
fragment header with (MF=0; Offset=0) in subsequent packets.
With the (RFC4890, Appendix A.2) text however, this behavior
is suppressed.

Where did the RFC4890 text come from? And, why is it there?

Thanks - Fred
fred.l.templin@boeing.com