
From mohamed.boucadair@orange.com  Tue May  7 07:50:46 2013
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEA6C21F85ED; Tue,  7 May 2013 07:50:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H20dGHWRQHQ4; Tue,  7 May 2013 07:50:42 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id 14B6B21F85D1; Tue,  7 May 2013 07:50:41 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id 401053246ED; Tue,  7 May 2013 16:50:41 +0200 (CEST)
Received: from PUEXCH41.nanterre.francetelecom.fr (unknown [10.101.44.30]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 1ACB623804B; Tue,  7 May 2013 16:50:41 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.233.200.25]) by PUEXCH41.nanterre.francetelecom.fr ([10.101.44.30]) with mapi; Tue, 7 May 2013 16:50:40 +0200
From: <mohamed.boucadair@orange.com>
To: 'Joshua Shire' <jshire@hyduke.com>, "fmc@ietf.org" <fmc@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>
Date: Tue, 7 May 2013 16:50:38 +0200
Thread-Topic: draft-boucadair-intarea-host-identifier-scenarios
Thread-Index: Ac5LMjyqGqkODLucTvmk2Pl+E8NMBw==
Message-ID: <94C682931C08B048B7A8645303FDC9F36ECE1436BE@PUEXCB1B.nanterre.francetelecom.fr>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.5.2.60325
Cc: "draft-boucadair-intarea-host-identifier-scenarios@tools.ietf.org" <draft-boucadair-intarea-host-identifier-scenarios@tools.ietf.org>
Subject: Re: [Int-area] draft-boucadair-intarea-host-identifier-scenarios
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
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, 07 May 2013 14:50:46 -0000

Dear Joshua,

Apologies for the delay to answer this message.

I see your point. I will add it to the list of items to be considered for t=
he next iteration of the document.=20

BTW, -03 already included some of requirements which cover security aspects=
 (see for instance REQ#1, REQ#2, REQ#3, REQ#9). Once we have a stable requi=
rements list, we will identify the requirements which are valid for each us=
e case: http://tools.ietf.org/html/draft-boucadair-intarea-host-identifier-=
scenarios-03#section-4.1=20

Cheers,
Med

>-----Message d'origine-----
>De : Joshua Shire [mailto:jshire@hyduke.com]=20
>Envoy=E9 : vendredi 25 janvier 2013 08:17
>=C0 : BOUCADAIR Mohamed OLNC/OLN; fmc@ietf.org; int-area@ietf.org
>Cc : draft-boucadair-intarea-host-identifier-scenarios@tools.ietf.org
>Objet : RE: draft-boucadair-intarea-host-identifier-scenarios
>
>Hello,
>
>I do not believe a pointer to=20
>http://tools.ietf.org/html/draft-ietf-intarea-nat-reveal-analys
>is-04#section-3  will be satisfactory for the security=20
>considerations section.=20
>
>http://www.ietf.org/rfc/rfc3552.txt  states that when writing=20
>a security considerations section, the process "...should be=20
>approached as an effort to perform "due diligence" in=20
>describing all known or foreseeable risks and threats to=20
>potential implementers and users." Normally we see RFCs=20
>describing more applied topics such as protocols, so the=20
>specific language and examples given in the above mentioned=20
>RFC may not seem directly applicable. However, "in spirit",=20
>the document seems clear in requiring all RFCs to examine in=20
>detail their potential security impact.
>
>As I'm sure we're all aware, some of the use cases identified=20
>are purposefully implemented to maintain the confidentiality=20
>of a client's identity (e.g. NAT to obfuscate the structure of=20
>an enterprise network, Open-Wifi to conceal the identity of a=20
>client under threat of persecution [or prosecution], etc.).=20
>
>Thus, in identifying these scenarios as sharing the "issue" of=20
>host identification, the author would seem to be required to=20
>discuss the potential security implications of treating the=20
>lack of host identification as such, rather than a desirable feature.
>
>Thanks,
>
>Joshua Shire
>Information Systems Manager
>Hyduke Energy Services Inc.
>
>-----Original Message-----
>From: int-area-bounces@ietf.org=20
>[mailto:int-area-bounces@ietf.org] On Behalf Of=20
>mohamed.boucadair@orange.com
>Sent: Monday, December 03, 2012 2:08 AM
>To: fmc@ietf.org; int-area@ietf.org
>Cc: draft-boucadair-intarea-host-identifier-scenarios@tools.ietf.org
>Subject: [Int-area] draft-boucadair-intarea-host-identifier-scenarios
>
>Dear all,
>
>We submitted an updated version of this draft to list use=20
>cases which encounter the issue of host identification. The=20
>following use cases are discussed in the draft:
>
>   (1)  Carrier Grade NAT (CGN)
>   (2)  A+P (e.g., MAP )
>   (3)  Application Proxies
>   (4)  Provider Wi-Fi
>   (5)  Policy and Charging Architectures
>   (6)  Cellular Networks
>   (7)  Femtocells
>   (8)  Overlay Networks (e.g., CDNs)
>
>The document does not include any solution-specific=20
>discussion. Its main goal is to identify the use cases and=20
>describe them.=20
>
>If you think your use case is not included in this version,=20
>please share it with us.=20
>
>Comments are welcome.=20
>
>Cheers,
>Med
>
>
>-----Message d'origine-----
>De : i-d-announce-bounces@ietf.org=20
>[mailto:i-d-announce-bounces@ietf.org] De la part de=20
>internet-drafts@ietf.org Envoy=E9 : lundi 3 d=E9cembre 2012 08:26=20
>=C0 : i-d-announce@ietf.org Objet : I-D Action:=20
>draft-boucadair-intarea-host-identifier-scenarios-02.txt
>
>
>A New Internet-Draft is available from the on-line=20
>Internet-Drafts directories.
>
>
>	Title           : Host Identification: Use Cases
>	Author(s)       : Mohamed Boucadair
>                          David Binet
>                          Sophie Durel
>                          Tirumaleswar Reddy
>                          Brandon Williams
>	Filename        :=20
>draft-boucadair-intarea-host-identifier-scenarios-02.txt
>	Pages           : 14
>	Date            : 2012-12-02
>
>Abstract:
>   This document describes a set of scenarios in which host
>   identification is required.
>
>
>The IETF datatracker status page for this draft is:
>https://datatracker.ietf.org/doc/draft-boucadair-intarea-host-i
>dentifier-scenarios
>
>There's also a htmlized version available at:
>http://tools.ietf.org/html/draft-boucadair-intarea-host-identif
>ier-scenarios-02
>
>A diff from the previous version is available at:
>http://www.ietf.org/rfcdiff?url2=3Ddraft-boucadair-intarea-host-i
>dentifier-scenarios-02
>
>
>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=20
>ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>_______________________________________________
>Int-area mailing list
>Int-area@ietf.org
>https://www.ietf.org/mailman/listinfo/int-area
>

From internet-drafts@ietf.org  Sat May 25 13:05:57 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CD4221F88FB; Sat, 25 May 2013 13:05:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.535
X-Spam-Level: 
X-Spam-Status: No, score=-102.535 tagged_above=-999 required=5 tests=[AWL=0.065, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W-yxqvalPXjP; Sat, 25 May 2013 13:05:55 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D836521F878C; Sat, 25 May 2013 13:05:55 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.50
Message-ID: <20130525200555.29609.2877.idtracker@ietfa.amsl.com>
Date: Sat, 25 May 2013 13:05:55 -0700
Cc: int-area@ietf.org
Subject: [Int-area] I-D Action: draft-ietf-intarea-flow-label-balancing-01.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 25 May 2013 20:05:57 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Internet Area Working Group Working Group=
 of the IETF.

	Title           : Using the IPv6 Flow Label for Server Load Balancing
	Author(s)       : Brian Carpenter
                          Sheng Jiang
                          Willy Tarreau
	Filename        : draft-ietf-intarea-flow-label-balancing-01.txt
	Pages           : 12
	Date            : 2013-05-25

Abstract:
   This document describes how the IPv6 flow label as currently
   specified can be used to enhance layer 3/4 load distribution and
   balancing for large server farms.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-intarea-flow-label-balancing

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-intarea-flow-label-balancing-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-intarea-flow-label-balancing-=
01


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


From rbonica@juniper.net  Wed May 29 06:40:28 2013
Return-Path: <rbonica@juniper.net>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C71DB21F91CB for <int-area@ietfa.amsl.com>; Wed, 29 May 2013 06:40:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.467
X-Spam-Level: 
X-Spam-Status: No, score=-103.467 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNRESOLVED_TEMPLATE=3.132, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hASHt24iTx5j for <int-area@ietfa.amsl.com>; Wed, 29 May 2013 06:40:22 -0700 (PDT)
Received: from exprod7og128.obsmtp.com (exprod7og128.obsmtp.com [64.18.2.121]) by ietfa.amsl.com (Postfix) with ESMTP id C5AF021F8FB6 for <int-area@ietf.org>; Wed, 29 May 2013 06:40:21 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob128.postini.com ([64.18.6.12]) with SMTP ID DSNKUaYFRKYfi7PC2C4yIf8IaRtJlUx5wwar@postini.com; Wed, 29 May 2013 06:40:21 PDT
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 29 May 2013 06:36:56 -0700
Received: from o365mail.juniper.net (207.17.137.149) by o365mail.juniper.net (172.24.192.60) with Microsoft SMTP Server id 14.1.355.2; Wed, 29 May 2013 06:36:56 -0700
Received: from DB8EHSOBE037.bigfish.com (213.199.154.188) by o365mail.juniper.net (207.17.137.149) with Microsoft SMTP Server (TLS) id 14.1.355.2; Wed, 29 May 2013 06:40:19 -0700
Received: from mail66-db8-R.bigfish.com (10.174.8.231) by DB8EHSOBE037.bigfish.com (10.174.4.100) with Microsoft SMTP Server id 14.1.225.23; Wed, 29 May 2013 13:36:54 +0000
Received: from mail66-db8 (localhost [127.0.0.1])	by mail66-db8-R.bigfish.com (Postfix) with ESMTP id 246D0640174	for <int-area@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Wed, 29 May 2013 13:36:54 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.238.5; KIP:(null); UIP:(null); (null); H:BY2PRD0512HT002.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -24
X-BigFish: PS-24(zz9371I936eI542I1432Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz1033IL17326ah8275dhz31h2a8h668h839h93fhd25hf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d07h1d0ch1d2eh1d3fh1dc1h1de9h1155h)
Received-SPF: softfail (mail66-db8: transitioning domain of juniper.net does not designate 157.56.238.5 as permitted sender) client-ip=157.56.238.5; envelope-from=rbonica@juniper.net; helo=BY2PRD0512HT002.namprd05.prod.outlook.com ; .outlook.com ; 
Received: from mail66-db8 (localhost.localdomain [127.0.0.1]) by mail66-db8 (MessageSwitch) id 1369834612699204_17109; Wed, 29 May 2013 13:36:52 +0000 (UTC)
Received: from DB8EHSMHS031.bigfish.com (unknown [10.174.8.240])	by mail66-db8.bigfish.com (Postfix) with ESMTP id 940EFC4004F	for <int-area@ietf.org>; Wed, 29 May 2013 13:36:52 +0000 (UTC)
Received: from BY2PRD0512HT002.namprd05.prod.outlook.com (157.56.238.5) by DB8EHSMHS031.bigfish.com (10.174.4.41) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 29 May 2013 13:36:51 +0000
Received: from BY2PRD0512MB653.namprd05.prod.outlook.com ([169.254.5.27]) by BY2PRD0512HT002.namprd05.prod.outlook.com ([10.255.243.35]) with mapi id 14.16.0311.000; Wed, 29 May 2013 13:36:39 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: Internet Area <int-area@ietf.org>
Thread-Topic: New Version Notification for draft-bonica-intarea-gre-mtu-00.txt
Thread-Index: AQHOXHFE+rFV8r4Gvkq/w+qmGi8xBZkcKdSA
Date: Wed, 29 May 2013 13:36:38 +0000
Message-ID: <2CF4CB03E2AA464BA0982EC92A02CE2509F187DD@BY2PRD0512MB653.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.232.2]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
Subject: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-00.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
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, 29 May 2013 13:40:28 -0000

Rm9sa3MsDQoNCklmIHlvdSBnZXQgYSBjaGFuY2UsIHBsZWFzZSBwcm92aWRlIGEgc2FuaXR5IGNo
ZWNrIG9uIHRoaXMgZG9jdW1lbnQuIEl0IGlzIHZlcnkgc2hvcnQsIHNvIGl0IHdvbid0IHRha2Ug
bXVjaCB0aW1lIHRvIHJldmlldy4NCg0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICBSb24NCg0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IGlu
dGVybmV0LWRyYWZ0c0BpZXRmLm9yZyBbbWFpbHRvOmludGVybmV0LWRyYWZ0c0BpZXRmLm9yZ10N
Cj4gU2VudDogV2VkbmVzZGF5LCBNYXkgMjksIDIwMTMgOTozNCBBTQ0KPiBUbzogUm9uYWxkIEJv
bmljYQ0KPiBTdWJqZWN0OiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9yIGRyYWZ0LWJvbmlj
YS1pbnRhcmVhLWdyZS1tdHUtDQo+IDAwLnR4dA0KPiANCj4gDQo+IEEgbmV3IHZlcnNpb24gb2Yg
SS1ELCBkcmFmdC1ib25pY2EtaW50YXJlYS1ncmUtbXR1LTAwLnR4dA0KPiBoYXMgYmVlbiBzdWNj
ZXNzZnVsbHkgc3VibWl0dGVkIGJ5IFJvbiBCb25pY2EgYW5kIHBvc3RlZCB0byB0aGUgSUVURg0K
PiByZXBvc2l0b3J5Lg0KPiANCj4gRmlsZW5hbWU6CSBkcmFmdC1ib25pY2EtaW50YXJlYS1ncmUt
bXR1DQo+IFJldmlzaW9uOgkgMDANCj4gVGl0bGU6CQkgR2VuZXJpYyBSb3V0aW5nIEVuY2Fwc3Vs
YXRpb24gKEdSRSkgRnJhZ21lbnRhdGlvbg0KPiBTdHJhdGVneQ0KPiBDcmVhdGlvbiBkYXRlOgkg
MjAxMy0wNS0yOQ0KPiBHcm91cDoJCSBJbmRpdmlkdWFsIFN1Ym1pc3Npb24NCj4gTnVtYmVyIG9m
IHBhZ2VzOiA4DQo+IFVSTDogICAgICAgICAgICAgaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5l
dC1kcmFmdHMvZHJhZnQtYm9uaWNhLQ0KPiBpbnRhcmVhLWdyZS1tdHUtMDAudHh0DQo+IFN0YXR1
czogICAgICAgICAgaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1ib25pY2Et
aW50YXJlYS0NCj4gZ3JlLW10dQ0KPiBIdG1saXplZDogICAgICAgIGh0dHA6Ly90b29scy5pZXRm
Lm9yZy9odG1sL2RyYWZ0LWJvbmljYS1pbnRhcmVhLWdyZS0NCj4gbXR1LTAwDQo+IA0KPiANCj4g
QWJzdHJhY3Q6DQo+ICAgIFRoaXMgbWVtbyBkb2N1bWVudHMgYSBHUkUgZnJhZ21lbnRhdGlvbiBz
dHJhdGVneSB1cG9uIHdoaWNoIG1hbnkNCj4gICAgdmVuZG9ycyBoYXZlIGNvbnZlcmdlZC4gIFNw
ZWNpZmljYWxseSwgaXQgZGVmaW5lcyBwcm9jZWR1cmVzIHRvIGJlDQo+ICAgIGV4ZWN1dGVkIGJ5
IEdSRSBpbmdyZXNzIHJvdXRlcnMuICBJdCBpcyBwdWJsaXNoZWQgc28gdGhhdCB0aG9zZQ0KPiAg
ICBidWlsZGluZyBuZXcgaW1wbGVtZW50YXRpb25zIHdpbGwgYmUgYXdhcmUgb2YgYmVzdCBjb21t
b24gcHJhY3RpY2UuDQo+ICAgIEl0IGlzIGFsc28gcHVibGlzaGVkIHNvIHRoYXQgdGhvc2UgYnVp
bGRpbmcgYXBwbGljYXRpb25zIG92ZXIgR1JFDQo+ICAgIHdpbGwgdW5kZXJzdGFuZCBob3cgR1JF
IHdvcmtzLg0KPiANCj4gDQo+IA0KPiANCj4gDQo+IFRoZSBJRVRGIFNlY3JldGFyaWF0DQo+IA0K
DQo=


From touch@isi.edu  Wed May 29 10:29:30 2013
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08E6921F90CD for <int-area@ietfa.amsl.com>; Wed, 29 May 2013 10:29:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mBnH7MM03Lcl for <int-area@ietfa.amsl.com>; Wed, 29 May 2013 10:29:25 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id CEE0121F9180 for <int-area@ietf.org>; Wed, 29 May 2013 10:29:19 -0700 (PDT)
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 r4THScPt016330 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 29 May 2013 10:28:38 -0700 (PDT)
Message-ID: <51A63AB8.1060401@isi.edu>
Date: Wed, 29 May 2013 10:28:24 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Ronald Bonica <rbonica@juniper.net>
References: <2CF4CB03E2AA464BA0982EC92A02CE2509F187DD@BY2PRD0512MB653.namprd05.prod.outlook.com>
In-Reply-To: <2CF4CB03E2AA464BA0982EC92A02CE2509F187DD@BY2PRD0512MB653.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
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-00.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
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, 29 May 2013 17:29:30 -0000

FWIW, I gave mine to Ron offline already.

Joe

On 5/29/2013 6:36 AM, Ronald Bonica wrote:
> Folks,
>
> If you get a chance, please provide a sanity check on this document. It is very short, so it won't take much time to review.
>
>                                           Ron
>
>
>> -----Original Message-----
>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>> Sent: Wednesday, May 29, 2013 9:34 AM
>> To: Ronald Bonica
>> Subject: New Version Notification for draft-bonica-intarea-gre-mtu-
>> 00.txt
>>
>>
>> A new version of I-D, draft-bonica-intarea-gre-mtu-00.txt
>> has been successfully submitted by Ron Bonica and posted to the IETF
>> repository.
>>
>> Filename:	 draft-bonica-intarea-gre-mtu
>> Revision:	 00
>> Title:		 Generic Routing Encapsulation (GRE) Fragmentation
>> Strategy
>> Creation date:	 2013-05-29
>> Group:		 Individual Submission
>> Number of pages: 8
>> URL:             http://www.ietf.org/internet-drafts/draft-bonica-
>> intarea-gre-mtu-00.txt
>> Status:          http://datatracker.ietf.org/doc/draft-bonica-intarea-
>> gre-mtu
>> Htmlized:        http://tools.ietf.org/html/draft-bonica-intarea-gre-
>> mtu-00
>>
>>
>> Abstract:
>>     This memo documents a GRE fragmentation strategy upon which many
>>     vendors have converged.  Specifically, it defines procedures to be
>>     executed by GRE ingress routers.  It is published so that those
>>     building new implementations will be aware of best common practice.
>>     It is also published so that those building applications over GRE
>>     will understand how GRE works.
>>
>>
>>
>>
>>
>> The IETF Secretariat
>>
>
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area
>

From linda.dunbar@huawei.com  Wed May 29 13:06:44 2013
Return-Path: <linda.dunbar@huawei.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C993E21F96B0 for <int-area@ietfa.amsl.com>; Wed, 29 May 2013 13:06:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OQfO+792GD9I for <int-area@ietfa.amsl.com>; Wed, 29 May 2013 13:06:39 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 606D121F96B4 for <int-area@ietf.org>; Wed, 29 May 2013 13:06:38 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ARX63517; Wed, 29 May 2013 20:06:37 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 29 May 2013 21:06:03 +0100
Received: from DFWEML405-HUB.china.huawei.com (10.193.5.102) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 29 May 2013 21:06:32 +0100
Received: from DFWEML509-MBX.china.huawei.com ([169.254.11.169]) by dfweml405-hub.china.huawei.com ([10.193.5.102]) with mapi id 14.01.0323.007; Wed, 29 May 2013 13:06:27 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: Ronald Bonica <rbonica@juniper.net>, Internet Area <int-area@ietf.org>
Thread-Topic: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-00.txt
Thread-Index: AQHOXHFE+rFV8r4Gvkq/w+qmGi8xBZkcKdSAgABps4A=
Date: Wed, 29 May 2013 20:06:27 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F645B3615C@dfweml509-mbx.china.huawei.com>
References: <2CF4CB03E2AA464BA0982EC92A02CE2509F187DD@BY2PRD0512MB653.namprd05.prod.outlook.com>
In-Reply-To: <2CF4CB03E2AA464BA0982EC92A02CE2509F187DD@BY2PRD0512MB653.namprd05.prod.outlook.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.153.203]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [Int-area] FW: New Version Notification for	draft-bonica-intarea-gre-mtu-00.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
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, 29 May 2013 20:06:44 -0000

Ron,=20

I do have a few questions and suggestion about the practices documented in =
the draft:

- Section 4.1, second paragraph:=20
why DF bit "MUST" set to 1  when the payload header has "0"? I would think =
default should be same as the "payload" DF setting.=20

- Section 5.1, last sentence: "The GRE egree router will forward the payloa=
d fragments to their ultimate destination where there will be reassembled"

The GRE egress router should reassemble the fragmented payloads before send=
ing to the destination.  In general, the network outside the Egress router =
should be same as the network before entering the Ingress router. If the da=
ta frame size is less than then MTU of the network before entering the Ingr=
ess router, the decapsulated frame size should be less than the MTU of the =
network outside the Egress router.=20

In addition, it is the Ingress node split the frame, the final destination =
may not be aware of how to reassemble the data frame.=20

- There should be two options when the encapsulated data frame exceeds MTU:=
 a) split the data frame to two smaller frames, with each frame being encap=
sulated; b) truncate the frame if the Egress node needs to receive the data=
 frame but doesn't have the capability to reassemble split frames.=20

Linda




> -----Original Message-----
> From: int-area-bounces@ietf.org [mailto:int-area-bounces@ietf.org] On
> Behalf Of Ronald Bonica
> Sent: Wednesday, May 29, 2013 8:37 AM
> To: Internet Area
> Subject: [Int-area] FW: New Version Notification for draft-bonica-
> intarea-gre-mtu-00.txt
>=20
> Folks,
>=20
> If you get a chance, please provide a sanity check on this document. It
> is very short, so it won't take much time to review.
>=20
>                                          Ron
>=20
>=20
> > -----Original Message-----
> > From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> > Sent: Wednesday, May 29, 2013 9:34 AM
> > To: Ronald Bonica
> > Subject: New Version Notification for draft-bonica-intarea-gre-mtu-
> > 00.txt
> >
> >
> > A new version of I-D, draft-bonica-intarea-gre-mtu-00.txt
> > has been successfully submitted by Ron Bonica and posted to the IETF
> > repository.
> >
> > Filename:	 draft-bonica-intarea-gre-mtu
> > Revision:	 00
> > Title:		 Generic Routing Encapsulation (GRE) Fragmentation
> > Strategy
> > Creation date:	 2013-05-29
> > Group:		 Individual Submission
> > Number of pages: 8
> > URL:             http://www.ietf.org/internet-drafts/draft-bonica-
> > intarea-gre-mtu-00.txt
> > Status:          http://datatracker.ietf.org/doc/draft-bonica-
> intarea-
> > gre-mtu
> > Htmlized:        http://tools.ietf.org/html/draft-bonica-intarea-gre-
> > mtu-00
> >
> >
> > Abstract:
> >    This memo documents a GRE fragmentation strategy upon which many
> >    vendors have converged.  Specifically, it defines procedures to be
> >    executed by GRE ingress routers.  It is published so that those
> >    building new implementations will be aware of best common practice.
> >    It is also published so that those building applications over GRE
> >    will understand how GRE works.
> >
> >
> >
> >
> >
> > The IETF Secretariat
> >
>=20
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area

From touch@isi.edu  Wed May 29 13:34:10 2013
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E821021F973A for <int-area@ietfa.amsl.com>; Wed, 29 May 2013 13:34:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.166
X-Spam-Level: 
X-Spam-Status: No, score=-105.166 tagged_above=-999 required=5 tests=[AWL=1.433, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z1OXjr4Ar-bT for <int-area@ietfa.amsl.com>; Wed, 29 May 2013 13:34:04 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 6956B21F9741 for <int-area@ietf.org>; Wed, 29 May 2013 13:33:59 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r4TKVxEY029880 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 29 May 2013 13:31:59 -0700 (PDT)
Message-ID: <51A665B1.40507@isi.edu>
Date: Wed, 29 May 2013 13:31:45 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Linda Dunbar <linda.dunbar@huawei.com>
References: <2CF4CB03E2AA464BA0982EC92A02CE2509F187DD@BY2PRD0512MB653.namprd05.prod.outlook.com> <4A95BA014132FF49AE685FAB4B9F17F645B3615C@dfweml509-mbx.china.huawei.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F645B3615C@dfweml509-mbx.china.huawei.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
Cc: Ronald Bonica <rbonica@juniper.net>, Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for	draft-bonica-intarea-gre-mtu-00.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
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, 29 May 2013 20:34:10 -0000

On 5/29/2013 1:06 PM, Linda Dunbar wrote:
> Ron,
>
> I do have a few questions and suggestion about the practices documented in the draft:
>
> - Section 4.1, second paragraph:
> why DF bit "MUST" set to 1  when the payload header has "0"? I would think default should be same as the "payload" DF setting.

DF in a tunnel header should be set to match the capability of that 
tunnel mechanism. Either the tunnel wants to find the MTU and match it 
or not; in the former case, it has to set DF=1 all the time.

For this doc, whether to set or copy the DF bit depends on whether PMTUD 
is supported on a given tunnel. If it is (whether PMTUD or PLMTUD), then 
set DF; otherwise, I agree - copy DF.

> - Section 5.1, last sentence: "The GRE egree router will forward the
> payload fragments to their ultimate destination where there will be
> reassembled"
>
> The GRE egress router should reassemble the fragmented payloads
> before sending to the destination. In general, the network outside
> the Egress router should be same as the network before entering the
> Ingress router. If the data frame size is less than then MTU of the
> network before entering the Ingress router, the decapsulated frame
> size should be less than the MTU of the network outside the Egress
> router.

I agree; my general recommendation has always been "the egress should 
always clean up any mess created by an ingress" - which means using 
"outer" fragmentation rather than "inner".

Yes, this can cause repeated frag/reassembly, but the alternative is to 
shift work to the end host, which I think is inappropriate. Further, 
this sort of clean-up is required by IPv6 and for IPv4 when when DF=1 on 
the inner packet anyway.

> In addition, it is the Ingress node split the frame, the final
> destination may not be aware of how to reassemble the data frame.

This is a spurious point; the information is there if the inner packet 
was fragmentable.

> - There should be two options when the encapsulated data frame
> exceeds MTU: a) split the data frame to two smaller frames, with each
> frame being encapsulated; b) truncate the frame if the Egress node
> needs to receive the data frame but doesn't have the capability to
> reassemble split frames.

There are two viable options:

	- fragment and reassemble (same as your option "a)" above)

	- drop the packet (and presumably send a signal upstream)

Sending a truncated frame serves no useful purpose.

Joe



From xuxiaohu@huawei.com  Thu May 30 00:02:49 2013
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0B3A21F96AA for <int-area@ietfa.amsl.com>; Thu, 30 May 2013 00:02:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.619
X-Spam-Level: **
X-Spam-Status: No, score=2.619 tagged_above=-999 required=5 tests=[AWL=-0.169,  BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339,  MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GquAqQaocapD for <int-area@ietfa.amsl.com>; Thu, 30 May 2013 00:02:16 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5AEFF21F9524 for <int-area@ietf.org>; Wed, 29 May 2013 23:58:45 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ATH78648; Thu, 30 May 2013 06:58:32 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 30 May 2013 07:57:58 +0100
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 30 May 2013 14:58:31 +0800
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.134]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.01.0323.007; Thu, 30 May 2013 14:58:23 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Joe Touch <touch@isi.edu>, Linda Dunbar <linda.dunbar@huawei.com>
Thread-Topic: [Int-area] FW: New Version Notification	for draft-bonica-intarea-gre-mtu-00.txt
Thread-Index: AQHOXKtSOs3MoCqFrEKhJeB/WjYkr5kcF5+AgAEsbdA=
Date: Thu, 30 May 2013 06:58:22 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE081C3BA8@NKGEML512-MBS.china.huawei.com>
References: <2CF4CB03E2AA464BA0982EC92A02CE2509F187DD@BY2PRD0512MB653.namprd05.prod.outlook.com> <4A95BA014132FF49AE685FAB4B9F17F645B3615C@dfweml509-mbx.china.huawei.com> <51A665B1.40507@isi.edu>
In-Reply-To: <51A665B1.40507@isi.edu>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.130]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: Ronald Bonica <rbonica@juniper.net>, Internet Area <int-area@ietf.org>
Subject: [Int-area] =?gb2312?b?tPC4tDogIEZXOiBOZXcgVmVyc2lvbiBOb3RpZmlj?= =?gb2312?b?YXRpb24JZm9yCWRyYWZ0LWJvbmljYS1pbnRhcmVhLWdyZS1tdHUtMDAudHh0?=
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 30 May 2013 07:02:52 -0000

DQoNCj4gLS0tLS3Tyrz+1K28/i0tLS0tDQo+ILeivP7IyzogaW50LWFyZWEtYm91bmNlc0BpZXRm
Lm9yZyBbbWFpbHRvOmludC1hcmVhLWJvdW5jZXNAaWV0Zi5vcmddILT6se0NCj4gSm9lIFRvdWNo
DQo+ILeiy83KsbzkOiAyMDEzxOo11MIzMMjVIDQ6MzINCj4gytW8/sjLOiBMaW5kYSBEdW5iYXIN
Cj4gs63LzTogUm9uYWxkIEJvbmljYTsgSW50ZXJuZXQgQXJlYQ0KPiDW98ziOiBSZTogW0ludC1h
cmVhXSBGVzogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvcg0KPiBkcmFmdC1ib25pY2EtaW50
YXJlYS1ncmUtbXR1LTAwLnR4dA0KPiANCj4gDQo+IA0KPiBPbiA1LzI5LzIwMTMgMTowNiBQTSwg
TGluZGEgRHVuYmFyIHdyb3RlOg0KPiA+IFJvbiwNCj4gPg0KPiA+IEkgZG8gaGF2ZSBhIGZldyBx
dWVzdGlvbnMgYW5kIHN1Z2dlc3Rpb24gYWJvdXQgdGhlIHByYWN0aWNlcyBkb2N1bWVudGVkIGlu
DQo+IHRoZSBkcmFmdDoNCj4gPg0KPiA+IC0gU2VjdGlvbiA0LjEsIHNlY29uZCBwYXJhZ3JhcGg6
DQo+ID4gd2h5IERGIGJpdCAiTVVTVCIgc2V0IHRvIDEgIHdoZW4gdGhlIHBheWxvYWQgaGVhZGVy
IGhhcyAiMCI/IEkgd291bGQgdGhpbmsNCj4gZGVmYXVsdCBzaG91bGQgYmUgc2FtZSBhcyB0aGUg
InBheWxvYWQiIERGIHNldHRpbmcuDQo+IA0KPiBERiBpbiBhIHR1bm5lbCBoZWFkZXIgc2hvdWxk
IGJlIHNldCB0byBtYXRjaCB0aGUgY2FwYWJpbGl0eSBvZiB0aGF0DQo+IHR1bm5lbCBtZWNoYW5p
c20uIEVpdGhlciB0aGUgdHVubmVsIHdhbnRzIHRvIGZpbmQgdGhlIE1UVSBhbmQgbWF0Y2ggaXQN
Cj4gb3Igbm90OyBpbiB0aGUgZm9ybWVyIGNhc2UsIGl0IGhhcyB0byBzZXQgREY9MSBhbGwgdGhl
IHRpbWUuDQo+IA0KPiBGb3IgdGhpcyBkb2MsIHdoZXRoZXIgdG8gc2V0IG9yIGNvcHkgdGhlIERG
IGJpdCBkZXBlbmRzIG9uIHdoZXRoZXIgUE1UVUQNCj4gaXMgc3VwcG9ydGVkIG9uIGEgZ2l2ZW4g
dHVubmVsLiBJZiBpdCBpcyAod2hldGhlciBQTVRVRCBvciBQTE1UVUQpLCB0aGVuDQo+IHNldCBE
Rjsgb3RoZXJ3aXNlLCBJIGFncmVlIC0gY29weSBERi4NCj4gDQo+ID4gLSBTZWN0aW9uIDUuMSwg
bGFzdCBzZW50ZW5jZTogIlRoZSBHUkUgZWdyZWUgcm91dGVyIHdpbGwgZm9yd2FyZCB0aGUNCj4g
PiBwYXlsb2FkIGZyYWdtZW50cyB0byB0aGVpciB1bHRpbWF0ZSBkZXN0aW5hdGlvbiB3aGVyZSB0
aGVyZSB3aWxsIGJlDQo+ID4gcmVhc3NlbWJsZWQiDQo+ID4NCj4gPiBUaGUgR1JFIGVncmVzcyBy
b3V0ZXIgc2hvdWxkIHJlYXNzZW1ibGUgdGhlIGZyYWdtZW50ZWQgcGF5bG9hZHMNCj4gPiBiZWZv
cmUgc2VuZGluZyB0byB0aGUgZGVzdGluYXRpb24uIEluIGdlbmVyYWwsIHRoZSBuZXR3b3JrIG91
dHNpZGUNCj4gPiB0aGUgRWdyZXNzIHJvdXRlciBzaG91bGQgYmUgc2FtZSBhcyB0aGUgbmV0d29y
ayBiZWZvcmUgZW50ZXJpbmcgdGhlDQo+ID4gSW5ncmVzcyByb3V0ZXIuIElmIHRoZSBkYXRhIGZy
YW1lIHNpemUgaXMgbGVzcyB0aGFuIHRoZW4gTVRVIG9mIHRoZQ0KPiA+IG5ldHdvcmsgYmVmb3Jl
IGVudGVyaW5nIHRoZSBJbmdyZXNzIHJvdXRlciwgdGhlIGRlY2Fwc3VsYXRlZCBmcmFtZQ0KPiA+
IHNpemUgc2hvdWxkIGJlIGxlc3MgdGhhbiB0aGUgTVRVIG9mIHRoZSBuZXR3b3JrIG91dHNpZGUg
dGhlIEVncmVzcw0KPiA+IHJvdXRlci4NCj4gDQo+IEkgYWdyZWU7IG15IGdlbmVyYWwgcmVjb21t
ZW5kYXRpb24gaGFzIGFsd2F5cyBiZWVuICJ0aGUgZWdyZXNzIHNob3VsZA0KPiBhbHdheXMgY2xl
YW4gdXAgYW55IG1lc3MgY3JlYXRlZCBieSBhbiBpbmdyZXNzIiAtIHdoaWNoIG1lYW5zIHVzaW5n
DQo+ICJvdXRlciIgZnJhZ21lbnRhdGlvbiByYXRoZXIgdGhhbiAiaW5uZXIiLg0KPiANCj4gWWVz
LCB0aGlzIGNhbiBjYXVzZSByZXBlYXRlZCBmcmFnL3JlYXNzZW1ibHksIGJ1dCB0aGUgYWx0ZXJu
YXRpdmUgaXMgdG8NCj4gc2hpZnQgd29yayB0byB0aGUgZW5kIGhvc3QsIHdoaWNoIEkgdGhpbmsg
aXMgaW5hcHByb3ByaWF0ZS4gRnVydGhlciwNCg0KUG9zdC1mcmFnbWVudGF0aW9uIGNvdWxkIGRl
Z3JhZGUgdGhlIHBlcmZvcm1hbmNlIG9uIHRoZSBlZ3Jlc3MgdHVubmVsIHBvaW50IGR1ZSB0byBz
b21lIHJlYXNvbiwgZS5nLiwgcGFja2V0IGRpc29yZGVyLiBUaGVyZWZvcmUsIHByZWZyYWdtZW50
YXRpb24gc2hvdWxkIGFsd2F5cyBiZSBwcmVmZXJyZWQgc2luY2UgaXQgY2FuIHNoaWZ0IHRoZSBy
ZWFzc2VtYmx5IHdvcmsgZnJvbSB0aGUgZWdyZXNzIHR1bm5lbCBwb2ludCB0byB0aGUgZW5kIGhv
c3RzLg0KDQo+IHRoaXMgc29ydCBvZiBjbGVhbi11cCBpcyByZXF1aXJlZCBieSBJUHY2IGFuZCBm
b3IgSVB2NCB3aGVuIHdoZW4gREY9MSBvbg0KPiB0aGUgaW5uZXIgcGFja2V0IGFueXdheS4NCg0K
SW4gdGhlIGFib3ZlIGNhc2UsIHRoZSBwYWNrZXQgc2hvdWxkIGJlIGRyb3BwZWQgYnkgdGhlIGlu
Z3Jlc3MgdHVubmVsIHBvaW50Lg0KDQpCZXN0IHJlZ2FyZHMsDQpYaWFvaHUNCg0KPiA+IEluIGFk
ZGl0aW9uLCBpdCBpcyB0aGUgSW5ncmVzcyBub2RlIHNwbGl0IHRoZSBmcmFtZSwgdGhlIGZpbmFs
DQo+ID4gZGVzdGluYXRpb24gbWF5IG5vdCBiZSBhd2FyZSBvZiBob3cgdG8gcmVhc3NlbWJsZSB0
aGUgZGF0YSBmcmFtZS4NCj4gDQo+IFRoaXMgaXMgYSBzcHVyaW91cyBwb2ludDsgdGhlIGluZm9y
bWF0aW9uIGlzIHRoZXJlIGlmIHRoZSBpbm5lciBwYWNrZXQNCj4gd2FzIGZyYWdtZW50YWJsZS4N
Cj4gDQo+ID4gLSBUaGVyZSBzaG91bGQgYmUgdHdvIG9wdGlvbnMgd2hlbiB0aGUgZW5jYXBzdWxh
dGVkIGRhdGEgZnJhbWUNCj4gPiBleGNlZWRzIE1UVTogYSkgc3BsaXQgdGhlIGRhdGEgZnJhbWUg
dG8gdHdvIHNtYWxsZXIgZnJhbWVzLCB3aXRoIGVhY2gNCj4gPiBmcmFtZSBiZWluZyBlbmNhcHN1
bGF0ZWQ7IGIpIHRydW5jYXRlIHRoZSBmcmFtZSBpZiB0aGUgRWdyZXNzIG5vZGUNCj4gPiBuZWVk
cyB0byByZWNlaXZlIHRoZSBkYXRhIGZyYW1lIGJ1dCBkb2Vzbid0IGhhdmUgdGhlIGNhcGFiaWxp
dHkgdG8NCj4gPiByZWFzc2VtYmxlIHNwbGl0IGZyYW1lcy4NCj4gDQo+IFRoZXJlIGFyZSB0d28g
dmlhYmxlIG9wdGlvbnM6DQo+IA0KPiAJLSBmcmFnbWVudCBhbmQgcmVhc3NlbWJsZSAoc2FtZSBh
cyB5b3VyIG9wdGlvbiAiYSkiIGFib3ZlKQ0KPiANCj4gCS0gZHJvcCB0aGUgcGFja2V0IChhbmQg
cHJlc3VtYWJseSBzZW5kIGEgc2lnbmFsIHVwc3RyZWFtKQ0KPiANCj4gU2VuZGluZyBhIHRydW5j
YXRlZCBmcmFtZSBzZXJ2ZXMgbm8gdXNlZnVsIHB1cnBvc2UuDQo+IA0KPiBKb2UNCj4gDQo+IA0K
PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBJbnQt
YXJlYSBtYWlsaW5nIGxpc3QNCj4gSW50LWFyZWFAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0
Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pbnQtYXJlYQ0K

From mohamed.boucadair@orange.com  Thu May 30 01:51:23 2013
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CE6B21F92FB for <int-area@ietfa.amsl.com>; Thu, 30 May 2013 01:51:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kMQjrr61VA3C for <int-area@ietfa.amsl.com>; Thu, 30 May 2013 01:51:18 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id 10CFA21F8F3E for <int-area@ietf.org>; Thu, 30 May 2013 01:51:18 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm10.si.francetelecom.fr (ESMTP service) with ESMTP id 7E540264B38 for <int-area@ietf.org>; Thu, 30 May 2013 10:51:17 +0200 (CEST)
Received: from PUEXCH41.nanterre.francetelecom.fr (unknown [10.101.44.30]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 65DE323804B for <int-area@ietf.org>; Thu, 30 May 2013 10:51:17 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.12]) by PUEXCH41.nanterre.francetelecom.fr ([10.101.44.30]) with mapi; Thu, 30 May 2013 10:51:12 +0200
From: <mohamed.boucadair@orange.com>
To: "Internet Area (int-area@ietf.org)" <int-area@ietf.org>
Date: Thu, 30 May 2013 10:51:11 +0200
Thread-Topic: I-D Action: draft-boucadair-connectivity-provisioning-protocol-00.txt
Thread-Index: Ac5cdx15DRY95yU0SOKTnbcTWQqlUwAm5ncg
Message-ID: <94C682931C08B048B7A8645303FDC9F36ED3A082A3@PUEXCB1B.nanterre.francetelecom.fr>
References: <20130529141609.7128.15421.idtracker@ietfa.amsl.com>
In-Reply-To: <20130529141609.7128.15421.idtracker@ietfa.amsl.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.5.30.81223
Subject: [Int-area] TR: I-D Action: draft-boucadair-connectivity-provisioning-protocol-00.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 30 May 2013 08:51:23 -0000

Dear all,

I'm forwarding this document to this list as it may be of your interest.

Comments are more than welcome.
Cheers,
Med

-----Message d'origine-----
De=A0: i-d-announce-bounces@ietf.org [mailto:i-d-announce-bounces@ietf.org]=
 De la part de internet-drafts@ietf.org
Envoy=E9=A0: mercredi 29 mai 2013 16:16
=C0=A0: i-d-announce@ietf.org
Objet=A0: I-D Action: draft-boucadair-connectivity-provisioning-protocol-00=
.txt


A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.


	Title           : Connectivity Provisioning Negotiation Protocol (CPNP)
	Author(s)       : Mohamed Boucadair
                          Christian Jacquenet
	Filename        : draft-boucadair-connectivity-provisioning-protocol-00.tx=
t
	Pages           : 34
	Date            : 2013-05-29

Abstract:
   This document specifies the Connectivity Provisioning Negotiation
   Protocol (CPNP) which is used to facilitate the dynamic negotiation
   of connectivity provisioning parameters between a Customer and a
   Provider.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-boucadair-connectivity-provisioning-=
protocol

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-boucadair-connectivity-provisioning-protoc=
ol-00


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 rbonica@juniper.net  Thu May 30 07:56:14 2013
Return-Path: <rbonica@juniper.net>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A6A821F8765 for <int-area@ietfa.amsl.com>; Thu, 30 May 2013 07:56:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.467
X-Spam-Level: 
X-Spam-Status: No, score=-103.467 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNRESOLVED_TEMPLATE=3.132, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eynzjDqgp-sj for <int-area@ietfa.amsl.com>; Thu, 30 May 2013 07:56:05 -0700 (PDT)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163]) by ietfa.amsl.com (Postfix) with ESMTP id B9E0B21F871C for <int-area@ietf.org>; Thu, 30 May 2013 07:56:04 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP ID DSNKUadog1AtJE6simaMnQ9+OrO3PdwROf5w@postini.com; Thu, 30 May 2013 07:56:04 PDT
Received: from P-CLDFE01-HQ.jnpr.net (172.24.192.59) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 30 May 2013 07:54:18 -0700
Received: from o365mail.juniper.net (207.17.137.149) by o365mail.juniper.net (172.24.192.59) with Microsoft SMTP Server id 14.1.355.2; Thu, 30 May 2013 07:54:17 -0700
Received: from DB8EHSOBE038.bigfish.com (213.199.154.188) by o365mail.juniper.net (207.17.137.149) with Microsoft SMTP Server (TLS) id 14.1.355.2; Thu, 30 May 2013 07:57:38 -0700
Received: from mail9-db8-R.bigfish.com (10.174.8.239) by DB8EHSOBE038.bigfish.com (10.174.4.101) with Microsoft SMTP Server id 14.1.225.23; Thu, 30 May 2013 14:54:15 +0000
Received: from mail9-db8 (localhost [127.0.0.1])	by mail9-db8-R.bigfish.com (Postfix) with ESMTP id C0C19800A3	for <int-area@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Thu, 30 May 2013 14:54:15 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.242.197; KIP:(null); UIP:(null); (null); H:BL2PRD0512HT004.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -25
X-BigFish: PS-25(zz9371I936eI148cI542I1432Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz1033IL17326ah8275dhz31h2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1155h)
Received-SPF: softfail (mail9-db8: transitioning domain of juniper.net does not designate 157.56.242.197 as permitted sender) client-ip=157.56.242.197; envelope-from=rbonica@juniper.net; helo=BL2PRD0512HT004.namprd05.prod.outlook.com ; .outlook.com ; 
Received: from mail9-db8 (localhost.localdomain [127.0.0.1]) by mail9-db8 (MessageSwitch) id 1369925654427619_17005; Thu, 30 May 2013 14:54:14 +0000 (UTC)
Received: from DB8EHSMHS032.bigfish.com (unknown [10.174.8.235])	by mail9-db8.bigfish.com (Postfix) with ESMTP id 64E03380052; Thu, 30 May 2013 14:54:14 +0000 (UTC)
Received: from BL2PRD0512HT004.namprd05.prod.outlook.com (157.56.242.197) by DB8EHSMHS032.bigfish.com (10.174.4.42) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 30 May 2013 14:54:12 +0000
Received: from BL2PRD0512MB646.namprd05.prod.outlook.com ([169.254.9.219]) by BL2PRD0512HT004.namprd05.prod.outlook.com ([10.255.233.37]) with mapi id 14.16.0311.000; Thu, 30 May 2013 14:54:05 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: Linda Dunbar <linda.dunbar@huawei.com>, Internet Area <int-area@ietf.org>
Thread-Topic: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-00.txt
Thread-Index: AQHOXKgY1rKVV58TzkKTHyI6yZ75jZkdw8vA
Date: Thu, 30 May 2013 14:54:04 +0000
Message-ID: <2CF4CB03E2AA464BA0982EC92A02CE2509F276DC@BL2PRD0512MB646.namprd05.prod.outlook.com>
References: <2CF4CB03E2AA464BA0982EC92A02CE2509F187DD@BY2PRD0512MB653.namprd05.prod.outlook.com> <4A95BA014132FF49AE685FAB4B9F17F645B3615C@dfweml509-mbx.china.huawei.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F645B3615C@dfweml509-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.232.2]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%HUAWEI.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
Subject: Re: [Int-area] FW: New Version Notification for	draft-bonica-intarea-gre-mtu-00.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 30 May 2013 14:56:14 -0000

Hi Linda,

Thanks for reading the document. Comments inline......

> -----Original Message-----
> From: Linda Dunbar [mailto:linda.dunbar@huawei.com]
> Sent: Wednesday, May 29, 2013 4:06 PM
> To: Ronald Bonica; Internet Area
> Subject: RE: [Int-area] FW: New Version Notification for draft-bonica-
> intarea-gre-mtu-00.txt
>=20
> Ron,
>=20
> I do have a few questions and suggestion about the practices documented
> in the draft:
>=20
> - Section 4.1, second paragraph:
> why DF bit "MUST" set to 1  when the payload header has "0"? I would
> think default should be same as the "payload" DF setting.

The actual text of the document is:

"When the GRE ingress router tunnels an IPv4 payload over IPv4, and the DF =
Bit in the payload header is set to 0 (May Fragment), **by default**, the G=
RE ingress router MUST set the DF bit in the delivery header to 1.  However=
, implementations MAY include a configuration option that allows the DF bit=
 to be copied from the payload header to the delivery header."

We say this because we want to avoid reassembly in the GRE egress router, a=
nd in order to avoid that, we need to avoid fragmentation by tunnel interio=
r routers.

However, this is only a default behavior. If an operator doesn't mind reass=
embly on the GRE egress router, there may be a configuration knob that allo=
ws the DF-bit to be copied from the payload header to the delivery header. =
However, operators should use that knob only if that is really what they wa=
nt to do.


>=20
> - Section 5.1, last sentence: "The GRE egree router will forward the
> payload fragments to their ultimate destination where there will be
> reassembled"
>=20
> The GRE egress router should reassemble the fragmented payloads before
> sending to the destination.  In general, the network outside the Egress
> router should be same as the network before entering the Ingress
> router. If the data frame size is less than then MTU of the network
> before entering the Ingress router, the decapsulated frame size should
> be less than the MTU of the network outside the Egress router.
>=20
> In addition, it is the Ingress node split the frame, the final
> destination may not be aware of how to reassemble the data frame.
>=20

Just to be sure that we aren't talking past each other, let's ensure that w=
e are talking about the same scenario. The GRE egress router receives
complete, non-fragmented packets, containing fragmented payloads. So, if th=
e deliver header is IPv4, its fragment offset is equal to 0 and its MF-bit =
is also set to 0. If the delivery header is IPv6, it does not contain a fra=
gment header. However, the payload is a single fragment of a larger packet.

Are we talking about the same scenario?

If so, it would be undesirable for the egress router to attempt reassembly =
for the following reasons:

- There are conditions in which the payload destination will be able to rea=
ssemble the packet, but the GRE ingress router cannot. For example, assume =
that the packet was fragmented several hops before entering the GRE tunnel.=
 One fragment traversed the GRE tunnel, but another fragment traversed anot=
her path, avoiding the tunnel. In this case, the tunnel egress router can't=
 reassemble the packet, because all of the fragments will not pass through =
it. However, the destination host can reassemble the packet.

- Even if the GRE egress router could reassemble he packet, it is preferabl=
e to execute the computationally expensive reassembly procedure at the endp=
oint.

> - There should be two options when the encapsulated data frame exceeds
> MTU: a) split the data frame to two smaller frames, with each frame
> being encapsulated;

This is the option that the draft currently offers. (Or am I misunderstandi=
ng your words?)

 b) truncate the frame if the Egress node needs to
> receive the data frame but doesn't have the capability to reassemble
> split frames.

I don't understand this option. Are you suggesting that we deliver the begi=
nning of the payload packet and discard the rest? I doubt if that is what y=
ou mean, but that is how I currently interpret your words.

                                           Ron

>=20
> Linda
>=20
>=20
>=20
>=20
> > -----Original Message-----
> > From: int-area-bounces@ietf.org [mailto:int-area-bounces@ietf.org] On
> > Behalf Of Ronald Bonica
> > Sent: Wednesday, May 29, 2013 8:37 AM
> > To: Internet Area
> > Subject: [Int-area] FW: New Version Notification for draft-bonica-
> > intarea-gre-mtu-00.txt
> >
> > Folks,
> >
> > If you get a chance, please provide a sanity check on this document.
> > It is very short, so it won't take much time to review.
> >
> >                                          Ron
> >
> >
> > > -----Original Message-----
> > > From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> > > Sent: Wednesday, May 29, 2013 9:34 AM
> > > To: Ronald Bonica
> > > Subject: New Version Notification for draft-bonica-intarea-gre-mtu-
> > > 00.txt
> > >
> > >
> > > A new version of I-D, draft-bonica-intarea-gre-mtu-00.txt
> > > has been successfully submitted by Ron Bonica and posted to the
> IETF
> > > repository.
> > >
> > > Filename:	 draft-bonica-intarea-gre-mtu
> > > Revision:	 00
> > > Title:		 Generic Routing Encapsulation (GRE) Fragmentation
> > > Strategy
> > > Creation date:	 2013-05-29
> > > Group:		 Individual Submission
> > > Number of pages: 8
> > > URL:             http://www.ietf.org/internet-drafts/draft-bonica-
> > > intarea-gre-mtu-00.txt
> > > Status:          http://datatracker.ietf.org/doc/draft-bonica-
> > intarea-
> > > gre-mtu
> > > Htmlized:        http://tools.ietf.org/html/draft-bonica-intarea-
> gre-
> > > mtu-00
> > >
> > >
> > > Abstract:
> > >    This memo documents a GRE fragmentation strategy upon which many
> > >    vendors have converged.  Specifically, it defines procedures to
> be
> > >    executed by GRE ingress routers.  It is published so that those
> > >    building new implementations will be aware of best common
> practice.
> > >    It is also published so that those building applications over
> GRE
> > >    will understand how GRE works.
> > >
> > >
> > >
> > >
> > >
> > > The IETF Secretariat
> > >
> >
> > _______________________________________________
> > Int-area mailing list
> > Int-area@ietf.org
> > https://www.ietf.org/mailman/listinfo/int-area



From linda.dunbar@huawei.com  Thu May 30 15:44:46 2013
Return-Path: <linda.dunbar@huawei.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC26921F91A5 for <int-area@ietfa.amsl.com>; Thu, 30 May 2013 15:44:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IEp04sVt7xrQ for <int-area@ietfa.amsl.com>; Thu, 30 May 2013 15:44:42 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 36BD821F8EBD for <int-area@ietf.org>; Thu, 30 May 2013 15:44:40 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ARY57460; Thu, 30 May 2013 22:38:29 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 30 May 2013 23:37:53 +0100
Received: from DFWEML406-HUB.china.huawei.com (10.193.5.131) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 31 May 2013 06:38:28 +0800
Received: from DFWEML509-MBX.china.huawei.com ([169.254.11.169]) by dfweml406-hub.china.huawei.com ([10.193.5.131]) with mapi id 14.01.0323.007; Thu, 30 May 2013 15:38:25 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: Ronald Bonica <rbonica@juniper.net>, Internet Area <int-area@ietf.org>
Thread-Topic: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-00.txt
Thread-Index: AQHOXHFE+rFV8r4Gvkq/w+qmGi8xBZkcKdSAgABps4CAAbP9AIAACI+Q
Date: Thu, 30 May 2013 22:38:23 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F645B368F6@dfweml509-mbx.china.huawei.com>
References: <2CF4CB03E2AA464BA0982EC92A02CE2509F187DD@BY2PRD0512MB653.namprd05.prod.outlook.com> <4A95BA014132FF49AE685FAB4B9F17F645B3615C@dfweml509-mbx.china.huawei.com> <2CF4CB03E2AA464BA0982EC92A02CE2509F276DC@BL2PRD0512MB646.namprd05.prod.outlook.com>
In-Reply-To: <2CF4CB03E2AA464BA0982EC92A02CE2509F276DC@BL2PRD0512MB646.namprd05.prod.outlook.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.192.11.210]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [Int-area] FW: New Version Notification for	draft-bonica-intarea-gre-mtu-00.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 30 May 2013 22:44:47 -0000

Ron,=20

Comments are inserted below:

> -----Original Message-----
>=20
> Just to be sure that we aren't talking past each other, let's ensure
> that we are talking about the same scenario. The GRE egress router
> receives
> complete, non-fragmented packets, containing fragmented payloads.=20

[Linda] The scenario I am talking about is:=20
   The packet arriving at the Ingress node is has packet size less than the=
 MTU. When the ingress node adds the GRE header, the new packet size exceed=
s the MTU. When this happens, the Ingress node has to break the received th=
e packet to two (half) frames, encapsulate each half frame with proper GRE =
header, and send two separate encapsulated frames to Egress node.=20


Is this same as your scenario?  From your description below, it doesn't sou=
nd like the same.=20
If it not the same, this scenario should be included in the draft. I can pr=
ovide a section to describe this scenario and proper processing in Ingress =
node and Egress node.=20

Under my scenario, the Egress node needs to reassemble the two half frames =
before sending to the destination because each half frame is not a complete=
 IP packet.=20




>
>So,
> if the deliver header is IPv4, its fragment offset is equal to 0 and
> its MF-bit is also set to 0. If the delivery header is IPv6, it does
> not contain a fragment header. However, the payload is a single
> fragment of a larger packet.
>=20
> Are we talking about the same scenario?
>=20
> If so, it would be undesirable for the egress router to attempt
> reassembly for the following reasons:
>=20
> - There are conditions in which the payload destination will be able to
> reassemble the packet, but the GRE ingress router cannot. For example,
> assume that the packet was fragmented several hops before entering the
> GRE tunnel. One fragment traversed the GRE tunnel, but another fragment
> traversed another path, avoiding the tunnel. In this case, the tunnel
> egress router can't reassemble the packet, because all of the fragments
> will not pass through it. However, the destination host can reassemble
> the packet.
>=20
> - Even if the GRE egress router could reassemble he packet, it is
> preferable to execute the computationally expensive reassembly
> procedure at the endpoint.
>=20
> > - There should be two options when the encapsulated data frame
> exceeds
> > MTU: a) split the data frame to two smaller frames, with each frame
> > being encapsulated;
>=20
> This is the option that the draft currently offers. (Or am I
> misunderstanding your words?)
>=20
>  b) truncate the frame if the Egress node needs to
> > receive the data frame but doesn't have the capability to reassemble
> > split frames.
>=20
> I don't understand this option. Are you suggesting that we deliver the
> beginning of the payload packet and discard the rest? I doubt if that
> is what you mean, but that is how I currently interpret your words.
>=20
>                                            Ron
>=20
> >
> > Linda
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: int-area-bounces@ietf.org [mailto:int-area-bounces@ietf.org]
> On
> > > Behalf Of Ronald Bonica
> > > Sent: Wednesday, May 29, 2013 8:37 AM
> > > To: Internet Area
> > > Subject: [Int-area] FW: New Version Notification for draft-bonica-
> > > intarea-gre-mtu-00.txt
> > >
> > > Folks,
> > >
> > > If you get a chance, please provide a sanity check on this document.
> > > It is very short, so it won't take much time to review.
> > >
> > >                                          Ron
> > >
> > >
> > > > -----Original Message-----
> > > > From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> > > > Sent: Wednesday, May 29, 2013 9:34 AM
> > > > To: Ronald Bonica
> > > > Subject: New Version Notification for draft-bonica-intarea-gre-
> mtu-
> > > > 00.txt
> > > >
> > > >
> > > > A new version of I-D, draft-bonica-intarea-gre-mtu-00.txt
> > > > has been successfully submitted by Ron Bonica and posted to the
> > IETF
> > > > repository.
> > > >
> > > > Filename:	 draft-bonica-intarea-gre-mtu
> > > > Revision:	 00
> > > > Title:		 Generic Routing Encapsulation (GRE)
> Fragmentation
> > > > Strategy
> > > > Creation date:	 2013-05-29
> > > > Group:		 Individual Submission
> > > > Number of pages: 8
> > > > URL:             http://www.ietf.org/internet-drafts/draft-
> bonica-
> > > > intarea-gre-mtu-00.txt
> > > > Status:          http://datatracker.ietf.org/doc/draft-bonica-
> > > intarea-
> > > > gre-mtu
> > > > Htmlized:        http://tools.ietf.org/html/draft-bonica-intarea-
> > gre-
> > > > mtu-00
> > > >
> > > >
> > > > Abstract:
> > > >    This memo documents a GRE fragmentation strategy upon which
> many
> > > >    vendors have converged.  Specifically, it defines procedures
> to
> > be
> > > >    executed by GRE ingress routers.  It is published so that
> those
> > > >    building new implementations will be aware of best common
> > practice.
> > > >    It is also published so that those building applications over
> > GRE
> > > >    will understand how GRE works.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > The IETF Secretariat
> > > >
> > >
> > > _______________________________________________
> > > Int-area mailing list
> > > Int-area@ietf.org
> > > https://www.ietf.org/mailman/listinfo/int-area
>=20


From rbonica@juniper.net  Fri May 31 06:10:20 2013
Return-Path: <rbonica@juniper.net>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0823B21F95FA for <int-area@ietfa.amsl.com>; Fri, 31 May 2013 06:10:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.467
X-Spam-Level: 
X-Spam-Status: No, score=-103.467 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNRESOLVED_TEMPLATE=3.132, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KfBvSVdVTwfg for <int-area@ietfa.amsl.com>; Fri, 31 May 2013 06:10:13 -0700 (PDT)
Received: from exprod7og120.obsmtp.com (exprod7og120.obsmtp.com [64.18.2.18]) by ietfa.amsl.com (Postfix) with ESMTP id 2450D21F949D for <int-area@ietf.org>; Fri, 31 May 2013 06:10:13 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob120.postini.com ([64.18.6.12]) with SMTP ID DSNKUaihNAki+q6krsrBVkWQZu7IcfaV+oLh@postini.com; Fri, 31 May 2013 06:10:13 PDT
Received: from P-CLDFE01-HQ.jnpr.net (172.24.192.59) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 31 May 2013 06:05:41 -0700
Received: from o365mail.juniper.net (207.17.137.224) by o365mail.juniper.net (172.24.192.59) with Microsoft SMTP Server id 14.1.355.2; Fri, 31 May 2013 06:05:41 -0700
Received: from tx2outboundpool.messaging.microsoft.com (65.55.88.11) by o365mail.juniper.net (207.17.137.224) with Microsoft SMTP Server (TLS) id 14.1.355.2; Fri, 31 May 2013 06:16:21 -0700
Received: from mail161-tx2-R.bigfish.com (10.9.14.254) by TX2EHSOBE006.bigfish.com (10.9.40.26) with Microsoft SMTP Server id 14.1.225.23; Fri, 31 May 2013 13:05:40 +0000
Received: from mail161-tx2 (localhost [127.0.0.1])	by mail161-tx2-R.bigfish.com (Postfix) with ESMTP id 7AAEFE0148	for <int-area@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Fri, 31 May 2013 13:05:40 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.238.5; KIP:(null); UIP:(null); (null); H:BY2PRD0512HT002.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -1
X-BigFish: PS-1(zz1432Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzzz31h2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1155h)
Received-SPF: softfail (mail161-tx2: transitioning domain of juniper.net does not designate 157.56.238.5 as permitted sender) client-ip=157.56.238.5; envelope-from=rbonica@juniper.net; helo=BY2PRD0512HT002.namprd05.prod.outlook.com ; .outlook.com ; 
Received: from mail161-tx2 (localhost.localdomain [127.0.0.1]) by mail161-tx2 (MessageSwitch) id 1370005539261174_27292; Fri, 31 May 2013 13:05:39 +0000 (UTC)
Received: from TX2EHSMHS023.bigfish.com (unknown [10.9.14.253])	by mail161-tx2.bigfish.com (Postfix) with ESMTP id 22C7518008A; Fri, 31 May 2013 13:05:39 +0000 (UTC)
Received: from BY2PRD0512HT002.namprd05.prod.outlook.com (157.56.238.5) by TX2EHSMHS023.bigfish.com (10.9.99.123) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 31 May 2013 13:05:37 +0000
Received: from BY2PRD0512MB653.namprd05.prod.outlook.com ([169.254.5.27]) by BY2PRD0512HT002.namprd05.prod.outlook.com ([10.255.243.35]) with mapi id 14.16.0311.000; Fri, 31 May 2013 13:05:37 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: Linda Dunbar <linda.dunbar@huawei.com>, Internet Area <int-area@ietf.org>
Thread-Topic: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-00.txt
Thread-Index: AQHOXKgY1rKVV58TzkKTHyI6yZ75jZkdw8vAgACPrYCAAOtNkA==
Date: Fri, 31 May 2013 13:05:36 +0000
Message-ID: <2CF4CB03E2AA464BA0982EC92A02CE2509F35114@BY2PRD0512MB653.namprd05.prod.outlook.com>
References: <2CF4CB03E2AA464BA0982EC92A02CE2509F187DD@BY2PRD0512MB653.namprd05.prod.outlook.com> <4A95BA014132FF49AE685FAB4B9F17F645B3615C@dfweml509-mbx.china.huawei.com> <2CF4CB03E2AA464BA0982EC92A02CE2509F276DC@BL2PRD0512MB646.namprd05.prod.outlook.com> <4A95BA014132FF49AE685FAB4B9F17F645B368F6@dfweml509-mbx.china.huawei.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F645B368F6@dfweml509-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.232.2]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%HUAWEI.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
Subject: Re: [Int-area] FW: New Version Notification for	draft-bonica-intarea-gre-mtu-00.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
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, 31 May 2013 13:10:20 -0000

> >
> > Just to be sure that we aren't talking past each other, let's ensure
> > that we are talking about the same scenario. The GRE egress router
> > receives complete, non-fragmented packets, containing fragmented
> > payloads.
>=20
> [Linda] The scenario I am talking about is:
>    The packet arriving at the Ingress node is has packet size less than
> the MTU. When the ingress node adds the GRE header, the new packet size
> exceeds the MTU. When this happens, the Ingress node has to break the
> received the packet to two (half) frames, encapsulate each half frame
> with proper GRE header, and send two separate encapsulated frames to
> Egress node.
>=20
>=20
> Is this same as your scenario?  From your description below, it doesn't
> sound like the same.
> If it not the same, this scenario should be included in the draft. I
> can provide a section to describe this scenario and proper processing
> in Ingress node and Egress node.
>=20
> Under my scenario, the Egress node needs to reassemble the two half
> frames before sending to the destination because each half frame is not
> a complete IP packet.
>=20
>=20

Hi Linda,

The scenarios are nearly the same. In the scenario that I describe, packet =
(size > TMTU). In the scenario that you describe (MTU > packet size > TMTU)=
. The difference between the two scenarios isn't significant. You should ge=
t the same behavior either way.

Given this scenario, the GRE ingress has the following choices:

1) fragment the payload and forward each payload fragment through the tunne=
l. The egress receives N complete, non-fragmented packets. Each of those pa=
ckets contains a fragment of the payload. The egress forwards the fragments=
 to the payload destination for reassembly.
2) do not fragment the payload. Alternatively, forward it through the tunne=
l, causing the delivery (outer) packet to be fragmented.  The tunnel egress=
 router reassembles the fragments of the delivery packet and forwards the p=
ayload to its destination.

Today, most implementations do #1, because reassembly is computationally ex=
pensive and they want to push computationally expensive activities out to t=
he endpoint.

One might argue that there are advantages to pros and cons of each strategy=
. While I am not averse to documenting those, the purpose of this document =
existing practice. It is not to change how people implement GRE.

                                                                        Ron



From Dirk.von-Hugo@telekom.de  Wed May 29 08:11:11 2013
Return-Path: <Dirk.von-Hugo@telekom.de>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3D0221F88B6; Wed, 29 May 2013 08:11:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uEjHFPDE4tdQ; Wed, 29 May 2013 08:11:07 -0700 (PDT)
Received: from tcmail43.telekom.de (tcmail43.telekom.de [80.149.113.173]) by ietfa.amsl.com (Postfix) with ESMTP id B09EE21F8825; Wed, 29 May 2013 08:11:05 -0700 (PDT)
Received: from he111631.emea1.cds.t-internal.com ([10.134.93.23]) by tcmail41.telekom.de with ESMTP/TLS/AES128-SHA; 29 May 2013 17:11:03 +0200
Received: from HE113484.emea1.cds.t-internal.com ([10.134.93.124]) by HE111631.emea1.cds.t-internal.com ([::1]) with mapi; Wed, 29 May 2013 17:11:02 +0200
From: <Dirk.von-Hugo@telekom.de>
To: <mohamed.boucadair@orange.com>, <jshire@hyduke.com>, <fmc@ietf.org>, <int-area@ietf.org>
Date: Wed, 29 May 2013 17:11:01 +0200
Thread-Topic: draft-boucadair-intarea-host-identifier-scenarios
Thread-Index: Ac5LMjyqGqkODLucTvmk2Pl+E8NMBwRSW5PQ
Message-ID: <05C81A773E48DD49B181B04BA21A342A2BBFB11613@HE113484.emea1.cds.t-internal.com>
References: <94C682931C08B048B7A8645303FDC9F36ECE1436BE@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36ECE1436BE@PUEXCB1B.nanterre.francetelecom.fr>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 31 May 2013 07:53:31 -0700
Cc: draft-boucadair-intarea-host-identifier-scenarios@tools.ietf.org
Subject: Re: [Int-area] draft-boucadair-intarea-host-identifier-scenarios
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
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, 29 May 2013 15:11:12 -0000

Hi Med, all,
I see also the section 3.7 on femto cells with high security demands for tu=
nneled (mobile) data via IPSec through the fixed network.

Another question is whether to include also a scenario for NAT46 addressing=
 IPv4 clients at end user nodes connected to both IPv6 RGW and IPv6 access =
network?  I think while many operators are starting to deploy IPv6 in their=
 core and aggregation networks there will always be (maybe old fashioned) c=
ustomers which continue to use their available equipment, e.g. for telephon=
y.
Perhaps this is already handled, e.g. in UC 3.6, but I couldn't find NAT46 =
to be mentioned. Did I miss something?

What do you think?
Thanks!

Best regards
Dirk
-----Original Message-----
From: fmc-bounces@ietf.org [mailto:fmc-bounces@ietf.org] On Behalf Of moham=
ed.boucadair@orange.com
Sent: Dienstag, 7. Mai 2013 16:51
To: 'Joshua Shire'; fmc@ietf.org; int-area@ietf.org
Cc: draft-boucadair-intarea-host-identifier-scenarios@tools.ietf.org
Subject: Re: [fmc] draft-boucadair-intarea-host-identifier-scenarios

Dear Joshua,

Apologies for the delay to answer this message.

I see your point. I will add it to the list of items to be considered for t=
he next iteration of the document.=20

BTW, -03 already included some of requirements which cover security aspects=
 (see for instance REQ#1, REQ#2, REQ#3, REQ#9). Once we have a stable requi=
rements list, we will identify the requirements which are valid for each us=
e case: http://tools.ietf.org/html/draft-boucadair-intarea-host-identifier-=
scenarios-03#section-4.1=20

Cheers,
Med

>-----Message d'origine-----
>De : Joshua Shire [mailto:jshire@hyduke.com]=20
>Envoy=E9 : vendredi 25 janvier 2013 08:17
>=C0 : BOUCADAIR Mohamed OLNC/OLN; fmc@ietf.org; int-area@ietf.org
>Cc : draft-boucadair-intarea-host-identifier-scenarios@tools.ietf.org
>Objet : RE: draft-boucadair-intarea-host-identifier-scenarios
>
>Hello,
>
>I do not believe a pointer to=20
>http://tools.ietf.org/html/draft-ietf-intarea-nat-reveal-analys
>is-04#section-3  will be satisfactory for the security=20
>considerations section.=20
>
>http://www.ietf.org/rfc/rfc3552.txt  states that when writing=20
>a security considerations section, the process "...should be=20
>approached as an effort to perform "due diligence" in=20
>describing all known or foreseeable risks and threats to=20
>potential implementers and users." Normally we see RFCs=20
>describing more applied topics such as protocols, so the=20
>specific language and examples given in the above mentioned=20
>RFC may not seem directly applicable. However, "in spirit",=20
>the document seems clear in requiring all RFCs to examine in=20
>detail their potential security impact.
>
>As I'm sure we're all aware, some of the use cases identified=20
>are purposefully implemented to maintain the confidentiality=20
>of a client's identity (e.g. NAT to obfuscate the structure of=20
>an enterprise network, Open-Wifi to conceal the identity of a=20
>client under threat of persecution [or prosecution], etc.).=20
>
>Thus, in identifying these scenarios as sharing the "issue" of=20
>host identification, the author would seem to be required to=20
>discuss the potential security implications of treating the=20
>lack of host identification as such, rather than a desirable feature.
>
>Thanks,
>
>Joshua Shire
>Information Systems Manager
>Hyduke Energy Services Inc.
>
>-----Original Message-----
>From: int-area-bounces@ietf.org=20
>[mailto:int-area-bounces@ietf.org] On Behalf Of=20
>mohamed.boucadair@orange.com
>Sent: Monday, December 03, 2012 2:08 AM
>To: fmc@ietf.org; int-area@ietf.org
>Cc: draft-boucadair-intarea-host-identifier-scenarios@tools.ietf.org
>Subject: [Int-area] draft-boucadair-intarea-host-identifier-scenarios
>
>Dear all,
>
>We submitted an updated version of this draft to list use=20
>cases which encounter the issue of host identification. The=20
>following use cases are discussed in the draft:
>
>   (1)  Carrier Grade NAT (CGN)
>   (2)  A+P (e.g., MAP )
>   (3)  Application Proxies
>   (4)  Provider Wi-Fi
>   (5)  Policy and Charging Architectures
>   (6)  Cellular Networks
>   (7)  Femtocells
>   (8)  Overlay Networks (e.g., CDNs)
>
>The document does not include any solution-specific=20
>discussion. Its main goal is to identify the use cases and=20
>describe them.=20
>
>If you think your use case is not included in this version,=20
>please share it with us.=20
>
>Comments are welcome.=20
>
>Cheers,
>Med
>
>
>-----Message d'origine-----
>De : i-d-announce-bounces@ietf.org=20
>[mailto:i-d-announce-bounces@ietf.org] De la part de=20
>internet-drafts@ietf.org Envoy=E9 : lundi 3 d=E9cembre 2012 08:26=20
>=C0 : i-d-announce@ietf.org Objet : I-D Action:=20
>draft-boucadair-intarea-host-identifier-scenarios-02.txt
>
>
>A New Internet-Draft is available from the on-line=20
>Internet-Drafts directories.
>
>
>	Title           : Host Identification: Use Cases
>	Author(s)       : Mohamed Boucadair
>                          David Binet
>                          Sophie Durel
>                          Tirumaleswar Reddy
>                          Brandon Williams
>	Filename        :=20
>draft-boucadair-intarea-host-identifier-scenarios-02.txt
>	Pages           : 14
>	Date            : 2012-12-02
>
>Abstract:
>   This document describes a set of scenarios in which host
>   identification is required.
>
>
>The IETF datatracker status page for this draft is:
>https://datatracker.ietf.org/doc/draft-boucadair-intarea-host-i
>dentifier-scenarios
>
>There's also a htmlized version available at:
>http://tools.ietf.org/html/draft-boucadair-intarea-host-identif
>ier-scenarios-02
>
>A diff from the previous version is available at:
>http://www.ietf.org/rfcdiff?url2=3Ddraft-boucadair-intarea-host-i
>dentifier-scenarios-02
>
>
>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=20
>ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>_______________________________________________
>Int-area mailing list
>Int-area@ietf.org
>https://www.ietf.org/mailman/listinfo/int-area
>
_______________________________________________
fmc mailing list
fmc@ietf.org
https://www.ietf.org/mailman/listinfo/fmc
