
From suresh.krishnan@ericsson.com  Mon Feb  3 16:25:28 2014
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F4CD1A0278 for <int-area@ietfa.amsl.com>; Mon,  3 Feb 2014 16:25:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RcKQcLdKgrCk for <int-area@ietfa.amsl.com>; Mon,  3 Feb 2014 16:25:24 -0800 (PST)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id F04FD1A0264 for <int-area@ietf.org>; Mon,  3 Feb 2014 16:25:23 -0800 (PST)
X-AuditID: c6180641-b7f2f8e000002cdc-c7-52f033749fcc
Received: from EUSAAHC004.ericsson.se (Unknown_Domain [147.117.188.84]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 69.FC.11484.47330F25; Tue,  4 Feb 2014 01:25:24 +0100 (CET)
Received: from [142.133.113.185] (147.117.188.8) by smtps-am.internal.ericsson.com (147.117.188.84) with Microsoft SMTP Server (TLS) id 14.2.347.0; Mon, 3 Feb 2014 19:25:23 -0500
Message-ID: <52F03372.9090301@ericsson.com>
Date: Mon, 3 Feb 2014 19:25:22 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: "int-area@ietf.org" <int-area@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [147.117.188.8]
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrJJMWRmVeSWpSXmKPExsUyuXRPiG6J8Ycgg6NP1SxuzLrJYvHuwFQm ByaPJUt+Mnksvd7GGsAUxWWTkpqTWZZapG+XwJXx6cg1loJ3zBUzTr5nbGD8xtTFyMkhIWAi 8f7OWnYIW0ziwr31bCC2kMARRolN2+q7GLmA7G2MEg29h8EaeAW0Jc7MfMUMYrMIqEicf3Ya rIENaNCGnZ/BakQFwiTaL8xkhqgXlDg58wkLiC0C1Lv/yQEwm1nATqJ/xiKwXmEBDYlDO6ex QsRtJS7MuQ5VIy+x/e0cZoiDNCW2rvnOCnGoosSL4z+ZJjAKzEKyYhaS9llI2hcwMq9i5Cgt Ti3LTTcy3MQIDL5jEmyOOxgXfLI8xCjNwaIkzvvlrXOQkEB6YklqdmpqQWpRfFFpTmrxIUYm Dk6pBsYVn90Lwtfb2AWJH3nyzE96Dl+T1l2WgP8FHyYdvH/0m/wR8Vu5oRZf4x6Yz+TIMN3d xnaJtZu3+Ort/+8tfPWO/TTQOLt2tr/pwXxdLbkvO09oHRDImzqlScJJ8N6Gvm/TnC9tK2jZ Pm03T+4Oh+xDu6Y8+H3lX7j/yWz2oG/sjwzEWterissrsRRnJBpqMRcVJwIAEM4GlQwCAAA=
Subject: [Int-area] Call for agenda items at IETF89
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2014 00:25:28 -0000

Hi all,
    The intarea WG will be meeting at the London IETF (we have been
allocated a short one hour slot) and we are in the process of setting 
the agenda. Please send us your request for slots to
intarea-chairs@tools.ietf.org detailing

* Name of the draft
* Short description of why you think the item needs to be discussed in 
the intarea meeting
* Whether the draft has already been presented or will be presented in 
some other wg/bof.

Thanks
Suresh and JC








From nobody Thu Feb 13 19:02:18 2014
Return-Path: <zehn.cao@gmail.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E4321A00B1 for <int-area@ietfa.amsl.com>; Thu, 13 Feb 2014 19:02:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XPEa4zRh36HJ for <int-area@ietfa.amsl.com>; Thu, 13 Feb 2014 19:02:13 -0800 (PST)
Received: from mail-qa0-x22a.google.com (mail-qa0-x22a.google.com [IPv6:2607:f8b0:400d:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 1D4D11A00AD for <int-area@ietf.org>; Thu, 13 Feb 2014 19:02:12 -0800 (PST)
Received: by mail-qa0-f42.google.com with SMTP id k4so17614860qaq.15 for <int-area@ietf.org>; Thu, 13 Feb 2014 19:02:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=KJNCWfE1+/BhQX49l1sh79ykj652u6ygCgiV29YDhRE=; b=DmITFMrTdJpXZ0EEZMRFM89kpFaAQglS8NM+qri2Ga6lTi0ILpReIQ2RLcS9/XTj6K QFKLAbUn0QKqxUmGpRLodS0aMS/kmstNLtF3R3ddjMyDFnj3I7bLUao052m6A/BrDXL3 s0RL+yDSsVMrFTMC3ojYrvR1tWLI7lvWEZMkyNHBmt2jPWNlapv8F9eZv9wR+ROHD4z3 IApDYL6EYtOqmC8hielSsMSUMNGflQ7AwRtZm9OlWnbH22hvEP54t45dZqrshe/qtXjR 11bIHh/hrr8L5yuLN4PkWXMc2GGCscj9ynxz0v4pHvE1PyCzKfmOVc/FtKdRWetd9gV8 1rJQ==
MIME-Version: 1.0
X-Received: by 10.140.48.104 with SMTP id n95mr8212634qga.90.1392346931664; Thu, 13 Feb 2014 19:02:11 -0800 (PST)
Received: by 10.96.58.106 with HTTP; Thu, 13 Feb 2014 19:02:11 -0800 (PST)
In-Reply-To: <20140213081732.14205.11009.idtracker@ietfa.amsl.com>
References: <20140213081732.14205.11009.idtracker@ietfa.amsl.com>
Date: Fri, 14 Feb 2014 11:02:11 +0800
Message-ID: <CAProHAQVRUpqRnF5F8SoLPCt5dPRQoSiYzeW_wKQzX2qfdrHMA@mail.gmail.com>
From: "Cao,Zhen" <zehn.cao@gmail.com>
To: int-area@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/X0FHGaZGGmkFNkbcm9-Sg2AxSeQ
Subject: [Int-area] Fwd: I-D Action: draft-cao-dataplane-acceleration-framework-00.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2014 03:02:15 -0000

Hi All,

Could you help review and comments. Thank you .

Best regards,
Zhen&co-authors
---------- Forwarded message ----------
From:  <internet-drafts@ietf.org>
Date: Thu, Feb 13, 2014 at 4:17 PM
Subject: I-D Action: draft-cao-dataplane-acceleration-framework-00.txt
To: i-d-announce@ietf.org



A New Internet-Draft is available from the on-line Internet-Drafts directories.


        Title           : Data Plane Processing Acceleration Framework
        Authors         : Zhen Cao
                          Qiao Fu
                          Lingli Deng
        Filename        : draft-cao-dataplane-acceleration-framework-00.txt
        Pages           : 9
        Date            : 2014-02-13

Abstract:
   It is getting popular to running data applications over general
   purpose hardware/chipsets, instead of customized and dedicated
   hardware/chipset.  This way further decouples the software functions
   from the hardware.  But moving data processing intensive applications
   to general purpose hardware is still challenging, although the
   industry has supplied some proprietary solutions.  This document
   discusses the problems of data plane acceleration and proposes its
   framework.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-cao-dataplane-acceleration-framework/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-cao-dataplane-acceleration-framework-00


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


From nobody Fri Feb 14 12:26:28 2014
Return-Path: <rbonica@juniper.net>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D0C71A03EC for <int-area@ietfa.amsl.com>; Fri, 14 Feb 2014 12:26:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.201
X-Spam-Level: 
X-Spam-Status: No, score=-104.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kjGMlYivdkSZ for <int-area@ietfa.amsl.com>; Fri, 14 Feb 2014 12:26:24 -0800 (PST)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe004.messaging.microsoft.com [65.55.88.14]) by ietfa.amsl.com (Postfix) with ESMTP id 05CA81A03DC for <int-area@ietf.org>; Fri, 14 Feb 2014 12:26:23 -0800 (PST)
Received: from mail45-tx2-R.bigfish.com (10.9.14.229) by TX2EHSOBE011.bigfish.com (10.9.40.31) with Microsoft SMTP Server id 14.1.225.22; Fri, 14 Feb 2014 20:26:22 +0000
Received: from mail45-tx2 (localhost [127.0.0.1])	by mail45-tx2-R.bigfish.com (Postfix) with ESMTP id 5172980412	for <int-area@ietf.org>; Fri, 14 Feb 2014 20:26:22 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT001.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -21
X-BigFish: VPS-21(zz9371I936eI542Izz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6hzz1de098h1033IL17326ah8275dh1de097h186068hz2fh109h2a8h839h93fhd24hf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d07h1d0ch1d2eh1d3fh1dc1h1de9h1dfeh1dffh1e1dh1fe8h1ff5h2216h22d0h2336h2461h2487h24d7h2516h2545h255eh9a9j1155h)
Received-SPF: pass (mail45-tx2: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=rbonica@juniper.net; helo=BL2PRD0510HT001.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(6009001)(377424004)(377454003)(199002)(189002)(13464003)(74662001)(74502001)(31966008)(47446002)(74706001)(76796001)(92566001)(59766001)(77982001)(74876001)(76576001)(33646001)(63696002)(81816001)(15975445006)(81686001)(53806001)(56816005)(90146001)(83072002)(87936001)(85852003)(51856001)(81342001)(77096001)(54356001)(46102001)(80976001)(76482001)(86362001)(81542001)(4396001)(76786001)(15202345003)(54316002)(94316002)(49866001)(94946001)(47736001)(50986001)(93136001)(93516002)(56776001)(2656002)(47976001)(76176001)(83322001)(65816001)(74316001)(80022001)(66066001)(69226001)(19580405001)(79102001)(95666001)(85306002)(87266001)(74366001)(19580395003)(95416001)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:CO1PR05MB442; H:CO1PR05MB442.namprd05.prod.outlook.com; CLIP:66.129.241.14; FPR:BCBAF1BE.AAF72FC6.77F13D77.D4DC10D0.20284; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
Received: from mail45-tx2 (localhost.localdomain [127.0.0.1]) by mail45-tx2 (MessageSwitch) id 1392409579915682_8011; Fri, 14 Feb 2014 20:26:19 +0000 (UTC)
Received: from TX2EHSMHS025.bigfish.com (unknown [10.9.14.244])	by mail45-tx2.bigfish.com (Postfix) with ESMTP id D98703A004A	for <int-area@ietf.org>; Fri, 14 Feb 2014 20:26:19 +0000 (UTC)
Received: from BL2PRD0510HT001.namprd05.prod.outlook.com (157.56.240.101) by TX2EHSMHS025.bigfish.com (10.9.99.125) with Microsoft SMTP Server (TLS) id 14.16.227.3; Fri, 14 Feb 2014 20:26:19 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) by BL2PRD0510HT001.namprd05.prod.outlook.com (10.255.100.36) with Microsoft SMTP Server (TLS) id 14.16.411.0; Fri, 14 Feb 2014 20:26:12 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) by CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) with Microsoft SMTP Server (TLS) id 15.0.878.16; Fri, 14 Feb 2014 20:26:10 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.51]) by CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.51]) with mapi id 15.00.0878.008; Fri, 14 Feb 2014 20:26:09 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: "int-area@ietf.org" <int-area@ietf.org>
Thread-Topic: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
Thread-Index: AQHPKcAwQtqxEb4ArEW/XYeQB9i6GZq1MkcQ
Date: Fri, 14 Feb 2014 20:26:09 +0000
Message-ID: <68a71d0317c546689875cfb7a1a67f9b@CO1PR05MB442.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.14]
x-forefront-prvs: 01221E3973
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/8Iwqgd4L2-TcDY4k8vbCOsRI9js
Subject: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2014 20:26:27 -0000

Rm9sa3MsDQoNClBsZWFzZSByZXZpZXcgYW5kIGNvbW1lbnQNCg0KICAgICAgICAgICAgICAgIFJv
bg0KDQoNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IGludGVybmV0LWRyYWZ0
c0BpZXRmLm9yZyBbbWFpbHRvOmludGVybmV0LWRyYWZ0c0BpZXRmLm9yZ10gDQpTZW50OiBGcmlk
YXksIEZlYnJ1YXJ5IDE0LCAyMDE0IDM6MDYgUE0NClRvOiBSb25hbGQgQm9uaWNhOyBEci4gSm9z
ZXBoIEQuIFRvdWNoOyBKb2UgVG91Y2g7IENhcmxvcyBQaWduYXRhcm87IFJvbmFsZCBCb25pY2E7
IENhcmxvcyBQaWduYXRhcm8NClN1YmplY3Q6IE5ldyBWZXJzaW9uIE5vdGlmaWNhdGlvbiBmb3Ig
ZHJhZnQtYm9uaWNhLWludGFyZWEtZ3JlLW10dS0wNC50eHQNCg0KDQpBIG5ldyB2ZXJzaW9uIG9m
IEktRCwgZHJhZnQtYm9uaWNhLWludGFyZWEtZ3JlLW10dS0wNC50eHQNCmhhcyBiZWVuIHN1Y2Nl
c3NmdWxseSBzdWJtaXR0ZWQgYnkgUm9uIEJvbmljYSBhbmQgcG9zdGVkIHRvIHRoZSBJRVRGIHJl
cG9zaXRvcnkuDQoNCk5hbWU6CQlkcmFmdC1ib25pY2EtaW50YXJlYS1ncmUtbXR1DQpSZXZpc2lv
bjoJMDQNClRpdGxlOgkJQSBGcmFnbWVudGF0aW9uIFN0cmF0ZWd5IGZvciBHZW5lcmljIFJvdXRp
bmcgRW5jYXBzdWxhdGlvbiAoR1JFKQ0KRG9jdW1lbnQgZGF0ZToJMjAxNC0wMi0xMg0KR3JvdXA6
CQlJbmRpdmlkdWFsIFN1Ym1pc3Npb24NClBhZ2VzOgkJMTENClVSTDogICAgICAgICAgICBodHRw
Oi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1ib25pY2EtaW50YXJlYS1ncmUt
bXR1LTA0LnR4dA0KU3RhdHVzOiAgICAgICAgIGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcv
ZG9jL2RyYWZ0LWJvbmljYS1pbnRhcmVhLWdyZS1tdHUvDQpIdG1saXplZDogICAgICAgaHR0cDov
L3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtYm9uaWNhLWludGFyZWEtZ3JlLW10dS0wNA0KRGlm
ZjogICAgICAgICAgIGh0dHA6Ly93d3cuaWV0Zi5vcmcvcmZjZGlmZj91cmwyPWRyYWZ0LWJvbmlj
YS1pbnRhcmVhLWdyZS1tdHUtMDQNCg0KQWJzdHJhY3Q6DQogICBUaGlzIG1lbW8gc3BlY2lmaWVz
IGEgZGVmYXVsdCBHUkUgdHVubmVsIGZyYWdtZW50YXRpb24gc3RyYXRlZ3ksDQogICB3aGljaCBo
YXMgYmVlbiBpbXBsZW1lbnRlZCBieSBtYW55IHZlbmRvcnMgYW5kIHdpZGVseSBkZXBsb3llZCBv
biB0aGUNCiAgIEludGVybmV0Lg0KDQogICBUaGlzIG1lbW8gYWxzbyBzcGVjaWZpZXMgcmVxdWly
ZW1lbnRzIGZvciBHUkUgaW1wbGVtZW50YXRpb25zLg0KICAgSGF2aW5nIHNhdGlzZmllZCB0aGVz
ZSByZXF1aXJlbWVudHMsIGEgR1JFIGltcGxlbWVudGF0aW9uIHdpbGwNCiAgIGV4ZWN1dGUgdGhl
IGRlZmF1bHQgR1JFIHR1bm5lbCBmcmFnbWVudGF0aW9uIHN0cmF0ZWd5LCBzcGVjaWZpZWQNCiAg
IGhlcmVpbiwgd2l0aCBtaW5pbWFsIGNvbmZpZ3VyYXRpb24uICBIb3dldmVyLCB3aXRoIGFkZGl0
aW9uYWwNCiAgIGNvbmZpZ3VyYXRpb24sIHRoZSBHUkUgaW1wbGVtZW50YXRpb24gY2FuIGV4ZWN1
dGUgYW55IG9mIHRoZSB0dW5uZWwNCiAgIGZyYWdtZW50YXRpb24gc3RyYXRlZ2llcyBkZWZpbmVk
IGluIFJGQyA0NDU5Lg0KDQoNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICANCg0KDQpQbGVhc2Ug
bm90ZSB0aGF0IGl0IG1heSB0YWtlIGEgY291cGxlIG9mIG1pbnV0ZXMgZnJvbSB0aGUgdGltZSBv
ZiBzdWJtaXNzaW9uIHVudGlsIHRoZSBodG1saXplZCB2ZXJzaW9uIGFuZCBkaWZmIGFyZSBhdmFp
bGFibGUgYXQgdG9vbHMuaWV0Zi5vcmcuDQoNClRoZSBJRVRGIFNlY3JldGFyaWF0DQoNCg0KDQo=


From nobody Fri Feb 14 13:19:46 2014
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42FD61A0357 for <int-area@ietfa.amsl.com>; Fri, 14 Feb 2014 13:19:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.749
X-Spam-Level: 
X-Spam-Status: No, score=-4.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N7ynOC4--_lm for <int-area@ietfa.amsl.com>; Fri, 14 Feb 2014 13:19:42 -0800 (PST)
Received: from slb-mbsout-02.boeing.com (slb-mbsout-02.boeing.com [130.76.64.129]) by ietfa.amsl.com (Postfix) with ESMTP id 3D6C21A0312 for <int-area@ietf.org>; Fri, 14 Feb 2014 13:19:42 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id s1ELJebl025916; Fri, 14 Feb 2014 13:19:40 -0800
Received: from XCH-PHX-513.sw.nos.boeing.com (xch-phx-513.sw.nos.boeing.com [10.57.37.30]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id s1ELJcJc025431 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Fri, 14 Feb 2014 13:19:38 -0800
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.102]) by XCH-PHX-513.sw.nos.boeing.com ([169.254.13.243]) with mapi id 14.03.0174.001;  Fri, 14 Feb 2014 13:19:37 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ronald Bonica <rbonica@juniper.net>, "int-area@ietf.org" <int-area@ietf.org>
Thread-Topic: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
Thread-Index: AQHPKcAwQtqxEb4ArEW/XYeQB9i6GZq1MkcQgAALxOA=
Date: Fri, 14 Feb 2014 21:19:37 +0000
Message-ID: <2134F8430051B64F815C691A62D983181CEEEF@XCH-BLV-504.nw.nos.boeing.com>
References: <68a71d0317c546689875cfb7a1a67f9b@CO1PR05MB442.namprd05.prod.outlook.com>
In-Reply-To: <68a71d0317c546689875cfb7a1a67f9b@CO1PR05MB442.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/mv_G25_0_1HT0OIFII4d6gkNoxE
Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2014 21:19:45 -0000

Hi Ron,

In Section 4.1, when the GRE ingress emits packets that *might* undergo
IPv4 fragmentation on the path to the egress, the ingress needs to use
rate limiting to ensure that no IPv4 reassembly misassociations occur a
the egress [RFC6864][RFC4963]. If the ingress has some way of discovering
that no IPv4 fragmentation will occur, it can then suspend rate limiting
and send at full line rates [draft-templin-aerolink].

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

> -----Original Message-----
> From: Int-area [mailto:int-area-bounces@ietf.org] On Behalf Of Ronald Bon=
ica
> Sent: Friday, February 14, 2014 12:26 PM
> To: int-area@ietf.org
> Subject: [Int-area] FW: New Version Notification for draft-bonica-intarea=
-gre-mtu-04.txt
>=20
> Folks,
>=20
> Please review and comment
>=20
>                 Ron
>=20
>=20
>=20
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: Friday, February 14, 2014 3:06 PM
> To: Ronald Bonica; Dr. Joseph D. Touch; Joe Touch; Carlos Pignataro; Rona=
ld Bonica; Carlos Pignataro
> Subject: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
>=20
>=20
> A new version of I-D, draft-bonica-intarea-gre-mtu-04.txt
> has been successfully submitted by Ron Bonica and posted to the IETF repo=
sitory.
>=20
> Name:		draft-bonica-intarea-gre-mtu
> Revision:	04
> Title:		A Fragmentation Strategy for Generic Routing Encapsulation (GRE)
> Document date:	2014-02-12
> Group:		Individual Submission
> Pages:		11
> URL:            http://www.ietf.org/internet-drafts/draft-bonica-intarea-=
gre-mtu-04.txt
> Status:         https://datatracker.ietf.org/doc/draft-bonica-intarea-gre=
-mtu/
> Htmlized:       http://tools.ietf.org/html/draft-bonica-intarea-gre-mtu-0=
4
> Diff:           http://www.ietf.org/rfcdiff?url2=3Ddraft-bonica-intarea-g=
re-mtu-04
>=20
> Abstract:
>    This memo specifies a default GRE tunnel fragmentation strategy,
>    which has been implemented by many vendors and widely deployed on the
>    Internet.
>=20
>    This memo also specifies requirements for GRE implementations.
>    Having satisfied these requirements, a GRE implementation will
>    execute the default GRE tunnel fragmentation strategy, specified
>    herein, with minimal configuration.  However, with additional
>    configuration, the GRE implementation can execute any of the tunnel
>    fragmentation strategies defined in RFC 4459.
>=20
>=20
>=20
>=20
>=20
> Please note that it may take a couple of minutes from the time of submiss=
ion until the htmlized
> version and diff are available at tools.ietf.org.
>=20
> The IETF Secretariat
>=20
>=20
>=20
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area


From nobody Fri Feb 14 13:31:24 2014
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CD2D1A0342 for <int-area@ietfa.amsl.com>; Fri, 14 Feb 2014 13:31:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w7XyPQYXZrQc for <int-area@ietfa.amsl.com>; Fri, 14 Feb 2014 13:31:17 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 4DD211A023F for <int-area@ietf.org>; Fri, 14 Feb 2014 13:31:17 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id s1ELV5xV012855 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 14 Feb 2014 13:31:05 -0800 (PST)
Message-ID: <52FE8B19.4070602@isi.edu>
Date: Fri, 14 Feb 2014 13:31:05 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, Ronald Bonica <rbonica@juniper.net>, "int-area@ietf.org" <int-area@ietf.org>
References: <68a71d0317c546689875cfb7a1a67f9b@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983181CEEEF@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D983181CEEEF@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/dimHOm-yMbZTvN8Vb3EPrw_AEy8
Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Feb 2014 21:31:20 -0000

Hi, Fred,

Yes, this doc should definitely include a discussion of 6864. We'll tend 
to that in the next revision.

Joe

On 2/14/2014 1:19 PM, Templin, Fred L wrote:
> Hi Ron,
>
> In Section 4.1, when the GRE ingress emits packets that *might* undergo
> IPv4 fragmentation on the path to the egress, the ingress needs to use
> rate limiting to ensure that no IPv4 reassembly misassociations occur a
> the egress [RFC6864][RFC4963]. If the ingress has some way of discovering
> that no IPv4 fragmentation will occur, it can then suspend rate limiting
> and send at full line rates [draft-templin-aerolink].
>
> Thanks - Fred
> fred.l.templin@boeing.com
>
>> -----Original Message-----
>> From: Int-area [mailto:int-area-bounces@ietf.org] On Behalf Of Ronald Bonica
>> Sent: Friday, February 14, 2014 12:26 PM
>> To: int-area@ietf.org
>> Subject: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
>>
>> Folks,
>>
>> Please review and comment
>>
>>                  Ron
>>
>>
>>
>> -----Original Message-----
>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>> Sent: Friday, February 14, 2014 3:06 PM
>> To: Ronald Bonica; Dr. Joseph D. Touch; Joe Touch; Carlos Pignataro; Ronald Bonica; Carlos Pignataro
>> Subject: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
>>
>>
>> A new version of I-D, draft-bonica-intarea-gre-mtu-04.txt
>> has been successfully submitted by Ron Bonica and posted to the IETF repository.
>>
>> Name:		draft-bonica-intarea-gre-mtu
>> Revision:	04
>> Title:		A Fragmentation Strategy for Generic Routing Encapsulation (GRE)
>> Document date:	2014-02-12
>> Group:		Individual Submission
>> Pages:		11
>> URL:            http://www.ietf.org/internet-drafts/draft-bonica-intarea-gre-mtu-04.txt
>> Status:         https://datatracker.ietf.org/doc/draft-bonica-intarea-gre-mtu/
>> Htmlized:       http://tools.ietf.org/html/draft-bonica-intarea-gre-mtu-04
>> Diff:           http://www.ietf.org/rfcdiff?url2=draft-bonica-intarea-gre-mtu-04
>>
>> Abstract:
>>     This memo specifies a default GRE tunnel fragmentation strategy,
>>     which has been implemented by many vendors and widely deployed on the
>>     Internet.
>>
>>     This memo also specifies requirements for GRE implementations.
>>     Having satisfied these requirements, a GRE implementation will
>>     execute the default GRE tunnel fragmentation strategy, specified
>>     herein, with minimal configuration.  However, with additional
>>     configuration, the GRE implementation can execute any of the tunnel
>>     fragmentation strategies defined in RFC 4459.
>>
>>
>>
>>
>>
>> Please note that it may take a couple of minutes from the time of submission until the htmlized
>> version and diff are available at tools.ietf.org.
>>
>> The IETF Secretariat
>>
>>
>>
>> _______________________________________________
>> Int-area mailing list
>> Int-area@ietf.org
>> https://www.ietf.org/mailman/listinfo/int-area
>
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area
>


From nobody Mon Feb 17 01:37:09 2014
Return-Path: <meng.wei2@zte.com.cn>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B3351A047B for <int-area@ietfa.amsl.com>; Mon, 17 Feb 2014 01:37:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.447
X-Spam-Level: 
X-Spam-Status: No, score=-102.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.548, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6DTAFuaIMQlt for <int-area@ietfa.amsl.com>; Mon, 17 Feb 2014 01:36:58 -0800 (PST)
Received: from mx6.zte.com.cn (mx6.zte.com.cn [95.130.199.165]) by ietfa.amsl.com (Postfix) with ESMTP id D206C1A0478 for <int-area@ietf.org>; Mon, 17 Feb 2014 01:36:56 -0800 (PST)
Received: from zte.com.cn (unknown [192.168.168.120]) by Websense Email Security Gateway with ESMTP id E6EBBB245B for <int-area@ietf.org>; Mon, 17 Feb 2014 17:36:36 +0800 (CST)
Received: from mse01.zte.com.cn (unknown [10.30.3.20]) by Websense Email Security Gateway with ESMTPS id 8FDC2CBEAB8 for <int-area@ietf.org>; Mon, 17 Feb 2014 17:36:35 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id s1H9acC8026068 for <int-area@ietf.org>; Mon, 17 Feb 2014 17:36:38 +0800 (GMT-8) (envelope-from meng.wei2@zte.com.cn)
In-Reply-To: <OF537A9D13.26A6879D-ON48257C47.003A5F85-48257C47.003A6292@LocalDomain>
To: int-area@ietf.org
MIME-Version: 1.0
X-KeepSent: AACE8064:9978BF9B-48257C82:00316807; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OFAACE8064.9978BF9B-ON48257C82.00316807-48257C82.0034F8C7@zte.com.cn>
From: meng.wei2@zte.com.cn
Date: Mon, 17 Feb 2014 17:36:33 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2014-02-17 17:36:26, Serialize complete at 2014-02-17 17:36:26
Content-Type: multipart/alternative; boundary="=_alternative 0034F8C248257C82_="
X-MAIL: mse01.zte.com.cn s1H9acC8026068
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/01u_3jc5mgtF5R_tNf4sBPL0D4Q
Subject: [Int-area] [intarea]Comments on draft-cui-intarea-unified-v6-framework-00
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Feb 2014 09:37:08 -0000

This is a multipart message in MIME format.
--=_alternative 0034F8C248257C82_=
Content-Type: text/plain; charset="US-ASCII"

Hi Yong, Yuchi, all

  This is a interesting topic. I reviewed this draft and  have some
comments and questions.

  1) In section 5

   "When receiving an incoming packet that doesn't have a match in the
   flow table (usually the intial packet of a new flow), CPE Switch and
   BR Switch MUST forward the packet to Controller.  Controller MUST
   determine how to proceed the flow (e.g. whether to apply NAT/ NAT64
   translation and/ or softwire encapsluaton/ decapuslutaion), and
   interpret the process into a set of forwarding rule configurations.
   Controller then passes these configurations to CPE Swtich and BR
   Switch.  CPE Switch and BR Switch then configure their flow table
   according to these configurations,"

  Why not let controller create flow table. Since packet is received by
controller, why not let it do more?
  BTW, does "usually the intial packet of a new flow" mean an intial 
packet
of each session? If so, it might lead to message congestion between switch 
&
controller.

  2) What is the concrete consideration between CPE/BR & controller? 
such as netconfig, i2rs.

  3) Logging is important in NAT, what is the consideration about it?
Maybe a switch is not suitable for logging itself.


Thanks,
Wei

--=_alternative 0034F8C248257C82_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi Yong, Yuchi, all</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; This is a interesting topic.
I reviewed this draft and &nbsp;have some</font>
<br><font size=2 face="sans-serif">comments and questions.</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; 1) In section 5</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; &nbsp;&quot;When receiving an
incoming packet that doesn't have a match in the</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp;flow table (usually the
intial packet of a new flow), CPE Switch and</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp;BR Switch MUST forward
the packet to Controller. &nbsp;Controller MUST</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp;determine how to proceed
the flow (e.g. whether to apply NAT/ NAT64</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp;translation and/ or softwire
encapsluaton/ decapuslutaion), and</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp;interpret the process into
a set of forwarding rule configurations.</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp;Controller then passes
these configurations to CPE Swtich and BR</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp;Switch. &nbsp;CPE Switch
and BR Switch then configure their flow table</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp;according to these configurations,&quot;</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; Why not let controller create
flow table. Since packet is received by</font>
<br><font size=2 face="sans-serif">controller, why not let it do more?</font>
<br><font size=2 face="sans-serif">&nbsp; BTW, does &quot;usually the intial
packet of a new flow&quot; mean an intial packet</font>
<br><font size=2 face="sans-serif">of each session? If so, it might lead
to message congestion between switch &amp;</font>
<br><font size=2 face="sans-serif">controller.</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; 2) What is the concrete consideration
between CPE/BR &amp; controller? </font>
<br><font size=2 face="sans-serif">such as netconfig, i2rs.</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; 3) Logging is important in NAT,
what is the consideration about it?</font>
<br><font size=2 face="sans-serif">Maybe a switch is not suitable for logging
itself.</font>
<br>
<br>
<br><font size=2 face="sans-serif">Thanks,</font>
<br><font size=2 face="sans-serif">Wei</font>
<br>
--=_alternative 0034F8C248257C82_=--


From nobody Mon Feb 17 10:52:02 2014
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F4B51A0135 for <int-area@ietfa.amsl.com>; Mon, 17 Feb 2014 10:52:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.749
X-Spam-Level: 
X-Spam-Status: No, score=-4.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3u7kgR33Vsrd for <int-area@ietfa.amsl.com>; Mon, 17 Feb 2014 10:51:56 -0800 (PST)
Received: from blv-mbsout-02.boeing.com (blv-mbsout-02.boeing.com [130.76.32.232]) by ietfa.amsl.com (Postfix) with ESMTP id A76C21A01D6 for <int-area@ietf.org>; Mon, 17 Feb 2014 10:51:55 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id s1HIppuh007338; Mon, 17 Feb 2014 10:51:51 -0800
Received: from XCH-PHX-411.sw.nos.boeing.com (xch-phx-411.sw.nos.boeing.com [10.57.37.42]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id s1HIpgOY007210 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Mon, 17 Feb 2014 10:51:42 -0800
Received: from XCH-BLV-502.nw.nos.boeing.com (130.247.25.191) by XCH-PHX-411.sw.nos.boeing.com (10.57.37.42) with Microsoft SMTP Server (TLS) id 14.3.174.1; Mon, 17 Feb 2014 10:51:41 -0800
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.102]) by XCH-BLV-502.nw.nos.boeing.com ([169.254.2.99]) with mapi id 14.03.0174.001; Mon, 17 Feb 2014 10:51:40 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ronald Bonica <rbonica@juniper.net>, "int-area@ietf.org" <int-area@ietf.org>
Thread-Topic: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
Thread-Index: AQHPKcAwQtqxEb4ArEW/XYeQB9i6GZq1MkcQgAR7o3A=
Date: Mon, 17 Feb 2014 18:51:40 +0000
Message-ID: <2134F8430051B64F815C691A62D983181D205B@XCH-BLV-504.nw.nos.boeing.com>
References: <68a71d0317c546689875cfb7a1a67f9b@CO1PR05MB442.namprd05.prod.outlook.com>
In-Reply-To: <68a71d0317c546689875cfb7a1a67f9b@CO1PR05MB442.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/llqPwfzlKUGaNmwCj7Dity0jTHE
Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Feb 2014 18:52:00 -0000

Hi Ron,

The document needs to talk about packet sizes for IP payload packets.
For IP payload packets no larger than MINMTU bytes, the GRE tunnel
MUST accommodate the packet even if a small amount of fragmentation
is necessary. (Here, the mandatory MINMTU for IPv6 is 1280 and the
recommended MINMTU for IPv4 is also 1280.)

Beyond MINMTU, there needs to be a balance between avoiding path
MTU related black holes for the source and avoiding excessive
fragmentation at the GRE tunnel egress. This balance is situation
dependent. For example, if the GRE tunnel ingress is located close
to the source, it should be reasonable to expect that the source
would be able to receive any ICMP PTB messages sent by the ingress.
Or, if the GRE tunnel egress is located close to the destination,
it should be reasonable to expect that the egress can perform a
small amount of reassembly.

If the GRE tunnel ingress is located "far" from the source, then it
must strive to ensure that packets up to 1500 bytes are accommodated
even if a small amount of fragmentation is necessary, since 1500 is
the MTU size configured by the vast majority of host links in the
Internet. For packets larger than 1500 bytes, the GRE tunnel ingress
should not allow fragmentation, as this would cause excessive
reassembly for the tunnel egress.

So, a suitable algorithm for the GRE tunnel ingress would be:

1) For IP payload packets no larger than MINMTU, encapsulate in the
   GRE delivery headers (with DF=3D0 in the outer IP header for IPv4).
   If the packet is larger than GMTU, fragment the delivery packet
   and send all fragments to the tunnel egress (or, for IPv4, allow
   the network to do the fragmentation). (If the delivery packet
   did not require fragmentation, then just send unfragmented.)=20

2) For IP payload packets larger than MINMTU but no larger than 1500,
   if the packet is larger than GMTU and the ingress is located near
   the source, drop the packet and return an ICMP PTB. Otherwise,
   encapsulate in the GRE delivery headers (DF=3D0). If the payload
   packet is larger than GMTU, fragment the delivery packet and
   send all fragments to the tunnel egress (or, for IPv4, allow
   the network to do the fragmentation). (If the delivery packet
   did not require fragmentation, then just send unfragmented.)

3) For IP payload packets larger than 1500, if the packet is larger
   than GMTU drop and return an ICMP PTB. If the packet is no larger
   than GMTU, encapsulate and send unfragmented with DF=3D1.

In this algorithm, if IPv4 is used as the delivery protocol and there
is reason to believe that some fragmentation may occur on the path,
the GRE tunnel ingress MUST institute rate limiting per RFC6864 to
ensure that no reassembly misassociations occur. The ingress can test
to see if fragmentation is needed by sending an occasional encapsulated
1500 byte "ping" packet to the egress for which no fragmentation is
permitted. If the ping succeeds, the ingress can suspend fragmentation
and/or rate limiting. (This would constitute RFC4821 for tunnels.)

As an added means for minimizing fragmentation, the GRE tunnel ingress
can use MSS clamping to rewrite the TCP MSS size in the IP payload
packet to a smaller size [RFC0879][RFC6691]. This option may not be
available to all GRE tunnel ingresses however (e.g., if there are
multiple nested levels of encapsulation).

An underlying assumption in all of this is that sources that send
IP packets larger than 1500 are expected to use RFC4821 to ensure
that the larger packets are not being dropped into a black hole.
This should become a BCP recommendation for the Internet even
without respect to tunneling.

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

> -----Original Message-----
> From: Int-area [mailto:int-area-bounces@ietf.org] On Behalf Of Ronald Bon=
ica
> Sent: Friday, February 14, 2014 12:26 PM
> To: int-area@ietf.org
> Subject: [Int-area] FW: New Version Notification for draft-bonica-intarea=
-gre-mtu-04.txt
>=20
> Folks,
>=20
> Please review and comment
>=20
>                 Ron
>=20
>=20
>=20
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: Friday, February 14, 2014 3:06 PM
> To: Ronald Bonica; Dr. Joseph D. Touch; Joe Touch; Carlos Pignataro; Rona=
ld Bonica; Carlos Pignataro
> Subject: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
>=20
>=20
> A new version of I-D, draft-bonica-intarea-gre-mtu-04.txt
> has been successfully submitted by Ron Bonica and posted to the IETF repo=
sitory.
>=20
> Name:		draft-bonica-intarea-gre-mtu
> Revision:	04
> Title:		A Fragmentation Strategy for Generic Routing Encapsulation (GRE)
> Document date:	2014-02-12
> Group:		Individual Submission
> Pages:		11
> URL:            http://www.ietf.org/internet-drafts/draft-bonica-intarea-=
gre-mtu-04.txt
> Status:         https://datatracker.ietf.org/doc/draft-bonica-intarea-gre=
-mtu/
> Htmlized:       http://tools.ietf.org/html/draft-bonica-intarea-gre-mtu-0=
4
> Diff:           http://www.ietf.org/rfcdiff?url2=3Ddraft-bonica-intarea-g=
re-mtu-04
>=20
> Abstract:
>    This memo specifies a default GRE tunnel fragmentation strategy,
>    which has been implemented by many vendors and widely deployed on the
>    Internet.
>=20
>    This memo also specifies requirements for GRE implementations.
>    Having satisfied these requirements, a GRE implementation will
>    execute the default GRE tunnel fragmentation strategy, specified
>    herein, with minimal configuration.  However, with additional
>    configuration, the GRE implementation can execute any of the tunnel
>    fragmentation strategies defined in RFC 4459.
>=20
>=20
>=20
>=20
>=20
> Please note that it may take a couple of minutes from the time of submiss=
ion until the htmlized
> version and diff are available at tools.ietf.org.
>=20
> The IETF Secretariat
>=20
>=20
>=20
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area


From nobody Mon Feb 17 15:48:18 2014
Return-Path: <eckelcu@cisco.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 109F81A02A7; Mon, 17 Feb 2014 15:48:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.049
X-Spam-Level: 
X-Spam-Status: No, score=-10.049 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4WjRiGDO7ikx; Mon, 17 Feb 2014 15:48:09 -0800 (PST)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) by ietfa.amsl.com (Postfix) with ESMTP id 23B0E1A05AB; Mon, 17 Feb 2014 15:48:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1761; q=dns/txt; s=iport; t=1392680880; x=1393890480; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=QoqWk12fundKaB/HrLol/DN8rhh9nUsC5AmVGElQyHg=; b=ZgzjjuTnmiabJGcYKzizeQqpx8T5Sh7bngACDfwmongiKI0nM4jC3MMG osdumeNOwwynm3HPIW1ayy74LMI45cv/8PuHjhTN0ai3Kp/iw0vUwvbt7 Rtmgbt6b7pfh4W/FG8aIVXdvVcqfW1p5GWuV1Z1GvEnxKHxDLpGugc8St 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhkFAMyeAlOtJV2a/2dsb2JhbABZgwY4V8BgFnSCJQEBAQQBAQFrHQEIOzILGwEGBQQBEogFDco+F44thRMEiRCPHIEykHGBb4E+gio
X-IronPort-AV: E=Sophos;i="4.95,863,1384300800"; d="scan'208";a="21133022"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-5.cisco.com with ESMTP; 17 Feb 2014 23:48:00 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s1HNlxS3001507 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 17 Feb 2014 23:48:00 GMT
Received: from xmb-aln-x08.cisco.com ([169.254.3.8]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.03.0123.003; Mon, 17 Feb 2014 17:47:59 -0600
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "int-area@ietf.org" <int-area@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: [Aeon] Time slots for AEON session at IETF 89 - Please indicate available via link below by Wed. Feb 19
Thread-Index: AQHPLDqvmtNJ9L8wukKWAsGpI1Inkg==
Date: Mon, 17 Feb 2014 23:47:59 +0000
Message-ID: <CF27D98B.1F2AF%eckelcu@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.9.131030
x-originating-ip: [10.21.79.36]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <E94AA9333DA921499FCE7E90809FD757@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/XbgMAQfglqDuCRaPiCwaLdWmArQ
Subject: [Int-area] FW: [Aeon] Time slots for AEON session at IETF 89 - Please indicate available via link below by Wed. Feb 19
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Feb 2014 23:48:13 -0000

Just an FYI, we posted and presented the following draft at previous IETF
meetings:

A Framework for Signaling Flow Characteristics between Applications and
the Network=20
(http://tools.ietf.org/html/draft-eckert-intarea-flow-metadata-framework-02
)

We have taken the feedback from this and created two new drafts, focusing
on the problem statement and use cases, respectively:
"Application Enabled Open Networking: Problem Statement and Requirements=B2=
,
draft-eckel-aeon-problem-statement-00
(http://tools.ietf.org/html/draft-eckel-aeon-problem-statement-00)
"Application Enabled Open Networking Use Cases=B2,
draft-eckel-aeon-use-cases-01
(http://tools.ietf.org/html/draft-eckel-aeon-use-cases-01)

If you are interested in this area, you should consider subscribing to the
AEON list and attending the meeting we are planning at IETF 89, as
announced in the forwarded e-mail.

Cheers,
Charles

On 2/17/14, 10:12 AM, "Charles Eckel (eckelcu)" <eckelcu@cisco.com> wrote:

>AEON list members and other interested parties,
>
>We plan to reserve an IESG breakout room to have an AEON meeting at IETF
>89 in London.
>Please indicate which of the potential time slots work for you no later
>than Wednesday, Feb 19.
>All time slots are 1 hour in duration.
>The actual location and time will be announced on the AEON list.
>
>
>Preliminary agenda is as follows:
>1) problem statement draft
>2) draft charter
>
>The agenda will be finalized via a separate thread on the AEON list as
>well.
>Here is the link to the poll:
>http://www.doodle.com/fb8k5hyqap4iqyye
>
>
>Cheers,
>Charles
>
>_______________________________________________
>Aeon mailing list
>Aeon@ietf.org
>https://www.ietf.org/mailman/listinfo/aeon


From nobody Mon Feb 17 20:39:42 2014
Return-Path: <chenycmx@gmail.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B36D01A05D8 for <int-area@ietfa.amsl.com>; Mon, 17 Feb 2014 20:39:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fqz6ak9w5uIt for <int-area@ietfa.amsl.com>; Mon, 17 Feb 2014 20:39:39 -0800 (PST)
Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 581C11A04B7 for <int-area@ietf.org>; Mon, 17 Feb 2014 20:39:39 -0800 (PST)
Received: by mail-pa0-f46.google.com with SMTP id rd3so16119569pab.19 for <int-area@ietf.org>; Mon, 17 Feb 2014 20:39:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=date:from:to:cc:reply-to:subject:references:mime-version:message-id :content-type:content-transfer-encoding; bh=d9MAcOweyJU26XLH/kuUJTECyg0IZmkv8nE6szdQqUE=; b=CC1nbze6qMFonJzGktIXQoLhgkTMfsQEaVKeD1aRljwI9Jlm+GFmA+12guPHMFtYmA zyCzyRexqhAnIq/2Jy5sTFpWKMbmgj6NUVG4TxHGTGmjjueWDojjiCnxzcIJaJme6QxU nxhBG2gAmboi2olMn10UXuGHZu4Ps0fZ0RhX+IBYx3pQwn3AoQLMvyZQYSpSuulbc4iA 29Vvrn0MBKTJfBhRoLoOchT74Gn1s27h1G8Cn7VjqR/Qz/sGa9VFluNTTtIObSfp56sF FnmJJbcUmpA7QmtMD0tOkOKthGgp26PHr2OdvH+TmRc8gLYsk5GNYhgjGQq9JGkhGG2v Fa/Q==
X-Received: by 10.66.121.68 with SMTP id li4mr30812645pab.33.1392698376386; Mon, 17 Feb 2014 20:39:36 -0800 (PST)
Received: from netlab-PC ([166.111.68.231]) by mx.google.com with ESMTPSA id dk1sm51243553pbc.46.2014.02.17.20.39.33 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 17 Feb 2014 20:39:35 -0800 (PST)
Date: Tue, 18 Feb 2014 12:39:34 +0800
From: "Yuchi Chen" <chenycmx@gmail.com>
To: meng.wei2 <meng.wei2@zte.com.cn>
References: <CF27D98B.1F2AF%eckelcu@cisco.com>
X-Priority: 3
X-GUID: BB1074F0-ACA1-4320-AF3F-F93FC9EAA7CE
X-Has-Attach: no
X-Mailer: Foxmail 7.0.1.92[cn]
Mime-Version: 1.0
Message-ID: <2014021812393182855966@gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: base64
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/77IDATDwXoTh9rcJA3Oaz3I1ZQI
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] [intarea]Comments on draft-cui-intarea-unified-v6-framework-00
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: chenycmx <chenycmx@gmail.com>
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2014 04:39:41 -0000

SGkgV2VpLA0KDQpUaGFua3MgZm9yIHRoZSByZXZpZXcuIFRoZSBwdXJwb3NlIG9mIHRoaXMgd29y
ayBpcyB0byBwcm92aWRlIGEgdW5pZmllZCBhbmQgZmxleGlibGUgZnJhbWV3b3JrIA0KZm9yIGlt
cGxlbWVudGluZyBhbmQgZGVwbG95aW5nIElQdjYgdHJhbnNpdGlvbiBtZWNoYW5pc21zLCBhbmQg
ZW5hYmxlIHRoZXNlIG1lY2hhbmlzbXMgDQp0byBjb2V4aXN0IGluIHRoZSBzYW1lIGluZnJhc3Ry
dWN0dXJlLiBQbGVhc2Ugc2VlIGlubGluZSBmb3IgdGhlIGRldGFpbGVkIHJlc3BvbnNlcy4NCg0K
QmVzdCByZWdhcmRzIQ0KLS0tLS0tLS0tLS0tLS0NCll1Y2hpIENoZW4NCg0KT24gMi8xNy8xNCwg
MTc6MzYgUE0sICJtZW5nLndlaTJAenRlLmNvbS5jbiIgPG1lbmcud2VpMkB6dGUuY29tLmNuPiB3
cm90ZToNCg0KPkhpIFlvbmcsIFl1Y2hpLCBhbGwNCj4gDQo+ICBUaGlzIGlzIGEgaW50ZXJlc3Rp
bmcgdG9waWMuIEkgcmV2aWV3ZWQgdGhpcyBkcmFmdCBhbmQgIGhhdmUgc29tZQ0KPmNvbW1lbnRz
IGFuZCBxdWVzdGlvbnMuDQogDQo+ICAxKSBJbiBzZWN0aW9uIDUNCiANCj4gICAiV2hlbiByZWNl
aXZpbmcgYW4gaW5jb21pbmcgcGFja2V0IHRoYXQgZG9lc24ndCBoYXZlIGEgbWF0Y2ggaW4gdGhl
DQo+ICAgZmxvdyB0YWJsZSAodXN1YWxseSB0aGUgaW50aWFsIHBhY2tldCBvZiBhIG5ldyBmbG93
KSwgQ1BFIFN3aXRjaCBhbmQNCj4gICBCUiBTd2l0Y2ggTVVTVCBmb3J3YXJkIHRoZSBwYWNrZXQg
dG8gQ29udHJvbGxlci4gIENvbnRyb2xsZXIgTVVTVA0KPiAgIGRldGVybWluZSBob3cgdG8gcHJv
Y2VlZCB0aGUgZmxvdyAoZS5nLiB3aGV0aGVyIHRvIGFwcGx5IE5BVC8gTkFUNjQNCj4gICB0cmFu
c2xhdGlvbiBhbmQvIG9yIHNvZnR3aXJlIGVuY2Fwc2x1YXRvbi8gZGVjYXB1c2x1dGFpb24pLCBh
bmQNCj4gICBpbnRlcnByZXQgdGhlIHByb2Nlc3MgaW50byBhIHNldCBvZiBmb3J3YXJkaW5nIHJ1
bGUgY29uZmlndXJhdGlvbnMuDQo+ICAgQ29udHJvbGxlciB0aGVuIHBhc3NlcyB0aGVzZSBjb25m
aWd1cmF0aW9ucyB0byBDUEUgU3d0aWNoIGFuZCBCUg0KPiAgIFN3aXRjaC4gIENQRSBTd2l0Y2gg
YW5kIEJSIFN3aXRjaCB0aGVuIGNvbmZpZ3VyZSB0aGVpciBmbG93IHRhYmxlDQo+ICAgYWNjb3Jk
aW5nIHRvIHRoZXNlIGNvbmZpZ3VyYXRpb25zLCINCj4gDQo+ICBXaHkgbm90IGxldCBjb250cm9s
bGVyIGNyZWF0ZSBmbG93IHRhYmxlLiBTaW5jZSBwYWNrZXQgaXMgcmVjZWl2ZWQgYnkNCj5jb250
cm9sbGVyLCB3aHkgbm90IGxldCBpdCBkbyBtb3JlPw0KW3l1Y2hpXSBJbiB0aGlzIGZyYW1ld29y
ayBzd2l0Y2ggc2hvdWxkIGRvIHBhY2tldCBmb3J3YXJkaW5nLCBqdXN0IGxpa2UgdHJhZGl0aW9u
YWwgcm91dGVyIChvciBMMyBzd2l0Y2gpLiBUaGUNCm1haW4gZGlmZmVyZW5jZSBpcyB0aGF0IHN3
aXRjaCBkb2Vzbid0IGtub3cgYW55IG90aGVyIGluZm9ybWF0aW9uIGV4Y2VwdCBmb3IgaW5mb3Jt
YXRpb24gb2YgZmxvd3MgcGFzc2luZyBieSwgDQp3aGljaCBpcyBtYWludGFpbmVkIGluIHRoZSBm
bG93IHRhYmxlLiBDb250cm9sbGVyIC0gYSBjZW50cmFsaXplZCAoY2x1c3RlciBvZikgZGV2aWNl
KHMpIGF0IGEgaGlnaGVyIGxldmVsIGluIHRoZSANCm5ldHdvcmsgLSBrbm93cyBldmVyeXRoaW5n
IChlLmcuIHRvcG9sb2d5LCByb3V0aW5nLCBOQVQgc3RhdGVzLCBldGMpIG9mIHRoZSBuZXR3b3Jr
LiBJdCBjYW4gdGVsbCBhIHN3aXRjaCBob3cgDQp0byBwcm9jZWVkIGFuZCBmb3J3YXJkIHBhY2tl
dHMgb2YgZWFjaCBmbG93IGJ5IGNvbmZpZ3VyaW5nIHRoZSBmbG93IHRhYmxlIG1haW50YWluZWQg
Ynkgc3dpdGNoLiBIZW5jZSANCmNvbnRyb2xsZXIganVzdCBuZWVkcyB0byBkZWFsIHdpdGggdGhl
IGZpcnN0IHBhY2tldCBvZiBhIGZsb3csIGRldGVybWluZSBob3cgdG8gcHJvY2VlZCB0aGUgZmxv
dywgdGhlbiBsZXQgdGhlIA0Kc3dpdGNoIGRvIHRoZSByZXN0LiBJIHRoaW5rIGl0IG1pZ2h0IG5v
dCBiZSBlZmZpY2llbnQgYW5kIG1heSBsZWFkIHRvIG1lc3NhZ2UgY29uZ2VzdGlvbiBpZiBsZXQg
Y29udHJvbGxlciBkbyBhbGwgDQp0aGUgcGFja2V0IGZvcndhcmRpbmcuDQoNCj4gIEJUVywgZG9l
cyAidXN1YWxseSB0aGUgaW50aWFsIHBhY2tldCBvZiBhIG5ldyBmbG93IiBtZWFuIGFuIGludGlh
bCANCj5wYWNrZXQNCj5vZiBlYWNoIHNlc3Npb24/IElmIHNvLCBpdCBtaWdodCBsZWFkIHRvIG1l
c3NhZ2UgY29uZ2VzdGlvbiBiZXR3ZWVuIHN3aXRjaCANCj4mDQo+Y29udHJvbGxlci4NClt5dWNo
aV0gWWVzLCBzd2l0Y2ggc2hvdWxkIGZvcndhcmQgdGhlIGluaXRhbCBwYWNrZXQgb2YgZWFjaCBv
ZiB1bmtub3duIGZsb3dzIHRvIGNvbnRyb2xsZXIuIEkgYWdyZWUgdGhhdCANCml0IGluZGVlZCBt
YXkgbGVhZCB0byBjb25nZXN0aW9uIGlmIHRoZXJlIGFyZSB0b28gbWFueSBuZXcgZmxvd3MgY29u
Y3VycmVudGx5IHBhc3NpbmcgdGhyb3VnaCBzd2l0Y2guIA0KSG93ZXZlciwgYXMgY29udHJvbGxl
ciBhdCB0aGUgc2FtZSB0aW1lIG9ubHkgZGVhbHMgd2l0aCBwYWNrZXRzIG5vIG1vcmUgdGhhbiB0
aGUgbnVtYmVyIG9mIGNvbmN1cnJlbnQgDQpmbG93cyBwYXNzaW5nIHRocm91Z2ggc3dpdGNoZXMg
aXQgY29ubmVjdHMgdG8gKG5vdGUgdGhhdCBhbGwgdGhlIG91dGJvdW5kIGFuZCBpbmJvdW5kIHBh
Y2tldHMgb2YgYSBzZXNzaW9uIA0KY2FuIGJlIHJlZ2FyZGVkIGFzIGJlbG9uZ2luZyB0byB0aGUg
c2FtZSBmbG93KSwgSSB0aGluayB0aGUgY29uZ2VzdGlvbiBpcyBsZXNzIGxpa2VseSB0byBvY2N1
ciBhbmQgY2FuIGJlIA0KbWl0aWdhdGVkIGVhc2lseS4NCg0KPiANCj4gIDIpIFdoYXQgaXMgdGhl
IGNvbmNyZXRlIGNvbnNpZGVyYXRpb24gYmV0d2VlbiBDUEUvQlIgJiBjb250cm9sbGVyPyANCj5z
dWNoIGFzIG5ldGNvbmZpZywgaTJycy4NCj4gDQpbeXVjaGldIFRoZSBjb25jcmV0ZSBpbnRlcmZh
Y2UgKGlmIHRoaXMgaXMgd2hhdCB5b3UgbWVhbikgYmV0d2VlbiBzd2l0Y2ggYW5kIGNvbnRyb2xs
ZXIgaXMgbm90IHNwZWNpZmllZC4gDQpJTUhPIGFsbCB0aGUgcHJvdG9jb2xzIChvciBpbnRlcmZh
Y2VzKSB0aGF0IGFyZSBhYmxlIHRvIGNhcnJ5IGZsb3cgaW5mb3JtYXRpb24gYW5kIGZsb3cgdGFi
bGUgY29uZmlndXJhdGlvbiANCmNhbiBiZSBhZG9wdGVkLg0KDQo+ICAzKSBMb2dnaW5nIGlzIGlt
cG9ydGFudCBpbiBOQVQsIHdoYXQgaXMgdGhlIGNvbnNpZGVyYXRpb24gYWJvdXQgaXQ/DQo+TWF5
YmUgYSBzd2l0Y2ggaXMgbm90IHN1aXRhYmxlIGZvciBsb2dnaW5nIGl0c2VsZi4NClt5dWNoaV0g
VGhlIGxvZ2dpbmcgb2YgYSBzd2l0Y2ggY2FuIGJlIGRvbmUgYnkgaXRzIGFzc29jaWF0ZWQgY29u
dHJvbGxlci4gVGhlIGNvbnRyb2xsZXIgaXMgcmVzcG9uc2libGUgZm9yIA0KbWFpbnRhaW5pbmcg
YWxsIHN0YXRlcyB0aGF0IGlzIHJlbGF0ZWQgdG8gdGhlIHN3aXRjaCwgc3VjaCBhcyBOQVQ0NCBz
dGF0ZSBhbmQgZmxvdyB0YWJsZSAoaWYgbmVlZGVkKS4gDQo+IA0KPg0KPlRoYW5rcywNCj5XZWkN
Cj4NCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4g
SW50LWFyZWEgbWFpbGluZyBsaXN0DQo+IEludC1hcmVhQGlldGYub3JnDQo+IGh0dHBzOi8vd3d3
LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaW50LWFyZWENCg==


From nobody Mon Feb 17 23:16:57 2014
Return-Path: <meng.wei2@zte.com.cn>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B8ED1A05E9 for <int-area@ietfa.amsl.com>; Mon, 17 Feb 2014 23:16:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.847
X-Spam-Level: 
X-Spam-Status: No, score=-101.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_82=0.6, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.548, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RcNFeUC05jLX for <int-area@ietfa.amsl.com>; Mon, 17 Feb 2014 23:16:50 -0800 (PST)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id 9F10F1A05DD for <int-area@ietf.org>; Mon, 17 Feb 2014 23:16:49 -0800 (PST)
Received: from mse02.zte.com.cn (unknown [10.30.3.21]) by Websense Email Security Gateway with ESMTPS id F1C5C12A6323; Tue, 18 Feb 2014 15:16:34 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id s1I7FxaD023542; Tue, 18 Feb 2014 15:15:59 +0800 (GMT-8) (envelope-from meng.wei2@zte.com.cn)
In-Reply-To: <2014021812393182855966@gmail.com>
To: chenycmx <chenycmx@gmail.com>
MIME-Version: 1.0
X-KeepSent: 1DD91406:05BE610A-48257C83:0024E099; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF1DD91406.05BE610A-ON48257C83.0024E099-48257C83.00281864@zte.com.cn>
From: meng.wei2@zte.com.cn
Date: Tue, 18 Feb 2014 15:15:55 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2014-02-18 15:15:45, Serialize complete at 2014-02-18 15:15:45
Content-Type: multipart/alternative; boundary="=_alternative 0028185D48257C83_="
X-MAIL: mse02.zte.com.cn s1I7FxaD023542
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/oCFHZVeOv7rlOimoTpFc40zmrug
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] [intarea]Comments on draft-cui-intarea-unified-v6-framework-00
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2014 07:16:56 -0000

This is a multipart message in MIME format.
--=_alternative 0028185D48257C83_=
Content-Type: text/plain; charset="US-ASCII"

Hi,yuchi,

  PLS see inline.

Thanks,
Wei



"Yuchi Chen" <chenycmx@gmail.com> 2014-02-18 12:39:34:

> Hi Wei,
> 
> Thanks for the review. The purpose of this work is to provide a 
> unified and flexible framework 
> for implementing and deploying IPv6 transition mechanisms, and 
> enable these mechanisms 
> to coexist in the same infrastructure. Please see inline for the 
> detailed responses.
> 
> Best regards!
> --------------
> Yuchi Chen
> 
> On 2/17/14, 17:36 PM, "meng.wei2@zte.com.cn" <meng.wei2@zte.com.cn> 
wrote:
> 
> >Hi Yong, Yuchi, all
> > 
> >  This is a interesting topic. I reviewed this draft and  have some
> >comments and questions.
> 
> >  1) In section 5
> 
> >   "When receiving an incoming packet that doesn't have a match in the
> >   flow table (usually the intial packet of a new flow), CPE Switch and
> >   BR Switch MUST forward the packet to Controller.  Controller MUST
> >   determine how to proceed the flow (e.g. whether to apply NAT/ NAT64
> >   translation and/ or softwire encapsluaton/ decapuslutaion), and
> >   interpret the process into a set of forwarding rule configurations.
> >   Controller then passes these configurations to CPE Swtich and BR
> >   Switch.  CPE Switch and BR Switch then configure their flow table
> >   according to these configurations,"
> > 
> >  Why not let controller create flow table. Since packet is received by
> >controller, why not let it do more?
> [yuchi] In this framework switch should do packet forwarding, just 
> like traditional router (or L3 switch). The
> main difference is that switch doesn't know any other information 
> except for information of flows passing by, 
> which is maintained in the flow table. Controller - a centralized 
> (cluster of) device(s) at a higher level in the 
> network - knows everything (e.g. topology, routing, NAT states, etc)
> of the network. It can tell a switch how 
> to proceed and forward packets of each flow by configuring the flow 
> table maintained by switch. Hence 
> controller just needs to deal with the first packet of a flow, 
> determine how to proceed the flow, then let the 
> switch do the rest. I think it might not be efficient and may lead 
> to message congestion if let controller do all 
> the packet forwarding.
> 
> >  BTW, does "usually the intial packet of a new flow" mean an intial 
> >packet
> >of each session? If so, it might lead to message congestion between 
switch 
> >&
> >controller.
> [yuchi] Yes, switch should forward the inital packet of each of 
> unknown flows to controller. I agree that 
> it indeed may lead to congestion if there are too many new flows 
> concurrently passing through switch. 
> However, as controller at the same time only deals with packets no 
> more than the number of concurrent 
> flows passing through switches it connects to (note that all the 
> outbound and inbound packets of a session 
> can be regarded as belonging to the same flow), I think the 
> congestion is less likely to occur and can be 
> mitigated easily.

[Wei] I agree. Congestion might hardly occur in normal network traffic.
Anyway, the rate of  creating new sessions is a key performance indexes of
per apparatus under traditional routing scenario. 
  My proposal is that we should consider how to maintain existing 
performance
per apparatus (switch/router) while finding a way to unify IPv6 transition 

technologies.
  i.e. reasonable number of controllers in network...


> 
> > 
> >  2) What is the concrete consideration between CPE/BR & controller? 
> >such as netconfig, i2rs.
> > 
> [yuchi] The concrete interface (if this is what you mean) between 
> switch and controller is not specified. 
> IMHO all the protocols (or interfaces) that are able to carry flow 
> information and flow table configuration 
> can be adopted.
> 
> >  3) Logging is important in NAT, what is the consideration about it?
> >Maybe a switch is not suitable for logging itself.
> [yuchi] The logging of a switch can be done by its associated 
> controller. The controller is responsible for 
> maintaining all states that is related to the switch, such as NAT44 
> state and flow table (if needed). 

[Wei]If so, does a switch need to send its NAT44 sessions(or flow tables) 
to
the controller? 


> > 
> >
> >Thanks,
> >Wei
> >
> > _______________________________________________
> > Int-area mailing list
> > Int-area@ietf.org
> > https://www.ietf.org/mailman/listinfo/int-area

--=_alternative 0028185D48257C83_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Hi,yuchi,</font>
<br>
<br><font size=2 face="sans-serif">&nbsp; PLS see inline.</font>
<br>
<br><font size=2 face="sans-serif">Thanks,</font>
<br><font size=2 face="sans-serif">Wei</font>
<br>
<br>
<br>
<br><tt><font size=2>&quot;Yuchi Chen&quot; &lt;chenycmx@gmail.com&gt;
2014-02-18 12:39:34:<br>
<br>
&gt; Hi Wei,<br>
&gt; <br>
&gt; Thanks for the review. The purpose of this work is to provide a <br>
&gt; unified and flexible framework <br>
&gt; for implementing and deploying IPv6 transition mechanisms, and <br>
&gt; enable these mechanisms <br>
&gt; to coexist in the same infrastructure. Please see inline for the <br>
&gt; detailed responses.<br>
&gt; <br>
&gt; Best regards!<br>
&gt; --------------<br>
&gt; Yuchi Chen<br>
&gt; <br>
&gt; On 2/17/14, 17:36 PM, &quot;meng.wei2@zte.com.cn&quot; &lt;meng.wei2@zte.com.cn&gt;
wrote:<br>
&gt; <br>
&gt; &gt;Hi Yong, Yuchi, all<br>
&gt; &gt; <br>
&gt; &gt; &nbsp;This is a interesting topic. I reviewed this draft and
&nbsp;have some<br>
&gt; &gt;comments and questions.<br>
&gt; &nbsp;<br>
&gt; &gt; &nbsp;1) In section 5<br>
&gt; &nbsp;<br>
&gt; &gt; &nbsp; &quot;When receiving an incoming packet that doesn't have
a match in the<br>
&gt; &gt; &nbsp; flow table (usually the intial packet of a new flow),
CPE Switch and<br>
&gt; &gt; &nbsp; BR Switch MUST forward the packet to Controller. &nbsp;Controller
MUST<br>
&gt; &gt; &nbsp; determine how to proceed the flow (e.g. whether to apply
NAT/ NAT64<br>
&gt; &gt; &nbsp; translation and/ or softwire encapsluaton/ decapuslutaion),
and<br>
&gt; &gt; &nbsp; interpret the process into a set of forwarding rule configurations.<br>
&gt; &gt; &nbsp; Controller then passes these configurations to CPE Swtich
and BR<br>
&gt; &gt; &nbsp; Switch. &nbsp;CPE Switch and BR Switch then configure
their flow table<br>
&gt; &gt; &nbsp; according to these configurations,&quot;<br>
&gt; &gt; <br>
&gt; &gt; &nbsp;Why not let controller create flow table. Since packet
is received by<br>
&gt; &gt;controller, why not let it do more?<br>
&gt; [yuchi] In this framework switch should do packet forwarding, just
<br>
&gt; like traditional router (or L3 switch). The<br>
&gt; main difference is that switch doesn't know any other information
<br>
&gt; except for information of flows passing by, <br>
&gt; which is maintained in the flow table. Controller - a centralized
<br>
&gt; (cluster of) device(s) at a higher level in the <br>
&gt; network - knows everything (e.g. topology, routing, NAT states, etc)<br>
&gt; of the network. It can tell a switch how <br>
&gt; to proceed and forward packets of each flow by configuring the flow
<br>
&gt; table maintained by switch. Hence <br>
&gt; controller just needs to deal with the first packet of a flow, <br>
&gt; determine how to proceed the flow, then let the <br>
&gt; switch do the rest. I think it might not be efficient and may lead
<br>
&gt; to message congestion if let controller do all <br>
&gt; the packet forwarding.<br>
&gt; <br>
&gt; &gt; &nbsp;BTW, does &quot;usually the intial packet of a new flow&quot;
mean an intial <br>
&gt; &gt;packet<br>
&gt; &gt;of each session? If so, it might lead to message congestion between
switch <br>
&gt; &gt;&amp;<br>
&gt; &gt;controller.<br>
&gt; [yuchi] Yes, switch should forward the inital packet of each of <br>
&gt; unknown flows to controller. I agree that <br>
&gt; it indeed may lead to congestion if there are too many new flows <br>
&gt; concurrently passing through switch. <br>
&gt; However, as controller at the same time only deals with packets no
<br>
&gt; more than the number of concurrent <br>
&gt; flows passing through switches it connects to (note that all the <br>
&gt; outbound and inbound packets of a session <br>
&gt; can be regarded as belonging to the same flow), I think the <br>
&gt; congestion is less likely to occur and can be <br>
&gt; mitigated easily.</font></tt>
<br>
<br><tt><font size=2>[Wei] I agree. Congestion might hardly occur in normal
network traffic.</font></tt>
<br><tt><font size=2>Anyway, the rate of &nbsp;creating new sessions is
a key performance indexes of</font></tt>
<br><tt><font size=2>per apparatus under traditional routing scenario.
</font></tt>
<br><tt><font size=2>&nbsp; My proposal is that we should consider how
to maintain existing performance</font></tt>
<br><tt><font size=2>per apparatus (switch/router) while finding a way
to unify IPv6 transition </font></tt>
<br><tt><font size=2>technologies.</font></tt>
<br><tt><font size=2>&nbsp; i.e. reasonable number of controllers in network...</font></tt>
<br>
<br><tt><font size=2><br>
&gt; <br>
&gt; &gt; <br>
&gt; &gt; &nbsp;2) What is the concrete consideration between CPE/BR &amp;
controller? <br>
&gt; &gt;such as netconfig, i2rs.<br>
&gt; &gt; <br>
&gt; [yuchi] The concrete interface (if this is what you mean) between
<br>
&gt; switch and controller is not specified. <br>
&gt; IMHO all the protocols (or interfaces) that are able to carry flow
<br>
&gt; information and flow table configuration <br>
&gt; can be adopted.<br>
&gt; <br>
&gt; &gt; &nbsp;3) Logging is important in NAT, what is the consideration
about it?<br>
&gt; &gt;Maybe a switch is not suitable for logging itself.<br>
&gt; [yuchi] The logging of a switch can be done by its associated <br>
&gt; controller. The controller is responsible for <br>
&gt; maintaining all states that is related to the switch, such as NAT44
<br>
&gt; state and flow table (if needed). </font></tt>
<br>
<br><tt><font size=2>[Wei]If so, does a switch need to send its NAT44 sessions(or
flow tables) to</font></tt>
<br><tt><font size=2>the controller? </font></tt>
<br>
<br><tt><font size=2><br>
&gt; &gt; <br>
&gt; &gt;<br>
&gt; &gt;Thanks,<br>
&gt; &gt;Wei<br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; Int-area mailing list<br>
&gt; &gt; Int-area@ietf.org<br>
&gt; &gt; https://www.ietf.org/mailman/listinfo/int-area<br>
</font></tt>
--=_alternative 0028185D48257C83_=--


From nobody Tue Feb 18 00:46:51 2014
Return-Path: <chenycmx@gmail.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 559331A009E for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 00:46:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, J_CHICKENPOX_82=0.6, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J8FOomQHdbwn for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 00:46:42 -0800 (PST)
Received: from mail-pd0-x230.google.com (mail-pd0-x230.google.com [IPv6:2607:f8b0:400e:c02::230]) by ietfa.amsl.com (Postfix) with ESMTP id A4A0A1A005A for <int-area@ietf.org>; Tue, 18 Feb 2014 00:46:42 -0800 (PST)
Received: by mail-pd0-f176.google.com with SMTP id w10so15919768pde.7 for <int-area@ietf.org>; Tue, 18 Feb 2014 00:46:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=date:from:to:cc:reply-to:subject:references:mime-version:message-id :content-type:content-transfer-encoding; bh=+DWEvbbj0c+fF//98yJvZ5I6wUYkYHUOVokx0bYWJ+Y=; b=El2SHNRSiTNLLdzHTCh5qn8CikR6wW18GiiduQP+gPV0SXGCYZILagy/qFwT2hRbAS oN1hYNYYXfzjMhwFgB9UoKrWEgb14dPrwdQibRobZV1SudKKYj9RLPPm894ToFiOVOXZ PegNx9LCHP4WSf2/0mkGlIV/k2vvobz7Q2uZ0BVd8d5I60+lquynnWMc9uL8NHFIZiF1 IrraCjDULzeysDJSrNq4y1ylZYkhHjBNaXyq+QtmNaHSovdeZSzun0imI/En0ve+/Hzg RUwemfzkjZx69g8UELb9C4iYaR4fVHfjG1pJEE10lmC6+7NgwdlOTOAZLS7s4/oqxgNy Cgig==
X-Received: by 10.68.136.162 with SMTP id qb2mr32019538pbb.88.1392713199897; Tue, 18 Feb 2014 00:46:39 -0800 (PST)
Received: from netlab-PC ([166.111.68.231]) by mx.google.com with ESMTPSA id x5sm53517566pbw.26.2014.02.18.00.46.36 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 18 Feb 2014 00:46:38 -0800 (PST)
Date: Tue, 18 Feb 2014 16:46:37 +0800
From: "Yuchi Chen" <chenycmx@gmail.com>
To: meng.wei2 <meng.wei2@zte.com.cn>
References: <OF1DD91406.05BE610A-ON48257C83.0024E099-48257C83.00281864@zte.com.cn>
X-Priority: 3
X-GUID: A87EA19D-70F5-40CB-AC13-AB145ED6961D
X-Has-Attach: no
X-Mailer: Foxmail 7.0.1.92[cn]
Mime-Version: 1.0
Message-ID: <2014021816463439239482@gmail.com>
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/wrNC1_XrF7NModZtJQE7GPM8JV0
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] [intarea]Comments on draft-cui-intarea-unified-v6-framework-00
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: chenycmx <chenycmx@gmail.com>
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2014 08:46:44 -0000

SGkgV2VpLA0KDQpQbGVhc2Ugc2VlIGlubGluZS4NCg0KQmVzdCByZWdhcmRzIQ0KLS0tLS0tLS0t
LS0tLS0NCll1Y2hpIENoZW4NCg0KT24gMjAxNC0wMi0xOCwgMTU6MTUsICJtZW5nLndlaTIiIDxt
ZW5nLndlaTJAenRlLmNvbS5jbj4gd3JvdGU6DQo+W1dlaV0gSSBhZ3JlZS4gQ29uZ2VzdGlvbiBt
aWdodCBoYXJkbHkgb2NjdXIgaW4gbm9ybWFsIG5ldHdvcmsgdHJhZmZpYy4NCj5Bbnl3YXksIHRo
ZSByYXRlIG9mICBjcmVhdGluZyBuZXcgc2Vzc2lvbnMgaXMgYSBrZXkgcGVyZm9ybWFuY2UgaW5k
ZXhlcyBvZg0KPnBlciBhcHBhcmF0dXMgdW5kZXIgdHJhZGl0aW9uYWwgcm91dGluZyBzY2VuYXJp
by4gDQo+ICBNeSBwcm9wb3NhbCBpcyB0aGF0IHdlIHNob3VsZCBjb25zaWRlciBob3cgdG8gbWFp
bnRhaW4gZXhpc3RpbmcgDQo+cGVyZm9ybWFuY2UNCj5wZXIgYXBwYXJhdHVzIChzd2l0Y2gvcm91
dGVyKSB3aGlsZSBmaW5kaW5nIGEgd2F5IHRvIHVuaWZ5IElQdjYgdHJhbnNpdGlvbiANCj4NCj50
ZWNobm9sb2dpZXMuDQo+ICBpLmUuIHJlYXNvbmFibGUgbnVtYmVyIG9mIGNvbnRyb2xsZXJzIGlu
IG5ldHdvcmsuLi4NCg0KW3l1Y2hpXSBZZXMsIHRoYW5rcyBmb3IgeW91ciBzdWdnZXN0aW9uLiBU
aGUgc2NlbmFyaW8gb2YgdXNpbmcgc2V2ZXJhbCBjb250cm9sbGVyDQppcyBtZW50aW9uZWQgKGUu
Zy4sICJDb250cm9sbGVyIGNhbiBiZSBhIHNpbmdsZSBkZXZpY2Ugb3IgYSBjbHVzdGVyIG9mIGRl
dmljZXMiIGluIA0KQnVsbGV0IDMgb2YgVGVybWlub2xvZ3kgU2VjdGlvbikuIEkgdGhpbmsgdGhp
cyBzY2VuYXJpbyBjYW4gYmUgZGlzY3Vzc2VkIGluIG1vcmUgDQpkZXRhaWwgaW4gdGhlIHRleHQu
IA0KDQo+PiBbeXVjaGldIFRoZSBsb2dnaW5nIG9mIGEgc3dpdGNoIGNhbiBiZSBkb25lIGJ5IGl0
cyBhc3NvY2lhdGVkIA0KPj4gY29udHJvbGxlci4gVGhlIGNvbnRyb2xsZXIgaXMgcmVzcG9uc2li
bGUgZm9yIA0KPj4gbWFpbnRhaW5pbmcgYWxsIHN0YXRlcyB0aGF0IGlzIHJlbGF0ZWQgdG8gdGhl
IHN3aXRjaCwgc3VjaCBhcyBOQVQ0NCANCj4+IHN0YXRlIGFuZCBmbG93IHRhYmxlIChpZiBuZWVk
ZWQpLiANCj4NCj5bV2VpXUlmIHNvLCBkb2VzIGEgc3dpdGNoIG5lZWQgdG8gc2VuZCBpdHMgTkFU
NDQgc2Vzc2lvbnMob3IgZmxvdyB0YWJsZXMpIA0KPnRvDQo+dGhlIGNvbnRyb2xsZXI/IA0KPg0K
DQpbeXVjaGldIE5BVDQ0IHByb2Nlc3MgY2FuIGJlIGludGVycHJldGVkIGludG8gYWN0aW9ucyBh
bmQgcmVjb3JkZWQgaW4gdGhlIGZsb3cgdGFibGUuIEhlbmNlIA0KSSB0aGluayBzd2l0Y2ggZG9l
cyBub3QgaGF2ZSB0byBtYWludGFpbiBOQVQ0NCBzZXNzaW9uIHN0YXRlIChpZiB0aGlzIGlzIHdo
YXQgeW91IG1lYW4pLiANCg0KT24gdGhlIG90aGVyIGhhbmQsIGNvbnRyb2xsZXIgY2FuIGVzdGFi
bGlzaCByZWxhdGVkIHN0YXRlcyBhY2NvcmRpbmcgdG8gdGhlIGluaXRhbCBwYWNrZXQgb2YgZWFj
aCBmbG93LCANCndoaWNoIGlzIHdoYXQgc3dpdGNoIG5lZWRzIHRvIHNlbmQgdG8gY29udHJvbGxl
ci4gSWYgY29udHJvbGxlciBuZWVkcyB0aGUgaW5mb3JtYXRpb24gb2YgdGhlIGZsb3cgdGFibGUg
DQptYWludGFpbmVkIGJ5IHN3aXRjaCwgaXQgY2FuIGFzayBzd2l0Y2ggdG8gc2VuZCB0aGF0LiBI
ZW5jZSBzd2l0Y2ggaXMgbm90IHJlcXVpcmVkIHRvIHNlbmQgaXRzIGZsb3cgdGFibGUgDQp0byBj
b250cm9sbGVyIGJ5IGRlZmF1bHQuIA0K


From nobody Tue Feb 18 01:16:15 2014
Return-Path: <meng.wei2@zte.com.cn>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B500E1A00AF for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 01:16:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.847
X-Spam-Level: 
X-Spam-Status: No, score=-101.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_82=0.6, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.548, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sOG28jv_Nf9k for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 01:16:12 -0800 (PST)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id 510C21A00A6 for <int-area@ietf.org>; Tue, 18 Feb 2014 01:16:12 -0800 (PST)
Received: from zte.com.cn (unknown [192.168.168.119]) by Websense Email Security Gateway with ESMTP id 6EA8D12A9502 for <int-area@ietf.org>; Tue, 18 Feb 2014 17:15:56 +0800 (CST)
Received: from mse02.zte.com.cn (unknown [10.30.3.21]) by Websense Email Security Gateway with ESMTPS id 6A96370C99B; Tue, 18 Feb 2014 17:15:55 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id s1I9FuUf044939; Tue, 18 Feb 2014 17:15:56 +0800 (GMT-8) (envelope-from meng.wei2@zte.com.cn)
In-Reply-To: <2014021816463439239482@gmail.com>
To: chenycmx <chenycmx@gmail.com>
MIME-Version: 1.0
X-KeepSent: A466A5D8:34EB23FF-48257C83:00318B8B; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OFA466A5D8.34EB23FF-ON48257C83.00318B8B-48257C83.003313DB@zte.com.cn>
From: meng.wei2@zte.com.cn
Date: Tue, 18 Feb 2014 17:15:52 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2014-02-18 17:15:42, Serialize complete at 2014-02-18 17:15:42
Content-Type: multipart/alternative; boundary="=_alternative 003313D848257C83_="
X-MAIL: mse02.zte.com.cn s1I9FuUf044939
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/zmInae_yhZVM9ic33oF8b2JdL90
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] [intarea]Comments on draft-cui-intarea-unified-v6-framework-00
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2014 09:16:14 -0000

This is a multipart message in MIME format.
--=_alternative 003313D848257C83_=
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: base64

SGkgWXVjaHVpo6wNCg0KICBQTFMgc2VlIGlubGluZS4NCg0KVGhhbmtzo6wNCldlaQ0KDQoiWXVj
aGkgQ2hlbiIgPGNoZW55Y214QGdtYWlsLmNvbT4gIDIwMTQtMDItMTggMTY6NDY6Mzc6DQoNCj4g
SGkgV2VpLA0KPiANCj4gUGxlYXNlIHNlZSBpbmxpbmUuDQo+IA0KPiBCZXN0IHJlZ2FyZHMhDQo+
IC0tLS0tLS0tLS0tLS0tDQo+IFl1Y2hpIENoZW4NCj4gDQo+IE9uIDIwMTQtMDItMTgsIDE1OjE1
LCAibWVuZy53ZWkyIiA8bWVuZy53ZWkyQHp0ZS5jb20uY24+IHdyb3RlOg0KPiA+W1dlaV0gSSBh
Z3JlZS4gQ29uZ2VzdGlvbiBtaWdodCBoYXJkbHkgb2NjdXIgaW4gbm9ybWFsIG5ldHdvcmsgdHJh
ZmZpYy4NCj4gPkFueXdheSwgdGhlIHJhdGUgb2YgIGNyZWF0aW5nIG5ldyBzZXNzaW9ucyBpcyBh
IGtleSBwZXJmb3JtYW5jZSBpbmRleGVzIA0Kb2YNCj4gPnBlciBhcHBhcmF0dXMgdW5kZXIgdHJh
ZGl0aW9uYWwgcm91dGluZyBzY2VuYXJpby4gDQo+ID4gIE15IHByb3Bvc2FsIGlzIHRoYXQgd2Ug
c2hvdWxkIGNvbnNpZGVyIGhvdyB0byBtYWludGFpbiBleGlzdGluZyANCj4gPnBlcmZvcm1hbmNl
DQo+ID5wZXIgYXBwYXJhdHVzIChzd2l0Y2gvcm91dGVyKSB3aGlsZSBmaW5kaW5nIGEgd2F5IHRv
IHVuaWZ5IElQdjYgDQp0cmFuc2l0aW9uIA0KPiA+DQo+ID50ZWNobm9sb2dpZXMuDQo+ID4gIGku
ZS4gcmVhc29uYWJsZSBudW1iZXIgb2YgY29udHJvbGxlcnMgaW4gbmV0d29yay4uLg0KPiANCj4g
W3l1Y2hpXSBZZXMsIHRoYW5rcyBmb3IgeW91ciBzdWdnZXN0aW9uLiBUaGUgc2NlbmFyaW8gb2Yg
dXNpbmcgDQo+IHNldmVyYWwgY29udHJvbGxlcg0KPiBpcyBtZW50aW9uZWQgKGUuZy4sICJDb250
cm9sbGVyIGNhbiBiZSBhIHNpbmdsZSBkZXZpY2Ugb3IgYSBjbHVzdGVyIA0KPiBvZiBkZXZpY2Vz
IiBpbiANCj4gQnVsbGV0IDMgb2YgVGVybWlub2xvZ3kgU2VjdGlvbikuIEkgdGhpbmsgdGhpcyBz
Y2VuYXJpbyBjYW4gYmUgDQo+IGRpc2N1c3NlZCBpbiBtb3JlIA0KPiBkZXRhaWwgaW4gdGhlIHRl
eHQuIA0KPiANCj4gPj4gW3l1Y2hpXSBUaGUgbG9nZ2luZyBvZiBhIHN3aXRjaCBjYW4gYmUgZG9u
ZSBieSBpdHMgYXNzb2NpYXRlZCANCj4gPj4gY29udHJvbGxlci4gVGhlIGNvbnRyb2xsZXIgaXMg
cmVzcG9uc2libGUgZm9yIA0KPiA+PiBtYWludGFpbmluZyBhbGwgc3RhdGVzIHRoYXQgaXMgcmVs
YXRlZCB0byB0aGUgc3dpdGNoLCBzdWNoIGFzIE5BVDQ0IA0KPiA+PiBzdGF0ZSBhbmQgZmxvdyB0
YWJsZSAoaWYgbmVlZGVkKS4gDQo+ID4NCj4gPltXZWldSWYgc28sIGRvZXMgYSBzd2l0Y2ggbmVl
ZCB0byBzZW5kIGl0cyBOQVQ0NCBzZXNzaW9ucyhvciBmbG93IA0KdGFibGVzKSANCj4gPnRvDQo+
ID50aGUgY29udHJvbGxlcj8gDQo+ID4NCj4gDQo+IFt5dWNoaV0gTkFUNDQgcHJvY2VzcyBjYW4g
YmUgaW50ZXJwcmV0ZWQgaW50byBhY3Rpb25zIGFuZCByZWNvcmRlZCANCj4gaW4gdGhlIGZsb3cg
dGFibGUuIEhlbmNlIA0KPiBJIHRoaW5rIHN3aXRjaCBkb2VzIG5vdCBoYXZlIHRvIG1haW50YWlu
IE5BVDQ0IHNlc3Npb24gc3RhdGUgKGlmIA0KPiB0aGlzIGlzIHdoYXQgeW91IG1lYW4pLiANCg0K
W1dlaV0gR290IGl0LiBUaGlzIGludGVycHJldGluZyBpcyB3aGF0IGNvbnRyb2xsZXJzIG5lZWQg
dG8gZG8uIFRvDQphdm9pZCBjb25mdXNpb24sIEkgcHJvcG9zZSB0aGlzIHByb2Nlc3MgYW5kIHRo
ZSByZWxhdGlvbnNoaXAgb2YgDQpzdGF0dXMoc2Vzc2lvbikgJiAiZmxvdyB0YWJsZSIgbmVlZCBm
dXJ0aGVyIGV4cGxhbmF0aW9uIGluIHRoaXMgZHJhZnQsIA0KaWYgbmVlZGVkLiANCg0KDQo+IA0K
PiBPbiB0aGUgb3RoZXIgaGFuZCwgY29udHJvbGxlciBjYW4gZXN0YWJsaXNoIHJlbGF0ZWQgc3Rh
dGVzIGFjY29yZGluZw0KPiB0byB0aGUgaW5pdGFsIHBhY2tldCBvZiBlYWNoIGZsb3csIA0KPiB3
aGljaCBpcyB3aGF0IHN3aXRjaCBuZWVkcyB0byBzZW5kIHRvIGNvbnRyb2xsZXIuIElmIGNvbnRy
b2xsZXIgDQo+IG5lZWRzIHRoZSBpbmZvcm1hdGlvbiBvZiB0aGUgZmxvdyB0YWJsZSANCj4gbWFp
bnRhaW5lZCBieSBzd2l0Y2gsIGl0IGNhbiBhc2sgc3dpdGNoIHRvIHNlbmQgdGhhdC4gSGVuY2Ug
c3dpdGNoIA0KPiBpcyBub3QgcmVxdWlyZWQgdG8gc2VuZCBpdHMgZmxvdyB0YWJsZSANCj4gdG8g
Y29udHJvbGxlciBieSBkZWZhdWx0LiANCg0K
--=_alternative 003313D848257C83_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkhpIFl1Y2h1aaOsPC9mb250Pg0K
PGJyPg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj4mbmJzcDsgUExTIHNlZSBp
bmxpbmUuPC9mb250Pg0KPGJyPg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj5U
aGFua3OjrDwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+V2VpPC9m
b250Pg0KPGJyPg0KPGJyPjx0dD48Zm9udCBzaXplPTI+JnF1b3Q7WXVjaGkgQ2hlbiZxdW90OyAm
bHQ7Y2hlbnljbXhAZ21haWwuY29tJmd0Ow0KJm5ic3A7MjAxNC0wMi0xOCAxNjo0NjozNzo8YnI+
DQo8YnI+DQomZ3Q7IEhpIFdlaSw8YnI+DQomZ3Q7IDxicj4NCiZndDsgUGxlYXNlIHNlZSBpbmxp
bmUuPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IEJlc3QgcmVnYXJkcyE8YnI+DQomZ3Q7IC0tLS0tLS0t
LS0tLS0tPGJyPg0KJmd0OyBZdWNoaSBDaGVuPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IE9uIDIwMTQt
MDItMTgsIDE1OjE1LCAmcXVvdDttZW5nLndlaTImcXVvdDsgJmx0O21lbmcud2VpMkB6dGUuY29t
LmNuJmd0Ow0Kd3JvdGU6PGJyPg0KJmd0OyAmZ3Q7W1dlaV0gSSBhZ3JlZS4gQ29uZ2VzdGlvbiBt
aWdodCBoYXJkbHkgb2NjdXIgaW4gbm9ybWFsIG5ldHdvcmsNCnRyYWZmaWMuPGJyPg0KJmd0OyAm
Z3Q7QW55d2F5LCB0aGUgcmF0ZSBvZiAmbmJzcDtjcmVhdGluZyBuZXcgc2Vzc2lvbnMgaXMgYSBr
ZXkgcGVyZm9ybWFuY2UNCmluZGV4ZXMgb2Y8YnI+DQomZ3Q7ICZndDtwZXIgYXBwYXJhdHVzIHVu
ZGVyIHRyYWRpdGlvbmFsIHJvdXRpbmcgc2NlbmFyaW8uIDxicj4NCiZndDsgJmd0OyAmbmJzcDtN
eSBwcm9wb3NhbCBpcyB0aGF0IHdlIHNob3VsZCBjb25zaWRlciBob3cgdG8gbWFpbnRhaW4NCmV4
aXN0aW5nIDxicj4NCiZndDsgJmd0O3BlcmZvcm1hbmNlPGJyPg0KJmd0OyAmZ3Q7cGVyIGFwcGFy
YXR1cyAoc3dpdGNoL3JvdXRlcikgd2hpbGUgZmluZGluZyBhIHdheSB0byB1bmlmeSBJUHY2DQp0
cmFuc2l0aW9uIDxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsgJmd0O3RlY2hub2xvZ2llcy48YnI+
DQomZ3Q7ICZndDsgJm5ic3A7aS5lLiByZWFzb25hYmxlIG51bWJlciBvZiBjb250cm9sbGVycyBp
biBuZXR3b3JrLi4uPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IFt5dWNoaV0gWWVzLCB0aGFua3MgZm9y
IHlvdXIgc3VnZ2VzdGlvbi4gVGhlIHNjZW5hcmlvIG9mIHVzaW5nIDxicj4NCiZndDsgc2V2ZXJh
bCBjb250cm9sbGVyPGJyPg0KJmd0OyBpcyBtZW50aW9uZWQgKGUuZy4sICZxdW90O0NvbnRyb2xs
ZXIgY2FuIGJlIGEgc2luZ2xlIGRldmljZSBvciBhIGNsdXN0ZXINCjxicj4NCiZndDsgb2YgZGV2
aWNlcyZxdW90OyBpbiA8YnI+DQomZ3Q7IEJ1bGxldCAzIG9mIFRlcm1pbm9sb2d5IFNlY3Rpb24p
LiBJIHRoaW5rIHRoaXMgc2NlbmFyaW8gY2FuIGJlIDxicj4NCiZndDsgZGlzY3Vzc2VkIGluIG1v
cmUgPGJyPg0KJmd0OyBkZXRhaWwgaW4gdGhlIHRleHQuIDxicj4NCiZndDsgPGJyPg0KJmd0OyAm
Z3Q7Jmd0OyBbeXVjaGldIFRoZSBsb2dnaW5nIG9mIGEgc3dpdGNoIGNhbiBiZSBkb25lIGJ5IGl0
cyBhc3NvY2lhdGVkDQo8YnI+DQomZ3Q7ICZndDsmZ3Q7IGNvbnRyb2xsZXIuIFRoZSBjb250cm9s
bGVyIGlzIHJlc3BvbnNpYmxlIGZvciA8YnI+DQomZ3Q7ICZndDsmZ3Q7IG1haW50YWluaW5nIGFs
bCBzdGF0ZXMgdGhhdCBpcyByZWxhdGVkIHRvIHRoZSBzd2l0Y2gsIHN1Y2gNCmFzIE5BVDQ0IDxi
cj4NCiZndDsgJmd0OyZndDsgc3RhdGUgYW5kIGZsb3cgdGFibGUgKGlmIG5lZWRlZCkuIDxicj4N
CiZndDsgJmd0Ozxicj4NCiZndDsgJmd0O1tXZWldSWYgc28sIGRvZXMgYSBzd2l0Y2ggbmVlZCB0
byBzZW5kIGl0cyBOQVQ0NCBzZXNzaW9ucyhvciBmbG93DQp0YWJsZXMpIDxicj4NCiZndDsgJmd0
O3RvPGJyPg0KJmd0OyAmZ3Q7dGhlIGNvbnRyb2xsZXI/IDxicj4NCiZndDsgJmd0Ozxicj4NCiZn
dDsgPGJyPg0KJmd0OyBbeXVjaGldIE5BVDQ0IHByb2Nlc3MgY2FuIGJlIGludGVycHJldGVkIGlu
dG8gYWN0aW9ucyBhbmQgcmVjb3JkZWQNCjxicj4NCiZndDsgaW4gdGhlIGZsb3cgdGFibGUuIEhl
bmNlIDxicj4NCiZndDsgSSB0aGluayBzd2l0Y2ggZG9lcyBub3QgaGF2ZSB0byBtYWludGFpbiBO
QVQ0NCBzZXNzaW9uIHN0YXRlIChpZiA8YnI+DQomZ3Q7IHRoaXMgaXMgd2hhdCB5b3UgbWVhbiku
IDwvZm9udD48L3R0Pg0KPGJyPg0KPGJyPjx0dD48Zm9udCBzaXplPTI+W1dlaV0gR290IGl0LiBU
aGlzIGludGVycHJldGluZyBpcyB3aGF0IGNvbnRyb2xsZXJzDQpuZWVkIHRvIGRvLiBUbzwvZm9u
dD48L3R0Pg0KPGJyPjx0dD48Zm9udCBzaXplPTI+YXZvaWQgY29uZnVzaW9uLCBJIHByb3Bvc2Ug
dGhpcyBwcm9jZXNzIGFuZCB0aGUgcmVsYXRpb25zaGlwDQpvZiA8L2ZvbnQ+PC90dD4NCjxicj48
dHQ+PGZvbnQgc2l6ZT0yPnN0YXR1cyhzZXNzaW9uKSAmYW1wOyAmcXVvdDtmbG93IHRhYmxlJnF1
b3Q7IG5lZWQNCmZ1cnRoZXIgZXhwbGFuYXRpb24gaW4gdGhpcyBkcmFmdCwgPC9mb250PjwvdHQ+
DQo8YnI+PHR0Pjxmb250IHNpemU9Mj5pZiBuZWVkZWQuIDwvZm9udD48L3R0Pg0KPGJyPg0KPGJy
Pjx0dD48Zm9udCBzaXplPTI+PGJyPg0KJmd0OyA8YnI+DQomZ3Q7IE9uIHRoZSBvdGhlciBoYW5k
LCBjb250cm9sbGVyIGNhbiBlc3RhYmxpc2ggcmVsYXRlZCBzdGF0ZXMgYWNjb3JkaW5nPGJyPg0K
Jmd0OyB0byB0aGUgaW5pdGFsIHBhY2tldCBvZiBlYWNoIGZsb3csIDxicj4NCiZndDsgd2hpY2gg
aXMgd2hhdCBzd2l0Y2ggbmVlZHMgdG8gc2VuZCB0byBjb250cm9sbGVyLiBJZiBjb250cm9sbGVy
IDxicj4NCiZndDsgbmVlZHMgdGhlIGluZm9ybWF0aW9uIG9mIHRoZSBmbG93IHRhYmxlIDxicj4N
CiZndDsgbWFpbnRhaW5lZCBieSBzd2l0Y2gsIGl0IGNhbiBhc2sgc3dpdGNoIHRvIHNlbmQgdGhh
dC4gSGVuY2Ugc3dpdGNoDQo8YnI+DQomZ3Q7IGlzIG5vdCByZXF1aXJlZCB0byBzZW5kIGl0cyBm
bG93IHRhYmxlIDxicj4NCiZndDsgdG8gY29udHJvbGxlciBieSBkZWZhdWx0LiA8YnI+DQo8L2Zv
bnQ+PC90dD4NCg==
--=_alternative 003313D848257C83_=--


From nobody Tue Feb 18 01:24:16 2014
Return-Path: <chenycmx@gmail.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 658741A060B for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 01:24:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dhaYH8fGJcQ7 for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 01:24:13 -0800 (PST)
Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id ED8811A0461 for <int-area@ietf.org>; Tue, 18 Feb 2014 01:24:11 -0800 (PST)
Received: by mail-pa0-f41.google.com with SMTP id fa1so16556204pad.28 for <int-area@ietf.org>; Tue, 18 Feb 2014 01:24:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=date:from:to:cc:reply-to:subject:references:mime-version:message-id :content-type:content-transfer-encoding; bh=hOL7JIulwIyY2CP1ZpKXnkDcCJ4Kwk7dLMxqhrn07ic=; b=wDPo4gDMYKzeZJ5yHN+/1exsRDKVpJ7Hp12dgx//NiJ7Ioau+5XVPTWCK7iwL62io1 nCipkffm2etSxYrbTRHY+goFlL9uEhdsmmduNLNSjNwNjOLytHMQgN8D3KIulJJEVj+e QcVROdin6LSC6YMscj4PUQ2lviY0vrDhq8ztlR1ko8ucF4+XJyavruIRE0T9ICwQuyUq bVL8ASBqy+sbilmFAhNMQXYlpdxUmRrWvI8rQlgYE8bvQOLwBr77AnnVX4jco9/Lrj/u wyNvKirBZlY4R71TIn4z0flbSErSYrrOrWcRv1mbnRxfIxK+6SPyh1Vgnafbm7PX+i4j vJUw==
X-Received: by 10.66.129.133 with SMTP id nw5mr31585603pab.98.1392715449188; Tue, 18 Feb 2014 01:24:09 -0800 (PST)
Received: from netlab-PC ([166.111.68.231]) by mx.google.com with ESMTPSA id ns7sm53823980pbc.32.2014.02.18.01.24.03 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 18 Feb 2014 01:24:07 -0800 (PST)
Date: Tue, 18 Feb 2014 17:24:05 +0800
From: "Yuchi Chen" <chenycmx@gmail.com>
To: meng.wei2 <meng.wei2@zte.com.cn>
References: <OFA466A5D8.34EB23FF-ON48257C83.00318B8B-48257C83.003313DB@zte.com.cn>
X-Priority: 3
X-GUID: 6731160B-0544-46F4-9632-E6FEF33C711F
X-Has-Attach: no
X-Mailer: Foxmail 7.0.1.92[cn]
Mime-Version: 1.0
Message-ID: <2014021817240047124385@gmail.com>
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/IarReBiYxs_lqfIRQdlVRu3HJG8
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] [intarea]Comments on draft-cui-intarea-unified-v6-framework-00
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: chenycmx <chenycmx@gmail.com>
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2014 09:24:14 -0000

SGkgV2VpLA0KDQpPbiAyMDE0LTAyLTE4LCAxNzoxNSwgIm1lbmcud2VpMiIgPG1lbmcud2VpMkB6
dGUuY29tLmNuPiB3cm90ZToNCj5bV2VpXSBHb3QgaXQuIFRoaXMgaW50ZXJwcmV0aW5nIGlzIHdo
YXQgY29udHJvbGxlcnMgbmVlZCB0byBkby4gVG8NCj5hdm9pZCBjb25mdXNpb24sIEkgcHJvcG9z
ZSB0aGlzIHByb2Nlc3MgYW5kIHRoZSByZWxhdGlvbnNoaXAgb2YgDQo+c3RhdHVzKHNlc3Npb24p
ICYgImZsb3cgdGFibGUiIG5lZWQgZnVydGhlciBleHBsYW5hdGlvbiBpbiB0aGlzIGRyYWZ0LCAN
Cj5pZiBuZWVkZWQuDQoNClN1cmUsIHdlJ2xsIGNsYXJpZnkgdGhpcyBhcyB3ZWxsIGFzIG90aGVy
IHBvaW50cyB5b3Ugc3VnZ2VzdGVkIGluIHRoZSB0ZXh0LiBUaGFua3MgZm9yIHRoZSBjb21tZW50
cyENCg0KQmVzdCByZWdhcmRzIQ0KLS0tLS0tLS0tLS0tLS0NCll1Y2hpIENoZW4=


From nobody Tue Feb 18 08:48:00 2014
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40D9F1A04CB for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 08:47:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7_3xo3FguO0S for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 08:47:56 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 0C6311A0256 for <int-area@ietf.org>; Tue, 18 Feb 2014 08:47:56 -0800 (PST)
Received: from [192.168.1.91] (pool-71-105-87-112.lsanca.dsl-w.verizon.net [71.105.87.112]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id s1IGlD7b017089 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 18 Feb 2014 08:47:17 -0800 (PST)
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Content-Type: text/plain; charset=us-ascii
From: Joe Touch <touch@isi.edu>
In-Reply-To: <2134F8430051B64F815C691A62D983181D205B@XCH-BLV-504.nw.nos.boeing.com>
Date: Tue, 18 Feb 2014 08:47:12 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <F3D91914-1A80-4CEC-96B9-99CF2BF0F64B@isi.edu>
References: <68a71d0317c546689875cfb7a1a67f9b@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983181D205B@XCH-BLV-504.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.1827)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/Enz1FD7eHnbcb_uhIIVT6IS0Mfw
Cc: Ronald Bonica <rbonica@juniper.net>, "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2014 16:47:58 -0000

Hi, Fred,

On Feb 17, 2014, at 10:51 AM, Templin, Fred L =
<Fred.L.Templin@boeing.com> wrote:

> Hi Ron,
>=20
> The document needs to talk about packet sizes for IP payload packets.

Yes, and I'm hoping we can add additional detail.

Here's my view:

-- path MTU is based on the min of the largest packet each link in the =
path can support

-- links often transit packets larger than their native size, e.g., =
ATM's MTU is 9K, not 48 bytes

-- links do have a native transit size, though

So there ought to be two very different concepts

- MTU (maximum)

- PTU (preferred)

IMO, much of the confusion about how MTUs are handled by tunnels is =
based on confusing MTU to mean PTU.

I.e.,

	- a tunnel has a PTU based on avoiding ingress fragmentation
	and egress reassemly

	- a tunnel as a MTU, which is the MTU of the path of the tunnel
	minus the headers it adds at the ingress

> For IP payload packets no larger than MINMTU bytes, the GRE tunnel
> MUST accommodate the packet even if a small amount of fragmentation
> is necessary. (Here, the mandatory MINMTU for IPv6 is 1280 and the
> recommended MINMTU for IPv4 is also 1280.)

This artificially limits tunnel MTU based on trying to support a =
perceived PTU, but doesn't match PTU.

> Beyond MINMTU, there needs to be a balance between avoiding path
> MTU related black holes for the source and avoiding excessive
> fragmentation at the GRE tunnel egress.

If we really want to accomplish that, we need to flesh out the =
difference between MTU and PTU and teach our apps to focus on PTU, ala a =
new PLPTUD (vs. current PLMTUD).

I don't think we should be guessing this at the time we specify the =
tunnel, because the approach varies based on what's transited (real IP =
packets or some other sort of encapsulation, e.g., IPsec in UDP).


> This balance is situation
> dependent. For example, if the GRE tunnel ingress is located close
> to the source, it should be reasonable to expect that the source
> would be able to receive any ICMP PTB messages sent by the ingress.

Tunnels transit packets; they're not connected to sources or =
destinations. So are you proposing that a tunnel should now try to =
discover the length of the path in each direction and handle different =
addresses differently? IMO, that's worse than reassembly.

> Or, if the GRE tunnel egress is located close to the destination,
> it should be reasonable to expect that the egress can perform a
> small amount of reassembly.

Same problem, and worse- do you expect vendors to sell different tunnel =
engines based on intended traffic patterns?

----

In conclusion, I would urge this document to focus on MTU as the goal, =
at which point the only packets that ought to be dropped at the ingress =
ought to be those that cannot be encapsulated with another IPv4 header, =
i.e., that exceed the *MAXIMUM* payload size.

If we want to tune for preferred path size, we need to extend PLMTUD for =
that purpose.

Joe=


From nobody Tue Feb 18 09:27:28 2014
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC0691A020A for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 09:27:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.749
X-Spam-Level: 
X-Spam-Status: No, score=-4.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8aBWi6uyTVzK for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 09:27:17 -0800 (PST)
Received: from stl-mbsout-01.boeing.com (stl-mbsout-01.boeing.com [130.76.96.169]) by ietfa.amsl.com (Postfix) with ESMTP id 8DF1F1A06AE for <int-area@ietf.org>; Tue, 18 Feb 2014 09:27:12 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id s1IHR9V8027083; Tue, 18 Feb 2014 11:27:09 -0600
Received: from XCH-PHX-413.sw.nos.boeing.com (xch-phx-413.sw.nos.boeing.com [10.57.37.45]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id s1IHR64m027022 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Tue, 18 Feb 2014 11:27:07 -0600
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.102]) by XCH-PHX-413.sw.nos.boeing.com ([169.254.13.170]) with mapi id 14.03.0174.001;  Tue, 18 Feb 2014 09:27:06 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Joe Touch <touch@isi.edu>
Thread-Topic: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
Thread-Index: AQHPLMkvZ6PoNhiMLkS+vK8jjU2/Npq7PI9Q
Date: Tue, 18 Feb 2014 17:27:05 +0000
Message-ID: <2134F8430051B64F815C691A62D983181D35E5@XCH-BLV-504.nw.nos.boeing.com>
References: <68a71d0317c546689875cfb7a1a67f9b@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983181D205B@XCH-BLV-504.nw.nos.boeing.com> <F3D91914-1A80-4CEC-96B9-99CF2BF0F64B@isi.edu>
In-Reply-To: <F3D91914-1A80-4CEC-96B9-99CF2BF0F64B@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/I3vJUH5yf4hjwH-toKLOuTVQVT8
Cc: Ronald Bonica <rbonica@juniper.net>, "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2014 17:27:21 -0000

Hi Joe,

You seem to be talking past me - maybe it was because I wrote too much.
The fragmentation story for tunnels is very simple as follows:

1) IPv6 has a minimum MTU of 1280 bytes. So, packets that are no larger
   than this size MUST be accommodated even if a small amount of
   fragmentation is necessary. IPv4 has a much smaller minMTU, but
   IMHO tunnels SHOULD behave as if the IPv4 minMTU is also 1280.

2) Packets larger than 1500 bytes (with the exception of IPv4 packets
   with DF=3D0) should be allowed to sink or swim on their own. Tunnels
   therefore MUST NOT use fragmentation for packets larger than 1500.

3) Packets larger than 1280 but no larger than 1500 are in a "gray area"
   where the way the tunnel accommodates them depends on the specific
   tunnel orientation. In some cases the tunnel should send as a whole
   packet. In others, it should drop and send a PTB. In still others,
   it should fragment. The cases are easy to articulate.

That is really all there is to it. What is important to realize is
that case 3) needs to be architected according to the specific tunnel
orientation - there is no generic one-size-fits-all rule that can be
applied to all tunnels in all orientations.

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


> -----Original Message-----
> From: Joe Touch [mailto:touch@isi.edu]
> Sent: Tuesday, February 18, 2014 8:47 AM
> To: Templin, Fred L
> Cc: Ronald Bonica; int-area@ietf.org
> Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-int=
area-gre-mtu-04.txt
>=20
> Hi, Fred,
>=20
> On Feb 17, 2014, at 10:51 AM, Templin, Fred L <Fred.L.Templin@boeing.com>=
 wrote:
>=20
> > Hi Ron,
> >
> > The document needs to talk about packet sizes for IP payload packets.
>=20
> Yes, and I'm hoping we can add additional detail.
>=20
> Here's my view:
>=20
> -- path MTU is based on the min of the largest packet each link in the pa=
th can support
>=20
> -- links often transit packets larger than their native size, e.g., ATM's=
 MTU is 9K, not 48 bytes
>=20
> -- links do have a native transit size, though
>=20
> So there ought to be two very different concepts
>=20
> - MTU (maximum)
>=20
> - PTU (preferred)
>=20
> IMO, much of the confusion about how MTUs are handled by tunnels is based=
 on confusing MTU to mean
> PTU.
>=20
> I.e.,
>=20
> 	- a tunnel has a PTU based on avoiding ingress fragmentation
> 	and egress reassemly
>=20
> 	- a tunnel as a MTU, which is the MTU of the path of the tunnel
> 	minus the headers it adds at the ingress
>=20
> > For IP payload packets no larger than MINMTU bytes, the GRE tunnel
> > MUST accommodate the packet even if a small amount of fragmentation
> > is necessary. (Here, the mandatory MINMTU for IPv6 is 1280 and the
> > recommended MINMTU for IPv4 is also 1280.)
>=20
> This artificially limits tunnel MTU based on trying to support a perceive=
d PTU, but doesn't match PTU.
>=20
> > Beyond MINMTU, there needs to be a balance between avoiding path
> > MTU related black holes for the source and avoiding excessive
> > fragmentation at the GRE tunnel egress.
>=20
> If we really want to accomplish that, we need to flesh out the difference=
 between MTU and PTU and
> teach our apps to focus on PTU, ala a new PLPTUD (vs. current PLMTUD).
>=20
> I don't think we should be guessing this at the time we specify the tunne=
l, because the approach
> varies based on what's transited (real IP packets or some other sort of e=
ncapsulation, e.g., IPsec in
> UDP).
>=20
>=20
> > This balance is situation
> > dependent. For example, if the GRE tunnel ingress is located close
> > to the source, it should be reasonable to expect that the source
> > would be able to receive any ICMP PTB messages sent by the ingress.
>=20
> Tunnels transit packets; they're not connected to sources or destinations=
. So are you proposing that a
> tunnel should now try to discover the length of the path in each directio=
n and handle different
> addresses differently? IMO, that's worse than reassembly.
>=20
> > Or, if the GRE tunnel egress is located close to the destination,
> > it should be reasonable to expect that the egress can perform a
> > small amount of reassembly.
>=20
> Same problem, and worse- do you expect vendors to sell different tunnel e=
ngines based on intended
> traffic patterns?
>=20
> ----
>=20
> In conclusion, I would urge this document to focus on MTU as the goal, at=
 which point the only packets
> that ought to be dropped at the ingress ought to be those that cannot be =
encapsulated with another
> IPv4 header, i.e., that exceed the *MAXIMUM* payload size.
>=20
> If we want to tune for preferred path size, we need to extend PLMTUD for =
that purpose.
>=20
> Joe


From nobody Tue Feb 18 10:09:09 2014
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D313E1A06CB for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 10:09:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pXbql4auLQjS for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 10:09:03 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id C92141A06EE for <int-area@ietf.org>; Tue, 18 Feb 2014 10:09:03 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id s1II8gAb015173 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 18 Feb 2014 10:08:44 -0800 (PST)
Message-ID: <5303A1AD.9070904@isi.edu>
Date: Tue, 18 Feb 2014 10:08:45 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
References: <68a71d0317c546689875cfb7a1a67f9b@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983181D205B@XCH-BLV-504.nw.nos.boeing.com> <F3D91914-1A80-4CEC-96B9-99CF2BF0F64B@isi.edu> <2134F8430051B64F815C691A62D983181D35E5@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D983181D35E5@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/52eEqCRMh6g7q7lfq-Xgjyx_vx0
Cc: Ronald Bonica <rbonica@juniper.net>, "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2014 18:09:06 -0000

On 2/18/2014 9:27 AM, Templin, Fred L wrote:
> Hi Joe,
>
> You seem to be talking past me - maybe it was because I wrote too much.
> The fragmentation story for tunnels is very simple as follows:

Yes, IMO they are, and here's mine:

	- if a tunnel CAN transit a packet, it MUST try

		i.e., the MTU of a tunnel that uses IPv6 encapsulation
		is 65535 - encapsulation headers

	- if a tunnel CANNOT transit a packet, it rejects it

		i.e., anything larger than "65535 - encap headers"

Everything else mistakes MSS (maximum) for PSS (preferred). Preferred is 
the min of the MSS's. An IPv6 tunnel limits MSS only insofar as packets 
larger than 65535-headers cannot traverse it.

So...

> 1) IPv6 has a minimum MTU of 1280 bytes. So, packets that are no larger
>     than this size MUST be accommodated even if a small amount of
>     fragmentation is necessary. IPv4 has a much smaller minMTU, but
>     IMHO tunnels SHOULD behave as if the IPv4 minMTU is also 1280.

An IPv6 tunnel is a link to the IPv6 protocol. IPv6 requires that the 
smallest MTU of all links must be no less than 1280. So agreed.

> 2) Packets larger than 1500 bytes (with the exception of IPv4 packets
>     with DF=0) should be allowed to sink or swim on their own. Tunnels
>     therefore MUST NOT use fragmentation for packets larger than 1500.

Completely disagree. The max size of the payload of GRE in IPv6 is much 
larger than 1500.

You're trying to do something at the tunnel layer that the path is 
supposed to be in control of.

> 3) Packets larger than 1280 but no larger than 1500 are in a "gray area"
>     where the way the tunnel accommodates them depends on the specific
>     tunnel orientation. In some cases the tunnel should send as a whole
>     packet. In others, it should drop and send a PTB. In still others,
>     it should fragment. The cases are easy to articulate.

There is no grey area. Until the max payload of an IPv6 packet is 
decreased, there's simply no justification to do other than the above.

> That is really all there is to it. What is important to realize is
> that case 3) needs to be architected according to the specific tunnel
> orientation - there is no generic one-size-fits-all rule that can be
> applied to all tunnels in all orientations.

First, if rules depend on orientations, then there would be no rule for 
tunnels at all. You cannot specify the requirements of a tunnel if it 
depends on network placement - that rule does not exist for any other 
Internet component (excepting only endpoint vs. network, but that's 
function, not just placement).

Second, there is a rule. See above.

Joe


>
> Thanks - Fred
> fred.l.templin@boeing.com
>
>
>> -----Original Message-----
>> From: Joe Touch [mailto:touch@isi.edu]
>> Sent: Tuesday, February 18, 2014 8:47 AM
>> To: Templin, Fred L
>> Cc: Ronald Bonica; int-area@ietf.org
>> Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
>>
>> Hi, Fred,
>>
>> On Feb 17, 2014, at 10:51 AM, Templin, Fred L <Fred.L.Templin@boeing.com> wrote:
>>
>>> Hi Ron,
>>>
>>> The document needs to talk about packet sizes for IP payload packets.
>>
>> Yes, and I'm hoping we can add additional detail.
>>
>> Here's my view:
>>
>> -- path MTU is based on the min of the largest packet each link in the path can support
>>
>> -- links often transit packets larger than their native size, e.g., ATM's MTU is 9K, not 48 bytes
>>
>> -- links do have a native transit size, though
>>
>> So there ought to be two very different concepts
>>
>> - MTU (maximum)
>>
>> - PTU (preferred)
>>
>> IMO, much of the confusion about how MTUs are handled by tunnels is based on confusing MTU to mean
>> PTU.
>>
>> I.e.,
>>
>> 	- a tunnel has a PTU based on avoiding ingress fragmentation
>> 	and egress reassemly
>>
>> 	- a tunnel as a MTU, which is the MTU of the path of the tunnel
>> 	minus the headers it adds at the ingress
>>
>>> For IP payload packets no larger than MINMTU bytes, the GRE tunnel
>>> MUST accommodate the packet even if a small amount of fragmentation
>>> is necessary. (Here, the mandatory MINMTU for IPv6 is 1280 and the
>>> recommended MINMTU for IPv4 is also 1280.)
>>
>> This artificially limits tunnel MTU based on trying to support a perceived PTU, but doesn't match PTU.
>>
>>> Beyond MINMTU, there needs to be a balance between avoiding path
>>> MTU related black holes for the source and avoiding excessive
>>> fragmentation at the GRE tunnel egress.
>>
>> If we really want to accomplish that, we need to flesh out the difference between MTU and PTU and
>> teach our apps to focus on PTU, ala a new PLPTUD (vs. current PLMTUD).
>>
>> I don't think we should be guessing this at the time we specify the tunnel, because the approach
>> varies based on what's transited (real IP packets or some other sort of encapsulation, e.g., IPsec in
>> UDP).
>>
>>
>>> This balance is situation
>>> dependent. For example, if the GRE tunnel ingress is located close
>>> to the source, it should be reasonable to expect that the source
>>> would be able to receive any ICMP PTB messages sent by the ingress.
>>
>> Tunnels transit packets; they're not connected to sources or destinations. So are you proposing that a
>> tunnel should now try to discover the length of the path in each direction and handle different
>> addresses differently? IMO, that's worse than reassembly.
>>
>>> Or, if the GRE tunnel egress is located close to the destination,
>>> it should be reasonable to expect that the egress can perform a
>>> small amount of reassembly.
>>
>> Same problem, and worse- do you expect vendors to sell different tunnel engines based on intended
>> traffic patterns?
>>
>> ----
>>
>> In conclusion, I would urge this document to focus on MTU as the goal, at which point the only packets
>> that ought to be dropped at the ingress ought to be those that cannot be encapsulated with another
>> IPv4 header, i.e., that exceed the *MAXIMUM* payload size.
>>
>> If we want to tune for preferred path size, we need to extend PLMTUD for that purpose.
>>
>> Joe


From nobody Tue Feb 18 10:22:47 2014
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80F4E1A020C for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 10:22:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.749
X-Spam-Level: 
X-Spam-Status: No, score=-4.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nug4KYo_TzRK for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 10:22:41 -0800 (PST)
Received: from blv-mbsout-02.boeing.com (blv-mbsout-02.boeing.com [130.76.32.232]) by ietfa.amsl.com (Postfix) with ESMTP id ECC7D1A0250 for <int-area@ietf.org>; Tue, 18 Feb 2014 10:22:40 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id s1IIMbtv009228; Tue, 18 Feb 2014 10:22:38 -0800
Received: from XCH-PHX-209.sw.nos.boeing.com (xch-phx-209.sw.nos.boeing.com [130.247.25.29]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id s1IIMWKE009117 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Tue, 18 Feb 2014 10:22:32 -0800
Received: from XCH-BLV-206.nw.nos.boeing.com (10.57.37.16) by XCH-PHX-209.sw.nos.boeing.com (130.247.25.29) with Microsoft SMTP Server (TLS) id 14.3.174.1; Tue, 18 Feb 2014 10:22:31 -0800
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.102]) by XCH-BLV-206.nw.nos.boeing.com ([169.254.6.224]) with mapi id 14.03.0174.001; Tue, 18 Feb 2014 10:22:31 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Joe Touch <touch@isi.edu>
Thread-Topic: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
Thread-Index: AQHPLNR2Z6PoNhiMLkS+vK8jjU2/Npq7UHgQ
Date: Tue, 18 Feb 2014 18:22:30 +0000
Message-ID: <2134F8430051B64F815C691A62D983181D37B6@XCH-BLV-504.nw.nos.boeing.com>
References: <68a71d0317c546689875cfb7a1a67f9b@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983181D205B@XCH-BLV-504.nw.nos.boeing.com> <F3D91914-1A80-4CEC-96B9-99CF2BF0F64B@isi.edu> <2134F8430051B64F815C691A62D983181D35E5@XCH-BLV-504.nw.nos.boeing.com> <5303A1AD.9070904@isi.edu>
In-Reply-To: <5303A1AD.9070904@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/-BLqjCZ0BgkXzrtxC6GNq9cpDN8
Cc: Ronald Bonica <rbonica@juniper.net>, "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2014 18:22:45 -0000

Hi Joe,

I can see that I am going to have to write a draft on generic tunnel
fragmentation. It will be based on my e-mail from two messages ago.
I have already written drafts on 6rd tunnel fragmentation and AERO
tunnel fragmentation, and they are already consistent with the to-
be-written draft on generic tunnel fragmentation. Your draft on GRE
fragmentation can then also cite the generic tunnel fragmentation doc.

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

> -----Original Message-----
> From: Joe Touch [mailto:touch@isi.edu]
> Sent: Tuesday, February 18, 2014 10:09 AM
> To: Templin, Fred L
> Cc: Ronald Bonica; int-area@ietf.org
> Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-int=
area-gre-mtu-04.txt
>=20
>=20
>=20
> On 2/18/2014 9:27 AM, Templin, Fred L wrote:
> > Hi Joe,
> >
> > You seem to be talking past me - maybe it was because I wrote too much.
> > The fragmentation story for tunnels is very simple as follows:
>=20
> Yes, IMO they are, and here's mine:
>=20
> 	- if a tunnel CAN transit a packet, it MUST try
>=20
> 		i.e., the MTU of a tunnel that uses IPv6 encapsulation
> 		is 65535 - encapsulation headers
>=20
> 	- if a tunnel CANNOT transit a packet, it rejects it
>=20
> 		i.e., anything larger than "65535 - encap headers"
>=20
> Everything else mistakes MSS (maximum) for PSS (preferred). Preferred is
> the min of the MSS's. An IPv6 tunnel limits MSS only insofar as packets
> larger than 65535-headers cannot traverse it.
>=20
> So...
>=20
> > 1) IPv6 has a minimum MTU of 1280 bytes. So, packets that are no larger
> >     than this size MUST be accommodated even if a small amount of
> >     fragmentation is necessary. IPv4 has a much smaller minMTU, but
> >     IMHO tunnels SHOULD behave as if the IPv4 minMTU is also 1280.
>=20
> An IPv6 tunnel is a link to the IPv6 protocol. IPv6 requires that the
> smallest MTU of all links must be no less than 1280. So agreed.
>=20
> > 2) Packets larger than 1500 bytes (with the exception of IPv4 packets
> >     with DF=3D0) should be allowed to sink or swim on their own. Tunnel=
s
> >     therefore MUST NOT use fragmentation for packets larger than 1500.
>=20
> Completely disagree. The max size of the payload of GRE in IPv6 is much
> larger than 1500.
>=20
> You're trying to do something at the tunnel layer that the path is
> supposed to be in control of.
>=20
> > 3) Packets larger than 1280 but no larger than 1500 are in a "gray area=
"
> >     where the way the tunnel accommodates them depends on the specific
> >     tunnel orientation. In some cases the tunnel should send as a whole
> >     packet. In others, it should drop and send a PTB. In still others,
> >     it should fragment. The cases are easy to articulate.
>=20
> There is no grey area. Until the max payload of an IPv6 packet is
> decreased, there's simply no justification to do other than the above.
>=20
> > That is really all there is to it. What is important to realize is
> > that case 3) needs to be architected according to the specific tunnel
> > orientation - there is no generic one-size-fits-all rule that can be
> > applied to all tunnels in all orientations.
>=20
> First, if rules depend on orientations, then there would be no rule for
> tunnels at all. You cannot specify the requirements of a tunnel if it
> depends on network placement - that rule does not exist for any other
> Internet component (excepting only endpoint vs. network, but that's
> function, not just placement).
>=20
> Second, there is a rule. See above.
>=20
> Joe
>=20
>=20
> >
> > Thanks - Fred
> > fred.l.templin@boeing.com
> >
> >
> >> -----Original Message-----
> >> From: Joe Touch [mailto:touch@isi.edu]
> >> Sent: Tuesday, February 18, 2014 8:47 AM
> >> To: Templin, Fred L
> >> Cc: Ronald Bonica; int-area@ietf.org
> >> Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-=
intarea-gre-mtu-04.txt
> >>
> >> Hi, Fred,
> >>
> >> On Feb 17, 2014, at 10:51 AM, Templin, Fred L <Fred.L.Templin@boeing.c=
om> wrote:
> >>
> >>> Hi Ron,
> >>>
> >>> The document needs to talk about packet sizes for IP payload packets.
> >>
> >> Yes, and I'm hoping we can add additional detail.
> >>
> >> Here's my view:
> >>
> >> -- path MTU is based on the min of the largest packet each link in the=
 path can support
> >>
> >> -- links often transit packets larger than their native size, e.g., AT=
M's MTU is 9K, not 48 bytes
> >>
> >> -- links do have a native transit size, though
> >>
> >> So there ought to be two very different concepts
> >>
> >> - MTU (maximum)
> >>
> >> - PTU (preferred)
> >>
> >> IMO, much of the confusion about how MTUs are handled by tunnels is ba=
sed on confusing MTU to mean
> >> PTU.
> >>
> >> I.e.,
> >>
> >> 	- a tunnel has a PTU based on avoiding ingress fragmentation
> >> 	and egress reassemly
> >>
> >> 	- a tunnel as a MTU, which is the MTU of the path of the tunnel
> >> 	minus the headers it adds at the ingress
> >>
> >>> For IP payload packets no larger than MINMTU bytes, the GRE tunnel
> >>> MUST accommodate the packet even if a small amount of fragmentation
> >>> is necessary. (Here, the mandatory MINMTU for IPv6 is 1280 and the
> >>> recommended MINMTU for IPv4 is also 1280.)
> >>
> >> This artificially limits tunnel MTU based on trying to support a perce=
ived PTU, but doesn't match
> PTU.
> >>
> >>> Beyond MINMTU, there needs to be a balance between avoiding path
> >>> MTU related black holes for the source and avoiding excessive
> >>> fragmentation at the GRE tunnel egress.
> >>
> >> If we really want to accomplish that, we need to flesh out the differe=
nce between MTU and PTU and
> >> teach our apps to focus on PTU, ala a new PLPTUD (vs. current PLMTUD).
> >>
> >> I don't think we should be guessing this at the time we specify the tu=
nnel, because the approach
> >> varies based on what's transited (real IP packets or some other sort o=
f encapsulation, e.g., IPsec
> in
> >> UDP).
> >>
> >>
> >>> This balance is situation
> >>> dependent. For example, if the GRE tunnel ingress is located close
> >>> to the source, it should be reasonable to expect that the source
> >>> would be able to receive any ICMP PTB messages sent by the ingress.
> >>
> >> Tunnels transit packets; they're not connected to sources or destinati=
ons. So are you proposing
> that a
> >> tunnel should now try to discover the length of the path in each direc=
tion and handle different
> >> addresses differently? IMO, that's worse than reassembly.
> >>
> >>> Or, if the GRE tunnel egress is located close to the destination,
> >>> it should be reasonable to expect that the egress can perform a
> >>> small amount of reassembly.
> >>
> >> Same problem, and worse- do you expect vendors to sell different tunne=
l engines based on intended
> >> traffic patterns?
> >>
> >> ----
> >>
> >> In conclusion, I would urge this document to focus on MTU as the goal,=
 at which point the only
> packets
> >> that ought to be dropped at the ingress ought to be those that cannot =
be encapsulated with another
> >> IPv4 header, i.e., that exceed the *MAXIMUM* payload size.
> >>
> >> If we want to tune for preferred path size, we need to extend PLMTUD f=
or that purpose.
> >>
> >> Joe


From nobody Tue Feb 18 10:28:47 2014
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B8A01A0408 for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 10:28:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yMJesrkZ-BHf for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 10:28:44 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 9B3F71A03ED for <int-area@ietf.org>; Tue, 18 Feb 2014 10:28:44 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id s1IISWuG022113 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 18 Feb 2014 10:28:32 -0800 (PST)
Message-ID: <5303A650.2050303@isi.edu>
Date: Tue, 18 Feb 2014 10:28:32 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
References: <68a71d0317c546689875cfb7a1a67f9b@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983181D205B@XCH-BLV-504.nw.nos.boeing.com> <F3D91914-1A80-4CEC-96B9-99CF2BF0F64B@isi.edu> <2134F8430051B64F815C691A62D983181D35E5@XCH-BLV-504.nw.nos.boeing.com> <5303A1AD.9070904@isi.edu> <2134F8430051B64F815C691A62D983181D37B6@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D983181D37B6@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/RZzRnY2wQx3kwPGssB8ukjQbpGg
Cc: Ronald Bonica <rbonica@juniper.net>, "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2014 18:28:47 -0000

On 2/18/2014 10:22 AM, Templin, Fred L wrote:
> Hi Joe,
>
> I can see that I am going to have to write a draft on generic tunnel
> fragmentation.

That's already a section in the tunnel draft that has been a WG doc:

http://tools.ietf.org/html/draft-ietf-intarea-tunnels-00#section-3.2

That doc has languished for lack of feedback, but IMO that's the place 
to put all one-stop information on tunnels that transit IP packets.

I do agree that the current GRE doc could be more clear on this issue, 
but I don't think a new, separate doc on this is needed.

Joe

> It will be based on my e-mail from two messages ago.
> I have already written drafts on 6rd tunnel fragmentation and AERO
> tunnel fragmentation, and they are already consistent with the to-
> be-written draft on generic tunnel fragmentation. Your draft on GRE
> fragmentation can then also cite the generic tunnel fragmentation doc.
>
> Thanks - Fred
> fred.l.templin@boeing.com
>
>> -----Original Message-----
>> From: Joe Touch [mailto:touch@isi.edu]
>> Sent: Tuesday, February 18, 2014 10:09 AM
>> To: Templin, Fred L
>> Cc: Ronald Bonica; int-area@ietf.org
>> Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
>>
>>
>>
>> On 2/18/2014 9:27 AM, Templin, Fred L wrote:
>>> Hi Joe,
>>>
>>> You seem to be talking past me - maybe it was because I wrote too much.
>>> The fragmentation story for tunnels is very simple as follows:
>>
>> Yes, IMO they are, and here's mine:
>>
>> 	- if a tunnel CAN transit a packet, it MUST try
>>
>> 		i.e., the MTU of a tunnel that uses IPv6 encapsulation
>> 		is 65535 - encapsulation headers
>>
>> 	- if a tunnel CANNOT transit a packet, it rejects it
>>
>> 		i.e., anything larger than "65535 - encap headers"
>>
>> Everything else mistakes MSS (maximum) for PSS (preferred). Preferred is
>> the min of the MSS's. An IPv6 tunnel limits MSS only insofar as packets
>> larger than 65535-headers cannot traverse it.
>>
>> So...
>>
>>> 1) IPv6 has a minimum MTU of 1280 bytes. So, packets that are no larger
>>>      than this size MUST be accommodated even if a small amount of
>>>      fragmentation is necessary. IPv4 has a much smaller minMTU, but
>>>      IMHO tunnels SHOULD behave as if the IPv4 minMTU is also 1280.
>>
>> An IPv6 tunnel is a link to the IPv6 protocol. IPv6 requires that the
>> smallest MTU of all links must be no less than 1280. So agreed.
>>
>>> 2) Packets larger than 1500 bytes (with the exception of IPv4 packets
>>>      with DF=0) should be allowed to sink or swim on their own. Tunnels
>>>      therefore MUST NOT use fragmentation for packets larger than 1500.
>>
>> Completely disagree. The max size of the payload of GRE in IPv6 is much
>> larger than 1500.
>>
>> You're trying to do something at the tunnel layer that the path is
>> supposed to be in control of.
>>
>>> 3) Packets larger than 1280 but no larger than 1500 are in a "gray area"
>>>      where the way the tunnel accommodates them depends on the specific
>>>      tunnel orientation. In some cases the tunnel should send as a whole
>>>      packet. In others, it should drop and send a PTB. In still others,
>>>      it should fragment. The cases are easy to articulate.
>>
>> There is no grey area. Until the max payload of an IPv6 packet is
>> decreased, there's simply no justification to do other than the above.
>>
>>> That is really all there is to it. What is important to realize is
>>> that case 3) needs to be architected according to the specific tunnel
>>> orientation - there is no generic one-size-fits-all rule that can be
>>> applied to all tunnels in all orientations.
>>
>> First, if rules depend on orientations, then there would be no rule for
>> tunnels at all. You cannot specify the requirements of a tunnel if it
>> depends on network placement - that rule does not exist for any other
>> Internet component (excepting only endpoint vs. network, but that's
>> function, not just placement).
>>
>> Second, there is a rule. See above.
>>
>> Joe
>>
>>
>>>
>>> Thanks - Fred
>>> fred.l.templin@boeing.com
>>>
>>>
>>>> -----Original Message-----
>>>> From: Joe Touch [mailto:touch@isi.edu]
>>>> Sent: Tuesday, February 18, 2014 8:47 AM
>>>> To: Templin, Fred L
>>>> Cc: Ronald Bonica; int-area@ietf.org
>>>> Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
>>>>
>>>> Hi, Fred,
>>>>
>>>> On Feb 17, 2014, at 10:51 AM, Templin, Fred L <Fred.L.Templin@boeing.com> wrote:
>>>>
>>>>> Hi Ron,
>>>>>
>>>>> The document needs to talk about packet sizes for IP payload packets.
>>>>
>>>> Yes, and I'm hoping we can add additional detail.
>>>>
>>>> Here's my view:
>>>>
>>>> -- path MTU is based on the min of the largest packet each link in the path can support
>>>>
>>>> -- links often transit packets larger than their native size, e.g., ATM's MTU is 9K, not 48 bytes
>>>>
>>>> -- links do have a native transit size, though
>>>>
>>>> So there ought to be two very different concepts
>>>>
>>>> - MTU (maximum)
>>>>
>>>> - PTU (preferred)
>>>>
>>>> IMO, much of the confusion about how MTUs are handled by tunnels is based on confusing MTU to mean
>>>> PTU.
>>>>
>>>> I.e.,
>>>>
>>>> 	- a tunnel has a PTU based on avoiding ingress fragmentation
>>>> 	and egress reassemly
>>>>
>>>> 	- a tunnel as a MTU, which is the MTU of the path of the tunnel
>>>> 	minus the headers it adds at the ingress
>>>>
>>>>> For IP payload packets no larger than MINMTU bytes, the GRE tunnel
>>>>> MUST accommodate the packet even if a small amount of fragmentation
>>>>> is necessary. (Here, the mandatory MINMTU for IPv6 is 1280 and the
>>>>> recommended MINMTU for IPv4 is also 1280.)
>>>>
>>>> This artificially limits tunnel MTU based on trying to support a perceived PTU, but doesn't match
>> PTU.
>>>>
>>>>> Beyond MINMTU, there needs to be a balance between avoiding path
>>>>> MTU related black holes for the source and avoiding excessive
>>>>> fragmentation at the GRE tunnel egress.
>>>>
>>>> If we really want to accomplish that, we need to flesh out the difference between MTU and PTU and
>>>> teach our apps to focus on PTU, ala a new PLPTUD (vs. current PLMTUD).
>>>>
>>>> I don't think we should be guessing this at the time we specify the tunnel, because the approach
>>>> varies based on what's transited (real IP packets or some other sort of encapsulation, e.g., IPsec
>> in
>>>> UDP).
>>>>
>>>>
>>>>> This balance is situation
>>>>> dependent. For example, if the GRE tunnel ingress is located close
>>>>> to the source, it should be reasonable to expect that the source
>>>>> would be able to receive any ICMP PTB messages sent by the ingress.
>>>>
>>>> Tunnels transit packets; they're not connected to sources or destinations. So are you proposing
>> that a
>>>> tunnel should now try to discover the length of the path in each direction and handle different
>>>> addresses differently? IMO, that's worse than reassembly.
>>>>
>>>>> Or, if the GRE tunnel egress is located close to the destination,
>>>>> it should be reasonable to expect that the egress can perform a
>>>>> small amount of reassembly.
>>>>
>>>> Same problem, and worse- do you expect vendors to sell different tunnel engines based on intended
>>>> traffic patterns?
>>>>
>>>> ----
>>>>
>>>> In conclusion, I would urge this document to focus on MTU as the goal, at which point the only
>> packets
>>>> that ought to be dropped at the ingress ought to be those that cannot be encapsulated with another
>>>> IPv4 header, i.e., that exceed the *MAXIMUM* payload size.
>>>>
>>>> If we want to tune for preferred path size, we need to extend PLMTUD for that purpose.
>>>>
>>>> Joe


From nobody Tue Feb 18 10:44:57 2014
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36EFE1A034B for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 10:44:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.749
X-Spam-Level: 
X-Spam-Status: No, score=-4.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AJyyTsVDOc5u for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 10:44:50 -0800 (PST)
Received: from slb-mbsout-02.boeing.com (slb-mbsout-02.boeing.com [130.76.64.129]) by ietfa.amsl.com (Postfix) with ESMTP id C879B1A010A for <int-area@ietf.org>; Tue, 18 Feb 2014 10:44:50 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id s1IIilFa002482; Tue, 18 Feb 2014 10:44:47 -0800
Received: from XCH-PHX-212.sw.nos.boeing.com (xch-phx-212.sw.nos.boeing.com [130.247.25.141]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id s1IIic2R002352 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Tue, 18 Feb 2014 10:44:38 -0800
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.102]) by XCH-PHX-212.sw.nos.boeing.com ([169.254.12.71]) with mapi id 14.03.0174.001; Tue, 18 Feb 2014 10:44:37 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Joe Touch <touch@isi.edu>
Thread-Topic: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
Thread-Index: AQHPLNc6Z6PoNhiMLkS+vK8jjU2/Npq7VsvQ
Date: Tue, 18 Feb 2014 18:44:36 +0000
Message-ID: <2134F8430051B64F815C691A62D983181D3823@XCH-BLV-504.nw.nos.boeing.com>
References: <68a71d0317c546689875cfb7a1a67f9b@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983181D205B@XCH-BLV-504.nw.nos.boeing.com> <F3D91914-1A80-4CEC-96B9-99CF2BF0F64B@isi.edu> <2134F8430051B64F815C691A62D983181D35E5@XCH-BLV-504.nw.nos.boeing.com> <5303A1AD.9070904@isi.edu> <2134F8430051B64F815C691A62D983181D37B6@XCH-BLV-504.nw.nos.boeing.com> <5303A650.2050303@isi.edu>
In-Reply-To: <5303A650.2050303@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/T8wuMIQONdgICYq_4a2gSAi_bTk
Cc: Ronald Bonica <rbonica@juniper.net>, "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2014 18:44:54 -0000

Hi Joe,

> -----Original Message-----
> From: Joe Touch [mailto:touch@isi.edu]
> Sent: Tuesday, February 18, 2014 10:29 AM
> To: Templin, Fred L
> Cc: Ronald Bonica; int-area@ietf.org
> Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-int=
area-gre-mtu-04.txt
>=20
>=20
>=20
> On 2/18/2014 10:22 AM, Templin, Fred L wrote:
> > Hi Joe,
> >
> > I can see that I am going to have to write a draft on generic tunnel
> > fragmentation.
>=20
> That's already a section in the tunnel draft that has been a WG doc:
>=20
> http://tools.ietf.org/html/draft-ietf-intarea-tunnels-00#section-3.2
>=20
> That doc has languished for lack of feedback, but IMO that's the place
> to put all one-stop information on tunnels that transit IP packets.

I can articulate one-stop generic text for tunnel fragmentation. Are
you suggesting reviving the above document?
=20
> I do agree that the current GRE doc could be more clear on this issue,
> but I don't think a new, separate doc on this is needed.

Each tunnel type can certainly articulate its own fragmentation
scheme if it wants to - I have already done that for 6rd and AERO:

https://datatracker.ietf.org/doc/draft-foo-v6ops-6rdmtu/
https://datatracker.ietf.org/doc/draft-templin-aerolink/

But, would be better if the individual docs could point to a
one-stop generic text and then just give 1-2 sentences on their
specific adaptation of the generic text. Would that work for you?

Thanks - Fred
fred.l.templin@boeing.com
=20
> Joe
>=20
> > It will be based on my e-mail from two messages ago.
> > I have already written drafts on 6rd tunnel fragmentation and AERO
> > tunnel fragmentation, and they are already consistent with the to-
> > be-written draft on generic tunnel fragmentation. Your draft on GRE
> > fragmentation can then also cite the generic tunnel fragmentation doc.
> >
> > Thanks - Fred
> > fred.l.templin@boeing.com
> >
> >> -----Original Message-----
> >> From: Joe Touch [mailto:touch@isi.edu]
> >> Sent: Tuesday, February 18, 2014 10:09 AM
> >> To: Templin, Fred L
> >> Cc: Ronald Bonica; int-area@ietf.org
> >> Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-=
intarea-gre-mtu-04.txt
> >>
> >>
> >>
> >> On 2/18/2014 9:27 AM, Templin, Fred L wrote:
> >>> Hi Joe,
> >>>
> >>> You seem to be talking past me - maybe it was because I wrote too muc=
h.
> >>> The fragmentation story for tunnels is very simple as follows:
> >>
> >> Yes, IMO they are, and here's mine:
> >>
> >> 	- if a tunnel CAN transit a packet, it MUST try
> >>
> >> 		i.e., the MTU of a tunnel that uses IPv6 encapsulation
> >> 		is 65535 - encapsulation headers
> >>
> >> 	- if a tunnel CANNOT transit a packet, it rejects it
> >>
> >> 		i.e., anything larger than "65535 - encap headers"
> >>
> >> Everything else mistakes MSS (maximum) for PSS (preferred). Preferred =
is
> >> the min of the MSS's. An IPv6 tunnel limits MSS only insofar as packet=
s
> >> larger than 65535-headers cannot traverse it.
> >>
> >> So...
> >>
> >>> 1) IPv6 has a minimum MTU of 1280 bytes. So, packets that are no larg=
er
> >>>      than this size MUST be accommodated even if a small amount of
> >>>      fragmentation is necessary. IPv4 has a much smaller minMTU, but
> >>>      IMHO tunnels SHOULD behave as if the IPv4 minMTU is also 1280.
> >>
> >> An IPv6 tunnel is a link to the IPv6 protocol. IPv6 requires that the
> >> smallest MTU of all links must be no less than 1280. So agreed.
> >>
> >>> 2) Packets larger than 1500 bytes (with the exception of IPv4 packets
> >>>      with DF=3D0) should be allowed to sink or swim on their own. Tun=
nels
> >>>      therefore MUST NOT use fragmentation for packets larger than 150=
0.
> >>
> >> Completely disagree. The max size of the payload of GRE in IPv6 is muc=
h
> >> larger than 1500.
> >>
> >> You're trying to do something at the tunnel layer that the path is
> >> supposed to be in control of.
> >>
> >>> 3) Packets larger than 1280 but no larger than 1500 are in a "gray ar=
ea"
> >>>      where the way the tunnel accommodates them depends on the specif=
ic
> >>>      tunnel orientation. In some cases the tunnel should send as a wh=
ole
> >>>      packet. In others, it should drop and send a PTB. In still other=
s,
> >>>      it should fragment. The cases are easy to articulate.
> >>
> >> There is no grey area. Until the max payload of an IPv6 packet is
> >> decreased, there's simply no justification to do other than the above.
> >>
> >>> That is really all there is to it. What is important to realize is
> >>> that case 3) needs to be architected according to the specific tunnel
> >>> orientation - there is no generic one-size-fits-all rule that can be
> >>> applied to all tunnels in all orientations.
> >>
> >> First, if rules depend on orientations, then there would be no rule fo=
r
> >> tunnels at all. You cannot specify the requirements of a tunnel if it
> >> depends on network placement - that rule does not exist for any other
> >> Internet component (excepting only endpoint vs. network, but that's
> >> function, not just placement).
> >>
> >> Second, there is a rule. See above.
> >>
> >> Joe
> >>
> >>
> >>>
> >>> Thanks - Fred
> >>> fred.l.templin@boeing.com
> >>>
> >>>
> >>>> -----Original Message-----
> >>>> From: Joe Touch [mailto:touch@isi.edu]
> >>>> Sent: Tuesday, February 18, 2014 8:47 AM
> >>>> To: Templin, Fred L
> >>>> Cc: Ronald Bonica; int-area@ietf.org
> >>>> Subject: Re: [Int-area] FW: New Version Notification for draft-bonic=
a-intarea-gre-mtu-04.txt
> >>>>
> >>>> Hi, Fred,
> >>>>
> >>>> On Feb 17, 2014, at 10:51 AM, Templin, Fred L <Fred.L.Templin@boeing=
.com> wrote:
> >>>>
> >>>>> Hi Ron,
> >>>>>
> >>>>> The document needs to talk about packet sizes for IP payload packet=
s.
> >>>>
> >>>> Yes, and I'm hoping we can add additional detail.
> >>>>
> >>>> Here's my view:
> >>>>
> >>>> -- path MTU is based on the min of the largest packet each link in t=
he path can support
> >>>>
> >>>> -- links often transit packets larger than their native size, e.g., =
ATM's MTU is 9K, not 48 bytes
> >>>>
> >>>> -- links do have a native transit size, though
> >>>>
> >>>> So there ought to be two very different concepts
> >>>>
> >>>> - MTU (maximum)
> >>>>
> >>>> - PTU (preferred)
> >>>>
> >>>> IMO, much of the confusion about how MTUs are handled by tunnels is =
based on confusing MTU to
> mean
> >>>> PTU.
> >>>>
> >>>> I.e.,
> >>>>
> >>>> 	- a tunnel has a PTU based on avoiding ingress fragmentation
> >>>> 	and egress reassemly
> >>>>
> >>>> 	- a tunnel as a MTU, which is the MTU of the path of the tunnel
> >>>> 	minus the headers it adds at the ingress
> >>>>
> >>>>> For IP payload packets no larger than MINMTU bytes, the GRE tunnel
> >>>>> MUST accommodate the packet even if a small amount of fragmentation
> >>>>> is necessary. (Here, the mandatory MINMTU for IPv6 is 1280 and the
> >>>>> recommended MINMTU for IPv4 is also 1280.)
> >>>>
> >>>> This artificially limits tunnel MTU based on trying to support a per=
ceived PTU, but doesn't match
> >> PTU.
> >>>>
> >>>>> Beyond MINMTU, there needs to be a balance between avoiding path
> >>>>> MTU related black holes for the source and avoiding excessive
> >>>>> fragmentation at the GRE tunnel egress.
> >>>>
> >>>> If we really want to accomplish that, we need to flesh out the diffe=
rence between MTU and PTU and
> >>>> teach our apps to focus on PTU, ala a new PLPTUD (vs. current PLMTUD=
).
> >>>>
> >>>> I don't think we should be guessing this at the time we specify the =
tunnel, because the approach
> >>>> varies based on what's transited (real IP packets or some other sort=
 of encapsulation, e.g.,
> IPsec
> >> in
> >>>> UDP).
> >>>>
> >>>>
> >>>>> This balance is situation
> >>>>> dependent. For example, if the GRE tunnel ingress is located close
> >>>>> to the source, it should be reasonable to expect that the source
> >>>>> would be able to receive any ICMP PTB messages sent by the ingress.
> >>>>
> >>>> Tunnels transit packets; they're not connected to sources or destina=
tions. So are you proposing
> >> that a
> >>>> tunnel should now try to discover the length of the path in each dir=
ection and handle different
> >>>> addresses differently? IMO, that's worse than reassembly.
> >>>>
> >>>>> Or, if the GRE tunnel egress is located close to the destination,
> >>>>> it should be reasonable to expect that the egress can perform a
> >>>>> small amount of reassembly.
> >>>>
> >>>> Same problem, and worse- do you expect vendors to sell different tun=
nel engines based on intended
> >>>> traffic patterns?
> >>>>
> >>>> ----
> >>>>
> >>>> In conclusion, I would urge this document to focus on MTU as the goa=
l, at which point the only
> >> packets
> >>>> that ought to be dropped at the ingress ought to be those that canno=
t be encapsulated with
> another
> >>>> IPv4 header, i.e., that exceed the *MAXIMUM* payload size.
> >>>>
> >>>> If we want to tune for preferred path size, we need to extend PLMTUD=
 for that purpose.
> >>>>
> >>>> Joe


From nobody Tue Feb 18 10:45:15 2014
Return-Path: <rbonica@juniper.net>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 168B21A0401 for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 10:45:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.201
X-Spam-Level: 
X-Spam-Status: No, score=-104.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8mt8ZViIkmF7 for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 10:45:10 -0800 (PST)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe005.messaging.microsoft.com [65.55.88.15]) by ietfa.amsl.com (Postfix) with ESMTP id 470831A03DE for <int-area@ietf.org>; Tue, 18 Feb 2014 10:45:10 -0800 (PST)
Received: from mail102-tx2-R.bigfish.com (10.9.14.229) by TX2EHSOBE008.bigfish.com (10.9.40.28) with Microsoft SMTP Server id 14.1.225.22; Tue, 18 Feb 2014 18:45:07 +0000
Received: from mail102-tx2 (localhost [127.0.0.1])	by mail102-tx2-R.bigfish.com (Postfix) with ESMTP id F374F140161;	Tue, 18 Feb 2014 18:45:06 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT003.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -24
X-BigFish: VPS-24(z579ehzbb2dI98dI9371I542I1432I1418Izz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6hzd9hz1de098h1033IL8275dh1de097hz2fh109h2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1e1dh1fe8h1ff5h2216h22d0h2336h2461h2487h24ach24d7h2516h2545h255eh9a9j1155h)
Received-SPF: pass (mail102-tx2: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=rbonica@juniper.net; helo=BL2PRD0510HT003.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(6009001)(189002)(199002)(51444003)(479174003)(13464003)(24454002)(51704005)(377454003)(74366001)(47976001)(87266001)(19580395003)(95416001)(85306002)(47736001)(94946001)(83322001)(49866001)(56776001)(93136001)(93516002)(2656002)(95666001)(69226001)(19580405001)(79102001)(66066001)(74316001)(80022001)(59766001)(92566001)(76796001)(50986001)(33646001)(76482001)(31966008)(63696002)(74662001)(74502001)(47446002)(74706001)(85852003)(81816001)(81686001)(53806001)(90146001)(56816005)(2171001)(54316002)(81342001)(77982001)(94316002)(80976001)(76576001)(65816001)(74876001)(76786001)(86362001)(81542001)(51856001)(83072002)(87936001)(4396001)(54356001)(77096001)(46102001)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:CO1PR05MB442; H:CO1PR05MB442.namprd05.prod.outlook.com; CLIP:66.129.241.12; FPR:9E5AD1D4.9E27E756.E1D19D7B.84EC8AFC.2023C; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
Received: from mail102-tx2 (localhost.localdomain [127.0.0.1]) by mail102-tx2 (MessageSwitch) id 1392749105121610_18595; Tue, 18 Feb 2014 18:45:05 +0000 (UTC)
Received: from TX2EHSMHS036.bigfish.com (unknown [10.9.14.232])	by mail102-tx2.bigfish.com (Postfix) with ESMTP id 05120100188; Tue, 18 Feb 2014 18:45:05 +0000 (UTC)
Received: from BL2PRD0510HT003.namprd05.prod.outlook.com (157.56.240.101) by TX2EHSMHS036.bigfish.com (10.9.99.136) with Microsoft SMTP Server (TLS) id 14.16.227.3; Tue, 18 Feb 2014 18:45:04 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) by BL2PRD0510HT003.namprd05.prod.outlook.com (10.255.100.38) with Microsoft SMTP Server (TLS) id 14.16.411.0; Tue, 18 Feb 2014 18:45:02 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) by CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) with Microsoft SMTP Server (TLS) id 15.0.878.16; Tue, 18 Feb 2014 18:45:00 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.51]) by CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.51]) with mapi id 15.00.0878.008; Tue, 18 Feb 2014 18:45:00 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: Joe Touch <touch@isi.edu>, "Templin, Fred L" <Fred.L.Templin@boeing.com>
Thread-Topic: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
Thread-Index: AQHPLMlCh50qgiy+bEODxx+djLKnh5q7Q7aAgAALpICAAAPXAIAAAbAAgAAAjjA=
Date: Tue, 18 Feb 2014 18:45:00 +0000
Message-ID: <d02b9aae44b44fdb8bb880f2cdd555cd@CO1PR05MB442.namprd05.prod.outlook.com>
References: <68a71d0317c546689875cfb7a1a67f9b@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983181D205B@XCH-BLV-504.nw.nos.boeing.com> <F3D91914-1A80-4CEC-96B9-99CF2BF0F64B@isi.edu> <2134F8430051B64F815C691A62D983181D35E5@XCH-BLV-504 <5303A650.2050303@isi.edu>
In-Reply-To: <5303A650.2050303@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.12]
x-forefront-prvs: 0126A32F74
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/z1eNDmhEkKxp98YOQ3NCYyIAUbs
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2014 18:45:13 -0000

Folks,

I think that we are conflating two separate efforts.

Draft-bonica-intarea-gre-mtu describes what is widely deployed today. In to=
day's, one of the following conditions frequently holds:

- the operator of the GRE ingress knows that the GRE egress cannot reassemb=
le fragments at the required rate
- the operator of the GRE ingress has no information regarding whether the =
GRE egress can reassemble fragments at the required rate

Therefore, in draft-bonica, by default, the PTU is equal to the MTU. Fragme=
ntation doesn't happen in the tunnel. However, in the exceptional case, whe=
re the operator of the ingress knows that the egress can reassemble at the =
required rate, fragmentation of the delivery packet is permitted.

The draft that Joe and Fred are considering applies to environments where e=
gress routers are commonly capable of reassembling at line rate. Since this=
 is a different environment, it should be addressed in a separate draft.

                                               Ron


-----Original Message-----
From: Joe Touch [mailto:touch@isi.edu]=20
Sent: Tuesday, February 18, 2014 1:29 PM
To: Templin, Fred L
Cc: Ronald Bonica; int-area@ietf.org
Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-intar=
ea-gre-mtu-04.txt



On 2/18/2014 10:22 AM, Templin, Fred L wrote:
> Hi Joe,
>
> I can see that I am going to have to write a draft on generic tunnel=20
> fragmentation.

-=20


From nobody Tue Feb 18 10:51:30 2014
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6201D1A0401 for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 10:51:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.749
X-Spam-Level: 
X-Spam-Status: No, score=-4.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xy_mbYuzSQ6C for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 10:51:27 -0800 (PST)
Received: from blv-mbsout-02.boeing.com (blv-mbsout-02.boeing.com [130.76.32.232]) by ietfa.amsl.com (Postfix) with ESMTP id DC7B21A0250 for <int-area@ietf.org>; Tue, 18 Feb 2014 10:51:21 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id s1IIpJXV031826; Tue, 18 Feb 2014 10:51:19 -0800
Received: from XCH-PHX-112.sw.nos.boeing.com (xch-phx-112.sw.nos.boeing.com [130.247.25.134]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id s1IIpDFq031761 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Tue, 18 Feb 2014 10:51:13 -0800
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.102]) by XCH-PHX-112.sw.nos.boeing.com ([169.254.12.134]) with mapi id 14.03.0174.001;  Tue, 18 Feb 2014 10:51:12 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ronald Bonica <rbonica@juniper.net>, Joe Touch <touch@isi.edu>
Thread-Topic: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
Thread-Index: AQHPLMlCZ6PoNhiMLkS+vK8jjU2/Npq7Q7aAgAALpICAAAPXAIAAAbAAgAAAjjCAAASxAA==
Date: Tue, 18 Feb 2014 18:51:12 +0000
Message-ID: <2134F8430051B64F815C691A62D983181D386A@XCH-BLV-504.nw.nos.boeing.com>
References: <68a71d0317c546689875cfb7a1a67f9b@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983181D205B@XCH-BLV-504.nw.nos.boeing.com> <F3D91914-1A80-4CEC-96B9-99CF2BF0F64B@isi.edu> <2134F8430051B64F815C691A62D983181D35E5@XCH-BLV-504 <5303A650.2050303@isi.edu> <d02b9aae44b44fdb8bb880f2cdd555cd@CO1PR05MB442.namprd05.prod.outlook.com>
In-Reply-To: <d02b9aae44b44fdb8bb880f2cdd555cd@CO1PR05MB442.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/wtXfwaoXg1AW8BrPmDuFDm1O-Qw
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2014 18:51:29 -0000

Hi Ron,

What you are describing is easily articulated in the generic text
that would apply to all tunnel types - not just GRE. The draft Joe
and I are considering would be a generic document and not anything
that assumes any specific reassembly capabilities, for example.

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

> -----Original Message-----
> From: Ronald Bonica [mailto:rbonica@juniper.net]
> Sent: Tuesday, February 18, 2014 10:45 AM
> To: Joe Touch; Templin, Fred L
> Cc: int-area@ietf.org
> Subject: RE: [Int-area] FW: New Version Notification for draft-bonica-int=
area-gre-mtu-04.txt
>=20
> Folks,
>=20
> I think that we are conflating two separate efforts.
>=20
> Draft-bonica-intarea-gre-mtu describes what is widely deployed today. In =
today's, one of the following
> conditions frequently holds:
>=20
> - the operator of the GRE ingress knows that the GRE egress cannot reasse=
mble fragments at the
> required rate
> - the operator of the GRE ingress has no information regarding whether th=
e GRE egress can reassemble
> fragments at the required rate
>=20
> Therefore, in draft-bonica, by default, the PTU is equal to the MTU. Frag=
mentation doesn't happen in
> the tunnel. However, in the exceptional case, where the operator of the i=
ngress knows that the egress
> can reassemble at the required rate, fragmentation of the delivery packet=
 is permitted.
>=20
> The draft that Joe and Fred are considering applies to environments where=
 egress routers are commonly
> capable of reassembling at line rate. Since this is a different environme=
nt, it should be addressed in
> a separate draft.
>=20
>                                                Ron
>=20
>=20
> -----Original Message-----
> From: Joe Touch [mailto:touch@isi.edu]
> Sent: Tuesday, February 18, 2014 1:29 PM
> To: Templin, Fred L
> Cc: Ronald Bonica; int-area@ietf.org
> Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-int=
area-gre-mtu-04.txt
>=20
>=20
>=20
> On 2/18/2014 10:22 AM, Templin, Fred L wrote:
> > Hi Joe,
> >
> > I can see that I am going to have to write a draft on generic tunnel
> > fragmentation.
>=20
> -


From nobody Tue Feb 18 10:54:25 2014
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF9B51A03F9 for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 10:54:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D4cGSPd8SQvo for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 10:54:19 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id DFCC41A03ED for <int-area@ietf.org>; Tue, 18 Feb 2014 10:54:09 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id s1IIqqpv000637 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 18 Feb 2014 10:52:53 -0800 (PST)
Message-ID: <5303AC03.2090008@isi.edu>
Date: Tue, 18 Feb 2014 10:52:51 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
References: <68a71d0317c546689875cfb7a1a67f9b@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983181D205B@XCH-BLV-504.nw.nos.boeing.com> <F3D91914-1A80-4CEC-96B9-99CF2BF0F64B@isi.edu> <2134F8430051B64F815C691A62D983181D35E5@XCH-BLV-504.nw.nos.boeing.com> <5303A1AD.9070904@isi.edu> <2134F8430051B64F815C691A62D983181D37B6@XCH-BLV-504.nw.nos.boeing.com> <5303A650.2050303@isi.edu> <2134F8430051B64F815C691A62D983181D3823@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D983181D3823@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/3eDEbNND936wAVDCkCzQvv1WzfY
Cc: Ronald Bonica <rbonica@juniper.net>, "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2014 18:54:23 -0000

On 2/18/2014 10:44 AM, Templin, Fred L wrote:
> Hi Joe,
>
>> -----Original Message-----
>> From: Joe Touch [mailto:touch@isi.edu]
>> Sent: Tuesday, February 18, 2014 10:29 AM
>> To: Templin, Fred L
>> Cc: Ronald Bonica; int-area@ietf.org
>> Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
>>
>>
>>
>> On 2/18/2014 10:22 AM, Templin, Fred L wrote:
>>> Hi Joe,
>>>
>>> I can see that I am going to have to write a draft on generic tunnel
>>> fragmentation.
>>
>> That's already a section in the tunnel draft that has been a WG doc:
>>
>> http://tools.ietf.org/html/draft-ietf-intarea-tunnels-00#section-3.2
>>
>> That doc has languished for lack of feedback, but IMO that's the place
>> to put all one-stop information on tunnels that transit IP packets.
>
> I can articulate one-stop generic text for tunnel fragmentation. Are
> you suggesting reviving the above document?

Yes; it already is supposed to be one-stop, generic text for all tunnel 
issues, and has a section on MTU issues already. Can you let us know 
what part of that needs to be fixed?

>> I do agree that the current GRE doc could be more clear on this issue,
>> but I don't think a new, separate doc on this is needed.
>
> Each tunnel type can certainly articulate its own fragmentation
> scheme if it wants to - I have already done that for 6rd and AERO:
>
> https://datatracker.ietf.org/doc/draft-foo-v6ops-6rdmtu/
> https://datatracker.ietf.org/doc/draft-templin-aerolink/

The generic description should explain how and why the rules should 
vary. In that case, then specifics do belong in specific tunnel specs.

> But, would be better if the individual docs could point to a
> one-stop generic text and then just give 1-2 sentences on their
> specific adaptation of the generic text. Would that work for you?

Yes, but again that's already the purpose of the Intarea tunnel doc, 
which already has a lot of different discussions like this (ICMP signal 
relaying, MTU, etc.).

Joe



>
> Thanks - Fred
> fred.l.templin@boeing.com
>
>> Joe
>>
>>> It will be based on my e-mail from two messages ago.
>>> I have already written drafts on 6rd tunnel fragmentation and AERO
>>> tunnel fragmentation, and they are already consistent with the to-
>>> be-written draft on generic tunnel fragmentation. Your draft on GRE
>>> fragmentation can then also cite the generic tunnel fragmentation doc.
>>>
>>> Thanks - Fred
>>> fred.l.templin@boeing.com
>>>
>>>> -----Original Message-----
>>>> From: Joe Touch [mailto:touch@isi.edu]
>>>> Sent: Tuesday, February 18, 2014 10:09 AM
>>>> To: Templin, Fred L
>>>> Cc: Ronald Bonica; int-area@ietf.org
>>>> Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
>>>>
>>>>
>>>>
>>>> On 2/18/2014 9:27 AM, Templin, Fred L wrote:
>>>>> Hi Joe,
>>>>>
>>>>> You seem to be talking past me - maybe it was because I wrote too much.
>>>>> The fragmentation story for tunnels is very simple as follows:
>>>>
>>>> Yes, IMO they are, and here's mine:
>>>>
>>>> 	- if a tunnel CAN transit a packet, it MUST try
>>>>
>>>> 		i.e., the MTU of a tunnel that uses IPv6 encapsulation
>>>> 		is 65535 - encapsulation headers
>>>>
>>>> 	- if a tunnel CANNOT transit a packet, it rejects it
>>>>
>>>> 		i.e., anything larger than "65535 - encap headers"
>>>>
>>>> Everything else mistakes MSS (maximum) for PSS (preferred). Preferred is
>>>> the min of the MSS's. An IPv6 tunnel limits MSS only insofar as packets
>>>> larger than 65535-headers cannot traverse it.
>>>>
>>>> So...
>>>>
>>>>> 1) IPv6 has a minimum MTU of 1280 bytes. So, packets that are no larger
>>>>>       than this size MUST be accommodated even if a small amount of
>>>>>       fragmentation is necessary. IPv4 has a much smaller minMTU, but
>>>>>       IMHO tunnels SHOULD behave as if the IPv4 minMTU is also 1280.
>>>>
>>>> An IPv6 tunnel is a link to the IPv6 protocol. IPv6 requires that the
>>>> smallest MTU of all links must be no less than 1280. So agreed.
>>>>
>>>>> 2) Packets larger than 1500 bytes (with the exception of IPv4 packets
>>>>>       with DF=0) should be allowed to sink or swim on their own. Tunnels
>>>>>       therefore MUST NOT use fragmentation for packets larger than 1500.
>>>>
>>>> Completely disagree. The max size of the payload of GRE in IPv6 is much
>>>> larger than 1500.
>>>>
>>>> You're trying to do something at the tunnel layer that the path is
>>>> supposed to be in control of.
>>>>
>>>>> 3) Packets larger than 1280 but no larger than 1500 are in a "gray area"
>>>>>       where the way the tunnel accommodates them depends on the specific
>>>>>       tunnel orientation. In some cases the tunnel should send as a whole
>>>>>       packet. In others, it should drop and send a PTB. In still others,
>>>>>       it should fragment. The cases are easy to articulate.
>>>>
>>>> There is no grey area. Until the max payload of an IPv6 packet is
>>>> decreased, there's simply no justification to do other than the above.
>>>>
>>>>> That is really all there is to it. What is important to realize is
>>>>> that case 3) needs to be architected according to the specific tunnel
>>>>> orientation - there is no generic one-size-fits-all rule that can be
>>>>> applied to all tunnels in all orientations.
>>>>
>>>> First, if rules depend on orientations, then there would be no rule for
>>>> tunnels at all. You cannot specify the requirements of a tunnel if it
>>>> depends on network placement - that rule does not exist for any other
>>>> Internet component (excepting only endpoint vs. network, but that's
>>>> function, not just placement).
>>>>
>>>> Second, there is a rule. See above.
>>>>
>>>> Joe
>>>>
>>>>
>>>>>
>>>>> Thanks - Fred
>>>>> fred.l.templin@boeing.com
>>>>>
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Joe Touch [mailto:touch@isi.edu]
>>>>>> Sent: Tuesday, February 18, 2014 8:47 AM
>>>>>> To: Templin, Fred L
>>>>>> Cc: Ronald Bonica; int-area@ietf.org
>>>>>> Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
>>>>>>
>>>>>> Hi, Fred,
>>>>>>
>>>>>> On Feb 17, 2014, at 10:51 AM, Templin, Fred L <Fred.L.Templin@boeing.com> wrote:
>>>>>>
>>>>>>> Hi Ron,
>>>>>>>
>>>>>>> The document needs to talk about packet sizes for IP payload packets.
>>>>>>
>>>>>> Yes, and I'm hoping we can add additional detail.
>>>>>>
>>>>>> Here's my view:
>>>>>>
>>>>>> -- path MTU is based on the min of the largest packet each link in the path can support
>>>>>>
>>>>>> -- links often transit packets larger than their native size, e.g., ATM's MTU is 9K, not 48 bytes
>>>>>>
>>>>>> -- links do have a native transit size, though
>>>>>>
>>>>>> So there ought to be two very different concepts
>>>>>>
>>>>>> - MTU (maximum)
>>>>>>
>>>>>> - PTU (preferred)
>>>>>>
>>>>>> IMO, much of the confusion about how MTUs are handled by tunnels is based on confusing MTU to
>> mean
>>>>>> PTU.
>>>>>>
>>>>>> I.e.,
>>>>>>
>>>>>> 	- a tunnel has a PTU based on avoiding ingress fragmentation
>>>>>> 	and egress reassemly
>>>>>>
>>>>>> 	- a tunnel as a MTU, which is the MTU of the path of the tunnel
>>>>>> 	minus the headers it adds at the ingress
>>>>>>
>>>>>>> For IP payload packets no larger than MINMTU bytes, the GRE tunnel
>>>>>>> MUST accommodate the packet even if a small amount of fragmentation
>>>>>>> is necessary. (Here, the mandatory MINMTU for IPv6 is 1280 and the
>>>>>>> recommended MINMTU for IPv4 is also 1280.)
>>>>>>
>>>>>> This artificially limits tunnel MTU based on trying to support a perceived PTU, but doesn't match
>>>> PTU.
>>>>>>
>>>>>>> Beyond MINMTU, there needs to be a balance between avoiding path
>>>>>>> MTU related black holes for the source and avoiding excessive
>>>>>>> fragmentation at the GRE tunnel egress.
>>>>>>
>>>>>> If we really want to accomplish that, we need to flesh out the difference between MTU and PTU and
>>>>>> teach our apps to focus on PTU, ala a new PLPTUD (vs. current PLMTUD).
>>>>>>
>>>>>> I don't think we should be guessing this at the time we specify the tunnel, because the approach
>>>>>> varies based on what's transited (real IP packets or some other sort of encapsulation, e.g.,
>> IPsec
>>>> in
>>>>>> UDP).
>>>>>>
>>>>>>
>>>>>>> This balance is situation
>>>>>>> dependent. For example, if the GRE tunnel ingress is located close
>>>>>>> to the source, it should be reasonable to expect that the source
>>>>>>> would be able to receive any ICMP PTB messages sent by the ingress.
>>>>>>
>>>>>> Tunnels transit packets; they're not connected to sources or destinations. So are you proposing
>>>> that a
>>>>>> tunnel should now try to discover the length of the path in each direction and handle different
>>>>>> addresses differently? IMO, that's worse than reassembly.
>>>>>>
>>>>>>> Or, if the GRE tunnel egress is located close to the destination,
>>>>>>> it should be reasonable to expect that the egress can perform a
>>>>>>> small amount of reassembly.
>>>>>>
>>>>>> Same problem, and worse- do you expect vendors to sell different tunnel engines based on intended
>>>>>> traffic patterns?
>>>>>>
>>>>>> ----
>>>>>>
>>>>>> In conclusion, I would urge this document to focus on MTU as the goal, at which point the only
>>>> packets
>>>>>> that ought to be dropped at the ingress ought to be those that cannot be encapsulated with
>> another
>>>>>> IPv4 header, i.e., that exceed the *MAXIMUM* payload size.
>>>>>>
>>>>>> If we want to tune for preferred path size, we need to extend PLMTUD for that purpose.
>>>>>>
>>>>>> Joe


From nobody Tue Feb 18 10:58:34 2014
Return-Path: <rbonica@juniper.net>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A661A1A0535 for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 10:58:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.201
X-Spam-Level: 
X-Spam-Status: No, score=-104.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qQwCrMzAJK54 for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 10:58:29 -0800 (PST)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe005.messaging.microsoft.com [65.55.88.15]) by ietfa.amsl.com (Postfix) with ESMTP id 1BD9B1A015F for <int-area@ietf.org>; Tue, 18 Feb 2014 10:58:26 -0800 (PST)
Received: from mail64-tx2-R.bigfish.com (10.9.14.227) by TX2EHSOBE008.bigfish.com (10.9.40.28) with Microsoft SMTP Server id 14.1.225.22; Tue, 18 Feb 2014 18:58:23 +0000
Received: from mail64-tx2 (localhost [127.0.0.1])	by mail64-tx2-R.bigfish.com (Postfix) with ESMTP id 229301040205; Tue, 18 Feb 2014 18:58:23 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT005.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -24
X-BigFish: VPS-24(z579ehzbb2dI98dI9371I542I1432I1418Izz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6hzd9hz1de098h1033IL8275bh8275dh1de097hz2fh109h2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1e1dh1fe8h1ff5h2216h22d0h2336h2461h2487h24ach24d7h2516h2545h255eh9a9j1155h)
Received-SPF: pass (mail64-tx2: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=rbonica@juniper.net; helo=BL2PRD0510HT005.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(6009001)(377454003)(51704005)(199002)(189002)(51444003)(24454002)(13464003)(479174003)(74706001)(85852003)(47446002)(56816005)(2171001)(90146001)(53806001)(81686001)(81816001)(74502001)(74662001)(76482001)(31966008)(63696002)(51856001)(83072002)(87936001)(86362001)(81542001)(54356001)(77096001)(46102001)(4396001)(94316002)(81342001)(77982001)(54316002)(74876001)(76786001)(76576001)(80976001)(65816001)(83322001)(56776001)(49866001)(94946001)(47736001)(2656002)(93136001)(93516002)(47976001)(74366001)(19580395003)(95416001)(87266001)(85306002)(92566001)(76796001)(59766001)(33646001)(50986001)(19580405001)(69226001)(95666001)(79102001)(80022001)(74316001)(66066001)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:CO1PR05MB442; H:CO1PR05MB442.namprd05.prod.outlook.com; CLIP:66.129.241.12; FPR:AE5CD1D4.9E2BE756.E1D19D7B.84F4EA7D.202D8; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
Received: from mail64-tx2 (localhost.localdomain [127.0.0.1]) by mail64-tx2 (MessageSwitch) id 13927499012058_21923; Tue, 18 Feb 2014 18:58:21 +0000 (UTC)
Received: from TX2EHSMHS042.bigfish.com (unknown [10.9.14.237])	by mail64-tx2.bigfish.com (Postfix) with ESMTP id E2228A201A6;	Tue, 18 Feb 2014 18:58:20 +0000 (UTC)
Received: from BL2PRD0510HT005.namprd05.prod.outlook.com (157.56.240.101) by TX2EHSMHS042.bigfish.com (10.9.99.142) with Microsoft SMTP Server (TLS) id 14.16.227.3; Tue, 18 Feb 2014 18:58:17 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) by BL2PRD0510HT005.namprd05.prod.outlook.com (10.255.100.40) with Microsoft SMTP Server (TLS) id 14.16.411.0; Tue, 18 Feb 2014 18:58:17 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) by CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) with Microsoft SMTP Server (TLS) id 15.0.878.16; Tue, 18 Feb 2014 18:58:14 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.51]) by CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.51]) with mapi id 15.00.0878.008; Tue, 18 Feb 2014 18:58:14 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, Joe Touch <touch@isi.edu>
Thread-Topic: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
Thread-Index: AQHPLMlCh50qgiy+bEODxx+djLKnh5q7Q7aAgAALpICAAAPXAIAAAbAAgAAAjjCAAAXHAIAAAb8w
Date: Tue, 18 Feb 2014 18:58:13 +0000
Message-ID: <9094cfbcd86b4abeaeb16715e17f820e@CO1PR05MB442.namprd05.prod.outlook.com>
References: <68a71d0317c546689875cfb7a1a67f9b@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983181D205B@XCH-BLV-504.nw.nos.boeing.com> <F3D91914-1A80-4CEC-96B9-99CF2BF0F64B@isi.edu> <2134F8430051B64F815C691A62D983181D35E5@XCH-BLV-504 <5303A650.2050303@isi.edu> <d02b9aae44b44fdb8bb880f2cdd555cd@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983181D386A@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D983181D386A@XCH-BLV-504.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.12]
x-forefront-prvs: 0126A32F74
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/7CAX7lUTHUIXF-zksOju82vdJqw
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2014 18:58:32 -0000

Hi Fred,

All the more reason to address the issue in a separate draft!

                         Ron

-----Original Message-----
From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]=20
Sent: Tuesday, February 18, 2014 1:51 PM
To: Ronald Bonica; Joe Touch
Cc: int-area@ietf.org
Subject: RE: [Int-area] FW: New Version Notification for draft-bonica-intar=
ea-gre-mtu-04.txt

Hi Ron,

What you are describing is easily articulated in the generic text that woul=
d apply to all tunnel types - not just GRE. The draft Joe and I are conside=
ring would be a generic document and not anything that assumes any specific=
 reassembly capabilities, for example.

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

> -----Original Message-----
> From: Ronald Bonica [mailto:rbonica@juniper.net]
> Sent: Tuesday, February 18, 2014 10:45 AM
> To: Joe Touch; Templin, Fred L
> Cc: int-area@ietf.org
> Subject: RE: [Int-area] FW: New Version Notification for=20
> draft-bonica-intarea-gre-mtu-04.txt
>=20
> Folks,
>=20
> I think that we are conflating two separate efforts.
>=20
> Draft-bonica-intarea-gre-mtu describes what is widely deployed today.=20
> In today's, one of the following conditions frequently holds:
>=20
> - the operator of the GRE ingress knows that the GRE egress cannot=20
> reassemble fragments at the required rate
> - the operator of the GRE ingress has no information regarding whether=20
> the GRE egress can reassemble fragments at the required rate
>=20
> Therefore, in draft-bonica, by default, the PTU is equal to the MTU.=20
> Fragmentation doesn't happen in the tunnel. However, in the=20
> exceptional case, where the operator of the ingress knows that the egress=
 can reassemble at the required rate, fragmentation of the delivery packet =
is permitted.
>=20
> The draft that Joe and Fred are considering applies to environments=20
> where egress routers are commonly capable of reassembling at line=20
> rate. Since this is a different environment, it should be addressed in a =
separate draft.
>=20
>                                                Ron
>=20
>=20
> -----Original Message-----
> From: Joe Touch [mailto:touch@isi.edu]
> Sent: Tuesday, February 18, 2014 1:29 PM
> To: Templin, Fred L
> Cc: Ronald Bonica; int-area@ietf.org
> Subject: Re: [Int-area] FW: New Version Notification for=20
> draft-bonica-intarea-gre-mtu-04.txt
>=20
>=20
>=20
> On 2/18/2014 10:22 AM, Templin, Fred L wrote:
> > Hi Joe,
> >
> > I can see that I am going to have to write a draft on generic tunnel=20
> > fragmentation.
>=20
> -





From nobody Tue Feb 18 11:02:40 2014
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5900E1A0438 for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 11:02:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.749
X-Spam-Level: 
X-Spam-Status: No, score=-4.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fTsaZL_1GbM0 for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 11:02:36 -0800 (PST)
Received: from blv-mbsout-02.boeing.com (blv-mbsout-02.boeing.com [130.76.32.232]) by ietfa.amsl.com (Postfix) with ESMTP id E80241A010A for <int-area@ietf.org>; Tue, 18 Feb 2014 11:02:35 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id s1IJ2XbV008175; Tue, 18 Feb 2014 11:02:33 -0800
Received: from XCH-PHX-512.sw.nos.boeing.com (xch-phx-512.sw.nos.boeing.com [10.57.37.29]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id s1IJ2NYp008091 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Tue, 18 Feb 2014 11:02:23 -0800
Received: from XCH-BLV-201.nw.nos.boeing.com (10.57.37.66) by XCH-PHX-512.sw.nos.boeing.com (10.57.37.29) with Microsoft SMTP Server (TLS) id 14.3.174.1; Tue, 18 Feb 2014 11:02:22 -0800
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.102]) by XCH-BLV-201.nw.nos.boeing.com ([169.254.1.74]) with mapi id 14.03.0174.001; Tue, 18 Feb 2014 11:02:22 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Joe Touch <touch@isi.edu>
Thread-Topic: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
Thread-Index: AQHPLNqfZ6PoNhiMLkS+vK8jjU2/Npq7XQhQ
Date: Tue, 18 Feb 2014 19:02:21 +0000
Message-ID: <2134F8430051B64F815C691A62D983181D38BD@XCH-BLV-504.nw.nos.boeing.com>
References: <68a71d0317c546689875cfb7a1a67f9b@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983181D205B@XCH-BLV-504.nw.nos.boeing.com> <F3D91914-1A80-4CEC-96B9-99CF2BF0F64B@isi.edu> <2134F8430051B64F815C691A62D983181D35E5@XCH-BLV-504.nw.nos.boeing.com> <5303A1AD.9070904@isi.edu> <2134F8430051B64F815C691A62D983181D37B6@XCH-BLV-504.nw.nos.boeing.com> <5303A650.2050303@isi.edu> <2134F8430051B64F815C691A62D983181D3823@XCH-BLV-504.nw.nos.boeing.com> <5303AC03.2090008@isi.edu>
In-Reply-To: <5303AC03.2090008@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/FNCa5owqzSOsn8zCW-xYHAvzVmk
Cc: Ronald Bonica <rbonica@juniper.net>, "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2014 19:02:39 -0000

Hi Joe,

> -----Original Message-----
> From: Joe Touch [mailto:touch@isi.edu]
> Sent: Tuesday, February 18, 2014 10:53 AM
> To: Templin, Fred L
> Cc: Ronald Bonica; int-area@ietf.org
> Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-int=
area-gre-mtu-04.txt
>=20
>=20
>=20
> On 2/18/2014 10:44 AM, Templin, Fred L wrote:
> > Hi Joe,
> >
> >> -----Original Message-----
> >> From: Joe Touch [mailto:touch@isi.edu]
> >> Sent: Tuesday, February 18, 2014 10:29 AM
> >> To: Templin, Fred L
> >> Cc: Ronald Bonica; int-area@ietf.org
> >> Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-=
intarea-gre-mtu-04.txt
> >>
> >>
> >>
> >> On 2/18/2014 10:22 AM, Templin, Fred L wrote:
> >>> Hi Joe,
> >>>
> >>> I can see that I am going to have to write a draft on generic tunnel
> >>> fragmentation.
> >>
> >> That's already a section in the tunnel draft that has been a WG doc:
> >>
> >> http://tools.ietf.org/html/draft-ietf-intarea-tunnels-00#section-3.2
> >>
> >> That doc has languished for lack of feedback, but IMO that's the place
> >> to put all one-stop information on tunnels that transit IP packets.
> >
> > I can articulate one-stop generic text for tunnel fragmentation. Are
> > you suggesting reviving the above document?
>=20
> Yes; it already is supposed to be one-stop, generic text for all tunnel
> issues, and has a section on MTU issues already. Can you let us know
> what part of that needs to be fixed?

Sure, I will take a crack at this.

> >> I do agree that the current GRE doc could be more clear on this issue,
> >> but I don't think a new, separate doc on this is needed.
> >
> > Each tunnel type can certainly articulate its own fragmentation
> > scheme if it wants to - I have already done that for 6rd and AERO:
> >
> > https://datatracker.ietf.org/doc/draft-foo-v6ops-6rdmtu/
> > https://datatracker.ietf.org/doc/draft-templin-aerolink/
>=20
> The generic description should explain how and why the rules should
> vary. In that case, then specifics do belong in specific tunnel specs.

Yes, there will still be a place for specific tunnel specs, but
with heavy emphasis on the generic. The key is in the placement
of the tunnel egress and ingress in determining the specific
adaptations of the generic text to apply.

> > But, would be better if the individual docs could point to a
> > one-stop generic text and then just give 1-2 sentences on their
> > specific adaptation of the generic text. Would that work for you?
>=20
> Yes, but again that's already the purpose of the Intarea tunnel doc,
> which already has a lot of different discussions like this (ICMP signal
> relaying, MTU, etc.).

Do we have agreement that the Intarea tunnel doc would be
revived then (looks like it has been expired for a while now).

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

> Joe
>=20
>=20
>=20
> >
> > Thanks - Fred
> > fred.l.templin@boeing.com
> >
> >> Joe
> >>
> >>> It will be based on my e-mail from two messages ago.
> >>> I have already written drafts on 6rd tunnel fragmentation and AERO
> >>> tunnel fragmentation, and they are already consistent with the to-
> >>> be-written draft on generic tunnel fragmentation. Your draft on GRE
> >>> fragmentation can then also cite the generic tunnel fragmentation doc=
.
> >>>
> >>> Thanks - Fred
> >>> fred.l.templin@boeing.com
> >>>
> >>>> -----Original Message-----
> >>>> From: Joe Touch [mailto:touch@isi.edu]
> >>>> Sent: Tuesday, February 18, 2014 10:09 AM
> >>>> To: Templin, Fred L
> >>>> Cc: Ronald Bonica; int-area@ietf.org
> >>>> Subject: Re: [Int-area] FW: New Version Notification for draft-bonic=
a-intarea-gre-mtu-04.txt
> >>>>
> >>>>
> >>>>
> >>>> On 2/18/2014 9:27 AM, Templin, Fred L wrote:
> >>>>> Hi Joe,
> >>>>>
> >>>>> You seem to be talking past me - maybe it was because I wrote too m=
uch.
> >>>>> The fragmentation story for tunnels is very simple as follows:
> >>>>
> >>>> Yes, IMO they are, and here's mine:
> >>>>
> >>>> 	- if a tunnel CAN transit a packet, it MUST try
> >>>>
> >>>> 		i.e., the MTU of a tunnel that uses IPv6 encapsulation
> >>>> 		is 65535 - encapsulation headers
> >>>>
> >>>> 	- if a tunnel CANNOT transit a packet, it rejects it
> >>>>
> >>>> 		i.e., anything larger than "65535 - encap headers"
> >>>>
> >>>> Everything else mistakes MSS (maximum) for PSS (preferred). Preferre=
d is
> >>>> the min of the MSS's. An IPv6 tunnel limits MSS only insofar as pack=
ets
> >>>> larger than 65535-headers cannot traverse it.
> >>>>
> >>>> So...
> >>>>
> >>>>> 1) IPv6 has a minimum MTU of 1280 bytes. So, packets that are no la=
rger
> >>>>>       than this size MUST be accommodated even if a small amount of
> >>>>>       fragmentation is necessary. IPv4 has a much smaller minMTU, b=
ut
> >>>>>       IMHO tunnels SHOULD behave as if the IPv4 minMTU is also 1280=
.
> >>>>
> >>>> An IPv6 tunnel is a link to the IPv6 protocol. IPv6 requires that th=
e
> >>>> smallest MTU of all links must be no less than 1280. So agreed.
> >>>>
> >>>>> 2) Packets larger than 1500 bytes (with the exception of IPv4 packe=
ts
> >>>>>       with DF=3D0) should be allowed to sink or swim on their own. =
Tunnels
> >>>>>       therefore MUST NOT use fragmentation for packets larger than =
1500.
> >>>>
> >>>> Completely disagree. The max size of the payload of GRE in IPv6 is m=
uch
> >>>> larger than 1500.
> >>>>
> >>>> You're trying to do something at the tunnel layer that the path is
> >>>> supposed to be in control of.
> >>>>
> >>>>> 3) Packets larger than 1280 but no larger than 1500 are in a "gray =
area"
> >>>>>       where the way the tunnel accommodates them depends on the spe=
cific
> >>>>>       tunnel orientation. In some cases the tunnel should send as a=
 whole
> >>>>>       packet. In others, it should drop and send a PTB. In still ot=
hers,
> >>>>>       it should fragment. The cases are easy to articulate.
> >>>>
> >>>> There is no grey area. Until the max payload of an IPv6 packet is
> >>>> decreased, there's simply no justification to do other than the abov=
e.
> >>>>
> >>>>> That is really all there is to it. What is important to realize is
> >>>>> that case 3) needs to be architected according to the specific tunn=
el
> >>>>> orientation - there is no generic one-size-fits-all rule that can b=
e
> >>>>> applied to all tunnels in all orientations.
> >>>>
> >>>> First, if rules depend on orientations, then there would be no rule =
for
> >>>> tunnels at all. You cannot specify the requirements of a tunnel if i=
t
> >>>> depends on network placement - that rule does not exist for any othe=
r
> >>>> Internet component (excepting only endpoint vs. network, but that's
> >>>> function, not just placement).
> >>>>
> >>>> Second, there is a rule. See above.
> >>>>
> >>>> Joe
> >>>>
> >>>>
> >>>>>
> >>>>> Thanks - Fred
> >>>>> fred.l.templin@boeing.com
> >>>>>
> >>>>>
> >>>>>> -----Original Message-----
> >>>>>> From: Joe Touch [mailto:touch@isi.edu]
> >>>>>> Sent: Tuesday, February 18, 2014 8:47 AM
> >>>>>> To: Templin, Fred L
> >>>>>> Cc: Ronald Bonica; int-area@ietf.org
> >>>>>> Subject: Re: [Int-area] FW: New Version Notification for draft-bon=
ica-intarea-gre-mtu-04.txt
> >>>>>>
> >>>>>> Hi, Fred,
> >>>>>>
> >>>>>> On Feb 17, 2014, at 10:51 AM, Templin, Fred L <Fred.L.Templin@boei=
ng.com> wrote:
> >>>>>>
> >>>>>>> Hi Ron,
> >>>>>>>
> >>>>>>> The document needs to talk about packet sizes for IP payload pack=
ets.
> >>>>>>
> >>>>>> Yes, and I'm hoping we can add additional detail.
> >>>>>>
> >>>>>> Here's my view:
> >>>>>>
> >>>>>> -- path MTU is based on the min of the largest packet each link in=
 the path can support
> >>>>>>
> >>>>>> -- links often transit packets larger than their native size, e.g.=
, ATM's MTU is 9K, not 48
> bytes
> >>>>>>
> >>>>>> -- links do have a native transit size, though
> >>>>>>
> >>>>>> So there ought to be two very different concepts
> >>>>>>
> >>>>>> - MTU (maximum)
> >>>>>>
> >>>>>> - PTU (preferred)
> >>>>>>
> >>>>>> IMO, much of the confusion about how MTUs are handled by tunnels i=
s based on confusing MTU to
> >> mean
> >>>>>> PTU.
> >>>>>>
> >>>>>> I.e.,
> >>>>>>
> >>>>>> 	- a tunnel has a PTU based on avoiding ingress fragmentation
> >>>>>> 	and egress reassemly
> >>>>>>
> >>>>>> 	- a tunnel as a MTU, which is the MTU of the path of the tunnel
> >>>>>> 	minus the headers it adds at the ingress
> >>>>>>
> >>>>>>> For IP payload packets no larger than MINMTU bytes, the GRE tunne=
l
> >>>>>>> MUST accommodate the packet even if a small amount of fragmentati=
on
> >>>>>>> is necessary. (Here, the mandatory MINMTU for IPv6 is 1280 and th=
e
> >>>>>>> recommended MINMTU for IPv4 is also 1280.)
> >>>>>>
> >>>>>> This artificially limits tunnel MTU based on trying to support a p=
erceived PTU, but doesn't
> match
> >>>> PTU.
> >>>>>>
> >>>>>>> Beyond MINMTU, there needs to be a balance between avoiding path
> >>>>>>> MTU related black holes for the source and avoiding excessive
> >>>>>>> fragmentation at the GRE tunnel egress.
> >>>>>>
> >>>>>> If we really want to accomplish that, we need to flesh out the dif=
ference between MTU and PTU
> and
> >>>>>> teach our apps to focus on PTU, ala a new PLPTUD (vs. current PLMT=
UD).
> >>>>>>
> >>>>>> I don't think we should be guessing this at the time we specify th=
e tunnel, because the
> approach
> >>>>>> varies based on what's transited (real IP packets or some other so=
rt of encapsulation, e.g.,
> >> IPsec
> >>>> in
> >>>>>> UDP).
> >>>>>>
> >>>>>>
> >>>>>>> This balance is situation
> >>>>>>> dependent. For example, if the GRE tunnel ingress is located clos=
e
> >>>>>>> to the source, it should be reasonable to expect that the source
> >>>>>>> would be able to receive any ICMP PTB messages sent by the ingres=
s.
> >>>>>>
> >>>>>> Tunnels transit packets; they're not connected to sources or desti=
nations. So are you proposing
> >>>> that a
> >>>>>> tunnel should now try to discover the length of the path in each d=
irection and handle different
> >>>>>> addresses differently? IMO, that's worse than reassembly.
> >>>>>>
> >>>>>>> Or, if the GRE tunnel egress is located close to the destination,
> >>>>>>> it should be reasonable to expect that the egress can perform a
> >>>>>>> small amount of reassembly.
> >>>>>>
> >>>>>> Same problem, and worse- do you expect vendors to sell different t=
unnel engines based on
> intended
> >>>>>> traffic patterns?
> >>>>>>
> >>>>>> ----
> >>>>>>
> >>>>>> In conclusion, I would urge this document to focus on MTU as the g=
oal, at which point the only
> >>>> packets
> >>>>>> that ought to be dropped at the ingress ought to be those that can=
not be encapsulated with
> >> another
> >>>>>> IPv4 header, i.e., that exceed the *MAXIMUM* payload size.
> >>>>>>
> >>>>>> If we want to tune for preferred path size, we need to extend PLMT=
UD for that purpose.
> >>>>>>
> >>>>>> Joe


From nobody Tue Feb 18 11:02:49 2014
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DAEF1A050E for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 11:02:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8HK9bTAbr9Db for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 11:02:38 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id D990F1A03ED for <int-area@ietf.org>; Tue, 18 Feb 2014 11:02:38 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id s1IJ2JQ6004057 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 18 Feb 2014 11:02:19 -0800 (PST)
Message-ID: <5303AE3B.7010308@isi.edu>
Date: Tue, 18 Feb 2014 11:02:19 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Ronald Bonica <rbonica@juniper.net>, "Templin, Fred L" <Fred.L.Templin@boeing.com>
References: <68a71d0317c546689875cfb7a1a67f9b@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983181D205B@XCH-BLV-504.nw.nos.boeing.com> <F3D91914-1A80-4CEC-96B9-99CF2BF0F64B@isi.edu> <2134F8430051B64F815C691A62D983181D35E5@XCH-BLV-504 <5303A650.2050303@isi.edu> <d02b9aae44b44fdb8bb880f2cdd555cd@CO1PR05MB442.namprd05.prod.outlook.com>
In-Reply-To: <d02b9aae44b44fdb8bb880f2cdd555cd@CO1PR05MB442.namprd05.prod.outlook.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/2sLVm3zsLUSc-9ZbQ86g_Ze_rT4
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2014 19:02:40 -0000

On 2/18/2014 10:45 AM, Ronald Bonica wrote:
> Folks,
>
> I think that we are conflating two separate efforts.
>
> Draft-bonica-intarea-gre-mtu describes what is widely deployed
> today.

Understood, but it also out to explain how that corresponds to what 
should be done, referring to a generic doc to explain the details of 
what should be done.

> In today's, one of the following conditions frequently holds:
>
> - the operator of the GRE ingress knows that the GRE egress cannot
> reassemble fragments at the required rate
 >
> - the operator of the GRE ingress has no information regarding
> whether the GRE egress can reassemble fragments at the required rate
>
> Therefore, in draft-bonica, by default, the PTU is equal to the MTU.
> Fragmentation doesn't happen in the tunnel. However, in the exceptional
> case, where the operator of the ingress knows that the egress can
> reassemble at the required rate, fragmentation of the delivery packet is
> permitted.

Understood, but as Fred points out, that means that the GRE tunnel is 
non-compliant with IPv6 requirements. That needs to be discussed, even 
if we admit that this is current operation.

> The draft that Joe and Fred are considering

It's a draft that I and Mark Townsley already wrote. We started in 09 at 
the request of a few different ADs, as an effort to aggregate 
recommendations about how to tunnel IP packets, but it got virtually no 
discussion on the list.

FWIW, it's still in the INTAREA charter, and still a WG doc, even 
thought he current draft expired.

 > applies to environments
> where egress routers are commonly capable of reassembling at line rate.

All tunnels that cannot transit an IPv6 minimum MTU unfragmented MUST 
ingress fragment and egress reassemble. Otherwise you're noncompliant 
with IPv6, i.e., you're not a valid IPv6 link.

Any tunnel that uses IPv6 internally MUST therefore fragment/reassemble. 
Whether they can at line rate or not determines whether they're broken 
or not, not whether the spec has changed.

> Since this is a different environment, it should be addressed in a
> separate draft.

Neither of us is debating whether this should be a separate draft; every 
tunnel mechanism needs a distinct presentation. The issue is how much 
this doc should explain the issues and/or try to rationalize a 
noncompliant solution simply because it's deployed.

IMO, we ought to explain what it DOES, discuss whether it's compliant, 
and include what it would need to become compliant if not.

And refer to the tunnel draft for the details. That draft ought to be 
revived (I can easily resubmit) and we ought to wrap-up the 
recommendations in that doc and get it out the door (finally).

Joe


>
>                                                 Ron
>
>
> -----Original Message-----
> From: Joe Touch [mailto:touch@isi.edu]
> Sent: Tuesday, February 18, 2014 1:29 PM
> To: Templin, Fred L
> Cc: Ronald Bonica; int-area@ietf.org
> Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
>
>
>
> On 2/18/2014 10:22 AM, Templin, Fred L wrote:
>> Hi Joe,
>>
>> I can see that I am going to have to write a draft on generic tunnel
>> fragmentation.
>
> -
>


From nobody Tue Feb 18 11:15:44 2014
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D28C91A01B7 for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 11:15:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sU8v9PJKLHaI for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 11:15:39 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 9EED01A0150 for <int-area@ietf.org>; Tue, 18 Feb 2014 11:15:26 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id s1IJEnEG008123 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 18 Feb 2014 11:14:49 -0800 (PST)
Message-ID: <5303B129.8010706@isi.edu>
Date: Tue, 18 Feb 2014 11:14:49 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
References: <68a71d0317c546689875cfb7a1a67f9b@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983181D205B@XCH-BLV-504.nw.nos.boeing.com> <F3D91914-1A80-4CEC-96B9-99CF2BF0F64B@isi.edu> <2134F8430051B64F815C691A62D983181D35E5@XCH-BLV-504.nw.nos.boeing.com> <5303A1AD.9070904@isi.edu> <2134F8430051B64F815C691A62D983181D37B6@XCH-BLV-504.nw.nos.boeing.com> <5303A650.2050303@isi.edu> <2134F8430051B64F815C691A62D983181D3823@XCH-BLV-504.nw.nos.boeing.com> <5303AC03.2090008@isi.edu> <2134F8430051B64F815C691A62D983181D38BD@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D983181D38BD@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/gAeN1TCWkZhD--W1umVp-LSKHkw
Cc: Ronald Bonica <rbonica@juniper.net>, "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2014 19:15:41 -0000

On 2/18/2014 11:02 AM, Templin, Fred L wrote:
...
>> Yes, but again that's already the purpose of the Intarea tunnel doc,
>> which already has a lot of different discussions like this (ICMP signal
>> relaying, MTU, etc.).
>
> Do we have agreement that the Intarea tunnel doc would be
> revived then (looks like it has been expired for a while now).

IMO, yes. I think there has been a need for this doc for a while, but 
maybe the last few years the community has caught up and finally there's 
a clear need rather than seeing this as merely proactive.

Joe


From nobody Tue Feb 18 11:32:12 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74CE71A04CB for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 11:32:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L99zQt_5AteJ for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 11:32:07 -0800 (PST)
Received: from mail-pb0-x231.google.com (mail-pb0-x231.google.com [IPv6:2607:f8b0:400e:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id 4F76C1A0226 for <int-area@ietf.org>; Tue, 18 Feb 2014 11:32:07 -0800 (PST)
Received: by mail-pb0-f49.google.com with SMTP id up15so17093827pbc.22 for <int-area@ietf.org>; Tue, 18 Feb 2014 11:32:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=zE9MZpmfj2tYldmgYrrUSX8U8gQ5OiAJzwafeGwlbdw=; b=MuqVivRpyyk9sl3BsBcNyBOMAfu8+yGwIWkrbUvAXtvXOaqopoKSD/s3eNoSbMMP1E lR7YR8AN8Y/SOtTKYIdEbs4FiFLsbhtz+F2nyQZ7YZkBAQDKKhsYPu6rsr/j3RcCrQ97 p5KU5REaggh4/T7kM5zzcc666AQd6zvj10vgxvdqddK8s9CaNjXc+We8bDKm/UXl7U6m 6M+9I9fdkLfC5VJAcWdro2g3qRZWjzva5CZuXSRScFEKXpcXIIhvGM3xES/b6rMPg9rL R6Ky7Y7+TJzFy4vXSPZIc+8Lm8+kgKKOV9UzvxkJVA1T4eDzpOE6sRraCibfgvzgdrSa Mebg==
X-Received: by 10.68.204.161 with SMTP id kz1mr12042079pbc.156.1392751924438;  Tue, 18 Feb 2014 11:32:04 -0800 (PST)
Received: from [192.168.178.23] (200.192.69.111.dynamic.snap.net.nz. [111.69.192.200]) by mx.google.com with ESMTPSA id lh13sm148582233pab.4.2014.02.18.11.32.02 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 18 Feb 2014 11:32:03 -0800 (PST)
Message-ID: <5303B537.7080504@gmail.com>
Date: Wed, 19 Feb 2014 08:32:07 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: meng.wei2@zte.com.cn
References: <OF1DD91406.05BE610A-ON48257C83.0024E099-48257C83.00281864@zte.com.cn>
In-Reply-To: <OF1DD91406.05BE610A-ON48257C83.0024E099-48257C83.00281864@zte.com.cn>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/n1bNi5g_BGBc80dZGz1WqFZcobc
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] [intarea]Comments on draft-cui-intarea-unified-v6-framework-00
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2014 19:32:09 -0000

On 18/02/2014 20:15, meng.wei2@zte.com.cn wrote:
...
> "Yuchi Chen" <chenycmx@gmail.com> 2014-02-18 12:39:34:
...
>> [yuchi] Yes, switch should forward the inital packet of each of 
>> unknown flows to controller. I agree that 
>> it indeed may lead to congestion if there are too many new flows 
>> concurrently passing through switch. 

That sounds like an ideal and simple target for a DDOS attack.

   Brian


From nobody Tue Feb 18 18:53:55 2014
Return-Path: <cpignata@cisco.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F7A91A054A for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 18:53:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.049
X-Spam-Level: 
X-Spam-Status: No, score=-15.049 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0E6EllC5tGuY for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 18:53:50 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 9BC1F1A042B for <int-area@ietf.org>; Tue, 18 Feb 2014 18:53:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8959; q=dns/txt; s=iport; t=1392778428; x=1393988028; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=AAQq4aNfUFkRbDC0xthYYXgNuZyey5jePNkmv9P/JZY=; b=LwuHba55xz0uJqX1skNPO3TjQ+sHXIG3WklntFHNjMIyz967mabsE0Fp 2FTlM+i8giPgAm6w7kDPTz99EZwjPJhff1sqDpj7Dx0pL62tWzYIBL0zT +/HLxJhjngmfGaEOU6QZj0012zW2PynzJPlTOKGUwwf3omuYl+OQcuMBt A=;
X-Files: signature.asc : 203
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFALUbBFOtJV2Z/2dsb2JhbABZDoJ6OFW9GIEjFgF0g30BAQEDAQEBAQtXCQkCBQcEAgEIEQQBAQEnBycLFAkIAgQOBQ4Lh2MIDcRZEwSOMBEBJSsHBoMdgRMEkDOBMYYykhSCbD+BcTk
X-IronPort-AV: E=Sophos;i="4.97,863,1389744000";  d="asc'?scan'208";a="301938834"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-9.cisco.com with ESMTP; 19 Feb 2014 02:53:47 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s1J2rlgQ005617 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 19 Feb 2014 02:53:47 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.205]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.03.0123.003; Tue, 18 Feb 2014 20:53:46 -0600
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: Joe Touch <touch@isi.edu>
Thread-Topic: [Int-area] New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
Thread-Index: AQHPLR3OeY+namAN5U6dK0IqnxWO+w==
Date: Wed, 19 Feb 2014 02:53:46 +0000
Message-ID: <5EAA1AB8-EF82-468F-9E61-DDFF78762753@cisco.com>
References: <68a71d0317c546689875cfb7a1a67f9b@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983181D205B@XCH-BLV-504.nw.nos.boeing.com> <F3D91914-1A80-4CEC-96B9-99CF2BF0F64B@isi.edu> <2134F8430051B64F815C691A62D983181D35E5@XCH-BLV-504.nw.nos.boeing.com> <5303A1AD.9070904@isi.edu>
In-Reply-To: <5303A1AD.9070904@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.251.183]
Content-Type: multipart/signed; boundary="Apple-Mail=_83B2A243-E5C7-49BD-94D7-3269D85992B1"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/R2FmsOjzWxfG0lFAOTVa_7Ibf54
Cc: "Ronald P. Bonica" <rbonica@juniper.net>, "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2014 02:53:53 -0000

--Apple-Mail=_83B2A243-E5C7-49BD-94D7-3269D85992B1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Joe,

On Feb 18, 2014, at 1:08 PM, Joe Touch <touch@isi.edu> wrote:

>=20
>=20
> On 2/18/2014 9:27 AM, Templin, Fred L wrote:
>> Hi Joe,
>>=20
>> You seem to be talking past me - maybe it was because I wrote too =
much.
>> The fragmentation story for tunnels is very simple as follows:
>=20
> Yes, IMO they are, and here's mine:
>=20
> 	- if a tunnel CAN transit a packet, it MUST try
>=20
> 		i.e., the MTU of a tunnel that uses IPv6 encapsulation
> 		is 65535 - encapsulation headers
>=20

Where is this specified (other than stated by you in your email with =
2119 language)? This defeats the purpose of a configurable MTU, and =
frankly shows requirements that do not exist and are not met in real =
life.

Take for example RFC 1812, Section 3.3.4., "MTU":

   The MTU of each logical interface MUST be configurable within the
   range of legal MTUs for the interface.

   Many Link Layer protocols define a maximum frame size that may be
   sent.  In such cases, a router MUST NOT allow an MTU to be set which
   would allow sending of frames larger than those allowed by the Link
   Layer protocol.  However, a router SHOULD be willing to receive a
   packet as large as the maximum frame size even if that is larger than
   the MTU.

   DISCUSSION
...

Apologies as I have said the following on this list more than once, but =
to reiterate: if you consider a tunnel as a logical link, the "link max =
frame size" is 64k - tunnel encap. But that does *not* mean that's the =
MTU, nor that packets larger than the tunnel MTU need to be fragmented =
after encap because they fit this max link size.

If the MTU is configured on an ethernet link to be 500 B, but the =
physical media can (capable) send larger sizes, what happens with a =
1000B packet?


> 	- if a tunnel CANNOT transit a packet, it rejects it
>=20
> 		i.e., anything larger than "65535 - encap headers"
>=20
> Everything else mistakes MSS (maximum) for PSS (preferred). Preferred =
is the min of the MSS's. An IPv6 tunnel limits MSS only insofar as =
packets larger than 65535-headers cannot traverse it.
>=20

Similarly, where is "preferred" specified? And these are segment sizes =
and not MTUs?

Thanks,

-- Carlos.

> So...
>=20
>> 1) IPv6 has a minimum MTU of 1280 bytes. So, packets that are no =
larger
>>    than this size MUST be accommodated even if a small amount of
>>    fragmentation is necessary. IPv4 has a much smaller minMTU, but
>>    IMHO tunnels SHOULD behave as if the IPv4 minMTU is also 1280.
>=20
> An IPv6 tunnel is a link to the IPv6 protocol. IPv6 requires that the =
smallest MTU of all links must be no less than 1280. So agreed.
>=20
>> 2) Packets larger than 1500 bytes (with the exception of IPv4 packets
>>    with DF=3D0) should be allowed to sink or swim on their own. =
Tunnels
>>    therefore MUST NOT use fragmentation for packets larger than 1500.
>=20
> Completely disagree. The max size of the payload of GRE in IPv6 is =
much larger than 1500.
>=20
> You're trying to do something at the tunnel layer that the path is =
supposed to be in control of.
>=20
>> 3) Packets larger than 1280 but no larger than 1500 are in a "gray =
area"
>>    where the way the tunnel accommodates them depends on the specific
>>    tunnel orientation. In some cases the tunnel should send as a =
whole
>>    packet. In others, it should drop and send a PTB. In still others,
>>    it should fragment. The cases are easy to articulate.
>=20
> There is no grey area. Until the max payload of an IPv6 packet is =
decreased, there's simply no justification to do other than the above.
>=20
>> That is really all there is to it. What is important to realize is
>> that case 3) needs to be architected according to the specific tunnel
>> orientation - there is no generic one-size-fits-all rule that can be
>> applied to all tunnels in all orientations.
>=20
> First, if rules depend on orientations, then there would be no rule =
for tunnels at all. You cannot specify the requirements of a tunnel if =
it depends on network placement - that rule does not exist for any other =
Internet component (excepting only endpoint vs. network, but that's =
function, not just placement).
>=20
> Second, there is a rule. See above.
>=20
> Joe
>=20
>=20
>>=20
>> Thanks - Fred
>> fred.l.templin@boeing.com
>>=20
>>=20
>>> -----Original Message-----
>>> From: Joe Touch [mailto:touch@isi.edu]
>>> Sent: Tuesday, February 18, 2014 8:47 AM
>>> To: Templin, Fred L
>>> Cc: Ronald Bonica; int-area@ietf.org
>>> Subject: Re: [Int-area] FW: New Version Notification for =
draft-bonica-intarea-gre-mtu-04.txt
>>>=20
>>> Hi, Fred,
>>>=20
>>> On Feb 17, 2014, at 10:51 AM, Templin, Fred L =
<Fred.L.Templin@boeing.com> wrote:
>>>=20
>>>> Hi Ron,
>>>>=20
>>>> The document needs to talk about packet sizes for IP payload =
packets.
>>>=20
>>> Yes, and I'm hoping we can add additional detail.
>>>=20
>>> Here's my view:
>>>=20
>>> -- path MTU is based on the min of the largest packet each link in =
the path can support
>>>=20
>>> -- links often transit packets larger than their native size, e.g., =
ATM's MTU is 9K, not 48 bytes
>>>=20
>>> -- links do have a native transit size, though
>>>=20
>>> So there ought to be two very different concepts
>>>=20
>>> - MTU (maximum)
>>>=20
>>> - PTU (preferred)
>>>=20
>>> IMO, much of the confusion about how MTUs are handled by tunnels is =
based on confusing MTU to mean
>>> PTU.
>>>=20
>>> I.e.,
>>>=20
>>> 	- a tunnel has a PTU based on avoiding ingress fragmentation
>>> 	and egress reassemly
>>>=20
>>> 	- a tunnel as a MTU, which is the MTU of the path of the tunnel
>>> 	minus the headers it adds at the ingress
>>>=20
>>>> For IP payload packets no larger than MINMTU bytes, the GRE tunnel
>>>> MUST accommodate the packet even if a small amount of fragmentation
>>>> is necessary. (Here, the mandatory MINMTU for IPv6 is 1280 and the
>>>> recommended MINMTU for IPv4 is also 1280.)
>>>=20
>>> This artificially limits tunnel MTU based on trying to support a =
perceived PTU, but doesn't match PTU.
>>>=20
>>>> Beyond MINMTU, there needs to be a balance between avoiding path
>>>> MTU related black holes for the source and avoiding excessive
>>>> fragmentation at the GRE tunnel egress.
>>>=20
>>> If we really want to accomplish that, we need to flesh out the =
difference between MTU and PTU and
>>> teach our apps to focus on PTU, ala a new PLPTUD (vs. current =
PLMTUD).
>>>=20
>>> I don't think we should be guessing this at the time we specify the =
tunnel, because the approach
>>> varies based on what's transited (real IP packets or some other sort =
of encapsulation, e.g., IPsec in
>>> UDP).
>>>=20
>>>=20
>>>> This balance is situation
>>>> dependent. For example, if the GRE tunnel ingress is located close
>>>> to the source, it should be reasonable to expect that the source
>>>> would be able to receive any ICMP PTB messages sent by the ingress.
>>>=20
>>> Tunnels transit packets; they're not connected to sources or =
destinations. So are you proposing that a
>>> tunnel should now try to discover the length of the path in each =
direction and handle different
>>> addresses differently? IMO, that's worse than reassembly.
>>>=20
>>>> Or, if the GRE tunnel egress is located close to the destination,
>>>> it should be reasonable to expect that the egress can perform a
>>>> small amount of reassembly.
>>>=20
>>> Same problem, and worse- do you expect vendors to sell different =
tunnel engines based on intended
>>> traffic patterns?
>>>=20
>>> ----
>>>=20
>>> In conclusion, I would urge this document to focus on MTU as the =
goal, at which point the only packets
>>> that ought to be dropped at the ingress ought to be those that =
cannot be encapsulated with another
>>> IPv4 header, i.e., that exceed the *MAXIMUM* payload size.
>>>=20
>>> If we want to tune for preferred path size, we need to extend PLMTUD =
for that purpose.
>>>=20
>>> Joe
>=20
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area


--Apple-Mail=_83B2A243-E5C7-49BD-94D7-3269D85992B1
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlMEHLkACgkQtfDPGTp3USy3NgCfa1IwmXwuBgHhYHFopQ6xKvu1
ZQkAniWbnlzoLbXULFuMPA7Bf3OETiYH
=JFBB
-----END PGP SIGNATURE-----

--Apple-Mail=_83B2A243-E5C7-49BD-94D7-3269D85992B1--


From nobody Tue Feb 18 18:54:40 2014
Return-Path: <cpignata@cisco.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A334F1A01A0 for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 18:54:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.049
X-Spam-Level: 
X-Spam-Status: No, score=-10.049 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qvD6SgkGUpIV for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 18:54:38 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) by ietfa.amsl.com (Postfix) with ESMTP id F03761A042B for <int-area@ietf.org>; Tue, 18 Feb 2014 18:54:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2526; q=dns/txt; s=iport; t=1392778475; x=1393988075; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=dWhHUUpTwKhiwsGBfhd+mx1kN1ESGbobO9CIo6U8I3g=; b=d4C0+85LJfHWJspW2NoWLJtfSlRc3/uYvKQTPCe+90Q1NoQXKjQNH+Wo Wwd2ngY9jvZ/kZMlRmIdG1LAgUj+qhVe52Q4Fln+dEkhZBGJcFrZ4u1xu m2qZyYZknDIBp9NLVtDr89BeTwSXbEY4S+INMyQ2avH4grGdcyXdRCAxa s=;
X-Files: signature.asc : 203
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag0FACAcBFOtJV2b/2dsb2JhbABZgwY4V8BCgSIWdIIlAQEBAwEBAQFrCQIFBwQCAQgRBAEBAScHJwsUCQgCBA4FDodvCA3MURMEjmQHBoMegRQBA5BBgTOGPJIkgy2CKg
X-IronPort-AV: E=Sophos;i="4.97,503,1389744000";  d="asc'?scan'208";a="21449826"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-3.cisco.com with ESMTP; 19 Feb 2014 02:54:34 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s1J2sYv7004418 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 19 Feb 2014 02:54:34 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.205]) by xhc-rcd-x04.cisco.com ([::1]) with mapi id 14.03.0123.003; Tue, 18 Feb 2014 20:54:34 -0600
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: "Ronald P. Bonica" <rbonica@juniper.net>
Thread-Topic: [Int-area] New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
Thread-Index: AQHPLR3q3kItucEm4UOqhK0w6UfOJA==
Date: Wed, 19 Feb 2014 02:54:33 +0000
Message-ID: <46F7B2EF-DA23-4EAF-9163-2014749451E5@cisco.com>
References: <68a71d0317c546689875cfb7a1a67f9b@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983181D205B@XCH-BLV-504.nw.nos.boeing.com> <F3D91914-1A80-4CEC-96B9-99CF2BF0F64B@isi.edu> <2134F8430051B64F815C691A62D983181D35E5@XCH-BLV-504 <5303A650.2050303@isi.edu> <d02b9aae44b44fdb8bb880f2cdd555cd@CO1PR05MB442.namprd05.prod.outlook.com>
In-Reply-To: <d02b9aae44b44fdb8bb880f2cdd555cd@CO1PR05MB442.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.251.183]
Content-Type: multipart/signed; boundary="Apple-Mail=_CC3160C7-467C-4F99-A839-C7F3D3CB3451"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/Q-NZvAvD0nITMEO7Vjo7rPX6SRU
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2014 02:54:39 -0000

--Apple-Mail=_CC3160C7-467C-4F99-A839-C7F3D3CB3451
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

+1.

Thanks,

-- Carlos.

On Feb 18, 2014, at 1:45 PM, Ronald Bonica <rbonica@juniper.net> wrote:

> Folks,
>=20
> I think that we are conflating two separate efforts.
>=20
> Draft-bonica-intarea-gre-mtu describes what is widely deployed today. =
In today's, one of the following conditions frequently holds:
>=20
> - the operator of the GRE ingress knows that the GRE egress cannot =
reassemble fragments at the required rate
> - the operator of the GRE ingress has no information regarding whether =
the GRE egress can reassemble fragments at the required rate
>=20
> Therefore, in draft-bonica, by default, the PTU is equal to the MTU. =
Fragmentation doesn't happen in the tunnel. However, in the exceptional =
case, where the operator of the ingress knows that the egress can =
reassemble at the required rate, fragmentation of the delivery packet is =
permitted.
>=20
> The draft that Joe and Fred are considering applies to environments =
where egress routers are commonly capable of reassembling at line rate. =
Since this is a different environment, it should be addressed in a =
separate draft.
>=20
>                                               Ron
>=20
>=20
> -----Original Message-----
> From: Joe Touch [mailto:touch@isi.edu]=20
> Sent: Tuesday, February 18, 2014 1:29 PM
> To: Templin, Fred L
> Cc: Ronald Bonica; int-area@ietf.org
> Subject: Re: [Int-area] FW: New Version Notification for =
draft-bonica-intarea-gre-mtu-04.txt
>=20
>=20
>=20
> On 2/18/2014 10:22 AM, Templin, Fred L wrote:
>> Hi Joe,
>>=20
>> I can see that I am going to have to write a draft on generic tunnel=20=

>> fragmentation.
>=20
> -=20
>=20
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area


--Apple-Mail=_CC3160C7-467C-4F99-A839-C7F3D3CB3451
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlMEHOgACgkQtfDPGTp3USwddgCg1vJNN72cab/s4NLDm2wWcpvo
Ly0AnjaecaK0UnAC4Atb/UROwwKv9X0f
=DZBE
-----END PGP SIGNATURE-----

--Apple-Mail=_CC3160C7-467C-4F99-A839-C7F3D3CB3451--


From nobody Tue Feb 18 23:32:50 2014
Return-Path: <chenycmx@gmail.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE9C01A042D for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 23:32:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level: 
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLYTO=1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oZDPqL49NsPE for <int-area@ietfa.amsl.com>; Tue, 18 Feb 2014 23:32:44 -0800 (PST)
Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id D32241A0366 for <int-area@ietf.org>; Tue, 18 Feb 2014 23:32:44 -0800 (PST)
Received: by mail-pa0-f52.google.com with SMTP id bj1so19246pad.25 for <int-area@ietf.org>; Tue, 18 Feb 2014 23:32:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=date:from:to:cc:reply-to:subject:references:mime-version:message-id :content-type; bh=Zpfih0b0yzEL8xRPu1zTzDGdKkoT/cxsZGmzpbClSis=; b=VtmQTopQAhMXNdZF/Jb9UKM2Ftm7pFrhcUdHCXRPem0Xtvj8ytL3yOIZu3jfZblC6Y O37ZBl3BQktY7cn0XkDSbTpcCpiUV/dLrTJxITU0Ip5+nNLaa6ix746EW12iQGrsGiow 6PaCy69bq/0yu+I+GBREC2hWrFN7l8H+GuT7dDxFUbOlcQGfYfGy6Z1JNdH2RcI03rJb xUR4FAnoYiJVQcadHGwFwSmQa6h0Wl/Cc9nzPCuF/2NoMrMR/UvCwtfvyLwDo6Z7RpMH aXVPER5WP/8O4hNyCU4YxHJtxxy5jLmV8tBnpD9epXf+nKnjRVq73iqu/IJUlMbUaPNK 6Aeg==
X-Received: by 10.68.125.164 with SMTP id mr4mr37823004pbb.27.1392795160755; Tue, 18 Feb 2014 23:32:40 -0800 (PST)
Received: from netlab-PC ([166.111.68.231]) by mx.google.com with ESMTPSA id y9sm159842069pas.10.2014.02.18.23.32.36 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 18 Feb 2014 23:32:39 -0800 (PST)
Date: Wed, 19 Feb 2014 15:32:37 +0800
From: "Yuchi Chen" <chenycmx@gmail.com>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>,  meng.wei2 <meng.wei2@zte.com.cn>
References: <OF1DD91406.05BE610A-ON48257C83.0024E099-48257C83.00281864@zte.com.cn>,  <5303B537.7080504@gmail.com>
X-Priority: 3
X-GUID: 3CE92E18-5A87-4DCD-B868-28239F6E5BFE
X-Has-Attach: no
X-Mailer: Foxmail 7.0.1.92[cn]
Mime-Version: 1.0
Message-ID: <2014021915323402655631@gmail.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart187865723072_=----"
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/V0F55TWwEtj2d6CCExXi0-mt51Q
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] [intarea]Comments on draft-cui-intarea-unified-v6-framework-00
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: chenycmx <chenycmx@gmail.com>
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2014 07:32:48 -0000

This is a multi-part message in MIME format.

------=_001_NextPart187865723072_=----
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

SGkgQnJpYW4sDQoNClRoYW5rIHlvdSBmb3IgcmFpc2luZyB1cCB0aGlzIHBvaW50LiBJTUhPIHNv
bWUgZXhpc3RpbmcgbW9uaXRvcmluZyBvciBmaWx0ZXJpbmcgYXBwcm9hY2hlcyBzaG91bGQgYmUg
YWRvcHRlZCB0byBwcmV2ZW50IGFnYWluc3QgdGhlc2UgYXR0YWNrcy4gV2Ugd2lsbCBpbmNsdWRl
IHRoZXNlIGNvbnNpZGVyYXRpb25zIGluIHRoZSBuZXh0IHZlcnNpb24uDQoNCkluIGdlbmVyYWws
IEkgYmVsaWV2ZSB0aGF0IHRoaXMgd29yayB3aWxsIGJlIG9mIGJlbmVmaXRzLCB0aG91Z2ggaXQg
c3RpbGwgbmVlZHMgdG8gYmUgaW1wcm92ZWQuIEl0IHdpbGwgYmUgZ3JlYXRseSBhcHByZWNpYXRl
ZCBpZiB3ZSBjYW4gcmVjZWl2ZSBtb3JlIGNvbW1lbnRzIGZyb20gdGhlIFdHLiANCg0KQmVzdCBy
ZWdhcmRzIQ0KDQoNCg0KWXVjaGkgQ2hlbg0KDQpGcm9tOiBCcmlhbiBFIENhcnBlbnRlcg0KRGF0
ZTogMjAxNC0wMi0xOSAwMzozMg0KVG86IG1lbmcud2VpMg0KQ0M6IGNoZW55Y214OyBpbnQtYXJl
YUBpZXRmLm9yZw0KU3ViamVjdDogUmU6IFtJbnQtYXJlYV0gW2ludGFyZWFdQ29tbWVudHMgb24g
ZHJhZnQtY3VpLWludGFyZWEtdW5pZmllZC12Ni1mcmFtZXdvcmstMDANCk9uIDE4LzAyLzIwMTQg
MjA6MTUsIG1lbmcud2VpMkB6dGUuY29tLmNuIHdyb3RlOg0KLi4uDQo+ICJZdWNoaSBDaGVuIiA8
Y2hlbnljbXhAZ21haWwuY29tPiAyMDE0LTAyLTE4IDEyOjM5OjM0Og0KLi4uDQo+PiBbeXVjaGld
IFllcywgc3dpdGNoIHNob3VsZCBmb3J3YXJkIHRoZSBpbml0YWwgcGFja2V0IG9mIGVhY2ggb2Yg
DQo+PiB1bmtub3duIGZsb3dzIHRvIGNvbnRyb2xsZXIuIEkgYWdyZWUgdGhhdCANCj4+IGl0IGlu
ZGVlZCBtYXkgbGVhZCB0byBjb25nZXN0aW9uIGlmIHRoZXJlIGFyZSB0b28gbWFueSBuZXcgZmxv
d3MgDQo+PiBjb25jdXJyZW50bHkgcGFzc2luZyB0aHJvdWdoIHN3aXRjaC4gDQoNClRoYXQgc291
bmRzIGxpa2UgYW4gaWRlYWwgYW5kIHNpbXBsZSB0YXJnZXQgZm9yIGEgRERPUyBhdHRhY2suDQoN
CiAgIEJyaWFu

------=_001_NextPart187865723072_=----
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dutf-8" http-equiv=3DContent-Type>
<STYLE>
BLOCKQUOTE {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em
}
OL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
UL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
BODY {
	LINE-HEIGHT: 1.5; FONT-FAMILY: =E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91; COLO=
R: #000080; FONT-SIZE: 10.5pt
}
</STYLE>

<META name=3DGENERATOR content=3D"MSHTML 8.00.7601.17514"></HEAD>
<BODY style=3D"MARGIN: 10px">
<DIV>Hi Brian,</DIV>
<DIV>&nbsp;</DIV>
<DIV>Thank you&nbsp;for raising up this point.&nbsp;IMHO&nbsp;some existin=
g=20
monitoring or filtering approaches should be adopted to prevent against th=
ese=20
attacks. We&nbsp;will&nbsp;include these considerations in the next=20
version.</DIV>
<DIV>&nbsp;</DIV>
<DIV>In general, I believe that this work will be of benefits, though it s=
till=20
needs to be improved. It will be greatly appreciated if we can receive mor=
e=20
comments from the WG. </DIV>
<DIV>&nbsp;</DIV>
<DIV>Best regards!</DIV>
<HR style=3D"WIDTH: 210px; HEIGHT: 1px" align=3Dleft color=3D#b5c4df SIZE=
=3D1>

<DIV><SPAN><SPAN=20
style=3D"FONT-FAMILY: =E5=AE=8B=E4=BD=93; COLOR: #000000; FONT-SIZE: 10.5p=
t">Yuchi=20
Chen</SPAN></SPAN></DIV>
<DIV>&nbsp;</DIV>
<DIV=20
style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOT=
TOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt s=
olid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<DIV=20
style=3D"PADDING-BOTTOM: 8px; PADDING-LEFT: 8px; PADDING-RIGHT: 8px; BACKG=
ROUND: #efefef; COLOR: #000000; FONT-SIZE: 12px; PADDING-TOP: 8px">
<DIV><B>From:</B>&nbsp;<A href=3D"mailto:brian.e.carpenter@gmail.com">Bria=
n E=20
Carpenter</A></DIV>
<DIV><B>Date:</B>&nbsp;2014-02-19&nbsp;03:32</DIV>
<DIV><B>To:</B>&nbsp;<A href=3D"mailto:meng.wei2@zte.com.cn">meng.wei2</A>=
</DIV>
<DIV><B>CC:</B>&nbsp;<A href=3D"mailto:chenycmx@gmail.com">chenycmx</A>; <=
A=20
href=3D"mailto:int-area@ietf.org">int-area@ietf.org</A></DIV>
<DIV><B>Subject:</B>&nbsp;Re: [Int-area] [intarea]Comments on=20
draft-cui-intarea-unified-v6-framework-00</DIV></DIV></DIV>
<DIV>
<DIV>On&nbsp;18/02/2014&nbsp;20:15,&nbsp;meng.wei2@zte.com.cn&nbsp;wrote:<=
/DIV>
<DIV>...</DIV>
<DIV>&gt;&nbsp;"Yuchi&nbsp;Chen"&nbsp;&lt;chenycmx@gmail.com&gt;&nbsp;2014=
-02-18&nbsp;12:39:34:</DIV>
<DIV>...</DIV>
<DIV>&gt;&gt;&nbsp;[yuchi]&nbsp;Yes,&nbsp;switch&nbsp;should&nbsp;forward&=
nbsp;the&nbsp;inital&nbsp;packet&nbsp;of&nbsp;each&nbsp;of&nbsp;</DIV>
<DIV>&gt;&gt;&nbsp;unknown&nbsp;flows&nbsp;to&nbsp;controller.&nbsp;I&nbsp=
;agree&nbsp;that&nbsp;</DIV>
<DIV>&gt;&gt;&nbsp;it&nbsp;indeed&nbsp;may&nbsp;lead&nbsp;to&nbsp;congesti=
on&nbsp;if&nbsp;there&nbsp;are&nbsp;too&nbsp;many&nbsp;new&nbsp;flows&nbsp=
;</DIV>
<DIV>&gt;&gt;&nbsp;concurrently&nbsp;passing&nbsp;through&nbsp;switch.&nbs=
p;</DIV>
<DIV>&nbsp;</DIV>
<DIV>That&nbsp;sounds&nbsp;like&nbsp;an&nbsp;ideal&nbsp;and&nbsp;simple&nb=
sp;target&nbsp;for&nbsp;a&nbsp;DDOS&nbsp;attack.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp;&nbsp;Brian</DIV></DIV></BODY></HTML>

------=_001_NextPart187865723072_=------


From nobody Wed Feb 19 08:06:11 2014
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A034B1A04FD for <int-area@ietfa.amsl.com>; Wed, 19 Feb 2014 08:06:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.749
X-Spam-Level: 
X-Spam-Status: No, score=-4.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9GZboKsDJ8iB for <int-area@ietfa.amsl.com>; Wed, 19 Feb 2014 08:06:06 -0800 (PST)
Received: from blv-mbsout-01.boeing.com (blv-mbsout-01.boeing.com [130.76.32.231]) by ietfa.amsl.com (Postfix) with ESMTP id 2987F1A04DB for <int-area@ietf.org>; Wed, 19 Feb 2014 08:06:06 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id s1JG62r3026625; Wed, 19 Feb 2014 08:06:02 -0800
Received: from XCH-PHX-209.sw.nos.boeing.com (xch-phx-209.sw.nos.boeing.com [130.247.25.29]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id s1JG5wSl026574 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Wed, 19 Feb 2014 08:05:58 -0800
Received: from XCH-BLV-405.nw.nos.boeing.com (2002:82f7:199e::82f7:199e) by XCH-PHX-209.sw.nos.boeing.com (2002:82f7:191d::82f7:191d) with Microsoft SMTP Server (TLS) id 14.3.174.1; Wed, 19 Feb 2014 08:05:58 -0800
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.102]) by XCH-BLV-405.nw.nos.boeing.com ([169.254.5.253]) with mapi id 14.03.0174.001; Wed, 19 Feb 2014 08:05:58 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ronald Bonica <rbonica@juniper.net>, Joe Touch <touch@isi.edu>
Thread-Topic: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
Thread-Index: AQHPLMlCZ6PoNhiMLkS+vK8jjU2/Npq7Q7aAgAALpICAAAPXAIAAAbAAgAAAjjCAAWg84A==
Date: Wed, 19 Feb 2014 16:05:57 +0000
Message-ID: <2134F8430051B64F815C691A62D983181D46AF@XCH-BLV-504.nw.nos.boeing.com>
References: <68a71d0317c546689875cfb7a1a67f9b@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983181D205B@XCH-BLV-504.nw.nos.boeing.com> <F3D91914-1A80-4CEC-96B9-99CF2BF0F64B@isi.edu> <2134F8430051B64F815C691A62D983181D35E5@XCH-BLV-504 <5303A650.2050303@isi.edu> <d02b9aae44b44fdb8bb880f2cdd555cd@CO1PR05MB442.namprd05.prod.outlook.com>
In-Reply-To: <d02b9aae44b44fdb8bb880f2cdd555cd@CO1PR05MB442.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/OtbFTXPGmRgwnEbu44jwR0mHT3o
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2014 16:06:07 -0000

Hi Ron,

> The draft that Joe and Fred are considering applies to environments where=
 egress routers are commonly
> capable of reassembling at line rate. Since this is a different environme=
nt, it should be addressed in
> a separate draft.

No, that is not correct - the draft we are considering accounts for all
environments in which tunnel ingresses and egresses may be deployed.

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


From nobody Wed Feb 19 08:16:20 2014
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC34D1A0249 for <int-area@ietfa.amsl.com>; Wed, 19 Feb 2014 08:16:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3IhPveRGtYhx for <int-area@ietfa.amsl.com>; Wed, 19 Feb 2014 08:16:15 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 935F51A021B for <int-area@ietf.org>; Wed, 19 Feb 2014 08:16:15 -0800 (PST)
Received: from [192.168.1.93] (pool-71-105-87-112.lsanca.dsl-w.verizon.net [71.105.87.112]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id s1JGF80e018166 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 19 Feb 2014 08:15:11 -0800 (PST)
Message-ID: <5304D88D.4030307@isi.edu>
Date: Wed, 19 Feb 2014 08:15:09 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
References: <68a71d0317c546689875cfb7a1a67f9b@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983181D205B@XCH-BLV-504.nw.nos.boeing.com> <F3D91914-1A80-4CEC-96B9-99CF2BF0F64B@isi.edu> <2134F8430051B64F815C691A62D983181D35E5@XCH-BLV-504.nw.nos.boeing.com> <5303A1AD.9070904@isi.edu> <5EAA1AB8-EF82-468F-9E61-DDFF78762753@cisco.com>
In-Reply-To: <5EAA1AB8-EF82-468F-9E61-DDFF78762753@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/sNY4GAhxDYdTkF8JBXi4WkDDxHY
Cc: "Ronald P. Bonica" <rbonica@juniper.net>, "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2014 16:16:18 -0000

Carlos,

On 2/18/2014 6:53 PM, Carlos Pignataro (cpignata) wrote:
> Joe,
>
> On Feb 18, 2014, at 1:08 PM, Joe Touch <touch@isi.edu> wrote:
>
>>
>>
>> On 2/18/2014 9:27 AM, Templin, Fred L wrote:
>>> Hi Joe,
>>>
>>> You seem to be talking past me - maybe it was because I wrote too much.
>>> The fragmentation story for tunnels is very simple as follows:
>>
>> Yes, IMO they are, and here's mine:
>>
>> 	- if a tunnel CAN transit a packet, it MUST try
>>
>> 		i.e., the MTU of a tunnel that uses IPv6 encapsulation
>> 		is 65535 - encapsulation headers
>
> Where is this specified (other than stated by you in your email with
> 2119 language)?

Nowhere, and it need not be specified. It's basically the definition of 
an MTU.

> This defeats the purpose of a configurable MTU, and
> frankly shows requirements that do not exist and are not met in real life.
>
> Take for example RFC 1812, Section 3.3.4., "MTU":
>
>     The MTU of each logical interface MUST be configurable within the
>     range of legal MTUs for the interface.

RFC1812 is a spec for routers (gateways), not for tunnels. A tunnel is a 
link, where two or more links interconnect at a gateway.

I.e., the *link* has an MTU, which is defined as the largest message 
that can traverse the link. It's not defined as the largest message that 
can traverse the link without fragmentation inside the link.

The context of the above requirement is the configurable value within 
the router. Sure, the router operator can override the link MTU by 
setting an *interface* MTU <= link MTU.

However, when we specify a tunnel technology, we are talking about the 
link MTU, not the interface MTU.

>     Many Link Layer protocols define a maximum frame size that may be
>     sent.  In such cases, a router MUST NOT allow an MTU to be set which
>     would allow sending of frames larger than those allowed by the Link
>     Layer protocol.  However, a router SHOULD be willing to receive a
>     packet as large as the maximum frame size even if that is larger than
>     the MTU.

The above basically says, in other words, "routers MUST NOT set the 
interface MTU larger than the link MTU, and routers SHOULD receive 
packets larger than the interface MTU as long as it is no larger than 
the link MTU".

Again, for tunnels, we're talking about the link MTU.

> Apologies as I have said the following on this list more than once,
> but to reiterate: if you consider a tunnel as a logical link, the "link
> max frame size" is 64k - tunnel encap. But that does *not* mean that's
> the MTU, nor that packets larger than the tunnel MTU need to be

the interface MTU...

> fragmented after encap because they fit this max link size.

max link size = tunnel MTU.

It does mean that the egress MUST be capable of reassembling any packet 
no larger than the tunnel MTU.

So the *tunnel MTU* is 64K.

Yes, at the router, the *interface MTU* may override this to a lower 
value as a configuration parameter.

> If the MTU is configured on an ethernet link to be 500 B, but the

you configure an interface MTU, not a link MTU

> physical media can (capable) send larger sizes, what happens with a
> 1000B packet?

at the router, that depends on the interface MTU - if it's 500B, then 
the packet would be dropped by the router and an ICMP PTB sent upstream.

note that this router MUST be able to reassemble (at the "link layer", 
i.e., the added IP header) fragments that transit a 1000B IP packet, 
even if the interface MTU is 500B.

>> 	- if a tunnel CANNOT transit a packet, it rejects it
>>
>> 		i.e., anything larger than "65535 - encap headers"
>>
>> Everything else mistakes MSS (maximum) for PSS (preferred).
>> Preferredis the min of the MSS's. An IPv6 tunnel limits MSS only insofar as
>> packets larger than 65535-headers cannot traverse it.
>>
>
> Similarly, where is "preferred" specified?

I was introducing that term.

> And these are segment sizes and not MTUs?

Nope; I mistyped, and meant MTU and PTU, but I think the concept is 
equally applicable to transport layer segments (MSS and PSS).

Joe


From nobody Wed Feb 19 08:19:26 2014
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FD061A04D0 for <int-area@ietfa.amsl.com>; Wed, 19 Feb 2014 08:19:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9U-G7zLewzXA for <int-area@ietfa.amsl.com>; Wed, 19 Feb 2014 08:19:22 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id C22CC1A021B for <int-area@ietf.org>; Wed, 19 Feb 2014 08:19:22 -0800 (PST)
Received: from [192.168.1.93] (pool-71-105-87-112.lsanca.dsl-w.verizon.net [71.105.87.112]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id s1JGIigE019253 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 19 Feb 2014 08:18:47 -0800 (PST)
Message-ID: <5304D965.7040409@isi.edu>
Date: Wed, 19 Feb 2014 08:18:45 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, Ronald Bonica <rbonica@juniper.net>
References: <68a71d0317c546689875cfb7a1a67f9b@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983181D205B@XCH-BLV-504.nw.nos.boeing.com> <F3D91914-1A80-4CEC-96B9-99CF2BF0F64B@isi.edu> <2134F8430051B64F815C691A62D983181D35E5@XCH-BLV-504 <5303A650.2050303@isi.edu> <d02b9aae44b44fdb8bb880f2cdd555cd@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983181D46AF@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D983181D46AF@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/ImU4dDahK3CClvry_HZx1P4pm3c
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2014 16:19:24 -0000

On 2/19/2014 8:05 AM, Templin, Fred L wrote:
> Hi Ron,
>
>> The draft that Joe and Fred are considering applies to environments where egress routers are commonly
>> capable of reassembling at line rate. Since this is a different environment, it should be addressed in
>> a separate draft.
>
> No, that is not correct - the draft we are considering accounts for all
> environments in which tunnel ingresses and egresses may be deployed.

+1 and -1

+1 that the Intarea tunnel doc should address the generic case of 
tunnels that transit IP packets, including as many specific examples as 
possible.

-1 that the GRE tunnel spec needs to start with "what is deployed", but 
should compare that to the Intarea tunnel doc and provide a set of 
"SHOULD" recommendations to help transition GRE tunneling to follow BCP.

(IMO the Intarea doc is really targeted as a BCP, even though previously 
issued as informational).

Joe


From nobody Wed Feb 19 08:27:34 2014
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD6951A022F for <int-area@ietfa.amsl.com>; Wed, 19 Feb 2014 08:27:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.749
X-Spam-Level: 
X-Spam-Status: No, score=-4.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yeAFGWWh9nFU for <int-area@ietfa.amsl.com>; Wed, 19 Feb 2014 08:27:31 -0800 (PST)
Received: from slb-mbsout-01.boeing.com (slb-mbsout-01.boeing.com [130.76.64.128]) by ietfa.amsl.com (Postfix) with ESMTP id F19E61A01E2 for <int-area@ietf.org>; Wed, 19 Feb 2014 08:27:30 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id s1JGRRFP012396; Wed, 19 Feb 2014 08:27:27 -0800
Received: from XCH-PHX-213.sw.nos.boeing.com (xch-phx-213.sw.nos.boeing.com [130.247.25.142]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id s1JGRLRY012325 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Wed, 19 Feb 2014 08:27:22 -0800
Received: from XCH-BLV-403.nw.nos.boeing.com (2002:82f7:193e::82f7:193e) by XCH-PHX-213.sw.nos.boeing.com (2002:82f7:198e::82f7:198e) with Microsoft SMTP Server (TLS) id 14.3.174.1; Wed, 19 Feb 2014 08:27:21 -0800
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.102]) by XCH-BLV-403.nw.nos.boeing.com ([169.254.3.123]) with mapi id 14.03.0174.001; Wed, 19 Feb 2014 08:27:20 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Joe Touch <touch@isi.edu>, Ronald Bonica <rbonica@juniper.net>
Thread-Topic: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
Thread-Index: AQHPLY5DZ6PoNhiMLkS+vK8jjU2/Npq8wv4A
Date: Wed, 19 Feb 2014 16:27:20 +0000
Message-ID: <2134F8430051B64F815C691A62D983181D4707@XCH-BLV-504.nw.nos.boeing.com>
References: <68a71d0317c546689875cfb7a1a67f9b@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983181D205B@XCH-BLV-504.nw.nos.boeing.com> <F3D91914-1A80-4CEC-96B9-99CF2BF0F64B@isi.edu> <2134F8430051B64F815C691A62D983181D35E5@XCH-BLV-504 <5303A650.2050303@isi.edu> <d02b9aae44b44fdb8bb880f2cdd555cd@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983181D46AF@XCH-BLV-504.nw.nos.boeing.com> <5304D965.7040409@isi.edu>
In-Reply-To: <5304D965.7040409@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/C6_o9VqaKHYJ3hGSWzNTWD3tn9Y
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2014 16:27:32 -0000

Hi Joe,

> -----Original Message-----
> From: Joe Touch [mailto:touch@isi.edu]
> Sent: Wednesday, February 19, 2014 8:19 AM
> To: Templin, Fred L; Ronald Bonica
> Cc: int-area@ietf.org
> Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-int=
area-gre-mtu-04.txt
>=20
>=20
>=20
> On 2/19/2014 8:05 AM, Templin, Fred L wrote:
> > Hi Ron,
> >
> >> The draft that Joe and Fred are considering applies to environments wh=
ere egress routers are
> commonly
> >> capable of reassembling at line rate. Since this is a different enviro=
nment, it should be addressed
> in
> >> a separate draft.
> >
> > No, that is not correct - the draft we are considering accounts for all
> > environments in which tunnel ingresses and egresses may be deployed.
>=20
> +1 and -1
>=20
> +1 that the Intarea tunnel doc should address the generic case of
> tunnels that transit IP packets, including as many specific examples as
> possible.
>=20
> -1 that the GRE tunnel spec needs to start with "what is deployed", but
> should compare that to the Intarea tunnel doc and provide a set of
> "SHOULD" recommendations to help transition GRE tunneling to follow BCP.

I am OK with that. The same is true of my drafts on 6rd MTU and
AERO MTU. They will wrap themselves around the generic intarea
tunnel doc and then tell the restricting conditions that are
specific to those environments.

> (IMO the Intarea doc is really targeted as a BCP, even though previously
> issued as informational).

That sounds right to me.

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

> Joe


From nobody Wed Feb 19 10:14:29 2014
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A36C91A00B8 for <int-area@ietfa.amsl.com>; Wed, 19 Feb 2014 10:14:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.749
X-Spam-Level: 
X-Spam-Status: No, score=-4.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x-0fBZX0UCZE for <int-area@ietfa.amsl.com>; Wed, 19 Feb 2014 10:14:26 -0800 (PST)
Received: from slb-mbsout-02.boeing.com (slb-mbsout-02.boeing.com [130.76.64.129]) by ietfa.amsl.com (Postfix) with ESMTP id 233FF1A04B8 for <int-area@ietf.org>; Wed, 19 Feb 2014 10:14:25 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id s1JIELm7031612; Wed, 19 Feb 2014 10:14:21 -0800
Received: from XCH-PHX-411.sw.nos.boeing.com (xch-phx-411.sw.nos.boeing.com [10.57.37.42]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id s1JIEDf9031066 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Wed, 19 Feb 2014 10:14:13 -0800
Received: from XCH-BLV-503.nw.nos.boeing.com (130.247.25.192) by XCH-PHX-411.sw.nos.boeing.com (10.57.37.42) with Microsoft SMTP Server (TLS) id 14.3.174.1; Wed, 19 Feb 2014 10:14:12 -0800
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.102]) by XCH-BLV-503.nw.nos.boeing.com ([169.254.3.231]) with mapi id 14.03.0174.001; Wed, 19 Feb 2014 10:14:12 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Joe Touch <touch@isi.edu>, "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
Thread-Topic: [Int-area] New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
Thread-Index: AQHPLY3zBmxqlKZ1X0qVTICHOnF49Jq84R+Q
Date: Wed, 19 Feb 2014 18:14:11 +0000
Message-ID: <2134F8430051B64F815C691A62D983181D49D6@XCH-BLV-504.nw.nos.boeing.com>
References: <68a71d0317c546689875cfb7a1a67f9b@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983181D205B@XCH-BLV-504.nw.nos.boeing.com> <F3D91914-1A80-4CEC-96B9-99CF2BF0F64B@isi.edu> <2134F8430051B64F815C691A62D983181D35E5@XCH-BLV-504.nw.nos.boeing.com> <5303A1AD.9070904@isi.edu> <5EAA1AB8-EF82-468F-9E61-DDFF78762753@cisco.com> <5304D88D.4030307@isi.edu>
In-Reply-To: <5304D88D.4030307@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/3BAglT-bc-CshRm1UpZV2md48EQ
Cc: "Ronald P. Bonica" <rbonica@juniper.net>, "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2014 18:14:27 -0000

Hi Joe,

> So the *tunnel MTU* is 64K.

For IPv6-over-IPv6 tunnels, the MTU is actually 4G. Do we
want to mention jumbograms somewhere?

Thanks - Fred


From nobody Wed Feb 19 10:27:02 2014
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B34F01A01FB for <int-area@ietfa.amsl.com>; Wed, 19 Feb 2014 10:27:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.748
X-Spam-Level: 
X-Spam-Status: No, score=-4.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MvvrW12utZeN for <int-area@ietfa.amsl.com>; Wed, 19 Feb 2014 10:26:59 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id D3C4A1A04F4 for <int-area@ietf.org>; Wed, 19 Feb 2014 10:26:58 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id s1JIPx6H004137 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 19 Feb 2014 10:25:59 -0800 (PST)
Message-ID: <5304F737.70007@isi.edu>
Date: Wed, 19 Feb 2014 10:25:59 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
References: <68a71d0317c546689875cfb7a1a67f9b@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983181D205B@XCH-BLV-504.nw.nos.boeing.com> <F3D91914-1A80-4CEC-96B9-99CF2BF0F64B@isi.edu> <2134F8430051B64F815C691A62D983181D35E5@XCH-BLV-504.nw.nos.boeing.com> <5303A1AD.9070904@isi.edu> <5EAA1AB8-EF82-468F-9E61-DDFF78762753@cisco.com> <5304D88D.4030307@isi.edu> <2134F8430051B64F815C691A62D983181D49D6@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D983181D49D6@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/sSkcIv46hTlzddB9P-C3cCAFfwM
Cc: "Ronald P. Bonica" <rbonica@juniper.net>, "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2014 18:27:00 -0000

Yup.


On 2/19/2014 10:14 AM, Templin, Fred L wrote:
> Hi Joe,
>
>> So the *tunnel MTU* is 64K.
>
> For IPv6-over-IPv6 tunnels, the MTU is actually 4G. Do we
> want to mention jumbograms somewhere?
>
> Thanks - Fred
>


From nobody Wed Feb 19 10:34:53 2014
Return-Path: <rbonica@juniper.net>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EAB11A0504 for <int-area@ietfa.amsl.com>; Wed, 19 Feb 2014 10:34:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.601
X-Spam-Level: 
X-Spam-Status: No, score=-102.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wbsBgfbHY0nN for <int-area@ietfa.amsl.com>; Wed, 19 Feb 2014 10:34:50 -0800 (PST)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe004.messaging.microsoft.com [216.32.180.14]) by ietfa.amsl.com (Postfix) with ESMTP id E5F021A04EF for <int-area@ietf.org>; Wed, 19 Feb 2014 10:34:49 -0800 (PST)
Received: from mail219-va3-R.bigfish.com (10.7.14.243) by VA3EHSOBE007.bigfish.com (10.7.40.11) with Microsoft SMTP Server id 14.1.225.22; Wed, 19 Feb 2014 18:34:46 +0000
Received: from mail219-va3 (localhost [127.0.0.1])	by mail219-va3-R.bigfish.com (Postfix) with ESMTP id 30E54640235;	Wed, 19 Feb 2014 18:34:46 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT005.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: 2
X-BigFish: VPS2(z579ehzda00hdc73hzz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6hzd9hzz2fh109h2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1e1dh1fe8h1ff5h2216h22d0h2336h2461h2487h24ach24d7h2516h2545h255eh9a9j1155h)
Received-SPF: pass (mail219-va3: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=rbonica@juniper.net; helo=BL2PRD0510HT005.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(6009001)(189002)(199002)(81816001)(83322001)(54316002)(558084003)(31966008)(33646001)(56816005)(47976001)(93516002)(80976001)(47736001)(56776001)(79102001)(46102001)(74876001)(81686001)(74662001)(74316001)(51856001)(74706001)(83072002)(50986001)(77982001)(92566001)(85852003)(90146001)(76786001)(2171001)(69226001)(76796001)(74502001)(87266001)(94946001)(85306002)(95416001)(66066001)(65816001)(80022001)(74366001)(76482001)(95666001)(86362001)(4396001)(76576001)(77096001)(81342001)(49866001)(59766001)(47446002)(53806001)(63696002)(54356001)(81542001)(87936001)(93136001)(94316002)(2656002)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:CO1PR05MB443; H:CO1PR05MB442.namprd05.prod.outlook.com; CLIP:66.129.241.12; FPR:BEB6D897.2CB02E52.71CD81B0.44A49031.2007E; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
Received: from mail219-va3 (localhost.localdomain [127.0.0.1]) by mail219-va3 (MessageSwitch) id 1392834884455514_20606; Wed, 19 Feb 2014 18:34:44 +0000 (UTC)
Received: from VA3EHSMHS028.bigfish.com (unknown [10.7.14.244])	by mail219-va3.bigfish.com (Postfix) with ESMTP id 60FC1B4004E; Wed, 19 Feb 2014 18:34:44 +0000 (UTC)
Received: from BL2PRD0510HT005.namprd05.prod.outlook.com (157.56.240.101) by VA3EHSMHS028.bigfish.com (10.7.99.38) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 19 Feb 2014 18:34:42 +0000
Received: from CO1PR05MB443.namprd05.prod.outlook.com (10.141.73.152) by BL2PRD0510HT005.namprd05.prod.outlook.com (10.255.100.40) with Microsoft SMTP Server (TLS) id 14.16.411.0; Wed, 19 Feb 2014 18:34:42 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) by CO1PR05MB443.namprd05.prod.outlook.com (10.141.73.152) with Microsoft SMTP Server (TLS) id 15.0.878.16; Wed, 19 Feb 2014 18:34:38 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.51]) by CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.51]) with mapi id 15.00.0878.008; Wed, 19 Feb 2014 18:34:38 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, Joe Touch <touch@isi.edu>,  "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
Thread-Topic: [Int-area] New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
Thread-Index: AQHPLR3Yn1qDINdMBUybWbX0OOnVr5q8wUiAgAAhQoCAAAUVkA==
Date: Wed, 19 Feb 2014 18:34:37 +0000
Message-ID: <c33e467560ce49399bbf30fec1d1c911@CO1PR05MB442.namprd05.prod.outlook.com>
References: <68a71d0317c546689875cfb7a1a67f9b@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983181D205B@XCH-BLV-504.nw.nos.boeing.com> <F3D91914-1A80-4CEC-96B9-99CF2BF0F64B@isi.edu> <2134F8430051B64F815C691A62D983181D35E5@XCH-BLV-504.nw.nos.boeing.com> <5303A1AD.9070904@isi.edu> <5EAA1AB8-EF82-468F-9E61-DDFF78762753@cisco.com> <5304D88D.4030307@isi.edu> <2134F8430051B64F815C691A62D983181D49D6@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D983181D49D6@XCH-BLV-504.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.12]
x-forefront-prvs: 012792EC17
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/qw_qSzIx4LrBjtx3XKwbxrvNOug
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2014 18:34:52 -0000

Fred,

Can you provide a normative citation for the requirement that you state, be=
low?

                 Ron



>For IPv6-over-IPv6 tunnels, the MTU is actually 4G. Do we want to mention =
jumbograms somewhere?





From nobody Wed Feb 19 10:48:22 2014
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B8B41A0510 for <int-area@ietfa.amsl.com>; Wed, 19 Feb 2014 10:48:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.749
X-Spam-Level: 
X-Spam-Status: No, score=-4.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UV16FOXr83H1 for <int-area@ietfa.amsl.com>; Wed, 19 Feb 2014 10:48:16 -0800 (PST)
Received: from blv-mbsout-02.boeing.com (blv-mbsout-02.boeing.com [130.76.32.232]) by ietfa.amsl.com (Postfix) with ESMTP id 038371A0512 for <int-area@ietf.org>; Wed, 19 Feb 2014 10:48:15 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id s1JImC2K011217; Wed, 19 Feb 2014 10:48:12 -0800
Received: from XCH-PHX-313.sw.nos.boeing.com (xch-phx-313.sw.nos.boeing.com [130.247.25.175]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id s1JIm8lU011149 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Wed, 19 Feb 2014 10:48:08 -0800
Received: from XCH-BLV-107.nw.nos.boeing.com (2002:82f7:197b::82f7:197b) by XCH-PHX-313.sw.nos.boeing.com (2002:82f7:19af::82f7:19af) with Microsoft SMTP Server (TLS) id 14.3.174.1; Wed, 19 Feb 2014 10:48:08 -0800
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.102]) by XCH-BLV-107.nw.nos.boeing.com ([169.254.7.225]) with mapi id 14.03.0174.001; Wed, 19 Feb 2014 10:48:07 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ronald Bonica <rbonica@juniper.net>, Joe Touch <touch@isi.edu>, "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
Thread-Topic: [Int-area] New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
Thread-Index: AQHPLR3YBmxqlKZ1X0qVTICHOnF49Jq8wUiAgAAhQoCAAAUVkIAAA9SQ
Date: Wed, 19 Feb 2014 18:48:06 +0000
Message-ID: <2134F8430051B64F815C691A62D983181D4AB2@XCH-BLV-504.nw.nos.boeing.com>
References: <68a71d0317c546689875cfb7a1a67f9b@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983181D205B@XCH-BLV-504.nw.nos.boeing.com> <F3D91914-1A80-4CEC-96B9-99CF2BF0F64B@isi.edu> <2134F8430051B64F815C691A62D983181D35E5@XCH-BLV-504.nw.nos.boeing.com> <5303A1AD.9070904@isi.edu> <5EAA1AB8-EF82-468F-9E61-DDFF78762753@cisco.com> <5304D88D.4030307@isi.edu> <2134F8430051B64F815C691A62D983181D49D6@XCH-BLV-504.nw.nos.boeing.com> <c33e467560ce49399bbf30fec1d1c911@CO1PR05MB442.namprd05.prod.outlook.com>
In-Reply-To: <c33e467560ce49399bbf30fec1d1c911@CO1PR05MB442.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/kmhppzszVtQPeoJVNlLw68-DOwo
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2014 18:48:17 -0000

Hi Ron,

> Can you provide a normative citation for the requirement that you state, =
below?

Sure - RFC2675.

Thanks - Fred

>                  Ron
>=20
>=20
>=20
> >For IPv6-over-IPv6 tunnels, the MTU is actually 4G. Do we want to mentio=
n jumbograms somewhere?
>=20
>=20
>=20


From nobody Wed Feb 19 11:39:16 2014
Return-Path: <rbonica@juniper.net>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C8C81A03FB for <int-area@ietfa.amsl.com>; Wed, 19 Feb 2014 11:39:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.201
X-Spam-Level: 
X-Spam-Status: No, score=-104.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pjBYu7f4PjIa for <int-area@ietfa.amsl.com>; Wed, 19 Feb 2014 11:39:12 -0800 (PST)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe004.messaging.microsoft.com [65.55.88.14]) by ietfa.amsl.com (Postfix) with ESMTP id 222C11A04F4 for <int-area@ietf.org>; Wed, 19 Feb 2014 11:39:12 -0800 (PST)
Received: from mail129-tx2-R.bigfish.com (10.9.14.245) by TX2EHSOBE013.bigfish.com (10.9.40.33) with Microsoft SMTP Server id 14.1.225.22; Wed, 19 Feb 2014 19:39:08 +0000
Received: from mail129-tx2 (localhost [127.0.0.1])	by mail129-tx2-R.bigfish.com (Postfix) with ESMTP id 77022A0175;	Wed, 19 Feb 2014 19:39:08 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT001.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -21
X-BigFish: VPS-21(z579ehz9371I542I1432Izz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6hzd9hz1de098h1033IL8275dh1de097hz2fh109h2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1e1dh1fe8h1ff5h2216h22d0h2336h2461h2487h24ach24d7h2516h2545h255eh9a9j1155h)
Received-SPF: pass (mail129-tx2: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=rbonica@juniper.net; helo=BL2PRD0510HT001.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(6009001)(13464003)(199002)(189002)(51704005)(377454003)(65816001)(66066001)(93516002)(83322001)(93136001)(92566001)(81342001)(2656002)(81816001)(83072002)(79102001)(85852003)(80022001)(19580405001)(74706001)(77096001)(80976001)(19580395003)(56816005)(94946001)(54356001)(90146001)(4396001)(47976001)(76796001)(47736001)(86362001)(51856001)(76576001)(74316001)(74502001)(69226001)(74662001)(49866001)(87266001)(76786001)(50986001)(95416001)(77982001)(54316002)(53806001)(87936001)(46102001)(63696002)(33646001)(81686001)(59766001)(85306002)(31966008)(2171001)(47446002)(74876001)(95666001)(56776001)(76482001)(74366001)(81542001)(94316002)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:CO1PR05MB441; H:CO1PR05MB442.namprd05.prod.outlook.com; CLIP:66.129.241.12; FPR:BF9E5096.AC33CD50.B3FD8D8C.C4A6931C.20153; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
Received: from mail129-tx2 (localhost.localdomain [127.0.0.1]) by mail129-tx2 (MessageSwitch) id 1392838744127817_15576; Wed, 19 Feb 2014 19:39:04 +0000 (UTC)
Received: from TX2EHSMHS015.bigfish.com (unknown [10.9.14.240])	by mail129-tx2.bigfish.com (Postfix) with ESMTP id A78432E00B3; Wed, 19 Feb 2014 19:39:03 +0000 (UTC)
Received: from BL2PRD0510HT001.namprd05.prod.outlook.com (157.56.240.101) by TX2EHSMHS015.bigfish.com (10.9.99.115) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 19 Feb 2014 19:39:01 +0000
Received: from CO1PR05MB441.namprd05.prod.outlook.com (10.141.73.147) by BL2PRD0510HT001.namprd05.prod.outlook.com (10.255.100.36) with Microsoft SMTP Server (TLS) id 14.16.411.0; Wed, 19 Feb 2014 19:39:00 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) by CO1PR05MB441.namprd05.prod.outlook.com (10.141.73.147) with Microsoft SMTP Server (TLS) id 15.0.878.16; Wed, 19 Feb 2014 19:38:58 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.51]) by CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.51]) with mapi id 15.00.0878.008; Wed, 19 Feb 2014 19:38:58 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, Joe Touch <touch@isi.edu>,  "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
Thread-Topic: [Int-area] New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
Thread-Index: AQHPLR3Yn1qDINdMBUybWbX0OOnVr5q8wUiAgAAhQoCAAAUVkIAABGUAgAANt2A=
Date: Wed, 19 Feb 2014 19:38:57 +0000
Message-ID: <d8925788a96a443680d874296c498c6a@CO1PR05MB442.namprd05.prod.outlook.com>
References: <68a71d0317c546689875cfb7a1a67f9b@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983181D205B@XCH-BLV-504.nw.nos.boeing.com> <F3D91914-1A80-4CEC-96B9-99CF2BF0F64B@isi.edu> <2134F8430051B64F815C691A62D983181D35E5@XCH-BLV-504.nw.nos.boeing.com> <5303A1AD.9070904@isi.edu> <5EAA1AB8-EF82-468F-9E61-DDFF78762753@cisco.com> <5304D88D.4030307@isi.edu> <2134F8430051B64F815C691A62D983181D49D6@XCH-BLV-504.nw.nos.boeing.com> <c33e467560ce49399bbf30fec1d1c911@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983181D4AB2@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D983181D4AB2@XCH-BLV-504.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.12]
x-forefront-prvs: 012792EC17
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/1BJex8p1YtU51_mY_MEEk_DbTms
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2014 19:39:15 -0000

Fred,

The word "tunnel" does not appear in RFC 2675.

                               Ron


-----Original Message-----
From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]=20
Sent: Wednesday, February 19, 2014 1:48 PM
To: Ronald Bonica; Joe Touch; Carlos Pignataro (cpignata)
Cc: int-area@ietf.org
Subject: RE: [Int-area] New Version Notification for draft-bonica-intarea-g=
re-mtu-04.txt

Hi Ron,

> Can you provide a normative citation for the requirement that you state, =
below?

Sure - RFC2675.

Thanks - Fred

>                  Ron
>=20
>=20
>=20
> >For IPv6-over-IPv6 tunnels, the MTU is actually 4G. Do we want to mentio=
n jumbograms somewhere?
>=20
>=20
>=20





From nobody Wed Feb 19 12:17:52 2014
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A2501A022E for <int-area@ietfa.amsl.com>; Wed, 19 Feb 2014 12:17:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.749
X-Spam-Level: 
X-Spam-Status: No, score=-4.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qU7m5-OsDFJg for <int-area@ietfa.amsl.com>; Wed, 19 Feb 2014 12:17:49 -0800 (PST)
Received: from stl-mbsout-02.boeing.com (stl-mbsout-02.boeing.com [130.76.96.170]) by ietfa.amsl.com (Postfix) with ESMTP id 389F51A0167 for <int-area@ietf.org>; Wed, 19 Feb 2014 12:17:49 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id s1JKHj55006802; Wed, 19 Feb 2014 14:17:45 -0600
Received: from XCH-PHX-112.sw.nos.boeing.com (xch-phx-112.sw.nos.boeing.com [130.247.25.134]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id s1JKHck1006739 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Wed, 19 Feb 2014 14:17:39 -0600
Received: from XCH-BLV-304.nw.nos.boeing.com (2002:82f7:19d8::82f7:19d8) by XCH-PHX-112.sw.nos.boeing.com (2002:82f7:1986::82f7:1986) with Microsoft SMTP Server (TLS) id 14.3.174.1; Wed, 19 Feb 2014 12:17:38 -0800
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.102]) by XCH-BLV-304.nw.nos.boeing.com ([169.254.4.205]) with mapi id 14.03.0174.001; Wed, 19 Feb 2014 12:17:37 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ronald Bonica <rbonica@juniper.net>, Joe Touch <touch@isi.edu>, "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
Thread-Topic: [Int-area] New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
Thread-Index: AQHPLR3YBmxqlKZ1X0qVTICHOnF49Jq8wUiAgAAhQoCAAAUVkIAABGUAgAANt2CAAAmEsA==
Date: Wed, 19 Feb 2014 20:17:37 +0000
Message-ID: <2134F8430051B64F815C691A62D983181D4C94@XCH-BLV-504.nw.nos.boeing.com>
References: <68a71d0317c546689875cfb7a1a67f9b@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983181D205B@XCH-BLV-504.nw.nos.boeing.com> <F3D91914-1A80-4CEC-96B9-99CF2BF0F64B@isi.edu> <2134F8430051B64F815C691A62D983181D35E5@XCH-BLV-504.nw.nos.boeing.com> <5303A1AD.9070904@isi.edu> <5EAA1AB8-EF82-468F-9E61-DDFF78762753@cisco.com> <5304D88D.4030307@isi.edu> <2134F8430051B64F815C691A62D983181D49D6@XCH-BLV-504.nw.nos.boeing.com> <c33e467560ce49399bbf30fec1d1c911@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983181D4AB2@XCH-BLV-504.nw.nos.boeing.com> <d8925788a96a443680d874296c498c6a@CO1PR05MB442.namprd05.prod.outlook.com>
In-Reply-To: <d8925788a96a443680d874296c498c6a@CO1PR05MB442.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/IOBK4Unp8Q8LmMLXoNF6sUZGJ10
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2014 20:17:51 -0000

Hi Ron,

> -----Original Message-----
> From: Ronald Bonica [mailto:rbonica@juniper.net]
> Sent: Wednesday, February 19, 2014 11:39 AM
> To: Templin, Fred L; Joe Touch; Carlos Pignataro (cpignata)
> Cc: int-area@ietf.org
> Subject: RE: [Int-area] New Version Notification for draft-bonica-intarea=
-gre-mtu-04.txt
>=20
> Fred,
>=20
> The word "tunnel" does not appear in RFC 2675.

That's OK; it doesn't need to. But the generic tunnel doc will
say that the more specific tunnel specs are free to define a
jumbo-in-jumbo encapsulation format since the length of an
IPv6 packet is not restricted to 64KB.

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

>=20
>                                Ron
>=20
>=20
> -----Original Message-----
> From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]
> Sent: Wednesday, February 19, 2014 1:48 PM
> To: Ronald Bonica; Joe Touch; Carlos Pignataro (cpignata)
> Cc: int-area@ietf.org
> Subject: RE: [Int-area] New Version Notification for draft-bonica-intarea=
-gre-mtu-04.txt
>=20
> Hi Ron,
>=20
> > Can you provide a normative citation for the requirement that you state=
, below?
>=20
> Sure - RFC2675.
>=20
> Thanks - Fred
>=20
> >                  Ron
> >
> >
> >
> > >For IPv6-over-IPv6 tunnels, the MTU is actually 4G. Do we want to ment=
ion jumbograms somewhere?
> >
> >
> >
>=20
>=20
>=20


From nobody Mon Feb 24 11:20:48 2014
Return-Path: <brian@innovationslab.net>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1CC01A022D for <int-area@ietfa.amsl.com>; Mon, 24 Feb 2014 11:20:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level: 
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_40=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KDe6uWA5WaTO for <int-area@ietfa.amsl.com>; Mon, 24 Feb 2014 11:20:45 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 295051A01FC for <int-area@ietf.org>; Mon, 24 Feb 2014 11:20:45 -0800 (PST)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id C500E8807D for <int-area@ietf.org>; Mon, 24 Feb 2014 11:20:44 -0800 (PST)
Received: from 102524215.rudm1.ra.johnshopkins.edu (addr16212925014.ippl.jhmi.edu [162.129.250.14]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 8A9D3136814C for <int-area@ietf.org>; Mon, 24 Feb 2014 11:20:44 -0800 (PST)
Message-ID: <530B9B83.7050404@innovationslab.net>
Date: Mon, 24 Feb 2014 14:20:35 -0500
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "int-area@ietf.org" <int-area@ietf.org>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="14dTbVQ6rmcNJc8nvsAEj3hF5vHSIQRNj"
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/ihP4D0NWZtAgLAG4Hm5MvamqZ3g
Subject: [Int-area] INT ADs' Office Hours
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Feb 2014 19:20:46 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--14dTbVQ6rmcNJc8nvsAEj3hF5vHSIQRNj
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

All,
     As with previous meetings, the INT ADs will be holding office hours
in London.  We have scheduled our office hours for Thursday (Mar. 6th)
from 15:15 to 16:45.  We will hold these in the yet-to-be-identified
IESG break-out room.  There will be a follow-up e-mail once the room has
been identified.

Regards,
Brian




--14dTbVQ6rmcNJc8nvsAEj3hF5vHSIQRNj
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.20 (Darwin)
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJTC5uUAAoJEBOZRqCi7goqxcMH/0wjCMbqhUehbm1snhQIcTtx
Xgf5lkCxINkNXN1IgBgLlprb62rvxQDIltmWsG0wp5856+5lp8J7Euu4LWLBp7MC
EzanfxfuLOeHu43KB4ildlorUEhKNA7KnlC1iPn+ueNTT9qpmwIKpl1/VOt7GVK6
91TrOKLcWUd+vntey+Ofb4iDJ64KYychKk1rxZeP6LqpHP/HvOKgvNDDGouI0s08
7Zxd5C2PaIBxjqmR7vWGyd2gjVrYnXGac6OJ22qEJCsbFVj5QG+G70KugfeCVmMW
j8BaSjTN1u8NzWXVjbz5zB2yjJsMEbxq0uEvX7mcDHHxsAAgKUxA4ZQfUMmMQfM=
=j1x4
-----END PGP SIGNATURE-----

--14dTbVQ6rmcNJc8nvsAEj3hF5vHSIQRNj--


From nobody Tue Feb 25 23:39:41 2014
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CC9E1A0043 for <int-area@ietfa.amsl.com>; Tue, 25 Feb 2014 23:39:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6SoQxUOrmpXQ for <int-area@ietfa.amsl.com>; Tue, 25 Feb 2014 23:39:32 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 7A27D1A0047 for <int-area@ietf.org>; Tue, 25 Feb 2014 23:39:26 -0800 (PST)
Received: from [192.168.1.93] (pool-71-105-87-112.lsanca.dsl-w.verizon.net [71.105.87.112]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id s1Q7cphZ029925 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 25 Feb 2014 23:38:54 -0800 (PST)
Message-ID: <530D9A0F.3070508@isi.edu>
Date: Tue, 25 Feb 2014 23:38:55 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, Ronald Bonica <rbonica@juniper.net>
References: <68a71d0317c546689875cfb7a1a67f9b@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983181D205B@XCH-BLV-504.nw.nos.boeing.com> <F3D91914-1A80-4CEC-96B9-99CF2BF0F64B@isi.edu> <2134F8430051B64F815C691A62D983181D35E5@XCH-BLV-504 <5303A650.2050303@isi.edu> <d02b9aae44b44fdb8bb880f2cdd555cd@CO1PR05MB442.namprd05.prod.outlook.com> <2134F8430051B64F815C691A62D983181D46AF@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D983181D46AF@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/uyi__7Z3l9g2LFVAZwaATGNIRtI
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-04.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Feb 2014 07:39:37 -0000

FWIW, this refers to the existing draft in the intarea about tunnels, 
which is being 'revived'. I just confirmed with Mark Townsley, and he 
and I are revising that one shortly.

Joe

On 2/19/2014 8:05 AM, Templin, Fred L wrote:
> Hi Ron,
>
>> The draft that Joe and Fred are considering applies to environments where egress routers are commonly
>> capable of reassembling at line rate. Since this is a different environment, it should be addressed in
>> a separate draft.
>
> No, that is not correct - the draft we are considering accounts for all
> environments in which tunnel ingresses and egresses may be deployed.
>
> Thanks - Fred
> fred.l.templin@boeing.com
>


From nobody Wed Feb 26 11:28:20 2014
Return-Path: <brian@innovationslab.net>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 155BF1A087A for <int-area@ietfa.amsl.com>; Wed, 26 Feb 2014 11:28:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NeOG46_h44zt for <int-area@ietfa.amsl.com>; Wed, 26 Feb 2014 11:28:06 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 821D11A084B for <int-area@ietf.org>; Wed, 26 Feb 2014 11:28:02 -0800 (PST)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 6D1128811E for <int-area@ietf.org>; Wed, 26 Feb 2014 11:28:01 -0800 (PST)
Received: from 102523217.rudm1.ra.johnshopkins.edu (addr16212925014.ippl.jhmi.edu [162.129.250.14]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 313EE130002 for <int-area@ietf.org>; Wed, 26 Feb 2014 11:28:01 -0800 (PST)
Message-ID: <530E403B.4060600@innovationslab.net>
Date: Wed, 26 Feb 2014 14:27:55 -0500
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: int-area@ietf.org
References: <530B9B83.7050404@innovationslab.net>
In-Reply-To: <530B9B83.7050404@innovationslab.net>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="4HnEQkB9FESjKtOcfHEA5rGFP3K236dNW"
Archived-At: http://mailarchive.ietf.org/arch/msg/int-area/HssrEYgbR4gTWx9DiZebemERixw
Subject: Re: [Int-area] INT ADs' Office Hours
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Feb 2014 19:28:09 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--4HnEQkB9FESjKtOcfHEA5rGFP3K236dNW
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Our office hours will be held in Victoria (East Wing, Mezzanine Meeting
Rooms).

Regards,
Brian

On 2/24/14 2:20 PM, Brian Haberman wrote:
> All,
>      As with previous meetings, the INT ADs will be holding office hour=
s
> in London.  We have scheduled our office hours for Thursday (Mar. 6th)
> from 15:15 to 16:45.  We will hold these in the yet-to-be-identified
> IESG break-out room.  There will be a follow-up e-mail once the room ha=
s
> been identified.
>=20
> Regards,
> Brian
>=20
>=20
>=20
>=20
>=20
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area
>=20


--4HnEQkB9FESjKtOcfHEA5rGFP3K236dNW
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.20 (Darwin)
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJTDkBCAAoJEBOZRqCi7goqXsQIAIzW8enX9xnOFgzWAJJ/l10I
hpgEHndRVTM3rXAAEbCh2d+MK3S9XYJs1VujbIcqh3RhI4AmDzmrqFraCOqTPCqc
T7y42ayUhhyOrLQUju3RlbSPMQyiODsbLLGAedmJRBnufufkbNogpV55FXabE/CU
5l8ModDq6CKXqxHgFN3sPNGvsyLtgU/EqPj+kNj5ihN0WvF75fIR7yj6yQmbYaZo
QRDCS6SCQEFMrm3taQV4h7D1094w09UcDuA5ZpNFzx6WwsRvxUZPV2oXkUuRAgnz
pHRrYClliDq0XJg9eCTYRQC4IGCaS5AzYmjq4Xd1sNsv2vzgGblNcwIIQB07K8Q=
=7LIW
-----END PGP SIGNATURE-----

--4HnEQkB9FESjKtOcfHEA5rGFP3K236dNW--

