
From nordmark@acm.org  Thu Aug  1 00:49:36 2013
Return-Path: <nordmark@acm.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 79AF721F9DDB; Thu,  1 Aug 2013 00:49:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 Iw5l5XsgLHsC; Thu,  1 Aug 2013 00:49:30 -0700 (PDT)
Received: from a.mail.sonic.net (a.mail.sonic.net [64.142.16.245]) by ietfa.amsl.com (Postfix) with ESMTP id A5BDC21F9D89; Thu,  1 Aug 2013 00:49:30 -0700 (PDT)
Received: from [10.21.144.176] (128-107-239-233.cisco.com [128.107.239.233]) (authenticated bits=0) by a.mail.sonic.net (8.13.8.Beta0-Sonic/8.13.7) with ESMTP id r717nHmF016175 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 1 Aug 2013 00:49:19 -0700
Message-ID: <51FA12FB.1040709@acm.org>
Date: Thu, 01 Aug 2013 09:49:15 +0200
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Linda Dunbar <linda.dunbar@huawei.com>
References: <4A95BA014132FF49AE685FAB4B9F17F645B5269D@dfweml509-mbx.china.huawei.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F645B5269D@dfweml509-mbx.china.huawei.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Internet Area <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: [Int-area] any concerns of SEND mixed with Proxy Gateway described in draft-nachum-sarp-06?
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, 01 Aug 2013 07:49:36 -0000

On 7/31/13 11:11 AM, Linda Dunbar wrote:

> However, when SEND is used, Access (or Aggregation) switches might not
> possess knowledge of the attached hosts (VMs)’ private keys.
>
> Are there any concerns/feedback for giving the following recommendation
> in our draft? Any preferences?
>
> 1) state that SARP is not recommended when SEND is deployed;
>
> 2) recommend using RFC6496 (Secure Proxy ND Support for SEND).

I think it would be awkward to use RFC 6496 in this context since it 
requires that the host create a special certificate authorizing the 
switches to respond on their behalf. (That makes sense in cases like 
Mobile IP home agents where there is a pre-established relationship 
between the host and the home agent.)
Note that there would be some additional deployment issues as well, 
since all the hosts on the link would need to be able to do the RFC 6496 
validation - not just the normal SeND validation.

My take is that *if* we want to have the approach where a host's IP 
address should map to somebody else's MAC address, then I think the 
simplest (and secure) approach would be to have the host (somehow) find 
out the MAC address to use, and then have the hosts send the NAs themselves.

    Erik


From linda.dunbar@huawei.com  Thu Aug  1 04:07:48 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 2C69321E805F; Thu,  1 Aug 2013 04:07:36 -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=[AWL=0.000,  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 wQiTmGgVOki8; Thu,  1 Aug 2013 04:07:22 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id EBA9A21F9C69; Thu,  1 Aug 2013 04:07:05 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AVQ21566; Thu, 01 Aug 2013 11:06:57 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 1 Aug 2013 12:06:42 +0100
Received: from DFWEML407-HUB.china.huawei.com (10.193.5.132) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 1 Aug 2013 12:06:55 +0100
Received: from DFWEML509-MBX.china.huawei.com ([169.254.11.169]) by dfweml407-hub.china.huawei.com ([10.193.5.132]) with mapi id 14.01.0323.007; Thu, 1 Aug 2013 04:06:50 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: Erik Nordmark <nordmark@acm.org>
Thread-Topic: any concerns of SEND mixed with Proxy Gateway described in draft-nachum-sarp-06?
Thread-Index: AQHOjourmbP+4/tVPUmfPBOsQ4ICq5mAMTKw
Date: Thu, 1 Aug 2013 11:06:49 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F645B53F25@dfweml509-mbx.china.huawei.com>
References: <4A95BA014132FF49AE685FAB4B9F17F645B5269D@dfweml509-mbx.china.huawei.com> <51FA12FB.1040709@acm.org>
In-Reply-To: <51FA12FB.1040709@acm.org>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.130.179]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: Internet Area <int-area@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: [Int-area] any concerns of SEND mixed with Proxy Gateway described in draft-nachum-sarp-06?
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, 01 Aug 2013 11:07:49 -0000

> -----Original Message-----
>=20
> My take is that *if* we want to have the approach where a host's IP
> address should map to somebody else's MAC address, then I think the
> simplest (and secure) approach would be to have the host (somehow) find
> out the MAC address to use, and then have the hosts send the NAs
> themselves.

[Linda] Thank you for the suggestion. That is very reasonable.=20

>=20
>     Erik


From linda.dunbar@huawei.com  Fri Aug  2 04:33:41 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 572E511E8241 for <int-area@ietfa.amsl.com>; Fri,  2 Aug 2013 04:33:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 CeBIL279ak5X for <int-area@ietfa.amsl.com>; Fri,  2 Aug 2013 04:33:27 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 6C76B21E834B for <int-area@ietf.org>; Fri,  2 Aug 2013 04:33:11 -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 AUA57726; Fri, 02 Aug 2013 11:33:10 +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; Fri, 2 Aug 2013 12:32:53 +0100
Received: from DFWEML405-HUB.china.huawei.com (10.193.5.102) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 2 Aug 2013 12:32:56 +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; Fri, 2 Aug 2013 04:32:50 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: Internet Area <int-area@ietf.org>
Thread-Topic: comments to draft-matsushima-stateless-uplane-vepc-01
Thread-Index: Ac6PdAhK6af4K+BiRU+qjNRSkORWoQ==
Date: Fri, 2 Aug 2013 11:32:49 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F645B5467D@dfweml509-mbx.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.146.121]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F645B5467Ddfweml509mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [Int-area] comments to draft-matsushima-stateless-uplane-vepc-01
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, 02 Aug 2013 11:33:44 -0000

--_000_4A95BA014132FF49AE685FAB4B9F17F645B5467Ddfweml509mbxchi_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I am just repeating my comments made to draft-matsushima-stateless-uplane-v=
epc-01 during the InterArea WG session.

It seems to me that the case presented is the motivation for needing router=
s/switches in the network to dynamically change forwarding behavior that ar=
e triggered by external controller(s).
My question is: isn't it the right motivation for I2RS?

One of the co-authors stated on the microphone that it is. Just want to mak=
e sure what I heard is correct.

Linda


--_000_4A95BA014132FF49AE685FAB4B9F17F645B5467Ddfweml509mbxchi_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I am just repeating my comments made to draft-matsus=
hima-stateless-uplane-vepc-01 during the InterArea WG session.<o:p></o:p></=
p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">It seems to me that the case presented is the motiva=
tion for needing routers/switches in the network to dynamically change forw=
arding behavior that are triggered by external controller(s).
<o:p></o:p></p>
<p class=3D"MsoNormal">My question is: isn&#8217;t it the right motivation =
for I2RS?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">One of the co-authors stated on the microphone that =
it is. Just want to make sure what I heard is correct.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Linda<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_4A95BA014132FF49AE685FAB4B9F17F645B5467Ddfweml509mbxchi_--

From rbonica@juniper.net  Tue Aug  6 10:34:37 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 2483921E8096 for <int-area@ietfa.amsl.com>; Tue,  6 Aug 2013 10:34:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.18
X-Spam-Level: 
X-Spam-Status: No, score=-102.18 tagged_above=-999 required=5 tests=[AWL=1.420, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 yf+eOwkjhwj0 for <int-area@ietfa.amsl.com>; Tue,  6 Aug 2013 10:34:31 -0700 (PDT)
Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe001.messaging.microsoft.com [216.32.180.184]) by ietfa.amsl.com (Postfix) with ESMTP id 0464021E8097 for <int-area@ietf.org>; Tue,  6 Aug 2013 10:34:27 -0700 (PDT)
Received: from mail75-co1-R.bigfish.com (10.243.78.250) by CO1EHSOBE004.bigfish.com (10.243.66.67) with Microsoft SMTP Server id 14.1.225.22; Tue, 6 Aug 2013 17:34:27 +0000
Received: from mail75-co1 (localhost [127.0.0.1])	by mail75-co1-R.bigfish.com (Postfix) with ESMTP id 2D7BE3C0364	for <int-area@ietf.org>; Tue,  6 Aug 2013 17:34:27 +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: 2
X-BigFish: PS2(zzzz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz18602eh8275dh1de097hz2fh2a8h668h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d07h1d0ch1d2eh1d3fh1dc1h1de9h1dfeh1dffh1e1dh9a9j1155h)
Received-SPF: pass (mail75-co1: 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:(189002)(199002)(53806001)(83072001)(49866001)(33646001)(47736001)(74316001)(19580395003)(76796001)(54356001)(81342001)(31966008)(66066001)(81542001)(59766001)(74366001)(69226001)(16406001)(76576001)(76176001)(77096001)(65816001)(74502001)(63696002)(56816003)(56776001)(83322001)(76482001)(47446002)(74706001)(50986001)(77982001)(15974865002)(46102001)(74662001)(79102001)(4396001)(76786001)(74876001)(51856001)(80976001)(54316002)(47976001)(80022001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BL2PR05MB244; H:BL2PR05MB243.namprd05.prod.outlook.com; CLIP:66.129.232.2; RD:InfoNoRecords; MX:1; A:1; LANG:en; 
Received: from mail75-co1 (localhost.localdomain [127.0.0.1]) by mail75-co1 (MessageSwitch) id 1375810465338312_13927; Tue,  6 Aug 2013 17:34:25 +0000 (UTC)
Received: from CO1EHSMHS013.bigfish.com (unknown [10.243.78.251])	by mail75-co1.bigfish.com (Postfix) with ESMTP id 4EC76300041	for <int-area@ietf.org>; Tue,  6 Aug 2013 17:34:25 +0000 (UTC)
Received: from BL2PRD0510HT003.namprd05.prod.outlook.com (157.56.240.101) by CO1EHSMHS013.bigfish.com (10.243.66.23) with Microsoft SMTP Server (TLS) id 14.16.227.3; Tue, 6 Aug 2013 17:34:21 +0000
Received: from BL2PR05MB244.namprd05.prod.outlook.com (10.242.198.152) by BL2PRD0510HT003.namprd05.prod.outlook.com (10.255.100.38) with Microsoft SMTP Server (TLS) id 14.16.341.1; Tue, 6 Aug 2013 17:34:21 +0000
Received: from BL2PR05MB243.namprd05.prod.outlook.com (10.242.198.148) by BL2PR05MB244.namprd05.prod.outlook.com (10.242.198.152) with Microsoft SMTP Server (TLS) id 15.0.731.16; Tue, 6 Aug 2013 17:34:14 +0000
Received: from BL2PR05MB243.namprd05.prod.outlook.com ([169.254.8.111]) by BL2PR05MB243.namprd05.prod.outlook.com ([169.254.8.111]) with mapi id 15.00.0731.000; Tue, 6 Aug 2013 17:34:14 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: Internet Area <int-area@ietf.org>
Thread-Topic: draft-bonica-intarea-gre-mtu and ECN
Thread-Index: Ac6Syyo2lvW+6fj0T+qynpF9rNB3qg==
Date: Tue, 6 Aug 2013 17:34:13 +0000
Message-ID: <a4ede686715c4365b2ab88a90d43df38@BL2PR05MB243.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]
x-forefront-prvs: 0930AAFAD9
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%
Subject: [Int-area] draft-bonica-intarea-gre-mtu and ECN
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, 06 Aug 2013 17:34:37 -0000

Folks,

At our meeting in Berlin, someone (Lars?) came to the microphone to suggest=
 that draft-bonica-intarea-gre-mtu consider handling of the ECN bits. The p=
urpose of this message is to seek clarification on that comment.

Section 5.3 of RFC 3168 specifies procedures for handling the ECN bit when =
reassembling fragmented packets. These rules must be observed by any device=
 that reassembles fragmented packets, including tunnel egress routers. It w=
ould be reasonable to make note of this in draft-bonica-intarea-gre-mtu.

Section 9.1 of RFC 3168 as well as RFC 6040, specify procedures for propaga=
ting ECN bits between the tunnel payload and delivery header. These rules a=
pply to all tunneled packets, regardless of whether they are fragmented. Be=
cause the scope of draft-bonica-intarea-gre-mtu is limited to MTU and fragm=
entation issues, a discussion of these rules seems to be beyond the scope o=
f draft-bonica-intarea-gre-mtu.

Do folks agree?

--------------------------
Ron Bonica
vcard:       www.bonica.org/ron/ronbonica.vcf




From lars@netapp.com  Wed Aug  7 07:20:58 2013
Return-Path: <lars@netapp.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 6582D21F935A for <int-area@ietfa.amsl.com>; Wed,  7 Aug 2013 07:20:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.586
X-Spam-Level: 
X-Spam-Status: No, score=-4.586 tagged_above=-999 required=5 tests=[AWL=-2.587, BAYES_00=-2.599, J_CHICKENPOX_23=0.6]
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 bIEuJrHQrcOP for <int-area@ietfa.amsl.com>; Wed,  7 Aug 2013 07:20:53 -0700 (PDT)
Received: from mx11.netapp.com (mx11.netapp.com [216.240.18.76]) by ietfa.amsl.com (Postfix) with ESMTP id DF35021F9F7A for <int-area@ietf.org>; Wed,  7 Aug 2013 07:20:51 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.89,833,1367996400";  d="asc'?scan'208";a="39851269"
Received: from vmwexceht04-prd.hq.netapp.com ([10.106.77.34]) by mx11-out.netapp.com with ESMTP; 07 Aug 2013 07:20:49 -0700
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.240]) by vmwexceht04-prd.hq.netapp.com ([10.106.77.34]) with mapi id 14.03.0123.003; Wed, 7 Aug 2013 07:20:49 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: Ronald Bonica <rbonica@juniper.net>, Bob Briscoe <bob.briscoe@bt.com>
Thread-Topic: [Int-area] draft-bonica-intarea-gre-mtu and ECN
Thread-Index: Ac6Syyo2lvW+6fj0T+qynpF9rNB3qgA6NAyA
Date: Wed, 7 Aug 2013 14:20:48 +0000
Message-ID: <95E904E2-35A2-4715-AD95-2CFCDA2ECB0F@netapp.com>
References: <a4ede686715c4365b2ab88a90d43df38@BL2PR05MB243.namprd05.prod.outlook.com>
In-Reply-To: <a4ede686715c4365b2ab88a90d43df38@BL2PR05MB243.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.106.53.51]
Content-Type: multipart/signed; boundary="Apple-Mail=_0702E084-0B62-4472-9C36-1E064F47BC6D"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] draft-bonica-intarea-gre-mtu and ECN
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, 07 Aug 2013 14:20:58 -0000

--Apple-Mail=_0702E084-0B62-4472-9C36-1E064F47BC6D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

On Aug 6, 2013, at 19:34, Ronald Bonica <rbonica@juniper.net> wrote:
> Section 5.3 of RFC 3168 specifies procedures for handling the ECN bit =
when reassembling fragmented packets. These rules must be observed by =
any device that reassembles fragmented packets, including tunnel egress =
routers. It would be reasonable to make note of this in =
draft-bonica-intarea-gre-mtu.

agreed. You should also talk about what happens with the DSCP.

> Section 9.1 of RFC 3168 as well as RFC 6040, specify procedures for =
propagating ECN bits between the tunnel payload and delivery header. =
These rules apply to all tunneled packets, regardless of whether they =
are fragmented. Because the scope of draft-bonica-intarea-gre-mtu is =
limited to MTU and fragmentation issues, a discussion of these rules =
seems to be beyond the scope of draft-bonica-intarea-gre-mtu.

Agreed. However, given that the GRE spec predates the ECN spec, what are =
GRE implementations actually doing with the ECN/DSCP fields? =
Unfortunately, 3168 did not update 2784, although GRE can also provide =
an IP-in-IP tunnel type.=20

Lars

PS: CC'ing Bob, who also commented.

--Apple-Mail=_0702E084-0B62-4472-9C36-1E064F47BC6D
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

iQCVAwUBUgJXvtZcnpRveo1xAQKBtQP7BfxEYbpoaxYOm0D2vhGY7fUzK9AuQRFw
+GeETZ0YCHMl2yw+s+WAS0CWxUO0dg27+NpZHZe3r98H4NTGu8Xd/EQlMwMHwc1B
aD3edmrUiwalfwBrh1R6kTx2RHDrtml4ky4HjHAJFPIUQn1RAZQZdCsg9mNl0MGE
l0WhVQhIfO8=
=1JFa
-----END PGP SIGNATURE-----

--Apple-Mail=_0702E084-0B62-4472-9C36-1E064F47BC6D--

From rbonica@juniper.net  Wed Aug  7 08:33:05 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 E6DC921E8146 for <int-area@ietfa.amsl.com>; Wed,  7 Aug 2013 08:33:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.919
X-Spam-Level: 
X-Spam-Status: No, score=-103.919 tagged_above=-999 required=5 tests=[AWL=2.080, BAYES_00=-2.599, J_CHICKENPOX_23=0.6, 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 lDs6CwqY+gl3 for <int-area@ietfa.amsl.com>; Wed,  7 Aug 2013 08:32:58 -0700 (PDT)
Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe002.messaging.microsoft.com [207.46.163.25]) by ietfa.amsl.com (Postfix) with ESMTP id C5B0321E813B for <int-area@ietf.org>; Wed,  7 Aug 2013 08:32:55 -0700 (PDT)
Received: from mail218-co9-R.bigfish.com (10.236.132.231) by CO9EHSOBE008.bigfish.com (10.236.130.71) with Microsoft SMTP Server id 14.1.225.22; Wed, 7 Aug 2013 15:32:55 +0000
Received: from mail218-co9 (localhost [127.0.0.1])	by mail218-co9-R.bigfish.com (Postfix) with ESMTP id 366C0420192; Wed,  7 Aug 2013 15:32:55 +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: -2
X-BigFish: PS-2(zz98dI9371I542I1432Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz8275ch1de098h1de097hz2fh2a8h668h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1e1dh9a9j1155h)
Received-SPF: pass (mail218-co9: 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:(24454002)(199002)(51704005)(13464003)(189002)(377454003)(76576001)(83072001)(50986001)(46102001)(81542001)(80976001)(65816001)(76482001)(74316001)(74366001)(74876001)(80022001)(77096001)(56776001)(74706001)(47976001)(76796001)(4396001)(56816003)(59766001)(74502001)(54316002)(16406001)(63696002)(53806001)(47736001)(66066001)(77982001)(19580395003)(79102001)(76786001)(81342001)(83322001)(49866001)(47446002)(54356001)(19580405001)(33646001)(51856001)(31966008)(69226001)(74662001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BL2PR05MB242; H:BL2PR05MB243.namprd05.prod.outlook.com; CLIP:66.129.232.2; RD:InfoNoRecords; A:1; MX:1; LANG:en; 
Received: from mail218-co9 (localhost.localdomain [127.0.0.1]) by mail218-co9 (MessageSwitch) id 13758895745199_31913; Wed,  7 Aug 2013 15:32:54 +0000 (UTC)
Received: from CO9EHSMHS032.bigfish.com (unknown [10.236.132.231])	by mail218-co9.bigfish.com (Postfix) with ESMTP id E7E08240047; Wed,  7 Aug 2013 15:32:53 +0000 (UTC)
Received: from BL2PRD0510HT003.namprd05.prod.outlook.com (157.56.240.101) by CO9EHSMHS032.bigfish.com (10.236.130.42) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 7 Aug 2013 15:32:51 +0000
Received: from BL2PR05MB242.namprd05.prod.outlook.com (10.242.198.141) by BL2PRD0510HT003.namprd05.prod.outlook.com (10.255.100.38) with Microsoft SMTP Server (TLS) id 14.16.341.1; Wed, 7 Aug 2013 15:32:49 +0000
Received: from BL2PR05MB243.namprd05.prod.outlook.com (10.242.198.148) by BL2PR05MB242.namprd05.prod.outlook.com (10.242.198.141) with Microsoft SMTP Server (TLS) id 15.0.731.16; Wed, 7 Aug 2013 15:32:49 +0000
Received: from BL2PR05MB243.namprd05.prod.outlook.com ([169.254.8.111]) by BL2PR05MB243.namprd05.prod.outlook.com ([169.254.8.111]) with mapi id 15.00.0731.000; Wed, 7 Aug 2013 15:32:49 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: "Eggert, Lars" <lars@netapp.com>, Bob Briscoe <bob.briscoe@bt.com>
Thread-Topic: [Int-area] draft-bonica-intarea-gre-mtu and ECN
Thread-Index: Ac6Syyo2lvW+6fj0T+qynpF9rNB3qgA6NAyAAAxIejA=
Date: Wed, 7 Aug 2013 15:32:49 +0000
Message-ID: <7d516a96c7f8400ab458104030a3c141@BL2PR05MB243.namprd05.prod.outlook.com>
References: <a4ede686715c4365b2ab88a90d43df38@BL2PR05MB243.namprd05.prod.outlook.com> <95E904E2-35A2-4715-AD95-2CFCDA2ECB0F@netapp.com>
In-Reply-To: <95E904E2-35A2-4715-AD95-2CFCDA2ECB0F@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.232.2]
x-forefront-prvs: 0931CB1479
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%
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] draft-bonica-intarea-gre-mtu and ECN
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, 07 Aug 2013 15:33:05 -0000

Hi Lars,

We have a decision to make. Currently, the scope of the document is limited=
 to MTU and fragmentation issues. So, the reassembly issues in Section 5.3 =
of 3168 are clearly within scope.

However, DSCP handling has nothing to do with MTU and fragmentation. We cou=
ld include them, but that would mean expanding the scope of the document. D=
oes the WG want to do this?

Opinions?

                        Ron


> -----Original Message-----
> From: Eggert, Lars [mailto:lars@netapp.com]
> Sent: Wednesday, August 07, 2013 10:21 AM
> To: Ronald Bonica; Bob Briscoe
> Cc: Internet Area
> Subject: Re: [Int-area] draft-bonica-intarea-gre-mtu and ECN
>=20
> Hi,
>=20
> On Aug 6, 2013, at 19:34, Ronald Bonica <rbonica@juniper.net> wrote:
> > Section 5.3 of RFC 3168 specifies procedures for handling the ECN bit
> when reassembling fragmented packets. These rules must be observed by
> any device that reassembles fragmented packets, including tunnel egress
> routers. It would be reasonable to make note of this in draft-bonica-
> intarea-gre-mtu.
>=20
> agreed. You should also talk about what happens with the DSCP.
>=20
> > Section 9.1 of RFC 3168 as well as RFC 6040, specify procedures for
> propagating ECN bits between the tunnel payload and delivery header.
> These rules apply to all tunneled packets, regardless of whether they
> are fragmented. Because the scope of draft-bonica-intarea-gre-mtu is
> limited to MTU and fragmentation issues, a discussion of these rules
> seems to be beyond the scope of draft-bonica-intarea-gre-mtu.
>=20
> Agreed. However, given that the GRE spec predates the ECN spec, what
> are GRE implementations actually doing with the ECN/DSCP fields?
> Unfortunately, 3168 did not update 2784, although GRE can also provide
> an IP-in-IP tunnel type.
>=20
> Lars
>=20
> PS: CC'ing Bob, who also commented.


From bob.briscoe@bt.com  Wed Aug  7 10:42:21 2013
Return-Path: <bob.briscoe@bt.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 25C8411E8160 for <int-area@ietfa.amsl.com>; Wed,  7 Aug 2013 10:42:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.15
X-Spam-Level: 
X-Spam-Status: No, score=-3.15 tagged_above=-999 required=5 tests=[AWL=-0.151,  BAYES_00=-2.599, J_CHICKENPOX_23=0.6, 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 vEMQnUTz8epG for <int-area@ietfa.amsl.com>; Wed,  7 Aug 2013 10:42:13 -0700 (PDT)
Received: from hubrelay-rd.bt.com (hubrelay-rd.bt.com [62.239.224.99]) by ietfa.amsl.com (Postfix) with ESMTP id EADB111E80E2 for <int-area@ietf.org>; Wed,  7 Aug 2013 10:42:12 -0700 (PDT)
Received: from EVMHR01-UKBR.domain1.systemhost.net (193.113.108.40) by EVMHR67-UKRD.bt.com (10.187.101.22) with Microsoft SMTP Server (TLS) id 8.3.297.1; Wed, 7 Aug 2013 18:42:10 +0100
Received: from EPHR01-UKIP.domain1.systemhost.net (147.149.196.177) by EVMHR01-UKBR.domain1.systemhost.net (193.113.108.40) with Microsoft SMTP Server (TLS) id 8.3.297.1; Wed, 7 Aug 2013 18:42:09 +0100
Received: from bagheera.jungle.bt.co.uk (132.146.168.158) by EPHR01-UKIP.domain1.systemhost.net (147.149.196.177) with Microsoft SMTP Server id 14.2.342.3; Wed, 7 Aug 2013 18:42:08 +0100
Received: from BTP075694.jungle.bt.co.uk ([10.215.131.145])	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id r77Hg7l1020044; Wed, 7 Aug 2013 18:42:07 +0100
Message-ID: <201308071742.r77Hg7l1020044@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 7 Aug 2013 18:41:58 +0100
To: "Eggert, Lars" <lars@netapp.com>
From: Bob Briscoe <bob.briscoe@bt.com>
In-Reply-To: <95E904E2-35A2-4715-AD95-2CFCDA2ECB0F@netapp.com>
References: <a4ede686715c4365b2ab88a90d43df38@BL2PR05MB243.namprd05.prod.outlook.com> <95E904E2-35A2-4715-AD95-2CFCDA2ECB0F@netapp.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
Cc: Ronald Bonica <rbonica@juniper.net>, Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] draft-bonica-intarea-gre-mtu and ECN
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, 07 Aug 2013 17:42:21 -0000

Lars, Ron,

At 15:20 07/08/2013, Eggert, Lars wrote:
>Hi,
>
>On Aug 6, 2013, at 19:34, Ronald Bonica <rbonica@juniper.net> wrote:
> > Section 5.3 of RFC 3168 specifies procedures for handling the ECN 
> bit when reassembling fragmented packets. These rules must be 
> observed by any device that reassembles fragmented packets, 
> including tunnel egress routers. It would be reasonable to make 
> note of this in draft-bonica-intarea-gre-mtu.
>
>agreed.

+1

>You should also talk about what happens with the DSCP.

It is possible that different fragments of a packet will get 
different DSCPs (e.g. if some packets are re-marked due to being out 
of contract in a DS policer). However, RFC2474, RFC2983 (Diffserv & 
Tunnels) and RFC2597 (Diffserv AF) all fail to mention anything about 
what to do on re-assembly.

So I wouldn't open this can of worms, given no-one else has. It 
probably doesn't matter greatly which of the DSCPs on the fragments 
ends up being used for the reassembled packet, but I guess most 
implementations will use the DSCP on the first fragment, even if they 
haven't consciously thought about it.

It wouldn't take much to update 2474 to just say that - if someone 
has some spare clock cycles to waste.



> > Section 9.1 of RFC 3168 as well as RFC 6040, specify procedures 
> for propagating ECN bits between the tunnel payload and delivery 
> header. These rules apply to all tunneled packets, regardless of 
> whether they are fragmented. Because the scope of 
> draft-bonica-intarea-gre-mtu is limited to MTU and fragmentation 
> issues, a discussion of these rules seems to be beyond the scope of 
> draft-bonica-intarea-gre-mtu.
>
>Agreed.

+1

>However, given that the GRE spec predates the ECN spec, what are GRE 
>implementations actually doing with the ECN/DSCP fields? 
>Unfortunately, 3168 did not update 2784, although GRE can also 
>provide an IP-in-IP tunnel type.

Yes, I would be interested in an answer to that. Particularly given 
recent ideas on using GRE tunnels in data centres to turn on ECN 
edge-to-edge. See draft-briscoe-conex-data-centre-01 or 
<http://www.ietf.org/proceedings/87/slides/slides-87-conex-4.pdf>

PS. We also have an individual draft that clarifies that the RFC6040 
propagation of ECN should be used by all the different tunnelling 
protocols, including GRE: 
<http://tools.ietf.org/html/draft-briscoe-tsvwg-ecn-encap-guidelines-02>


Bob


>Lars
>
>PS: CC'ing Bob, who also commented.
>

________________________________________________________________
Bob Briscoe,                                                  BT 


From cpignata@cisco.com  Wed Aug  7 13:19:01 2013
Return-Path: <cpignata@cisco.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 7EB9111E80FA for <int-area@ietfa.amsl.com>; Wed,  7 Aug 2013 13:19:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.987
X-Spam-Level: 
X-Spam-Status: No, score=-109.987 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, J_CHICKENPOX_23=0.6, RCVD_IN_DNSWL_HI=-8, 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 JE-laPkPaxGK for <int-area@ietfa.amsl.com>; Wed,  7 Aug 2013 13:18:54 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 1284F11E80EC for <int-area@ietf.org>; Wed,  7 Aug 2013 13:18:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3389; q=dns/txt; s=iport; t=1375906720; x=1377116320; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=CphAr5/4TVDkzVnHfLbByAV0XAfLH+ewO3T1B1ppKOk=; b=Y0fIZ/85KLdE5yGowGdJnVtN4zvozWSUnJIs38umMnqI56/TsN1Zu135 tj4tmgVAX617UP3JgIYOYbStNQNHJHIk4dijrZJ4Phlr9w5Um1qDaMBKv y5L4IKqggqQDTVZQpm9h0tTdYdfmLymjYql7+F/jfw1Vxd+kFZh9bZtZ3 w=;
X-Files: signature.asc : 203
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAJGqAlKtJXHA/2dsb2JhbABbgwY1UL5EgR0WdIIkAQEBAwEBAQFrCwULAgEIGAokJwslAQEEDgUIBod8Bgy4MgSOXoELMQeDGnQDkBSBLZdvgxeBaEI
X-IronPort-AV: E=Sophos;i="4.89,835,1367971200";  d="asc'?scan'208";a="244744657"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-8.cisco.com with ESMTP; 07 Aug 2013 20:18:39 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r77KIc57010317 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 7 Aug 2013 20:18:38 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.110]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.02.0318.004; Wed, 7 Aug 2013 15:18:38 -0500
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: "Eggert, Lars" <lars@netapp.com>
Thread-Topic: [Int-area] draft-bonica-intarea-gre-mtu and ECN
Thread-Index: Ac6Syyo2lvW+6fj0T+qynpF9rNB3qgA6NAyAAAhOjAA=
Date: Wed, 7 Aug 2013 20:18:37 +0000
Message-ID: <95067C434CE250468B77282634C96ED322DE99D4@xmb-aln-x02.cisco.com>
References: <a4ede686715c4365b2ab88a90d43df38@BL2PR05MB243.namprd05.prod.outlook.com> <95E904E2-35A2-4715-AD95-2CFCDA2ECB0F@netapp.com>
In-Reply-To: <95E904E2-35A2-4715-AD95-2CFCDA2ECB0F@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.108.155]
Content-Type: multipart/signed; boundary="Apple-Mail=_592B46AA-9165-42CD-B39B-749982FA566F"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: Ronald Bonica <rbonica@juniper.net>, Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] draft-bonica-intarea-gre-mtu and ECN
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, 07 Aug 2013 20:19:01 -0000

--Apple-Mail=_592B46AA-9165-42CD-B39B-749982FA566F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi, Lars,

On Aug 7, 2013, at 4:20 PM, "Eggert, Lars" <lars@netapp.com>
 wrote:

> Hi,
>=20
> On Aug 6, 2013, at 19:34, Ronald Bonica <rbonica@juniper.net> wrote:
>> Section 5.3 of RFC 3168 specifies procedures for handling the ECN bit =
when reassembling fragmented packets. These rules must be observed by =
any device that reassembles fragmented packets, including tunnel egress =
routers. It would be reasonable to make note of this in =
draft-bonica-intarea-gre-mtu.
>=20
> agreed. You should also talk about what happens with the DSCP.

I am not sure I agree. RFC 3168 is broadly applicable and Section 5.3 =
specifies requirements for IP reassembly (and fragmentation) so that =
congestion information is not lost. However, that does not imply that =
this needs to be repeated in any document that talks about fragmentation =
and reassembly. Frankly, I see these as orthogonal issues.=20

In other words, noting S5.3 of RFC 3168 in draft-bonica-intarea-gre-mtu =
does not add as compared to not noting it -- the requirement already =
exists, and is applicable to any frag/reassembly, including GRE, any =
other tunnel, or any other protocol, as the ECN considerations at the IP =
layer. RFC 3168 specifies transport considerations for TCP and not for =
GRE also.

>=20
>> Section 9.1 of RFC 3168 as well as RFC 6040, specify procedures for =
propagating ECN bits between the tunnel payload and delivery header. =
These rules apply to all tunneled packets, regardless of whether they =
are fragmented. Because the scope of draft-bonica-intarea-gre-mtu is =
limited to MTU and fragmentation issues, a discussion of these rules =
seems to be beyond the scope of draft-bonica-intarea-gre-mtu.
>=20
> Agreed. However, given that the GRE spec predates the ECN spec, what =
are GRE implementations actually doing with the ECN/DSCP fields? =
Unfortunately, 3168 did not update 2784, although GRE can also provide =
an IP-in-IP tunnel type.=20
>=20

Section 9.3 covers GRE, and now draft-briscoe-tsvwg-ecn-encap-guidelines =
is clarifying the area previously left for further study.

Net-net, in my humble opinion, since draft-bonica-intarea-gre-mtu =
concerns itself with fragmentation strategies for GRE, these two ECN =
issues (ECN at reassembly and tunnels) seem orthogonal to the scope and =
goal of the document, and better dealt with in a separate place instead =
of intertwining them in draft-bonica-intarea-gre-mtu.

Thanks,

-- Carlos.

> Lars
>=20
> PS: CC'ing Bob, who also commented.
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area


--Apple-Mail=_592B46AA-9165-42CD-B39B-749982FA566F
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

iEYEARECAAYFAlICq50ACgkQtfDPGTp3USytggCgzoIvzZWJkg65r7oUBxLLthhk
cSUAn0sVC4WDc8bTMB6Ku1ulg3akM4v+
=/p2x
-----END PGP SIGNATURE-----

--Apple-Mail=_592B46AA-9165-42CD-B39B-749982FA566F--

From lars@netapp.com  Thu Aug  8 00:26:00 2013
Return-Path: <lars@netapp.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 457A021F9DAD for <int-area@ietfa.amsl.com>; Thu,  8 Aug 2013 00:26:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.885
X-Spam-Level: 
X-Spam-Status: No, score=-4.885 tagged_above=-999 required=5 tests=[AWL=-2.286, BAYES_00=-2.599]
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 Qh14oXsrZUF4 for <int-area@ietfa.amsl.com>; Thu,  8 Aug 2013 00:25:55 -0700 (PDT)
Received: from mx11.netapp.com (mx11.netapp.com [216.240.18.76]) by ietfa.amsl.com (Postfix) with ESMTP id 3B1BD11E81BF for <int-area@ietf.org>; Thu,  8 Aug 2013 00:25:55 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.89,837,1367996400";  d="asc'?scan'208";a="40055453"
Received: from vmwexceht04-prd.hq.netapp.com ([10.106.77.34]) by mx11-out.netapp.com with ESMTP; 08 Aug 2013 00:25:55 -0700
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.240]) by vmwexceht04-prd.hq.netapp.com ([10.106.77.34]) with mapi id 14.03.0123.003; Thu, 8 Aug 2013 00:25:54 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
Thread-Topic: [Int-area] draft-bonica-intarea-gre-mtu and ECN
Thread-Index: Ac6Syyo2lvW+6fj0T+qynpF9rNB3qgA6NAyAAAhOjAAAG362AA==
Date: Thu, 8 Aug 2013 07:25:53 +0000
Message-ID: <2AE4E0DE-B2E6-4318-9D88-B2D7C8A551D5@netapp.com>
References: <a4ede686715c4365b2ab88a90d43df38@BL2PR05MB243.namprd05.prod.outlook.com> <95E904E2-35A2-4715-AD95-2CFCDA2ECB0F@netapp.com> <95067C434CE250468B77282634C96ED322DE99D4@xmb-aln-x02.cisco.com>
In-Reply-To: <95067C434CE250468B77282634C96ED322DE99D4@xmb-aln-x02.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: multipart/signed; boundary="Apple-Mail=_6BC90F6A-45FF-4C61-9B40-602017AF4EB8"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: Ronald Bonica <rbonica@juniper.net>, Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] draft-bonica-intarea-gre-mtu and ECN
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, 08 Aug 2013 07:26:00 -0000

--Apple-Mail=_6BC90F6A-45FF-4C61-9B40-602017AF4EB8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

On Aug 7, 2013, at 22:18, Carlos Pignataro (cpignata) =
<cpignata@cisco.com> wrote:
> In other words, noting S5.3 of RFC 3168 in =
draft-bonica-intarea-gre-mtu does not add as compared to not noting it =
-- the requirement already exists, and is applicable to any =
frag/reassembly, including GRE, any other tunnel, or any other protocol, =
as the ECN considerations at the IP layer. RFC 3168 specifies transport =
considerations for TCP and not for GRE also.

you're correct. In practice, however, not everyone is familiar with the =
contents of all related RFCs when implementing a given protocol =
extension, and I think pointing implementors at relevant related specs - =
esp. when mandatory to support - is a courtesy.

> Net-net, in my humble opinion, since draft-bonica-intarea-gre-mtu =
concerns itself with fragmentation strategies for GRE, these two ECN =
issues (ECN at reassembly and tunnels) seem orthogonal to the scope and =
goal of the document, and better dealt with in a separate place instead =
of intertwining them in draft-bonica-intarea-gre-mtu.

Which document specifies the reassembly of fragments carried in GRE?

Lars

--Apple-Mail=_6BC90F6A-45FF-4C61-9B40-602017AF4EB8
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

iQCVAwUBUgNIANZcnpRveo1xAQLBUwP/T1CaIB41czLkNnCVYAK5HtfHAWEOQmqs
Jdopom3w5ynYKmzsknK2tVwNY2RolDPiCg8m05cfhf//cx0VbErUPrPzZFiU/vVc
elCXYXNQVv0AEMAKPNhrW+uqs3ESrXu+anC3DOnhg5NBVCSSAPKnCWB6uGeDNWu4
mUejmFF9fz4=
=O+dQ
-----END PGP SIGNATURE-----

--Apple-Mail=_6BC90F6A-45FF-4C61-9B40-602017AF4EB8--

From rbonica@juniper.net  Thu Aug  8 11:01:13 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 261D91F0D5F for <int-area@ietfa.amsl.com>; Thu,  8 Aug 2013 11:01:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.982
X-Spam-Level: 
X-Spam-Status: No, score=-102.982 tagged_above=-999 required=5 tests=[AWL=0.617, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 j+eKrnyzlIhT for <int-area@ietfa.amsl.com>; Thu,  8 Aug 2013 11:01:06 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe001.messaging.microsoft.com [216.32.180.11]) by ietfa.amsl.com (Postfix) with ESMTP id 9E0431F0CB2 for <int-area@ietf.org>; Thu,  8 Aug 2013 11:01:06 -0700 (PDT)
Received: from mail97-va3-R.bigfish.com (10.7.14.229) by VA3EHSOBE009.bigfish.com (10.7.40.29) with Microsoft SMTP Server id 14.1.225.22; Thu, 8 Aug 2013 18:00:58 +0000
Received: from mail97-va3 (localhost [127.0.0.1])	by mail97-va3-R.bigfish.com (Postfix) with ESMTP id 9127A200EC; Thu,  8 Aug 2013 18:00:58 +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: -3
X-BigFish: PS-3(zz98dI9371I542I1432I1418Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1de098h8275bh1de097hz2fh2a8h668h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1e1dh1fe8h9a9j1155h)
Received-SPF: pass (mail97-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:(24454002)(51704005)(199002)(51444003)(13464003)(189002)(377454003)(46102001)(50986001)(76576001)(83072001)(80976001)(81542001)(74876001)(74316001)(65816001)(76482001)(74366001)(56776001)(81686001)(4396001)(74706001)(76796001)(77096001)(56816003)(47976001)(59766001)(74662001)(54316002)(74502001)(77982001)(66066001)(47736001)(53806001)(63696002)(33646001)(47446002)(31966008)(76786001)(79102001)(49866001)(81342001)(83322001)(16406001)(19580395003)(80022001)(54356001)(19580405001)(69226001)(51856001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BL2PR05MB242; H:BL2PR05MB243.namprd05.prod.outlook.com; CLIP:66.129.232.2; RD:InfoNoRecords; A:1; MX:1; LANG:en; 
Received: from mail97-va3 (localhost.localdomain [127.0.0.1]) by mail97-va3 (MessageSwitch) id 1375984856566292_7760; Thu,  8 Aug 2013 18:00:56 +0000 (UTC)
Received: from VA3EHSMHS044.bigfish.com (unknown [10.7.14.245])	by mail97-va3.bigfish.com (Postfix) with ESMTP id 7A4983A004D; Thu,  8 Aug 2013 18:00:56 +0000 (UTC)
Received: from BL2PRD0510HT005.namprd05.prod.outlook.com (157.56.240.101) by VA3EHSMHS044.bigfish.com (10.7.99.54) with Microsoft SMTP Server (TLS) id 14.16.227.3; Thu, 8 Aug 2013 18:00:56 +0000
Received: from BL2PR05MB242.namprd05.prod.outlook.com (10.242.198.141) by BL2PRD0510HT005.namprd05.prod.outlook.com (10.255.100.40) with Microsoft SMTP Server (TLS) id 14.16.341.1; Thu, 8 Aug 2013 18:00:56 +0000
Received: from BL2PR05MB243.namprd05.prod.outlook.com (10.242.198.148) by BL2PR05MB242.namprd05.prod.outlook.com (10.242.198.141) with Microsoft SMTP Server (TLS) id 15.0.731.16; Thu, 8 Aug 2013 18:00:55 +0000
Received: from BL2PR05MB243.namprd05.prod.outlook.com ([169.254.8.111]) by BL2PR05MB243.namprd05.prod.outlook.com ([169.254.8.111]) with mapi id 15.00.0731.000; Thu, 8 Aug 2013 18:00:55 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: "Eggert, Lars" <lars@netapp.com>, "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
Thread-Topic: [Int-area] draft-bonica-intarea-gre-mtu and ECN
Thread-Index: Ac6Syyo2lvW+6fj0T+qynpF9rNB3qgA6NAyAAAhOjAAAG362AAAHO4MQ
Date: Thu, 8 Aug 2013 18:00:54 +0000
Message-ID: <af0635b8d3254ee2891c8cfd8b5e04b6@BL2PR05MB243.namprd05.prod.outlook.com>
References: <a4ede686715c4365b2ab88a90d43df38@BL2PR05MB243.namprd05.prod.outlook.com> <95E904E2-35A2-4715-AD95-2CFCDA2ECB0F@netapp.com> <95067C434CE250468B77282634C96ED322DE99D4@xmb-aln-x02.cisco.com> <2AE4E0DE-B2E6-4318-9D88-B2D7C8A551D5@netapp.com>
In-Reply-To: <2AE4E0DE-B2E6-4318-9D88-B2D7C8A551D5@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.232.2]
x-forefront-prvs: 093290AD39
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%
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] draft-bonica-intarea-gre-mtu and ECN
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, 08 Aug 2013 18:01:13 -0000

Folks,

I think that we have agreed to the following:

- We should include a reference to S5.3 of RFC 3168, reminding implementers=
 that when reassembling a packet, if any packet has ECN set, the reassemble=
d packet MUST have ECN set. While this may be orthogonal to the draft, it i=
s included as a courtesy.

- We don't need to add any text about copying DSCP or ECN bits back and for=
th between the payload and delivery headers, as this issues are beyond the =
scope of the document.

Have we in fact agreed on this?

                                       Ron


> -----Original Message-----
> From: Eggert, Lars [mailto:lars@netapp.com]
> Sent: Thursday, August 08, 2013 3:26 AM
> To: Carlos Pignataro (cpignata)
> Cc: Ronald Bonica; Bob Briscoe; Internet Area
> Subject: Re: [Int-area] draft-bonica-intarea-gre-mtu and ECN
>=20
> Hi,
>=20
> On Aug 7, 2013, at 22:18, Carlos Pignataro (cpignata)
> <cpignata@cisco.com> wrote:
> > In other words, noting S5.3 of RFC 3168 in draft-bonica-intarea-gre-
> mtu does not add as compared to not noting it -- the requirement
> already exists, and is applicable to any frag/reassembly, including
> GRE, any other tunnel, or any other protocol, as the ECN considerations
> at the IP layer. RFC 3168 specifies transport considerations for TCP
> and not for GRE also.
>=20
> you're correct. In practice, however, not everyone is familiar with the
> contents of all related RFCs when implementing a given protocol
> extension, and I think pointing implementors at relevant related specs
> - esp. when mandatory to support - is a courtesy.
>=20
> > Net-net, in my humble opinion, since draft-bonica-intarea-gre-mtu
> concerns itself with fragmentation strategies for GRE, these two ECN
> issues (ECN at reassembly and tunnels) seem orthogonal to the scope and
> goal of the document, and better dealt with in a separate place instead
> of intertwining them in draft-bonica-intarea-gre-mtu.
>=20
> Which document specifies the reassembly of fragments carried in GRE?
>=20
> Lars


From cpignata@cisco.com  Thu Aug  8 14:23:11 2013
Return-Path: <cpignata@cisco.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 1E64D11E8220 for <int-area@ietfa.amsl.com>; Thu,  8 Aug 2013 14:23:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.31
X-Spam-Level: 
X-Spam-Status: No, score=-110.31 tagged_above=-999 required=5 tests=[AWL=0.289, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 lPTLzGgnfAxI for <int-area@ietfa.amsl.com>; Thu,  8 Aug 2013 14:22:34 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id A05FF21E8082 for <int-area@ietf.org>; Thu,  8 Aug 2013 14:22:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2957; q=dns/txt; s=iport; t=1375996950; x=1377206550; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=dajRz2He287oEj/jJd0A3LJZQdG6hz17DTMWkcNlsXk=; b=hLDIgPeScxcTzpO9nKDWvC4O3qZLk+sezgAqCx6ptp+fCCNWRD7MJrSM e0/WFuw94jOfL85206vtx73zSBQH8lP9Q87QriKywXC1stmyl5+2puzX5 oayZseL2xcZEfGH3j0k3mhU7t15uL6fJA3X63hzEnwVX/KYJADPlkiWCs k=;
X-Files: signature.asc : 203
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkIFABgLBFKtJV2d/2dsb2JhbABbgwY1UL5NgRoWdIIkAQEBAwFnEgULAgEIGAokMiUBAQQOBQgGh3wGDLhSj2oxB4MadAOQFIEth0qQJYMYgio
X-IronPort-AV: E=Sophos;i="4.89,841,1367971200";  d="asc'?scan'208";a="245235327"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-5.cisco.com with ESMTP; 08 Aug 2013 21:22:23 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r78LMMVb006197 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 8 Aug 2013 21:22:22 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.110]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.02.0318.004; Thu, 8 Aug 2013 16:22:22 -0500
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: "Eggert, Lars" <lars@netapp.com>
Thread-Topic: [Int-area] draft-bonica-intarea-gre-mtu and ECN
Thread-Index: Ac6Syyo2lvW+6fj0T+qynpF9rNB3qgA6NAyAAAhOjAAAG362AAAZBWoA
Date: Thu, 8 Aug 2013 21:22:21 +0000
Message-ID: <95067C434CE250468B77282634C96ED322DEE296@xmb-aln-x02.cisco.com>
References: <a4ede686715c4365b2ab88a90d43df38@BL2PR05MB243.namprd05.prod.outlook.com> <95E904E2-35A2-4715-AD95-2CFCDA2ECB0F@netapp.com> <95067C434CE250468B77282634C96ED322DE99D4@xmb-aln-x02.cisco.com> <2AE4E0DE-B2E6-4318-9D88-B2D7C8A551D5@netapp.com>
In-Reply-To: <2AE4E0DE-B2E6-4318-9D88-B2D7C8A551D5@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.108.155]
Content-Type: multipart/signed; boundary="Apple-Mail=_FBCA1FDD-9246-47D5-A8C6-D74476563854"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: Ronald Bonica <rbonica@juniper.net>, Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] draft-bonica-intarea-gre-mtu and ECN
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, 08 Aug 2013 21:23:12 -0000

--Apple-Mail=_FBCA1FDD-9246-47D5-A8C6-D74476563854
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi, Lars,

On Aug 8, 2013, at 9:25 AM, "Eggert, Lars" <lars@netapp.com> wrote:

> Hi,
>=20
> On Aug 7, 2013, at 22:18, Carlos Pignataro (cpignata) =
<cpignata@cisco.com> wrote:
>> In other words, noting S5.3 of RFC 3168 in =
draft-bonica-intarea-gre-mtu does not add as compared to not noting it =
-- the requirement already exists, and is applicable to any =
frag/reassembly, including GRE, any other tunnel, or any other protocol, =
as the ECN considerations at the IP layer. RFC 3168 specifies transport =
considerations for TCP and not for GRE also.
>=20
> you're correct. In practice, however, not everyone is familiar with =
the contents of all related RFCs when implementing a given protocol =
extension, and I think pointing implementors at relevant related specs - =
esp. when mandatory to support - is a courtesy.

I agree in principle with this, although there's a degree of relevance =
for these informational and contextual "reminder" pointers. Yes, I've =
also seen then be of help in practice as well, but I wouldn't want to =
cite every mandatory RFC related to fragmentation.

In this case, draft-bonica-intarea-gre-mtu is more about fragmentation =
than reassembly, while S5.3 of RFC3168 concerns itself with reassembly =
mostly, which is why I think the correlation is tenuous. On the other =
side, I do not see any harm with adding it (it's not a major distraction =
from the main topic), and I can see potential benefit with awareness =
raising.

>=20
>> Net-net, in my humble opinion, since draft-bonica-intarea-gre-mtu =
concerns itself with fragmentation strategies for GRE, these two ECN =
issues (ECN at reassembly and tunnels) seem orthogonal to the scope and =
goal of the document, and better dealt with in a separate place instead =
of intertwining them in draft-bonica-intarea-gre-mtu.
>=20
> Which document specifies the reassembly of fragments carried in GRE?
>=20

RFC 791 and RFC 2460 (if I understood your question correctly :-). If IP =
fragments are carried in GRE, after decapsulation, IP is exposed. As far =
as ECN propagation and behavior, I think the best is =
http://tools.ietf.org/html/draft-briscoe-tsvwg-ecn-encap-guidelines-02#sec=
tion-4.1

> Lars

Thanks,

-- Carlos.

--Apple-Mail=_FBCA1FDD-9246-47D5-A8C6-D74476563854
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

iEYEARECAAYFAlIEDAoACgkQtfDPGTp3USyO1QCgtn0kI878lWhOIsUTtrhvrH8b
9xUAoMJF4KXFlqSbXWLEAvParx6mqqQp
=GvGE
-----END PGP SIGNATURE-----

--Apple-Mail=_FBCA1FDD-9246-47D5-A8C6-D74476563854--

From cpignata@cisco.com  Thu Aug  8 14:23:21 2013
Return-Path: <cpignata@cisco.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 9F1CB11E8248 for <int-area@ietfa.amsl.com>; Thu,  8 Aug 2013 14:23:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.333
X-Spam-Level: 
X-Spam-Status: No, score=-110.333 tagged_above=-999 required=5 tests=[AWL=0.266, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 vHUZ-Lyui0aK for <int-area@ietfa.amsl.com>; Thu,  8 Aug 2013 14:23:13 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id CF27321F9E88 for <int-area@ietf.org>; Thu,  8 Aug 2013 14:23:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2982; q=dns/txt; s=iport; t=1375996991; x=1377206591; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Bt5mXsOciGWdppBob6Ouliqq8o68Bv8Cfgdf3jstNJ8=; b=jda9zqEnGf5hOBD2smlz+UtxqbvBCsKaF/rZAPooBofam8xAsP/CIPH5 aRr2uiqPqOjh05Oy66ah61tDvzmu9aVL8SrpkU2UTNDcsMTrEBYBO120R 414/EJb5PjNCm/TR6aVaqI7CZO4Yxu/hY7dEfIzoyPLdathOk9SjKtyOW E=;
X-Files: signature.asc : 203
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkIFAJILBFKtJV2b/2dsb2JhbABbgwaBBb5NgRoWdIIkAQEBAwFnEgUHBAIBCA4DBAEBAQodBzIUCQgBAQQOBQgGh3wGuF6PajEHBoMUdAOQFIEtl2+DGIIq
X-IronPort-AV: E=Sophos;i="4.89,841,1367971200";  d="asc'?scan'208";a="245236457"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-8.cisco.com with ESMTP; 08 Aug 2013 21:23:05 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r78LN5Zc014016 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 8 Aug 2013 21:23:05 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.110]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.02.0318.004; Thu, 8 Aug 2013 16:23:05 -0500
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: Ronald Bonica <rbonica@juniper.net>
Thread-Topic: [Int-area] draft-bonica-intarea-gre-mtu and ECN
Thread-Index: Ac6Syyo2lvW+6fj0T+qynpF9rNB3qgA6NAyAAAhOjAAAG362AAAHO4MQABHQwgA=
Date: Thu, 8 Aug 2013 21:23:04 +0000
Message-ID: <95067C434CE250468B77282634C96ED322DEE2B1@xmb-aln-x02.cisco.com>
References: <a4ede686715c4365b2ab88a90d43df38@BL2PR05MB243.namprd05.prod.outlook.com> <95E904E2-35A2-4715-AD95-2CFCDA2ECB0F@netapp.com> <95067C434CE250468B77282634C96ED322DE99D4@xmb-aln-x02.cisco.com> <2AE4E0DE-B2E6-4318-9D88-B2D7C8A551D5@netapp.com> <af0635b8d3254ee2891c8cfd8b5e04b6@BL2PR05MB243.namprd05.prod.outlook.com>
In-Reply-To: <af0635b8d3254ee2891c8cfd8b5e04b6@BL2PR05MB243.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.21.108.155]
Content-Type: multipart/signed; boundary="Apple-Mail=_4AB07688-04EC-477C-93ED-7DBED028213C"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] draft-bonica-intarea-gre-mtu and ECN
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, 08 Aug 2013 21:23:21 -0000

--Apple-Mail=_4AB07688-04EC-477C-93ED-7DBED028213C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi Ron,

This sounds good to me. Thanks!

-- Carlos.

On Aug 8, 2013, at 8:00 PM, Ronald Bonica <rbonica@juniper.net> wrote:

> Folks,
>=20
> I think that we have agreed to the following:
>=20
> - We should include a reference to S5.3 of RFC 3168, reminding =
implementers that when reassembling a packet, if any packet has ECN set, =
the reassembled packet MUST have ECN set. While this may be orthogonal =
to the draft, it is included as a courtesy.
>=20
> - We don't need to add any text about copying DSCP or ECN bits back =
and forth between the payload and delivery headers, as this issues are =
beyond the scope of the document.
>=20
> Have we in fact agreed on this?
>=20
>                                       Ron
>=20
>=20
>> -----Original Message-----
>> From: Eggert, Lars [mailto:lars@netapp.com]
>> Sent: Thursday, August 08, 2013 3:26 AM
>> To: Carlos Pignataro (cpignata)
>> Cc: Ronald Bonica; Bob Briscoe; Internet Area
>> Subject: Re: [Int-area] draft-bonica-intarea-gre-mtu and ECN
>>=20
>> Hi,
>>=20
>> On Aug 7, 2013, at 22:18, Carlos Pignataro (cpignata)
>> <cpignata@cisco.com> wrote:
>>> In other words, noting S5.3 of RFC 3168 in draft-bonica-intarea-gre-
>> mtu does not add as compared to not noting it -- the requirement
>> already exists, and is applicable to any frag/reassembly, including
>> GRE, any other tunnel, or any other protocol, as the ECN =
considerations
>> at the IP layer. RFC 3168 specifies transport considerations for TCP
>> and not for GRE also.
>>=20
>> you're correct. In practice, however, not everyone is familiar with =
the
>> contents of all related RFCs when implementing a given protocol
>> extension, and I think pointing implementors at relevant related =
specs
>> - esp. when mandatory to support - is a courtesy.
>>=20
>>> Net-net, in my humble opinion, since draft-bonica-intarea-gre-mtu
>> concerns itself with fragmentation strategies for GRE, these two ECN
>> issues (ECN at reassembly and tunnels) seem orthogonal to the scope =
and
>> goal of the document, and better dealt with in a separate place =
instead
>> of intertwining them in draft-bonica-intarea-gre-mtu.
>>=20
>> Which document specifies the reassembly of fragments carried in GRE?
>>=20
>> Lars
>=20


--Apple-Mail=_4AB07688-04EC-477C-93ED-7DBED028213C
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

iEYEARECAAYFAlIEDDgACgkQtfDPGTp3USwU/wCgpM8pvCbJZgPHg47wgDDFvDs5
eSsAoME5aXu7qrJIijxJ49dutqGOUDCr
=H7N1
-----END PGP SIGNATURE-----

--Apple-Mail=_4AB07688-04EC-477C-93ED-7DBED028213C--

From rbonica@juniper.net  Thu Aug 15 10:51:27 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 5C59F11E81E2 for <int-area@ietfa.amsl.com>; Thu, 15 Aug 2013 10:51:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.432
X-Spam-Level: 
X-Spam-Status: No, score=-103.432 tagged_above=-999 required=5 tests=[AWL=0.167, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 Lx65BIjOWkQ7 for <int-area@ietfa.amsl.com>; Thu, 15 Aug 2013 10:51:22 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe002.messaging.microsoft.com [216.32.180.12]) by ietfa.amsl.com (Postfix) with ESMTP id 3433A11E8219 for <int-area@ietf.org>; Thu, 15 Aug 2013 10:51:20 -0700 (PDT)
Received: from mail115-va3-R.bigfish.com (10.7.14.229) by VA3EHSOBE007.bigfish.com (10.7.40.11) with Microsoft SMTP Server id 14.1.225.22; Thu, 15 Aug 2013 17:51:19 +0000
Received: from mail115-va3 (localhost [127.0.0.1])	by mail115-va3-R.bigfish.com (Postfix) with ESMTP id 4BD054000A2	for <int-area@ietf.org>; Thu, 15 Aug 2013 17:51:19 +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: -22
X-BigFish: VPS-22(zz9371I936eI542I1432Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1de098h1033IL17326ah1de096h8275dh1de097hz2fh2a8h668h839h93fhd24hf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d07h1d0ch1d2eh1d3fh1dc1h1de9h1dfeh1dffh1e1dh1fe8h1ff5h9a9j1155h)
Received-SPF: pass (mail115-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:(199002)(189002)(13464003)(377454003)(51704005)(377424004)(19580395003)(80022001)(65816001)(74502001)(59766001)(74876001)(46102001)(81342001)(80976001)(74706001)(76176001)(15202345003)(66066001)(4396001)(56816003)(31966008)(54356001)(56776001)(53806001)(79102001)(49866001)(47736001)(47976001)(69226001)(16406001)(50986001)(51856001)(33646001)(83322001)(74662001)(19580405001)(77982001)(83072001)(19580385001)(76786001)(81686001)(74316001)(76576001)(47446002)(76796001)(77096001)(63696002)(74366001)(54316002)(76482001)(81542001)(81816001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BL2PR05MB244; H:BL2PR05MB243.namprd05.prod.outlook.com; CLIP:66.129.238.2; RD:InfoNoRecords; A:1; MX:1; LANG:en; 
Received: from mail115-va3 (localhost.localdomain [127.0.0.1]) by mail115-va3 (MessageSwitch) id 1376589078264872_26208; Thu, 15 Aug 2013 17:51:18 +0000 (UTC)
Received: from VA3EHSMHS026.bigfish.com (unknown [10.7.14.229])	by mail115-va3.bigfish.com (Postfix) with ESMTP id 3291944004D	for <int-area@ietf.org>; Thu, 15 Aug 2013 17:51:18 +0000 (UTC)
Received: from BL2PRD0510HT005.namprd05.prod.outlook.com (157.56.240.101) by VA3EHSMHS026.bigfish.com (10.7.99.36) with Microsoft SMTP Server (TLS) id 14.16.227.3; Thu, 15 Aug 2013 17:51:18 +0000
Received: from BL2PR05MB244.namprd05.prod.outlook.com (10.242.198.152) by BL2PRD0510HT005.namprd05.prod.outlook.com (10.255.100.40) with Microsoft SMTP Server (TLS) id 14.16.347.3; Thu, 15 Aug 2013 17:51:17 +0000
Received: from BL2PR05MB243.namprd05.prod.outlook.com (10.242.198.148) by BL2PR05MB244.namprd05.prod.outlook.com (10.242.198.152) with Microsoft SMTP Server (TLS) id 15.0.731.16; Thu, 15 Aug 2013 17:51:16 +0000
Received: from BL2PR05MB243.namprd05.prod.outlook.com ([169.254.8.111]) by BL2PR05MB243.namprd05.prod.outlook.com ([169.254.8.111]) with mapi id 15.00.0731.000; Thu, 15 Aug 2013 17:51:16 +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-03.txt
Thread-Index: AQHOmd++taPbdUaCMEe99itTicLVLZmWjCTQ
Date: Thu, 15 Aug 2013 17:51:14 +0000
Message-ID: <a4ebf56365e44291b46c268bdb055e9d@BL2PR05MB243.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.238.2]
x-forefront-prvs: 0939529DE2
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%
Subject: [Int-area] FW: New Version Notification for draft-bonica-intarea-gre-mtu-03.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, 15 Aug 2013 17:51:27 -0000

Rm9sa3MsDQoNClRoaXMgZHJhZnQgdmVyc2lvbiBhZGRyZXNzZXMgaXNzdWVzIHJhaXNlZCBieSBM
YXJzIGFuZCBCb2IuDQoNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBSb24N
Cg0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IGludGVybmV0LWRyYWZ0
c0BpZXRmLm9yZyBbbWFpbHRvOmludGVybmV0LWRyYWZ0c0BpZXRmLm9yZ10NCj4gU2VudDogVGh1
cnNkYXksIEF1Z3VzdCAxNSwgMjAxMyAxOjQ5IFBNDQo+IFRvOiBSb25hbGQgQm9uaWNhOyBDYXJs
b3MgUGlnbmF0YXJvOyBKb2UgVG91Y2g7IERyLkpvc2VwaCBELlRvdWNoDQo+IFN1YmplY3Q6IE5l
dyBWZXJzaW9uIE5vdGlmaWNhdGlvbiBmb3IgZHJhZnQtYm9uaWNhLWludGFyZWEtZ3JlLW10dS0N
Cj4gMDMudHh0DQo+IA0KPiANCj4gQSBuZXcgdmVyc2lvbiBvZiBJLUQsIGRyYWZ0LWJvbmljYS1p
bnRhcmVhLWdyZS1tdHUtMDMudHh0DQo+IGhhcyBiZWVuIHN1Y2Nlc3NmdWxseSBzdWJtaXR0ZWQg
YnkgUm9uIEJvbmljYSBhbmQgcG9zdGVkIHRvIHRoZSBJRVRGDQo+IHJlcG9zaXRvcnkuDQo+IA0K
PiBGaWxlbmFtZToJIGRyYWZ0LWJvbmljYS1pbnRhcmVhLWdyZS1tdHUNCj4gUmV2aXNpb246CSAw
Mw0KPiBUaXRsZToJCSBBIEZyYWdtZW50YXRpb24gU3RyYXRlZ3kgZm9yIEdlbmVyaWMgUm91dGlu
Zw0KPiBFbmNhcHN1bGF0aW9uIChHUkUpDQo+IENyZWF0aW9uIGRhdGU6CSAyMDEzLTA4LTE1DQo+
IEdyb3VwOgkJIEluZGl2aWR1YWwgU3VibWlzc2lvbg0KPiBOdW1iZXIgb2YgcGFnZXM6IDEyDQo+
IFVSTDogICAgICAgICAgICAgaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJh
ZnQtYm9uaWNhLQ0KPiBpbnRhcmVhLWdyZS1tdHUtMDMudHh0DQo+IFN0YXR1czogICAgICAgICAg
aHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1ib25pY2EtaW50YXJlYS0NCj4g
Z3JlLW10dQ0KPiBIdG1saXplZDogICAgICAgIGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2Ry
YWZ0LWJvbmljYS1pbnRhcmVhLWdyZS0NCj4gbXR1LTAzDQo+IERpZmY6ICAgICAgICAgICAgaHR0
cDovL3d3dy5pZXRmLm9yZy9yZmNkaWZmP3VybDI9ZHJhZnQtYm9uaWNhLWludGFyZWEtDQo+IGdy
ZS1tdHUtMDMNCj4gDQo+IEFic3RyYWN0Og0KPiAgICBUaGlzIG1lbW8gZG9jdW1lbnRzIGEgR1JF
IGZyYWdtZW50YXRpb24gc3RyYXRlZ3kgdGhhdCBoYXMgYmVlbg0KPiAgICBpbXBsZW1lbnRlZCBi
eSBtYW55IHZlbmRvcnMgYW5kIGRlcGxveWVkIGluIG1hbnkgbmV0d29ya3MuICBJdCB3YXMNCj4g
ICAgd3JpdHRlbiBzbyB0aGF0IGEpIGltcGxlbWVudG9ycyB3aWxsIGJlIGF3YXJlIG9mIGJlc3Qg
Y29tbW9uDQo+IHByYWN0aWNlDQo+ICAgIGFuZCBiKSB0aG9zZSB3aG8gcmVseSBvbiBHUkUgd2ls
bCB1bmRlcnN0YW5kIGhvdyBpbXBsZW1lbnRhdGlvbnMNCj4gICAgd29yay4gIFRoZSBzY29wZSBv
ZiB0aGlzIG1lbW8gaXMgbGltaXRlZCB0byBwb2ludC10by1wb2ludCBHUkUNCj4gICAgdHVubmVs
cy4gIEFsbCBvdGhlciB0dW5uZWwgdHlwZXMgYXJlIGJleW9uZCB0aGUgc2NvcGUgb2YgdGhpcyBt
ZW1vLg0KPiANCj4gDQo+IA0KPiANCj4gDQo+IFBsZWFzZSBub3RlIHRoYXQgaXQgbWF5IHRha2Ug
YSBjb3VwbGUgb2YgbWludXRlcyBmcm9tIHRoZSB0aW1lIG9mDQo+IHN1Ym1pc3Npb24gdW50aWwg
dGhlIGh0bWxpemVkIHZlcnNpb24gYW5kIGRpZmYgYXJlIGF2YWlsYWJsZSBhdA0KPiB0b29scy5p
ZXRmLm9yZy4NCj4gDQo+IFRoZSBJRVRGIFNlY3JldGFyaWF0DQo+IA0KPiANCg0K


From suresh.krishnan@ericsson.com  Tue Aug 20 21:01:46 2013
Return-Path: <suresh.krishnan@ericsson.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 7CB1D11E8384 for <int-area@ietfa.amsl.com>; Tue, 20 Aug 2013 21:01:46 -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=[AWL=0.000, 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 8-AwLjM13DEP for <int-area@ietfa.amsl.com>; Tue, 20 Aug 2013 21:01:39 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id CF44811E80FF for <int-area@ietf.org>; Tue, 20 Aug 2013 21:01:39 -0700 (PDT)
X-AuditID: c6180641-b7fe28e000000d82-71-52143ba25e73
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id B0.59.03458.2AB34125; Wed, 21 Aug 2013 06:01:38 +0200 (CEST)
Received: from [164.48.125.52] (147.117.188.135) by smtps-am.internal.ericsson.com (147.117.188.87) with Microsoft SMTP Server (TLS) id 14.2.328.9; Wed, 21 Aug 2013 00:01:37 -0400
Message-ID: <52143AFF.3060403@ericsson.com>
Date: Tue, 20 Aug 2013 23:58:55 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
To: Internet Area <int-area@ietf.org>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [147.117.188.135]
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrLJMWRmVeSWpSXmKPExsUyuXRPuO4ia5Egg79TzS1uzLrJ4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujParn5gLrrFUTPt0i7GB8S5zFyMHh4SAicS5NxFdjJxAppjE hXvr2UBsIYGjjBLL/0d1MXIB2dsZJTqu9zOBJHgFtCVO3bnDCmKzCKhK7Dx4iQXEZgOas2Hn Z7AaUYEwifvnDkHVC0qcnPkErEYEqP711otgC4QFzCROTnzABrFYUmLbomPsIDazgJ7ElKst jBC2vMT2t3OYIQ7SlNi65jsrxM3KEjtmJE5gFJiFZMMsJN2zkHQvYGRexchRWpxalptuZLiJ ERhkxyTYHHcwLvhkeYhRmoNFSZx3g96ZQCGB9MSS1OzU1ILUovii0pzU4kOMTBycUg2MHvJT PC1WvlCyl3hw6s99xRONd2vLalIlF+6d81HjyFtG7o8M+RnHPk4pZijLWto+xcd8Y/oMLcue 5xckr+caF5v9XyvNzLDrX2DiwlkHc1a8/F0RYOEjpuL9kzdNuKh6zt1PsSwiOq+CldapJ0yI lPr9lt0079v5pvi+UCW+Ywr5B+7ek5+mxFKckWioxVxUnAgArXP1wAACAAA=
Subject: [Int-area] Call for adoption of draft-nachum-sarp-06.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, 21 Aug 2013 04:01:46 -0000

Hi all,
  This draft has been presented at several intarea face to face meetings
and has received quite a bit of discussion. It has been difficult to
gauge whether the wg is interested in this work or not. This call is
being initiated to determine whether there is WG consensus towards
adoption of draft-nachum-sarp-06 as an intarea WG draft. Please state
whether or not you're in favor of the adoption by replying to this
email. If you are not in favor, please also state your objections in
your response. This adoption call will complete on 2013-09-04.

Regards
Suresh & Julien




From jiangsheng@huawei.com  Thu Aug 22 18:48:10 2013
Return-Path: <jiangsheng@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 BE94D21F9E69 for <int-area@ietfa.amsl.com>; Thu, 22 Aug 2013 18:48:10 -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 M0f85ic7hfsd for <int-area@ietfa.amsl.com>; Thu, 22 Aug 2013 18:48:06 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 3FAFE21F9E48 for <int-area@ietf.org>; Thu, 22 Aug 2013 18:48:06 -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 AWI71097; Fri, 23 Aug 2013 01:48:04 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 23 Aug 2013 02:47:06 +0100
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 23 Aug 2013 02:48:02 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.66]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.01.0323.007; Fri, 23 Aug 2013 09:47:55 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Internet Area <int-area@ietf.org>
Thread-Topic: [Int-area] Call for adoption of draft-nachum-sarp-06.txt
Thread-Index: AQHOniNEIagGiH1urESXIhoJk1D+K5miCLzQ
Date: Fri, 23 Aug 2013 01:47:55 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AD00331@nkgeml512-mbx.china.huawei.com>
References: <52143AFF.3060403@ericsson.com>
In-Reply-To: <52143AFF.3060403@ericsson.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [Int-area] Call for adoption of draft-nachum-sarp-06.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, 23 Aug 2013 01:48:10 -0000

U3VwcG9ydCB0aGUgYWRvcHRpb24uIFRoaXMgZG9jdW1lbnQgaGFzIHRhcmdldGVkIGEgcmVhbCBp
c3N1ZSBhbmQgcHJvcG9zZWQgYSB3b3JrYWJsZSBzb2x1dGlvbi4NCg0KUmVnYXJkcywNCg0KU2hl
bmcNCg0KPi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+RnJvbTogaW50LWFyZWEtYm91bmNl
c0BpZXRmLm9yZyBbbWFpbHRvOmludC1hcmVhLWJvdW5jZXNAaWV0Zi5vcmddIE9uDQo+QmVoYWxm
IE9mIFN1cmVzaCBLcmlzaG5hbg0KPlNlbnQ6IFdlZG5lc2RheSwgQXVndXN0IDIxLCAyMDEzIDEx
OjU5IEFNDQo+VG86IEludGVybmV0IEFyZWENCj5TdWJqZWN0OiBbSW50LWFyZWFdIENhbGwgZm9y
IGFkb3B0aW9uIG9mIGRyYWZ0LW5hY2h1bS1zYXJwLTA2LnR4dA0KPg0KPkhpIGFsbCwNCj4gIFRo
aXMgZHJhZnQgaGFzIGJlZW4gcHJlc2VudGVkIGF0IHNldmVyYWwgaW50YXJlYSBmYWNlIHRvIGZh
Y2UgbWVldGluZ3MNCj5hbmQgaGFzIHJlY2VpdmVkIHF1aXRlIGEgYml0IG9mIGRpc2N1c3Npb24u
IEl0IGhhcyBiZWVuIGRpZmZpY3VsdCB0bw0KPmdhdWdlIHdoZXRoZXIgdGhlIHdnIGlzIGludGVy
ZXN0ZWQgaW4gdGhpcyB3b3JrIG9yIG5vdC4gVGhpcyBjYWxsIGlzDQo+YmVpbmcgaW5pdGlhdGVk
IHRvIGRldGVybWluZSB3aGV0aGVyIHRoZXJlIGlzIFdHIGNvbnNlbnN1cyB0b3dhcmRzDQo+YWRv
cHRpb24gb2YgZHJhZnQtbmFjaHVtLXNhcnAtMDYgYXMgYW4gaW50YXJlYSBXRyBkcmFmdC4gUGxl
YXNlIHN0YXRlDQo+d2hldGhlciBvciBub3QgeW91J3JlIGluIGZhdm9yIG9mIHRoZSBhZG9wdGlv
biBieSByZXBseWluZyB0byB0aGlzDQo+ZW1haWwuIElmIHlvdSBhcmUgbm90IGluIGZhdm9yLCBw
bGVhc2UgYWxzbyBzdGF0ZSB5b3VyIG9iamVjdGlvbnMgaW4NCj55b3VyIHJlc3BvbnNlLiBUaGlz
IGFkb3B0aW9uIGNhbGwgd2lsbCBjb21wbGV0ZSBvbiAyMDEzLTA5LTA0Lg0KPg0KPlJlZ2FyZHMN
Cj5TdXJlc2ggJiBKdWxpZW4NCj4NCj4NCj4NCj5fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fXw0KPkludC1hcmVhIG1haWxpbmcgbGlzdA0KPkludC1hcmVhQGll
dGYub3JnDQo+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pbnQtYXJlYQ0K

From sarikaya2012@gmail.com  Fri Aug 23 08:12:10 2013
Return-Path: <sarikaya2012@gmail.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 26DC811E827B for <int-area@ietfa.amsl.com>; Fri, 23 Aug 2013 08:12:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-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 da1TIze7HS2o for <int-area@ietfa.amsl.com>; Fri, 23 Aug 2013 08:12:09 -0700 (PDT)
Received: from mail-la0-x22a.google.com (mail-la0-x22a.google.com [IPv6:2a00:1450:4010:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 1D1D611E81B8 for <int-area@ietf.org>; Fri, 23 Aug 2013 08:12:08 -0700 (PDT)
Received: by mail-la0-f42.google.com with SMTP id ep20so590877lab.29 for <int-area@ietf.org>; Fri, 23 Aug 2013 08:12:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=RebbNbpvab1yr513NranmKuHYYkMOdltsH0etpiNvbo=; b=jTvEX04Q2+3pYIybOf+/eEiEa7VUgoYFH4acogEjR1fA8CEG1UQLENXNfypNCnKKYs jFrTud3QzySEoL9LJNF/U601g0O9cf+xf69LPpBg5HQg2Qfy5o8pF86ZiD+C00+3JvO3 2lDAwq/3tXAH22ju7PYc7ZPpw6PE2XQsTNyYVT6fNYI408OBOYabMOkVdzsLdi+a/bSJ +WVEgutSvjBgQcBMKvvWtXzbVOA1GVVfSqksrNoDGxMv606ck84dr3eWn10SVE1fU5MH EpHNlN2P7YfLCsUTBXPBQeiWmLLRmKO7M4eqnHTMHY0qjhbOnR7o5atrO5kZPfJeGgVa SYoQ==
MIME-Version: 1.0
X-Received: by 10.152.87.169 with SMTP id az9mr65969lab.65.1377270727998; Fri, 23 Aug 2013 08:12:07 -0700 (PDT)
Received: by 10.114.98.227 with HTTP; Fri, 23 Aug 2013 08:12:07 -0700 (PDT)
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AD00331@nkgeml512-mbx.china.huawei.com>
References: <52143AFF.3060403@ericsson.com> <5D36713D8A4E7348A7E10DF7437A4B923AD00331@nkgeml512-mbx.china.huawei.com>
Date: Fri, 23 Aug 2013 10:12:07 -0500
Message-ID: <CAC8QAcfErmVMXmEZ-v6JAo3XJVCET0ZTUJ1xtNtokAGKmvL4FQ@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Sheng Jiang <jiangsheng@huawei.com>
Content-Type: multipart/alternative; boundary=001a11c240dc80818004e49ed40a
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] Call for adoption of draft-nachum-sarp-06.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: sarikaya@ieee.org
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, 23 Aug 2013 15:12:10 -0000

--001a11c240dc80818004e49ed40a
Content-Type: text/plain; charset=ISO-8859-1

+1

Regards,

Behcet


On Thu, Aug 22, 2013 at 8:47 PM, Sheng Jiang <jiangsheng@huawei.com> wrote:

> Support the adoption. This document has targeted a real issue and proposed
> a workable solution.
>
> Regards,
>
> Sheng
>
> >-----Original Message-----
> >From: int-area-bounces@ietf.org [mailto:int-area-bounces@ietf.org] On
> >Behalf Of Suresh Krishnan
> >Sent: Wednesday, August 21, 2013 11:59 AM
> >To: Internet Area
> >Subject: [Int-area] Call for adoption of draft-nachum-sarp-06.txt
> >
> >Hi all,
> >  This draft has been presented at several intarea face to face meetings
> >and has received quite a bit of discussion. It has been difficult to
> >gauge whether the wg is interested in this work or not. This call is
> >being initiated to determine whether there is WG consensus towards
> >adoption of draft-nachum-sarp-06 as an intarea WG draft. Please state
> >whether or not you're in favor of the adoption by replying to this
> >email. If you are not in favor, please also state your objections in
> >your response. This adoption call will complete on 2013-09-04.
> >
> >Regards
> >Suresh & Julien
> >
> >
> >
> >_______________________________________________
> >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
>

--001a11c240dc80818004e49ed40a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>+1<br><br></div>Regards,<br><br></div>Behcet<br>=
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Thu,=
 Aug 22, 2013 at 8:47 PM, Sheng Jiang <span dir=3D"ltr">&lt;<a href=3D"mail=
to:jiangsheng@huawei.com" target=3D"_blank">jiangsheng@huawei.com</a>&gt;</=
span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Support the adoption. This document has targ=
eted a real issue and proposed a workable solution.<br>
<br>
Regards,<br>
<br>
Sheng<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
&gt;-----Original Message-----<br>
&gt;From: <a href=3D"mailto:int-area-bounces@ietf.org">int-area-bounces@iet=
f.org</a> [mailto:<a href=3D"mailto:int-area-bounces@ietf.org">int-area-bou=
nces@ietf.org</a>] On<br>
&gt;Behalf Of Suresh Krishnan<br>
&gt;Sent: Wednesday, August 21, 2013 11:59 AM<br>
&gt;To: Internet Area<br>
&gt;Subject: [Int-area] Call for adoption of draft-nachum-sarp-06.txt<br>
&gt;<br>
&gt;Hi all,<br>
&gt; =A0This draft has been presented at several intarea face to face meeti=
ngs<br>
&gt;and has received quite a bit of discussion. It has been difficult to<br=
>
&gt;gauge whether the wg is interested in this work or not. This call is<br=
>
&gt;being initiated to determine whether there is WG consensus towards<br>
&gt;adoption of draft-nachum-sarp-06 as an intarea WG draft. Please state<b=
r>
&gt;whether or not you&#39;re in favor of the adoption by replying to this<=
br>
&gt;email. If you are not in favor, please also state your objections in<br=
>
&gt;your response. This adoption call will complete on 2013-09-04.<br>
&gt;<br>
&gt;Regards<br>
&gt;Suresh &amp; Julien<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;_______________________________________________<br>
&gt;Int-area mailing list<br>
&gt;<a href=3D"mailto:Int-area@ietf.org">Int-area@ietf.org</a><br>
&gt;<a href=3D"https://www.ietf.org/mailman/listinfo/int-area" target=3D"_b=
lank">https://www.ietf.org/mailman/listinfo/int-area</a><br>
_______________________________________________<br>
Int-area mailing list<br>
<a href=3D"mailto:Int-area@ietf.org">Int-area@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/int-area" target=3D"_blank=
">https://www.ietf.org/mailman/listinfo/int-area</a><br>
</div></div></blockquote></div><br></div>

--001a11c240dc80818004e49ed40a--

From shares@ndzh.com  Fri Aug 23 09:14:03 2013
Return-Path: <shares@ndzh.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 EFE9F11E81BF for <int-area@ietfa.amsl.com>; Fri, 23 Aug 2013 09:14:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.062
X-Spam-Level: 
X-Spam-Status: No, score=-0.062 tagged_above=-999 required=5 tests=[AWL=-0.323, BAYES_20=-0.74, DOS_OUTLOOK_TO_MX=1, HTML_MESSAGE=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 jaXS6xaKXvT9 for <int-area@ietfa.amsl.com>; Fri, 23 Aug 2013 09:13:59 -0700 (PDT)
Received: from hickoryhill-consulting.com (hhc-web3.hickoryhill-consulting.com [64.9.205.143]) by ietfa.amsl.com (Postfix) with ESMTP id CD59111E8103 for <int-area@ietf.org>; Fri, 23 Aug 2013 09:13:58 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=174.124.177.50; 
From: "Susan Hares" <shares@ndzh.com>
To: <int-area@ietf.org>
Date: Fri, 23 Aug 2013 12:13:56 -0400
Message-ID: <01c701cea01b$c54bbf80$4fe33e80$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01C8_01CE9FFA.3E3AE2D0"
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: Ac6gG5ZNKxnBwREVTYa8sRnW7gBXZg==
X-Authenticated-User: skh@ndzh.com 
Subject: [Int-area]  Call for adoption of draft-nachum-sarp-06.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, 23 Aug 2013 16:14:04 -0000

This is a multipart message in MIME format.

------=_NextPart_000_01C8_01CE9FFA.3E3AE2D0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Suresh and Julien:

 

+1 - in favor of adopton 

 

Also +1 - will commit to comment and review drafts.

 

Sue Hares 


------=_NextPart_000_01C8_01CE9FFA.3E3AE2D0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Suresh and =
Julien:<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>+1 &#8211; in favor of adopton <o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Also +1 =
&#8211; will commit to comment and review drafts.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Sue Hares =
<o:p></o:p></p></div></body></html>
------=_NextPart_000_01C8_01CE9FFA.3E3AE2D0--


From linda.dunbar@huawei.com  Fri Aug 23 10:58:41 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 2B93811E8121 for <int-area@ietfa.amsl.com>; Fri, 23 Aug 2013 10:58:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.278
X-Spam-Level: 
X-Spam-Status: No, score=-5.278 tagged_above=-999 required=5 tests=[AWL=1.321,  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 aXEV3Nf8296c for <int-area@ietfa.amsl.com>; Fri, 23 Aug 2013 10:58:37 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 96E7B11E80ED for <int-area@ietf.org>; Fri, 23 Aug 2013 10:58:36 -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 AUQ99904; Fri, 23 Aug 2013 17:58:26 +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; Fri, 23 Aug 2013 18:57:51 +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; Fri, 23 Aug 2013 18:58:25 +0100
Received: from DFWEML509-MBX.china.huawei.com ([169.254.11.52]) by dfweml405-hub.china.huawei.com ([10.193.5.102]) with mapi id 14.01.0323.007; Fri, 23 Aug 2013 10:58:22 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>, Internet Area <int-area@ietf.org>
Thread-Topic: [Int-area] Call for adoption of draft-nachum-sarp-06.txt
Thread-Index: AQHOniNFMXHqUclFB0+plegHtPYYUJmjF4gg
Date: Fri, 23 Aug 2013 17:58:21 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F645B83278@dfweml509-mbx.china.huawei.com>
References: <52143AFF.3060403@ericsson.com>
In-Reply-To: <52143AFF.3060403@ericsson.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.146.172]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [Int-area] Call for adoption of draft-nachum-sarp-06.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, 23 Aug 2013 17:58:41 -0000

Support!


This draft is about the proxy gateway to make switch's FDB not explode in D=
C environment where hosts in one VLAN (or subnet) can be placed anywhere.=20

NVo3 and TRILL can hide hosts' addresses from switches/routers in the core.=
 But If NVO3 edges (NVE) are Top of Rack switches or End of Row switches,  =
those edge switches and switches between hosts (VMs) and Overlay Edges will=
 also run into MAC table explosion problem.

When hosts in a VLAN (or subnet) span across multiple access domains and ea=
ch access domain has hosts belonging to different VLANs, each access switch=
 has to enable many VLANs. Then, those access switches will be exposed to a=
ll MAC addresses among all the VLANs enabled.

The draft specifies a scheme to allow all hosts in an access domain to be r=
epresented by the Domain Gateway MAC address(es). By doing so, switches in =
each domain are only exposed to MAC addresses of local hosts and remote gat=
eway MAC addresses. So that their FDB will not explode as VLANs spread acro=
ss many access domains.

If this draft is adopted by the WG, we might need to use a more accurate ti=
tle, something along the line of Proxy-Gateway.=20

Linda


> -----Original Message-----
> From: int-area-bounces@ietf.org [mailto:int-area-bounces@ietf.org] On
> Behalf Of Suresh Krishnan
> Sent: Tuesday, August 20, 2013 10:59 PM
> To: Internet Area
> Subject: [Int-area] Call for adoption of draft-nachum-sarp-06.txt
>=20
> Hi all,
>   This draft has been presented at several intarea face to face
> meetings
> and has received quite a bit of discussion. It has been difficult to
> gauge whether the wg is interested in this work or not. This call is
> being initiated to determine whether there is WG consensus towards
> adoption of draft-nachum-sarp-06 as an intarea WG draft. Please state
> whether or not you're in favor of the adoption by replying to this
> email. If you are not in favor, please also state your objections in
> your response. This adoption call will complete on 2013-09-04.
>=20
> Regards
> Suresh & Julien
>=20
>=20
>=20
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area

From d3e3e3@gmail.com  Fri Aug 23 16:19:16 2013
Return-Path: <d3e3e3@gmail.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 2BA4621F9EAD for <int-area@ietfa.amsl.com>; Fri, 23 Aug 2013 16:19:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.149
X-Spam-Level: 
X-Spam-Status: No, score=-102.149 tagged_above=-999 required=5 tests=[AWL=0.451, 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 P7uGZl8iZqiq for <int-area@ietfa.amsl.com>; Fri, 23 Aug 2013 16:19:15 -0700 (PDT)
Received: from mail-ob0-x236.google.com (mail-ob0-x236.google.com [IPv6:2607:f8b0:4003:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id AB2CE21F9EA8 for <int-area@ietf.org>; Fri, 23 Aug 2013 16:19:15 -0700 (PDT)
Received: by mail-ob0-f182.google.com with SMTP id wo10so1288157obc.41 for <int-area@ietf.org>; Fri, 23 Aug 2013 16:19:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=mR2DTysgCspYIsSgKYriGyUTunzf9AZMaO52IOEk3ho=; b=iSigd/ZQ88OkVYdAiQxlqZazsh6PSlqCv9mo1vr4jrO+fxVT2Ba0CZkvcjs2p7S1mm rvBiOBMj7pHR1ERRSX08P19MEGnu+ljgrEeITSM3iZoPnLn+fdeJmBuOqgc2ZFl9gfZW WZ37F3vk/JdsOFQi/lds2s3Tn5lJZwzNyIsPSvPKMsB9zwC2z4dtAOwtbICXC1NGiiah +rfURV1df1r/eY9kQdvNC9kIZ5rw5EhIULt3KVkQS7yoasxvDjVWi3Q//BCaU0HkdBHV lKkaO6hAQV9BoJfGV6PmlIY4z4xZsuR/wFFmzi69jFIcb538bVMS0mtoGsJhmu+2Jjeg N6gA==
X-Received: by 10.60.95.229 with SMTP id dn5mr1815075oeb.26.1377299955227; Fri, 23 Aug 2013 16:19:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.131.7 with HTTP; Fri, 23 Aug 2013 16:18:55 -0700 (PDT)
In-Reply-To: <52143AFF.3060403@ericsson.com>
References: <52143AFF.3060403@ericsson.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 23 Aug 2013 19:18:55 -0400
Message-ID: <CAF4+nEHpxzqdzQLBN1u+xrnMyJZu9=HkHUU=wwaB2-u5prtxrw@mail.gmail.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] Call for adoption of draft-nachum-sarp-06.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, 23 Aug 2013 23:19:16 -0000

I believe this draft should be adopted by the INTAREA WG. It promises
substantial reductions in MAC learning load and multi-destination
frames, improving scaling. There is additional engineering to be done
on this draft and the INTAREA WG seems like an appropriate place to do
that work.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com


On Tue, Aug 20, 2013 at 11:58 PM, Suresh Krishnan
<suresh.krishnan@ericsson.com> wrote:
> Hi all,
>   This draft has been presented at several intarea face to face meetings
> and has received quite a bit of discussion. It has been difficult to
> gauge whether the wg is interested in this work or not. This call is
> being initiated to determine whether there is WG consensus towards
> adoption of draft-nachum-sarp-06 as an intarea WG draft. Please state
> whether or not you're in favor of the adoption by replying to this
> email. If you are not in favor, please also state your objections in
> your response. This adoption call will complete on 2013-09-04.
>
> Regards
> Suresh & Julien
>
>
>
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area

From melinda.shore@gmail.com  Fri Aug 23 16:37:58 2013
Return-Path: <melinda.shore@gmail.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 F409721F9AFE for <int-area@ietfa.amsl.com>; Fri, 23 Aug 2013 16:37:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 JWj6yZtLKe8t for <int-area@ietfa.amsl.com>; Fri, 23 Aug 2013 16:37:57 -0700 (PDT)
Received: from mail-pb0-x234.google.com (mail-pb0-x234.google.com [IPv6:2607:f8b0:400e:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id 97F6A21F9AC1 for <int-area@ietf.org>; Fri, 23 Aug 2013 16:37:57 -0700 (PDT)
Received: by mail-pb0-f52.google.com with SMTP id wz12so1219515pbc.39 for <int-area@ietf.org>; Fri, 23 Aug 2013 16:37:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=IYsF6PFgl5AI3eD5aSH2pa2tJyXgFP7PMiRq6oM8bNY=; b=RULHfqWEyNNGJULONcjJy95DidlJunfmMtvgZjoZQf/DFDfuuD8gVV5Hserak4iZwC lin9tJqNxBREdMUphoqt4Q29XDmlJZ9hQXfSYbgy1B8nye4OyFdZ/uMZ6YjHGIykzXUo acoxS+g+HhmBrilzyk8ItNMnJ2wMPi58H4f5Kigab0YJ9l4cV+S+bs1fx/iD+9zSo3YI JvuUJGzfgK00MAnR3ly45FJa9RuAqmtc8FvMSwFb54o11dh7Rl6glUA6tyLFBZUQECNT 6GlN743tJ8FDqfkKmTIIVuB0ojvX+MkyjRrF5byYRsnnYGilWHEV/kF1BCsxgYAUPW18 vGmQ==
X-Received: by 10.67.11.103 with SMTP id eh7mr1408660pad.153.1377301077338; Fri, 23 Aug 2013 16:37:57 -0700 (PDT)
Received: from spandex.local (209-193-57-23-rb1.fai.dsl.dynamic.acsalaska.net. [209.193.57.23]) by mx.google.com with ESMTPSA id jf4sm2251802pbb.19.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 23 Aug 2013 16:37:56 -0700 (PDT)
Message-ID: <5217F252.6010301@gmail.com>
Date: Fri, 23 Aug 2013 15:37:54 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
References: <52143AFF.3060403@ericsson.com> <CAF4+nEHpxzqdzQLBN1u+xrnMyJZu9=HkHUU=wwaB2-u5prtxrw@mail.gmail.com>
In-Reply-To: <CAF4+nEHpxzqdzQLBN1u+xrnMyJZu9=HkHUU=wwaB2-u5prtxrw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] Call for adoption of draft-nachum-sarp-06.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, 23 Aug 2013 23:37:58 -0000

>   This draft has been presented at several intarea face to face meetings
> and has received quite a bit of discussion. It has been difficult to
> gauge whether the wg is interested in this work or not. This call is
> being initiated to determine whether there is WG consensus towards
> adoption of draft-nachum-sarp-06 as an intarea WG draft. Please state
> whether or not you're in favor of the adoption by replying to this
> email. If you are not in favor, please also state your objections in
> your response. This adoption call will complete on 2013-09-04.

I'd like to see the working group adopt this draft.  This problem
is well-documented but unresolved, and this proposal seems like a
reasonable place to start.

Melinda


From talmi@marvell.com  Tue Aug 27 23:40:04 2013
Return-Path: <talmi@marvell.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 5684011E8141 for <int-area@ietfa.amsl.com>; Tue, 27 Aug 2013 23:40:04 -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 bFznBdnKtVty for <int-area@ietfa.amsl.com>; Tue, 27 Aug 2013 23:39:59 -0700 (PDT)
Received: from na3sys009aog137.obsmtp.com (na3sys009aog137.obsmtp.com [74.125.149.18]) by ietfa.amsl.com (Postfix) with ESMTP id A7D2E11E8109 for <int-area@ietf.org>; Tue, 27 Aug 2013 23:39:54 -0700 (PDT)
Received: from sc-owa02.marvell.com ([199.233.58.137]) (using TLSv1) by na3sys009aob137.postini.com ([74.125.148.12]) with SMTP ID DSNKUh2bOC7yYm4CBdO7Szm/qrkMiiorCqS9@postini.com; Tue, 27 Aug 2013 23:39:56 PDT
Received: from YK-HUB01.marvell.com (10.4.102.51) by sc-owa02.marvell.com (10.93.76.22) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 27 Aug 2013 23:37:16 -0700
Received: from IL-MB01.marvell.com ([10.4.102.53]) by YK-HUB01.marvell.com ([10.4.102.51]) with mapi; Wed, 28 Aug 2013 09:35:58 +0300
From: Tal Mizrahi <talmi@marvell.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>, Internet Area <int-area@ietf.org>
Date: Wed, 28 Aug 2013 09:35:57 +0300
Thread-Topic: [Int-area] Call for adoption of draft-nachum-sarp-06.txt
Thread-Index: Ac6eIyuUAjsgz+7mRYiV7gqOpL581gFlY/2g
Message-ID: <74470498B659FA4687F0B0018C19A89C01B87D3B0DD6@IL-MB01.marvell.com>
References: <52143AFF.3060403@ericsson.com>
In-Reply-To: <52143AFF.3060403@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Int-area] Call for adoption of draft-nachum-sarp-06.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, 28 Aug 2013 06:40:04 -0000

I support WG adoption
(as a co-author)

Tal.


-----Original Message-----
From: int-area-bounces@ietf.org [mailto:int-area-bounces@ietf.org] On Behal=
f Of Suresh Krishnan
Sent: Wednesday, August 21, 2013 6:59 AM
To: Internet Area
Subject: [Int-area] Call for adoption of draft-nachum-sarp-06.txt

Hi all,
  This draft has been presented at several intarea face to face meetings an=
d has received quite a bit of discussion. It has been difficult to gauge wh=
ether the wg is interested in this work or not. This call is being initiate=
d to determine whether there is WG consensus towards adoption of draft-nach=
um-sarp-06 as an intarea WG draft. Please state whether or not you're in fa=
vor of the adoption by replying to this email. If you are not in favor, ple=
ase also state your objections in your response. This adoption call will co=
mplete on 2013-09-04.

Regards
Suresh & Julien



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

From hu.fangwei@zte.com.cn  Tue Aug 27 23:43:19 2013
Return-Path: <hu.fangwei@zte.com.cn>
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 2868511E8125; Tue, 27 Aug 2013 23:43:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.839
X-Spam-Level: 
X-Spam-Status: No, score=-98.839 tagged_above=-999 required=5 tests=[AWL=3.759, BAYES_00=-2.599, HTML_MESSAGE=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 PLG47+ffjhNK; Tue, 27 Aug 2013 23:43:15 -0700 (PDT)
Received: from zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id BA1E211E8104; Tue, 27 Aug 2013 23:43:14 -0700 (PDT)
Received: from mse02.zte.com.cn (unknown [10.30.3.21]) by Websense Email Security Gateway with ESMTPS id 3F2E41255BA9; Wed, 28 Aug 2013 14:42:46 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id r7S6ggOv001671; Wed, 28 Aug 2013 14:42:42 +0800 (GMT-8) (envelope-from hu.fangwei@zte.com.cn)
In-Reply-To: <74470498B659FA4687F0B0018C19A89C01B87D3B0DD6@IL-MB01.marvell.com>
To: Internet Area <int-area@ietf.org>, int-area-bounces@ietf.org, Suresh Krishnan <suresh.krishnan@ericsson.com>
MIME-Version: 1.0
X-KeepSent: C0CC5CFE:7D2CB5D1-48257BD5:0024AFF7; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OFC0CC5CFE.7D2CB5D1-ON48257BD5.0024AFF7-48257BD5.0024CF4E@zte.com.cn>
From: hu.fangwei@zte.com.cn
Date: Wed, 28 Aug 2013 14:42:20 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2013-08-28 14:42:39, Serialize complete at 2013-08-28 14:42:39
Content-Type: multipart/alternative; boundary="=_alternative 0024CF4E48257BD5_="
X-MAIL: mse02.zte.com.cn r7S6ggOv001671
Subject: Re: [Int-area] Call for adoption of draft-nachum-sarp-06.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, 28 Aug 2013 06:43:19 -0000

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

I have read the draft, and support for adoption.

Fangwei
 



Subject: [Int-area] Call for adoption of draft-nachum-sarp-06.txt

Hi all,
  This draft has been presented at several intarea face to face meetings 
and has received quite a bit of discussion. It has been difficult to gauge 
whether the wg is interested in this work or not. This call is being 
initiated to determine whether there is WG consensus towards adoption of 
draft-nachum-sarp-06 as an intarea WG draft. Please state whether or not 
you're in favor of the adoption by replying to this email. If you are not 
in favor, please also state your objections in your response. This 
adoption call will complete on 2013-09-04.

Regards
Suresh & Julien



_______________________________________________
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


--=_alternative 0024CF4E48257BD5_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">I have read the draft, and support for
adoption.</font>
<br>
<br><font size=2 face="sans-serif">Fangwei</font>
<br><font size=1 face="Arial">&nbsp;</font>
<br>
<br>
<br><tt><font size=2><br>
Subject: [Int-area] Call for adoption of draft-nachum-sarp-06.txt<br>
<br>
Hi all,<br>
 &nbsp;This draft has been presented at several intarea face to face meetings
and has received quite a bit of discussion. It has been difficult to gauge
whether the wg is interested in this work or not. This call is being initiated
to determine whether there is WG consensus towards adoption of draft-nachum-sarp-06
as an intarea WG draft. Please state whether or not you're in favor of
the adoption by replying to this email. If you are not in favor, please
also state your objections in your response. This adoption call will complete
on 2013-09-04.<br>
<br>
Regards<br>
Suresh &amp; Julien<br>
<br>
<br>
<br>
_______________________________________________<br>
Int-area mailing list<br>
Int-area@ietf.org<br>
https://www.ietf.org/mailman/listinfo/int-area<br>
_______________________________________________<br>
Int-area mailing list<br>
Int-area@ietf.org<br>
https://www.ietf.org/mailman/listinfo/int-area<br>
</font></tt>
<br>
--=_alternative 0024CF4E48257BD5_=--

From minch.zur@gmail.com  Thu Aug 29 00:55:33 2013
Return-Path: <minch.zur@gmail.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 3040921F84B7 for <int-area@ietfa.amsl.com>; Thu, 29 Aug 2013 00:55:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-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 Dgm3pYAALitL for <int-area@ietfa.amsl.com>; Thu, 29 Aug 2013 00:55:32 -0700 (PDT)
Received: from mail-ie0-x22e.google.com (mail-ie0-x22e.google.com [IPv6:2607:f8b0:4001:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 7B05621F847C for <int-area@ietf.org>; Thu, 29 Aug 2013 00:55:32 -0700 (PDT)
Received: by mail-ie0-f174.google.com with SMTP id k14so132428iea.19 for <int-area@ietf.org>; Thu, 29 Aug 2013 00:55:32 -0700 (PDT)
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 :cc:content-type; bh=1fBQ+2yRY7+9bkN3Y2NtNqWbq4gslB+1crlIDV7JzEI=; b=dRnAUc+stlY4etLsYMn3Hb6i9wcOOHXsYH82dxZEIq/VNvLfZXosEBYBUWkM9jwOos 7qvMYBqJ7ErJA+Xh9g3qvlh+ryWGmkxRxp91SIDA6J1ZgL2MMi4y7XLiZ9fKFl4gdkpZ rgMprrh5Xt+CF0jbxW0M+FJx9tkp+ipHrja/ZWCr4h6CPuG1u8QXTLAmuGNgAQaiLiRe babvDIak70A8wb87aZ/J94su3bKnZxjini83HAy3rNhUW2EEHY8XdUa27bdDhZMKp8d4 da/VsYatdP1IDSktsbAUAIrX092vPkfgufeV45dpP5NDwna6Nfo8h9WMrXYqDGPYtJ+C ud3w==
MIME-Version: 1.0
X-Received: by 10.42.65.82 with SMTP id k18mr1012107ici.23.1377762932093; Thu, 29 Aug 2013 00:55:32 -0700 (PDT)
Received: by 10.50.12.38 with HTTP; Thu, 29 Aug 2013 00:55:32 -0700 (PDT)
In-Reply-To: <74470498B659FA4687F0B0018C19A89C01B87D3B0DD6@IL-MB01.marvell.com>
References: <52143AFF.3060403@ericsson.com> <74470498B659FA4687F0B0018C19A89C01B87D3B0DD6@IL-MB01.marvell.com>
Date: Thu, 29 Aug 2013 15:55:32 +0800
Message-ID: <CA+L6EHGkFZDvR0+wTJdKvL_ZeL0iiOMjyWyaauxmRLLDFYGLyQ@mail.gmail.com>
From: Zur Minch <minch.zur@gmail.com>
To: Tal Mizrahi <talmi@marvell.com>
Content-Type: multipart/alternative; boundary=90e6ba614fc426fb7d04e5116e74
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] Call for adoption of draft-nachum-sarp-06.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, 29 Aug 2013 07:55:33 -0000

--90e6ba614fc426fb7d04e5116e74
Content-Type: text/plain; charset=ISO-8859-1

I've read the draft, it provides a valuable scalable MAC entries
solution for intra/inter data center. The proxy gateway described in the
draft makes switch's FDB not explode in data center environment where hosts
in one VLAN (or subnet) can be placed anywhere.

I support the draft adopt as WG draft.

Minch
2013/8/28 Tal Mizrahi <talmi@marvell.com>

> I support WG adoption
> (as a co-author)
>
> Tal.
>
>
> -----Original Message-----
> From: int-area-bounces@ietf.org [mailto:int-area-bounces@ietf.org] On
> Behalf Of Suresh Krishnan
> Sent: Wednesday, August 21, 2013 6:59 AM
> To: Internet Area
> Subject: [Int-area] Call for adoption of draft-nachum-sarp-06.txt
>
> Hi all,
>   This draft has been presented at several intarea face to face meetings
> and has received quite a bit of discussion. It has been difficult to gauge
> whether the wg is interested in this work or not. This call is being
> initiated to determine whether there is WG consensus towards adoption of
> draft-nachum-sarp-06 as an intarea WG draft. Please state whether or not
> you're in favor of the adoption by replying to this email. If you are not
> in favor, please also state your objections in your response. This adoption
> call will complete on 2013-09-04.
>
> Regards
> Suresh & Julien
>
>
>
> _______________________________________________
> 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
>

--90e6ba614fc426fb7d04e5116e74
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>I&#39;ve read the draft, it provides a valuable scalable MAC entries s=
olution=A0for intra/inter data center. The proxy gateway described in the d=
raft makes switch&#39;s FDB not explode in data center environment where ho=
sts in one VLAN (or subnet) can be placed anywhere.</div>

<div>=A0</div>
<div>I support the draft adopt as WG draft.</div>
<div>=A0</div>
<div>Minch<br></div>
<div class=3D"gmail_quote">2013/8/28 Tal Mizrahi <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:talmi@marvell.com" target=3D"_blank">talmi@marvell.com</a>&gt=
;</span><br>
<blockquote style=3D"BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PA=
DDING-LEFT:1ex" class=3D"gmail_quote">I support WG adoption<br>(as a co-aut=
hor)<br><br>Tal.<br><br><br>-----Original Message-----<br>From: <a href=3D"=
mailto:int-area-bounces@ietf.org">int-area-bounces@ietf.org</a> [mailto:<a =
href=3D"mailto:int-area-bounces@ietf.org">int-area-bounces@ietf.org</a>] On=
 Behalf Of Suresh Krishnan<br>
Sent: Wednesday, August 21, 2013 6:59 AM<br>To: Internet Area<br>Subject: [=
Int-area] Call for adoption of draft-nachum-sarp-06.txt<br><br>Hi all,<br>=
=A0 This draft has been presented at several intarea face to face meetings =
and has received quite a bit of discussion. It has been difficult to gauge =
whether the wg is interested in this work or not. This call is being initia=
ted to determine whether there is WG consensus towards adoption of draft-na=
chum-sarp-06 as an intarea WG draft. Please state whether or not you&#39;re=
 in favor of the adoption by replying to this email. If you are not in favo=
r, please also state your objections in your response. This adoption call w=
ill complete on 2013-09-04.<br>
<br>Regards<br>Suresh &amp; Julien<br><br><br><br>_________________________=
______________________<br>Int-area mailing list<br><a href=3D"mailto:Int-ar=
ea@ietf.org">Int-area@ietf.org</a><br><a href=3D"https://www.ietf.org/mailm=
an/listinfo/int-area" target=3D"_blank">https://www.ietf.org/mailman/listin=
fo/int-area</a><br>
_______________________________________________<br>Int-area mailing list<br=
><a href=3D"mailto:Int-area@ietf.org">Int-area@ietf.org</a><br><a href=3D"h=
ttps://www.ietf.org/mailman/listinfo/int-area" target=3D"_blank">https://ww=
w.ietf.org/mailman/listinfo/int-area</a><br>
</blockquote></div><br>

--90e6ba614fc426fb7d04e5116e74--

From youval@netoptics.com  Thu Aug 29 02:30:31 2013
Return-Path: <youval@netoptics.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 9F50A21F8749 for <int-area@ietfa.amsl.com>; Thu, 29 Aug 2013 02:30:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=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 gyqpDJb9hPYS for <int-area@ietfa.amsl.com>; Thu, 29 Aug 2013 02:30:25 -0700 (PDT)
Received: from mail.netoptics.com (mail.netoptics.com [208.74.182.243]) by ietfa.amsl.com (Postfix) with ESMTP id 5FC3921F9926 for <int-area@ietf.org>; Thu, 29 Aug 2013 02:30:22 -0700 (PDT)
Received: from WIN8M46R9BG5H4 (unknown [82.102.170.82]) by mail.netoptics.com (Postfix) with ESMTPSA id F0C801035E2B for <int-area@ietf.org>; Thu, 29 Aug 2013 02:30:20 -0700 (PDT)
From: "youval" <youval@netoptics.com>
To: "'Internet Area'" <int-area@ietf.org>
References: <52143AFF.3060403@ericsson.com>	<74470498B659FA4687F0B0018C19A89C01B87D3B0DD6@IL-MB01.marvell.com> <CA+L6EHGkFZDvR0+wTJdKvL_ZeL0iiOMjyWyaauxmRLLDFYGLyQ@mail.gmail.com>
In-Reply-To: <CA+L6EHGkFZDvR0+wTJdKvL_ZeL0iiOMjyWyaauxmRLLDFYGLyQ@mail.gmail.com>
Date: Thu, 29 Aug 2013 12:30:16 +0300
Message-ID: <00f601cea49a$61ed17d0$25c74770$@netoptics.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00F7_01CEA4B3.873AEC10"
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQKdj9YaflTMOnhcwuVtbC+CFyUm2gIa6QUAAp8q8kaX6EOZUA==
Content-Language: en-us
Subject: Re: [Int-area] Call for adoption of draft-nachum-sarp-06.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, 29 Aug 2013 09:30:31 -0000

This is a multipart message in MIME format.

------=_NextPart_000_00F7_01CEA4B3.873AEC10
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi all,

 

Support!

 

I believe that this draft should be adopted by the INTAREA WG. 

 

SARP architecture significantly reduces switches MAC table size and
decreases the impact of  ARP/ND retransmissions on the network. It also
provides scalability and mobility. 

I would like to keep the momentum of developing this draft and the INTAREA
WG is an appropriate WG to do so.

 

Best Regards 

UV


-----Original Message-----
From: int-area-bounces@ietf.org <mailto:int-area-bounces@ietf.org>
[mailto:int-area-bounces@ietf.org <mailto:int-area-bounces@ietf.org> ] On
Behalf Of Suresh Krishnan
Sent: Wednesday, August 21, 2013 6:59 AM
To: Internet Area
Subject: [Int-area] Call for adoption of draft-nachum-sarp-06.txt

Hi all,
  This draft has been presented at several intarea face to face meetings and
has received quite a bit of discussion. It has been difficult to gauge
whether the wg is interested in this work or not. This call is being
initiated to determine whether there is WG consensus towards adoption of
draft-nachum-sarp-06 as an intarea WG draft. Please state whether or not
you're in favor of the adoption by replying to this email. If you are not in
favor, please also state your objections in your response. This adoption
call will complete on 2013-09-04.

Regards
Suresh & Julien



_______________________________________________
Int-area mailing list
Int-area@ietf.org <mailto:Int-area@ietf.org> 
https://www.ietf.org/mailman/listinfo/int-area

 

 


------=_NextPart_000_00F7_01CEA4B3.873AEC10
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 15 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle18
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Hi =
all,<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Support!<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I believe =
that this draft should be adopted by the INTAREA WG. <o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>SARP =
architecture significantly reduces switches MAC table size and decreases =
the impact of &nbsp;ARP/ND retransmissions on the network. It also =
provides scalability and mobility. <o:p></o:p></p><p class=3DMsoNormal>I =
would like to keep the momentum of developing this draft and the INTAREA =
WG is an appropriate WG to do so.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Best Regards =
<o:p></o:p></p><p class=3DMsoNormal>UV<o:p></o:p></p><p =
class=3DMsoNormal><br>-----Original Message-----<br>From: <a =
href=3D"mailto:int-area-bounces@ietf.org">int-area-bounces@ietf.org</a> =
[mailto:<a =
href=3D"mailto:int-area-bounces@ietf.org">int-area-bounces@ietf.org</a>] =
On Behalf Of Suresh Krishnan<br>Sent: Wednesday, August 21, 2013 6:59 =
AM<br>To: Internet Area<br>Subject: [Int-area] Call for adoption of =
draft-nachum-sarp-06.txt<br><br>Hi all,<br>&nbsp; This draft has been =
presented at several intarea face to face meetings and has received =
quite a bit of discussion. It has been difficult to gauge whether the wg =
is interested in this work or not. This call is being initiated to =
determine whether there is WG consensus towards adoption of =
draft-nachum-sarp-06 as an intarea WG draft. Please state whether or not =
you're in favor of the adoption by replying to this email. If you are =
not in favor, please also state your objections in your response. This =
adoption call will complete on 2013-09-04.<br><br>Regards<br>Suresh =
&amp; =
Julien<br><br><br><br>_______________________________________________<br>=
Int-area mailing list<br><a =
href=3D"mailto:Int-area@ietf.org">Int-area@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/int-area" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/int-area</a><o:p>=
</o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p></div></body></html>
------=_NextPart_000_00F7_01CEA4B3.873AEC10--


From yilan@marvell.com  Thu Aug 29 06:10:06 2013
Return-Path: <yilan@marvell.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 2BFC421F9B25 for <int-area@ietfa.amsl.com>; Thu, 29 Aug 2013 06:10:06 -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=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 b7zLRZTLd2Xs for <int-area@ietfa.amsl.com>; Thu, 29 Aug 2013 06:10:04 -0700 (PDT)
Received: from na3sys009aog104.obsmtp.com (na3sys009aog104.obsmtp.com [74.125.149.73]) by ietfa.amsl.com (Postfix) with ESMTP id 5181B21E8085 for <int-area@ietf.org>; Thu, 29 Aug 2013 06:09:58 -0700 (PDT)
Received: from SC-OWA01.marvell.com ([199.233.58.136]) (using TLSv1) by na3sys009aob104.postini.com ([74.125.148.12]) with SMTP ID DSNKUh9IID5rnDEviIIt5sk7YPTsusw7jgMY@postini.com; Thu, 29 Aug 2013 06:09:58 PDT
Received: from YK-HUB02.marvell.com (10.4.102.52) by sc-owa01.marvell.com (10.93.76.21) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 29 Aug 2013 06:09:25 -0700
Received: from IL-MB01.marvell.com ([10.4.102.53]) by YK-HUB02.marvell.com ([10.4.102.52]) with mapi; Thu, 29 Aug 2013 16:09:22 +0300
From: Ilan Yerushalmi <yilan@marvell.com>
To: "int-area@ietf.org" <int-area@ietf.org>
Date: Thu, 29 Aug 2013 16:09:14 +0300
Thread-Topic: [Int-area] Call for adoption of draft-nachum-sarp-06.txt
Thread-Index: Ac6ktzroGdLeGQG2S+KhgGQ1PxJ67A==
Message-ID: <74470498B659FA4687F0B0018C19A89C01B87D3B12AC@IL-MB01.marvell.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_74470498B659FA4687F0B0018C19A89C01B87D3B12ACILMB01marve_"
MIME-Version: 1.0
Subject: [Int-area]  Call for adoption of draft-nachum-sarp-06.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, 29 Aug 2013 13:10:06 -0000

--_000_74470498B659FA4687F0B0018C19A89C01B87D3B12ACILMB01marve_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


I support WG adoption
(as a co-author)


Ilan


--_000_74470498B659FA4687F0B0018C19A89C01B87D3B12ACILMB01marve_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Arial","sans-serif";
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:10.0pt;font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span><=
/p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courie=
r New"'>I support WG adoption<o:p></o:p></span></p><p class=3DMsoNormal><sp=
an style=3D'font-size:10.0pt;font-family:"Courier New"'>(as a co-author)<o:=
p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;fon=
t-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><s=
pan style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-=
family:"Arial","sans-serif"'>Ilan<o:p></o:p></span></p><p class=3DMsoNormal=
><span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p>&nb=
sp;</o:p></span></p></div></body></html>=

--_000_74470498B659FA4687F0B0018C19A89C01B87D3B12ACILMB01marve_--

From david.i.allan@ericsson.com  Thu Aug 29 10:53:09 2013
Return-Path: <david.i.allan@ericsson.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 34A7421E80B9 for <int-area@ietfa.amsl.com>; Thu, 29 Aug 2013 10:53:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=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 rsT1MVqBUYUL for <int-area@ietfa.amsl.com>; Thu, 29 Aug 2013 10:53:01 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 5A96721E80A1 for <int-area@ietf.org>; Thu, 29 Aug 2013 10:53:01 -0700 (PDT)
X-AuditID: c6180641-b7fe28e000000d82-32-521f8a7c92ae
Received: from EUSAAHC006.ericsson.se (Unknown_Domain [147.117.188.90]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id E4.C7.03458.C7A8F125; Thu, 29 Aug 2013 19:53:00 +0200 (CEST)
Received: from EUSAAMB105.ericsson.se ([147.117.188.122]) by EUSAAHC006.ericsson.se ([147.117.188.90]) with mapi id 14.02.0328.009; Thu, 29 Aug 2013 13:53:00 -0400
From: David Allan I <david.i.allan@ericsson.com>
To: "int-area@ietf.org" <int-area@ietf.org>
Thread-Topic: Call for adoption of draft-nachum-sarp-06.txt
Thread-Index: Ac6k3Qh4liphP7t3SLCZUsNPa0sSWA==
Date: Thu, 29 Aug 2013 17:52:59 +0000
Message-ID: <E6C17D2345AC7A45B7D054D407AA205C11608602@eusaamb105.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.134]
Content-Type: multipart/alternative; boundary="_000_E6C17D2345AC7A45B7D054D407AA205C11608602eusaamb105erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrBLMWRmVeSWpSXmKPExsUyuXRPlG5Nl3yQQcdXS4sbs26yODB6LFny kymAMYrLJiU1J7MstUjfLoEr483VLsaCu6UVFybNYmxgnJXexcjJISFgIrGu5xQ7hC0mceHe erYuRi4OIYGjjBJNZ1ZCOcsZJT49ucgGUsUmYCCx5/8XRhBbREBbYv+TAywgtrCAmcTJiQ/Y IOLWEvOfzmaFsPUkPuy+AbaBRUBV4ufU9UwgNq+Ar8SU+ZvAehmBNn8/tQYsziwgLnHryXwm iIsEJJbsOc8MYYtKvHz8jxXCVpZY8mQ/C0R9vsSsrXuZIWYKSpyc+YRlAqPQLCSjZiEpm4Wk DCKuI7Fg9yc2CFtbYtnC18ww9pkDj5mQxRcwsq9i5CgtTi3LTTcy3MQIDP1jEmyOOxgXfLI8 xCjNwaIkzrtB70ygkEB6YklqdmpqQWpRfFFpTmrxIUYmDk6pBsa8dwdWzI9cqcllM+tZRMU6 81CFjKz7BxV/vJt2bskCwQkS9sa7646XprNLlMwW87617d+fads9otub07n+K6RmRjmV/XhR fnq1QdiM3S3vjLdVsdVwtv7ZHDFX5SH/a9+g+e+LgllFgr0key5PvKi+bX5XpcKr/+H8bgWq ORXTd9pN/Lj+SKcSS3FGoqEWc1FxIgDmip1OSwIAAA==
Subject: [Int-area] Call for adoption of draft-nachum-sarp-06.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, 29 Aug 2013 17:53:09 -0000

--_000_E6C17D2345AC7A45B7D054D407AA205C11608602eusaamb105erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi:

I have read this draft and will state I'm not a fan. My issues can be summa=
rized as follows:


1)  The first justification example in the motivation section is just plain=
 silly, yet I keep seeing it over and over in IETF discussions. No one woul=
d ever design and implement the deployment of any single application that w=
ay, let alone all apps attached to every TOR in a cloud. VM placement affin=
ity rules would NEVER see absolutely every local VM belonging to a differen=
t tenant network and requiring connectivity only to remote VMs. Which says =
to me this is a solution to a non-problem unless the goal is to circumvent =
near-malicious stupidity in the design of the provisioning algorithms used =
in the cloud management system.



2)  I believe the notion of an ARP proxy and use of MAC-NAT for scaling are=
 divisible concepts and each can be examined in isolation.

a.  If I want an ARP proxy system, Ethernet already defines the capability =
to map frames with a specific Ethertype to a distinct VLAN, so ARP transact=
ions (0x806) can be separated out of the datastream using existing standard=
ized technology and delivered to a remote proxy ARP system of any arbitrary=
 design, no further standardization required.

b.  An alternative to MAC NAT (a form of summarization in a flat dataplane)=
 is with MACinMAC (a form of summarization via hierarchical stacking). Whic=
h is already standardized and deployed and would have identical scaling pro=
perties. NVO3 class of solutions while not yet standard, have similar prope=
rties.

c.  MAC NAT itself means the e2e path has a pseudo L3 hop in it, which effe=
ctively prevents all L2 protocols (e.g. CFM, DCB etc.) from being able to i=
nstrument connectivity e2e, so (for example) to diagnose what looks like an=
 L2 hop, I would need to use both ETH-LB and ICMP ping, even then with ques=
tionable ability to fault sectionalize after the MAC NAT function.



So IMO solutions exist to the problem space both from the POV of operationa=
l practice. existing standardized technology, and solutions on the drawing =
board. I personally do not think we need yet another approach.



My 2 cents

Dave



----------------------------
Hi all,
  This draft has been presented at several intarea face to face meetings
and has received quite a bit of discussion. It has been difficult to
gauge whether the wg is interested in this work or not. This call is
being initiated to determine whether there is WG consensus towards
adoption of draft-nachum-sarp-06 as an intarea WG draft. Please state
whether or not you're in favor of the adoption by replying to this
email. If you are not in favor, please also state your objections in
your response. This adoption call will complete on 2013-09-04.

Regards
Suresh & Julien

--_000_E6C17D2345AC7A45B7D054D407AA205C11608602eusaamb105erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:323894814;
	mso-list-type:hybrid;
	mso-list-template-ids:-1011980592 67698705 67698713 67698715 67698703 6769=
8713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Hi:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">I have read this draft and will state I&#8217;m not a fan.=
 My issues can be summarized as follows:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"font-size:10.0pt;font-family:&q=
uot;Courier New&quot;"><span style=3D"mso-list:Ignore">1)<span style=3D"fon=
t:7.0pt &quot;Times New Roman&quot;">&nbsp;
</span></span></span><![endif]><span style=3D"font-size:10.0pt;font-family:=
&quot;Courier New&quot;">The first justification example in the motivation =
section is just plain silly, yet I keep seeing it over and over in IETF dis=
cussions. No one would ever design and implement
 the deployment of any single application that way, let alone all apps atta=
ched to every TOR in a cloud. VM placement affinity rules would NEVER see a=
bsolutely every local VM belonging to a different tenant network and requir=
ing connectivity only to remote
 VMs. Which says to me this is a solution to a non-problem unless the goal =
is to circumvent near-malicious stupidity in the design of the provisioning=
 algorithms used in the cloud management system.<o:p></o:p></span></p>
<p class=3D"MsoListParagraph"><span style=3D"font-size:10.0pt;font-family:&=
quot;Courier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"font-size:10.0pt;font-family:&q=
uot;Courier New&quot;"><span style=3D"mso-list:Ignore">2)<span style=3D"fon=
t:7.0pt &quot;Times New Roman&quot;">&nbsp;
</span></span></span><![endif]><span style=3D"font-size:10.0pt;font-family:=
&quot;Courier New&quot;">I believe the notion of an ARP proxy and use of MA=
C-NAT for scaling are divisible concepts and each can be examined in isolat=
ion.
<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.0in;text-indent:-.25in=
;mso-list:l0 level2 lfo1">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:&quot;Cour=
ier New&quot;"><span style=3D"mso-list:Ignore">a.<span style=3D"font:7.0pt =
&quot;Times New Roman&quot;">&nbsp;
</span></span></span><![endif]><span style=3D"font-size:10.0pt;font-family:=
&quot;Courier New&quot;">If I want an ARP proxy system, Ethernet already de=
fines the capability to map frames with a specific Ethertype to a distinct =
VLAN, so ARP transactions (0x806) can be separated
 out of the datastream using existing standardized technology and delivered=
 to a remote proxy ARP system of any arbitrary design, no further standardi=
zation required.<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.0in;text-indent:-.25in=
;mso-list:l0 level2 lfo1">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:&quot;Cour=
ier New&quot;"><span style=3D"mso-list:Ignore">b.<span style=3D"font:7.0pt =
&quot;Times New Roman&quot;">&nbsp;
</span></span></span><![endif]><span style=3D"font-size:10.0pt;font-family:=
&quot;Courier New&quot;">An alternative to MAC NAT (a form of summarization=
 in a flat dataplane) is with MACinMAC (a form of summarization via hierarc=
hical stacking). Which is already standardized
 and deployed and would have identical scaling properties. NVO3 class of so=
lutions while not yet standard, have similar properties.<o:p></o:p></span><=
/p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.0in;text-indent:-.25in=
;mso-list:l0 level2 lfo1">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:&quot;Cour=
ier New&quot;"><span style=3D"mso-list:Ignore">c.<span style=3D"font:7.0pt =
&quot;Times New Roman&quot;">&nbsp;
</span></span></span><![endif]><span style=3D"font-size:10.0pt;font-family:=
&quot;Courier New&quot;">MAC NAT itself means the e2e path has a pseudo L3 =
hop in it, which effectively prevents all L2 protocols (e.g. CFM, DCB etc.)=
 from being able to instrument connectivity
 e2e, so (for example) to diagnose what looks like an L2 hop, I would need =
to use both ETH-LB and ICMP ping, even then with questionable ability to fa=
ult sectionalize after the MAC NAT function.<o:p></o:p></span></p>
<p class=3D"MsoListParagraph"><span style=3D"font-size:10.0pt;font-family:&=
quot;Courier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:0in"><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;">So IMO solutions exist to=
 the problem space both from the POV of operational practice. existing stan=
dardized technology, and solutions on the drawing
 board. I personally do not think we need yet another approach.<o:p></o:p><=
/span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:0in"><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoListParagraph" style=3D"margin-left:0in"><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;">My 2 cents<o:p></o:p></sp=
an></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:0in"><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;">Dave<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">----------------------------<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Hi all,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp; This draft has been presented at several intarea fa=
ce to face meetings<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">and has received quite a bit of discussion. It has been di=
fficult to<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">gauge whether the wg is interested in this work or not. Th=
is call is<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">being initiated to determine whether there is WG consensus=
 towards<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">adoption of draft-nachum-sarp-06 as an intarea WG draft. P=
lease state<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">whether or not you're in favor of the adoption by replying=
 to this<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">email. If you are not in favor, please also state your obj=
ections in<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">your response. This adoption call will complete on 2013-09=
-04.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Regards<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;">Suresh &amp; Julien</span><o:p></o:p=
></p>
</div>
</body>
</html>

--_000_E6C17D2345AC7A45B7D054D407AA205C11608602eusaamb105erics_--

From linda.dunbar@huawei.com  Thu Aug 29 11:39:40 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 3FBC421E80BB for <int-area@ietfa.amsl.com>; Thu, 29 Aug 2013 11:39:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.655
X-Spam-Level: 
X-Spam-Status: No, score=-5.655 tagged_above=-999 required=5 tests=[AWL=0.943,  BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 JjTaNHL7IIkZ for <int-area@ietfa.amsl.com>; Thu, 29 Aug 2013 11:39:34 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id DA20A21F9F2B for <int-area@ietf.org>; Thu, 29 Aug 2013 11:39:33 -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 AWS36579; Thu, 29 Aug 2013 18:39:29 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 29 Aug 2013 19:39:12 +0100
Received: from DFWEML406-HUB.china.huawei.com (10.193.5.131) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 29 Aug 2013 19:39:27 +0100
Received: from DFWEML509-MBX.china.huawei.com ([169.254.11.52]) by dfweml406-hub.china.huawei.com ([10.193.5.131]) with mapi id 14.01.0323.007; Thu, 29 Aug 2013 11:39:20 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: David Allan I <david.i.allan@ericsson.com>, "int-area@ietf.org" <int-area@ietf.org>
Thread-Topic: Call for adoption of draft-nachum-sarp-06.txt
Thread-Index: Ac6k3Qh4liphP7t3SLCZUsNPa0sSWAABEZ9A
Date: Thu, 29 Aug 2013 18:39:19 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F645B86597@dfweml509-mbx.china.huawei.com>
References: <E6C17D2345AC7A45B7D054D407AA205C11608602@eusaamb105.ericsson.se>
In-Reply-To: <E6C17D2345AC7A45B7D054D407AA205C11608602@eusaamb105.ericsson.se>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.146.116]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F645B86597dfweml509mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [Int-area] Call for adoption of draft-nachum-sarp-06.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, 29 Aug 2013 18:39:40 -0000

--_000_4A95BA014132FF49AE685FAB4B9F17F645B86597dfweml509mbxchi_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

David,

Answers to your comments are inserted below:


From: int-area-bounces@ietf.org [mailto:int-area-bounces@ietf.org] On Behal=
f Of David Allan I
Sent: Thursday, August 29, 2013 12:53 PM
To: int-area@ietf.org
Subject: [Int-area] Call for adoption of draft-nachum-sarp-06.txt

Hi:

I have read this draft and will state I'm not a fan. My issues can be summa=
rized as follows:


1)  The first justification example in the motivation section is just plain=
 silly, yet I keep seeing it over and over in IETF discussions. No one woul=
d ever design and implement the deployment of any single application that w=
ay, let alone all apps attached to every TOR in a cloud.

[Linda] The motivation is showing that today's server virtualization and bu=
siness demand has made applications in one subnet no longer necessarily be =
placed closely together.  They are the same driver for NVo3. If you go to t=
his week's VMWorld, you will see more.
The motivation doesn't say anything along the line of "all apps attached to=
 every TOR in a cloud".


VM placement affinity rules would NEVER see absolutely every local VM belon=
ging to a different tenant network and requiring connectivity only to remot=
e VMs.

[Linda] "VM placement affinity rule" is set by operators. One operator can =
set the rule of not allowing different subnets to be placed under one rack,=
 by sacrificing the flexibility of placement.  Other operators may prefer t=
he flexibility by setting more lose rules.


Which says to me this is a solution to a non-problem unless the goal is to =
circumvent near-malicious stupidity in the design of the provisioning algor=
ithms used in the cloud management system.

[Linda] You can still implement the rule of requiring hosts of one subnet b=
eing placed together under one ToR.  Then there is no problem. But it doesn=
't mean that we don't need to evolve network to enable operators to utilize=
 the new technology for flexibility and elasticity.




2)  I believe the notion of an ARP proxy and use of MAC-NAT for scaling are=
 divisible concepts and each can be examined in isolation.

[Linda] Agree with your point here. The draft really has two portions: Prox=
y Gateway and caching the entries.


a.  If I want an ARP proxy system, Ethernet already defines the capability =
to map frames with a specific Ethertype to a distinct VLAN, so ARP transact=
ions (0x806) can be separated out of the datastream using existing standard=
ized technology and delivered to a remote proxy ARP system of any arbitrary=
 design, no further standardization required.
[Linda] There can be multiple VLANs hosts (applications) placed on the rack=
. Do you mean giving them different EtherTypes? So the traffic is mapped to=
 another VLAN? Does it mean each subnet will need two VLANs?
Besides, you can't dictate on what EtherType to use for applications being =
instantiated on servers. Can you elaborate more of this "ARP Transactions"?=
 If it works well, we can document it in the draft and replace the ARP prox=
y being currently described.



b.  An alternative to MAC NAT (a form of summarization in a flat dataplane)=
 is with MACinMAC (a form of summarization via hierarchical stacking).

[Linda] MACinMAC (IEEE802.1ah) doesn't summarize all remote hosts with comm=
on MAC. All switches and hosts attached to the boundary Edge and the Backbo=
ne Edge are exposed to all the remote hosts' MAC/VLAN addresses.


Which is already standardized and deployed and would have identical scaling=
 properties. NVO3 class of solutions while not yet standard, have similar p=
roperties.

c.  MAC NAT itself means the e2e path has a pseudo L3 hop in it, which effe=
ctively prevents all L2 protocols (e.g. CFM, DCB etc.) from being able to i=
nstrument connectivity e2e, so (for example) to diagnose what looks like an=
 L2 hop, I would need to use both ETH-LB and ICMP ping, even then with ques=
tionable ability to fault sectionalize after the MAC NAT function.

[Linda] CFM is among switches, not among end stations. The proxy Gateway is=
 to represent all remote end-stations (or hosts) by their Gateway addresses=
. Switch addresses are never an issue because there are only very limited n=
umber of switches in the network.
Can you elaborate this "pseudo L3 hop"?  ETH-LB and ICMP are also for switc=
h nodes too. They are not for end stations.




My 2 cents

Dave



----------------------------
Hi all,
  This draft has been presented at several intarea face to face meetings
and has received quite a bit of discussion. It has been difficult to
gauge whether the wg is interested in this work or not. This call is
being initiated to determine whether there is WG consensus towards
adoption of draft-nachum-sarp-06 as an intarea WG draft. Please state
whether or not you're in favor of the adoption by replying to this
email. If you are not in favor, please also state your objections in
your response. This adoption call will complete on 2013-09-04.

Regards
Suresh & Julien

--_000_4A95BA014132FF49AE685FAB4B9F17F645B86597dfweml509mbxchi_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:323894814;
	mso-list-type:hybrid;
	mso-list-template-ids:-1011980592 67698705 67698713 67698715 67698703 6769=
8713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">David, <o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Answers to your commen=
ts are inserted below:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> int-area=
-bounces@ietf.org [mailto:int-area-bounces@ietf.org]
<b>On Behalf Of </b>David Allan I<br>
<b>Sent:</b> Thursday, August 29, 2013 12:53 PM<br>
<b>To:</b> int-area@ietf.org<br>
<b>Subject:</b> [Int-area] Call for adoption of draft-nachum-sarp-06.txt<o:=
p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Hi:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">I have read this draft and will state I&#8217;m not a fan.=
 My issues can be summarized as follows:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:.7in;text-indent:-.25in;=
mso-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:&quot;Cour=
ier New&quot;"><span style=3D"mso-list:Ignore">1)<span style=3D"font:7.0pt =
&quot;Times New Roman&quot;">&nbsp;
</span></span></span><![endif]><span style=3D"font-size:10.0pt;font-family:=
&quot;Courier New&quot;">The first justification example in the motivation =
section is just plain silly, yet I keep seeing it over and over in IETF dis=
cussions. No one would ever design and implement
 the deployment of any single application that way, let alone all apps atta=
ched to every TOR in a cloud.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Linda] The motivation=
 is showing that today&#8217;s server virtualization and business demand ha=
s made applications in one subnet no longer necessarily be placed closely t=
ogether. &nbsp;They are the same driver for NVo3.
 If you go to this week&#8217;s VMWorld, you will see more. <o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">The motivation doesn&#=
8217;t say anything along the line of &#8220;all apps attached to every TOR=
 in a cloud&#8221;.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal" style=3D"margin-left:.7in"><span style=3D"font-size:=
10.0pt;font-family:&quot;Courier New&quot;">VM placement affinity rules wou=
ld NEVER see absolutely every local VM belonging to a different tenant netw=
ork and requiring connectivity only to remote VMs.
<span style=3D"color:#1F497D"><o:p></o:p></span></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Linda] &#8220;VM plac=
ement affinity rule&#8221; is set by operators. One operator can set the ru=
le of not allowing different subnets to be placed under one rack, by sacrif=
icing the flexibility of placement. &nbsp;Other operators
 may prefer the flexibility by setting more lose rules.<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal" style=3D"margin-left:.7in"><span style=3D"font-size:=
10.0pt;font-family:&quot;Courier New&quot;">Which says to me this is a solu=
tion to a non-problem unless the goal is to circumvent near-malicious stupi=
dity in the design of the provisioning algorithms
 used in the cloud management system.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Linda] You can still =
implement the rule of requiring hosts of one subnet being placed together u=
nder one ToR. &nbsp;Then there is no problem. But it doesn&#8217;t mean tha=
t we don&#8217;t need to evolve network to enable operators
 to utilize the new technology for flexibility and elasticity. <o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoListParagraph"><span style=3D"font-size:10.0pt;font-family:&=
quot;Courier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"font-size:10.0pt;font-family:&q=
uot;Courier New&quot;"><span style=3D"mso-list:Ignore">2)<span style=3D"fon=
t:7.0pt &quot;Times New Roman&quot;">&nbsp;
</span></span></span><![endif]><span style=3D"font-size:10.0pt;font-family:=
&quot;Courier New&quot;">I believe the notion of an ARP proxy and use of MA=
C-NAT for scaling are divisible concepts and each can be examined in isolat=
ion.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Linda] Agree with you=
r point here. The draft really has two portions: Proxy Gateway and caching =
the entries.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.0in;text-indent:-.25in=
;mso-list:l0 level2 lfo2">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:&quot;Cour=
ier New&quot;"><span style=3D"mso-list:Ignore">a.<span style=3D"font:7.0pt =
&quot;Times New Roman&quot;">&nbsp;
</span></span></span><![endif]><span style=3D"font-size:10.0pt;font-family:=
&quot;Courier New&quot;">If I want an ARP proxy system, Ethernet already de=
fines the capability to map frames with a specific Ethertype to a distinct =
VLAN, so ARP transactions (0x806) can be separated
 out of the datastream using existing standardized technology and delivered=
 to a remote proxy ARP system of any arbitrary design, no further standardi=
zation required.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Linda] There can be m=
ultiple VLANs hosts (applications) placed on the rack. Do you mean giving t=
hem different EtherTypes? So the traffic is mapped to another VLAN? Does it=
 mean each subnet will need two VLANs?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Besides, you can&#8217=
;t dictate on what EtherType to use for applications being instantiated on =
servers. Can you elaborate more of this &#8220;ARP Transactions&#8221;? If =
it works well, we can document it in the draft and replace
 the ARP proxy being currently described. <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.0in;text-indent:-.25in=
;mso-list:l0 level2 lfo2">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:&quot;Cour=
ier New&quot;"><span style=3D"mso-list:Ignore">b.<span style=3D"font:7.0pt =
&quot;Times New Roman&quot;">&nbsp;
</span></span></span><![endif]><span style=3D"font-size:10.0pt;font-family:=
&quot;Courier New&quot;">An alternative to MAC NAT (a form of summarization=
 in a flat dataplane) is with MACinMAC (a form of summarization via hierarc=
hical stacking).
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Linda] MACinMAC (IEEE=
802.1ah) doesn&#8217;t summarize all remote hosts with common MAC. All swit=
ches and hosts attached to the boundary Edge and the Backbone Edge are expo=
sed to all the remote hosts&#8217; MAC/VLAN addresses.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal" style=3D"margin-left:1.0in"><span style=3D"font-size=
:10.0pt;font-family:&quot;Courier New&quot;">Which is already standardized =
and deployed and would have identical scaling properties. NVO3 class of sol=
utions while not yet standard, have similar properties.<o:p></o:p></span></=
p>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.0in;text-indent:-.25in=
;mso-list:l0 level2 lfo2">
<![if !supportLists]><span style=3D"font-size:10.0pt;font-family:&quot;Cour=
ier New&quot;"><span style=3D"mso-list:Ignore">c.<span style=3D"font:7.0pt =
&quot;Times New Roman&quot;">&nbsp;
</span></span></span><![endif]><span style=3D"font-size:10.0pt;font-family:=
&quot;Courier New&quot;">MAC NAT itself means the e2e path has a pseudo L3 =
hop in it, which effectively prevents all L2 protocols (e.g. CFM, DCB etc.)=
 from being able to instrument connectivity
 e2e, so (for example) to diagnose what looks like an L2 hop, I would need =
to use both ETH-LB and ICMP ping, even then with questionable ability to fa=
ult sectionalize after the MAC NAT function.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Linda] CFM is among s=
witches, not among end stations. The proxy Gateway is to represent all remo=
te end-stations (or hosts) by their Gateway addresses. Switch addresses are=
 never an issue because there are only
 very limited number of switches in the network. <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Can you elaborate this=
 &#8220;pseudo L3 hop&#8221;? &nbsp;ETH-LB and ICMP are also for switch nod=
es too. They are not for end stations.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:0in"><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoListParagraph" style=3D"margin-left:0in"><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;">My 2 cents<o:p></o:p></sp=
an></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:0in"><span style=3D"font=
-size:10.0pt;font-family:&quot;Courier New&quot;">Dave<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">----------------------------<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Hi all,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp; This draft has been presented at several intarea fa=
ce to face meetings<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">and has received quite a bit of discussion. It has been di=
fficult to<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">gauge whether the wg is interested in this work or not. Th=
is call is<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">being initiated to determine whether there is WG consensus=
 towards<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">adoption of draft-nachum-sarp-06 as an intarea WG draft. P=
lease state<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">whether or not you're in favor of the adoption by replying=
 to this<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">email. If you are not in favor, please also state your obj=
ections in<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">your response. This adoption call will complete on 2013-09=
-04.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">Regards<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;">Suresh &amp; Julien</span><o:p></o:p=
></p>
</div>
</div>
</body>
</html>

--_000_4A95BA014132FF49AE685FAB4B9F17F645B86597dfweml509mbxchi_--

From david.i.allan@ericsson.com  Thu Aug 29 12:27:31 2013
Return-Path: <david.i.allan@ericsson.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 6226511E816E for <int-area@ietfa.amsl.com>; Thu, 29 Aug 2013 12:27:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599]
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 SGfhTAF2QgQu for <int-area@ietfa.amsl.com>; Thu, 29 Aug 2013 12:27:24 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id A765711E8156 for <int-area@ietf.org>; Thu, 29 Aug 2013 12:27:24 -0700 (PDT)
X-AuditID: c618062d-b7fda8e0000024c6-19-521fa099da32
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 78.81.09414.990AF125; Thu, 29 Aug 2013 21:27:21 +0200 (CEST)
Received: from EUSAAMB105.ericsson.se ([147.117.188.122]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.02.0328.009; Thu, 29 Aug 2013 15:27:15 -0400
From: David Allan I <david.i.allan@ericsson.com>
To: Linda Dunbar <linda.dunbar@huawei.com>, "int-area@ietf.org" <int-area@ietf.org>
Thread-Topic: Call for adoption of draft-nachum-sarp-06.txt
Thread-Index: Ac6k3Qh4liphP7t3SLCZUsNPa0sSWAABEZ9AAAGx72A=
Date: Thu, 29 Aug 2013 19:27:14 +0000
Message-ID: <E6C17D2345AC7A45B7D054D407AA205C1160873C@eusaamb105.ericsson.se>
References: <E6C17D2345AC7A45B7D054D407AA205C11608602@eusaamb105.ericsson.se> <4A95BA014132FF49AE685FAB4B9F17F645B86597@dfweml509-mbx.china.huawei.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F645B86597@dfweml509-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.134]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrELMWRmVeSWpSXmKPExsUyuXRPgu7MBfJBBo2PDS1uzLrJYnG3ZSKT A5NHy5G3rB5LlvxkCmCK4rJJSc3JLEst0rdL4Mpo+HWdseCQXcWqNRwNjJOMuhg5OSQETCQ6 Hv5ihLDFJC7cW8/WxcjFISRwlFHiyZkjjBDOckaJC2c/soFUsQkYSOz5/wWsQ0QgVOLx9H5m EFtYwEpibc9JNoi4tcT8p7NZIWwriU2bz4PVsAioSrTvXA1WwyvgK7Fo2k12iAUzGSW+7H3C BJLgFAiT2Pb8AJjNCHTS91NrwGxmAXGJW0/mM0GcKiCxZA/EUAkBUYmXj/+xQtjKEkue7GeB qNeTuDF1ChuErS2xbOFrZojFghInZz5hmcAoOgvJ2FlIWmYhaZmFpGUBI8sqRo7S4tSy3HQj g02MwHg4JsGmu4Nxz0vLQ4zSHCxK4ryr9M4ECgmkJ5akZqemFqQWxReV5qQWH2Jk4uCUamAs 42mJ/6unG62/+V/X8zkmYfyu54vFkmLuzTpeGjx16+F1Ij+XSLy+drSqlOvzoj8PW3ZM1bq+ QunFzUkl21/bT2bImGFmH2so/ietkl8yIi1GL0YgJOufbb/tXP4lraJ5SQIHvKXv6704d3tT ksCe17t3tSwLklvq2fvnfN16d6eZ56tfnetVYinOSDTUYi4qTgQAAlcnDVUCAAA=
Subject: Re: [Int-area] Call for adoption of draft-nachum-sarp-06.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, 29 Aug 2013 19:27:31 -0000

HI Linda:

My replies in line marked with [DA]. Reverting to plain text..

Dave's issue 1) The first justification example in the motivation section i=
s just plain silly, yet I keep seeing it over and over in IETF discussions.=
 No one would ever design and implement the deployment of any single applic=
ation that way, let alone all apps attached to every TOR in a cloud.=20

[Linda] The motivation is showing that today's server virtualization and bu=
siness demand has made applications in one subnet no longer necessarily be =
placed closely together. =A0They are the same driver for NVo3. If you go to=
 this week's VMWorld, you will see more.=20
The motivation doesn't say anything along the line of "all apps attached to=
 every TOR in a cloud".=20

[DA] IMO I might like the flexibility to put anything anywhere and not have=
 to think about it, but I am introducing latency and degrading scalability =
and consuming excessive system bandwidth when I do so, so I will likely thi=
nk about it anyway and collocate communicating VMs as much as possible. =20

[DA]And my summarization of the example could use a rephrasing, I assumed i=
f I had one TOR for which every VM instance was part of a unique non-overla=
pping subnet, I would have others....which is what I actually meant. Not an=
 app had an end point attached to every TOR... I hope this is clearer.

VM placement affinity rules would NEVER see absolutely every local VM belon=
ging to a different tenant network and requiring connectivity only to remot=
e VMs.=20

[Linda] "VM placement affinity rule" is set by operators. One operator can =
set the rule of not allowing different subnets to be placed under one rack,=
 by sacrificing the flexibility of placement. =A0Other operators may prefer=
 the flexibility by setting more lose rules.

[DA] I know which one I would contract with. I would co-locate VMs as much =
as possible within the limits of my failure risk constraints, and as an ope=
rator would mix very risk constrained VMs with those less constrained in co=
mmon equipment exactly to avoid the pathological case outlined in motivatio=
ns.

Which says to me this is a solution to a non-problem unless the goal is to =
circumvent near-malicious stupidity in the design of the provisioning algor=
ithms used in the cloud management system.

[Linda] You can still implement the rule of requiring hosts of one subnet b=
eing placed together under one ToR. =A0Then there is no problem. But it doe=
sn't mean that we don't need to evolve network to enable operators to utili=
ze the new technology for flexibility and elasticity.=20

[DA] If flexibility means latency and needing much bigger switches. go for =
it and let me know how it turns out ;-)

Dave's issue 2) I believe the notion of an ARP proxy and use of MAC-NAT for=
 scaling are divisible concepts and each can be examined in isolation.=20

[Linda] Agree with your point here. The draft really has two portions: Prox=
y Gateway and caching the entries.=20
[DA] Great.

a. If I want an ARP proxy system, Ethernet already defines the capability t=
o map frames with a specific Ethertype to a distinct VLAN, so ARP transacti=
ons (0x806) can be separated out of the datastream using existing standardi=
zed technology and delivered to a remote proxy ARP system of any arbitrary =
design, no further standardization required.
[Linda] There can be multiple VLANs hosts (applications) placed on the rack=
. Do you mean giving them different EtherTypes? So the traffic is mapped to=
 another VLAN? Does it mean each subnet will need two VLANs?

[DA] I was not planning on designing such a system off the top of my head, =
merely expose that such capability existed, but if I actually needed a prox=
y ARP system and implemented it this way, yes it would a distinct VID separ=
ate from the regular dataplane for connectivity to the ARP proxy from which=
 the ARP system could infer the specific tenant subnet.

[Linda] Besides, you can't dictate on what EtherType to use for application=
s being instantiated on servers.=20

[DA] I wasn't.. bog standard 0x806

Can you elaborate more of this "ARP Transactions"? If it works well, we can=
 document it in the draft and replace the ARP proxy being currently describ=
ed.

[DA]  ARP request/reply is what I meant. That's all.I'm not sure it replace=
s the proxy. And on first blush I don't think the way it works in the draft=
 can be easily  replaced, as the ARP needs to resolve to the egress MAC-NAT=
 function for the rest of it to work.=20
=20

b. An alternative to MAC NAT (a form of summarization in a flat dataplane) =
is with MACinMAC (a form of summarization via hierarchical stacking).=20

[Linda] MACinMAC (IEEE802.1ah) doesn't summarize all remote hosts with comm=
on MAC.=20

[DA] Excuse me.? It encapsulates frames from a remote BEB with a header tha=
t includes the BMAC of the remote BEB which is what appears in all core for=
warding tables.  If you want to call it something else fine, but it is func=
tionally equivalent.

All switches and hosts attached to the boundary Edge and the Backbone Edge =
are exposed to all the remote hosts' MAC/VLAN addresses. =20

[DA] Ahhh, you are worried about compressing the MAC state in the ingress T=
OR and replacing it with state in the egress in a new function requiring a =
technology change and a separate table. I'd concede you will get some benef=
it in theoretical scalability, but individual TOR chips these days can hand=
le north of 250000 MAC addresses in on chip tables, so again unless you are=
 focused on an extreme corner case which I do not subscribe to , I do not s=
ee an issue with current technology=20
=A0
Which is already standardized and deployed and would have identical scaling=
 properties. NVO3 class of solutions while not yet standard, have similar p=
roperties.
c. MAC NAT itself means the e2e path has a pseudo L3 hop in it, which effec=
tively prevents all L2 protocols (e.g. CFM, DCB etc.) from being able to in=
strument connectivity e2e, so (for example) to diagnose what looks like an =
L2 hop, I would need to use both ETH-LB and ICMP ping, even then with quest=
ionable ability to fault sectionalize after the MAC NAT function.

[Linda] CFM is among switches, not among end stations. The proxy Gateway is=
 to represent all remote end-stations (or hosts) by their Gateway addresses=
. Switch addresses are never an issue because there are only very limited n=
umber of switches in the network.=20
Can you elaborate this "pseudo L3 hop"? =A0ETH-LB and ICMP are also for swi=
tch nodes too. They are not for end stations.=20

[DA] What I mean by a pseudo hop is that the MAC-NAT function receives a fr=
ame, and needs to resolve the actual MAC address for the End station. As it=
 summarizes (many end stations are compressed to a single MAC address of th=
e NAT function) it is not a clean pass though for any L2 frames. There is a=
n L3 to MAC resolution step in the middle of the path.

[DA] I would consider a hypervisor vSwitch to be a valid MEP in any operati=
onal system and would expect testability to it, which is not  an L3 address=
ed end point.  I do not have this with the SARP proposed solution.

I hope this clarifies my issues!
cheers
Dave


----------------------------
Hi all,
=A0 This draft has been presented at several intarea face to face meetings
and has received quite a bit of discussion. It has been difficult to
gauge whether the wg is interested in this work or not. This call is
being initiated to determine whether there is WG consensus towards
adoption of draft-nachum-sarp-06 as an intarea WG draft. Please state
whether or not you're in favor of the adoption by replying to this
email. If you are not in favor, please also state your objections in
your response. This adoption call will complete on 2013-09-04.

Regards
Suresh & Julien

From linda.dunbar@huawei.com  Thu Aug 29 13:49:53 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 077AD11E8175 for <int-area@ietfa.amsl.com>; Thu, 29 Aug 2013 13:49:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.865
X-Spam-Level: 
X-Spam-Status: No, score=-5.865 tagged_above=-999 required=5 tests=[AWL=0.734,  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 1c9NsmrO1gW9 for <int-area@ietfa.amsl.com>; Thu, 29 Aug 2013 13:49:48 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 694E111E8134 for <int-area@ietf.org>; Thu, 29 Aug 2013 13:49:47 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AWS41949; Thu, 29 Aug 2013 20:49:33 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 29 Aug 2013 21:48:40 +0100
Received: from DFWEML407-HUB.china.huawei.com (10.193.5.132) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 29 Aug 2013 21:49:31 +0100
Received: from DFWEML509-MBX.china.huawei.com ([169.254.11.52]) by dfweml407-hub.china.huawei.com ([10.193.5.132]) with mapi id 14.01.0323.007; Thu, 29 Aug 2013 13:49:27 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: David Allan I <david.i.allan@ericsson.com>, "int-area@ietf.org" <int-area@ietf.org>
Thread-Topic: Call for adoption of draft-nachum-sarp-06.txt
Thread-Index: Ac6k3Qh4liphP7t3SLCZUsNPa0sSWAABEZ9AAAGx72AAA7zigA==
Date: Thu, 29 Aug 2013 20:49:26 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F645B86775@dfweml509-mbx.china.huawei.com>
References: <E6C17D2345AC7A45B7D054D407AA205C11608602@eusaamb105.ericsson.se> <4A95BA014132FF49AE685FAB4B9F17F645B86597@dfweml509-mbx.china.huawei.com> <E6C17D2345AC7A45B7D054D407AA205C1160873C@eusaamb105.ericsson.se>
In-Reply-To: <E6C17D2345AC7A45B7D054D407AA205C1160873C@eusaamb105.ericsson.se>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.146.116]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [Int-area] Call for adoption of draft-nachum-sarp-06.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, 29 Aug 2013 20:49:53 -0000

David,=20

One correction, I meant to say MACinMAC (same as TRILL or NVO3) only hides =
hosts addresses from the core nodes, but, all the overlay edge nodes are st=
ill exposed to all the hosts addresses on the VLANs that are enabled on the=
 edge.

We have seriously considered MACinMAC back then for Ethernet transport, but=
 found out that most networks have access traffic to most of nodes, i.e. mo=
st of the nodes become "MACinMAC" edge nodes. Basically there is no core no=
des to benefit from hiding individual addresses in access domains. =20

Same goes with Overlay Edge enabled on TOR or EOR, there is limited number =
of nodes between ToR to DC Gateway, to benefit from hosts addresses being h=
iden. Maybe only aggregation switches benefit from the overlay, the DC gate=
way routers have to be exposed to all addresses of hosts who communicate wi=
th external peers. Most of hosts in DC do communicate with external peers, =
maybe the volume is not as high as east/west traffic.=20

Linda


> -----Original Message-----
> [Linda] MACinMAC (IEEE802.1ah) doesn't summarize all remote hosts with
> common MAC.
>=20
> [DA] Excuse me.? It encapsulates frames from a remote BEB with a header
> that includes the BMAC of the remote BEB which is what appears in all
> core forwarding tables.  If you want to call it something else fine,
> but it is functionally equivalent.
>=20
> All switches and hosts attached to the boundary Edge and the Backbone
> Edge are exposed to all the remote hosts' MAC/VLAN addresses.
>=20
> [DA] Ahhh, you are worried about compressing the MAC state in the
> ingress TOR and replacing it with state in the egress in a new function
> requiring a technology change and a separate table. I'd concede you
> will get some benefit in theoretical scalability, but individual TOR
> chips these days can handle north of 250000 MAC addresses in on chip
> tables, so again unless you are focused on an extreme corner case which
> I do not subscribe to , I do not see an issue with current technology
>=20

Linda

From david.i.allan@ericsson.com  Thu Aug 29 13:58:09 2013
Return-Path: <david.i.allan@ericsson.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 4144721F9476 for <int-area@ietfa.amsl.com>; Thu, 29 Aug 2013 13:58:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
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 9amhx+wwftYi for <int-area@ietfa.amsl.com>; Thu, 29 Aug 2013 13:58:02 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 4BA0221F94FD for <int-area@ietf.org>; Thu, 29 Aug 2013 13:57:58 -0700 (PDT)
X-AuditID: c6180641-b7fe28e000000d82-64-521fb5d0d81a
Received: from EUSAAHC003.ericsson.se (Unknown_Domain [147.117.188.81]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 83.F3.03458.0D5BF125; Thu, 29 Aug 2013 22:57:53 +0200 (CEST)
Received: from EUSAAMB105.ericsson.se ([147.117.188.122]) by EUSAAHC003.ericsson.se ([147.117.188.81]) with mapi id 14.02.0328.009; Thu, 29 Aug 2013 16:57:52 -0400
From: David Allan I <david.i.allan@ericsson.com>
To: Linda Dunbar <linda.dunbar@huawei.com>, "int-area@ietf.org" <int-area@ietf.org>
Thread-Topic: Call for adoption of draft-nachum-sarp-06.txt
Thread-Index: Ac6k3Qh4liphP7t3SLCZUsNPa0sSWAABEZ9AAAGx72AAA7zigAAAlJEw
Date: Thu, 29 Aug 2013 20:57:51 +0000
Message-ID: <E6C17D2345AC7A45B7D054D407AA205C1160897B@eusaamb105.ericsson.se>
References: <E6C17D2345AC7A45B7D054D407AA205C11608602@eusaamb105.ericsson.se> <4A95BA014132FF49AE685FAB4B9F17F645B86597@dfweml509-mbx.china.huawei.com> <E6C17D2345AC7A45B7D054D407AA205C1160873C@eusaamb105.ericsson.se> <4A95BA014132FF49AE685FAB4B9F17F645B86775@dfweml509-mbx.china.huawei.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F645B86775@dfweml509-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.134]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrELMWRmVeSWpSXmKPExsUyuXRPoO7FrfJBBjd+8lrcmHWTxeJuy0Qm ByaPliNvWT2WLPnJFMAUxWWTkpqTWZZapG+XwJVx6Jl/QYd4xYVfC9kaGNcJdTFyckgImEgc eHWSGcIWk7hwbz1bFyMXh5DAUUaJaYtPs0A4yxklHu//zApSxSZgILHn/xdGEFtEIFTi8fR+ sG5hASuJtT0n2SDi1hLzn85mhbDdJN4ePcEEYrMIqErMXTURrJ5XwFei4XAfI8SClUwSt3Z2 gyU4BcIkjj98C7aAEeik76fWgDUzC4hL3HoynwniVAGJJXvOQ50tKvHy8T9WCFtZYsmT/SwQ 9ToSC3Z/YoOwtSWWLXwNtVhQ4uTMJywTGEVnIRk7C0nLLCQts5C0LGBkWcXIUVqcWpabbmS4 iREYD8ck2Bx3MC74ZHmIUZqDRUmcd4PemUAhgfTEktTs1NSC1KL4otKc1OJDjEwcnFINjO05 MUGMT0SFOrfnT7+Rnx8ZzNyT8VBWL831s/5RtS1remQeG7w9/rr0h6yY2PO1H/LPuRv6bb/f seZvoZH4lo+9+tY/KtyLcrPKG45NMJXZ5bloornIdEWtc9t4v9R13l3WE3Rp1hWtrKXqZzqK j/4s/1aYkVhz7NOJsFXeElvaOWfrFG/3UWIpzkg01GIuKk4EAF9LprZVAgAA
Subject: Re: [Int-area] Call for adoption of draft-nachum-sarp-06.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, 29 Aug 2013 20:58:09 -0000

HI Linda:

Replies marked [DA]

One correction, I meant to say MACinMAC (same as TRILL or NVO3) only hides =
hosts addresses from the core nodes, but, all the overlay edge nodes are st=
ill exposed to all the hosts addresses on the VLANs that are enabled on the=
 edge.

[DA] I eventually figured out what you were getting at :-)

We have seriously considered MACinMAC back then for Ethernet transport, but=
 found out that most networks have access traffic to most of nodes, i.e. mo=
st of the nodes become "MACinMAC" edge nodes. Basically there is no core no=
des to benefit from hiding individual addresses in access domains. =20

[DA] That does not mean that the overall set of customer MACs for a given n=
etwork is not divided amongst the set of BEBs. As we both agreed, every VLA=
N does not have end-stations on every BEB. So there is an element of divide=
 and conquer here. Which as I've indicated, with a tiny bit of discipline i=
n implementing VM affinity rules would become even more beneficial for scal=
ing.

Same goes with Overlay Edge enabled on TOR or EOR, there is limited number =
of nodes between ToR to DC Gateway, to benefit from hosts addresses being h=
iden. Maybe only aggregation switches benefit from the overlay, the DC gate=
way routers have to be exposed to all addresses of hosts who communicate wi=
th external peers.=20

[DA] We need to separate DC to DC and user to DC when discussing the gatewa=
ys. I do not know why gateways would see VM MACs in the DC to DC case (see =
draft-allan-l2vpn-spbm-evpn...), and those MACs would be unique vs the user=
 to DC case.

Most of hosts in DC do communicate with external peers, maybe the volume is=
 not as high as east/west traffic.=20

[DA] traffic wise I would agree external traffic is a fraction of east west=
....

Cheers
Dave


> -----Original Message-----
> [Linda] MACinMAC (IEEE802.1ah) doesn't summarize all remote hosts with=20
> common MAC.
>=20
> [DA] Excuse me.? It encapsulates frames from a remote BEB with a=20
> header that includes the BMAC of the remote BEB which is what appears=20
> in all core forwarding tables.  If you want to call it something else=20
> fine, but it is functionally equivalent.
>=20
> All switches and hosts attached to the boundary Edge and the Backbone=20
> Edge are exposed to all the remote hosts' MAC/VLAN addresses.
>=20
> [DA] Ahhh, you are worried about compressing the MAC state in the=20
> ingress TOR and replacing it with state in the egress in a new=20
> function requiring a technology change and a separate table. I'd=20
> concede you will get some benefit in theoretical scalability, but=20
> individual TOR chips these days can handle north of 250000 MAC=20
> addresses in on chip tables, so again unless you are focused on an=20
> extreme corner case which I do not subscribe to , I do not see an=20
> issue with current technology
>=20

Linda

From linda.dunbar@huawei.com  Fri Aug 30 13:25:17 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 5612321F9F0A for <int-area@ietfa.amsl.com>; Fri, 30 Aug 2013 13:25:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.938
X-Spam-Level: 
X-Spam-Status: No, score=-5.938 tagged_above=-999 required=5 tests=[AWL=0.661,  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 ySS0Uf5cWCpb for <int-area@ietfa.amsl.com>; Fri, 30 Aug 2013 13:25:11 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 07C3D21F9F13 for <int-area@ietf.org>; Fri, 30 Aug 2013 13:25:07 -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 AUX19473; Fri, 30 Aug 2013 20:25:04 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.146.0; Fri, 30 Aug 2013 21:25:00 +0100
Received: from DFWEML407-HUB.china.huawei.com (10.193.5.132) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.146.0; Fri, 30 Aug 2013 21:25:02 +0100
Received: from DFWEML509-MBB.china.huawei.com ([169.254.2.107]) by dfweml407-hub.china.huawei.com ([10.193.5.132]) with mapi id 14.03.0146.000; Fri, 30 Aug 2013 13:24:58 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: David Allan I <david.i.allan@ericsson.com>, "int-area@ietf.org" <int-area@ietf.org>
Thread-Topic: Call for adoption of draft-nachum-sarp-06.txt
Thread-Index: Ac6k3Qh4liphP7t3SLCZUsNPa0sSWAABEZ9AAAGx72AANU9SoA==
Date: Fri, 30 Aug 2013 20:24:57 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F645B911E9@dfweml509-mbb.china.huawei.com>
References: <E6C17D2345AC7A45B7D054D407AA205C11608602@eusaamb105.ericsson.se> <4A95BA014132FF49AE685FAB4B9F17F645B86597@dfweml509-mbx.china.huawei.com> <E6C17D2345AC7A45B7D054D407AA205C1160873C@eusaamb105.ericsson.se>
In-Reply-To: <E6C17D2345AC7A45B7D054D407AA205C1160873C@eusaamb105.ericsson.se>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.136.35]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [Int-area] Call for adoption of draft-nachum-sarp-06.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, 30 Aug 2013 20:25:17 -0000

> -----Original Message-----
> VM placement affinity rules would NEVER see absolutely every local VM
> belonging to a different tenant network and requiring connectivity only
> to remote VMs.

[Linda] Being in one VLAN (or subnet) doesn't mean that those hosts (or app=
lications) have higher traffic among themselves. For a typical Data Center,=
 you may have many instances of WebServer in one subnet (typical one VLAN),=
 many instances of AppServer in another subnet (VLAN), and many instances o=
f DBServer in yet another subnet. The Subnet is only for policy enforcement=
 and load balance purposes. The amount of traffic between "WebServer Instan=
ces" <-> "AppServer instances" <-> "DB server instances" is magnitude highe=
r than the heartbeat traffic among all instances of one function.=20
For some DC operators who want to optimize their traffic across racks, plac=
ing instances from different subnets in one rack can eliminate a lot of tra=
ffic traversing among racks.=20


Linda
