
From touch@isi.edu  Mon Jul  1 01:21:41 2013
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA03B21F99AA for <int-area@ietfa.amsl.com>; Mon,  1 Jul 2013 01:21:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UW6ngw7j0eYv for <int-area@ietfa.amsl.com>; Mon,  1 Jul 2013 01:20:46 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 3DB1821F926E for <int-area@ietf.org>; Mon,  1 Jul 2013 01:19:38 -0700 (PDT)
Received: from [10.10.224.128] (pc2.prince-kyoto2013-unet.ocn.ne.jp [118.22.20.194]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r618HXSr021699 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 1 Jul 2013 01:17:43 -0700 (PDT)
Message-ID: <51D13B22.2050801@isi.edu>
Date: Mon, 01 Jul 2013 01:17:38 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
References: <2CF4CB03E2AA464BA0982EC92A02CE2509F187DD@BY2PRD0512MB653.namprd05.prod.outlook.com> <4A95BA014132FF49AE685FAB4B9F17F645B3615C@dfweml509-mbx.china.huawei.com> <51A665B1.40507@isi.edu> <95067C434CE250468B77282634C96ED322BD8932@xmb-aln-x02.cisco.com> <51ACD5DF.7040800@isi.edu> <95067C434CE250468B77282634C96ED322BDF244@xmb-aln-x02.cisco.com> <51AD307D.1070007@isi.edu> <4A95BA014132FF49AE685FAB4B9F17F645B3D1CC@dfweml509-mbx.china.huawei.com>, <51C9C9FD.2080406@isi.edu>	<BE15D088-4145-4EEB-861F-9A19B5E5495E@cisco.com> <51C9DDC2.6090904@isi.edu> <2134F8430051B64F815C691A62D983180AA7CC@XCH-BLV-504.nw.nos.boeing.com> <51CA0DB8.6090401@isi.edu> <2134F8430051B64F815C691A62D983180AAB85@XCH-BLV-504.nw.nos.boeing.com> <51CA1771.6020304@isi.edu> <2134F8430051B64F815C691A62D983180AABF9@XCH-BLV-504.nw.nos.boeing.com> <51CA5B8A.4060008@isi.edu> <2134F8430051B64F815C691A62D983180AC895@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D983180AC895@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "Carlos Pignataro \(cpignata\)" <cpignata@cisco.com>, Internet Area <int-area@ietf.org>, Ronald Bonica <rbonica@juniper.net>
Subject: Re: [Int-area] New Version Notification	for draft-bonica-intarea-gre-mtu-00.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jul 2013 08:21:42 -0000

Hi, Fred,

On 6/26/2013 8:42 AM, Templin, Fred L wrote:
> Hi Joe,
>
>> -----Original Message-----
>> From: Joe Touch [mailto:touch@isi.edu]
>> Sent: Tuesday, June 25, 2013 8:10 PM
>> To: Templin, Fred L
>> Cc: Carlos Pignataro (cpignata); Ronald Bonica; Internet Area
>> Subject: Re: [Int-area] New Version Notification for draft-bonica-
>> intarea-gre-mtu-00.txt
>>
>> Hi, Fred,
>>
>> On 6/25/2013 3:32 PM, Templin, Fred L wrote:
>>> Hi Joe,
>>>
>>> The constraint you seem to be missing is that RFC2460 only requires
>>> IPv6 nodes to reassemble as much as 1500 bytes.
>>
>> Right; sorry for not noticing that further. Had IPv4 on the brain.
>
> OK, but IPv4 also has a limit of minMRU=576. So, we have:
>
>    IPv4 minMTU = 576 (*)
>    IPv4 minMRU = 576
>    IPv6 minMTU = 1280
>    IPv6 minMRU = 1500
>
> (*) Even though the specs say that IPv4 minMTU = 68, everyone
> seems to be saying that for practical purposes it is now 576.

There needs to be a difference between the minMTU and the minMRU; if 
not, then IP-in-IP tunnels will never succeed without a separate 
fragmentation and reassembly layer - and although SEAL provides that, we 
currently do not require anything like that for X-in-X encapsulation.

>> ...
>>> Granted, my algorithm is asking GRE egress tunnel endpoints to
>>> configure a reassembly buffer size of 1500 *plus* the tunnel
>>> encapsulation overhead, which is more than RFC2460 ensures.
>>
>> Agreed.
>
> Right. So, then the fragmentation threshold for GRE over IPv6
> needs to be (1500 - HLEN) instead of 1500.
>
>> ...
>>> Also think about it this way. Why should the tunnel work hard to
>>> pass a packet that is larger than 1500 bytes and also larger than
>>> the minimum link MTU within the tunneled path when the source could
>>> instead adjust the size of the packets it is sending downward?
>>
>> That's not a good argument. I agree that all that need be satisfied is
>> the largest reassembled IPv6 packet, but not that we should assume the
>> source can or will adjust downward - if that were the case, you could
>> ignore the overhead of GRE and just claim that the MTU is 1280.
>
> In my lab, my implementation sends a single packet for packet
> sizes no larger than (1280 - HLEN). For packets that are larger
> than (1280 - HLEN) but no larger than 1500, it fragments the
> packet into two pieces and sends both pieces to the tunnel far
> end which then needs to reassemble. But, reassembly will be
> delayed by the inter-packet delay plus the time it takes to
> run the reassembly routine, and the delay is measurable. So,
> we really only want to use frag/reass when we absolutely have to.

My view is that discovering the path MTU for the purposes of avoiding 
frag/reassembly is either necessary or an optimization (such as you 
mention above, to avoid delays and conserve resources). That's in 
keeping with the "work first, optimize later" approach of the Internet.

So frag/reassemble unless you CANNOT. Send too-big messages back to help 
the system optimize. But never deliberately drop anything you could have 
sent with frag/reassembly.

Joe

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

From touch@isi.edu  Mon Jul  1 01:34:27 2013
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 383AE21F85E6 for <int-area@ietfa.amsl.com>; Mon,  1 Jul 2013 01:34:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kJ9l7qKsEj-x for <int-area@ietfa.amsl.com>; Mon,  1 Jul 2013 01:34:01 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id E2D6321F91CE for <int-area@ietf.org>; Mon,  1 Jul 2013 01:28:47 -0700 (PDT)
Received: from [10.10.224.128] (pc2.prince-kyoto2013-unet.ocn.ne.jp [118.22.20.194]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r618R2R9023352 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 1 Jul 2013 01:27:12 -0700 (PDT)
Message-ID: <51D13D5B.2080001@isi.edu>
Date: Mon, 01 Jul 2013 01:27:07 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Linda Dunbar <linda.dunbar@huawei.com>
References: <2CF4CB03E2AA464BA0982EC92A02CE2509F187DD@BY2PRD0512MB653.namprd05.prod.outlook.com> <4A95BA014132FF49AE685FAB4B9F17F645B3615C@dfweml509-mbx.china.huawei.com> <51A665B1.40507@isi.edu> <95067C434CE250468B77282634C96ED322BD8932@xmb-aln-x02.cisco.com> <51ACD5DF.7040800@isi.edu> <95067C434CE250468B77282634C96ED322BDF244@xmb-aln-x02.cisco.com> <51AD307D.1070007@isi.edu> <4A95BA014132FF49AE685FAB4B9F17F645B3D1CC@dfweml509-mbx.china.huawei.com> <2CF4CB03E2AA464BA0982EC92A02CE2509F895CE@BY2PRD0512MB653.namprd05.prod.outlook.com> <4A95BA014132FF49AE685FAB4B9F17F645B4038F@dfweml509-mbx.china.huawei.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F645B4038F@dfweml509-mbx.china.huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Ronald Bonica <rbonica@juniper.net>, Internet Area <int-area@ietf.org>, "Carlos Pignataro \(cpignata\)" <cpignata@cisco.com>
Subject: Re: [Int-area] New Version Notification	for draft-bonica-intarea-gre-mtu-00.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jul 2013 08:34:41 -0000

On 6/26/2013 1:09 PM, Linda Dunbar wrote:
> Ron,
>
> Those applications ignore the ICMP messages and keep sending data
> frames as if there is no ICMP message received.
> We ran into this problem in testing Video distribution system. After
> the first few frames, the receivers can't receive anything. After
> lengthy debugging, we found out that an intermediate node drops packets
> when GRE encapsulated frames exceed the link MTU. We tested that ICMP
> message is sent back, but the source node didn't respond. We tried
> several setting as Joe pointed out. Some guest OSs change behavior, some
> don't.

Who to fix in this situation depends on how the ICMPs received are being 
handled.

Are they being sent to the transport layer?

Is the app tracking the errors?

It might or might not be the OS's fault.

Joe


> Linda
>
>> -----Original Message-----
>> From: Ronald Bonica [mailto:rbonica@juniper.net]
>> Sent: Wednesday, June 26, 2013 8:00 AM
>> To: Linda Dunbar; Joe Touch; Carlos Pignataro (cpignata)
>> Cc: Internet Area
>> Subject: RE: [Int-area] New Version Notification for draft-bonica-
>> intarea-gre-mtu-00.txt
>>
>> Linda,
>>
>> What do these platforms do when they receive an ICMP Packet too big
>> from a router that isn't a tunnel ingress?
>>
>>                                              Ron
>>
>>
>>> -----Original Message-----
>>> From: Linda Dunbar [mailto:linda.dunbar@huawei.com]
>>> Sent: Tuesday, June 25, 2013 10:05 AM
>>> To: Joe Touch; Carlos Pignataro (cpignata)
>>> Cc: Ronald Bonica; Internet Area
>>> Subject: RE: [Int-area] New Version Notification for draft-bonica-
>>> intarea-gre-mtu-00.txt
>>>
>>> Ron,
>>>
>>> Your draft recommends that the ingress node discards the frame and
>>> sends ICMP msg to the source node when the size of GRE encapsulated
>>> frame exceeds link MTU.
>>> We experienced that Window XP doesn't adjust frame size after
>> receiving
>>> ICMP message. Many Linux based applications don't do anything either
>>> with the MTU ICMP message. I think your draft should point those
>> issues
>>> out and recommend fragmentation approach under those circumstances.
>>>
>>> Linda
>>>
>>>
>>>
>>
>>
>

From Fred.L.Templin@boeing.com  Mon Jul  1 08:34:59 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 260A311E8181 for <int-area@ietfa.amsl.com>; Mon,  1 Jul 2013 08:34:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.468
X-Spam-Level: 
X-Spam-Status: No, score=-6.468 tagged_above=-999 required=5 tests=[AWL=0.131,  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 hefMxw2Jiubu for <int-area@ietfa.amsl.com>; Mon,  1 Jul 2013 08:34:52 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (slb-mbsout-02.boeing.com [130.76.64.129]) by ietfa.amsl.com (Postfix) with ESMTP id A8C6911E80F7 for <int-area@ietf.org>; Mon,  1 Jul 2013 08:34:52 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r61FYprC020358 for <int-area@ietf.org>; Mon, 1 Jul 2013 08:34:51 -0700
Received: from XCH-NWHT-02.nw.nos.boeing.com (xch-nwht-02.nw.nos.boeing.com [130.247.70.248]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r61FYnVh020351 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Mon, 1 Jul 2013 08:34:49 -0700
Received: from XCH-BLV-507.nw.nos.boeing.com (130.247.25.197) by XCH-NWHT-02.nw.nos.boeing.com (130.247.70.248) with Microsoft SMTP Server (TLS) id 8.3.297.1; Mon, 1 Jul 2013 08:34:49 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.48]) by XCH-BLV-507.nw.nos.boeing.com ([169.254.7.131]) with mapi id 14.02.0328.011; Mon, 1 Jul 2013 08:34:48 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Joe Touch <touch@isi.edu>
Thread-Topic: [Int-area] New Version Notification	for draft-bonica-intarea-gre-mtu-00.txt
Thread-Index: AQHOdjOl4b1RAvvaSUeqp+MHZfntPplP8ESg
Date: Mon, 1 Jul 2013 15:34:47 +0000
Message-ID: <2134F8430051B64F815C691A62D983180B1944@XCH-BLV-504.nw.nos.boeing.com>
References: <2CF4CB03E2AA464BA0982EC92A02CE2509F187DD@BY2PRD0512MB653.namprd05.prod.outlook.com> <4A95BA014132FF49AE685FAB4B9F17F645B3615C@dfweml509-mbx.china.huawei.com> <51A665B1.40507@isi.edu> <95067C434CE250468B77282634C96ED322BD8932@xmb-aln-x02.cisco.com> <51ACD5DF.7040800@isi.edu> <95067C434CE250468B77282634C96ED322BDF244@xmb-aln-x02.cisco.com> <51AD307D.1070007@isi.edu> <4A95BA014132FF49AE685FAB4B9F17F645B3D1CC@dfweml509-mbx.china.huawei.com>, <51C9C9FD.2080406@isi.edu>	<BE15D088-4145-4EEB-861F-9A19B5E5495E@cisco.com> <51C9DDC2.6090904@isi.edu> <2134F8430051B64F815C691A62D983180AA7CC@XCH-BLV-504.nw.nos.boeing.com> <51CA0DB8.6090401@isi.edu> <2134F8430051B64F815C691A62D983180AAB85@XCH-BLV-504.nw.nos.boeing.com> <51CA1771.6020304@isi.edu> <2134F8430051B64F815C691A62D983180AABF9@XCH-BLV-504.nw.nos.boeing.com> <51CA5B8A.4060008@isi.edu> <2134F8430051B64F815C691A62D983180AC895@XCH-BLV-504.nw.nos.boeing.com> <51D13B22.2050801@isi.edu>
In-Reply-To: <51D13B22.2050801@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "Carlos Pignataro \(cpignata\)" <cpignata@cisco.com>, Internet Area <int-area@ietf.org>, Ronald Bonica <rbonica@juniper.net>
Subject: Re: [Int-area] New Version Notification	for draft-bonica-intarea-gre-mtu-00.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jul 2013 15:34:59 -0000

Hi Joe,

> -----Original Message-----
> From: Joe Touch [mailto:touch@isi.edu]
> Sent: Monday, July 01, 2013 1:18 AM
> To: Templin, Fred L
> Cc: Carlos Pignataro (cpignata); Ronald Bonica; Internet Area
> Subject: Re: [Int-area] New Version Notification for draft-bonica-
> intarea-gre-mtu-00.txt
>=20
> Hi, Fred,
>=20
> On 6/26/2013 8:42 AM, Templin, Fred L wrote:
> > Hi Joe,
> >
> >> -----Original Message-----
> >> From: Joe Touch [mailto:touch@isi.edu]
> >> Sent: Tuesday, June 25, 2013 8:10 PM
> >> To: Templin, Fred L
> >> Cc: Carlos Pignataro (cpignata); Ronald Bonica; Internet Area
> >> Subject: Re: [Int-area] New Version Notification for draft-bonica-
> >> intarea-gre-mtu-00.txt
> >>
> >> Hi, Fred,
> >>
> >> On 6/25/2013 3:32 PM, Templin, Fred L wrote:
> >>> Hi Joe,
> >>>
> >>> The constraint you seem to be missing is that RFC2460 only requires
> >>> IPv6 nodes to reassemble as much as 1500 bytes.
> >>
> >> Right; sorry for not noticing that further. Had IPv4 on the brain.
> >
> > OK, but IPv4 also has a limit of minMRU=3D576. So, we have:
> >
> >    IPv4 minMTU =3D 576 (*)
> >    IPv4 minMRU =3D 576
> >    IPv6 minMTU =3D 1280
> >    IPv6 minMRU =3D 1500
> >
> > (*) Even though the specs say that IPv4 minMTU =3D 68, everyone
> > seems to be saying that for practical purposes it is now 576.
>=20
> There needs to be a difference between the minMTU and the minMRU; if
> not, then IP-in-IP tunnels will never succeed without a separate
> fragmentation and reassembly layer - and although SEAL provides that,
> we
> currently do not require anything like that for X-in-X encapsulation.

With IPv4, there is no difference between minMTU and minMRU.
Tunnels over IPv4 therefore set DF=3D0 to allow for in the
network fragmentation if necessary.

With IPv6, minMTU is smaller than minMRU but that does not
guarantee that a packet sent by the ingress can be received
by the egress without fragmentation. RFC2473 acknowledges
this by using fragmentation at the ingress as a limiting
condition for when the MTU within the tunnel becomes too
small. This can happen for example if there is a 1280 MTU
link within the tunnel, if there are nested encapsulations
within the tunnel, etc.
=20
> >> ...
> >>> Granted, my algorithm is asking GRE egress tunnel endpoints to
> >>> configure a reassembly buffer size of 1500 *plus* the tunnel
> >>> encapsulation overhead, which is more than RFC2460 ensures.
> >>
> >> Agreed.
> >
> > Right. So, then the fragmentation threshold for GRE over IPv6
> > needs to be (1500 - HLEN) instead of 1500.
> >
> >> ...
> >>> Also think about it this way. Why should the tunnel work hard to
> >>> pass a packet that is larger than 1500 bytes and also larger than
> >>> the minimum link MTU within the tunneled path when the source could
> >>> instead adjust the size of the packets it is sending downward?
> >>
> >> That's not a good argument. I agree that all that need be satisfied
> is
> >> the largest reassembled IPv6 packet, but not that we should assume
> the
> >> source can or will adjust downward - if that were the case, you
> could
> >> ignore the overhead of GRE and just claim that the MTU is 1280.
> >
> > In my lab, my implementation sends a single packet for packet
> > sizes no larger than (1280 - HLEN). For packets that are larger
> > than (1280 - HLEN) but no larger than 1500, it fragments the
> > packet into two pieces and sends both pieces to the tunnel far
> > end which then needs to reassemble. But, reassembly will be
> > delayed by the inter-packet delay plus the time it takes to
> > run the reassembly routine, and the delay is measurable. So,
> > we really only want to use frag/reass when we absolutely have to.
>=20
> My view is that discovering the path MTU for the purposes of avoiding
> frag/reassembly is either necessary or an optimization (such as you
> mention above, to avoid delays and conserve resources). That's in
> keeping with the "work first, optimize later" approach of the Internet.
>=20
> So frag/reassemble unless you CANNOT. Send too-big messages back to
> help
> the system optimize. But never deliberately drop anything you could
> have
> sent with frag/reassembly.

What the SEAL approach fosters is a natural transition to larger
packets where packets up to 1500 are accommodated using fragmentation
if necessary but larger packets are allowed through in one piece as
long as they fit the available MTU. Then, hosts can reasonably assume
that their 1500 packets will get through, but to send anything larger
than that they should use RFC4821. The hosts will notice that they
get better performance using larger packets, and we will be well on
our way to an 8KB Internet.

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

> Joe
>=20
> >
> > Thanks - Fred
> > fred.l.templin@boeing.com
> >
> >> Joe

From brian@innovationslab.net  Mon Jul  1 13:06:42 2013
Return-Path: <brian@innovationslab.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 45B1E11E823F for <int-area@ietfa.amsl.com>; Mon,  1 Jul 2013 13:06:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.999
X-Spam-Level: 
X-Spam-Status: No, score=-102.999 tagged_above=-999 required=5 tests=[AWL=-0.400, 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 CvbsT2LfupDt for <int-area@ietfa.amsl.com>; Mon,  1 Jul 2013 13:06:35 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 2A80711E822D for <int-area@ietf.org>; Mon,  1 Jul 2013 13:06:35 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 1D70888117 for <int-area@ietf.org>; Mon,  1 Jul 2013 13:06:35 -0700 (PDT)
Received: from 10252428.rudm1.ra.johnshopkins.edu (addr16212925014.ippl.jhmi.edu [162.129.250.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id D8523130003 for <int-area@ietf.org>; Mon,  1 Jul 2013 13:06:34 -0700 (PDT)
Message-ID: <51D1E14C.8050205@innovationslab.net>
Date: Mon, 01 Jul 2013 16:06:36 -0400
From: Brian Haberman <brian@innovationslab.net>
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: "int-area@ietf.org" <int-area@ietf.org>
References: <20130701193936.10181.90437.idtracker@ietfa.amsl.com>
In-Reply-To: <20130701193936.10181.90437.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20130701193936.10181.90437.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Int-area] Fwd: IETF Mentor Program
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: Mon, 01 Jul 2013 20:06:42 -0000

All,
      I know I talked to a few of you during IETF 86 about mentoring. 
Please consider volunteering.  You do not need to be a greybeard to help 
out...

Regards,
Brian


-------- Original Message --------
Subject: IETF Mentor Program
Date: Mon, 01 Jul 2013 12:39:36 -0700
From: IETF Chair <chair@ietf.org>
Reply-To: ietf@ietf.org
To: IETF Announcement List <ietf-announce@ietf.org>

Hi all,

     Based on discussions during IETF 86, we are trialing an IETF 
mentoring program.  During this trial period, we would like to pair 
newcomers (people who have attended 3 or fewer meetings or have 
registered as students) with existing IETF participants.  The goal is to 
provide a resource for the newcomer who can assist them with integrating 
into the IETF community.  Mentors and newcomers will be paired prior to 
IETF 87.

     What we need is for people to volunteer to be mentors. As a mentor, 
we would ask that you be willing to assist your mentoring participant 
before, during, and (hopefully) after IETF 87.  The actual level of 
interaction will be driven by an agreement between the mentor and the 
mentoring participant. Additionally, we would need a brief description 
of your areas of expertise, technical interests, and conversational 
languages.

     A description of the Mentor Program (including a FAQ describing
how to volunteer to be a mentor) is available:

http://www.ietf.org/resources/mentoring-program.html.

     Anyone interested in being a mentor should follow the sign-up
instructions contained in the above URL.  The more volunteers we have,
the stronger the program will be!

Regards,
IETF Chair



From touch@isi.edu  Mon Jul  1 13:07:38 2013
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 310FE11E8229 for <int-area@ietfa.amsl.com>; Mon,  1 Jul 2013 13:07:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d77peJE-CGdX for <int-area@ietfa.amsl.com>; Mon,  1 Jul 2013 13:07:26 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id EACA011E822D for <int-area@ietf.org>; Mon,  1 Jul 2013 13:07:25 -0700 (PDT)
Received: from [10.10.224.128] (pc2.prince-kyoto2013-unet.ocn.ne.jp [118.22.20.194]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id r61K5BwR004227 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 1 Jul 2013 13:05:22 -0700 (PDT)
Message-ID: <51D1E0F6.4050300@isi.edu>
Date: Mon, 01 Jul 2013 13:05:10 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
References: <2CF4CB03E2AA464BA0982EC92A02CE2509F187DD@BY2PRD0512MB653.namprd05.prod.outlook.com> <51A665B1.40507@isi.edu> <95067C434CE250468B77282634C96ED322BD8932@xmb-aln-x02.cisco.com> <51ACD5DF.7040800@isi.edu> <95067C434CE250468B77282634C96ED322BDF244@xmb-aln-x02.cisco.com> <51AD307D.1070007@isi.edu> <4A95BA014132FF49AE685FAB4B9F17F645B3D1CC@dfweml509-mbx.china.huawei.com>, <51C9C9FD.2080406@isi.edu>	<BE15D088-4145-4EEB-861F-9A19B5E5495E@cisco.com> <51C9DDC2.6090904@isi.edu> <2134F8430051B64F815C691A62D983180AA7CC@XCH-BLV-504.nw.nos.boeing.com> <51CA0DB8.6090401@isi.edu> <2134F8430051B64F815C691A62D983180AAB85@XCH-BLV-504.nw.nos.boeing.com> <51CA1771.6020304@isi.edu> <2134F8430051B64F815C691A62D983180AABF9@XCH-BLV-504.nw.nos.boeing.com> <51CA5B8A.4060008@isi.edu> <2134F8430051B64F815C691A62D983180AC895@XCH-BLV-504.nw.nos.boeing.com> <51D13B22.2050801@isi.edu> <2134F8430051B64F815C691A62D983180B1944@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D983180B1944@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "Carlos Pignataro \(cpignata\)" <cpignata@cisco.com>, Internet Area <int-area@ietf.org>, Ronald Bonica <rbonica@juniper.net>
Subject: Re: [Int-area] New Version Notification	for draft-bonica-intarea-gre-mtu-00.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jul 2013 20:07:38 -0000

Hi, Fred,

On 7/1/2013 8:34 AM, Templin, Fred L wrote:
>>> OK, but IPv4 also has a limit of minMRU=576. So, we have:
>>>
>>>     IPv4 minMTU = 576 (*)
>>>     IPv4 minMRU = 576
>>>     IPv6 minMTU = 1280
>>>     IPv6 minMRU = 1500
>>>
>>> (*) Even though the specs say that IPv4 minMTU = 68, everyone
>>> seems to be saying that for practical purposes it is now 576.
>>
>> There needs to be a difference between the minMTU and the minMRU; if
>> not, then IP-in-IP tunnels will never succeed without a separate
>> fragmentation and reassembly layer - and although SEAL provides that,
>> we
>> currently do not require anything like that for X-in-X encapsulation.
>
> With IPv4, there is no difference between minMTU and minMRU.
> Tunnels over IPv4 therefore set DF=0 to allow for in the
> network fragmentation if necessary.

But then that's useless. Let's say you already send just 576, and set 
DF=1, and that packet encounters an IPv4 tunnel. You add 20 bytes of 
header, resulting in 596.

At the tunnel ingress, you can't fragment the inner packet because DF=1 
- and why shouldn't it be set? You're using the minMTU.

At that ingress, you can't fragment the outer packet because you would 
need the egress to reassemble something that is 596 -- larger than the 
egress ever expected to reassembly (minMRU).

So you drop the packet and send an ICMP too-big back to the source, who 
drops it because they're already sending minMTU packets and doesn't 
think it should have to drop the MTU below that.

AFAICT, you now have broken the path completely.

> With IPv6, minMTU is smaller than minMRU but that does not
> guarantee that a packet sent by the ingress can be received
> by the egress without fragmentation.

No, but it does guarantee that the packet can traverse a tunnel and 
still make it to its destination.

The difference between minMTU and minMRU is the amount of accumulated 
headers you can accommodate by tunneling. At 1500-1280, that's 5 levels 
of nested IPv6 tunnels, or more than a few IPsec tunnel-mode tunnels if 
needed.

That's not as much as I'd like, but it's at least non-zero.

 > RFC2473 acknowledges
> this by using fragmentation at the ingress as a limiting
> condition for when the MTU within the tunnel becomes too
> small. This can happen for example if there is a 1280 MTU
> link within the tunnel, if there are nested encapsulations
> within the tunnel, etc.

Yes, but if minMRU == minMTU, then the number of encapsulations 
supported is zero.

Joe

From Fred.L.Templin@boeing.com  Mon Jul  1 13:28:29 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CC8F11E8254 for <int-area@ietfa.amsl.com>; Mon,  1 Jul 2013 13:28:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.481
X-Spam-Level: 
X-Spam-Status: No, score=-6.481 tagged_above=-999 required=5 tests=[AWL=0.118,  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 YrZUQcKBIZ3c for <int-area@ietfa.amsl.com>; Mon,  1 Jul 2013 13:28:22 -0700 (PDT)
Received: from blv-mbsout-02.boeing.com (blv-mbsout-02.boeing.com [130.76.32.232]) by ietfa.amsl.com (Postfix) with ESMTP id 8268A11E8248 for <int-area@ietf.org>; Mon,  1 Jul 2013 13:28:02 -0700 (PDT)
Received: from blv-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r61KS1q0000945 for <int-area@ietf.org>; Mon, 1 Jul 2013 13:28:01 -0700
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r61KRxOB000928 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Mon, 1 Jul 2013 13:27:59 -0700
Received: from XCH-BLV-104.nw.nos.boeing.com (130.247.25.120) by XCH-NWHT-11.nw.nos.boeing.com (130.247.25.114) with Microsoft SMTP Server (TLS) id 8.3.297.1; Mon, 1 Jul 2013 13:28:00 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.48]) by XCH-BLV-104.nw.nos.boeing.com ([169.254.4.39]) with mapi id 14.02.0328.011; Mon, 1 Jul 2013 13:28:00 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Joe Touch <touch@isi.edu>
Thread-Topic: [Int-area] New Version Notification	for draft-bonica-intarea-gre-mtu-00.txt
Thread-Index: AQHOdpZK4b1RAvvaSUeqp+MHZfntPplQQVyQ
Date: Mon, 1 Jul 2013 20:27:59 +0000
Message-ID: <2134F8430051B64F815C691A62D983180B1E08@XCH-BLV-504.nw.nos.boeing.com>
References: <2CF4CB03E2AA464BA0982EC92A02CE2509F187DD@BY2PRD0512MB653.namprd05.prod.outlook.com> <51A665B1.40507@isi.edu> <95067C434CE250468B77282634C96ED322BD8932@xmb-aln-x02.cisco.com> <51ACD5DF.7040800@isi.edu> <95067C434CE250468B77282634C96ED322BDF244@xmb-aln-x02.cisco.com> <51AD307D.1070007@isi.edu> <4A95BA014132FF49AE685FAB4B9F17F645B3D1CC@dfweml509-mbx.china.huawei.com>, <51C9C9FD.2080406@isi.edu>	<BE15D088-4145-4EEB-861F-9A19B5E5495E@cisco.com> <51C9DDC2.6090904@isi.edu> <2134F8430051B64F815C691A62D983180AA7CC@XCH-BLV-504.nw.nos.boeing.com> <51CA0DB8.6090401@isi.edu> <2134F8430051B64F815C691A62D983180AAB85@XCH-BLV-504.nw.nos.boeing.com> <51CA1771.6020304@isi.edu> <2134F8430051B64F815C691A62D983180AABF9@XCH-BLV-504.nw.nos.boeing.com> <51CA5B8A.4060008@isi.edu> <2134F8430051B64F815C691A62D983180AC895@XCH-BLV-504.nw.nos.boeing.com> <51D13B22.2050801@isi.edu> <2134F8430051B64F815C691A62D983180B1944@XCH-BLV-504.nw.nos.boeing.com> <51D1E0F6.4050300@isi.edu>
In-Reply-To: <51D1E0F6.4050300@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "Carlos Pignataro \(cpignata\)" <cpignata@cisco.com>, Internet Area <int-area@ietf.org>, Ronald Bonica <rbonica@juniper.net>
Subject: Re: [Int-area] New Version Notification	for draft-bonica-intarea-gre-mtu-00.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jul 2013 20:28:29 -0000

Hi Joe,

> -----Original Message-----
> From: Joe Touch [mailto:touch@isi.edu]
> Sent: Monday, July 01, 2013 1:05 PM
> To: Templin, Fred L
> Cc: Carlos Pignataro (cpignata); Ronald Bonica; Internet Area
> Subject: Re: [Int-area] New Version Notification for draft-bonica-
> intarea-gre-mtu-00.txt
>=20
> Hi, Fred,
>=20
> On 7/1/2013 8:34 AM, Templin, Fred L wrote:
> >>> OK, but IPv4 also has a limit of minMRU=3D576. So, we have:
> >>>
> >>>     IPv4 minMTU =3D 576 (*)
> >>>     IPv4 minMRU =3D 576
> >>>     IPv6 minMTU =3D 1280
> >>>     IPv6 minMRU =3D 1500
> >>>
> >>> (*) Even though the specs say that IPv4 minMTU =3D 68, everyone
> >>> seems to be saying that for practical purposes it is now 576.
> >>
> >> There needs to be a difference between the minMTU and the minMRU; if
> >> not, then IP-in-IP tunnels will never succeed without a separate
> >> fragmentation and reassembly layer - and although SEAL provides
> that,
> >> we
> >> currently do not require anything like that for X-in-X
> encapsulation.
> >
> > With IPv4, there is no difference between minMTU and minMRU.
> > Tunnels over IPv4 therefore set DF=3D0 to allow for in the
> > network fragmentation if necessary.
>=20
> But then that's useless. Let's say you already send just 576, and set
> DF=3D1, and that packet encounters an IPv4 tunnel. You add 20 bytes of
> header, resulting in 596.
>=20
> At the tunnel ingress, you can't fragment the inner packet because DF=3D1
> - and why shouldn't it be set? You're using the minMTU.
>=20
> At that ingress, you can't fragment the outer packet because you would
> need the egress to reassemble something that is 596 -- larger than the
> egress ever expected to reassembly (minMRU).
>=20
> So you drop the packet and send an ICMP too-big back to the source, who
> drops it because they're already sending minMTU packets and doesn't
> think it should have to drop the MTU below that.
>=20
> AFAICT, you now have broken the path completely.

For IPv6-within-IPv4 at least, most of these "transition mechanism"
tunnels assume a minMRU of 1500 even though the IPv4 specs say that
the MRU is 576. Sure, that is broken but it seems to have become the
IPv6 transition mechanism "best practice".

> > With IPv6, minMTU is smaller than minMRU but that does not
> > guarantee that a packet sent by the ingress can be received
> > by the egress without fragmentation.
>=20
> No, but it does guarantee that the packet can traverse a tunnel and
> still make it to its destination.

Right, but remember that the IPv6 minMRU is only 1500 bytes.
So, we can't assume an unlimited reassembly buffer on the
tunnel egress.

> The difference between minMTU and minMRU is the amount of accumulated
> headers you can accommodate by tunneling. At 1500-1280, that's 5 levels
> of nested IPv6 tunnels, or more than a few IPsec tunnel-mode tunnels if
> needed.

I addressed this point on the IPv6 list, but think for a moment
what this means. It means that the fist tunnel ingress would have
to configure a 1280 MTU, the second tunnel ingress would need to
configure a 1320 MTU (to accept encapsulated packets from the first),
the third tunnel ingress would need to configure a 1360 MTU (to
accept encapsulated packets from the second), etc. up to 5 levels
of nesting. I don't know about you, but I can imagine many situations
where it is not possible for a single operator to lay hands on every
tunnel ingress so as to carefully set each MTU in this way (I gave
one example on the IPv6 list).

> That's not as much as I'd like, but it's at least non-zero.

I think the maximum acceptable level of nesting is somewhere
between 5 and 10 before the nesting would be declared "recursive"
(i.e., a routing loop). SEAL allows up to 8 levels of nesting.

>  > RFC2473 acknowledges
> > this by using fragmentation at the ingress as a limiting
> > condition for when the MTU within the tunnel becomes too
> > small. This can happen for example if there is a 1280 MTU
> > link within the tunnel, if there are nested encapsulations
> > within the tunnel, etc.
>=20
> Yes, but if minMRU =3D=3D minMTU, then the number of encapsulations
> supported is zero.

Right. That's why IPv6-in-IPv4 transition mechanisms cheat and
assume 1500 when the specs say they can only assume 576.

Thanks - Fred
fred.l.templin@boeing.com
=20
> Joe

From touch@isi.edu  Mon Jul  1 13:52:26 2013
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4509911E825F for <int-area@ietfa.amsl.com>; Mon,  1 Jul 2013 13:52:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0WlkVI8oI7xw for <int-area@ietfa.amsl.com>; Mon,  1 Jul 2013 13:52:20 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 71FDB21F9C88 for <int-area@ietf.org>; Mon,  1 Jul 2013 13:52:20 -0700 (PDT)
Received: from [10.10.224.128] (pc2.prince-kyoto2013-unet.ocn.ne.jp [118.22.20.194]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r61Kov0e018387 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 1 Jul 2013 13:51:07 -0700 (PDT)
Message-ID: <51D1EBB1.6010002@isi.edu>
Date: Mon, 01 Jul 2013 13:50:57 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
References: <2CF4CB03E2AA464BA0982EC92A02CE2509F187DD@BY2PRD0512MB653.namprd05.prod.outlook.com> <51ACD5DF.7040800@isi.edu> <95067C434CE250468B77282634C96ED322BDF244@xmb-aln-x02.cisco.com> <51AD307D.1070007@isi.edu> <4A95BA014132FF49AE685FAB4B9F17F645B3D1CC@dfweml509-mbx.china.huawei.com>, <51C9C9FD.2080406@isi.edu>	<BE15D088-4145-4EEB-861F-9A19B5E5495E@cisco.com> <51C9DDC2.6090904@isi.edu> <2134F8430051B64F815C691A62D983180AA7CC@XCH-BLV-504.nw.nos.boeing.com> <51CA0DB8.6090401@isi.edu> <2134F8430051B64F815C691A62D983180AAB85@XCH-BLV-504.nw.nos.boeing.com> <51CA1771.6020304@isi.edu> <2134F8430051B64F815C691A62D983180AABF9@XCH-BLV-504.nw.nos.boeing.com> <51CA5B8A.4060008@isi.edu> <2134F8430051B64F815C691A62D983180AC895@XCH-BLV-504.nw.nos.boeing.com> <51D13B22.2050801@isi.edu> <2134F8430051B64F815C691A62D983180B1944@XCH-BLV-504.nw.nos.boeing.com> <51D1E0F6.4050300@isi.edu> <2134F8430051B64F815C691A62D983180B1E08@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D983180B1E08@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "Carlos Pignataro \(cpignata\)" <cpignata@cisco.com>, Internet Area <int-area@ietf.org>, Ronald Bonica <rbonica@juniper.net>
Subject: Re: [Int-area] New Version Notification	for draft-bonica-intarea-gre-mtu-00.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jul 2013 20:52:26 -0000

Hi, Fred,

On 7/1/2013 1:27 PM, Templin, Fred L wrote:
...
>> On 7/1/2013 8:34 AM, Templin, Fred L wrote:
>>>>> OK, but IPv4 also has a limit of minMRU=576. So, we have:
>>>>>
>>>>>      IPv4 minMTU = 576 (*)
>>>>>      IPv4 minMRU = 576
>>>>>      IPv6 minMTU = 1280
>>>>>      IPv6 minMRU = 1500
>>>>>
>>>>> (*) Even though the specs say that IPv4 minMTU = 68, everyone
>>>>> seems to be saying that for practical purposes it is now 576.
>>>>
>>>> There needs to be a difference between the minMTU and the minMRU; if
>>>> not, then IP-in-IP tunnels will never succeed without a separate
>>>> fragmentation and reassembly layer - and although SEAL provides
>> that,
>>>> we
>>>> currently do not require anything like that for X-in-X
>> encapsulation.
>>>
>>> With IPv4, there is no difference between minMTU and minMRU.
>>> Tunnels over IPv4 therefore set DF=0 to allow for in the
>>> network fragmentation if necessary.
>>
>> But then that's useless. Let's say you already send just 576, and set
>> DF=1, and that packet encounters an IPv4 tunnel. You add 20 bytes of
>> header, resulting in 596.
>>
>> At the tunnel ingress, you can't fragment the inner packet because DF=1
>> - and why shouldn't it be set? You're using the minMTU.
>>
>> At that ingress, you can't fragment the outer packet because you would
>> need the egress to reassemble something that is 596 -- larger than the
>> egress ever expected to reassembly (minMRU).
>>
>> So you drop the packet and send an ICMP too-big back to the source, who
>> drops it because they're already sending minMTU packets and doesn't
>> think it should have to drop the MTU below that.
>>
>> AFAICT, you now have broken the path completely.
>
> For IPv6-within-IPv4 at least, most of these "transition mechanism"
> tunnels assume a minMRU of 1500 even though the IPv4 specs say that
> the MRU is 576. Sure, that is broken but it seems to have become the
> IPv6 transition mechanism "best practice".

I was giving an example of IPv4-in-IPv4, to demonstrate that when minMTU 
== minMRU then tunnels are not possible.

>>> With IPv6, minMTU is smaller than minMRU but that does not
>>> guarantee that a packet sent by the ingress can be received
>>> by the egress without fragmentation.
>>
>> No, but it does guarantee that the packet can traverse a tunnel and
>> still make it to its destination.
>
> Right, but remember that the IPv6 minMRU is only 1500 bytes.
> So, we can't assume an unlimited reassembly buffer on the
> tunnel egress.

Agreed.

>> The difference between minMTU and minMRU is the amount of accumulated
>> headers you can accommodate by tunneling. At 1500-1280, that's 5 levels
>> of nested IPv6 tunnels, or more than a few IPsec tunnel-mode tunnels if
>> needed.
>
> I addressed this point on the IPv6 list, but think for a moment
> what this means. It means that the fist tunnel ingress would have
> to configure a 1280 MTU, the second tunnel ingress would need to
> configure a 1320 MTU (to accept encapsulated packets from the first),
> the third tunnel ingress would need to configure a 1360 MTU (to
> accept encapsulated packets from the second), etc. up to 5 levels
> of nesting. I don't know about you, but I can imagine many situations
> where it is not possible for a single operator to lay hands on every
> tunnel ingress so as to carefully set each MTU in this way (I gave
> one example on the IPv6 list).

We agree, but the punchline is that:

a) minMRU *MUST* be larger than minMTU, or else there cannot be tunnels

	how much larger depends on how much nesting you expect;
	IPv6 allows 5 levels if plain nesting and around 2 of IPsec.
	The former seems fine, but the latter is tight. I would not
	at all be surprised if future networking ended up experiencing
	more than 2 levels of IPsec tunnel.

b) we CANNOT deprecate fragmentation

	if we do, we are deprecating tunneling

>> That's not as much as I'd like, but it's at least non-zero.
>
> I think the maximum acceptable level of nesting is somewhere
> between 5 and 10 before the nesting would be declared "recursive"
> (i.e., a routing loop). SEAL allows up to 8 levels of nesting.

It's "recursive" when it's recursive, and there's strictly no way to 
determine that because an address can have different meanings at 
different layers. The only solution would be to have each layer insert a 
"thumbprint" and look for cycles in that, but that approach would 
consume the encapsulation budget more quickly.

Two levels of tunnel are required to allow revisitation, where a single 
machine can emulate multiple virtual routers (without requiring OS 
virtualization such as VMware). More levels are needed to support other 
kinds of abstraction; my own work used up to 4 levels for 
non-demonstration purposes (we demo'd 16).

>>   > RFC2473 acknowledges
>>> this by using fragmentation at the ingress as a limiting
>>> condition for when the MTU within the tunnel becomes too
>>> small. This can happen for example if there is a 1280 MTU
>>> link within the tunnel, if there are nested encapsulations
>>> within the tunnel, etc.
>>
>> Yes, but if minMRU == minMTU, then the number of encapsulations
>> supported is zero.
>
> Right. That's why IPv6-in-IPv4 transition mechanisms cheat and
> assume 1500 when the specs say they can only assume 576.

Agreed. That's why we need *realistic* numbers for that, not merely 
those that reflect what's implemented (e.g., for IPv4).

Joe

From Fred.L.Templin@boeing.com  Mon Jul  1 14:18:21 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4345E11E8297 for <int-area@ietfa.amsl.com>; Mon,  1 Jul 2013 14:18:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.489
X-Spam-Level: 
X-Spam-Status: No, score=-6.489 tagged_above=-999 required=5 tests=[AWL=0.110,  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 nECCFzE05kes for <int-area@ietfa.amsl.com>; Mon,  1 Jul 2013 14:18:07 -0700 (PDT)
Received: from blv-mbsout-02.boeing.com (blv-mbsout-02.boeing.com [130.76.32.232]) by ietfa.amsl.com (Postfix) with ESMTP id 79FAE11E828C for <int-area@ietf.org>; Mon,  1 Jul 2013 14:18:07 -0700 (PDT)
Received: from blv-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r61LI52k016470 for <int-area@ietf.org>; Mon, 1 Jul 2013 14:18:05 -0700
Received: from XCH-PHX-109.sw.nos.boeing.com (xch-phx-109.sw.nos.boeing.com [130.247.25.36]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r61LI4Y7016454 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Mon, 1 Jul 2013 14:18:04 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.48]) by XCH-PHX-109.sw.nos.boeing.com ([169.254.9.190]) with mapi id 14.02.0328.011; Mon, 1 Jul 2013 14:18:04 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Joe Touch <touch@isi.edu>
Thread-Topic: [Int-area] New Version Notification	for draft-bonica-intarea-gre-mtu-00.txt
Thread-Index: AQHOdpyv4b1RAvvaSUeqp+MHZfntPplQTayw
Date: Mon, 1 Jul 2013 21:18:04 +0000
Message-ID: <2134F8430051B64F815C691A62D983180B1EE3@XCH-BLV-504.nw.nos.boeing.com>
References: <2CF4CB03E2AA464BA0982EC92A02CE2509F187DD@BY2PRD0512MB653.namprd05.prod.outlook.com> <51ACD5DF.7040800@isi.edu> <95067C434CE250468B77282634C96ED322BDF244@xmb-aln-x02.cisco.com> <51AD307D.1070007@isi.edu> <4A95BA014132FF49AE685FAB4B9F17F645B3D1CC@dfweml509-mbx.china.huawei.com>, <51C9C9FD.2080406@isi.edu>	<BE15D088-4145-4EEB-861F-9A19B5E5495E@cisco.com> <51C9DDC2.6090904@isi.edu> <2134F8430051B64F815C691A62D983180AA7CC@XCH-BLV-504.nw.nos.boeing.com> <51CA0DB8.6090401@isi.edu> <2134F8430051B64F815C691A62D983180AAB85@XCH-BLV-504.nw.nos.boeing.com> <51CA1771.6020304@isi.edu> <2134F8430051B64F815C691A62D983180AABF9@XCH-BLV-504.nw.nos.boeing.com> <51CA5B8A.4060008@isi.edu> <2134F8430051B64F815C691A62D983180AC895@XCH-BLV-504.nw.nos.boeing.com> <51D13B22.2050801@isi.edu> <2134F8430051B64F815C691A62D983180B1944@XCH-BLV-504.nw.nos.boeing.com> <51D1E0F6.4050300@isi.edu> <2134F8430051B64F815C691A62D983180B1E08@XCH-BLV-504.nw.nos.boeing.com> <51D1EBB1.6010002@isi.edu>
In-Reply-To: <51D1EBB1.6010002@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "Carlos Pignataro \(cpignata\)" <cpignata@cisco.com>, Internet Area <int-area@ietf.org>, Ronald Bonica <rbonica@juniper.net>
Subject: Re: [Int-area] New Version Notification	for draft-bonica-intarea-gre-mtu-00.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jul 2013 21:18:21 -0000

Hi Joe,

> -----Original Message-----
> From: Joe Touch [mailto:touch@isi.edu]
> Sent: Monday, July 01, 2013 1:51 PM
> To: Templin, Fred L
> Cc: Carlos Pignataro (cpignata); Ronald Bonica; Internet Area
> Subject: Re: [Int-area] New Version Notification for draft-bonica-
> intarea-gre-mtu-00.txt
>=20
> Hi, Fred,
>=20
> On 7/1/2013 1:27 PM, Templin, Fred L wrote:
> ...
> >> On 7/1/2013 8:34 AM, Templin, Fred L wrote:
> >>>>> OK, but IPv4 also has a limit of minMRU=3D576. So, we have:
> >>>>>
> >>>>>      IPv4 minMTU =3D 576 (*)
> >>>>>      IPv4 minMRU =3D 576
> >>>>>      IPv6 minMTU =3D 1280
> >>>>>      IPv6 minMRU =3D 1500
> >>>>>
> >>>>> (*) Even though the specs say that IPv4 minMTU =3D 68, everyone
> >>>>> seems to be saying that for practical purposes it is now 576.
> >>>>
> >>>> There needs to be a difference between the minMTU and the minMRU;
> if
> >>>> not, then IP-in-IP tunnels will never succeed without a separate
> >>>> fragmentation and reassembly layer - and although SEAL provides
> >> that,
> >>>> we
> >>>> currently do not require anything like that for X-in-X
> >> encapsulation.
> >>>
> >>> With IPv4, there is no difference between minMTU and minMRU.
> >>> Tunnels over IPv4 therefore set DF=3D0 to allow for in the
> >>> network fragmentation if necessary.
> >>
> >> But then that's useless. Let's say you already send just 576, and
> set
> >> DF=3D1, and that packet encounters an IPv4 tunnel. You add 20 bytes of
> >> header, resulting in 596.
> >>
> >> At the tunnel ingress, you can't fragment the inner packet because
> DF=3D1
> >> - and why shouldn't it be set? You're using the minMTU.
> >>
> >> At that ingress, you can't fragment the outer packet because you
> would
> >> need the egress to reassemble something that is 596 -- larger than
> the
> >> egress ever expected to reassembly (minMRU).
> >>
> >> So you drop the packet and send an ICMP too-big back to the source,
> who
> >> drops it because they're already sending minMTU packets and doesn't
> >> think it should have to drop the MTU below that.
> >>
> >> AFAICT, you now have broken the path completely.
> >
> > For IPv6-within-IPv4 at least, most of these "transition mechanism"
> > tunnels assume a minMRU of 1500 even though the IPv4 specs say that
> > the MRU is 576. Sure, that is broken but it seems to have become the
> > IPv6 transition mechanism "best practice".
>=20
> I was giving an example of IPv4-in-IPv4, to demonstrate that when
> minMTU
> =3D=3D minMRU then tunnels are not possible.

I took a quick look, and it looks like RFC2003 skirted the issue
of minMTU/minMRU sizes altogether. At least the v6/v4 transition
mechs did a cursory study of packet sizes.

> >>> With IPv6, minMTU is smaller than minMRU but that does not
> >>> guarantee that a packet sent by the ingress can be received
> >>> by the egress without fragmentation.
> >>
> >> No, but it does guarantee that the packet can traverse a tunnel and
> >> still make it to its destination.
> >
> > Right, but remember that the IPv6 minMRU is only 1500 bytes.
> > So, we can't assume an unlimited reassembly buffer on the
> > tunnel egress.
>=20
> Agreed.

OK.

> >> The difference between minMTU and minMRU is the amount of
> accumulated
> >> headers you can accommodate by tunneling. At 1500-1280, that's 5
> levels
> >> of nested IPv6 tunnels, or more than a few IPsec tunnel-mode tunnels
> if
> >> needed.
> >
> > I addressed this point on the IPv6 list, but think for a moment
> > what this means. It means that the fist tunnel ingress would have
> > to configure a 1280 MTU, the second tunnel ingress would need to
> > configure a 1320 MTU (to accept encapsulated packets from the first),
> > the third tunnel ingress would need to configure a 1360 MTU (to
> > accept encapsulated packets from the second), etc. up to 5 levels
> > of nesting. I don't know about you, but I can imagine many situations
> > where it is not possible for a single operator to lay hands on every
> > tunnel ingress so as to carefully set each MTU in this way (I gave
> > one example on the IPv6 list).
>=20
> We agree, but the punchline is that:
>=20
> a) minMRU *MUST* be larger than minMTU, or else there cannot be tunnels

Yes - I am totally with you on this.

> 	how much larger depends on how much nesting you expect;

Not necessarily. If the first tunnel ingress set a small fragment
size (say, 1280) and fragments anything between (1280-1500) to
something smaller (say 750), then each subsequent ingress in the
path would not need to fragment further and we can get away with
a reassembly buffer size of just (1500+HLEN) at the ultimate tunnel
far end.
=20
> 	IPv6 allows 5 levels if plain nesting and around 2 of IPsec.
> 	The former seems fine, but the latter is tight. I would not
> 	at all be surprised if future networking ended up experiencing
> 	more than 2 levels of IPsec tunnel.

Right, but without fragmentation the way you *stack* those levels
of nesting needs to be carefully coordinated which may not always
be possible.

> b) we CANNOT deprecate fragmentation

100% with you that fragmentation is needed, but:

> 	if we do, we are deprecating tunneling

If we deprecate IP fragmentation but then at the same time replace
it with SEAL we will still have the functionality that we need.
=20
> >> That's not as much as I'd like, but it's at least non-zero.
> >
> > I think the maximum acceptable level of nesting is somewhere
> > between 5 and 10 before the nesting would be declared "recursive"
> > (i.e., a routing loop). SEAL allows up to 8 levels of nesting.
>=20
> It's "recursive" when it's recursive, and there's strictly no way to
> determine that because an address can have different meanings at
> different layers. The only solution would be to have each layer insert
> a
> "thumbprint" and look for cycles in that, but that approach would
> consume the encapsulation budget more quickly.

SEAL has a "level" field which is essentially a counter that counts
down from 7 to zero. When we reach level 0, assume recursion and quit.

> Two levels of tunnel are required to allow revisitation, where a single
> machine can emulate multiple virtual routers (without requiring OS
> virtualization such as VMware). More levels are needed to support other
> kinds of abstraction; my own work used up to 4 levels for
> non-demonstration purposes (we demo'd 16).

Sounds very reasonable. I think we want to avoid getting locked
into rigid notions of what tunnel nesting would be used for.

> >>   > RFC2473 acknowledges
> >>> this by using fragmentation at the ingress as a limiting
> >>> condition for when the MTU within the tunnel becomes too
> >>> small. This can happen for example if there is a 1280 MTU
> >>> link within the tunnel, if there are nested encapsulations
> >>> within the tunnel, etc.
> >>
> >> Yes, but if minMRU =3D=3D minMTU, then the number of encapsulations
> >> supported is zero.
> >
> > Right. That's why IPv6-in-IPv4 transition mechanisms cheat and
> > assume 1500 when the specs say they can only assume 576.
>=20
> Agreed. That's why we need *realistic* numbers for that, not merely
> those that reflect what's implemented (e.g., for IPv4).

Right, but what I am ultimately after is an unlimited tunnel
MTU (I think you were on board with this idea from earlier
discussion). The only difference is that I want fragmentation
and reassembly out to 1500 bytes only, and then let the bigger
packets go through unfragmented as long as they fit. "Take care
of the smalls, and let the bigs take care of themselves."

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

> Joe

From touch@isi.edu  Mon Jul  1 14:35:32 2013
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08EE811E829B for <int-area@ietfa.amsl.com>; Mon,  1 Jul 2013 14:35:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ezr7pT7PmAXO for <int-area@ietfa.amsl.com>; Mon,  1 Jul 2013 14:35:26 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 3A5D811E8298 for <int-area@ietf.org>; Mon,  1 Jul 2013 14:35:26 -0700 (PDT)
Received: from [10.10.224.128] (pc2.prince-kyoto2013-unet.ocn.ne.jp [118.22.20.194]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r61LYOYn026344 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 1 Jul 2013 14:34:51 -0700 (PDT)
Message-ID: <51D1F5DF.6000607@isi.edu>
Date: Mon, 01 Jul 2013 14:34:23 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
References: <2CF4CB03E2AA464BA0982EC92A02CE2509F187DD@BY2PRD0512MB653.namprd05.prod.outlook.com> <51AD307D.1070007@isi.edu> <4A95BA014132FF49AE685FAB4B9F17F645B3D1CC@dfweml509-mbx.china.huawei.com>, <51C9C9FD.2080406@isi.edu>	<BE15D088-4145-4EEB-861F-9A19B5E5495E@cisco.com> <51C9DDC2.6090904@isi.edu> <2134F8430051B64F815C691A62D983180AA7CC@XCH-BLV-504.nw.nos.boeing.com> <51CA0DB8.6090401@isi.edu> <2134F8430051B64F815C691A62D983180AAB85@XCH-BLV-504.nw.nos.boeing.com> <51CA1771.6020304@isi.edu> <2134F8430051B64F815C691A62D983180AABF9@XCH-BLV-504.nw.nos.boeing.com> <51CA5B8A.4060008@isi.edu> <2134F8430051B64F815C691A62D983180AC895@XCH-BLV-504.nw.nos.boeing.com> <51D13B22.2050801@isi.edu> <2134F8430051B64F815C691A62D983180B1944@XCH-BLV-504.nw.nos.boeing.com> <51D1E0F6.4050300@isi.edu> <2134F8430051B64F815C691A62D983180B1E08@XCH-BLV-504.nw.nos.boeing.com> <51D1EBB1.6010002@isi.edu> <2134F8430051B64F815C691A62D983180B1EE3@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D983180B1EE3@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "Carlos Pignataro \(cpignata\)" <cpignata@cisco.com>, Internet Area <int-area@ietf.org>, Ronald Bonica <rbonica@juniper.net>
Subject: Re: [Int-area] New Version Notification	for draft-bonica-intarea-gre-mtu-00.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jul 2013 21:35:32 -0000

Cutting to the chase...

On 7/1/2013 2:18 PM, Templin, Fred L wrote:
> If we deprecate IP fragmentation but then at the same time replace
> it with SEAL we will still have the functionality that we need.

That's replacing fragmentation with fragmentation. The only reason to 
want to get rid of fragmentation is to simplify endpoints and/or 
simplify forwarding that does DPI. SEAL won't help either of those.

Further, we *have* fragmentation now. Getting rid of it would be 
premature until SEAL is required and widely deployed.

>>>> > >>   > RFC2473 acknowledges
>>>>> > >>>this by using fragmentation at the ingress as a limiting
>>>>> > >>>condition for when the MTU within the tunnel becomes too
>>>>> > >>>small. This can happen for example if there is a 1280 MTU
>>>>> > >>>link within the tunnel, if there are nested encapsulations
>>>>> > >>>within the tunnel, etc.
>>>> > >>
>>>> > >>Yes, but if minMRU == minMTU, then the number of encapsulations
>>>> > >>supported is zero.
>>> > >
>>> > >Right. That's why IPv6-in-IPv4 transition mechanisms cheat and
>>> > >assume 1500 when the specs say they can only assume 576.
>> >
>> >Agreed. That's why we need*realistic*  numbers for that, not merely
>> >those that reflect what's implemented (e.g., for IPv4).
 >
> Right, but what I am ultimately after is an unlimited tunnel
> MTU (I think you were on board with this idea from earlier
> discussion). The only difference is that I want fragmentation
> and reassembly out to 1500 bytes only, and then let the bigger
> packets go through unfragmented as long as they fit. "Take care
> of the smalls, and let the bigs take care of themselves."

We don't disagree on IPv6. My claim is that for IPv4 it is *necessary* 
that endpoints support MTUs lower than 567 to allow IPv4 fragmentation 
to support IPv4-in-IPv4 tunnels, including IPsec.

There are two solutions, of course - deploying SEAL would be the other. 
But I would expect that fixing incorrect implementations of an existing 
standard would be a lot easier than getting new code deployed for 
something that isn't yet standard.

Joe

From Fred.L.Templin@boeing.com  Mon Jul  1 14:50:29 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6941321F9C8D for <int-area@ietfa.amsl.com>; Mon,  1 Jul 2013 14:50:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.496
X-Spam-Level: 
X-Spam-Status: No, score=-6.496 tagged_above=-999 required=5 tests=[AWL=0.103,  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 8iHNoRnQ3xLd for <int-area@ietfa.amsl.com>; Mon,  1 Jul 2013 14:50:22 -0700 (PDT)
Received: from blv-mbsout-01.boeing.com (blv-mbsout-01.boeing.com [130.76.32.231]) by ietfa.amsl.com (Postfix) with ESMTP id E3B8021F9C73 for <int-area@ietf.org>; Mon,  1 Jul 2013 14:50:12 -0700 (PDT)
Received: from blv-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r61Lorac023831 for <int-area@ietf.org>; Mon, 1 Jul 2013 14:50:53 -0700
Received: from XCH-NWHT-05.nw.nos.boeing.com (xch-nwht-05.nw.nos.boeing.com [130.247.25.109]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r61LoqAQ023828 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Mon, 1 Jul 2013 14:50:52 -0700
Received: from XCH-EXCO-104.nw.nos.boeing.com (130.247.204.53) by XCH-NWHT-05.nw.nos.boeing.com (130.247.25.109) with Microsoft SMTP Server (TLS) id 8.3.297.1; Mon, 1 Jul 2013 14:50:11 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.48]) by XCH-EXCO-104.nw.nos.boeing.com ([fe80::f999:17c9:231b:b8ac%15]) with mapi id 14.02.0328.011; Mon, 1 Jul 2013 16:50:10 -0500
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Joe Touch <touch@isi.edu>
Thread-Topic: [Int-area] New Version Notification	for draft-bonica-intarea-gre-mtu-00.txt
Thread-Index: AQHOdqLA4b1RAvvaSUeqp+MHZfntPplQWTvg
Date: Mon, 1 Jul 2013 21:50:07 +0000
Message-ID: <2134F8430051B64F815C691A62D983180B1F8A@XCH-BLV-504.nw.nos.boeing.com>
References: <2CF4CB03E2AA464BA0982EC92A02CE2509F187DD@BY2PRD0512MB653.namprd05.prod.outlook.com> <51AD307D.1070007@isi.edu> <4A95BA014132FF49AE685FAB4B9F17F645B3D1CC@dfweml509-mbx.china.huawei.com>, <51C9C9FD.2080406@isi.edu>	<BE15D088-4145-4EEB-861F-9A19B5E5495E@cisco.com> <51C9DDC2.6090904@isi.edu> <2134F8430051B64F815C691A62D983180AA7CC@XCH-BLV-504.nw.nos.boeing.com> <51CA0DB8.6090401@isi.edu> <2134F8430051B64F815C691A62D983180AAB85@XCH-BLV-504.nw.nos.boeing.com> <51CA1771.6020304@isi.edu> <2134F8430051B64F815C691A62D983180AABF9@XCH-BLV-504.nw.nos.boeing.com> <51CA5B8A.4060008@isi.edu> <2134F8430051B64F815C691A62D983180AC895@XCH-BLV-504.nw.nos.boeing.com> <51D13B22.2050801@isi.edu> <2134F8430051B64F815C691A62D983180B1944@XCH-BLV-504.nw.nos.boeing.com> <51D1E0F6.4050300@isi.edu> <2134F8430051B64F815C691A62D983180B1E08@XCH-BLV-504.nw.nos.boeing.com> <51D1EBB1.6010002@isi.edu> <2134F8430051B64F815C691A62D983180B1EE3@XCH-BLV-504.nw.nos.boeing.com> <51D1F5DF.6000607@isi.edu>
In-Reply-To: <51D1F5DF.6000607@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "Carlos Pignataro \(cpignata\)" <cpignata@cisco.com>, Internet Area <int-area@ietf.org>, Ronald Bonica <rbonica@juniper.net>
Subject: Re: [Int-area] New Version Notification	for draft-bonica-intarea-gre-mtu-00.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jul 2013 21:50:29 -0000

Hi Joe,

> -----Original Message-----
> From: Joe Touch [mailto:touch@isi.edu]
> Sent: Monday, July 01, 2013 2:34 PM
> To: Templin, Fred L
> Cc: Carlos Pignataro (cpignata); Ronald Bonica; Internet Area
> Subject: Re: [Int-area] New Version Notification for draft-bonica-
> intarea-gre-mtu-00.txt
>=20
> Cutting to the chase...
>=20
> On 7/1/2013 2:18 PM, Templin, Fred L wrote:
> > If we deprecate IP fragmentation but then at the same time replace
> > it with SEAL we will still have the functionality that we need.
>=20
> That's replacing fragmentation with fragmentation. The only reason to
> want to get rid of fragmentation is to simplify endpoints and/or
> simplify forwarding that does DPI. SEAL won't help either of those.

SEAL helps with the DPI because it makes sure that the ULP headers
appear in the first fragment - there is no possible way to construct
a "runt" first fragment with SEAL. SEAL also takes care of the
overlapping fragments attack vector. There is a growing laundry list
of other complaints about IP fragmentation (e.g., Identification field
length and ID setting strategy) that do not apply to SEAL.=20
=20
> Further, we *have* fragmentation now. Getting rid of it would be
> premature until SEAL is required and widely deployed.

SEAL is compatible with IP fragmentation, so we can transition
to SEAL without having to first decommission IP fragmentation.
So, maybe the document should advocate "SEAL transition" rather
than "IP fragmentation deprecation".=20

> >>>> > >>   > RFC2473 acknowledges
> >>>>> > >>>this by using fragmentation at the ingress as a limiting
> >>>>> > >>>condition for when the MTU within the tunnel becomes too
> >>>>> > >>>small. This can happen for example if there is a 1280 MTU
> >>>>> > >>>link within the tunnel, if there are nested encapsulations
> >>>>> > >>>within the tunnel, etc.
> >>>> > >>
> >>>> > >>Yes, but if minMRU =3D=3D minMTU, then the number of
> encapsulations
> >>>> > >>supported is zero.
> >>> > >
> >>> > >Right. That's why IPv6-in-IPv4 transition mechanisms cheat and
> >>> > >assume 1500 when the specs say they can only assume 576.
> >> >
> >> >Agreed. That's why we need*realistic*  numbers for that, not merely
> >> >those that reflect what's implemented (e.g., for IPv4).
>  >
> > Right, but what I am ultimately after is an unlimited tunnel
> > MTU (I think you were on board with this idea from earlier
> > discussion). The only difference is that I want fragmentation
> > and reassembly out to 1500 bytes only, and then let the bigger
> > packets go through unfragmented as long as they fit. "Take care
> > of the smalls, and let the bigs take care of themselves."
>=20
> We don't disagree on IPv6. My claim is that for IPv4 it is *necessary*
> that endpoints support MTUs lower than 567 to allow IPv4 fragmentation
> to support IPv4-in-IPv4 tunnels, including IPsec.

I think there is way too much deployed base out there now
that boldly assumes 1500 that it would be impossible to put
them back in the bottle now.

> There are two solutions, of course - deploying SEAL would be the other.
> But I would expect that fixing incorrect implementations of an existing
> standard would be a lot easier than getting new code deployed for
> something that isn't yet standard.

There are too many compelling reasons to migrate away from IP
fragmentation and move toward SEAL. Maybe also look at some of
the discussion on the IPv6 list so we can avoid duplication.

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

> Joe

From touch@isi.edu  Mon Jul  1 15:22:18 2013
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D59711E82CF for <int-area@ietfa.amsl.com>; Mon,  1 Jul 2013 15:22:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iwjTeQ0FPvGR for <int-area@ietfa.amsl.com>; Mon,  1 Jul 2013 15:22:12 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 36B8511E82B6 for <int-area@ietf.org>; Mon,  1 Jul 2013 15:21:59 -0700 (PDT)
Received: from [10.10.224.128] (pc2.prince-kyoto2013-unet.ocn.ne.jp [118.22.20.194]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r61ML8cE004066 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 1 Jul 2013 15:21:18 -0700 (PDT)
Message-ID: <51D200D4.7030101@isi.edu>
Date: Mon, 01 Jul 2013 15:21:08 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
References: <2CF4CB03E2AA464BA0982EC92A02CE2509F187DD@BY2PRD0512MB653.namprd05.prod.outlook.com> <51C9C9FD.2080406@isi.edu>	<BE15D088-4145-4EEB-861F-9A19B5E5495E@cisco.com> <51C9DDC2.6090904@isi.edu> <2134F8430051B64F815C691A62D983180AA7CC@XCH-BLV-504.nw.nos.boeing.com> <51CA0DB8.6090401@isi.edu> <2134F8430051B64F815C691A62D983180AAB85@XCH-BLV-504.nw.nos.boeing.com> <51CA1771.6020304@isi.edu> <2134F8430051B64F815C691A62D983180AABF9@XCH-BLV-504.nw.nos.boeing.com> <51CA5B8A.4060008@isi.edu> <2134F8430051B64F815C691A62D983180AC895@XCH-BLV-504.nw.nos.boeing.com> <51D13B22.2050801@isi.edu> <2134F8430051B64F815C691A62D983180B1944@XCH-BLV-504.nw.nos.boeing.com> <51D1E0F6.4050300@isi.edu> <2134F8430051B64F815C691A62D983180B1E08@XCH-BLV-504.nw.nos.boeing.com> <51D1EBB1.6010002@isi.edu> <2134F8430051B64F815C691A62D983180B1EE3@XCH-BLV-504.nw.nos.boeing.com> <51D1F5DF.6000607@isi.edu> <2134F8430051B64F815C691A62D983180B1F8A@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D983180B1F8A@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "Carlos Pignataro \(cpignata\)" <cpignata@cisco.com>, Internet Area <int-area@ietf.org>, Ronald Bonica <rbonica@juniper.net>
Subject: Re: [Int-area] New Version Notification	for draft-bonica-intarea-gre-mtu-00.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jul 2013 22:22:18 -0000

On 7/1/2013 2:50 PM, Templin, Fred L wrote:
> Hi Joe,
>
>> -----Original Message-----
>> From: Joe Touch [mailto:touch@isi.edu]
>> Sent: Monday, July 01, 2013 2:34 PM
>> To: Templin, Fred L
>> Cc: Carlos Pignataro (cpignata); Ronald Bonica; Internet Area
>> Subject: Re: [Int-area] New Version Notification for draft-bonica-
>> intarea-gre-mtu-00.txt
>>
>> Cutting to the chase...
>>
>> On 7/1/2013 2:18 PM, Templin, Fred L wrote:
>>> If we deprecate IP fragmentation but then at the same time replace
>>> it with SEAL we will still have the functionality that we need.
>>
>> That's replacing fragmentation with fragmentation. The only reason to
>> want to get rid of fragmentation is to simplify endpoints and/or
>> simplify forwarding that does DPI. SEAL won't help either of those.
>
> SEAL helps with the DPI because it makes sure that the ULP headers
> appear in the first fragment

You can't know that unless you parse the IPv6 header chain. And adding 
SEAL inbetween IPv6 and the inner IPv6 adds one more step to that chain.

Either way, DPI has to follow the chain step-by-step, vs. in a single 
leap as with IPv4.

> - there is no possible way to construct
> a "runt" first fragment with SEAL. SEAL also takes care of the
> overlapping fragments attack vector. There is a growing laundry list
> of other complaints about IP fragmentation (e.g., Identification field
> length and ID setting strategy) that do not apply to SEAL.

Yes, but support for (vs not interfering with) DPI isn't one of them.

>> Further, we *have* fragmentation now. Getting rid of it would be
>> premature until SEAL is required and widely deployed.
>
> SEAL is compatible with IP fragmentation, so we can transition
> to SEAL without having to first decommission IP fragmentation.
> So, maybe the document should advocate "SEAL transition" rather
> than "IP fragmentation deprecation".

You can talk to Ron about that. But AFAICT that won't solve the overall 
problems his draft is seeking to address (whether they can or should be 
addressed is debatable, IMO).

...
>>>>>>> Right. That's why IPv6-in-IPv4 transition mechanisms cheat and
>>>>>>> assume 1500 when the specs say they can only assume 576.
>>>>>
...
>>
>> We don't disagree on IPv6. My claim is that for IPv4 it is *necessary*
>> that endpoints support MTUs lower than 567 to allow IPv4 fragmentation
>> to support IPv4-in-IPv4 tunnels, including IPsec.
>
> I think there is way too much deployed base out there now
> that boldly assumes 1500 that it would be impossible to put
> them back in the bottle now.

Then your table should have said IPv4 has a minMRU of 1500, but it 
doesn't. That's widely deployed, but cannot be assumed. Esp. on 
low-powered/low-mem devices.

>> There are two solutions, of course - deploying SEAL would be the other.
>> But I would expect that fixing incorrect implementations of an existing
>> standard would be a lot easier than getting new code deployed for
>> something that isn't yet standard.
>
> There are too many compelling reasons to migrate away from IP
> fragmentation and move toward SEAL. Maybe also look at some of
> the discussion on the IPv6 list so we can avoid duplication.

I agree that SEAL is better than IP at fragmentation, but it's still a 
network fragmentation layer when used for IP tunnels. It doesn't solve 
the issues that some are concerned about recently.

Joe

From Fred.L.Templin@boeing.com  Mon Jul  1 15:51:41 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C991711E82E1 for <int-area@ietfa.amsl.com>; Mon,  1 Jul 2013 15:51:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.503
X-Spam-Level: 
X-Spam-Status: No, score=-6.503 tagged_above=-999 required=5 tests=[AWL=0.096,  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 5Xcm+CBzSBle for <int-area@ietfa.amsl.com>; Mon,  1 Jul 2013 15:51:35 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (slb-mbsout-02.boeing.com [130.76.64.129]) by ietfa.amsl.com (Postfix) with ESMTP id 566BD11E82EF for <int-area@ietf.org>; Mon,  1 Jul 2013 15:51:31 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r61MpVYM003690 for <int-area@ietf.org>; Mon, 1 Jul 2013 15:51:31 -0700
Received: from XCH-NWHT-04.nw.nos.boeing.com (xch-nwht-04.nw.nos.boeing.com [130.247.64.250]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r61MpUms003673 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Mon, 1 Jul 2013 15:51:31 -0700
Received: from XCH-BLV-301.nw.nos.boeing.com (130.247.25.213) by XCH-NWHT-04.nw.nos.boeing.com (130.247.64.250) with Microsoft SMTP Server (TLS) id 8.3.297.1; Mon, 1 Jul 2013 15:51:30 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.48]) by XCH-BLV-301.nw.nos.boeing.com ([169.254.1.3]) with mapi id 14.02.0328.011; Mon, 1 Jul 2013 15:51:29 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Joe Touch <touch@isi.edu>
Thread-Topic: [Int-area] New Version Notification	for draft-bonica-intarea-gre-mtu-00.txt
Thread-Index: AQHOdqlI4b1RAvvaSUeqp+MHZfntPplQagbA
Date: Mon, 1 Jul 2013 22:51:28 +0000
Message-ID: <2134F8430051B64F815C691A62D983180B2019@XCH-BLV-504.nw.nos.boeing.com>
References: <2CF4CB03E2AA464BA0982EC92A02CE2509F187DD@BY2PRD0512MB653.namprd05.prod.outlook.com> <51C9C9FD.2080406@isi.edu>	<BE15D088-4145-4EEB-861F-9A19B5E5495E@cisco.com> <51C9DDC2.6090904@isi.edu> <2134F8430051B64F815C691A62D983180AA7CC@XCH-BLV-504.nw.nos.boeing.com> <51CA0DB8.6090401@isi.edu> <2134F8430051B64F815C691A62D983180AAB85@XCH-BLV-504.nw.nos.boeing.com> <51CA1771.6020304@isi.edu> <2134F8430051B64F815C691A62D983180AABF9@XCH-BLV-504.nw.nos.boeing.com> <51CA5B8A.4060008@isi.edu> <2134F8430051B64F815C691A62D983180AC895@XCH-BLV-504.nw.nos.boeing.com> <51D13B22.2050801@isi.edu> <2134F8430051B64F815C691A62D983180B1944@XCH-BLV-504.nw.nos.boeing.com> <51D1E0F6.4050300@isi.edu> <2134F8430051B64F815C691A62D983180B1E08@XCH-BLV-504.nw.nos.boeing.com> <51D1EBB1.6010002@isi.edu> <2134F8430051B64F815C691A62D983180B1EE3@XCH-BLV-504.nw.nos.boeing.com> <51D1F5DF.6000607@isi.edu> <2134F8430051B64F815C691A62D983180B1F8A@XCH-BLV-504.nw.nos.boeing.com> <51D200D4.7030101@isi.edu>
In-Reply-To: <51D200D4.7030101@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "Carlos Pignataro \(cpignata\)" <cpignata@cisco.com>, Internet Area <int-area@ietf.org>, Ronald Bonica <rbonica@juniper.net>
Subject: Re: [Int-area] New Version Notification	for draft-bonica-intarea-gre-mtu-00.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jul 2013 22:51:41 -0000

Hi Joe,

> -----Original Message-----
> From: Joe Touch [mailto:touch@isi.edu]
> Sent: Monday, July 01, 2013 3:21 PM
> To: Templin, Fred L
> Cc: Carlos Pignataro (cpignata); Ronald Bonica; Internet Area
> Subject: Re: [Int-area] New Version Notification for draft-bonica-
> intarea-gre-mtu-00.txt
>=20
>=20
>=20
> On 7/1/2013 2:50 PM, Templin, Fred L wrote:
> > Hi Joe,
> >
> >> -----Original Message-----
> >> From: Joe Touch [mailto:touch@isi.edu]
> >> Sent: Monday, July 01, 2013 2:34 PM
> >> To: Templin, Fred L
> >> Cc: Carlos Pignataro (cpignata); Ronald Bonica; Internet Area
> >> Subject: Re: [Int-area] New Version Notification for draft-bonica-
> >> intarea-gre-mtu-00.txt
> >>
> >> Cutting to the chase...
> >>
> >> On 7/1/2013 2:18 PM, Templin, Fred L wrote:
> >>> If we deprecate IP fragmentation but then at the same time replace
> >>> it with SEAL we will still have the functionality that we need.
> >>
> >> That's replacing fragmentation with fragmentation. The only reason
> to
> >> want to get rid of fragmentation is to simplify endpoints and/or
> >> simplify forwarding that does DPI. SEAL won't help either of those.
> >
> > SEAL helps with the DPI because it makes sure that the ULP headers
> > appear in the first fragment
>=20
> You can't know that unless you parse the IPv6 header chain. And adding
> SEAL inbetween IPv6 and the inner IPv6 adds one more step to that
> chain.

The SEAL first fragment MUST contain at least 256 bytes (or up to
the end of the packet) according to the specs. If that is not large
enough to include sufficient ULP headers then the packet should
probably be dropped anyway. =20

> Either way, DPI has to follow the chain step-by-step, vs. in a single
> leap as with IPv4.

Right, but how long can those chains be and still be considered
a "realistic" IPv6 packet?

> > - there is no possible way to construct
> > a "runt" first fragment with SEAL. SEAL also takes care of the
> > overlapping fragments attack vector. There is a growing laundry list
> > of other complaints about IP fragmentation (e.g., Identification
> field
> > length and ID setting strategy) that do not apply to SEAL.
>=20
> Yes, but support for (vs not interfering with) DPI isn't one of them.

This comes to whether it is possible to set a maximum upper
bound on the length of a chain of IPv6 extension headers. And,
if 256 is too small SEAL the spec can still be changed to push
it to 512.

Maybe what is needed is a specification of the maximum IPv6
header length the same as we have a specification for the
maximum IPv4 header length? I would propose 256 bytes, but
I could live with something somewhat larger like 512.

> >> Further, we *have* fragmentation now. Getting rid of it would be
> >> premature until SEAL is required and widely deployed.
> >
> > SEAL is compatible with IP fragmentation, so we can transition
> > to SEAL without having to first decommission IP fragmentation.
> > So, maybe the document should advocate "SEAL transition" rather
> > than "IP fragmentation deprecation".
>=20
> You can talk to Ron about that. But AFAICT that won't solve the overall
> problems his draft is seeking to address (whether they can or should be
> addressed is debatable, IMO).
>=20
> ...
> >>>>>>> Right. That's why IPv6-in-IPv4 transition mechanisms cheat and
> >>>>>>> assume 1500 when the specs say they can only assume 576.
> >>>>>
> ...
> >>
> >> We don't disagree on IPv6. My claim is that for IPv4 it is
> *necessary*
> >> that endpoints support MTUs lower than 567 to allow IPv4
> fragmentation
> >> to support IPv4-in-IPv4 tunnels, including IPsec.
> >
> > I think there is way too much deployed base out there now
> > that boldly assumes 1500 that it would be impossible to put
> > them back in the bottle now.
>=20
> Then your table should have said IPv4 has a minMRU of 1500, but it
> doesn't. That's widely deployed, but cannot be assumed. Esp. on
> low-powered/low-mem devices.

About the 1500/576, I'm just repeating what I read in RFCs 791
and 1122. I think we need to stop debating about IPv4 tunnels.
They're widely deployed, and we can't put them back in the bottle.

> >> There are two solutions, of course - deploying SEAL would be the
> other.
> >> But I would expect that fixing incorrect implementations of an
> existing
> >> standard would be a lot easier than getting new code deployed for
> >> something that isn't yet standard.
> >
> > There are too many compelling reasons to migrate away from IP
> > fragmentation and move toward SEAL. Maybe also look at some of
> > the discussion on the IPv6 list so we can avoid duplication.
>=20
> I agree that SEAL is better than IP at fragmentation, but it's still a
> network fragmentation layer when used for IP tunnels. It doesn't solve
> the issues that some are concerned about recently.

As we have discussed in the ipv6 list, I am proposing SEAL as a
general fragmentation/reassembly framework for all applications
and not just tunneling. The SEAL header has the same footprint
as IPv6 frag header and can be used for the same purpose, whether
it be in tunnel-mode or transport-mode.

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

> Joe

From touch@isi.edu  Mon Jul  1 16:20:56 2013
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BC7811E82D7 for <int-area@ietfa.amsl.com>; Mon,  1 Jul 2013 16:20:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QiboZ-NG6fA5 for <int-area@ietfa.amsl.com>; Mon,  1 Jul 2013 16:20:50 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id C245011E82CC for <int-area@ietf.org>; Mon,  1 Jul 2013 16:20:50 -0700 (PDT)
Received: from [10.10.224.128] (pc2.prince-kyoto2013-unet.ocn.ne.jp [118.22.20.194]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r61NK2N1014521 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 1 Jul 2013 16:20:12 -0700 (PDT)
Message-ID: <51D20EA1.9090708@isi.edu>
Date: Mon, 01 Jul 2013 16:20:01 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
References: <2CF4CB03E2AA464BA0982EC92A02CE2509F187DD@BY2PRD0512MB653.namprd05.prod.outlook.com> <51C9DDC2.6090904@isi.edu> <2134F8430051B64F815C691A62D983180AA7CC@XCH-BLV-504.nw.nos.boeing.com> <51CA0DB8.6090401@isi.edu> <2134F8430051B64F815C691A62D983180AAB85@XCH-BLV-504.nw.nos.boeing.com> <51CA1771.6020304@isi.edu> <2134F8430051B64F815C691A62D983180AABF9@XCH-BLV-504.nw.nos.boeing.com> <51CA5B8A.4060008@isi.edu> <2134F8430051B64F815C691A62D983180AC895@XCH-BLV-504.nw.nos.boeing.com> <51D13B22.2050801@isi.edu> <2134F8430051B64F815C691A62D983180B1944@XCH-BLV-504.nw.nos.boeing.com> <51D1E0F6.4050300@isi.edu> <2134F8430051B64F815C691A62D983180B1E08@XCH-BLV-504.nw.nos.boeing.com> <51D1EBB1.6010002@isi.edu> <2134F8430051B64F815C691A62D983180B1EE3@XCH-BLV-504.nw.nos.boeing.com> <51D1F5DF.6000607@isi.edu> <2134F8430051B64F815C691A62D983180B1F8A@XCH-BLV-504.nw.nos.boeing.com> <51D200D4.7030101@isi.edu> <2134F8430051B64F815C691A62D983180B2019@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D983180B2019@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "Carlos Pignataro \(cpignata\)" <cpignata@cisco.com>, Internet Area <int-area@ietf.org>, Ronald Bonica <rbonica@juniper.net>
Subject: Re: [Int-area] New Version Notification	for draft-bonica-intarea-gre-mtu-00.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jul 2013 23:20:56 -0000

Fred,

On 7/1/2013 3:51 PM, Templin, Fred L wrote:
>> You can't know that unless you parse the IPv6 header chain. And adding
>> >SEAL inbetween IPv6 and the inner IPv6 adds one more step to that
>> >chain.
> The SEAL first fragment MUST contain at least 256 bytes (or up to
> the end of the packet) according to the specs. If that is not large
> enough to include sufficient ULP headers then the packet should
> probably be dropped anyway.
>
>> >Either way, DPI has to follow the chain step-by-step, vs. in a single
>> >leap as with IPv4.
 >
> Right, but how long can those chains be and still be considered
> a "realistic" IPv6 packet?

Although I agree it's important to have the header you want to examine 
in the first fragment, you still need to parse the chain.

With IPv4 that's one opcode - jump based on the offset in a memory.

With IPv6, you need to run that opcode as many times as there are 
headers. That's the problem. Not whether you have the header you want to 
examine, but whether you can access it in a single hardware operation.

That's a problem with or without SEAL, and it's the problem that the 
current discussion on intarea is trying to address.

Joe

From Fred.L.Templin@boeing.com  Mon Jul  1 16:31:15 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6914111E82F5 for <int-area@ietfa.amsl.com>; Mon,  1 Jul 2013 16:31:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.508
X-Spam-Level: 
X-Spam-Status: No, score=-6.508 tagged_above=-999 required=5 tests=[AWL=0.091,  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 a2j-Kole6fsW for <int-area@ietfa.amsl.com>; Mon,  1 Jul 2013 16:30:57 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (stl-mbsout-01.boeing.com [130.76.96.169]) by ietfa.amsl.com (Postfix) with ESMTP id D570011E82E2 for <int-area@ietf.org>; Mon,  1 Jul 2013 16:30:56 -0700 (PDT)
Received: from stl-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r61NUted004028 for <int-area@ietf.org>; Mon, 1 Jul 2013 18:30:56 -0500
Received: from XCH-NWHT-06.nw.nos.boeing.com (xch-nwht-06.nw.nos.boeing.com [130.247.25.110]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r61NUs3b004024 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Mon, 1 Jul 2013 18:30:55 -0500
Received: from XCH-EXCO-103.nw.nos.boeing.com (130.247.25.37) by XCH-NWHT-06.nw.nos.boeing.com (130.247.25.110) with Microsoft SMTP Server (TLS) id 8.3.297.1; Mon, 1 Jul 2013 16:30:54 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.48]) by XCH-EXCO-103.nw.nos.boeing.com ([fe80::7434:66d:a0ba:2234%15]) with mapi id 14.02.0328.011; Mon, 1 Jul 2013 16:30:53 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Joe Touch <touch@isi.edu>
Thread-Topic: [Int-area] New Version Notification	for draft-bonica-intarea-gre-mtu-00.txt
Thread-Index: AQHOdrGC4b1RAvvaSUeqp+MHZfntPplQdr8g
Date: Mon, 1 Jul 2013 23:30:53 +0000
Message-ID: <2134F8430051B64F815C691A62D983180B208E@XCH-BLV-504.nw.nos.boeing.com>
References: <2CF4CB03E2AA464BA0982EC92A02CE2509F187DD@BY2PRD0512MB653.namprd05.prod.outlook.com> <51C9DDC2.6090904@isi.edu> <2134F8430051B64F815C691A62D983180AA7CC@XCH-BLV-504.nw.nos.boeing.com> <51CA0DB8.6090401@isi.edu> <2134F8430051B64F815C691A62D983180AAB85@XCH-BLV-504.nw.nos.boeing.com> <51CA1771.6020304@isi.edu> <2134F8430051B64F815C691A62D983180AABF9@XCH-BLV-504.nw.nos.boeing.com> <51CA5B8A.4060008@isi.edu> <2134F8430051B64F815C691A62D983180AC895@XCH-BLV-504.nw.nos.boeing.com> <51D13B22.2050801@isi.edu> <2134F8430051B64F815C691A62D983180B1944@XCH-BLV-504.nw.nos.boeing.com> <51D1E0F6.4050300@isi.edu> <2134F8430051B64F815C691A62D983180B1E08@XCH-BLV-504.nw.nos.boeing.com> <51D1EBB1.6010002@isi.edu> <2134F8430051B64F815C691A62D983180B1EE3@XCH-BLV-504.nw.nos.boeing.com> <51D1F5DF.6000607@isi.edu> <2134F8430051B64F815C691A62D983180B1F8A@XCH-BLV-504.nw.nos.boeing.com> <51D200D4.7030101@isi.edu> <2134F8430051B64F815C691A62D983180B2019@XCH-BLV-504.nw.nos.boeing.com> <51D20EA1.9090708@isi.edu>
In-Reply-To: <51D20EA1.9090708@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "Carlos Pignataro \(cpignata\)" <cpignata@cisco.com>, Internet Area <int-area@ietf.org>, Ronald Bonica <rbonica@juniper.net>
Subject: Re: [Int-area] New Version Notification	for draft-bonica-intarea-gre-mtu-00.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jul 2013 23:31:16 -0000

Hi Joe,

> -----Original Message-----
> From: Joe Touch [mailto:touch@isi.edu]
> Sent: Monday, July 01, 2013 4:20 PM
> To: Templin, Fred L
> Cc: Carlos Pignataro (cpignata); Ronald Bonica; Internet Area
> Subject: Re: [Int-area] New Version Notification for draft-bonica-
> intarea-gre-mtu-00.txt
>=20
> Fred,
>=20
> On 7/1/2013 3:51 PM, Templin, Fred L wrote:
> >> You can't know that unless you parse the IPv6 header chain. And
> adding
> >> >SEAL inbetween IPv6 and the inner IPv6 adds one more step to that
> >> >chain.
> > The SEAL first fragment MUST contain at least 256 bytes (or up to
> > the end of the packet) according to the specs. If that is not large
> > enough to include sufficient ULP headers then the packet should
> > probably be dropped anyway.
> >
> >> >Either way, DPI has to follow the chain step-by-step, vs. in a
> single
> >> >leap as with IPv4.
>  >
> > Right, but how long can those chains be and still be considered
> > a "realistic" IPv6 packet?
>=20
> Although I agree it's important to have the header you want to examine
> in the first fragment,

Good. That means we need to set an upper bound on the maximum
length of an IPv6 header chain, right? And remember, with SEAL
the minimum first fragment size is 256 bytes whereas the min
first-frag size for IPv6 fragment header is only 8 bytes. SEAL
therefore naturally avoids an attack vector available for IPv6
frag/reass.

> you still need to parse the chain.

That is by design of the IPv6 protocol, and not something that
can be changed now regardless of the encapsulation, right?

> With IPv4 that's one opcode - jump based on the offset in a memory.

Right.

> With IPv6, you need to run that opcode as many times as there are
> headers. That's the problem. Not whether you have the header you want
> to
> examine, but whether you can access it in a single hardware operation.
>=20
> That's a problem with or without SEAL, and it's the problem that the
> current discussion on intarea is trying to address.

Have there been any proposals? As in, is there any way to approach
this without a major redesign of IPv6? I also thought that the IPv6
"quadword-aligned" requirement addressed performance. Is that not
helpful?

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

> Joe

From touch@isi.edu  Mon Jul  1 16:55:42 2013
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75E7811E833D for <int-area@ietfa.amsl.com>; Mon,  1 Jul 2013 16:55:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jEw4zxGF-Du7 for <int-area@ietfa.amsl.com>; Mon,  1 Jul 2013 16:55:30 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id B7E3F11E8318 for <int-area@ietf.org>; Mon,  1 Jul 2013 16:54:46 -0700 (PDT)
Received: from [10.10.224.128] (pc2.prince-kyoto2013-unet.ocn.ne.jp [118.22.20.194]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r61NrttQ020997 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 1 Jul 2013 16:54:05 -0700 (PDT)
Message-ID: <51D21693.2060301@isi.edu>
Date: Mon, 01 Jul 2013 16:53:55 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
References: <2CF4CB03E2AA464BA0982EC92A02CE2509F187DD@BY2PRD0512MB653.namprd05.prod.outlook.com> <51CA0DB8.6090401@isi.edu> <2134F8430051B64F815C691A62D983180AAB85@XCH-BLV-504.nw.nos.boeing.com> <51CA1771.6020304@isi.edu> <2134F8430051B64F815C691A62D983180AABF9@XCH-BLV-504.nw.nos.boeing.com> <51CA5B8A.4060008@isi.edu> <2134F8430051B64F815C691A62D983180AC895@XCH-BLV-504.nw.nos.boeing.com> <51D13B22.2050801@isi.edu> <2134F8430051B64F815C691A62D983180B1944@XCH-BLV-504.nw.nos.boeing.com> <51D1E0F6.4050300@isi.edu> <2134F8430051B64F815C691A62D983180B1E08@XCH-BLV-504.nw.nos.boeing.com> <51D1EBB1.6010002@isi.edu> <2134F8430051B64F815C691A62D983180B1EE3@XCH-BLV-504.nw.nos.boeing.com> <51D1F5DF.6000607@isi.edu> <2134F8430051B64F815C691A62D983180B1F8A@XCH-BLV-504.nw.nos.boeing.com> <51D200D4.7030101@isi.edu> <2134F8430051B64F815C691A62D983180B2019@XCH-BLV-504.nw.nos.boeing.com> <51D20EA1.9090708@isi.edu> <2134F8430051B64F815C691A62D983180B208E@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D983180B208E@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "Carlos Pignataro \(cpignata\)" <cpignata@cisco.com>, Internet Area <int-area@ietf.org>, Ronald Bonica <rbonica@juniper.net>
Subject: Re: [Int-area] New Version Notification	for draft-bonica-intarea-gre-mtu-00.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jul 2013 23:55:43 -0000

Hi, Fred,

On 7/1/2013 4:30 PM, Templin, Fred L wrote:
> Hi Joe,
>
>...
>>>>> Either way, DPI has to follow the chain step-by-step, vs. in a
>> single leap as with IPv4.
>>>
>>> Right, but how long can those chains be and still be considered
>>> a "realistic" IPv6 packet?
>>
>> Although I agree it's important to have the header you want to examine
>> in the first fragment,
>
> Good. That means we need to set an upper bound on the maximum
> length of an IPv6 header chain, right?

That is only part of the solution. The other part is a way to jump to 
the place you want to quickly, but that makes it hard to modify the chain.

>> you still need to parse the chain.
>
> That is by design of the IPv6 protocol,

Yes.

> and not something that
> can be changed now regardless of the encapsulation, right?

Well, some are trying to "change" it by deprecating IPv6 options 
completely - including fragmentation. That would mean that 
non-encapsulated packets would have a zero-length chain.

It doesn't help packets with encapsulation - for SEAL, IP-in-IP, etc.

>> With IPv4 that's one opcode - jump based on the offset in a memory.
>
> Right.
>
>> With IPv6, you need to run that opcode as many times as there are
>> headers. That's the problem. Not whether you have the header you want
>> to
>> examine, but whether you can access it in a single hardware operation.
>>
>> That's a problem with or without SEAL, and it's the problem that the
>> current discussion on intarea is trying to address.
>
> Have there been any proposals? As in, is there any way to approach
> this without a major redesign of IPv6? I also thought that the IPv6
> "quadword-aligned" requirement addressed performance. Is that not
> helpful?

The primary proposal is to deprecate all IP options.

Alignment addresses one part of the problem - how fine-grained the jumps 
are - but not the chain.

--

My point is that SEAL is not a solution to the problem driving the 
desire to get rid of IP fragmentation. That desire isn't because 
fragmentation is incomplete or suboptimal, it's because it's *there*.

Joe

From Fred.L.Templin@boeing.com  Tue Jul  2 08:06:24 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9611221F9F55 for <int-area@ietfa.amsl.com>; Tue,  2 Jul 2013 08:06:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.513
X-Spam-Level: 
X-Spam-Status: No, score=-6.513 tagged_above=-999 required=5 tests=[AWL=0.086,  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 BVfAbLCFGpsr for <int-area@ietfa.amsl.com>; Tue,  2 Jul 2013 08:06:18 -0700 (PDT)
Received: from blv-mbsout-01.boeing.com (blv-mbsout-01.boeing.com [130.76.32.231]) by ietfa.amsl.com (Postfix) with ESMTP id C823521F9F57 for <int-area@ietf.org>; Tue,  2 Jul 2013 08:06:06 -0700 (PDT)
Received: from blv-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r62F6k5Q029931 for <int-area@ietf.org>; Tue, 2 Jul 2013 08:06:47 -0700
Received: from XCH-NWHT-03.nw.nos.boeing.com (xch-nwht-03.nw.nos.boeing.com [130.247.71.23]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r62F6j5V029919 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Tue, 2 Jul 2013 08:06:45 -0700
Received: from XCH-BLV-202.nw.nos.boeing.com (10.57.37.69) by XCH-NWHT-03.nw.nos.boeing.com (130.247.71.23) with Microsoft SMTP Server (TLS) id 8.3.297.1; Tue, 2 Jul 2013 08:06:04 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.48]) by XCH-BLV-202.nw.nos.boeing.com ([169.254.2.60]) with mapi id 14.02.0328.011; Tue, 2 Jul 2013 08:06:04 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Joe Touch <touch@isi.edu>
Thread-Topic: [Int-area] New Version Notification	for draft-bonica-intarea-gre-mtu-00.txt
Thread-Index: AQHOdrY+4b1RAvvaSUeqp+MHZfntPplRe89A
Date: Tue, 2 Jul 2013 15:06:03 +0000
Message-ID: <2134F8430051B64F815C691A62D983180B2A10@XCH-BLV-504.nw.nos.boeing.com>
References: <2CF4CB03E2AA464BA0982EC92A02CE2509F187DD@BY2PRD0512MB653.namprd05.prod.outlook.com> <51CA0DB8.6090401@isi.edu> <2134F8430051B64F815C691A62D983180AAB85@XCH-BLV-504.nw.nos.boeing.com> <51CA1771.6020304@isi.edu> <2134F8430051B64F815C691A62D983180AABF9@XCH-BLV-504.nw.nos.boeing.com> <51CA5B8A.4060008@isi.edu> <2134F8430051B64F815C691A62D983180AC895@XCH-BLV-504.nw.nos.boeing.com> <51D13B22.2050801@isi.edu> <2134F8430051B64F815C691A62D983180B1944@XCH-BLV-504.nw.nos.boeing.com> <51D1E0F6.4050300@isi.edu> <2134F8430051B64F815C691A62D983180B1E08@XCH-BLV-504.nw.nos.boeing.com> <51D1EBB1.6010002@isi.edu> <2134F8430051B64F815C691A62D983180B1EE3@XCH-BLV-504.nw.nos.boeing.com> <51D1F5DF.6000607@isi.edu> <2134F8430051B64F815C691A62D983180B1F8A@XCH-BLV-504.nw.nos.boeing.com> <51D200D4.7030101@isi.edu> <2134F8430051B64F815C691A62D983180B2019@XCH-BLV-504.nw.nos.boeing.com> <51D20EA1.9090708@isi.edu> <2134F8430051B64F815C691A62D983180B208E@XCH-BLV-504.nw.nos.boeing.com> <51D21693.2060301@isi.edu>
In-Reply-To: <51D21693.2060301@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Cc: "Carlos Pignataro \(cpignata\)" <cpignata@cisco.com>, Internet Area <int-area@ietf.org>, Ronald Bonica <rbonica@juniper.net>
Subject: Re: [Int-area] New Version Notification	for draft-bonica-intarea-gre-mtu-00.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Jul 2013 15:06:24 -0000

Hi Joe,

It occurred to me that the SEAL header has an available byte
that could be used as an offset to branch to the end of the
extension header chain without having to parse all other
extension headers in between. If that's not good enough
then I don't know what else to say, because we have already
established that some form of fragmentation is necessary.

Please don't answer if it is uncomfortable to do so, Joe,
but are you against seeing IPv6 move forward?

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

> -----Original Message-----
> From: Joe Touch [mailto:touch@isi.edu]
> Sent: Monday, July 01, 2013 4:54 PM
> To: Templin, Fred L
> Cc: Carlos Pignataro (cpignata); Ronald Bonica; Internet Area
> Subject: Re: [Int-area] New Version Notification for draft-bonica-
> intarea-gre-mtu-00.txt
>=20
> Hi, Fred,
>=20
> On 7/1/2013 4:30 PM, Templin, Fred L wrote:
> > Hi Joe,
> >
> >...
> >>>>> Either way, DPI has to follow the chain step-by-step, vs. in a
> >> single leap as with IPv4.
> >>>
> >>> Right, but how long can those chains be and still be considered
> >>> a "realistic" IPv6 packet?
> >>
> >> Although I agree it's important to have the header you want to
> examine
> >> in the first fragment,
> >
> > Good. That means we need to set an upper bound on the maximum
> > length of an IPv6 header chain, right?
>=20
> That is only part of the solution. The other part is a way to jump to
> the place you want to quickly, but that makes it hard to modify the
> chain.
>=20
> >> you still need to parse the chain.
> >
> > That is by design of the IPv6 protocol,
>=20
> Yes.
>=20
> > and not something that
> > can be changed now regardless of the encapsulation, right?
>=20
> Well, some are trying to "change" it by deprecating IPv6 options
> completely - including fragmentation. That would mean that
> non-encapsulated packets would have a zero-length chain.
>=20
> It doesn't help packets with encapsulation - for SEAL, IP-in-IP, etc.
>=20
> >> With IPv4 that's one opcode - jump based on the offset in a memory.
> >
> > Right.
> >
> >> With IPv6, you need to run that opcode as many times as there are
> >> headers. That's the problem. Not whether you have the header you
> want
> >> to
> >> examine, but whether you can access it in a single hardware
> operation.
> >>
> >> That's a problem with or without SEAL, and it's the problem that the
> >> current discussion on intarea is trying to address.
> >
> > Have there been any proposals? As in, is there any way to approach
> > this without a major redesign of IPv6? I also thought that the IPv6
> > "quadword-aligned" requirement addressed performance. Is that not
> > helpful?
>=20
> The primary proposal is to deprecate all IP options.
>=20
> Alignment addresses one part of the problem - how fine-grained the
> jumps
> are - but not the chain.
>=20
> --
>=20
> My point is that SEAL is not a solution to the problem driving the
> desire to get rid of IP fragmentation. That desire isn't because
> fragmentation is incomplete or suboptimal, it's because it's *there*.
>=20
> Joe

From touch@isi.edu  Tue Jul  2 14:20:41 2013
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F35AF21F9590 for <int-area@ietfa.amsl.com>; Tue,  2 Jul 2013 14:20:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rpKnYjbr2Nbb for <int-area@ietfa.amsl.com>; Tue,  2 Jul 2013 14:20:35 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 3A86721F955A for <int-area@ietf.org>; Tue,  2 Jul 2013 14:20:35 -0700 (PDT)
Received: from [10.10.224.128] (pc2.prince-kyoto2013-unet.ocn.ne.jp [118.22.20.194]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r62LJfAr005940 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 2 Jul 2013 14:19:51 -0700 (PDT)
Message-ID: <51D343ED.3080607@isi.edu>
Date: Tue, 02 Jul 2013 14:19:41 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
References: <2CF4CB03E2AA464BA0982EC92A02CE2509F187DD@BY2PRD0512MB653.namprd05.prod.outlook.com> <51CA1771.6020304@isi.edu> <2134F8430051B64F815C691A62D983180AABF9@XCH-BLV-504.nw.nos.boeing.com> <51CA5B8A.4060008@isi.edu> <2134F8430051B64F815C691A62D983180AC895@XCH-BLV-504.nw.nos.boeing.com> <51D13B22.2050801@isi.edu> <2134F8430051B64F815C691A62D983180B1944@XCH-BLV-504.nw.nos.boeing.com> <51D1E0F6.4050300@isi.edu> <2134F8430051B64F815C691A62D983180B1E08@XCH-BLV-504.nw.nos.boeing.com> <51D1EBB1.6010002@isi.edu> <2134F8430051B64F815C691A62D983180B1EE3@XCH-BLV-504.nw.nos.boeing.com> <51D1F5DF.6000607@isi.edu> <2134F8430051B64F815C691A62D983180B1F8A@XCH-BLV-504.nw.nos.boeing.com> <51D200D4.7030101@isi.edu> <2134F8430051B64F815C691A62D983180B2019@XCH-BLV-504.nw.nos.boeing.com> <51D20EA1.9090708@isi.edu> <2134F8430051B64F815C691A62D983180B208E@XCH-BLV-504.nw.nos.boeing.com> <51D21693.2060301@isi.edu> <2134F8430051B64F815C691A62D983180B2A10@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D983180B2A10@XCH-BLV-504.nw.nos.boeing.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "Carlos Pignataro \(cpignata\)" <cpignata@cisco.com>, Internet Area <int-area@ietf.org>, Ronald Bonica <rbonica@juniper.net>
Subject: Re: [Int-area] New Version Notification	for draft-bonica-intarea-gre-mtu-00.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Jul 2013 21:20:41 -0000

Hi, Fred,

On 7/2/2013 8:06 AM, Templin, Fred L wrote:
> Hi Joe,
>
> It occurred to me that the SEAL header has an available byte
> that could be used as an offset to branch to the end of the
> extension header chain without having to parse all other
> extension headers in between. If that's not good enough
> then I don't know what else to say, because we have already
> established that some form of fragmentation is necessary.
>
> Please don't answer if it is uncomfortable to do so, Joe,
> but are you against seeing IPv6 move forward?

I'm not, but this won't help.

I had thought about this as a possibility for a new IP option, i.e., one 
that jumps to the end of the options. However, that option would need to 
be updated by any code that added an intermediate header, and I'm not 
sure how that would work.

IP already puts all the options that a router should be looking at in 
one place - by design. The problem here is that routers want to look 
further. In IPv4, there's a notion of the base header, option headers, 
and a payload. In the 'old days', the payload was the transport header, 
so it was easy to know where to look to find port numbers.

Those days have changed. There are many protocols that add 'shim' layers 
between IP and transport, or other places in the conventional stack. 
That's part of why IPv6 designed its headers as chained - to make it 
easier to support shim layers without redesigning IP and without 
limiting the space available for such layers.

So we have a tension between the many folks who want to insert these 
shims and DPI devices. The DPI devices want to do less work than an 
endpoint to find the transport information, but that may or may not be 
feasible using the current IPv6 structure.

Joe

From suresh.krishnan@ericsson.com  Fri Jul  5 10:39:27 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 9B34021F8B07 for <int-area@ietfa.amsl.com>; Fri,  5 Jul 2013 10:39:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eAq1ZNpRM+jR for <int-area@ietfa.amsl.com>; Fri,  5 Jul 2013 10:39:21 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 3D18321F93BF for <int-area@ietf.org>; Fri,  5 Jul 2013 10:39:21 -0700 (PDT)
X-AuditID: c6180641-b7f986d000007a82-fd-51d704c806fe
Received: from EUSAAHC001.ericsson.se (Unknown_Domain [147.117.188.75]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id CC.79.31362.8C407D15; Fri,  5 Jul 2013 19:39:20 +0200 (CEST)
Received: from [142.133.112.75] (147.117.188.135) by smtps-am.internal.ericsson.com (147.117.188.75) with Microsoft SMTP Server (TLS) id 14.2.328.9; Fri, 5 Jul 2013 13:39:19 -0400
Message-ID: <51D7042D.6070207@ericsson.com>
Date: Fri, 5 Jul 2013 13:36:45 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130404 Thunderbird/17.0.5
MIME-Version: 1.0
To: "int-area@ietf.org" <int-area@ietf.org>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [147.117.188.135]
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrHJMWRmVeSWpSXmKPExsUyuXSPt+4JluuBBmf3SlncmHWTxYHRY8mS n0wBjFFcNimpOZllqUX6dglcGY33j7MWnGKu2NS1hLWB8Q5TFyMnh4SAicSiratZIWwxiQv3 1rN1MXJxCAkcZZR4c/8CC0hCSGA7o8SXp2UgNq+AtsT+NdeYQWwWARWJ/x0HwAaxAQ3asPMz mC0qECbxYdkSJoh6QYmTM5+AzREB6X1yAMwWFtCQmDp/OtRiSYktL9rZQWxmAT2JKVdbGCFs eYntb+cwQ9ygKbF1zXegeg6gemWJHTMSJzAKzEKyYRaS7llIuhcwMq9i5CgtTi3LTTcy3MQI DLNjEmyOOxgXfLI8xCjNwaIkzrtB70ygkEB6YklqdmpqQWpRfFFpTmrxIUYmDk6pBkbfpT0f /0zsfhjd8tV8h8kZw4y9KyT/6lSuLrabuuPd53nlyRnFYka1n09sOrvnjFL8Sichk8MN7Qdm tZrriCkdfPL33oIc9wVfgv1FI4UUBc9/MuvfrSuhs+pEUprI7Z/zzOQv1zO9eOAz+VO4bmTK La+03X/Zdd1qrM6ocx7sFV+vl/ZeuFCJpTgj0VCLuag4EQBMplhtAQIAAA==
Subject: [Int-area] Call for agenda items at IETF87
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, 05 Jul 2013 17:39:27 -0000

Hi all,
   The intarea WG will be meeting at the Berlin IETF (we have been
allocated a 2 hour slot on Friday) and we are in the process of setting
the agenda. Please send us your request for slots detailing

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

Thanks
Suresh and Julien






From ryuji.wakikawa@gmail.com  Wed Jul 10 09:15:40 2013
Return-Path: <ryuji.wakikawa@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 201D621F864D for <int-area@ietfa.amsl.com>; Wed, 10 Jul 2013 09:15:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BVkj3OT1qOTD for <int-area@ietfa.amsl.com>; Wed, 10 Jul 2013 09:15:39 -0700 (PDT)
Received: from mail-ve0-x22e.google.com (mail-ve0-x22e.google.com [IPv6:2607:f8b0:400c:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 77C8321F8F09 for <int-area@ietf.org>; Wed, 10 Jul 2013 09:15:36 -0700 (PDT)
Received: by mail-ve0-f174.google.com with SMTP id oz10so6042652veb.5 for <int-area@ietf.org>; Wed, 10 Jul 2013 09:15:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:date:references :to:message-id:mime-version:x-mailer; bh=Yyttm84sUKah/pJyNiIxkvto8c3qhre+QbgOyms/z2A=; b=YYUBbglQ63Nq/jhMnW90H7HWC3TcKgbaS3UAeb9p/DYzPn66KbF2vdhn8+69AfYFAl ml204GncUyl70RAsfC+KlxDlpIJ0Q7l7zaTbZlu+8L4hv/I2bhEved0krS6ZWZeg6rsa DogBBkZbvQDi0zp28WOjJTZzIr8aXIFbC+Z2WyCVFA6R4RF/ylmormzqmT23Tr9WBYnc RpUqMmcEsOkY4qE34qBHt73iEoLT+o0fr+g9nfshxSOvjCpkYG/o40454bfVSaJARr1x s4k1AEW6yz4sePqC7Uwp+glQiMz6jbtkqEcwbMyLD6bFpzaccETsqzByFiU72B+QRZN3 IcjQ==
X-Received: by 10.220.111.206 with SMTP id t14mr19691475vcp.77.1373472935849;  Wed, 10 Jul 2013 09:15:35 -0700 (PDT)
Received: from [10.71.31.234] ([38.126.120.10]) by mx.google.com with ESMTPSA id 20sm25568371vde.3.2013.07.10.09.15.34 for <int-area@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 10 Jul 2013 09:15:34 -0700 (PDT)
From: Ryuji Wakikawa <ryuji.wakikawa@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Wed, 10 Jul 2013 09:15:34 -0700
References: <20130710160944.11064.6824.idtracker@ietfa.amsl.com>
To: Internet Area <int-area@ietf.org>
Message-Id: <492A8226-B3D0-4347-8A85-0967F89519AE@gmail.com>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
Subject: [Int-area] Fwd: New Version Notification for draft-matsushima-stateless-uplane-vepc-00.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jul 2013 16:15:40 -0000

Hi=20

We submit a new document of new mobile architecture.=20
This document discuss mobility system in general, Please allow me to =
post it to INT area.
Your comments are appreciated!=20

thanks,
ryuji


Begin forwarded message:

> From: internet-drafts@ietf.org
> Subject: New Version Notification for =
draft-matsushima-stateless-uplane-vepc-00.txt
> Date: July 10, 2013 9:09:44 AM PDT
> To: Ryuji Wakikawa <ryuji.wakikawa@gmail.com>, Satoru Matsushima =
<satoru.matsushima@g.softbank.co.jp>
>=20
>=20
> A new version of I-D, draft-matsushima-stateless-uplane-vepc-00.txt
> has been successfully submitted by Satoru Matsushima and posted to the
> IETF repository.
>=20
> Filename:	 draft-matsushima-stateless-uplane-vepc
> Revision:	 00
> Title:		 Stateless user-plane architecture for =
virtualized EPC (vEPC)
> Creation date:	 2013-07-10
> Group:		 Individual Submission
> Number of pages: 19
> URL:             =
http://www.ietf.org/internet-drafts/draft-matsushima-stateless-uplane-vepc=
-00.txt
> Status:          =
http://datatracker.ietf.org/doc/draft-matsushima-stateless-uplane-vepc
> Htmlized:        =
http://tools.ietf.org/html/draft-matsushima-stateless-uplane-vepc-00
>=20
>=20
> Abstract:
>   We envision a new mobile architecture for the future Evolved Packet
>   Core (EPC).  The new architecture is designed to support the
>   virtualization scheme called NFV (Network Function Virtualization).
>   In our architecture, the user plane of EPC is decoupled from the
>   control-plane and uses routing information to forward packets of
>   mobile nodes.  Although the EPC control plane will run on =
hypervisor,
>   our proposal does not modify the signaling of the EPC control plane.
>   The benefits of our architecture are 1) scalability, 2) flexibility
>   and 3) Manageability.  How to run the EPC control plane on NFV is =
out
>   of our focus in this document.
>=20
>=20
>=20
>=20
> The IETF Secretariat
>=20


From suresh.krishnan@ericsson.com  Wed Jul 10 15:52:09 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 0FE7311E8144 for <int-area@ietfa.amsl.com>; Wed, 10 Jul 2013 15:52:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aYAhTBDcrlfy for <int-area@ietfa.amsl.com>; Wed, 10 Jul 2013 15:52:02 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 1172411E813D for <int-area@ietf.org>; Wed, 10 Jul 2013 15:51:54 -0700 (PDT)
X-AuditID: c618062d-b7fc36d0000032ea-51-51dde589125e
Received: from EUSAAHC004.ericsson.se (Unknown_Domain [147.117.188.84]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id DF.C3.13034.985EDD15; Thu, 11 Jul 2013 00:51:53 +0200 (CEST)
Received: from [142.133.112.97] (147.117.188.135) by smtps-am.internal.ericsson.com (147.117.188.84) with Microsoft SMTP Server (TLS) id 14.2.328.9; Wed, 10 Jul 2013 18:51:44 -0400
Message-ID: <51DDE4E6.80103@ericsson.com>
Date: Wed, 10 Jul 2013 18:49:10 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130404 Thunderbird/17.0.5
MIME-Version: 1.0
To: Internet Area <int-area@ietf.org>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [147.117.188.135]
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrLJMWRmVeSWpSXmKPExsUyuXRPiG7n07uBBg8eGVrcmHWTxYHRY8mS n0wBjFFcNimpOZllqUX6dglcGW+PHGYveM1SsWnyL8YGxg6WLkZODgkBE4lJG5eyQ9hiEhfu rWfrYuTiEBI4yihxr38lK0hCSGAHo8TlHlEQm1dAU2L15knMIDaLgKrEhzldjCA2G9CgDTs/ M4HYogJhEh+WLWGCqBeUODnzCdgyEaD611svAi3g4BAW8Je4uZ0JYq+kxJYX7WA3MAvoSUy5 2sIIYctLbH87hxniBE2JrWu+s4K0SggoS+yYkTiBUWAWkgWzkHTPQtK9gJF5FSNHaXFqWW66 kcEmRmCQHZNg093BuOel5SFGaQ4WJXHeVXpnAoUE0hNLUrNTUwtSi+KLSnNSiw8xMnFwSjUw FkWxP3u3xeuh0T0xKd+k9yWndzdLGxme2CGtVnaAYyoD19SHOec97Ji/xT/6f3kjY7Hpzr5f AlfOpSUzMyrfKCkzzuIo2dT1fNY7xzSn88EcSyyMVealPvBQYo+4dMw88o5wrUvD/XYXt5UW W668u8ZoaSZXcF4rXsXzvQKXXfV0tiVfTv9XYinOSDTUYi4qTgQA/NuMegACAAA=
Subject: [Int-area] Working group last call for draft-ietf-intarea-flow-label-balancing-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: Wed, 10 Jul 2013 22:52:09 -0000

Hi all,
  This message starts a two week intarea working group last call on this
draft describing the use of IPv6 Flow Label for Server Load Balancing as
an Informational RFC. The draft is available at

http://www.ietf.org/id/draft-ietf-intarea-flow-label-balancing-01.txt
http://tools.ietf.org/html/draft-ietf-intarea-flow-label-balancing-01

Substantive comments and statements of support/opposition for advancing
this document should be directed to the mailing list. Editorial
suggestions can be sent directly to the authors. This last call will
conclude on July 24, 2013.

Regards,
Suresh & Julien


From leo.liubing@huawei.com  Wed Jul 10 18:41:12 2013
Return-Path: <leo.liubing@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 DA2F521F8ECB for <int-area@ietfa.amsl.com>; Wed, 10 Jul 2013 18:41:12 -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 w8ePtqY62eCK for <int-area@ietfa.amsl.com>; Wed, 10 Jul 2013 18:41:08 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 217E621F8F4F for <int-area@ietf.org>; Wed, 10 Jul 2013 18:40:43 -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 ATI13755; Thu, 11 Jul 2013 01:40:42 +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; Thu, 11 Jul 2013 02:40:18 +0100
Received: from NKGEML402-HUB.china.huawei.com (10.98.56.33) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 11 Jul 2013 02:40:38 +0100
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.240]) by nkgeml402-hub.china.huawei.com ([10.98.56.33]) with mapi id 14.01.0323.007; Thu, 11 Jul 2013 09:40:31 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>, Internet Area <int-area@ietf.org>
Thread-Topic: [Int-area] Working group last call for draft-ietf-intarea-flow-label-balancing-01
Thread-Index: AQHOfcAjjtJn8ctfxkaPcA3sFjohNJlespWA
Date: Thu, 11 Jul 2013 01:40:30 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D73A404@nkgeml506-mbx.china.huawei.com>
References: <51DDE4E6.80103@ericsson.com>
In-Reply-To: <51DDE4E6.80103@ericsson.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.161]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [Int-area] Working group last call for	draft-ietf-intarea-flow-label-balancing-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: Thu, 11 Jul 2013 01:41:13 -0000

Hi, WG

I'm in favor of advancing it.=20

B.R.
Bing

> -----Original Message-----
> From: int-area-bounces@ietf.org [mailto:int-area-bounces@ietf.org] On
> Behalf Of Suresh Krishnan
> Sent: Thursday, July 11, 2013 6:49 AM
> To: Internet Area
> Subject: [Int-area] Working group last call for
> draft-ietf-intarea-flow-label-balancing-01
>=20
> Hi all,
>   This message starts a two week intarea working group last call on this
> draft describing the use of IPv6 Flow Label for Server Load Balancing as
> an Informational RFC. The draft is available at
>=20
> http://www.ietf.org/id/draft-ietf-intarea-flow-label-balancing-01.txt
> http://tools.ietf.org/html/draft-ietf-intarea-flow-label-balancing-01
>=20
> Substantive comments and statements of support/opposition for advancing
> this document should be directed to the mailing list. Editorial
> suggestions can be sent directly to the authors. This last call will
> conclude on July 24, 2013.
>=20
> Regards,
> Suresh & Julien
>=20
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area

From bingxuere@gmail.com  Wed Jul 10 22:20:47 2013
Return-Path: <bingxuere@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 403E721F933B for <int-area@ietfa.amsl.com>; Wed, 10 Jul 2013 22:20:47 -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 jxfIPJUlYYir for <int-area@ietfa.amsl.com>; Wed, 10 Jul 2013 22:20:46 -0700 (PDT)
Received: from mail-vc0-x22d.google.com (mail-vc0-x22d.google.com [IPv6:2607:f8b0:400c:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 5F2E621F9339 for <int-area@ietf.org>; Wed, 10 Jul 2013 22:20:46 -0700 (PDT)
Received: by mail-vc0-f173.google.com with SMTP id ht10so6367849vcb.18 for <int-area@ietf.org>; Wed, 10 Jul 2013 22:20:45 -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=u1f+EXL9A3zzlNlS+FToprccS1etwIzxqQZGBKN3tuw=; b=n/gcAiBJjpmGSrlknp/ILTC1Rzmr3KS1oYKp17bLuOwQGe595vxXh/UG88DUVh1xww ojm8tzFrjcbt8D391x2VjskfUmB7WbIeUAtzpDBU5oTYGslepN8gW5fD3pLAxbQvGseB 5xuxtCpBlYjglg4jlz+KJ/LrK6SSJJKbcWvdUubttKUiBJjBTqER80Iz/QVRpCfpgI4c 4uGjJMBl0aduZ8/u0wLR6OcF+90viQMSIsHOT+7I26P8akS+Zf2CtmZ8mjpdBNV5l0aE QcAogdFCzQlVmU3o5pjM7HPcDhNyWUhD2PXKXwiGmTPgIt/OuuCnTDe1kT2uh11FnkHf TuZA==
X-Received: by 10.58.127.202 with SMTP id ni10mr20324856veb.27.1373520045272;  Wed, 10 Jul 2013 22:20:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.210.202 with HTTP; Wed, 10 Jul 2013 22:20:05 -0700 (PDT)
In-Reply-To: <51DDE4E6.80103@ericsson.com>
References: <51DDE4E6.80103@ericsson.com>
From: Qiong <bingxuere@gmail.com>
Date: Thu, 11 Jul 2013 13:20:05 +0800
Message-ID: <CAH3bfABG+-WQysRQHtFjU6PfNmSnkqqnTsUEMWT8Hd=uWL+F=g@mail.gmail.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Content-Type: multipart/alternative; boundary=047d7b5d870f63f3e904e1358e0d
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] Working group last call for draft-ietf-intarea-flow-label-balancing-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: Thu, 11 Jul 2013 05:20:47 -0000

--047d7b5d870f63f3e904e1358e0d
Content-Type: text/plain; charset=UTF-8

Dear all,

I think it is ready to move forward.

Thanks

Best wishes
Qiong


On Thu, Jul 11, 2013 at 6:49 AM, Suresh Krishnan <
suresh.krishnan@ericsson.com> wrote:

> Hi all,
>   This message starts a two week intarea working group last call on this
> draft describing the use of IPv6 Flow Label for Server Load Balancing as
> an Informational RFC. The draft is available at
>
> http://www.ietf.org/id/draft-ietf-intarea-flow-label-balancing-01.txt
> http://tools.ietf.org/html/draft-ietf-intarea-flow-label-balancing-01
>
> Substantive comments and statements of support/opposition for advancing
> this document should be directed to the mailing list. Editorial
> suggestions can be sent directly to the authors. This last call will
> conclude on July 24, 2013.
>
> Regards,
> Suresh & Julien
>
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area
>



-- 
==============================================
Qiong Sun
China Telecom Beijing Research Institude


Open source code:
lightweight 4over6: *http://sourceforge.net/projects/laft6/*
PCP-natcoord:* http://sourceforge.net/projects/pcpportsetdemo/ *
===============================================

--047d7b5d870f63f3e904e1358e0d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Dear all,<div><br></div><div style>I think it is ready to =
move forward.</div><div style><br></div><div style>Thanks</div><div style><=
br></div><div style>Best wishes</div><div style>Qiong=C2=A0</div><div class=
=3D"gmail_extra">

<br><br><div class=3D"gmail_quote">On Thu, Jul 11, 2013 at 6:49 AM, Suresh =
Krishnan <span dir=3D"ltr">&lt;<a href=3D"mailto:suresh.krishnan@ericsson.c=
om" target=3D"_blank">suresh.krishnan@ericsson.com</a>&gt;</span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">

Hi all,<br>
=C2=A0 This message starts a two week intarea working group last call on th=
is<br>
draft describing the use of IPv6 Flow Label for Server Load Balancing as<br=
>
an Informational RFC. The draft is available at<br>
<br>
<a href=3D"http://www.ietf.org/id/draft-ietf-intarea-flow-label-balancing-0=
1.txt" target=3D"_blank">http://www.ietf.org/id/draft-ietf-intarea-flow-lab=
el-balancing-01.txt</a><br>
<a href=3D"http://tools.ietf.org/html/draft-ietf-intarea-flow-label-balanci=
ng-01" target=3D"_blank">http://tools.ietf.org/html/draft-ietf-intarea-flow=
-label-balancing-01</a><br>
<br>
Substantive comments and statements of support/opposition for advancing<br>
this document should be directed to the mailing list. Editorial<br>
suggestions can be sent directly to the authors. This last call will<br>
conclude on July 24, 2013.<br>
<br>
Regards,<br>
Suresh &amp; Julien<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><br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>Qiong Sun<br>China T=
elecom Beijing Research Institude<br><br><br>Open source code:<br>lightweig=
ht 4over6: <i><a href=3D"http://sourceforge.net/projects/laft6/" target=3D"=
_blank">http://sourceforge.net/projects/laft6/</a></i><br>

PCP-natcoord:<i> <a href=3D"http://sourceforge.net/projects/pcpportsetdemo/=
" target=3D"_blank">http://sourceforge.net/projects/pcpportsetdemo/</a> </i=
><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br=
><br>
</div></div>

--047d7b5d870f63f3e904e1358e0d--

From eleven.fuyu@huawei.com  Thu Jul 11 00:27:32 2013
Return-Path: <eleven.fuyu@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 CC3A421F99FB for <int-area@ietfa.amsl.com>; Thu, 11 Jul 2013 00:27:32 -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=[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 A4Z5sbScfgV0 for <int-area@ietfa.amsl.com>; Thu, 11 Jul 2013 00:27:28 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0AD2021F8F78 for <int-area@ietf.org>; Thu, 11 Jul 2013 00:27:27 -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 AUX33875; Thu, 11 Jul 2013 07:27:18 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 11 Jul 2013 08:26:34 +0100
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 11 Jul 2013 08:27:08 +0100
Received: from NKGEML505-MBX.china.huawei.com ([169.254.1.159]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.01.0323.007; Thu, 11 Jul 2013 15:27:01 +0800
From: "Fuyu (Eleven)" <eleven.fuyu@huawei.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Thread-Topic: [Int-area] Working group last call for draft-ietf-intarea-flow-label-balancing-01
Thread-Index: AQHOffZy2esCCLl6zEG7/2re9Ft6NplfEYAQ
Date: Thu, 11 Jul 2013 07:27:01 +0000
Message-ID: <EF6A204047BD994A860EE26D5F23BF5840561187@nkgeml505-mbx.china.huawei.com>
References: <51DDE4E6.80103@ericsson.com> <CAH3bfABG+-WQysRQHtFjU6PfNmSnkqqnTsUEMWT8Hd=uWL+F=g@mail.gmail.com>
In-Reply-To: <CAH3bfABG+-WQysRQHtFjU6PfNmSnkqqnTsUEMWT8Hd=uWL+F=g@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.99.137]
Content-Type: multipart/alternative; boundary="_000_EF6A204047BD994A860EE26D5F23BF5840561187nkgeml505mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] Working group last call for	draft-ietf-intarea-flow-label-balancing-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: Thu, 11 Jul 2013 07:27:32 -0000

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

SGkgIGFsbA0KDQogICAgICsxIHN1cHBvcnQgZm9yIG1vdmluZyBmb3J3YXJkLg0KDQpCUg0KWXUN
Cg0KRnJvbTogaW50LWFyZWEtYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOmludC1hcmVhLWJvdW5j
ZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBRaW9uZw0KU2VudDogVGh1cnNkYXksIEp1bHkgMTEs
IDIwMTMgMToyMCBQTQ0KVG86IFN1cmVzaCBLcmlzaG5hbg0KQ2M6IEludGVybmV0IEFyZWENClN1
YmplY3Q6IFJlOiBbSW50LWFyZWFdIFdvcmtpbmcgZ3JvdXAgbGFzdCBjYWxsIGZvciBkcmFmdC1p
ZXRmLWludGFyZWEtZmxvdy1sYWJlbC1iYWxhbmNpbmctMDENCg0KRGVhciBhbGwsDQoNCkkgdGhp
bmsgaXQgaXMgcmVhZHkgdG8gbW92ZSBmb3J3YXJkLg0KDQpUaGFua3MNCg0KQmVzdCB3aXNoZXMN
ClFpb25nDQoNCk9uIFRodSwgSnVsIDExLCAyMDEzIGF0IDY6NDkgQU0sIFN1cmVzaCBLcmlzaG5h
biA8c3VyZXNoLmtyaXNobmFuQGVyaWNzc29uLmNvbTxtYWlsdG86c3VyZXNoLmtyaXNobmFuQGVy
aWNzc29uLmNvbT4+IHdyb3RlOg0KSGkgYWxsLA0KICBUaGlzIG1lc3NhZ2Ugc3RhcnRzIGEgdHdv
IHdlZWsgaW50YXJlYSB3b3JraW5nIGdyb3VwIGxhc3QgY2FsbCBvbiB0aGlzDQpkcmFmdCBkZXNj
cmliaW5nIHRoZSB1c2Ugb2YgSVB2NiBGbG93IExhYmVsIGZvciBTZXJ2ZXIgTG9hZCBCYWxhbmNp
bmcgYXMNCmFuIEluZm9ybWF0aW9uYWwgUkZDLiBUaGUgZHJhZnQgaXMgYXZhaWxhYmxlIGF0DQoN
Cmh0dHA6Ly93d3cuaWV0Zi5vcmcvaWQvZHJhZnQtaWV0Zi1pbnRhcmVhLWZsb3ctbGFiZWwtYmFs
YW5jaW5nLTAxLnR4dA0KaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1pbnRh
cmVhLWZsb3ctbGFiZWwtYmFsYW5jaW5nLTAxDQoNClN1YnN0YW50aXZlIGNvbW1lbnRzIGFuZCBz
dGF0ZW1lbnRzIG9mIHN1cHBvcnQvb3Bwb3NpdGlvbiBmb3IgYWR2YW5jaW5nDQp0aGlzIGRvY3Vt
ZW50IHNob3VsZCBiZSBkaXJlY3RlZCB0byB0aGUgbWFpbGluZyBsaXN0LiBFZGl0b3JpYWwNCnN1
Z2dlc3Rpb25zIGNhbiBiZSBzZW50IGRpcmVjdGx5IHRvIHRoZSBhdXRob3JzLiBUaGlzIGxhc3Qg
Y2FsbCB3aWxsDQpjb25jbHVkZSBvbiBKdWx5IDI0LCAyMDEzLg0KDQpSZWdhcmRzLA0KU3VyZXNo
ICYgSnVsaWVuDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fDQpJbnQtYXJlYSBtYWlsaW5nIGxpc3QNCkludC1hcmVhQGlldGYub3JnPG1haWx0bzpJbnQt
YXJlYUBpZXRmLm9yZz4NCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaW50
LWFyZWENCg0KDQo=

--_000_EF6A204047BD994A860EE26D5F23BF5840561187nkgeml505mbxchi_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6eD0idXJuOnNjaGVtYXMtbWljcm9z
b2Z0LWNvbTpvZmZpY2U6ZXhjZWwiIHhtbG5zOm09Imh0dHA6Ly9zY2hlbWFzLm1pY3Jvc29mdC5j
b20vb2ZmaWNlLzIwMDQvMTIvb21tbCIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnL1RSL1JFQy1o
dG1sNDAiPg0KPGhlYWQ+DQo8bWV0YSBodHRwLWVxdWl2PSJDb250ZW50LVR5cGUiIGNvbnRlbnQ9
InRleHQvaHRtbDsgY2hhcnNldD11dGYtOCI+DQo8bWV0YSBuYW1lPSJHZW5lcmF0b3IiIGNvbnRl
bnQ9Ik1pY3Jvc29mdCBXb3JkIDEyIChmaWx0ZXJlZCBtZWRpdW0pIj4NCjxzdHlsZT48IS0tDQov
KiBGb250IERlZmluaXRpb25zICovDQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OuWui+S9kzsN
CglwYW5vc2UtMToyIDEgNiAwIDMgMSAxIDEgMSAxO30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1p
bHk6IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9u
dC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQg
MyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseToiXEDlrovkvZMiOw0KCXBhbm9zZS0x
OjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpUYWhvbWE7
DQoJcGFub3NlLTE6MiAxMSA2IDQgMyA1IDQgNCAyIDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMg
Ki8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBj
bTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZh
bWlseTrlrovkvZM7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJp
b3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6
dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6
OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0Kc3Bhbi5F
bWFpbFN0eWxlMTcNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1p
bHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjojMUY0OTdEO30NCi5Nc29DaHBEZWZh
dWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0K
CXtzaXplOjYxMi4wcHQgNzkyLjBwdDsNCgltYXJnaW46NzIuMHB0IDkwLjBwdCA3Mi4wcHQgOTAu
MHB0O30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHls
ZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQi
IHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+
PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0
IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFk
Pg0KPGJvZHkgbGFuZz0iWkgtQ04iIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBj
bGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNl
cmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkhpJm5ic3A7IGFsbDxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMx
RjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPiZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyAmIzQzOzEgc3VwcG9ydCBmb3IgbW92aW5nIGZvcndhcmQuPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJm
b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29s
b3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+QlI8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5
bGU9ImZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90
Oztjb2xvcjojMUY0OTdEIj5ZdTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZh
bWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFG
NDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5v
bmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGNtIDBjbSAw
Y20iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJm
b250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5z
LXNlcmlmJnF1b3Q7Ij5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJm
b250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5z
LXNlcmlmJnF1b3Q7Ij4gaW50LWFyZWEtYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOmludC1hcmVh
LWJvdW5jZXNAaWV0Zi5vcmddDQo8Yj5PbiBCZWhhbGYgT2YgPC9iPlFpb25nPGJyPg0KPGI+U2Vu
dDo8L2I+IFRodXJzZGF5LCBKdWx5IDExLCAyMDEzIDE6MjAgUE08YnI+DQo8Yj5Ubzo8L2I+IFN1
cmVzaCBLcmlzaG5hbjxicj4NCjxiPkNjOjwvYj4gSW50ZXJuZXQgQXJlYTxicj4NCjxiPlN1Ympl
Y3Q6PC9iPiBSZTogW0ludC1hcmVhXSBXb3JraW5nIGdyb3VwIGxhc3QgY2FsbCBmb3IgZHJhZnQt
aWV0Zi1pbnRhcmVhLWZsb3ctbGFiZWwtYmFsYW5jaW5nLTAxPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4m
bmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IGxhbmc9IkVOLVVTIj5EZWFyIGFsbCw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9
IkVOLVVTIj5JIHRoaW5rIGl0IGlzIHJlYWR5IHRvIG1vdmUgZm9yd2FyZC48bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5n
PSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPlRoYW5rczxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9
IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+QmVzdCB3aXNoZXM8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBs
YW5nPSJFTi1VUyI+UWlvbmcmbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxz
cGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPk9uIFRodSwgSnVsIDExLCAyMDEz
IGF0IDY6NDkgQU0sIFN1cmVzaCBLcmlzaG5hbiAmbHQ7PGEgaHJlZj0ibWFpbHRvOnN1cmVzaC5r
cmlzaG5hbkBlcmljc3Nvbi5jb20iIHRhcmdldD0iX2JsYW5rIj5zdXJlc2gua3Jpc2huYW5AZXJp
Y3Nzb24uY29tPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPkhpIGFsbCw8YnI+DQombmJzcDsgVGhpcyBt
ZXNzYWdlIHN0YXJ0cyBhIHR3byB3ZWVrIGludGFyZWEgd29ya2luZyBncm91cCBsYXN0IGNhbGwg
b24gdGhpczxicj4NCmRyYWZ0IGRlc2NyaWJpbmcgdGhlIHVzZSBvZiBJUHY2IEZsb3cgTGFiZWwg
Zm9yIFNlcnZlciBMb2FkIEJhbGFuY2luZyBhczxicj4NCmFuIEluZm9ybWF0aW9uYWwgUkZDLiBU
aGUgZHJhZnQgaXMgYXZhaWxhYmxlIGF0PGJyPg0KPGJyPg0KPGEgaHJlZj0iaHR0cDovL3d3dy5p
ZXRmLm9yZy9pZC9kcmFmdC1pZXRmLWludGFyZWEtZmxvdy1sYWJlbC1iYWxhbmNpbmctMDEudHh0
IiB0YXJnZXQ9Il9ibGFuayI+aHR0cDovL3d3dy5pZXRmLm9yZy9pZC9kcmFmdC1pZXRmLWludGFy
ZWEtZmxvdy1sYWJlbC1iYWxhbmNpbmctMDEudHh0PC9hPjxicj4NCjxhIGhyZWY9Imh0dHA6Ly90
b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtaW50YXJlYS1mbG93LWxhYmVsLWJhbGFuY2lu
Zy0wMSIgdGFyZ2V0PSJfYmxhbmsiPmh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWll
dGYtaW50YXJlYS1mbG93LWxhYmVsLWJhbGFuY2luZy0wMTwvYT48YnI+DQo8YnI+DQpTdWJzdGFu
dGl2ZSBjb21tZW50cyBhbmQgc3RhdGVtZW50cyBvZiBzdXBwb3J0L29wcG9zaXRpb24gZm9yIGFk
dmFuY2luZzxicj4NCnRoaXMgZG9jdW1lbnQgc2hvdWxkIGJlIGRpcmVjdGVkIHRvIHRoZSBtYWls
aW5nIGxpc3QuIEVkaXRvcmlhbDxicj4NCnN1Z2dlc3Rpb25zIGNhbiBiZSBzZW50IGRpcmVjdGx5
IHRvIHRoZSBhdXRob3JzLiBUaGlzIGxhc3QgY2FsbCB3aWxsPGJyPg0KY29uY2x1ZGUgb24gSnVs
eSAyNCwgMjAxMy48YnI+DQo8YnI+DQpSZWdhcmRzLDxicj4NClN1cmVzaCAmYW1wOyBKdWxpZW48
YnI+DQo8YnI+DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
Xzxicj4NCkludC1hcmVhIG1haWxpbmcgbGlzdDxicj4NCjxhIGhyZWY9Im1haWx0bzpJbnQtYXJl
YUBpZXRmLm9yZyI+SW50LWFyZWFAaWV0Zi5vcmc8L2E+PGJyPg0KPGEgaHJlZj0iaHR0cHM6Ly93
d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pbnQtYXJlYSIgdGFyZ2V0PSJfYmxhbmsiPmh0
dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaW50LWFyZWE8L2E+PG86cD48L286
cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJF
Ti1VUyI+PGJyPg0KPGJyIGNsZWFyPSJhbGwiPg0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9k
aXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_EF6A204047BD994A860EE26D5F23BF5840561187nkgeml505mbxchi_--

From linda.dunbar@huawei.com  Thu Jul 11 07:52:31 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 C28E411E81B5 for <int-area@ietfa.amsl.com>; Thu, 11 Jul 2013 07:52:31 -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 1R2t5wOSLn16 for <int-area@ietfa.amsl.com>; Thu, 11 Jul 2013 07:52:27 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id F1B8B11E81B8 for <int-area@ietf.org>; Thu, 11 Jul 2013 07:52:26 -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 AUX74459; Thu, 11 Jul 2013 14:52:25 +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, 11 Jul 2013 15:51:59 +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; Thu, 11 Jul 2013 15:52:21 +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; Thu, 11 Jul 2013 07:52:09 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: "Fuyu (Eleven)" <eleven.fuyu@huawei.com>, Suresh Krishnan <suresh.krishnan@ericsson.com>
Thread-Topic: [Int-area] Working group last call	for draft-ietf-intarea-flow-label-balancing-01
Thread-Index: AQHOfgh/zBr4YZSrdkOiQCn8iUHZtJlfkEtQ
Date: Thu, 11 Jul 2013 14:52:08 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F645B46E2C@dfweml509-mbx.china.huawei.com>
References: <51DDE4E6.80103@ericsson.com> <CAH3bfABG+-WQysRQHtFjU6PfNmSnkqqnTsUEMWT8Hd=uWL+F=g@mail.gmail.com> <EF6A204047BD994A860EE26D5F23BF5840561187@nkgeml505-mbx.china.huawei.com>
In-Reply-To: <EF6A204047BD994A860EE26D5F23BF5840561187@nkgeml505-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.192.11.162]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F645B46E2Cdfweml509mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] Working group last call	for	draft-ietf-intarea-flow-label-balancing-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: Thu, 11 Jul 2013 14:52:31 -0000

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

U3VwcG9ydC4NCg0KTGluZGENCg0KDQpGcm9tOiBpbnQtYXJlYS1ib3VuY2VzQGlldGYub3JnIFtt
YWlsdG86aW50LWFyZWEtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIFFpb25nDQpTZW50
OiBUaHVyc2RheSwgSnVseSAxMSwgMjAxMyAxOjIwIFBNDQpUbzogU3VyZXNoIEtyaXNobmFuDQpD
YzogSW50ZXJuZXQgQXJlYQ0KU3ViamVjdDogUmU6IFtJbnQtYXJlYV0gV29ya2luZyBncm91cCBs
YXN0IGNhbGwgZm9yIGRyYWZ0LWlldGYtaW50YXJlYS1mbG93LWxhYmVsLWJhbGFuY2luZy0wMQ0K
DQpEZWFyIGFsbCwNCg0KSSB0aGluayBpdCBpcyByZWFkeSB0byBtb3ZlIGZvcndhcmQuDQoNClRo
YW5rcw0KDQpCZXN0IHdpc2hlcw0KUWlvbmcNCg0KT24gVGh1LCBKdWwgMTEsIDIwMTMgYXQgNjo0
OSBBTSwgU3VyZXNoIEtyaXNobmFuIDxzdXJlc2gua3Jpc2huYW5AZXJpY3Nzb24uY29tPG1haWx0
bzpzdXJlc2gua3Jpc2huYW5AZXJpY3Nzb24uY29tPj4gd3JvdGU6DQpIaSBhbGwsDQogIFRoaXMg
bWVzc2FnZSBzdGFydHMgYSB0d28gd2VlayBpbnRhcmVhIHdvcmtpbmcgZ3JvdXAgbGFzdCBjYWxs
IG9uIHRoaXMNCmRyYWZ0IGRlc2NyaWJpbmcgdGhlIHVzZSBvZiBJUHY2IEZsb3cgTGFiZWwgZm9y
IFNlcnZlciBMb2FkIEJhbGFuY2luZyBhcw0KYW4gSW5mb3JtYXRpb25hbCBSRkMuIFRoZSBkcmFm
dCBpcyBhdmFpbGFibGUgYXQNCg0KaHR0cDovL3d3dy5pZXRmLm9yZy9pZC9kcmFmdC1pZXRmLWlu
dGFyZWEtZmxvdy1sYWJlbC1iYWxhbmNpbmctMDEudHh0DQpodHRwOi8vdG9vbHMuaWV0Zi5vcmcv
aHRtbC9kcmFmdC1pZXRmLWludGFyZWEtZmxvdy1sYWJlbC1iYWxhbmNpbmctMDENCg0KU3Vic3Rh
bnRpdmUgY29tbWVudHMgYW5kIHN0YXRlbWVudHMgb2Ygc3VwcG9ydC9vcHBvc2l0aW9uIGZvciBh
ZHZhbmNpbmcNCnRoaXMgZG9jdW1lbnQgc2hvdWxkIGJlIGRpcmVjdGVkIHRvIHRoZSBtYWlsaW5n
IGxpc3QuIEVkaXRvcmlhbA0Kc3VnZ2VzdGlvbnMgY2FuIGJlIHNlbnQgZGlyZWN0bHkgdG8gdGhl
IGF1dGhvcnMuIFRoaXMgbGFzdCBjYWxsIHdpbGwNCmNvbmNsdWRlIG9uIEp1bHkgMjQsIDIwMTMu
DQoNClJlZ2FyZHMsDQpTdXJlc2ggJiBKdWxpZW4NCg0KX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX18NCkludC1hcmVhIG1haWxpbmcgbGlzdA0KSW50LWFyZWFA
aWV0Zi5vcmc8bWFpbHRvOkludC1hcmVhQGlldGYub3JnPg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcv
bWFpbG1hbi9saXN0aW5mby9pbnQtYXJlYQ0KDQoNCg==

--_000_4A95BA014132FF49AE685FAB4B9F17F645B46E2Cdfweml509mbxchi_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6eD0idXJuOnNjaGVtYXMtbWljcm9z
b2Z0LWNvbTpvZmZpY2U6ZXhjZWwiIHhtbG5zOm09Imh0dHA6Ly9zY2hlbWFzLm1pY3Jvc29mdC5j
b20vb2ZmaWNlLzIwMDQvMTIvb21tbCIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnL1RSL1JFQy1o
dG1sNDAiPg0KPGhlYWQ+DQo8bWV0YSBodHRwLWVxdWl2PSJDb250ZW50LVR5cGUiIGNvbnRlbnQ9
InRleHQvaHRtbDsgY2hhcnNldD11dGYtOCI+DQo8bWV0YSBuYW1lPSJHZW5lcmF0b3IiIGNvbnRl
bnQ9Ik1pY3Jvc29mdCBXb3JkIDEyIChmaWx0ZXJlZCBtZWRpdW0pIj4NCjxzdHlsZT48IS0tDQov
KiBGb250IERlZmluaXRpb25zICovDQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OuWui+S9kzsN
CglwYW5vc2UtMToyIDEgNiAwIDMgMSAxIDEgMSAxO30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1p
bHk6IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9u
dC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQg
MyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpUYWhvbWE7DQoJcGFub3NlLTE6MiAx
MSA2IDQgMyA1IDQgNCAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseToiXEDlrovkvZMi
Ow0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMg
Ki8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBp
bjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZh
bWlseTrlrovkvZM7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJp
b3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6
dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6
OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0Kc3Bhbi5F
bWFpbFN0eWxlMTcNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJZm9udC1mYW1pbHk6IkNh
bGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjojMUY0OTdEO30NCnNwYW4uRW1haWxTdHlsZTE4
DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJp
Iiwic2Fucy1zZXJpZiI7DQoJY29sb3I6IzFGNDk3RDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28t
c3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6MTAuMHB0O30NCkBwYWdlIFdvcmRT
ZWN0aW9uMQ0KCXtzaXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4waW4gMS4yNWluIDEuMGlu
IDEuMjVpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwv
c3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJl
ZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNv
IDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0i
ZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwv
aGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIj4NCjxk
aXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90
O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+U3VwcG9ydC4NCjxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90
Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVv
dDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+TGlu
ZGENCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1
b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bh
bj48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEu
NXB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNC4wcHQiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0I1
QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluIj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1Rh
aG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZx
dW90O3NhbnMtc2VyaWYmcXVvdDsiPiBpbnQtYXJlYS1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86
aW50LWFyZWEtYm91bmNlc0BpZXRmLm9yZ10NCjxiPk9uIEJlaGFsZiBPZiA8L2I+UWlvbmc8YnI+
DQo8Yj5TZW50OjwvYj4gVGh1cnNkYXksIEp1bHkgMTEsIDIwMTMgMToyMCBQTTxicj4NCjxiPlRv
OjwvYj4gU3VyZXNoIEtyaXNobmFuPGJyPg0KPGI+Q2M6PC9iPiBJbnRlcm5ldCBBcmVhPGJyPg0K
PGI+U3ViamVjdDo8L2I+IFJlOiBbSW50LWFyZWFdIFdvcmtpbmcgZ3JvdXAgbGFzdCBjYWxsIGZv
ciBkcmFmdC1pZXRmLWludGFyZWEtZmxvdy1sYWJlbC1iYWxhbmNpbmctMDE8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkRlYXIgYWxsLDxvOnA+PC9vOnA+PC9w
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SSB0aGluayBpdCBpcyByZWFkeSB0byBt
b3ZlIGZvcndhcmQuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPlRoYW5rczxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj5CZXN0IHdpc2hlczxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+UWlvbmcmbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24gVGh1
LCBKdWwgMTEsIDIwMTMgYXQgNjo0OSBBTSwgU3VyZXNoIEtyaXNobmFuICZsdDs8YSBocmVmPSJt
YWlsdG86c3VyZXNoLmtyaXNobmFuQGVyaWNzc29uLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPnN1cmVz
aC5rcmlzaG5hbkBlcmljc3Nvbi5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPkhpIGFsbCw8YnI+DQombmJzcDsgVGhpcyBtZXNzYWdlIHN0YXJ0
cyBhIHR3byB3ZWVrIGludGFyZWEgd29ya2luZyBncm91cCBsYXN0IGNhbGwgb24gdGhpczxicj4N
CmRyYWZ0IGRlc2NyaWJpbmcgdGhlIHVzZSBvZiBJUHY2IEZsb3cgTGFiZWwgZm9yIFNlcnZlciBM
b2FkIEJhbGFuY2luZyBhczxicj4NCmFuIEluZm9ybWF0aW9uYWwgUkZDLiBUaGUgZHJhZnQgaXMg
YXZhaWxhYmxlIGF0PGJyPg0KPGJyPg0KPGEgaHJlZj0iaHR0cDovL3d3dy5pZXRmLm9yZy9pZC9k
cmFmdC1pZXRmLWludGFyZWEtZmxvdy1sYWJlbC1iYWxhbmNpbmctMDEudHh0IiB0YXJnZXQ9Il9i
bGFuayI+aHR0cDovL3d3dy5pZXRmLm9yZy9pZC9kcmFmdC1pZXRmLWludGFyZWEtZmxvdy1sYWJl
bC1iYWxhbmNpbmctMDEudHh0PC9hPjxicj4NCjxhIGhyZWY9Imh0dHA6Ly90b29scy5pZXRmLm9y
Zy9odG1sL2RyYWZ0LWlldGYtaW50YXJlYS1mbG93LWxhYmVsLWJhbGFuY2luZy0wMSIgdGFyZ2V0
PSJfYmxhbmsiPmh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtaW50YXJlYS1m
bG93LWxhYmVsLWJhbGFuY2luZy0wMTwvYT48YnI+DQo8YnI+DQpTdWJzdGFudGl2ZSBjb21tZW50
cyBhbmQgc3RhdGVtZW50cyBvZiBzdXBwb3J0L29wcG9zaXRpb24gZm9yIGFkdmFuY2luZzxicj4N
CnRoaXMgZG9jdW1lbnQgc2hvdWxkIGJlIGRpcmVjdGVkIHRvIHRoZSBtYWlsaW5nIGxpc3QuIEVk
aXRvcmlhbDxicj4NCnN1Z2dlc3Rpb25zIGNhbiBiZSBzZW50IGRpcmVjdGx5IHRvIHRoZSBhdXRo
b3JzLiBUaGlzIGxhc3QgY2FsbCB3aWxsPGJyPg0KY29uY2x1ZGUgb24gSnVseSAyNCwgMjAxMy48
YnI+DQo8YnI+DQpSZWdhcmRzLDxicj4NClN1cmVzaCAmYW1wOyBKdWxpZW48YnI+DQo8YnI+DQpf
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxicj4NCkludC1h
cmVhIG1haWxpbmcgbGlzdDxicj4NCjxhIGhyZWY9Im1haWx0bzpJbnQtYXJlYUBpZXRmLm9yZyI+
SW50LWFyZWFAaWV0Zi5vcmc8L2E+PGJyPg0KPGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcv
bWFpbG1hbi9saXN0aW5mby9pbnQtYXJlYSIgdGFyZ2V0PSJfYmxhbmsiPmh0dHBzOi8vd3d3Lmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8vaW50LWFyZWE8L2E+PG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxicj4NCjxiciBjbGVhcj0iYWxsIj4NCjxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+
DQo=

--_000_4A95BA014132FF49AE685FAB4B9F17F645B46E2Cdfweml509mbxchi_--

From brian@innovationslab.net  Thu Jul 11 10:22:57 2013
Return-Path: <brian@innovationslab.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 29AAE21F9F37 for <int-area@ietfa.amsl.com>; Thu, 11 Jul 2013 10:22:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.779
X-Spam-Level: 
X-Spam-Status: No, score=-102.779 tagged_above=-999 required=5 tests=[AWL=-0.180, 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 018jeDKxd7ER for <int-area@ietfa.amsl.com>; Thu, 11 Jul 2013 10:22:46 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id B13FC21F9C70 for <int-area@ietf.org>; Thu, 11 Jul 2013 10:22:45 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 68BC5880F0; Thu, 11 Jul 2013 10:22:45 -0700 (PDT)
Received: from 102525194.rudm1.ra.johnshopkins.edu (addr16212925014.ippl.jhmi.edu [162.129.250.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 27B3C130003; Thu, 11 Jul 2013 10:22:45 -0700 (PDT)
Message-ID: <51DEE9E5.5090202@innovationslab.net>
Date: Thu, 11 Jul 2013 13:22:45 -0400
From: Brian Haberman <brian@innovationslab.net>
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: "int-area@ietf.org" <int-area@ietf.org>,  "int-chairs@tools.ietf.org" <int-chairs@tools.ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Int-area] INT ADs' office hours
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "int-ads@tools.ietf.org" <int-ads@tools.ietf.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: Thu, 11 Jul 2013 17:22:57 -0000

All,
      As in the previous few meetings, the INT ADs will be holding 
"office hours" in Berlin.  We will be available on Monday from 1300 to 
1500 in the yet-to-be-identified IESG breakout room.  Feel free to stop 
by and ask questions or chat about any concerns/ideas you have about an 
INT WG or the area as a whole.

Regards,
Brian & Ted

From linda.dunbar@huawei.com  Thu Jul 11 14:49:59 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 A967C11E812F for <int-area@ietfa.amsl.com>; Thu, 11 Jul 2013 14:49:59 -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 J5xxyVFY8+Ez for <int-area@ietfa.amsl.com>; Thu, 11 Jul 2013 14:49:54 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id C00BC11E8129 for <int-area@ietf.org>; Thu, 11 Jul 2013 14:49:53 -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 AUX93926; Thu, 11 Jul 2013 21:49:51 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 11 Jul 2013 22:49:25 +0100
Received: from DFWEML407-HUB.china.huawei.com (10.193.5.132) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 11 Jul 2013 22:49:47 +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, 11 Jul 2013 14:49:42 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: Internet Area <int-area@ietf.org>, Suresh Krishnan <suresh.krishnan@ericsson.com>
Thread-Topic: New Version Notification for draft-nachum-sarp-05.txt
Thread-Index: AQHOfnMVFF8CrgJjSkGXOxQqOr265plf/aiw
Date: Thu, 11 Jul 2013 21:49:40 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F645B472B6@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.192.11.162]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [Int-area] FW: New Version Notification for draft-nachum-sarp-05.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, 11 Jul 2013 21:49:59 -0000

ZHJhZnQtbmFjaHVtLXNhcnAgaGFzIGJlZW4gcHJlc2VudGVkIGF0IEludGVyQXJlYSBXRyAzIHRp
bWVzLiBBcyB0aGUgbW90aXZhdGlvbiBmb3IgdGhlIHNjaGVtZSB3YXNuJ3QgY2xlYXJseSBzdGF0
ZWQsIG1hbnkgcGVvcGxlIGluIHRoZSBXRyBoYXZlIGJlZW4gZGViYXRpbmcgb24gdGhlIG5lY2Vz
c2l0eSBvZiB0aGUgc2NoZW1lIGR1cmluZyB0aGUgbWVldGluZyBhbmQgb3ZlciB0aGUgbWFpbGlu
ZyBsaXN0LiANCg0KV2UgdXBkYXRlZCB0aGUgZHJhZnQgdG8gYWRkcmVzcyB0aGUgaXNzdWVzIHRo
YXQgV0cgaGF2ZSBicm91Z2h0IHVwOiBodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0
cy9kcmFmdC1uYWNodW0tc2FycC0wNS50eHQNCg0KDQpUaGUgcHJvcG9zZWQgc2NoZW1lIGlzIG1v
cmUgbGlrZSBwcm94eSBnYXRld2F5IHRvIGFkZHJlc3MgdGhlIGZvbGxvd2luZyBpc3N1ZXMgZmFj
aW5nIERhdGEgQ2VudGVycyB3aXRoIGxhcmdlIG51bWJlciB2aXJ0dWFsIG1hY2hpbmVzIHRoYXQg
ZG9uJ3QgaGF2ZSBmaXhlZCBhc3NvY2lhdGlvbiB3aXRoIGFjY2VzcyBzd2l0Y2hlczoNCg0KMSkJ
aW50ZXJtZWRpYXRlIHN3aXRjaGVz4oCZIE1BQyBhZGRyZXNzIHRhYmxlIChGREIpIGV4cGxvc2lv
bjoNCldoZW4gaG9zdHMgaW4gYSBWTEFOIChvciBzdWJuZXQpIHNwYW4gYWNyb3NzIG1hbnkgbG9j
YXRpb25zIChvciBBY2Nlc3MgU3dpdGNoZXMpIGFuZCBlYWNoIEFjY2VzcyBTd2l0Y2ggaGFzIG1h
bnkgVkxBTnMgZW5hYmxlZCwgdGhlIEFjY2VzcyBzd2l0Y2hlcyBhcmUgZXhwb3NlZCB0byBhbGwg
TUFDIGFkZHJlc3NlcyBhbW9uZyBhbGwgdGhlIFZMQU5zIGVuYWJsZWQuIA0KRm9yIGV4YW1wbGUs
IGZvciBhbiBBY2Nlc3Mgc3dpdGNoIHdpdGggNDAgcGh5c2ljYWwgc2VydmVycyBhdHRhY2hlZCwg
YW5kIGVhY2ggc2VydmVyIGhhcyAxMDAgVk1zLCB0aGVyZSBhcmUgNDAwMCBob3N0cyB1bmRlciB0
aGUgQWNjZXNzIFN3aXRjaC4gSWYgaXQgaXMgdHJ1bHkgdGhhdCBob3N0cy9WTXMgY2FuIGJlIG1v
dmVkIGFueXdoZXJlLCB0aGUgd29yc3QgY2FzZSBmb3IgdGhlIEFjY2VzcyBTd2l0Y2ggaXMgd2hl
biBhbGwgdGhvc2UgNDAwMCBWTXMgYmVsb25nIHRvIGRpZmZlcmVudCBWTEFOcywgaS5lLiB0aGUg
YWNjZXNzIHN3aXRjaCBoYXMgNDAwMCBWTEFOcyBlbmFibGVkLiBJZiBlYWNoIG9mIFZMQU5zIGhh
cyAyMDAgaG9zdHMsIHRoaXMgYWNjZXNzIHN3aXRjaOKAmXMgTUFDIHRhYmxlIHBvdGVudGlhbGx5
IGhhcyAyMDAqNDAwMCA9IDgwMCwwMDAgZW50cmllcy4gDQpBbHRob3VnaCBhYm92ZSBjYXNlIGlz
IHJhcmUsIGJ1dCBjb3VsZCBoYXBwZW4gcmVnYXJkbGVzcyBJUHY0IG9yIElQdjYuIA0KVGhpcyBp
cyB3b3JzZSB0aGFuIHdoYXQgdG9kYXnigJlzIEwyLzMgR2F0ZXdheSBoYXMgdG8gZmFjZS4gSW4g
dG9kYXnigJlzIGVudmlyb25tZW50IHdoZXJlIGVhY2ggc3VibmV0IGlzIGxpbWl0ZWQgdG8gYSBm
ZXcgYWNjZXNzIHN3aXRjaGVzLCBvbmx5IHRoZSBsaW1pdGVkIHBvcnRzIGZhY2luZyB0aG9zZSBh
Y2Nlc3Mgc3dpdGNoZXMgYXJlIGV4cG9zZWQgdG8gTUFDIGFkZHJlc3Mgb2YgdGhlIHN1Ym5ldC4g
DQoNCjIpCXRoZSBBUlAvTkQgcHJvY2Vzc2luZyBsb2FkIGltcGFjdCBvbiB0aGUgTDIvTDMgYm91
bmRhcnkgcm91dGVyczsgDQpBbGwgVk1zIHBlcmlvZGljYWxseSBzZW5kIE5EcyB0byB0aGVpciBj
b3JyZXNwb25kaW5nIEdhdGV3YXkgbm9kZXMgdG8gZ2V0IGdhdGV3YXkgbm9kZXPigJkgTUFDIGFk
ZHJlc3Nlcy4gV2hlbiB0aGUgY29tYmluZWQgVk1zIGFjcm9zcyBhbGwgdGhlIFZMQU5zIGFyZSBs
YXJnZSwgcHJvY2Vzc2luZyB0aGUgcmVzcG9uc2VzIHRvIHRoZSBORCByZXF1ZXN0cyBmcm9tIHRo
b3NlIFZNcyBjYW4gZWFzaWx5IGtub2NrIGRvd24gdGhlIGdhdGV3YXnigJlzIENQVSB1dGlsaXph
dGlvbi4gDQpBIEwyL0wzIGJvdW5kYXJ5IHJvdXRlciBjb3VsZCBiZSBoaXQgd2l0aCBBUlAvTkQg
dHdpY2Ugd2hlbiB0aGUgb3JpZ2luYXRpbmcgYW5kIGRlc3RpbmF0aW9uIHN0YXRpb25zIGFyZSBp
biBkaWZmZXJlbnQgc3VibmV0cyBhdHRhY2hlZCB0byB0aGUgc2FtZSByb3V0ZXIgYW5kIHdoZW4g
dGhvc2UgaG9zdHMgZG9u4oCZdCBjb21tdW5pY2F0ZSB3aXRoIGV4dGVybmFsIHBlZXJzIHZlcnkg
b2Z0ZW4uIFRoZSBmaXJzdCBoaXQgaXMgd2hlbiB0aGUgb3JpZ2luYXRpbmcgc3RhdGlvbiBpbiBz
dWJuZXQtQSBpbml0aWF0ZXMgQVJQL05EIHJlcXVlc3QgdG8gdGhlIEwyL0wzIGJvdW5kYXJ5IHJv
dXRlciBpZiB0aGUgcm91dGVy4oCZcyBNQUMgaXMgbm90IGluIHRoZSBob3N04oCZcyBjYWNoZTsg
YW5kIHRoZSBzZWNvbmQgaGl0IGlzIHdoZW4gdGhlIEwyL0wzIGJvdW5kYXJ5IHJvdXRlciBpbml0
aWF0ZXMgQVJQL05EIHJlcXVlc3RzIHRvIHRoZSB0YXJnZXQgaW4gc3VibmV0LUIgaWYgdGhlIHRh
cmdldCBpcyBub3QgaW4gcm91dGVy4oCZcyBBUlAvTkQgY2FjaGUuDQoNCjMpCUluIElQdjQsIGV2
ZXJ5IGVuZCBzdGF0aW9uIGluIGEgc3VibmV0IHJlY2VpdmVzIEFSUCBicm9hZGNhc3QgbWVzc2Fn
ZXMgZnJvbSBhbGwgb3RoZXIgZW5kIHN0YXRpb25zIGluIHRoZSBzdWJuZXQuIElQdjYgTkQgaGFz
IGVsaW1pbmF0ZWQgdGhpcyBpc3N1ZSBieSB1c2luZyBtdWx0aWNhc3QuICANCkhvd2V2ZXIsIG1v
c3QgZGV2aWNlcyBoYXZlIGxpbWl0ZWQgbnVtYmVyIG9mIE11bHRpY2FzdCBmaWx0ZXJpbmcuIE9u
Y2UgdGhlIG51bWJlciBvZiBtdWx0aWNhc3QgYWRkcmVzc2VzIGdvZXMgYmV5b25kIHRoZSBtdWx0
aWNhc3QgZmlsdGVyIGxpbWl0LCB0aGUgbXVsdGljYXN0IGFkZHJlc3NlcyBoYXZlIHRvIGJlIHBy
b2Nlc3NlZCBieSBkZXZpY2Vz4oCZIENQVSAoaS5lLiB0aGUgc2xvdyBwYXRoKS4gDQpJdCBpcyBs
ZXNzIG9mIGFuIGlzc3VlIGluIERDIHdpdGhvdXQgVk0gbW9iaWxpdHkgYmVjYXVzZSBlYWNoIHBv
cnQgaXMgb25seSBkZWRpY2F0ZWQgdG8gb25lIChvciBhIGZldyBudW1iZXIgb2YpIFZMQU5zLiBT
byB0aGUgbnVtYmVyIG9mIG11bHRpY2FzdCBhZGRyZXNzZXMgaGl0dGluZyBlYWNoIHBvcnQgaXMg
bXVjaCBsZXNzLiANCg0KNCkJdGhlIEFSUC9ORCBtZXNzYWdlcyBiZWluZyBmbG9vZGVkIHRvIG1h
bnkgcGh5c2ljYWwgbGluayBzZWdtZW50cyB3aGljaCBjYW4gcmVkdWNlIGJhbmR3aWR0aCB1dGls
aXphdGlvbiBmb3IgdXNlciB0cmFmZmljOyANCg0KQVJQL05EIGZsb29kaW5nIGlzIHByb2JhYmx5
IGFuIGluc2lnbmlmaWNhbnQgaXNzdWUgaW4gdG9kYXnigJlzIGRhdGEgY2VudGVyIGJlY2F1c2Ug
dGhlIG1ham9yaXR5IG9mIGRhdGEgY2VudGVyIHNlcnZlcnMgYXJlIG1vdmluZyB0b3dhcmRzIDFH
IG9yIDEwRyBwb3J0cy4gVGhlIGJhbmR3aWR0aCB0YWtlbiBieSBBUlAvTkQsIGV2ZW4gd2l0aCB0
aGVtIGZsb29kZWQgdG8gYWxsIHBoeXNpY2FsIGxpbmtzLCBiZWNvbWVzIG5lZ2xpZ2libGUgY29t
cGFyaW5nIHdpdGggdGhlIGxpbmsgYmFuZHdpZHRoLiBJbiBhZGRpdGlvbiwgdGhlIElHTVAvTUxE
IHNub29waW5nIFtSRkM0NTQxXSBjYW4gZnVydGhlciByZWR1Y2UgdGhlIE5EIG11bHRpY2FzdCB0
cmFmZmljIHRvIHNvbWUgcGh5c2ljYWwgbGluayBzZWdtZW50cy4NCg0KDQpIb3BlIHRob3NlIHBv
aW50cyBhcmUgbW9yZSBjbGVhci4gDQoNCkxpbmRhIA0KDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2Fn
ZS0tLS0tDQpGcm9tOiBpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmcgW21haWx0bzppbnRlcm5ldC1k
cmFmdHNAaWV0Zi5vcmddIA0KU2VudDogVGh1cnNkYXksIEp1bHkgMTEsIDIwMTMgMzoxMyBQTQ0K
VG86IExpbmRhIER1bmJhcjsgWW91dmFsIE5hY2h1bTsgSWxhbiBZZXJ1c2hhbG1pOyBUYWwgTWl6
cmFoaQ0KU3ViamVjdDogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC1uYWNodW0t
c2FycC0wNS50eHQNCg0KDQpBIG5ldyB2ZXJzaW9uIG9mIEktRCwgZHJhZnQtbmFjaHVtLXNhcnAt
MDUudHh0DQpoYXMgYmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5IFlvdXZhbCBOYWNodW0g
YW5kIHBvc3RlZCB0byB0aGUNCklFVEYgcmVwb3NpdG9yeS4NCg0KRmlsZW5hbWU6CSBkcmFmdC1u
YWNodW0tc2FycA0KUmV2aXNpb246CSAwNQ0KVGl0bGU6CQkgU2NhbGluZyB0aGUgQWRkcmVzcyBS
ZXNvbHV0aW9uIFByb3RvY29sIGZvciBMYXJnZSBEYXRhIENlbnRlcnMgKFNBUlApDQpDcmVhdGlv
biBkYXRlOgkgMjAxMy0wNy0xMQ0KR3JvdXA6CQkgSW5kaXZpZHVhbCBTdWJtaXNzaW9uDQpOdW1i
ZXIgb2YgcGFnZXM6IDIwDQpVUkw6ICAgICAgICAgICAgIGh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50
ZXJuZXQtZHJhZnRzL2RyYWZ0LW5hY2h1bS1zYXJwLTA1LnR4dA0KU3RhdHVzOiAgICAgICAgICBo
dHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LW5hY2h1bS1zYXJwDQpIdG1saXpl
ZDogICAgICAgIGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LW5hY2h1bS1zYXJwLTA1
DQpEaWZmOiAgICAgICAgICAgIGh0dHA6Ly93d3cuaWV0Zi5vcmcvcmZjZGlmZj91cmwyPWRyYWZ0
LW5hY2h1bS1zYXJwLTA1DQoNCkFic3RyYWN0Og0KICAgVGhpcyBkb2N1bWVudCBpbnRyb2R1Y2Vz
IFNBUlAsIGFuIGFyY2hpdGVjdHVyZSB0aGF0IHVzZXMgcHJveHkNCiAgIGdhdGV3YXlzIGFuZCBh
bGxvd3MgdG8gc2NhbGUgZGF0YSBjZW50ZXIgbmV0d29ya3MuIFNBUlAgaXMgYmFzZWQgb24NCiAg
IGZhc3QgcHJveGllcyB0aGF0IHNpZ25pZmljYW50bHkgcmVkdWNlIHN3aXRjaGVzJyBGREIgKE1B
QyB0YWJsZSkNCiAgIHNpemVzIGFuZCBBUlAvTkQgaW1wYWN0IG9uIG5ldHdvcmsgZWxlbWVudHMg
aW4gYW4gZW52aXJvbm1lbnQgdGhhdA0KICAgaG9zdHMgd2l0aGluIG9uZSBzdWJuZXQgKG9yIFZM
QU4pIGNhbiBzcHJlYWQgb3ZlciB2YXJpb3VzIGxvY2F0aW9ucy4NCiAgIFNBUlAgc3VwcG9ydHMg
c21vb3RoIGFuZCBmYXN0IHZpcnR1YWwgbWFjaGluZSAoVk0pIG1vYmlsaXR5IHdpdGhvdXQNCiAg
IGFueSBtb2RpZmljYXRpb24gdG8gdGhlIFZNLCB3aGlsZSBrZWVwaW5nIHRoZSBjb25uZWN0aW9u
IHVwIGFuZA0KICAgcnVubmluZyBlZmZpY2llbnRseS4gIFNBUlAgaXMgdGFyZ2V0ZWQgZm9yIG1h
c3NpdmUgc2NhbGluZyBkYXRhDQogICBjZW50ZXJzIHdpdGggYSBzaWduaWZpY2FudCBudW1iZXIg
b2YgVk1zIHRoYXQgY2FuIG1vdmUgYWNyb3NzIHZhcmlvdXMNCiAgIHBoeXNpY2FsIGxvY2F0aW9u
cy4NCg0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0KDQoNClRoZSBJRVRGIFNlY3JldGFyaWF0
DQoNCg==

From Ted.Lemon@nominum.com  Thu Jul 11 15:37:52 2013
Return-Path: <Ted.Lemon@nominum.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 22F7B11E8130 for <int-area@ietfa.amsl.com>; Thu, 11 Jul 2013 15:37:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.589
X-Spam-Level: 
X-Spam-Status: No, score=-106.589 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OnLmnKx0a2KC for <int-area@ietfa.amsl.com>; Thu, 11 Jul 2013 15:37:45 -0700 (PDT)
Received: from exprod7og107.obsmtp.com (exprod7og107.obsmtp.com [64.18.2.167]) by ietfa.amsl.com (Postfix) with ESMTP id A303D21F9FCA for <int-area@ietf.org>; Thu, 11 Jul 2013 15:37:35 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP ID DSNKUd8zr5+33rWODJJqxZv4unpI4xfm2yb7@postini.com; Thu, 11 Jul 2013 15:37:41 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id D95121B8075 for <int-area@ietf.org>; Thu, 11 Jul 2013 15:37:34 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 2D896190052; Thu, 11 Jul 2013 15:37:34 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Thu, 11 Jul 2013 15:37:34 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Linda Dunbar <linda.dunbar@huawei.com>
Thread-Topic: [Int-area] FW: New Version Notification for draft-nachum-sarp-05.txt
Thread-Index: AQHOfnMVFF8CrgJjSkGXOxQqOr265plf/aiwgACJQoA=
Date: Thu, 11 Jul 2013 22:37:33 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077520C0F0@mbx-01.win.nominum.com>
References: <4A95BA014132FF49AE685FAB4B9F17F645B472B6@dfweml509-mbx.china.huawei.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F645B472B6@dfweml509-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <9BE3839E186B754AB3A552ABF5BF3915@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-nachum-sarp-05.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, 11 Jul 2013 22:37:52 -0000

How does this relate to the work being done in the trill and nvo3 working g=
roups?


From linda.dunbar@huawei.com  Thu Jul 11 15:48: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 7588611E81B9 for <int-area@ietfa.amsl.com>; Thu, 11 Jul 2013 15:48:40 -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 gpgijWmR+gTF for <int-area@ietfa.amsl.com>; Thu, 11 Jul 2013 15:48:35 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id C4E2911E8139 for <int-area@ietf.org>; Thu, 11 Jul 2013 15:48:34 -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 AUX96155; Thu, 11 Jul 2013 22:48:32 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 11 Jul 2013 23:48:06 +0100
Received: from DFWEML407-HUB.china.huawei.com (10.193.5.132) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 11 Jul 2013 23:48:28 +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, 11 Jul 2013 15:48:24 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: [Int-area] FW: New Version Notification for draft-nachum-sarp-05.txt
Thread-Index: AQHOfnMVFF8CrgJjSkGXOxQqOr265plf/aiwgACJQoD//4rqAA==
Date: Thu, 11 Jul 2013 22:48:24 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F645B473B1@dfweml509-mbx.china.huawei.com>
References: <4A95BA014132FF49AE685FAB4B9F17F645B472B6@dfweml509-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B63077520C0F0@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077520C0F0@mbx-01.win.nominum.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.192.11.162]
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>
Subject: Re: [Int-area] FW: New Version Notification for draft-nachum-sarp-05.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, 11 Jul 2013 22:48:40 -0000

Ted,=20

Glad you ask this question.=20

TRILL and NVO3 provides an overlay mechanism so that the hosts (or VMs) add=
resses are hidden from the switches in the core.=20

However, all the overlay edge switches are still exposed to all the hosts a=
ddresses on the VLANs that are enabled on the edge. If the number of VMs at=
tached to an edge is very small (e.g. overlay edge in the server), then the=
 number of VLANs enabled on the edge is limited. In this scenario, there co=
uld be very large number of edges for large DC, which sometimes makes IGP c=
hallenging.=20

For a typical Access switch (Top of Rack)  with 40 physical servers attache=
d, where each server has 100 VMs, there are 4000 hosts under the Access Swi=
tch. If indeed hosts/VMs can be moved anywhere, the worst case for the Acce=
ss Switch is when all those 4000 VMs belong to different VLANs, i.e. the ac=
cess switch has 4000 VLANs enabled. If each VLAN has 200 hosts, this access=
 switch's MAC table potentially has 200*4000 =3D 800,000 entries.=20
It is important to note that the example above is relevant regardless of wh=
ether IPv4 or IPv6 are used.=20
The example illustrates a scenario that is worse than what today's L2/3 Gat=
eway has to face. In today's environment where each subnet is limited to a =
few access switches, the number of MAC addresses the gateway has to learn i=
s of a significantly smaller scale.


Linda=20

> -----Original Message-----
> From: Ted Lemon [mailto:Ted.Lemon@nominum.com]
> Sent: Thursday, July 11, 2013 5:38 PM
> To: Linda Dunbar
> Cc: Internet Area; Suresh Krishnan
> Subject: Re: [Int-area] FW: New Version Notification for draft-nachum-
> sarp-05.txt
>=20
> How does this relate to the work being done in the trill and nvo3
> working groups?


From Ted.Lemon@nominum.com  Thu Jul 11 16:02:52 2013
Return-Path: <Ted.Lemon@nominum.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 2FE4911E8136 for <int-area@ietfa.amsl.com>; Thu, 11 Jul 2013 16:02:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.589
X-Spam-Level: 
X-Spam-Status: No, score=-106.589 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D3mzuMKdzoRH for <int-area@ietfa.amsl.com>; Thu, 11 Jul 2013 16:02:45 -0700 (PDT)
Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155]) by ietfa.amsl.com (Postfix) with ESMTP id 6F00211E8114 for <int-area@ietf.org>; Thu, 11 Jul 2013 16:02:45 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob101.postini.com ([64.18.6.12]) with SMTP ID DSNKUd85lRRYBeho+bgXeeHHQ/H9+D++YdwH@postini.com; Thu, 11 Jul 2013 16:02:45 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 0452E1B81B3 for <int-area@ietf.org>; Thu, 11 Jul 2013 16:02:45 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id EE508190052; Thu, 11 Jul 2013 16:02:44 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Thu, 11 Jul 2013 16:02:45 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Linda Dunbar <linda.dunbar@huawei.com>
Thread-Topic: [Int-area] FW: New Version Notification for draft-nachum-sarp-05.txt
Thread-Index: AQHOfnMVFF8CrgJjSkGXOxQqOr265plf/aiwgACJQoD//4rqAIAAfB6A
Date: Thu, 11 Jul 2013 23:02:44 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077520C2DC@mbx-01.win.nominum.com>
References: <4A95BA014132FF49AE685FAB4B9F17F645B472B6@dfweml509-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B63077520C0F0@mbx-01.win.nominum.com> <4A95BA014132FF49AE685FAB4B9F17F645B473B1@dfweml509-mbx.china.huawei.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F645B473B1@dfweml509-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <D9873A9403DF6C4AA86A4BA29F64AFE3@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-nachum-sarp-05.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, 11 Jul 2013 23:02:52 -0000

On Jul 11, 2013, at 6:48 PM, Linda Dunbar <linda.dunbar@huawei.com> wrote:
> TRILL and NVO3 provides an overlay mechanism so that the hosts (or VMs) a=
ddresses are hidden from the switches in the core.=20

> However, all the overlay edge switches are still exposed to all the hosts=
 addresses on the VLANs that are enabled on the edge. If the number of VMs =
attached to an edge is very small (e.g. overlay edge in the server), then t=
he number of VLANs enabled on the edge is limited. In this scenario, there =
could be very large number of edges for large DC, which sometimes makes IGP=
 challenging.=20

True.   However, they do have various strategies for addressing this proble=
m, and I was wondering how you think your proposal fits in.   For example, =
the trill working group recently submitted a document for publication that =
addresses the issue of small, scattered virtual links with frequently migra=
ting VMs in a very large campus using a directory service.   I reviewed an =
nvo3 problem statement document for the telechat two weeks ago that talked =
about the same issue as well.


From linda.dunbar@huawei.com  Fri Jul 12 08:29:09 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 44B7011E814C for <int-area@ietfa.amsl.com>; Fri, 12 Jul 2013 08:29:09 -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 pMMSnjdcUsTS for <int-area@ietfa.amsl.com>; Fri, 12 Jul 2013 08:29:03 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0B70111E815A for <int-area@ietf.org>; Fri, 12 Jul 2013 08:28:49 -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 AUY63866; Fri, 12 Jul 2013 15:28:47 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 12 Jul 2013 16:28:19 +0100
Received: from DFWEML407-HUB.china.huawei.com (10.193.5.132) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 12 Jul 2013 16:28:43 +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; Fri, 12 Jul 2013 08:28:37 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: [Int-area] FW: New Version Notification for draft-nachum-sarp-05.txt
Thread-Index: AQHOfnMVFF8CrgJjSkGXOxQqOr265plf/aiwgACJQoD//4rqAIAAfB6AgACXJ3A=
Date: Fri, 12 Jul 2013 15:28:37 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F645B47919@dfweml509-mbx.china.huawei.com>
References: <4A95BA014132FF49AE685FAB4B9F17F645B472B6@dfweml509-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B63077520C0F0@mbx-01.win.nominum.com> <4A95BA014132FF49AE685FAB4B9F17F645B473B1@dfweml509-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B63077520C2DC@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077520C2DC@mbx-01.win.nominum.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.132.213]
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>
Subject: Re: [Int-area] FW: New Version Notification for draft-nachum-sarp-05.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, 12 Jul 2013 15:29:09 -0000

Ted,=20

You have really good questions.=20

Answers to your questions are inserted below:=20

> -----Original Message-----
>=20
> True.   However, they do have various strategies for addressing this
> problem, and I was wondering how you think your proposal fits in.   For
> example, the trill working group recently submitted a document for
> publication that addresses the issue of small, scattered virtual links
> with frequently migrating VMs in a very large campus using a directory
> service.  =20

[Linda] TRILL Directory Service, which I am one of the authors, allows ingr=
ess edge nodes to resolve the target egress edge node(s) without flooding d=
ata frames (unknown DA or ARP/ND) across the core. The SARP mechanism is to=
 reduce the amount of hosts (VMs) addresses exposed to edge nodes: all remo=
te hosts (VMs) are represented by their corresponding GW.=20


Directory Service can make SARP run more smoothly. When remote VMs are move=
d/added/deleted, the Directory Service can quickly inform the relevant edge=
 nodes on the change.=20



I reviewed an nvo3 problem statement document for the
> telechat two weeks ago that talked about the same issue as well.

[Linda] If NVO3 edges (NVE) are on Top of Rack switch or End of Row switch =
and there are switches between hosts (VMs) and Overlay Edges, all those swi=
tches/overlay edges will also run into MAC table explosion problem.=20

I once saw a NvGRE presentation by Microsoft which has a section on overlay=
 edge node behaving as proxy Gateway for all the hosts (VMs) attached. SARP=
 is along the same principle, i.e. making VMs use their corresponding Edge =
node's MAC address as MAC-DA instead of the MAC address of their Layer 2 pe=
ers' that are attached to different edge nodes.=20

Please ask more questions!  It will help us to make the draft more clear.=20


Linda


From sunqi.csnet.thu@gmail.com  Thu Jul 11 19:49:39 2013
Return-Path: <sunqi.csnet.thu@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 46A1E11E80EA for <int-area@ietfa.amsl.com>; Thu, 11 Jul 2013 19:49:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[AWL=-0.698,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
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 whFFBugXAwkN for <int-area@ietfa.amsl.com>; Thu, 11 Jul 2013 19:49:38 -0700 (PDT)
Received: from mail-pd0-x232.google.com (mail-pd0-x232.google.com [IPv6:2607:f8b0:400e:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id A1B6021F9D4A for <int-area@ietf.org>; Thu, 11 Jul 2013 19:49:38 -0700 (PDT)
Received: by mail-pd0-f178.google.com with SMTP id w11so8159781pde.9 for <int-area@ietf.org>; Thu, 11 Jul 2013 19:49:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to:x-mailer; bh=LX8Cm3/RFGSM08oUJnC9iFwT7Fh8+J08/pJoovuL8kE=; b=J/fnMJiuSbbBW5o4iytD96omeh3DtHLjOhgfvYD5Sf938/Vr+HeCgTMCP495CClpVQ 4zbsIUYZHHdjz2IBBcO7XA7sUDf3h93RiOCkMn5uso49VQHFyzw+EobTrwTSSmLZKC2a N3+ltSQbS1geO0f2cy3QwZMLQupoHbJjJhsg6+FAF2N3asJbVFDf5fp16v2KLgkSiGb2 F38ATE6DCPrXQziCaf/BSPZEK1rpCfP4GqL55CHLbqoxtMOCcszqPFAoWiU1trOYZJj3 FoXLTeNnGX4Is6lkLVa3KOvYfJdSkwh/B5Mpsabh4hin8UmEcDK4Pkwqhd1n4OrZMWR5 YHQw==
X-Received: by 10.67.23.3 with SMTP id hw3mr12662480pad.54.1373597377358; Thu, 11 Jul 2013 19:49:37 -0700 (PDT)
Received: from [192.168.1.107] ([166.111.68.233]) by mx.google.com with ESMTPSA id xl3sm42592117pbb.17.2013.07.11.19.49.34 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 11 Jul 2013 19:49:36 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-61-153177745
From: Qi Sun <sunqi.csnet.thu@gmail.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F645B46E2C@dfweml509-mbx.china.huawei.com>
Date: Fri, 12 Jul 2013 10:49:28 +0800
Message-Id: <1795A383-530A-4255-A6DB-DE97B10FB7D6@gmail.com>
References: <51DDE4E6.80103@ericsson.com> <CAH3bfABG+-WQysRQHtFjU6PfNmSnkqqnTsUEMWT8Hd=uWL+F=g@mail.gmail.com> <EF6A204047BD994A860EE26D5F23BF5840561187@nkgeml505-mbx.china.huawei.com> <4A95BA014132FF49AE685FAB4B9F17F645B46E2C@dfweml509-mbx.china.huawei.com>
To: Linda Dunbar <linda.dunbar@huawei.com>
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Fri, 12 Jul 2013 09:47:48 -0700
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] Working group last call	for	draft-ietf-intarea-flow-label-balancing-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, 12 Jul 2013 02:49:39 -0000

--Apple-Mail-61-153177745
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Support.

Best Regards,
Qi Sun

On 2013-7-11, at =E4=B8=8B=E5=8D=8810:52, Linda Dunbar wrote:

> Support.
> =20
> Linda
> =20
> =20
> From: int-area-bounces@ietf.org [mailto:int-area-bounces@ietf.org] On =
Behalf Of Qiong
> Sent: Thursday, July 11, 2013 1:20 PM
> To: Suresh Krishnan
> Cc: Internet Area
> Subject: Re: [Int-area] Working group last call for =
draft-ietf-intarea-flow-label-balancing-01
> =20
> Dear all,
> =20
> I think it is ready to move forward.
> =20
> Thanks
> =20
> Best wishes
> Qiong=20
> =20
>=20
> On Thu, Jul 11, 2013 at 6:49 AM, Suresh Krishnan =
<suresh.krishnan@ericsson.com> wrote:
> Hi all,
>   This message starts a two week intarea working group last call on =
this
> draft describing the use of IPv6 Flow Label for Server Load Balancing =
as
> an Informational RFC. The draft is available at
>=20
> http://www.ietf.org/id/draft-ietf-intarea-flow-label-balancing-01.txt
> http://tools.ietf.org/html/draft-ietf-intarea-flow-label-balancing-01
>=20
> Substantive comments and statements of support/opposition for =
advancing
> this document should be directed to the mailing list. Editorial
> suggestions can be sent directly to the authors. This last call will
> conclude on July 24, 2013.
>=20
> Regards,
> Suresh & Julien
>=20
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area
>=20
>=20
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area


--Apple-Mail-61-153177745
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><base href=3D"x-msg://637/"></head><body style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; ">Support.<div><br></div><div>Best =
Regards,</div><div>Qi Sun</div><div><br><div><div>On 2013-7-11, at =
=E4=B8=8B=E5=8D=8810:52, Linda Dunbar wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: 'Heiti SC'; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div class=3D"WordSection1" =
style=3D"page: WordSection1; "><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: =E5=AE=8B=E4=BD=93; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
">Support.<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: =E5=AE=8B=E4=BD=93; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: =E5=AE=8B=E4=BD=93; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
">Linda<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: =E5=AE=8B=E4=BD=93; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
"><o:p>&nbsp;</o:p></span></div><div style=3D"border-top-style: none; =
border-right-style: none; border-bottom-style: none; border-width: =
initial; border-color: initial; border-left-style: solid; =
border-left-color: blue; border-left-width: 1.5pt; padding-top: 0in; =
padding-right: 0in; padding-bottom: 0in; padding-left: 4pt; "><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 12pt; font-family: =E5=AE=8B=E4=BD=93; =
"><span style=3D"font-size: 10.5pt; font-family: Calibri, sans-serif; =
color: rgb(31, 73, 125); "><o:p>&nbsp;</o:p></span></div><div =
style=3D"border-right-style: none; border-bottom-style: none; =
border-left-style: none; border-width: initial; border-color: initial; =
border-top-style: solid; border-top-color: rgb(181, 196, 223); =
border-top-width: 1pt; padding-top: 3pt; padding-right: 0in; =
padding-bottom: 0in; padding-left: 0in; "><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: =E5=AE=8B=E4=BD=93; "><b><span style=3D"font-size: =
10pt; font-family: Tahoma, sans-serif; ">From:</span></b><span =
style=3D"font-size: 10pt; font-family: Tahoma, sans-serif; "><span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:int-area-bounces@ietf.org" style=3D"color: blue; =
text-decoration: underline; ">int-area-bounces@ietf.org</a><span =
class=3D"Apple-converted-space">&nbsp;</span>[mailto:int-area-bounces@ietf=
.org]<span class=3D"Apple-converted-space">&nbsp;</span><b>On Behalf =
Of<span =
class=3D"Apple-converted-space">&nbsp;</span></b>Qiong<br><b>Sent:</b><spa=
n class=3D"Apple-converted-space">&nbsp;</span>Thursday, July 11, 2013 =
1:20 PM<br><b>To:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Suresh =
Krishnan<br><b>Cc:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Internet =
Area<br><b>Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Re: [Int-area] Working =
group last call for =
draft-ietf-intarea-flow-label-balancing-01<o:p></o:p></span></div></div><d=
iv style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 12pt; font-family: =E5=AE=8B=E4=BD=93; =
"><o:p>&nbsp;</o:p></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: =E5=AE=8B=E4=BD=93; ">Dear =
all,<o:p></o:p></div><div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; =
font-family: =E5=AE=8B=E4=BD=93; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: =E5=AE=8B=E4=BD=93; ">I think it is ready to move =
forward.<o:p></o:p></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: =E5=AE=8B=E4=BD=93; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: =E5=AE=8B=E4=BD=93; =
">Thanks<o:p></o:p></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: =E5=AE=8B=E4=BD=93; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: =E5=AE=8B=E4=BD=93; ">Best =
wishes<o:p></o:p></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
12pt; font-family: =E5=AE=8B=E4=BD=93; =
">Qiong&nbsp;<o:p></o:p></div></div><div><p class=3D"MsoNormal" =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 12pt; =
margin-left: 0in; font-size: 12pt; font-family: =E5=AE=8B=E4=BD=93; =
"><o:p>&nbsp;</o:p></p><div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 12pt; =
font-family: =E5=AE=8B=E4=BD=93; ">On Thu, Jul 11, 2013 at 6:49 AM, =
Suresh Krishnan &lt;<a href=3D"mailto:suresh.krishnan@ericsson.com" =
target=3D"_blank" style=3D"color: blue; text-decoration: underline; =
">suresh.krishnan@ericsson.com</a>&gt; wrote:<o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 12pt; font-family: =E5=AE=8B=E4=BD=93; ">Hi =
all,<br>&nbsp; This message starts a two week intarea working group last =
call on this<br>draft describing the use of IPv6 Flow Label for Server =
Load Balancing as<br>an Informational RFC. The draft is available =
at<br><br><a =
href=3D"http://www.ietf.org/id/draft-ietf-intarea-flow-label-balancing-01.=
txt" target=3D"_blank" style=3D"color: blue; text-decoration: underline; =
">http://www.ietf.org/id/draft-ietf-intarea-flow-label-balancing-01.txt</a=
><br><a =
href=3D"http://tools.ietf.org/html/draft-ietf-intarea-flow-label-balancing=
-01" target=3D"_blank" style=3D"color: blue; text-decoration: underline; =
">http://tools.ietf.org/html/draft-ietf-intarea-flow-label-balancing-01</a=
><br><br>Substantive comments and statements of support/opposition for =
advancing<br>this document should be directed to the mailing list. =
Editorial<br>suggestions can be sent directly to the authors. This last =
call will<br>conclude on July 24, 2013.<br><br>Regards,<br>Suresh &amp; =
Julien<br><br>_______________________________________________<br>Int-area =
mailing list<br><a href=3D"mailto:Int-area@ietf.org" style=3D"color: =
blue; text-decoration: underline; ">Int-area@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/int-area" target=3D"_blank" =
style=3D"color: blue; text-decoration: underline; =
">https://www.ietf.org/mailman/listinfo/int-area</a><o:p></o:p></div></div=
><div style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: =
0.0001pt; margin-left: 0in; font-size: 12pt; font-family: =E5=AE=8B=E4=BD=93=
; "><br><br =
clear=3D"all"><o:p></o:p></div></div></div></div></div>___________________=
____________________________<br>Int-area mailing list<br><a =
href=3D"mailto:Int-area@ietf.org" style=3D"color: blue; text-decoration: =
underline; ">Int-area@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/int-area" style=3D"color: =
blue; text-decoration: underline; =
">https://www.ietf.org/mailman/listinfo/int-area</a><br></div></span></blo=
ckquote></div><br></div></body></html>=

--Apple-Mail-61-153177745--

From jrjahangir@gmail.com  Fri Jul 12 23:04:30 2013
Return-Path: <jrjahangir@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 0C6BD21E80D1 for <int-area@ietfa.amsl.com>; Fri, 12 Jul 2013 23:04:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150,  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 BgzSpN25gaNG for <int-area@ietfa.amsl.com>; Fri, 12 Jul 2013 23:04:29 -0700 (PDT)
Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) by ietfa.amsl.com (Postfix) with ESMTP id F3A7C21E8095 for <int-area@ietf.org>; Fri, 12 Jul 2013 23:04:28 -0700 (PDT)
Received: by mail-wi0-f172.google.com with SMTP id c10so1342552wiw.5 for <int-area@ietf.org>; Fri, 12 Jul 2013 23:04:26 -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=0kRMmivPOK4d2x5XbFKrGCJlipelkm7G8Am8+hJKsD0=; b=GTxqypTleVLXi+VEkzVheStSvDn/oFIjeyDA2p4QwZU87WElZ+78NdvLMFr6OrCYRK IA8wgLbKq/bRKGZDA2Vij59gbGNhFc5bolW06DUHXjlUklzFXzB4EoXcnkMvDnuzPIlX Jz+HvDB0iZp9xeCXVCYXJ47r9WZjqR/uXPD1jvGd5oE3fpJxR1kPcx9Fyje4Tul3Ti+h atHdRNnYCArxtMAvghsqdSMrKYAr0vzSX//RbCjmkKJIWPE4+mqI1jEaT7l3EJQ71bl+ t29iHVLwNuofGJd230ZhdhYL3D2Np1VDhDGTzmOZwqkHdJfNTV3o0aWNjQmo77+3sFpc OEaA==
MIME-Version: 1.0
X-Received: by 10.180.108.115 with SMTP id hj19mr3551389wib.4.1373695466792; Fri, 12 Jul 2013 23:04:26 -0700 (PDT)
Received: by 10.194.3.72 with HTTP; Fri, 12 Jul 2013 23:04:26 -0700 (PDT)
In-Reply-To: <1795A383-530A-4255-A6DB-DE97B10FB7D6@gmail.com>
References: <51DDE4E6.80103@ericsson.com> <CAH3bfABG+-WQysRQHtFjU6PfNmSnkqqnTsUEMWT8Hd=uWL+F=g@mail.gmail.com> <EF6A204047BD994A860EE26D5F23BF5840561187@nkgeml505-mbx.china.huawei.com> <4A95BA014132FF49AE685FAB4B9F17F645B46E2C@dfweml509-mbx.china.huawei.com> <1795A383-530A-4255-A6DB-DE97B10FB7D6@gmail.com>
Date: Sat, 13 Jul 2013 12:04:26 +0600
Message-ID: <CAG5EbHLxGzpezr6hOWRsXTpAMidUvp17KyZNi9ziT4kTNniqZw@mail.gmail.com>
From: "Md.Jahangir Hossain" <jrjahangir@gmail.com>
To: Qi Sun <sunqi.csnet.thu@gmail.com>
Content-Type: multipart/alternative; boundary=e89a8f2344a353edc204e15e662b
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] Working group last call for draft-ietf-intarea-flow-label-balancing-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: Sat, 13 Jul 2013 06:04:30 -0000

--e89a8f2344a353edc204e15e662b
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi , I am quit new on IETF platform but i read the draft link.

Based on my understanding i think, it should go the next step and i support
this.




Tx-     Thanks  //  Md. Jahangir Hossain



On Fri, Jul 12, 2013 at 8:49 AM, Qi Sun <sunqi.csnet.thu@gmail.com> wrote:

> Support.
>
> Best Regards,
> Qi Sun
>
> On 2013-7-11, at =E4=B8=8B=E5=8D=8810:52, Linda Dunbar wrote:
>
> Support.****
> ** **
> Linda****
> ** **
> ** **
> *From:* int-area-bounces@ietf.org [mailto:int-area-bounces@ietf.org] *On
> Behalf Of *Qiong
> *Sent:* Thursday, July 11, 2013 1:20 PM
> *To:* Suresh Krishnan
> *Cc:* Internet Area
> *Subject:* Re: [Int-area] Working group last call for
> draft-ietf-intarea-flow-label-balancing-01****
> ** **
> Dear all,****
> ** **
> I think it is ready to move forward.****
> ** **
> Thanks****
> ** **
> Best wishes****
> Qiong ****
>
> ** **
> On Thu, Jul 11, 2013 at 6:49 AM, Suresh Krishnan <
> suresh.krishnan@ericsson.com> wrote:****
> Hi all,
>   This message starts a two week intarea working group last call on this
> draft describing the use of IPv6 Flow Label for Server Load Balancing as
> an Informational RFC. The draft is available at
>
> http://www.ietf.org/id/draft-ietf-intarea-flow-label-balancing-01.txt
> http://tools.ietf.org/html/draft-ietf-intarea-flow-label-balancing-01
>
> Substantive comments and statements of support/opposition for advancing
> this document should be directed to the mailing list. Editorial
> suggestions can be sent directly to the authors. This last call will
> conclude on July 24, 2013.
>
> 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
>
>
>
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area
>
>


--=20




**

--e89a8f2344a353edc204e15e662b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi , I am quit new on IETF platform but i read the dr=
aft link. <br><br></div>Based on my understanding i think, it should go the=
 next step and i support this.<br><div><div><br><br><br><br><div class=3D"g=
mail_extra">
Tx- =C2=A0=C2=A0=C2=A0 Thanks=C2=A0 //=C2=A0 Md. Jahangir Hossain<br><br><b=
r><br><div class=3D"gmail_quote">On Fri, Jul 12, 2013 at 8:49 AM, Qi Sun <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:sunqi.csnet.thu@gmail.com" target=3D"=
_blank">sunqi.csnet.thu@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex"><div style=3D"word-wrap:b=
reak-word">Support.<div><br></div><div>Best Regards,</div><div>Qi Sun</div>=
<div>
<div class=3D"h5"><div><br><div><div>On 2013-7-11, at =E4=B8=8B=E5=8D=8810:=
52, Linda Dunbar wrote:</div><br><blockquote type=3D"cite"><span style=3D"b=
order-collapse:separate;font-family:&#39;Heiti SC&#39;;font-style:normal;fo=
nt-variant:normal;font-weight:normal;letter-spacing:normal;line-height:norm=
al;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;=
font-size:medium"><div link=3D"blue" vlink=3D"purple" lang=3D"EN-US">
<div><div style=3D"margin:0in 0in 0.0001pt;font-size:12pt;font-family:=E5=
=AE=8B=E4=BD=93"><span style=3D"font-size:11pt;font-family:Calibri,sans-ser=
if;color:rgb(31,73,125)">Support.<u></u><u></u></span></div><div style=3D"m=
argin:0in 0in 0.0001pt;font-size:12pt;font-family:=E5=AE=8B=E4=BD=93">
<span style=3D"font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,7=
3,125)"><u></u>=C2=A0<u></u></span></div><div style=3D"margin:0in 0in 0.000=
1pt;font-size:12pt;font-family:=E5=AE=8B=E4=BD=93"><span style=3D"font-size=
:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Linda<u></u><u><=
/u></span></div>
<div style=3D"margin:0in 0in 0.0001pt;font-size:12pt;font-family:=E5=AE=8B=
=E4=BD=93"><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;col=
or:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></div><div style=3D"border-st=
yle:none none none solid;border-top-width:initial;border-right-width:initia=
l;border-bottom-width:initial;border-top-color:initial;border-right-color:i=
nitial;border-bottom-color:initial;border-left:1.5pt solid blue;padding:0in=
 0in 0in 4pt">
<div style=3D"margin:0in 0in 0.0001pt;font-size:12pt;font-family:=E5=AE=8B=
=E4=BD=93"><span style=3D"font-size:10.5pt;font-family:Calibri,sans-serif;c=
olor:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></div><div style=3D"border-=
style:solid none none;border-right-width:initial;border-bottom-width:initia=
l;border-left-width:initial;border-right-color:initial;border-bottom-color:=
initial;border-left-color:initial;border-top:1pt solid rgb(181,196,223);pad=
ding:3pt 0in 0in">
<div style=3D"margin:0in 0in 0.0001pt;font-size:12pt;font-family:=E5=AE=8B=
=E4=BD=93"><b><span style=3D"font-size:10pt;font-family:Tahoma,sans-serif">=
From:</span></b><span style=3D"font-size:10pt;font-family:Tahoma,sans-serif=
"><span>=C2=A0</span><a href=3D"mailto:int-area-bounces@ietf.org" style=3D"=
color:blue;text-decoration:underline" target=3D"_blank">int-area-bounces@ie=
tf.org</a><span>=C2=A0</span>[mailto:<a href=3D"mailto:int-area-bounces@iet=
f.org" target=3D"_blank">int-area-bounces@ietf.org</a>]<span>=C2=A0</span><=
b>On Behalf Of<span>=C2=A0</span></b>Qiong<br>
<b>Sent:</b><span>=C2=A0</span>Thursday, July 11, 2013 1:20 PM<br><b>To:</b=
><span>=C2=A0</span>Suresh Krishnan<br><b>Cc:</b><span>=C2=A0</span>Interne=
t Area<br><b>Subject:</b><span>=C2=A0</span>Re: [Int-area] Working group la=
st call for draft-ietf-intarea-flow-label-balancing-01<u></u><u></u></span>=
</div>
</div><div style=3D"margin:0in 0in 0.0001pt;font-size:12pt;font-family:=E5=
=AE=8B=E4=BD=93"><u></u>=C2=A0<u></u></div><div><div style=3D"margin:0in 0i=
n 0.0001pt;font-size:12pt;font-family:=E5=AE=8B=E4=BD=93">Dear all,<u></u><=
u></u></div><div><div style=3D"margin:0in 0in 0.0001pt;font-size:12pt;font-=
family:=E5=AE=8B=E4=BD=93">
<u></u>=C2=A0<u></u></div></div><div><div style=3D"margin:0in 0in 0.0001pt;=
font-size:12pt;font-family:=E5=AE=8B=E4=BD=93">I think it is ready to move =
forward.<u></u><u></u></div></div><div><div style=3D"margin:0in 0in 0.0001p=
t;font-size:12pt;font-family:=E5=AE=8B=E4=BD=93">
<u></u>=C2=A0<u></u></div></div><div><div style=3D"margin:0in 0in 0.0001pt;=
font-size:12pt;font-family:=E5=AE=8B=E4=BD=93">Thanks<u></u><u></u></div></=
div><div><div style=3D"margin:0in 0in 0.0001pt;font-size:12pt;font-family:=
=E5=AE=8B=E4=BD=93"><u></u>=C2=A0<u></u></div>
</div><div><div style=3D"margin:0in 0in 0.0001pt;font-size:12pt;font-family=
:=E5=AE=8B=E4=BD=93">Best wishes<u></u><u></u></div></div><div><div style=
=3D"margin:0in 0in 0.0001pt;font-size:12pt;font-family:=E5=AE=8B=E4=BD=93">=
Qiong=C2=A0<u></u><u></u></div></div><div>
<p class=3D"" style=3D"margin:0in 0in 12pt;font-size:12pt;font-family:=E5=
=AE=8B=E4=BD=93"><u></u>=C2=A0<u></u></p><div><div style=3D"margin:0in 0in =
0.0001pt;font-size:12pt;font-family:=E5=AE=8B=E4=BD=93">On Thu, Jul 11, 201=
3 at 6:49 AM, Suresh Krishnan &lt;<a href=3D"mailto:suresh.krishnan@ericsso=
n.com" style=3D"color:blue;text-decoration:underline" target=3D"_blank">sur=
esh.krishnan@ericsson.com</a>&gt; wrote:<u></u><u></u></div>
<div style=3D"margin:0in 0in 0.0001pt;font-size:12pt;font-family:=E5=AE=8B=
=E4=BD=93">Hi all,<br>=C2=A0 This message starts a two week intarea working=
 group last call on this<br>draft describing the use of IPv6 Flow Label for=
 Server Load Balancing as<br>
an Informational RFC. The draft is available at<br><br><a href=3D"http://ww=
w.ietf.org/id/draft-ietf-intarea-flow-label-balancing-01.txt" style=3D"colo=
r:blue;text-decoration:underline" target=3D"_blank">http://www.ietf.org/id/=
draft-ietf-intarea-flow-label-balancing-01.txt</a><br>
<a href=3D"http://tools.ietf.org/html/draft-ietf-intarea-flow-label-balanci=
ng-01" style=3D"color:blue;text-decoration:underline" target=3D"_blank">htt=
p://tools.ietf.org/html/draft-ietf-intarea-flow-label-balancing-01</a><br><=
br>
Substantive comments and statements of support/opposition for advancing<br>=
this document should be directed to the mailing list. Editorial<br>suggesti=
ons can be sent directly to the authors. This last call will<br>conclude on=
 July 24, 2013.<br>
<br>Regards,<br>Suresh &amp; Julien<br><br>________________________________=
_______________<br>Int-area mailing list<br><a href=3D"mailto:Int-area@ietf=
.org" style=3D"color:blue;text-decoration:underline" target=3D"_blank">Int-=
area@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/int-area" style=3D"color:b=
lue;text-decoration:underline" target=3D"_blank">https://www.ietf.org/mailm=
an/listinfo/int-area</a><u></u><u></u></div></div><div style=3D"margin:0in =
0in 0.0001pt;font-size:12pt;font-family:=E5=AE=8B=E4=BD=93">
<br><br clear=3D"all"><u></u><u></u></div></div></div></div></div>_________=
______________________________________<br>Int-area mailing list<br><a href=
=3D"mailto:Int-area@ietf.org" style=3D"color:blue;text-decoration:underline=
" target=3D"_blank">Int-area@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/int-area" style=3D"color:b=
lue;text-decoration:underline" target=3D"_blank">https://www.ietf.org/mailm=
an/listinfo/int-area</a><br></div></span></blockquote></div><br></div></div=
></div>
</div><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>
<br></blockquote></div><br><br clear=3D"all"><br>-- <br><div dir=3D"ltr"><d=
iv><br><br></div><div>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 <br></div><div><br></d=
iv><b></b><div><pre><br></pre></div></div>
</div></div></div></div>

--e89a8f2344a353edc204e15e662b--

From Ted.Lemon@nominum.com  Sun Jul 14 11:09:02 2013
Return-Path: <Ted.Lemon@nominum.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 1431721F9C72 for <int-area@ietfa.amsl.com>; Sun, 14 Jul 2013 11:09:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.6
X-Spam-Level: 
X-Spam-Status: No, score=-106.6 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vIQsqvlJQaFJ for <int-area@ietfa.amsl.com>; Sun, 14 Jul 2013 11:08:42 -0700 (PDT)
Received: from exprod7og128.obsmtp.com (exprod7og128.obsmtp.com [64.18.2.121]) by ietfa.amsl.com (Postfix) with ESMTP id 6088421F9BA8 for <int-area@ietf.org>; Sun, 14 Jul 2013 11:08:42 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob128.postini.com ([64.18.6.12]) with SMTP ID DSNKUeLpKI29UvpFAM02ULMeneyaBLtxgjBc@postini.com; Sun, 14 Jul 2013 11:08:42 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id C543E1B821E for <int-area@ietf.org>; Sun, 14 Jul 2013 11:08:40 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id A752C190052; Sun, 14 Jul 2013 11:08:40 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Sun, 14 Jul 2013 11:08:40 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Linda Dunbar <linda.dunbar@huawei.com>
Thread-Topic: [Int-area] New Version Notification for draft-nachum-sarp-05.txt
Thread-Index: AQHOgL0r1QxUU0G4yUGaaSKAInlpGA==
Date: Sun, 14 Jul 2013 18:08:39 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077521009E@mbx-01.win.nominum.com>
References: <4A95BA014132FF49AE685FAB4B9F17F645B472B6@dfweml509-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B63077520C0F0@mbx-01.win.nominum.com> <4A95BA014132FF49AE685FAB4B9F17F645B473B1@dfweml509-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B63077520C2DC@mbx-01.win.nominum.com> <4A95BA014132FF49AE685FAB4B9F17F645B47919@dfweml509-mbx.china.huawei.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F645B47919@dfweml509-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <A10221424408294AA3B6CCDDCF18DB64@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] New Version Notification for draft-nachum-sarp-05.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: Sun, 14 Jul 2013 18:09:02 -0000

On Jul 12, 2013, at 11:28 AM, Linda Dunbar <linda.dunbar@huawei.com> wrote:
> You have really good questions.=20

What these are are questions by your AD who is trying to figure out how thi=
s stuff all fits together.   It's kind of you to say that they are good que=
stions, but really I'm just trying to fill in knowledge of things about whi=
ch I am fairly ignorant.

The question I was trying to answer was how this differs from the technique=
s described in the two drafts to which I was referring.   I had read the do=
cument fairly carefully at the beginning, but didn't really understand what=
 it was trying to do, and it seemed to be doing the same thing that the tri=
ll and nvo3 drafts are talking about, hence the questions.   I hadn't notic=
ed that you were a co-author of the trill draft=97sorry about that.   I not=
ice now that you also refer to the nvo3 draft in this draft.

So one thing that I think this draft fails to do right now that you need to=
 fix is that I didn't actually know what technique was being described in t=
he draft until reading section 3.2.   It would really help to have somethin=
g in the introduction that says something like "this document describes a t=
echnique for reducing the size of arp tables on L2/L3 switches by substitut=
ing the MAC address of the switch to which a host is connected for the MAC =
address of the host when forwarding packets to other switches hosting the s=
ame VLAN to which the source host is connected."

I realize that this text isn't exactly right, but something like this would=
 help.   It would really help to have two or three paragraphs after the ini=
tial section 1 header that talk very briefly about the motivation for the w=
ork, and then describe the technique at the level of overview that I used i=
n my example.   Having to get through a page and a half of motivation, a pa=
ge and a half of deployment scenario, and still not know what the draft is =
actually going to tell me how to do makes it difficult to get motivated to =
go any deeper.

The draft also over-uses abbreviations.   For instance:

   When a VM transmits packets to a destination VM that is located at
   the same site, there is no change in the data plane. The packets are
   sent from (IP-S, MAC-S) to (IP-D, MAC-D).

Why is it necessary to abbreviate like this?  Why not say:

   When a VM transmits packets to a destination VM that is located at
   the same site, there is no change in the data plane. The packets are
   sent from the source host IP and MAC address to the destination host
   IP and MAC address?

Or if you want to keep the tuples:

   When a VM transmits packets to a destination VM that is located at
   the same site, there is no change in the data plane. The packets are
   sent from (IP Source, MAC Source) to (IP Dest, MAC Dest).

This isn't all that important in the example I'm giving, but it was a bit p=
ainful to read the rest of this section because of all the abbreviations.

It would also help the readability of this document prior to its arrival at=
 the RFC Editor, assuming it gets there, if you could clean up some of the =
indentation problems in the introduction=97these make the document look rou=
gh, which again discourages reading it.   Using xml2rfc hanging indent for =
the numbered items in 1.1 and making sure there's a blank line between para=
graphs would neaten it up.   I realize this is a really minor nit, but when=
 you're asking for review making your document as clean as possible really =
helps.

Anyway, I think the answer to the main question that I was asking about thi=
s draft has been answered.   The question I was trying to figure out was wh=
y you were proposing this in intarea and not trill or nvo3; the answer, I p=
resume, is that the solution applies to both?


From linda.dunbar@huawei.com  Mon Jul 15 07:19:23 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 D582F21E8082 for <int-area@ietfa.amsl.com>; Mon, 15 Jul 2013 07:19:23 -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 yAXboNWk1pzY for <int-area@ietfa.amsl.com>; Mon, 15 Jul 2013 07:19:18 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 2EF6C21E8056 for <int-area@ietf.org>; Mon, 15 Jul 2013 07:19:18 -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 AVA61794; Mon, 15 Jul 2013 14:19:03 +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; Mon, 15 Jul 2013 15:18:13 +0100
Received: from DFWEML408-HUB.china.huawei.com (10.193.5.134) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.1.323.7; Mon, 15 Jul 2013 15:19:00 +0100
Received: from DFWEML509-MBX.china.huawei.com ([169.254.11.169]) by dfweml408-hub.china.huawei.com ([10.193.5.134]) with mapi id 14.01.0323.007; Mon, 15 Jul 2013 07:18:56 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: [Int-area] New Version Notification for draft-nachum-sarp-05.txt
Thread-Index: AQHOgL0z3cRk3SoBoUu/RRnnEkuT9JllyWlg
Date: Mon, 15 Jul 2013 14:18:55 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F645B49236@dfweml509-mbx.china.huawei.com>
References: <4A95BA014132FF49AE685FAB4B9F17F645B472B6@dfweml509-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B63077520C0F0@mbx-01.win.nominum.com> <4A95BA014132FF49AE685FAB4B9F17F645B473B1@dfweml509-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B63077520C2DC@mbx-01.win.nominum.com> <4A95BA014132FF49AE685FAB4B9F17F645B47919@dfweml509-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B63077521009E@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077521009E@mbx-01.win.nominum.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.134.20]
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>
Subject: Re: [Int-area] New Version Notification for draft-nachum-sarp-05.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: Mon, 15 Jul 2013 14:19:24 -0000

Ted,=20

Thank you very much for the suggested text.=20
I tweaked a little bit. How about the following text added to the Introduct=
ion section?

"This document describes a proxy gateway technique, which is called SARP th=
roughout this document, to reduce switches' FDB (MAC table) sizes and ARP/N=
D impact on network elements in an environment where hosts within one subne=
t (or VLAN) can spread over various access domains in data centers.=20

The main idea of SARP is to make all VMs (or hosts) under each access domai=
n be represented by their corresponding access (or aggregation) node's MAC =
address regardless if the access (or aggregation) node is the VMs (hosts)' =
gateway or not. For example, when a host "a" under access domain "S" needs =
to communicate with peers in the same VLAN but located in other access doma=
ins, SARP requires "a" to use remote access node's MAC address instead of t=
heir remote Layer 2 peer's MAC address. By doing so, all the switches' FDB =
don't need to keep remote hosts MAC addresses."  =20



> -----Original Message-----
> "this document describes a technique for reducing the size of arp
> tables on L2/L3 switches by substituting the MAC address of the switch
> to which a host is connected for the MAC address of the host when
> forwarding packets to other switches hosting the same VLAN to which the
> source host is connected."



>=20
> Anyway, I think the answer to the main question that I was asking about
> this draft has been answered.   The question I was trying to figure out
> was why you were proposing this in intarea and not trill or nvo3; the
> answer, I presume, is that the solution applies to both?

[Linda] Yes, the proposed solution applies to both.=20

Thank you.=20

Linda


From Ted.Lemon@nominum.com  Mon Jul 15 08:17:19 2013
Return-Path: <Ted.Lemon@nominum.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 729F911E80EC for <int-area@ietfa.amsl.com>; Mon, 15 Jul 2013 08:17:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.6
X-Spam-Level: 
X-Spam-Status: No, score=-106.6 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cd8evkaHQl4k for <int-area@ietfa.amsl.com>; Mon, 15 Jul 2013 08:17:12 -0700 (PDT)
Received: from exprod7og119.obsmtp.com (exprod7og119.obsmtp.com [64.18.2.16]) by ietfa.amsl.com (Postfix) with ESMTP id AF6C611E80DC for <int-area@ietf.org>; Mon, 15 Jul 2013 08:17:12 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob119.postini.com ([64.18.6.12]) with SMTP ID DSNKUeQSeK5IeXzLwt+wxnGYLojgpKOwSZ9u@postini.com; Mon, 15 Jul 2013 08:17:12 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 21A611B813B for <int-area@ietf.org>; Mon, 15 Jul 2013 08:17:12 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 0584E190052; Mon, 15 Jul 2013 08:17:12 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Mon, 15 Jul 2013 08:17:12 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Linda Dunbar <linda.dunbar@huawei.com>
Thread-Topic: [Int-area] New Version Notification for draft-nachum-sarp-05.txt
Thread-Index: AQHOgL0r1QxUU0G4yUGaaSKAInlpGJlmQFiAgAAQRgA=
Date: Mon, 15 Jul 2013 15:17:10 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775211477@mbx-01.win.nominum.com>
References: <4A95BA014132FF49AE685FAB4B9F17F645B472B6@dfweml509-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B63077520C0F0@mbx-01.win.nominum.com> <4A95BA014132FF49AE685FAB4B9F17F645B473B1@dfweml509-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B63077520C2DC@mbx-01.win.nominum.com> <4A95BA014132FF49AE685FAB4B9F17F645B47919@dfweml509-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B63077521009E@mbx-01.win.nominum.com> <4A95BA014132FF49AE685FAB4B9F17F645B49236@dfweml509-mbx.china.huawei.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F645B49236@dfweml509-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <286675ED08E6574A940976CD15663793@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] New Version Notification for draft-nachum-sarp-05.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: Mon, 15 Jul 2013 15:17:19 -0000

On Jul 15, 2013, at 7:18 AM, Linda Dunbar <linda.dunbar@huawei.com> wrote:
> "This document describes a proxy gateway technique, which is called SARP =
throughout this document, to reduce switches' FDB (MAC table) sizes and ARP=
/ND impact on network elements in an environment where hosts within one sub=
net (or VLAN) can spread over various access domains in data centers.=20
>=20
> The main idea of SARP is to make all VMs (or hosts) under each access dom=
ain be represented by their corresponding access (or aggregation) node's MA=
C address regardless if the access (or aggregation) node is the VMs (hosts)=
' gateway or not. For example, when a host "a" under access domain "S" need=
s to communicate with peers in the same VLAN but located in other access do=
mains, SARP requires "a" to use remote access node's MAC address instead of=
 their remote Layer 2 peer's MAC address. By doing so, all the switches' FD=
B don't need to keep remote hosts MAC addresses."  =20

How about:


   This document describes a proxy gateway technique called Scalable       =
       =20
   Address Resolution Protocol (SARP), which reduces switches' Friends     =
       =20
   Database (FDB) table size and limits and ARP/Neighbor Discovery         =
       =20
   impact on network elements in an environment where hosts within one     =
    =20
   subnet (or VLAN) can spread over various access domains in data         =
                       =20
   centers.                                                                =
    =20

   The main idea of SARP is to represent all VMs (or hosts) under each     =
       =20
   access domain by their corresponding access (or aggregation) node's     =
       =20
   MAC address, regardless of whether the access (or aggregation) node     =
       =20
   is the VMs (hosts)' gateway or not. For example, when a host "a"        =
    =20
   under access domain "S" needs to communicate with a peer on the         =
    =20
   same VLAN but connected to a different access domain, SARP requires     =
    =20
   "a" to use the remote access node's MAC address, rather than the        =
    =20
   peer's MAC address. By doing so, each switch in the VLAN does not
   need to maintain a list of MAC addresses for all each node on the=20
   VLAN in its FDB.

I don't know what FDB stands for, and the acronym is never expanded in the =
document, so I just said "Friends Database" but obviously you should substi=
tute in whatever FDB _actually_ stands for.    You should make sure that th=
ere are no unexpanded acronyms in the document.   Even if acronyms are gene=
rally understood by people who are working on the document, excessive use o=
f acronyms and use of unexpanded acronyms creates an very high barrier to e=
ntry for new readers of a document.

BTW, can you speak briefly to the question of how this actually saves signi=
ficant space in an FDB?   The reason I ask is that it seems to me that you =
still need to keep a complete list of all IP addresses in the FDB, even if =
they refer to the same MAC address.   So this represents a space savings of=
 maybe 27%, assuming a very efficient data representation.   The win is muc=
h bigger for IPv4 addresses, but it's still only 60%.


From linda.dunbar@huawei.com  Mon Jul 15 09:02:49 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 38F0111E812C for <int-area@ietfa.amsl.com>; Mon, 15 Jul 2013 09:02:49 -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 K8Xj0QBjN2k6 for <int-area@ietfa.amsl.com>; Mon, 15 Jul 2013 09:02:44 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 803B711E811B for <int-area@ietf.org>; Mon, 15 Jul 2013 09:02:43 -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 AVA69311; Mon, 15 Jul 2013 16:02:42 +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; Mon, 15 Jul 2013 17:01:51 +0100
Received: from DFWEML406-HUB.china.huawei.com (10.193.5.131) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.1.323.7; Mon, 15 Jul 2013 17:02:38 +0100
Received: from DFWEML509-MBX.china.huawei.com ([169.254.11.169]) by dfweml406-hub.china.huawei.com ([10.193.5.131]) with mapi id 14.01.0323.007; Mon, 15 Jul 2013 09:02:33 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: [Int-area] New Version Notification for draft-nachum-sarp-05.txt
Thread-Index: AQHOgL0z3cRk3SoBoUu/RRnnEkuT9JllyWlggACHNQD//5AkEA==
Date: Mon, 15 Jul 2013 16:02:33 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F645B4935C@dfweml509-mbx.china.huawei.com>
References: <4A95BA014132FF49AE685FAB4B9F17F645B472B6@dfweml509-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B63077520C0F0@mbx-01.win.nominum.com> <4A95BA014132FF49AE685FAB4B9F17F645B473B1@dfweml509-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B63077520C2DC@mbx-01.win.nominum.com> <4A95BA014132FF49AE685FAB4B9F17F645B47919@dfweml509-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B63077521009E@mbx-01.win.nominum.com> <4A95BA014132FF49AE685FAB4B9F17F645B49236@dfweml509-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B630775211477@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775211477@mbx-01.win.nominum.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.134.20]
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>
Subject: Re: [Int-area] New Version Notification for draft-nachum-sarp-05.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: Mon, 15 Jul 2013 16:02:49 -0000

Ted,=20

Thank you very much for the suggested text. We will change the draft before=
 uploading today. We will also spell out all the acronyms and reduce using =
them as much as possible.=20

FDB: Filtering Data Base, which is a term used for Layer 2 switches (IEEE80=
2.1Q).=20
Layer 2 switches flood data frames when MAC-DA is not in FDB, whereas route=
rs drop data frames when the DA is not in the Forwarding Information Base (=
FIB).=20

That is why Filtering Data Base (FDB) is used for Layer 2 switches.=20



> -----Original Message-----
> BTW, can you speak briefly to the question of how this actually saves
> significant space in an FDB?   The reason I ask is that it seems to me
> that you still need to keep a complete list of all IP addresses in the
> FDB, even if they refer to the same MAC address.   So this represents a
> space savings of maybe 27%, assuming a very efficient data
> representation.   The win is much bigger for IPv4 addresses, but it's
> still only 60%.

[Linda] Good question. When remote VMs (hosts) are represented by their cor=
responding access (or aggregation) node's MAC address, all switches only ne=
ed to keep the MAC addresses of their local VMs (hosts) and the MAC address=
es of remote access nodes in their FDB. They don't need to keep the MAC add=
resses of remote VMs (hosts). That is how all switches' FDB size is signifi=
cantly reduced no matter how wide VLANs are spread.=20
=20

The SARP scheme also includes MAC address translation at egress gateway. I.=
e. when an egress SARP gateway receives a data frame with destination addre=
ss equal to itself, the egress gateway will replace the destination MAC to =
the local host's MAC based on the inner IP destination address.=20


Hope it helps.=20

Linda




=20

From Ted.Lemon@nominum.com  Mon Jul 15 09:05:48 2013
Return-Path: <Ted.Lemon@nominum.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 4473621F9AD2 for <int-area@ietfa.amsl.com>; Mon, 15 Jul 2013 09:05:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.592
X-Spam-Level: 
X-Spam-Status: No, score=-106.592 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WYtVBctaEKnj for <int-area@ietfa.amsl.com>; Mon, 15 Jul 2013 09:05:41 -0700 (PDT)
Received: from exprod7og108.obsmtp.com (exprod7og108.obsmtp.com [64.18.2.169]) by ietfa.amsl.com (Postfix) with ESMTP id 8F50B21F9D1C for <int-area@ietf.org>; Mon, 15 Jul 2013 09:05:40 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob108.postini.com ([64.18.6.12]) with SMTP ID DSNKUeQd09KRbPJeGyejfOo5Z7PdkLt5gcFv@postini.com; Mon, 15 Jul 2013 09:05:40 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 30B771B8250 for <int-area@ietf.org>; Mon, 15 Jul 2013 09:05:39 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 179CC190052; Mon, 15 Jul 2013 09:05:39 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Mon, 15 Jul 2013 09:05:39 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Linda Dunbar <linda.dunbar@huawei.com>
Thread-Topic: [Int-area] New Version Notification for draft-nachum-sarp-05.txt
Thread-Index: AQHOgL0r1QxUU0G4yUGaaSKAInlpGJlmQFiAgAAQRgCAAAyugIAAAN0A
Date: Mon, 15 Jul 2013 16:05:38 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307752116E6@mbx-01.win.nominum.com>
References: <4A95BA014132FF49AE685FAB4B9F17F645B472B6@dfweml509-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B63077520C0F0@mbx-01.win.nominum.com> <4A95BA014132FF49AE685FAB4B9F17F645B473B1@dfweml509-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B63077520C2DC@mbx-01.win.nominum.com> <4A95BA014132FF49AE685FAB4B9F17F645B47919@dfweml509-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B63077521009E@mbx-01.win.nominum.com> <4A95BA014132FF49AE685FAB4B9F17F645B49236@dfweml509-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B630775211477@mbx-01.win.nominum.com> <4A95BA014132FF49AE685FAB4B9F17F645B4935C@dfweml509-mbx.china.huawei.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F645B4935C@dfweml509-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <10A4F408B43C614D9186CB68DA60E029@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] New Version Notification for draft-nachum-sarp-05.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: Mon, 15 Jul 2013 16:05:48 -0000

On Jul 15, 2013, at 9:02 AM, Linda Dunbar <linda.dunbar@huawei.com> wrote:
> [Linda] Good question. When remote VMs (hosts) are represented by their c=
orresponding access (or aggregation) node's MAC address, all switches only =
need to keep the MAC addresses of their local VMs (hosts) and the MAC addre=
sses of remote access nodes in their FDB. They don't need to keep the MAC a=
ddresses of remote VMs (hosts). That is how all switches' FDB size is signi=
ficantly reduced no matter how wide VLANs are spread.=20

The name "filtering database" clarified it, actually.   You don't need to s=
tore the IP addresses at all, right?


From linda.dunbar@huawei.com  Mon Jul 15 09:08:29 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 7E41021E80CF for <int-area@ietfa.amsl.com>; Mon, 15 Jul 2013 09:08:29 -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 WZ39-7UIsvaC for <int-area@ietfa.amsl.com>; Mon, 15 Jul 2013 09:08:12 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 122E321E80CA for <int-area@ietf.org>; Mon, 15 Jul 2013 09:08:11 -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 ATL63890; Mon, 15 Jul 2013 16:08:10 +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; Mon, 15 Jul 2013 17:07:37 +0100
Received: from DFWEML405-HUB.china.huawei.com (10.193.5.102) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.7; Mon, 15 Jul 2013 17:07:54 +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; Mon, 15 Jul 2013 09:07:47 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: [Int-area] New Version Notification for draft-nachum-sarp-05.txt
Thread-Index: AQHOgL0z3cRk3SoBoUu/RRnnEkuT9JllyWlggACHNQD//5AkEIAAfWcA//+LJ5A=
Date: Mon, 15 Jul 2013 16:07:47 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F645B49372@dfweml509-mbx.china.huawei.com>
References: <4A95BA014132FF49AE685FAB4B9F17F645B472B6@dfweml509-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B63077520C0F0@mbx-01.win.nominum.com> <4A95BA014132FF49AE685FAB4B9F17F645B473B1@dfweml509-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B63077520C2DC@mbx-01.win.nominum.com> <4A95BA014132FF49AE685FAB4B9F17F645B47919@dfweml509-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B63077521009E@mbx-01.win.nominum.com> <4A95BA014132FF49AE685FAB4B9F17F645B49236@dfweml509-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B630775211477@mbx-01.win.nominum.com> <4A95BA014132FF49AE685FAB4B9F17F645B4935C@dfweml509-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B6307752116E6@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307752116E6@mbx-01.win.nominum.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.134.20]
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>
Subject: Re: [Int-area] New Version Notification for draft-nachum-sarp-05.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: Mon, 15 Jul 2013 16:08:29 -0000

> -----Original Message-----
>=20
> The name "filtering database" clarified it, actually.   You don't need
> to store the IP addresses at all, right?

[Linda] Correct.=20



From linda.dunbar@huawei.com  Mon Jul 15 12:09:46 2013
Return-Path: <linda.dunbar@huawei.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49D9411E821D for <int-area@ietfa.amsl.com>; Mon, 15 Jul 2013 12:09:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 txCUMKas24oR for <int-area@ietfa.amsl.com>; Mon, 15 Jul 2013 12:09:42 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 50D4411E820F for <int-area@ietf.org>; Mon, 15 Jul 2013 12:09:41 -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 ATL72458; Mon, 15 Jul 2013 19:09:40 +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; Mon, 15 Jul 2013 20:09:05 +0100
Received: from DFWEML406-HUB.china.huawei.com (10.193.5.131) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.7; Mon, 15 Jul 2013 20:09:37 +0100
Received: from DFWEML509-MBX.china.huawei.com ([169.254.11.169]) by dfweml406-hub.china.huawei.com ([10.193.5.131]) with mapi id 14.01.0323.007; Mon, 15 Jul 2013 12:09:35 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: Ted Lemon <Ted.Lemon@nominum.com>, Internet Area <int-area@ietf.org>, Suresh Krishnan <suresh.krishnan@ericsson.com>
Thread-Topic: New Version Notification for draft-nachum-sarp-06.txt
Thread-Index: AQHOgY51lpZYbJtUrUSb1ETRt8fCN5lmGefA
Date: Mon, 15 Jul 2013 19:09:34 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F645B495AB@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.134.20]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [Int-area] FW: New Version Notification for 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: Mon, 15 Jul 2013 19:09:46 -0000

DQpNYW55IFRoYW5rcyB0byBUZWQgTGVtb24gaW4gYXNraW5nIG1hbnkgZ29vZCBxdWVzdGlvbnMg
YW5kIHByb3ZpZGluZyBnb29kIHN1Z2dlc3Rpb24gb24gdGhlIHRleHQuIFdlIGhhdmUgdXBkYXRl
ZCB0aGUgZHJhZnQgYmFzZWQgb24gVGVkJ3MgaW5wdXQuIA0KDQpMaW5kYSANCg0KDQotLS0tLU9y
aWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnIFttYWls
dG86aW50ZXJuZXQtZHJhZnRzQGlldGYub3JnXSANClNlbnQ6IE1vbmRheSwgSnVseSAxNSwgMjAx
MyAyOjA2IFBNDQpUbzogTGluZGEgRHVuYmFyOyBZb3V2YWwgTmFjaHVtOyBJbGFuIFllcnVzaGFs
bWk7IFRhbCBNaXpyYWhpDQpTdWJqZWN0OiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9yIGRy
YWZ0LW5hY2h1bS1zYXJwLTA2LnR4dA0KDQoNCkEgbmV3IHZlcnNpb24gb2YgSS1ELCBkcmFmdC1u
YWNodW0tc2FycC0wNi50eHQNCmhhcyBiZWVuIHN1Y2Nlc3NmdWxseSBzdWJtaXR0ZWQgYnkgWW91
dmFsIE5hY2h1bSBhbmQgcG9zdGVkIHRvIHRoZQ0KSUVURiByZXBvc2l0b3J5Lg0KDQpGaWxlbmFt
ZToJIGRyYWZ0LW5hY2h1bS1zYXJwDQpSZXZpc2lvbjoJIDA2DQpUaXRsZToJCSBTY2FsaW5nIHRo
ZSBBZGRyZXNzIFJlc29sdXRpb24gUHJvdG9jb2wgZm9yIExhcmdlIERhdGEgQ2VudGVycyAoU0FS
UCkNCkNyZWF0aW9uIGRhdGU6CSAyMDEzLTA3LTE1DQpHcm91cDoJCSBJbmRpdmlkdWFsIFN1Ym1p
c3Npb24NCk51bWJlciBvZiBwYWdlczogMjENClVSTDogICAgICAgICAgICAgaHR0cDovL3d3dy5p
ZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtbmFjaHVtLXNhcnAtMDYudHh0DQpTdGF0dXM6
ICAgICAgICAgIGh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtbmFjaHVtLXNh
cnANCkh0bWxpemVkOiAgICAgICAgaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtbmFj
aHVtLXNhcnAtMDYNCkRpZmY6ICAgICAgICAgICAgaHR0cDovL3d3dy5pZXRmLm9yZy9yZmNkaWZm
P3VybDI9ZHJhZnQtbmFjaHVtLXNhcnAtMDYNCg0KQWJzdHJhY3Q6DQogICBUaGlzIGRvY3VtZW50
IGludHJvZHVjZXMgU0FSUCwgYW4gYXJjaGl0ZWN0dXJlIHRoYXQgdXNlcyBwcm94eQ0KICAgZ2F0
ZXdheXMgdG8gc2NhbGUgbGFyZ2UgZGF0YSBjZW50ZXIgbmV0d29ya3MuIFNBUlAgaXMgYmFzZWQg
b24NCiAgIGZhc3QgcHJveGllcyB0aGF0IHNpZ25pZmljYW50bHkgcmVkdWNlIHN3aXRjaGVzJyBG
REIgKE1BQyB0YWJsZSkNCiAgIHNpemVzIGFuZCBBUlAvTkQgaW1wYWN0IG9uIG5ldHdvcmsgZWxl
bWVudHMgaW4gYW4gZW52aXJvbm1lbnQNCiAgIHdoZXJlIGhvc3RzIHdpdGhpbiBvbmUgc3VibmV0
IChvciBWTEFOKSBjYW4gc3ByZWFkIG92ZXIgdmFyaW91cw0KICAgbG9jYXRpb25zLiBTQVJQIGlz
IHRhcmdldGVkIGZvciBtYXNzaXZlIGRhdGEgY2VudGVycyB3aXRoIGENCiAgIHNpZ25pZmljYW50
IG51bWJlciBvZiBWTXMgdGhhdCBjYW4gbW92ZSBhY3Jvc3MgdmFyaW91cyBwaHlzaWNhbA0KICAg
bG9jYXRpb25zLg0KDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgDQoNCg0KVGhlIElFVEYgU2Vj
cmV0YXJpYXQNCg0K

From eckelcu@cisco.com  Mon Jul 15 14:07:30 2013
Return-Path: <eckelcu@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 1B86911E818A for <int-area@ietfa.amsl.com>; Mon, 15 Jul 2013 14:07:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 UHjfDb8j5mSf for <int-area@ietfa.amsl.com>; Mon, 15 Jul 2013 14:07:25 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 2924E11E81C0 for <int-area@ietf.org>; Mon, 15 Jul 2013 14:07:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2764; q=dns/txt; s=iport; t=1373922438; x=1375132038; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=GXRyrgNUhpLWDynYpdFB3OyXi8KtX9fnMgOPeEoNuGo=; b=DflmzL1ZRtSZqJR625+gVVBnz8xKqO8NawOqxT2UtmGffu09usYMZl8g /KXje07pHVSthM4VXen23c33GiL1zwZfDmbdnbO0ISboPQj1qSZk7iigb Kh1mKZtOaPRvEX3NqhhdFBSL/0sPtkNkt+6myA4d4q7LFeej9COZ65cFV 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah4FABFk5FGtJV2a/2dsb2JhbABagwY0T4MGvlYXfRZ0giMBAQEEIxFDDgYBCBEEAQEDAgYdAwIEMBQBBgEBBQQBBBMIAYgGAQyVZ459kUyBJo4NPoJSM20DmQWQJIFZgTmCKA
X-IronPort-AV: E=Sophos;i="4.89,671,1367971200"; d="scan'208";a="235128649"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-7.cisco.com with ESMTP; 15 Jul 2013 21:07:17 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r6FL7HuC004678 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <int-area@ietf.org>; Mon, 15 Jul 2013 21:07:17 GMT
Received: from xmb-aln-x08.cisco.com ([169.254.3.187]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.02.0318.004; Mon, 15 Jul 2013 16:07:17 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "int-area@ietf.org" <int-area@ietf.org>
Thread-Topic: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
Thread-Index: Ac6Bn0gbxl2mtmX2RumGmT6rK69PKg==
Date: Mon, 15 Jul 2013 21:07:17 +0000
Message-ID: <92B7E61ADAC1BB4F941F943788C08828048B4221@xmb-aln-x08.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [171.68.16.40]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jul 2013 21:07:30 -0000

V2UgaGF2ZSBzdWJtaXR0ZWQgYW5kIHdvdWxkIGFwcHJlY2lhdGUgY29tbWVudHMgb24gdGhlIGZv
bGxvd2luZyBkcmFmdC4gSXQgcHJvdmlkZXMgYSBmcmFtZXdvcmsgZm9yIGFwcGxpY2F0aW9ucyBh
bmQgbmV0d29yayBkZXZpY2VzIHRvIGNvbW11bmljYXRlIGNoYXJhY3RlcmlzdGljcyBhbmQgc2Vy
dmljZSBhdHRyaWJ1dGVzIGZvciB0cmFmZmljIGZsb3cuIE9uZSBhc3BlY3Qgd2UgYW50aWNpcGF0
ZSB0byBiZSBvZiBwYXJ0aWN1bGFyIGludGVyZXN0IHRvIHRoaXMgYXVkaWVuY2UgaXMgdGhlIHVz
ZSBvZiBJUEZJWCBpbiB0aGUgaW5mb3JtYXRpb24gbW9kZWwgd2UgZGVmaW5lZC4NCg0KQ2hlZXJz
LA0KQ2hhcmxlcw0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogaW50ZXJuZXQt
ZHJhZnRzQGlldGYub3JnIFttYWlsdG86aW50ZXJuZXQtZHJhZnRzQGlldGYub3JnXSANClNlbnQ6
IE1vbmRheSwgSnVseSAxNSwgMjAxMyAxOjQxIFBNDQpUbzogVG9lcmxlc3MgRWNrZXJ0IChlY2tl
cnQpOyBBbWluZSBDaG91a2lyIChhbWNob3VraSk7IFJlaW5hbGRvIFBlbm5vIChyZXBlbm5vKTsg
Q2hhcmxlcyBFY2tlbCAoZWNrZWxjdSkNClN1YmplY3Q6IE5ldyBWZXJzaW9uIE5vdGlmaWNhdGlv
biBmb3IgZHJhZnQtZWNrZXJ0LWludGFyZWEtZmxvdy1tZXRhZGF0YS1mcmFtZXdvcmstMDEudHh0
DQoNCg0KQSBuZXcgdmVyc2lvbiBvZiBJLUQsIGRyYWZ0LWVja2VydC1pbnRhcmVhLWZsb3ctbWV0
YWRhdGEtZnJhbWV3b3JrLTAxLnR4dA0KaGFzIGJlZW4gc3VjY2Vzc2Z1bGx5IHN1Ym1pdHRlZCBi
eSBUb2VybGVzcyBFY2tlcnQgYW5kIHBvc3RlZCB0byB0aGUNCklFVEYgcmVwb3NpdG9yeS4NCg0K
RmlsZW5hbWU6CSBkcmFmdC1lY2tlcnQtaW50YXJlYS1mbG93LW1ldGFkYXRhLWZyYW1ld29yaw0K
UmV2aXNpb246CSAwMQ0KVGl0bGU6CQkgQSBGcmFtZXdvcmsgZm9yIFNpZ25hbGluZyBGbG93IENo
YXJhY3RlcmlzdGljcyBiZXR3ZWVuIEFwcGxpY2F0aW9ucyBhbmQgdGhlIE5ldHdvcmsNCkNyZWF0
aW9uIGRhdGU6CSAyMDEzLTA3LTE1DQpHcm91cDoJCSBJbmRpdmlkdWFsIFN1Ym1pc3Npb24NCk51
bWJlciBvZiBwYWdlczogMTcNClVSTDogICAgICAgICAgICAgaHR0cDovL3d3dy5pZXRmLm9yZy9p
bnRlcm5ldC1kcmFmdHMvZHJhZnQtZWNrZXJ0LWludGFyZWEtZmxvdy1tZXRhZGF0YS1mcmFtZXdv
cmstMDEudHh0DQpTdGF0dXM6ICAgICAgICAgIGh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9k
b2MvZHJhZnQtZWNrZXJ0LWludGFyZWEtZmxvdy1tZXRhZGF0YS1mcmFtZXdvcmsNCkh0bWxpemVk
OiAgICAgICAgaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtZWNrZXJ0LWludGFyZWEt
Zmxvdy1tZXRhZGF0YS1mcmFtZXdvcmstMDENCkRpZmY6ICAgICAgICAgICAgaHR0cDovL3d3dy5p
ZXRmLm9yZy9yZmNkaWZmP3VybDI9ZHJhZnQtZWNrZXJ0LWludGFyZWEtZmxvdy1tZXRhZGF0YS1m
cmFtZXdvcmstMDENCg0KQWJzdHJhY3Q6DQogICBUaGlzIGRvY3VtZW50IHByb3ZpZGVzIGEgZnJh
bWV3b3JrIGZvciBjb21tdW5pY2F0aW5nIGluZm9ybWF0aW9uDQogICBlbGVtZW50cyAoYS5rLmEu
IG1ldGFkYXRhKSBpbiBhIGNvbnNpc3RlbnQgbWFubmVyIGJldHdlZW4NCiAgIGFwcGxpY2F0aW9u
cyBhbmQgdGhlIG5ldHdvcmsgdG8gcHJvdmlkZSBiZXR0ZXIgdmlzaWJpbGl0eSBvZg0KICAgYXBw
bGljYXRpb24gZmxvd3MsIHRoZXJlYnkgZW5hYmxpbmcgZGlmZmVyZW50aWF0ZWQgdHJlYXRtZW50
IG9mIHRob3NlDQogICBmbG93cy4gIFRoZXNlIGluZm9ybWF0aW9uIGVsZW1lbnRzIGNhbiBiZSBj
b252ZXllZCB1c2luZyB2YXJpb3VzDQogICBzaWduYWxpbmcgcHJvdG9jb2xzLCBpbmNsdWRpbmcg
UENQLCBSU1ZQLCBhbmQgU1RVTi4NCg0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0KDQoNClRo
ZSBJRVRGIFNlY3JldGFyaWF0DQoNCg==

From Ted.Lemon@nominum.com  Wed Jul 17 20:08:55 2013
Return-Path: <Ted.Lemon@nominum.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 BEC0921F9A2E for <int-area@ietfa.amsl.com>; Wed, 17 Jul 2013 20:08:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.593
X-Spam-Level: 
X-Spam-Status: No, score=-106.593 tagged_above=-999 required=5 tests=[AWL=0.006, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qcoWH2Qw9eVr for <int-area@ietfa.amsl.com>; Wed, 17 Jul 2013 20:08:42 -0700 (PDT)
Received: from exprod7og121.obsmtp.com (exprod7og121.obsmtp.com [64.18.2.20]) by ietfa.amsl.com (Postfix) with ESMTP id F118021F99F6 for <int-area@ietf.org>; Wed, 17 Jul 2013 20:08:41 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob121.postini.com ([64.18.6.12]) with SMTP ID DSNKUedcOIyKmWCx43kcD6JaYT8L0qOgoX/t@postini.com; Wed, 17 Jul 2013 20:08:42 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 59ED21B8254 for <int-area@ietf.org>; Wed, 17 Jul 2013 20:08:40 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 37C48190060; Wed, 17 Jul 2013 20:08:40 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Wed, 17 Jul 2013 20:08:40 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Linda Dunbar <linda.dunbar@huawei.com>
Thread-Topic: New Version Notification for draft-nachum-sarp-06.txt
Thread-Index: AQHOgY51lpZYbJtUrUSb1ETRt8fCN5lmGefAgAQghgA=
Date: Thu, 18 Jul 2013 03:08:39 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077521753B@mbx-01.win.nominum.com>
References: <4A95BA014132FF49AE685FAB4B9F17F645B495AB@dfweml509-mbx.china.huawei.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F645B495AB@dfweml509-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <048F08DA9F75024586ABC49E99264416@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] New Version Notification for 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, 18 Jul 2013 03:08:55 -0000

On Jul 15, 2013, at 12:09 PM, Linda Dunbar <linda.dunbar@huawei.com> wrote:
> Many Thanks to Ted Lemon in asking many good questions and providing good=
 suggestion on the text. We have updated the draft based on Ted's input.=20

Thanks for taking some of my suggestions.   I still strongly advise you to =
be sensitive about the over-use of abbreviations, as I mentioned in a recen=
t email message.   A well-written, easily understood document is likely to =
get more review and more support than one that is difficult for new readers=
 to follow.


From mohamed.boucadair@orange.com  Thu Jul 18 02:13:50 2013
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6484021F91BF for <int-area@ietfa.amsl.com>; Thu, 18 Jul 2013 02:13:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7DyX1cLtkS66 for <int-area@ietfa.amsl.com>; Thu, 18 Jul 2013 02:13:46 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 0433421F8FF3 for <int-area@ietf.org>; Thu, 18 Jul 2013 02:13:45 -0700 (PDT)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm10.si.francetelecom.fr (ESMTP service) with ESMTP id 4933E2645FE; Thu, 18 Jul 2013 11:13:44 +0200 (CEST)
Received: from PUEXCH71.nanterre.francetelecom.fr (unknown [10.101.44.33]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id 2D2A027C054; Thu, 18 Jul 2013 11:13:44 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.233.200.25]) by PUEXCH71.nanterre.francetelecom.fr ([10.101.44.33]) with mapi; Thu, 18 Jul 2013 11:13:44 +0200
From: <mohamed.boucadair@orange.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "int-area@ietf.org" <int-area@ietf.org>
Date: Thu, 18 Jul 2013 11:13:42 +0200
Thread-Topic: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
Thread-Index: Ac6Bn0gbxl2mtmX2RumGmT6rK69PKgB822jg
Message-ID: <94C682931C08B048B7A8645303FDC9F36EE2DDB4FE@PUEXCB1B.nanterre.francetelecom.fr>
References: <92B7E61ADAC1BB4F941F943788C08828048B4221@xmb-aln-x08.cisco.com>
In-Reply-To: <92B7E61ADAC1BB4F941F943788C08828048B4221@xmb-aln-x08.cisco.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.7.1.45418
Subject: Re: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Jul 2013 09:13:50 -0000

Dear Charles, all,

The idea of an application sending flow characterization messages to the ne=
twork is interesting. This is an idea which is worth to be discussed and ch=
allenged. Thank you for writing this document.

The proposed framework makes sense in some contexts but I'm afraid it does =
not solve the limitations you listed in the document (e.g., avoid some clas=
sification functions in the network). The framework as it is won't simplify=
 the network side since in addition to legacy tools, a new function to inte=
rcept the flow characterization messages will be needed. The benefit of the=
 approach depends on the willing of application developers to signal the fl=
ow characteristic to the network.=20

IMHO, it would be useful if the document elaborates on deployment aspects a=
nd what are the facilitators to ease adoption of such approach. For example=
, why an application relying on HTTPS would sent a non-encrypted flow chara=
cterization message for analytic purposes? What is the role of a CPE in suc=
h model? How to trust the data sent by an application? These are examples o=
f points which should be further discussed in the document.=20

If the purpose of the document is not to claim the limitations you identifi=
ed will be mitigated but instead this framework is an additional tool at di=
sposal for implementers/operators/etc to ease service ordering and delivery=
, then a note should be added to the draft. This will be helpful to avoid a=
ny confusion.

Personally, I'm not a fun of solutions which requires explicit resource inv=
ocation before making use of a subscribed service. This mode should not be =
generalized (it does make sense if a very few services rely on that mode). =
I understand there are deployment cases which would rely on such mode but t=
his should be discussed in the document too.=20

I didn't understood well why the encoding is discussed in this document. Th=
e focus should be on the information model not data models (which are proto=
col-specific).

Cheers,
Med

>-----Message d'origine-----
>De=A0: int-area-bounces@ietf.org [mailto:int-area-bounces@ietf.org] De la
>part de Charles Eckel (eckelcu)
>Envoy=E9=A0: lundi 15 juillet 2013 23:07
>=C0=A0: int-area@ietf.org
>Objet=A0: [Int-area] FW: New Version Notification for draft-eckert-intarea=
-
>flow-metadata-framework-01.txt
>
>We have submitted and would appreciate comments on the following draft. It
>provides a framework for applications and network devices to communicate
>characteristics and service attributes for traffic flow. One aspect we
>anticipate to be of particular interest to this audience is the use of
>IPFIX in the information model we defined.
>
>Cheers,
>Charles
>
>-----Original Message-----
>From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>Sent: Monday, July 15, 2013 1:41 PM
>To: Toerless Eckert (eckert); Amine Choukir (amchouki); Reinaldo Penno
>(repenno); Charles Eckel (eckelcu)
>Subject: New Version Notification for draft-eckert-intarea-flow-metadata-
>framework-01.txt
>
>
>A new version of I-D, draft-eckert-intarea-flow-metadata-framework-01.txt
>has been successfully submitted by Toerless Eckert and posted to the
>IETF repository.
>
>Filename:	 draft-eckert-intarea-flow-metadata-framework
>Revision:	 01
>Title:		 A Framework for Signaling Flow Characteristics between
>Applications and the Network
>Creation date:	 2013-07-15
>Group:		 Individual Submission
>Number of pages: 17
>URL:             http://www.ietf.org/internet-drafts/draft-eckert-intarea-
>flow-metadata-framework-01.txt
>Status:          http://datatracker.ietf.org/doc/draft-eckert-intarea-flow=
-
>metadata-framework
>Htmlized:        http://tools.ietf.org/html/draft-eckert-intarea-flow-
>metadata-framework-01
>Diff:            http://www.ietf.org/rfcdiff?url2=3Ddraft-eckert-intarea-
>flow-metadata-framework-01
>
>Abstract:
>   This document provides a framework for communicating information
>   elements (a.k.a. metadata) in a consistent manner between
>   applications and the network to provide better visibility of
>   application flows, thereby enabling differentiated treatment of those
>   flows.  These information elements can be conveyed using various
>   signaling protocols, including PCP, RSVP, and STUN.
>
>
>
>
>The IETF Secretariat
>
>_______________________________________________
>Int-area mailing list
>Int-area@ietf.org
>https://www.ietf.org/mailman/listinfo/int-area

From repenno@cisco.com  Thu Jul 18 03:47:52 2013
Return-Path: <repenno@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 DFED021E80D9 for <int-area@ietfa.amsl.com>; Thu, 18 Jul 2013 03:47:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 0MgIM1ee1fht for <int-area@ietfa.amsl.com>; Thu, 18 Jul 2013 03:47:44 -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 5EA1E21E80D7 for <int-area@ietf.org>; Thu, 18 Jul 2013 03:47:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5851; q=dns/txt; s=iport; t=1374144464; x=1375354064; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=FG4uN1xWkq0HJqOqIduISUekgJV7Epwn7nL7DVFuJwc=; b=Quw/QaI5tSxrHaLTMEhWs1Cb6dFm0Sj4pgBsoVljIoD7sRxrDtEi2Pq/ zeQzTZCzzmgkGKIJmAhOJg0NBR36CGAvqQlrjhWxAOJpEjPVSn0VBfQyr 2fc6l3MJs+3sPgTyyyuTk846sZ397w+7czeFUt0XIcSKUoxdZ+rLFXPxK c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aj4FAE/G51GtJXHA/2dsb2JhbABagwY0SgbAPoEPFnSCIwEBAQEDAQEBawkOBgEIEQQBAQsZBC4LFAgBCAIEEwgBEod1BwWVeqBYj0cCOAaDB24DiG+QFpAkgVmBOYIo
X-IronPort-AV: E=Sophos;i="4.89,692,1367971200"; d="scan'208";a="236375516"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-5.cisco.com with ESMTP; 18 Jul 2013 10:47:43 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r6IAlhEf019333 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <int-area@ietf.org>; Thu, 18 Jul 2013 10:47:43 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.56]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.02.0318.004; Thu, 18 Jul 2013 05:47:43 -0500
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: "int-area@ietf.org" <int-area@ietf.org>
Thread-Topic: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
Thread-Index: AQHOg6Q6xl2mtmX2RumGmT6rK69PKg==
Date: Thu, 18 Jul 2013 10:47:42 +0000
Message-ID: <45A697A8FFD7CF48BCF2BE7E106F0604090C853C@xmb-rcd-x04.cisco.com>
In-Reply-To: <CE0D4AE3.18401%repenno@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.13.0.110805
x-originating-ip: [10.86.255.244]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <B9E5D58CBFFBC642ACF0B7207724E52D@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Jul 2013 10:47:53 -0000

Hi Med,

Thanks for your review. Inline with [RP]

On 7/18/13 6:13 AM, "mohamed.boucadair@orange.com"
<mohamed.boucadair@orange.com> wrote:

>Dear Charles, all,
>
>The idea of an application sending flow characterization messages to the
>network is interesting. This is an idea which is worth to be discussed
>and challenged. Thank you for writing this document.
>
>The proposed framework makes sense in some contexts but I'm afraid it
>does not solve the limitations you listed in the document (e.g., avoid
>some classification functions in the network). The framework as it is
>won't simplify the network side since in addition to legacy tools, a new
>function to intercept the flow characterization messages will be needed.

[RP] Interception is only needed with some transports. We should certainly
highlight that.

>The benefit of the approach depends on the willing of application
>developers to signal the flow characteristic to the network.


[RP] Yes. I believe this is somewhat a chicken and egg thing. Because such
functionality was never truly available in the network, there was no
incentive to applications developers.

>
>IMHO, it would be useful if the document elaborates on deployment aspects
>and what are the facilitators to ease adoption of such approach. For
>example, why an application relying on HTTPS would sent a non-encrypted
>flow characterization message for analytic purposes? What is the role of
>a CPE in such model?


[RP] I believe the end-point making the request for flow characteristics
will be the CPE in many cases where the applications is not metadata
aware. In other words, the CPE makes the request on behalf of applications.

>How to trust the data sent by an application? These are examples of
>points which should be further discussed in the document.


[RP] I think this depends on the transport. Some transports like PCP or
STUN have some built-in authentication.

>
>If the purpose of the document is not to claim the limitations you
>identified will be mitigated but instead this framework is an additional
>tool at disposal for implementers/operators/etc to ease service ordering
>and delivery, then a note should be added to the draft. This will be
>helpful to avoid any confusion.
>
>Personally, I'm not a fun of solutions which requires explicit resource
>invocation before making use of a subscribed service.


[RP] Me neither. I was hoping the draft did not come as that. The idea
here is that any metadata could be send before or after connection is
established and reservation is not required at all. In other words,
applications will work as always have but could request metadata service
if they so desire. If request is denied, everything continues to work as
is.


>This mode should not be generalized (it does make sense if a very few
>services rely on that mode). I understand there are deployment cases
>which would rely on such mode but this should be discussed in the
>document too.
>
>I didn't understood well why the encoding is discussed in this document.
>The focus should be on the information model not data models (which are
>protocol-specific).
>
>Cheers,
>Med


>>
>>>-----Message d'origine-----
>>>De : int-area-bounces@ietf.org [mailto:int-area-bounces@ietf.org] De la
>>>part de Charles Eckel (eckelcu)
>>>Envoy=E9 : lundi 15 juillet 2013 23:07
>>>=C0 : int-area@ietf.org
>>>Objet : [Int-area] FW: New Version Notification for
>>>draft-eckert-intarea-
>>>flow-metadata-framework-01.txt
>>>
>>>We have submitted and would appreciate comments on the following draft.
>>>It
>>>provides a framework for applications and network devices to communicate
>>>characteristics and service attributes for traffic flow. One aspect we
>>>anticipate to be of particular interest to this audience is the use of
>>>IPFIX in the information model we defined.
>>>
>>>Cheers,
>>>Charles
>>>
>>>-----Original Message-----
>>>From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>>>Sent: Monday, July 15, 2013 1:41 PM
>>>To: Toerless Eckert (eckert); Amine Choukir (amchouki); Reinaldo Penno
>>>(repenno); Charles Eckel (eckelcu)
>>>Subject: New Version Notification for
>>>draft-eckert-intarea-flow-metadata-
>>>framework-01.txt
>>>
>>>
>>>A new version of I-D,
>>>draft-eckert-intarea-flow-metadata-framework-01.txt
>>>has been successfully submitted by Toerless Eckert and posted to the
>>>IETF repository.
>>>
>>>Filename:	 draft-eckert-intarea-flow-metadata-framework
>>>Revision:	 01
>>>Title:		 A Framework for Signaling Flow Characteristics between
>>>Applications and the Network
>>>Creation date:	 2013-07-15
>>>Group:		 Individual Submission
>>>Number of pages: 17
>>>URL:           =20
>>>http://www.ietf.org/internet-drafts/draft-eckert-intarea-
>>>flow-metadata-framework-01.txt
>>>Status:        =20
>>>http://datatracker.ietf.org/doc/draft-eckert-intarea-flow-
>>>metadata-framework
>>>Htmlized:        http://tools.ietf.org/html/draft-eckert-intarea-flow-
>>>metadata-framework-01
>>>Diff:            http://www.ietf.org/rfcdiff?url2=3Ddraft-eckert-intarea=
-
>>>flow-metadata-framework-01
>>>
>>>Abstract:
>>>   This document provides a framework for communicating information
>>>   elements (a.k.a. metadata) in a consistent manner between
>>>   applications and the network to provide better visibility of
>>>   application flows, thereby enabling differentiated treatment of those
>>>   flows.  These information elements can be conveyed using various
>>>   signaling protocols, including PCP, RSVP, and STUN.
>>>
>>>
>>>
>>>
>>>The IETF Secretariat
>>>
>>>_______________________________________________
>>>Int-area mailing list
>>>Int-area@ietf.org
>>>https://www.ietf.org/mailman/listinfo/int-area
>


From mohamed.boucadair@orange.com  Thu Jul 18 05:11:39 2013
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C60611E812D for <int-area@ietfa.amsl.com>; Thu, 18 Jul 2013 05:11:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8M1jjkZGW8wV for <int-area@ietfa.amsl.com>; Thu, 18 Jul 2013 05:11:23 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 797C621E80C5 for <int-area@ietf.org>; Thu, 18 Jul 2013 05:11:23 -0700 (PDT)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id 9ACC23B4AC6; Thu, 18 Jul 2013 14:11:22 +0200 (CEST)
Received: from PUEXCH71.nanterre.francetelecom.fr (unknown [10.101.44.33]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id 792D427C067; Thu, 18 Jul 2013 14:11:22 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.233.200.25]) by PUEXCH71.nanterre.francetelecom.fr ([10.101.44.33]) with mapi; Thu, 18 Jul 2013 14:11:22 +0200
From: <mohamed.boucadair@orange.com>
To: "Reinaldo Penno (repenno)" <repenno@cisco.com>, "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "int-area@ietf.org" <int-area@ietf.org>
Date: Thu, 18 Jul 2013 14:11:21 +0200
Thread-Topic: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
Thread-Index: Ac6Bn0gbxl2mtmX2RumGmT6rK69PKgB822jgAAhZAoAAAX6WIA==
Message-ID: <94C682931C08B048B7A8645303FDC9F36EE2DDB59F@PUEXCB1B.nanterre.francetelecom.fr>
References: <94C682931C08B048B7A8645303FDC9F36EE2DDB4FE@PUEXCB1B.nanterre.francetelecom.fr> <45A697A8FFD7CF48BCF2BE7E106F0604090C8510@xmb-rcd-x04.cisco.com>
In-Reply-To: <45A697A8FFD7CF48BCF2BE7E106F0604090C8510@xmb-rcd-x04.cisco.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.7.18.100017
Subject: Re: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Jul 2013 12:11:39 -0000

Hi Reinaldo,=20

Please see inline.=20

Cheers,
Med

>-----Message d'origine-----
>De=A0: Reinaldo Penno (repenno) [mailto:repenno@cisco.com]
>Envoy=E9=A0: jeudi 18 juillet 2013 12:41
>=C0=A0: BOUCADAIR Mohamed OLNC/OLN; Charles Eckel (eckelcu); int-area@ietf=
.org
>Objet=A0: Re: [Int-area] FW: New Version Notification for draft-eckert-
>intarea-flow-metadata-framework-01.txt
>
>Hi Med,
>
>Thanks for your review. Inline with [RP]
>
>On 7/18/13 6:13 AM, "mohamed.boucadair@orange.com"
><mohamed.boucadair@orange.com> wrote:
>
>>Dear Charles, all,
>>
>>The idea of an application sending flow characterization messages to the
>>network is interesting. This is an idea which is worth to be discussed
>>and challenged. Thank you for writing this document.
>>
>>The proposed framework makes sense in some contexts but I'm afraid it
>>does not solve the limitations you listed in the document (e.g., avoid
>>some classification functions in the network). The framework as it is
>>won't simplify the network side since in addition to legacy tools, a new
>>function to intercept the flow characterization messages will be needed.
>
>[RP] Interception is only needed with some transports. We should certainly
>highlight that.
>
>>The benefit of the approach depends on the willing of application
>>developers to signal the flow characteristic to the network.
>
>
>[RP] Yes. I believe this is somewhat a chicken and egg thing. Because such
>functionality was never truly available in the network, there was no
>incentive to applications developers.
[Med] Makes sense. This is why I see this approach as a new tool in additio=
n to existing ones rather than presenting it will remove immediately some o=
f the limitations of current designs. This can be highlighted in the docume=
nt. =20

>
>>
>>
>>IMHO, it would be useful if the document elaborates on deployment aspects
>>and what are the facilitators to ease adoption of such approach. For
>>example, why an application relying on HTTPS would sent a non-encrypted
>>flow characterization message for analytic purposes? What is the role of
>>a CPE in such model?
>
>
>[RP] I believe the end-point making the request for flow characteristics
>will be the CPE in many cases where the applications is not metadata
>aware. In other words, the CPE makes the request on behalf of applications=
.
[Med] I'm more interested in this CPE flavor (managed CPE) since it avoids =
relying on applications to benefit from the added value of this approach. T=
his is worth be discussed in the document too.=20

>
>>How to trust the data sent by an application? These are examples of
>>points which should be further discussed in the document.
>
>
>[RP] I think this depends on the transport. Some transports like PCP or
>STUN have some built-in authentication.
[Med] The question is not whether a secure transport is used or not but to =
what extent the flow description is accurate (e.g., send fake flow descript=
ion, systematically request treatment with higher priority, etc.).

>
>>
>>
>>If the purpose of the document is not to claim the limitations you
>>identified will be mitigated but instead this framework is an additional
>>tool at disposal for implementers/operators/etc to ease service ordering
>>and delivery, then a note should be added to the draft. This will be
>>helpful to avoid any confusion.
>>
>>Personally, I'm not a fun of solutions which requires explicit resource
>>invocation before making use of a subscribed service.
>
>
>[RP] Me neither. I was hoping the draft did not come as that. The idea
>here is that any metadata could be send before or after connection is
>established and reservation is not required at all. In other words,
>applications will work as always have but could request metadata service
>if they so desire. If request is denied, everything continues to work as
>is.
>
>
>>This mode should not be generalized (it does make sense if a very few
>>services rely on that mode). I understand there are deployment cases
>>which would rely on such mode but this should be discussed in the
>>document too.
>>
>>I didn't understood well why the encoding is discussed in this document.
>>The focus should be on the information model not data models (which are
>>protocol-specific).
>>
>>Cheers,
>>Med
>>
>>>-----Message d'origine-----
>>>De : int-area-bounces@ietf.org [mailto:int-area-bounces@ietf.org] De la
>>>part de Charles Eckel (eckelcu)
>>>Envoy=E9 : lundi 15 juillet 2013 23:07
>>>=C0 : int-area@ietf.org
>>>Objet : [Int-area] FW: New Version Notification for draft-eckert-intarea=
-
>>>flow-metadata-framework-01.txt
>>>
>>>We have submitted and would appreciate comments on the following draft.
>>>It
>>>provides a framework for applications and network devices to communicate
>>>characteristics and service attributes for traffic flow. One aspect we
>>>anticipate to be of particular interest to this audience is the use of
>>>IPFIX in the information model we defined.
>>>
>>>Cheers,
>>>Charles
>>>
>>>-----Original Message-----
>>>From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>>>Sent: Monday, July 15, 2013 1:41 PM
>>>To: Toerless Eckert (eckert); Amine Choukir (amchouki); Reinaldo Penno
>>>(repenno); Charles Eckel (eckelcu)
>>>Subject: New Version Notification for draft-eckert-intarea-flow-metadata=
-
>>>framework-01.txt
>>>
>>>
>>>A new version of I-D, draft-eckert-intarea-flow-metadata-framework-01.tx=
t
>>>has been successfully submitted by Toerless Eckert and posted to the
>>>IETF repository.
>>>
>>>Filename:	 draft-eckert-intarea-flow-metadata-framework
>>>Revision:	 01
>>>Title:		 A Framework for Signaling Flow Characteristics between
>>>Applications and the Network
>>>Creation date:	 2013-07-15
>>>Group:		 Individual Submission
>>>Number of pages: 17
>>>URL:
>>>http://www.ietf.org/internet-drafts/draft-eckert-intarea-
>>>flow-metadata-framework-01.txt
>>>Status:
>>>http://datatracker.ietf.org/doc/draft-eckert-intarea-flow-
>>>metadata-framework
>>>Htmlized:        http://tools.ietf.org/html/draft-eckert-intarea-flow-
>>>metadata-framework-01
>>>Diff:            http://www.ietf.org/rfcdiff?url2=3Ddraft-eckert-intarea=
-
>>>flow-metadata-framework-01
>>>
>>>Abstract:
>>>   This document provides a framework for communicating information
>>>   elements (a.k.a. metadata) in a consistent manner between
>>>   applications and the network to provide better visibility of
>>>   application flows, thereby enabling differentiated treatment of those
>>>   flows.  These information elements can be conveyed using various
>>>   signaling protocols, including PCP, RSVP, and STUN.
>>>
>>>
>>>
>>>
>>>The IETF Secretariat
>>>
>>>_______________________________________________
>>>Int-area mailing list
>>>Int-area@ietf.org
>>>https://www.ietf.org/mailman/listinfo/int-area


From repenno@cisco.com  Thu Jul 18 03:41:29 2013
Return-Path: <repenno@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 75D8221E80E3 for <int-area@ietfa.amsl.com>; Thu, 18 Jul 2013 03:41:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 7A2GYE7F7vrX for <int-area@ietfa.amsl.com>; Thu, 18 Jul 2013 03:41:23 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 32FD021E80DE for <int-area@ietf.org>; Thu, 18 Jul 2013 03:41:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5778; q=dns/txt; s=iport; t=1374144083; x=1375353683; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=KjWULoOLdrwCgu+LM35LUtV0SgtqV138jQC4jThaMlg=; b=mUi5ZkQCARuqKrICQLYS2oqwqujA6pf/GQBYYBcJIzmKZudmaulihKfT mIqjlJWvbj2asWiNHKrhn43ftQRMXmTVUs/Mosz1F+zRm/zDtEes2vtsV y807qnkArA7DQXxX0xiRBDErGTpPw1VhRkmvZaJsLCEyK1H9eifATVQGB c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aj4FAM/E51GtJV2a/2dsb2JhbABagwY0SgbAPoEPFnSCIwEBAQEDAQEBawkOBgEIEQQBAQsZBC4LFAgBCAEBBAESCAESh3UHBbZWj0k4BoMHbgOIb5AWkCSBWYE5gig
X-IronPort-AV: E=Sophos;i="4.89,692,1367971200"; d="scan'208";a="236387208"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-6.cisco.com with ESMTP; 18 Jul 2013 10:41:22 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r6IAfMmU010846 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 18 Jul 2013 10:41:22 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.56]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.02.0318.004; Thu, 18 Jul 2013 05:41:21 -0500
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "int-area@ietf.org" <int-area@ietf.org>
Thread-Topic: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
Thread-Index: Ac6Bn0gbxl2mtmX2RumGmT6rK69PKgB822jgAAhZAoA=
Date: Thu, 18 Jul 2013 10:41:21 +0000
Message-ID: <45A697A8FFD7CF48BCF2BE7E106F0604090C8510@xmb-rcd-x04.cisco.com>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36EE2DDB4FE@PUEXCB1B.nanterre.francetelecom.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.13.0.110805
x-originating-ip: [10.86.255.244]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <83608707D0AA11408EC53565ACB912D4@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Thu, 18 Jul 2013 08:02:17 -0700
Subject: Re: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Jul 2013 10:41:29 -0000

Hi Med,

Thanks for your review. Inline with [RP]

On 7/18/13 6:13 AM, "mohamed.boucadair@orange.com"
<mohamed.boucadair@orange.com> wrote:

>Dear Charles, all,
>
>The idea of an application sending flow characterization messages to the
>network is interesting. This is an idea which is worth to be discussed
>and challenged. Thank you for writing this document.
>
>The proposed framework makes sense in some contexts but I'm afraid it
>does not solve the limitations you listed in the document (e.g., avoid
>some classification functions in the network). The framework as it is
>won't simplify the network side since in addition to legacy tools, a new
>function to intercept the flow characterization messages will be needed.

[RP] Interception is only needed with some transports. We should certainly
highlight that.

>The benefit of the approach depends on the willing of application
>developers to signal the flow characteristic to the network.


[RP] Yes. I believe this is somewhat a chicken and egg thing. Because such
functionality was never truly available in the network, there was no
incentive to applications developers.

>=20
>
>IMHO, it would be useful if the document elaborates on deployment aspects
>and what are the facilitators to ease adoption of such approach. For
>example, why an application relying on HTTPS would sent a non-encrypted
>flow characterization message for analytic purposes? What is the role of
>a CPE in such model?


[RP] I believe the end-point making the request for flow characteristics
will be the CPE in many cases where the applications is not metadata
aware. In other words, the CPE makes the request on behalf of applications.

>How to trust the data sent by an application? These are examples of
>points which should be further discussed in the document.


[RP] I think this depends on the transport. Some transports like PCP or
STUN have some built-in authentication.

>=20
>
>If the purpose of the document is not to claim the limitations you
>identified will be mitigated but instead this framework is an additional
>tool at disposal for implementers/operators/etc to ease service ordering
>and delivery, then a note should be added to the draft. This will be
>helpful to avoid any confusion.
>
>Personally, I'm not a fun of solutions which requires explicit resource
>invocation before making use of a subscribed service.


[RP] Me neither. I was hoping the draft did not come as that. The idea
here is that any metadata could be send before or after connection is
established and reservation is not required at all. In other words,
applications will work as always have but could request metadata service
if they so desire. If request is denied, everything continues to work as
is.=20


>This mode should not be generalized (it does make sense if a very few
>services rely on that mode). I understand there are deployment cases
>which would rely on such mode but this should be discussed in the
>document too.=20
>
>I didn't understood well why the encoding is discussed in this document.
>The focus should be on the information model not data models (which are
>protocol-specific).
>
>Cheers,
>Med
>
>>-----Message d'origine-----
>>De : int-area-bounces@ietf.org [mailto:int-area-bounces@ietf.org] De la
>>part de Charles Eckel (eckelcu)
>>Envoy=E9 : lundi 15 juillet 2013 23:07
>>=C0 : int-area@ietf.org
>>Objet : [Int-area] FW: New Version Notification for draft-eckert-intarea-
>>flow-metadata-framework-01.txt
>>
>>We have submitted and would appreciate comments on the following draft.
>>It
>>provides a framework for applications and network devices to communicate
>>characteristics and service attributes for traffic flow. One aspect we
>>anticipate to be of particular interest to this audience is the use of
>>IPFIX in the information model we defined.
>>
>>Cheers,
>>Charles
>>
>>-----Original Message-----
>>From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>>Sent: Monday, July 15, 2013 1:41 PM
>>To: Toerless Eckert (eckert); Amine Choukir (amchouki); Reinaldo Penno
>>(repenno); Charles Eckel (eckelcu)
>>Subject: New Version Notification for draft-eckert-intarea-flow-metadata-
>>framework-01.txt
>>
>>
>>A new version of I-D, draft-eckert-intarea-flow-metadata-framework-01.txt
>>has been successfully submitted by Toerless Eckert and posted to the
>>IETF repository.
>>
>>Filename:	 draft-eckert-intarea-flow-metadata-framework
>>Revision:	 01
>>Title:		 A Framework for Signaling Flow Characteristics between
>>Applications and the Network
>>Creation date:	 2013-07-15
>>Group:		 Individual Submission
>>Number of pages: 17
>>URL:            =20
>>http://www.ietf.org/internet-drafts/draft-eckert-intarea-
>>flow-metadata-framework-01.txt
>>Status:         =20
>>http://datatracker.ietf.org/doc/draft-eckert-intarea-flow-
>>metadata-framework
>>Htmlized:        http://tools.ietf.org/html/draft-eckert-intarea-flow-
>>metadata-framework-01
>>Diff:            http://www.ietf.org/rfcdiff?url2=3Ddraft-eckert-intarea-
>>flow-metadata-framework-01
>>
>>Abstract:
>>   This document provides a framework for communicating information
>>   elements (a.k.a. metadata) in a consistent manner between
>>   applications and the network to provide better visibility of
>>   application flows, thereby enabling differentiated treatment of those
>>   flows.  These information elements can be conveyed using various
>>   signaling protocols, including PCP, RSVP, and STUN.
>>
>>
>>
>>
>>The IETF Secretariat
>>
>>_______________________________________________
>>Int-area mailing list
>>Int-area@ietf.org
>>https://www.ietf.org/mailman/listinfo/int-area


From linda.dunbar@huawei.com  Thu Jul 18 08:36:32 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 244AF11E816F for <int-area@ietfa.amsl.com>; Thu, 18 Jul 2013 08:36:31 -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 GHWwuXiM4UZ7 for <int-area@ietfa.amsl.com>; Thu, 18 Jul 2013 08:36:20 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0D98821E813C for <int-area@ietf.org>; Thu, 18 Jul 2013 08:35:18 -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 AVE24690; Thu, 18 Jul 2013 15:35:01 +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, 18 Jul 2013 16:34:18 +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, 18 Jul 2013 16:34:59 +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, 18 Jul 2013 08:34:55 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: New Version Notification for draft-nachum-sarp-06.txt
Thread-Index: AQHOgY51lpZYbJtUrUSb1ETRt8fCN5lmGefAgAQghgCAAFrAEA==
Date: Thu, 18 Jul 2013 15:34:54 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F645B4ABF0@dfweml509-mbx.china.huawei.com>
References: <4A95BA014132FF49AE685FAB4B9F17F645B495AB@dfweml509-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B63077521753B@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077521753B@mbx-01.win.nominum.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.192.11.162]
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>
Subject: Re: [Int-area] New Version Notification for 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, 18 Jul 2013 15:36:32 -0000

Ted,=20

Thank you very much for the advice. We will clean up the acronyms in the ne=
xt revision.=20

Linda

> -----Original Message-----
> From: Ted Lemon [mailto:Ted.Lemon@nominum.com]
> Sent: Wednesday, July 17, 2013 10:09 PM
> To: Linda Dunbar
> Cc: Internet Area; Suresh Krishnan; Tal Mizrahi
> Subject: Re: New Version Notification for draft-nachum-sarp-06.txt
>=20
> On Jul 15, 2013, at 12:09 PM, Linda Dunbar <linda.dunbar@huawei.com>
> wrote:
> > Many Thanks to Ted Lemon in asking many good questions and providing
> good suggestion on the text. We have updated the draft based on Ted's
> input.
>=20
> Thanks for taking some of my suggestions.   I still strongly advise you
> to be sensitive about the over-use of abbreviations, as I mentioned in
> a recent email message.   A well-written, easily understood document is
> likely to get more review and more support than one that is difficult
> for new readers to follow.


From Ted.Lemon@nominum.com  Thu Jul 18 08:39:40 2013
Return-Path: <Ted.Lemon@nominum.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 5E79711E80FC for <int-area@ietfa.amsl.com>; Thu, 18 Jul 2013 08:39:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.593
X-Spam-Level: 
X-Spam-Status: No, score=-106.593 tagged_above=-999 required=5 tests=[AWL=0.006, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r02snfldpYOS for <int-area@ietfa.amsl.com>; Thu, 18 Jul 2013 08:39:33 -0700 (PDT)
Received: from exprod7og111.obsmtp.com (exprod7og111.obsmtp.com [64.18.2.175]) by ietfa.amsl.com (Postfix) with ESMTP id A0CF321F8DE3 for <int-area@ietf.org>; Thu, 18 Jul 2013 08:39:33 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob111.postini.com ([64.18.6.12]) with SMTP ID DSNKUegMNTpeGambKl1tV4jHC9ECk7qsqdFY@postini.com; Thu, 18 Jul 2013 08:39:33 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 52A411B81DA for <int-area@ietf.org>; Thu, 18 Jul 2013 08:39:33 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 4C328190060; Thu, 18 Jul 2013 08:39:33 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Thu, 18 Jul 2013 08:39:33 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Linda Dunbar <linda.dunbar@huawei.com>
Thread-Topic: New Version Notification for draft-nachum-sarp-06.txt
Thread-Index: AQHOgY51lpZYbJtUrUSb1ETRt8fCN5lmGefAgAQghgCAAFrAEIAAdw6A
Date: Thu, 18 Jul 2013 15:39:32 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077521823F@mbx-01.win.nominum.com>
References: <4A95BA014132FF49AE685FAB4B9F17F645B495AB@dfweml509-mbx.china.huawei.com> <8D23D4052ABE7A4490E77B1A012B63077521753B@mbx-01.win.nominum.com> <4A95BA014132FF49AE685FAB4B9F17F645B4ABF0@dfweml509-mbx.china.huawei.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F645B4ABF0@dfweml509-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2DEA43267F8B6C4FA0FFE474F76C401A@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] New Version Notification for 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, 18 Jul 2013 15:39:40 -0000

On Jul 18, 2013, at 8:34 AM, Linda Dunbar <linda.dunbar@huawei.com> wrote:
> Thank you very much for the advice. We will clean up the acronyms in the =
next revision.=20

Great, thanks!


From brian.e.carpenter@gmail.com  Thu Jul 18 12:58:40 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBBA411E81CE for <int-area@ietfa.amsl.com>; Thu, 18 Jul 2013 12:58:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.489
X-Spam-Level: 
X-Spam-Status: No, score=-102.489 tagged_above=-999 required=5 tests=[AWL=0.110, 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 iswl0INefKMw for <int-area@ietfa.amsl.com>; Thu, 18 Jul 2013 12:58:39 -0700 (PDT)
Received: from mail-pa0-x22d.google.com (mail-pa0-x22d.google.com [IPv6:2607:f8b0:400e:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 4BE3C21F9EF2 for <int-area@ietf.org>; Thu, 18 Jul 2013 12:58:39 -0700 (PDT)
Received: by mail-pa0-f45.google.com with SMTP id bg2so7067pad.32 for <int-area@ietf.org>; Thu, 18 Jul 2013 12:58:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=gUNqelaCiaqSFFPFrZpXrC9CiHZd7aVIeOHhrH64J88=; b=faqAqYGxbb27mBMo+Xuk5yJOJp2ywbkvp4BushhWGATIZkziPdUVw3dLwZkAABbnVV midj2Zhtin0iKIDcTE7X1oDw9y73rtBT1wUujaxa+mTL2ht2dkZ4WHBsyxYBwKcb7x2l W+0cFYKkPUdxlc2QxpG2JsfY2pUSgR5qDfr3SniEcvaucZAycNM2ghlz0hE1aiZX90ao 8FM6Igz5RMA57SOIER9C7BzkrD+ZJfwiiIU7IUHTi0pgs484PribOzW48kKwkA218zrY Ds0TNr7tWEwkqb1fCNi1avpRFSUc+DoR2k6CP0CDvRg0DwUBQnltQBPd1FBBKPlj9909 JXSA==
X-Received: by 10.68.171.99 with SMTP id at3mr13871721pbc.64.1374177519048; Thu, 18 Jul 2013 12:58:39 -0700 (PDT)
Received: from [192.168.178.23] (127.199.69.111.dynamic.snap.net.nz. [111.69.199.127]) by mx.google.com with ESMTPSA id is3sm9130280pbc.25.2013.07.18.12.58.36 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 18 Jul 2013 12:58:38 -0700 (PDT)
Message-ID: <51E848F4.9010003@gmail.com>
Date: Fri, 19 Jul 2013 07:58:44 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: mohamed.boucadair@orange.com
References: <94C682931C08B048B7A8645303FDC9F36EE2DDB4FE@PUEXCB1B.nanterre.francetelecom.fr>	<45A697A8FFD7CF48BCF2BE7E106F0604090C8510@xmb-rcd-x04.cisco.com> <94C682931C08B048B7A8645303FDC9F36EE2DDB59F@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36EE2DDB59F@PUEXCB1B.nanterre.francetelecom.fr>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Jul 2013 19:58:40 -0000

On 19/07/2013 00:11, mohamed.boucadair@orange.com wrote:
...
>>> How to trust the data sent by an application? These are examples of
>>> points which should be further discussed in the document.
>>
>> [RP] I think this depends on the transport. Some transports like PCP or
>> STUN have some built-in authentication.
> [Med] The question is not whether a secure transport is used or not but to what extent the flow description is accurate (e.g., send fake flow description, systematically request treatment with higher priority, etc.).

This of course is why the diffserv model assumes that traffic will
be reclassified at domain boundaries, since you can't trust what your
neighbour tells you about QoS requirements. This proposal would be no
different in the general case; flow metadata needs to be trustworthy.
If not it will be a recipe for theft of service or DoS.

Why is this an intarea topic? To my mind it fits in tsvwg, which is
currently discussing things like QoS for rtcweb.

   Brian

From eckelcu@cisco.com  Thu Jul 18 13:07:06 2013
Return-Path: <eckelcu@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 E85D821E80E3 for <int-area@ietfa.amsl.com>; Thu, 18 Jul 2013 13:07:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.513
X-Spam-Level: 
X-Spam-Status: No, score=-10.513 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 WABGPQiR7G3f for <int-area@ietfa.amsl.com>; Thu, 18 Jul 2013 13:07:01 -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 3C9AC11E8152 for <int-area@ietf.org>; Thu, 18 Jul 2013 13:07:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9095; q=dns/txt; s=iport; t=1374178020; x=1375387620; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=UndOVhhSbM+LKx+lPy1sbPlGW4F8AOqAWd1WvGbHm8Y=; b=KSABLFYe4m3jE9jqocQ9+miU2nsaRBdC15f4BUJqRsAp2u/AIalU1QLF HvHpcqLh4zrsq93HCEM3sy9mqSq35QJwQ3bi+R5ZDrdchYdsq3uorSd31 jMLr/jP10mqy/Z23FWhhh2OMHf1Xg8H9K5DEYBSskGR9Xkp+yplZMYS59 I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AikFADxK6FGtJV2Z/2dsb2JhbABagwY1SgbARoETFnSCJAEBAQEDAQEBawkOBAIBCBEEAQEBChkEBycLFAgBCAEBBAESCAESh3QBBwW2A49eOAaDCG4DiHCLFoUAkCSBWYE5gio
X-IronPort-AV: E=Sophos;i="4.89,696,1367971200"; d="scan'208";a="236626970"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-8.cisco.com with ESMTP; 18 Jul 2013 20:06:59 +0000
Received: from xhc-aln-x06.cisco.com (xhc-aln-x06.cisco.com [173.36.12.80]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r6IK6wPD021179 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 18 Jul 2013 20:06:58 GMT
Received: from xmb-aln-x08.cisco.com ([169.254.3.187]) by xhc-aln-x06.cisco.com ([173.36.12.80]) with mapi id 14.02.0318.004; Thu, 18 Jul 2013 15:06:58 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "Reinaldo Penno (repenno)" <repenno@cisco.com>, "int-area@ietf.org" <int-area@ietf.org>
Thread-Topic: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
Thread-Index: Ac6Bn0gbxl2mtmX2RumGmT6rK69PKgB822jgAAhZAoAAAX6WIAANU3hg
Date: Thu, 18 Jul 2013 20:06:57 +0000
Message-ID: <92B7E61ADAC1BB4F941F943788C08828048B669B@xmb-aln-x08.cisco.com>
References: <94C682931C08B048B7A8645303FDC9F36EE2DDB4FE@PUEXCB1B.nanterre.francetelecom.fr> <45A697A8FFD7CF48BCF2BE7E106F0604090C8510@xmb-rcd-x04.cisco.com> <94C682931C08B048B7A8645303FDC9F36EE2DDB59F@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36EE2DDB59F@PUEXCB1B.nanterre.francetelecom.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [171.68.16.40]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Jul 2013 20:07:07 -0000

Hi Med,

Thank you for your review and corresponding comments. Please see inline.

> -----Original Message-----
> From: mohamed.boucadair@orange.com
> [mailto:mohamed.boucadair@orange.com]
> Sent: Thursday, July 18, 2013 5:11 AM
> To: Reinaldo Penno (repenno); Charles Eckel (eckelcu); int-area@ietf.org
> Subject: RE: [Int-area] FW: New Version Notification for draft-eckert-int=
area-
> flow-metadata-framework-01.txt
>=20
> Hi Reinaldo,
>=20
> Please see inline.
>=20
> Cheers,
> Med
>=20
> >-----Message d'origine-----
> >De=A0: Reinaldo Penno (repenno) [mailto:repenno@cisco.com]
> >Envoy=E9=A0: jeudi 18 juillet 2013 12:41
> >=C0=A0: BOUCADAIR Mohamed OLNC/OLN; Charles Eckel (eckelcu); int-
> area@ietf.org
> >Objet=A0: Re: [Int-area] FW: New Version Notification for draft-eckert-
> >intarea-flow-metadata-framework-01.txt
> >
> >Hi Med,
> >
> >Thanks for your review. Inline with [RP]
> >
> >On 7/18/13 6:13 AM, "mohamed.boucadair@orange.com"
> ><mohamed.boucadair@orange.com> wrote:
> >
> >>Dear Charles, all,
> >>
> >>The idea of an application sending flow characterization messages to th=
e
> >>network is interesting. This is an idea which is worth to be discussed
> >>and challenged. Thank you for writing this document.
> >>
> >>The proposed framework makes sense in some contexts but I'm afraid it
> >>does not solve the limitations you listed in the document (e.g., avoid
> >>some classification functions in the network). The framework as it is
> >>won't simplify the network side since in addition to legacy tools, a ne=
w
> >>function to intercept the flow characterization messages will be needed=
.
> >
> >[RP] Interception is only needed with some transports. We should certain=
ly
> >highlight that.
> >
> >>The benefit of the approach depends on the willing of application
> >>developers to signal the flow characteristic to the network.
> >
> >
> >[RP] Yes. I believe this is somewhat a chicken and egg thing. Because su=
ch
> >functionality was never truly available in the network, there was no
> >incentive to applications developers.
> [Med] Makes sense. This is why I see this approach as a new tool in addit=
ion
> to existing ones rather than presenting it will remove immediately some o=
f the
> limitations of current designs. This can be highlighted in the document.

[cue] Good point. We do not expect or require all applications and network =
elements to start using this mechanism in order for it provide value. As yo=
u suggest, this is one more tool in the toolset, and it may be used in comb=
ination with other existing tools. We can certainly add text to clarify thi=
s.
=20
>=20
> >
> >>
> >>
> >>IMHO, it would be useful if the document elaborates on deployment aspec=
ts
> >>and what are the facilitators to ease adoption of such approach. For
> >>example, why an application relying on HTTPS would sent a non-encrypted
> >>flow characterization message for analytic purposes? What is the role o=
f
> >>a CPE in such model?
> >
> >
> >[RP] I believe the end-point making the request for flow characteristics
> >will be the CPE in many cases where the applications is not metadata
> >aware. In other words, the CPE makes the request on behalf of applicatio=
ns.
> [Med] I'm more interested in this CPE flavor (managed CPE) since it avoid=
s
> relying on applications to benefit from the added value of this approach.=
 This
> is worth be discussed in the document too.

[cue] Agreed. This is what we describe as "Proxy originated information" in=
 section 3.1.4.1 (http://tools.ietf.org/html/draft-eckert-intarea-flow-meta=
data-framework-01#section-3.1.4.1). Does this address your concern?


> >
> >>How to trust the data sent by an application? These are examples of
> >>points which should be further discussed in the document.
> >
> >
> >[RP] I think this depends on the transport. Some transports like PCP or
> >STUN have some built-in authentication.
> [Med] The question is not whether a secure transport is used or not but t=
o
> what extent the flow description is accurate (e.g., send fake flow descri=
ption,
> systematically request treatment with higher priority, etc.).

[cue] Section 3.1.4.2 (http://tools.ietf.org/html/draft-eckert-intarea-flow=
-metadata-framework-01#section-3.1.4.2) touches on the authentication requi=
rement, but we need to address authorization as well.   Applications may no=
t be authorized to request network resources, but instead authorization has=
 to first be obtained from a network element such as a call controller or p=
olicy element. We will add a discussion of this. As Reinaldo pointed out, t=
he transport may provide some mechanisms, but we plan to have mechanisms pr=
ovided within transport independent encoding as well (for additional detail=
s see http://tools.ietf.org/html/draft-choukir-tsvwg-flow-metadata-encoding=
-01#section-2.2.8).

Cheers,
Charles


> >>
> >>
> >>If the purpose of the document is not to claim the limitations you
> >>identified will be mitigated but instead this framework is an additiona=
l
> >>tool at disposal for implementers/operators/etc to ease service orderin=
g
> >>and delivery, then a note should be added to the draft. This will be
> >>helpful to avoid any confusion.
> >>
> >>Personally, I'm not a fun of solutions which requires explicit resource
> >>invocation before making use of a subscribed service.
> >
> >
> >[RP] Me neither. I was hoping the draft did not come as that. The idea
> >here is that any metadata could be send before or after connection is
> >established and reservation is not required at all. In other words,
> >applications will work as always have but could request metadata service
> >if they so desire. If request is denied, everything continues to work as
> >is.
> >
> >
> >>This mode should not be generalized (it does make sense if a very few
> >>services rely on that mode). I understand there are deployment cases
> >>which would rely on such mode but this should be discussed in the
> >>document too.
> >>
> >>I didn't understood well why the encoding is discussed in this document=
.
> >>The focus should be on the information model not data models (which are
> >>protocol-specific).
> >>
> >>Cheers,
> >>Med
> >>
> >>>-----Message d'origine-----
> >>>De : int-area-bounces@ietf.org [mailto:int-area-bounces@ietf.org] De l=
a
> >>>part de Charles Eckel (eckelcu)
> >>>Envoy=E9 : lundi 15 juillet 2013 23:07
> >>>=C0 : int-area@ietf.org
> >>>Objet : [Int-area] FW: New Version Notification for draft-eckert-intar=
ea-
> >>>flow-metadata-framework-01.txt
> >>>
> >>>We have submitted and would appreciate comments on the following draft=
.
> >>>It
> >>>provides a framework for applications and network devices to
> communicate
> >>>characteristics and service attributes for traffic flow. One aspect we
> >>>anticipate to be of particular interest to this audience is the use of
> >>>IPFIX in the information model we defined.
> >>>
> >>>Cheers,
> >>>Charles
> >>>
> >>>-----Original Message-----
> >>>From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> >>>Sent: Monday, July 15, 2013 1:41 PM
> >>>To: Toerless Eckert (eckert); Amine Choukir (amchouki); Reinaldo Penno
> >>>(repenno); Charles Eckel (eckelcu)
> >>>Subject: New Version Notification for draft-eckert-intarea-flow-metada=
ta-
> >>>framework-01.txt
> >>>
> >>>
> >>>A new version of I-D, draft-eckert-intarea-flow-metadata-framework-01.=
txt
> >>>has been successfully submitted by Toerless Eckert and posted to the
> >>>IETF repository.
> >>>
> >>>Filename:	 draft-eckert-intarea-flow-metadata-framework
> >>>Revision:	 01
> >>>Title:		 A Framework for Signaling Flow Characteristics between
> >>>Applications and the Network
> >>>Creation date:	 2013-07-15
> >>>Group:		 Individual Submission
> >>>Number of pages: 17
> >>>URL:
> >>>http://www.ietf.org/internet-drafts/draft-eckert-intarea-
> >>>flow-metadata-framework-01.txt
> >>>Status:
> >>>http://datatracker.ietf.org/doc/draft-eckert-intarea-flow-
> >>>metadata-framework
> >>>Htmlized:        http://tools.ietf.org/html/draft-eckert-intarea-flow-
> >>>metadata-framework-01
> >>>Diff:            http://www.ietf.org/rfcdiff?url2=3Ddraft-eckert-intar=
ea-
> >>>flow-metadata-framework-01
> >>>
> >>>Abstract:
> >>>   This document provides a framework for communicating information
> >>>   elements (a.k.a. metadata) in a consistent manner between
> >>>   applications and the network to provide better visibility of
> >>>   application flows, thereby enabling differentiated treatment of tho=
se
> >>>   flows.  These information elements can be conveyed using various
> >>>   signaling protocols, including PCP, RSVP, and STUN.
> >>>
> >>>
> >>>
> >>>
> >>>The IETF Secretariat
> >>>
> >>>_______________________________________________
> >>>Int-area mailing list
> >>>Int-area@ietf.org
> >>>https://www.ietf.org/mailman/listinfo/int-area


From repenno@cisco.com  Thu Jul 18 14:41:49 2013
Return-Path: <repenno@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 E84F411E8224 for <int-area@ietfa.amsl.com>; Thu, 18 Jul 2013 14:41:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 ui-GdFe7-NIe for <int-area@ietfa.amsl.com>; Thu, 18 Jul 2013 14:41:44 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 5F95B11E8227 for <int-area@ietf.org>; Thu, 18 Jul 2013 14:41:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=342; q=dns/txt; s=iport; t=1374183704; x=1375393304; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=INF2dECWFlrJOlVJ2E/P+X2aTNjOzBPDBlbdiLeGm7U=; b=iUfWoQjaRVLbHn4wqCi99F0T28R+rjD8GrqCiYo/z0FWMaine9zhkcpQ fs2sxRBCZjWXou/tArJ7s45KRH26FugC1j56kFz0nBkCcE6TVTV9pPVkf jV+FytbkJ+i3ST2o70jWVta/t5DyduGdq2PnYdYgAhz+v+OUPfk4cPBp5 I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhAFALxg6FGtJV2Y/2dsb2JhbABagwaBBcBGgRMWdIIkAQEBAQM6PQISAQgiFAUsERwJAQEEAQ0FCId2Aw+tMg2IXo0jgjsxB4MObgOVdI4QhSaBWYE5gio
X-IronPort-AV: E=Sophos;i="4.89,696,1367971200"; d="scan'208";a="236694120"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-3.cisco.com with ESMTP; 18 Jul 2013 21:41:33 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r6ILfXqU000553 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 18 Jul 2013 21:41:33 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.56]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.02.0318.004; Thu, 18 Jul 2013 16:41:33 -0500
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Thread-Topic: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
Thread-Index: Ac6Bn0gbxl2mtmX2RumGmT6rK69PKgB822jgAAhZAoAAAX6WIAAYQm8A///qawA=
Date: Thu, 18 Jul 2013 21:41:32 +0000
Message-ID: <45A697A8FFD7CF48BCF2BE7E106F0604090C8B4D@xmb-rcd-x04.cisco.com>
In-Reply-To: <51E848F4.9010003@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.13.0.110805
x-originating-ip: [10.86.248.169]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1A7B250955B98848A5D5FC83BE6AE9D5@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Jul 2013 21:41:50 -0000

Hi Brian,

Metadata has many uses and not just QoS.

Therefore we believe int-area to be appropriate. What are your thoughts?



On 7/18/13 4:58 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
wrote:

>Why is this an intarea topic? To my mind it fits in tsvwg, which is
>currently discussing things like QoS for rtcweb.
>


From brian.e.carpenter@gmail.com  Thu Jul 18 16:20:36 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FD9121E8145 for <int-area@ietfa.amsl.com>; Thu, 18 Jul 2013 16:20:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.498
X-Spam-Level: 
X-Spam-Status: No, score=-102.498 tagged_above=-999 required=5 tests=[AWL=0.101, 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 kqOSVMGFj9CW for <int-area@ietfa.amsl.com>; Thu, 18 Jul 2013 16:20:34 -0700 (PDT)
Received: from mail-pb0-x22a.google.com (mail-pb0-x22a.google.com [IPv6:2607:f8b0:400e:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 23C1821E8143 for <int-area@ietf.org>; Thu, 18 Jul 2013 16:20:34 -0700 (PDT)
Received: by mail-pb0-f42.google.com with SMTP id un1so3727953pbc.29 for <int-area@ietf.org>; Thu, 18 Jul 2013 16:20:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=1LoJEoYzX2UIy3WNHUEPlDXY19FLI9md73sRDoKrM5g=; b=bM6C92oshIBUIBYDxR0XV9vC9ZahINA5Fzh+CGKSIMIxoRU21w7M60BWWwPTXZYrT8 weGHkDs1uakFnJXmJU0WyKJHBBRVqPjnqiPfXCqvQL9dfZGGo55q1NeNof8/KlfTtR3Z PVyx/lAtNA3i01rF+nhsr1TiwZljtYtdNwTC7kIWP9MY/MoihLetrNgx3u10OhBZJSZK riw+i5vbeZTFyJpYygn/Y3Di/ODBXr0E1OKQ4EOdiyTwsmG9VE0ZpiLgBSMeJJ0xQZyM w4BFykSnULwKwPWzrC9JwSAgZuTMgvspr5+yu4qw9kTzZjtJVcrHVA5FF7CzpG/avSRk 6e7w==
X-Received: by 10.66.219.135 with SMTP id po7mr15516029pac.21.1374189633881; Thu, 18 Jul 2013 16:20:33 -0700 (PDT)
Received: from [192.168.178.23] (127.199.69.111.dynamic.snap.net.nz. [111.69.199.127]) by mx.google.com with ESMTPSA id sp4sm15897052pbc.45.2013.07.18.16.20.31 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 18 Jul 2013 16:20:33 -0700 (PDT)
Message-ID: <51E87848.2030805@gmail.com>
Date: Fri, 19 Jul 2013 11:20:40 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Reinaldo Penno (repenno)" <repenno@cisco.com>
References: <45A697A8FFD7CF48BCF2BE7E106F0604090C8B4D@xmb-rcd-x04.cisco.com>
In-Reply-To: <45A697A8FFD7CF48BCF2BE7E106F0604090C8B4D@xmb-rcd-x04.cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Jul 2013 23:20:36 -0000

On 19/07/2013 09:41, Reinaldo Penno (repenno) wrote:
> Hi Brian,
> 
> Metadata has many uses and not just QoS.

Sure, but some of them clearly concern layers above 3.

> 
> Therefore we believe int-area to be appropriate. What are your thoughts?

I think this is a case where early discussion in TSVWG would avoid
problems later. In the end the choice of WG doesn't matter as long as
cross-area issues are caught as soon as possible.

   Brian

> On 7/18/13 4:58 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
> wrote:
> 
>> Why is this an intarea topic? To my mind it fits in tsvwg, which is
>> currently discussing things like QoS for rtcweb.
>>
> 
> 

From eckert@cisco.com  Thu Jul 18 18:38:50 2013
Return-Path: <eckert@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 39B1621E8116 for <int-area@ietfa.amsl.com>; Thu, 18 Jul 2013 18:38:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.239
X-Spam-Level: 
X-Spam-Status: No, score=-10.239 tagged_above=-999 required=5 tests=[AWL=-0.195, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_OBFU_PRESENTLY=0.555]
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 UfUuEIN5keyC for <int-area@ietfa.amsl.com>; Thu, 18 Jul 2013 18:38:50 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 1333B21E80E8 for <int-area@ietf.org>; Thu, 18 Jul 2013 18:38:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1791; q=dns/txt; s=iport; t=1374197930; x=1375407530; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=uDZZZU5tZ18IBDKXgaEcHjEhpvzggb9I8ptS+ymbDY0=; b=K0/riN580PI8Oc5WaFhVEqsHXFZhaPGbTwuEc+y6Y+CYhEDFIuXia5OK DHxQ4ci6x81C/FSNlC6QdhT6SaEQus4phFq/xF5syMOVj2Vv+GQCuYx2Z 4p7bq1UEZX7URiKIkKJpdHcEZGZGDZh5NmoI7ZNyy3gj+UsnsWAZhIJnF 4=;
X-IronPort-AV: E=Sophos;i="4.89,697,1367971200"; d="scan'208";a="86422504"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-4.cisco.com with ESMTP; 19 Jul 2013 01:38:48 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r6J1clEA004233 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Jul 2013 01:38:47 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id r6J1clHd001627;  Thu, 18 Jul 2013 18:38:47 -0700
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id r6J1clDA001626; Thu, 18 Jul 2013 18:38:47 -0700
Date: Thu, 18 Jul 2013 18:38:47 -0700
From: Toerless Eckert <eckert@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <20130719013847.GA1589@cisco.com>
References: <45A697A8FFD7CF48BCF2BE7E106F0604090C8B4D@xmb-rcd-x04.cisco.com> <51E87848.2030805@gmail.com> <20130719013510.GI23170@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20130719013510.GI23170@cisco.com>
User-Agent: Mutt/1.4.2.2i
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Jul 2013 01:38:50 -0000

Brian,

Let me give you a comparison: I think DNS is a system with
a standardized data-model for information about specific objects,
primarily hosts and services. The result/action from using DNS is
most commonly some TCP connection(s). That does not make DNS a
TSV target. The metadata framework is in my eyes about a system
with a standardized data-model for traffic-flows and the result/action
is most commonly some form of QoS for the traffic flows. Go figure.

Having said this, we asked to preesent in TSVWG as well, but it does 
not seem as if it would get onto the TSVWG WG agenda. I think there 
would be good collaborators to be found from TSV because like DNS
i would expect that the folks interested in the actions taken
have an interest to build a data-model to make their actions easier.

Cheers
    Toerless

On Fri, Jul 19, 2013 at 11:20:40AM +1200, Brian E Carpenter wrote:
> On 19/07/2013 09:41, Reinaldo Penno (repenno) wrote:
> > Hi Brian,
> > 
> > Metadata has many uses and not just QoS.
> 
> Sure, but some of them clearly concern layers above 3.
> 
> > 
> > Therefore we believe int-area to be appropriate. What are your thoughts?
> 
> I think this is a case where early discussion in TSVWG would avoid
> problems later. In the end the choice of WG doesn't matter as long as
> cross-area issues are caught as soon as possible.
> 
>    Brian
> 
> > On 7/18/13 4:58 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
> > wrote:
> > 
> >> Why is this an intarea topic? To my mind it fits in tsvwg, which is
> >> currently discussing things like QoS for rtcweb.
> >>
> > 
> > 
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area

From eckert@cisco.com  Thu Jul 18 20:12:47 2013
Return-Path: <eckert@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 EF70D21E81A2 for <int-area@ietfa.amsl.com>; Thu, 18 Jul 2013 20:12:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.508
X-Spam-Level: 
X-Spam-Status: No, score=-10.508 tagged_above=-999 required=5 tests=[AWL=0.091, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 50fUIYpCoRln for <int-area@ietfa.amsl.com>; Thu, 18 Jul 2013 20:12:42 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id CB56C21E818D for <int-area@ietf.org>; Thu, 18 Jul 2013 20:12:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1547; q=dns/txt; s=iport; t=1374203559; x=1375413159; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=K9tePYrayK7jcVamDfVBrcrrhbAYzIl965PNfBE3dvg=; b=b+7INcjPbuqchQux3mItCUFrUF9vNv25g8S253xhUhuI336rBSZk7PNf TRGlhFLYUG1aV7Cg7ZKaiLSiCFRWbqBz1aKc7qWCy1ONw7Na3Q2DiqU3t BO2W/XYeWHxtTgeJIyDIsBj75mAn8RUDVCy0H9+h7Tuk8DvpsDYjDBkqS Y=;
X-IronPort-AV: E=Sophos;i="4.89,698,1367971200"; d="scan'208";a="83412585"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-1.cisco.com with ESMTP; 19 Jul 2013 03:12:38 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r6J3CcQi018093 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Jul 2013 03:12:38 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id r6J3CbmG004954;  Thu, 18 Jul 2013 20:12:37 -0700
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id r6J3CbCT004953; Thu, 18 Jul 2013 20:12:37 -0700
Date: Thu, 18 Jul 2013 20:12:37 -0700
From: Toerless Eckert <eckert@cisco.com>
To: mohamed.boucadair@orange.com
Message-ID: <20130719031237.GM23170@cisco.com>
References: <94C682931C08B048B7A8645303FDC9F36EE2DDB4FE@PUEXCB1B.nanterre.francetelecom.fr> <45A697A8FFD7CF48BCF2BE7E106F0604090C8510@xmb-rcd-x04.cisco.com> <94C682931C08B048B7A8645303FDC9F36EE2DDB59F@PUEXCB1B.nanterre.francetelecom.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36EE2DDB59F@PUEXCB1B.nanterre.francetelecom.fr>
User-Agent: Mutt/1.4.2.2i
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Jul 2013 03:12:48 -0000

On Thu, Jul 18, 2013 at 02:11:21PM +0200, mohamed.boucadair@orange.com wrote:
> >[RP] I believe the end-point making the request for flow characteristics
> >will be the CPE in many cases where the applications is not metadata
> >aware. In other words, the CPE makes the request on behalf of applications.
> [Med] I'm more interested in this CPE flavor (managed CPE) since it avoids relying on applications to benefit from the added value of this approach. This is worth be discussed in the document too. 

See section 3.1.4.1 which talks about proxies. The problem really is where
the proxied information comes from. If the proxy is doing DPI inspection to
deduce it or some configured mappings, then it's likely going to be unreliable
(encryption) or suffer from problems in getting it provisioned.

To me these inspecting proxies are a way to get a foot in the door with
the method while it takes its time to persuade app-developers (or middleware
like browsers) to signal the information explicitly (couple of years ?...).

> [Med] The question is not whether a secure transport is used or not but to what extent the flow description is accurate (e.g., send fake flow description, systematically request treatment with higher priority, etc.).

Right. That was the intention of 3.1.4.2. Ultimately the network taking
action on the metadata needs to trust the authenticated identity
associated with the attributes to not lie about the attributes - OR
enforce the semantic of the attributes signalled.

Cheers
    Toerless

From eckert@cisco.com  Thu Jul 18 20:40:12 2013
Return-Path: <eckert@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 D481011E8279 for <int-area@ietfa.amsl.com>; Thu, 18 Jul 2013 20:40:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.512
X-Spam-Level: 
X-Spam-Status: No, score=-10.512 tagged_above=-999 required=5 tests=[AWL=0.087, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 Tcd+ZX5FWaeh for <int-area@ietfa.amsl.com>; Thu, 18 Jul 2013 20:40:07 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 95F4711E8276 for <int-area@ietf.org>; Thu, 18 Jul 2013 20:40:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1196; q=dns/txt; s=iport; t=1374205207; x=1375414807; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=rj/L2ll7w4Ab6qhK/UxOmhRvkoCAf2vnbnjNLuIww9g=; b=FmF61BWpWiSOiO1GK+l+hzTvXKTGc4Kq1CjHvbYa9ftKLmdVu5Ng+I77 e2QJJYDAMCW1T6IkpP7iHP/8R/UUQIrKZs0sVCk3aveHG3cUQUq4OemKj kXwixweA7PV0Z1+aMGB4k8/7eMhnP6urmwjt50fI6J2Jz38hokIRyBT+q w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAKS06FGrRDoJ/2dsb2JhbABagwbBSYEVFnSCJAEBAQMBOj0CBQsLIQwZDwU6O4dxBbZLkA8HCgyDZgOJKI40AZFNgVmBWRyBLCQ
X-IronPort-AV: E=Sophos;i="4.89,698,1367971200"; d="scan'208";a="83413536"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-1.cisco.com with ESMTP; 19 Jul 2013 03:40:04 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by mtv-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r6J3e4C0026292 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Jul 2013 03:40:04 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id r6J3e4Mf005918;  Thu, 18 Jul 2013 20:40:04 -0700
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id r6J3e4gm005917; Thu, 18 Jul 2013 20:40:04 -0700
Date: Thu, 18 Jul 2013 20:40:04 -0700
From: Toerless Eckert <eckert@cisco.com>
To: mohamed.boucadair@orange.com
Message-ID: <20130719034004.GP23170@cisco.com>
References: <94C682931C08B048B7A8645303FDC9F36EE2DDB4FE@PUEXCB1B.nanterre.francetelecom.fr> <45A697A8FFD7CF48BCF2BE7E106F0604090C8510@xmb-rcd-x04.cisco.com> <94C682931C08B048B7A8645303FDC9F36EE2DDB59F@PUEXCB1B.nanterre.francetelecom.fr> <20130719031237.GM23170@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20130719031237.GM23170@cisco.com>
User-Agent: Mutt/1.4.2.2i
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Jul 2013 03:40:13 -0000

Btw: I wrote something about proxies i would like to amend:

> See section 3.1.4.1 which talks about proxies. The problem really is where
> the proxied information comes from. If the proxy is doing DPI inspection to
> deduce it or some configured mappings, then it's likely going to be unreliable
> (encryption) or suffer from problems in getting it provisioned.

In a prior life, we IETF standardized IP Multicast SSM which does require
application upgrade (signal S,G), and then we and other vendors implemented
what we call "SSM mapping" to work around that (not requiring application
update). Call it an SSM proxy. No vendor brought this into the IETF
because we always wanted to see this positioned as a temporary transition
technology and not make it too attractive to run forever. 

Now, you don't want to know what really is deployed in networks and what
strategies customer apply. Lets just say that SSM mapping is very successfull.

So, to a degree you can account my above paragraph either as 
"famous last words" or "don't give up the good fight". So i am all for
standardizing any proxy methods the IETF thinks makes sense to standardize.

Cheers
    Toerless

From brian.e.carpenter@gmail.com  Thu Jul 18 21:14:58 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C5E821E819E for <int-area@ietfa.amsl.com>; Thu, 18 Jul 2013 21:14:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.224
X-Spam-Level: 
X-Spam-Status: No, score=-102.224 tagged_above=-999 required=5 tests=[AWL=-0.180, BAYES_00=-2.599, SARE_OBFU_PRESENTLY=0.555, 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 ckSwN659kqrC for <int-area@ietfa.amsl.com>; Thu, 18 Jul 2013 21:14:58 -0700 (PDT)
Received: from mail-pd0-x230.google.com (mail-pd0-x230.google.com [IPv6:2607:f8b0:400e:c02::230]) by ietfa.amsl.com (Postfix) with ESMTP id 1E75211E8276 for <int-area@ietf.org>; Thu, 18 Jul 2013 21:14:58 -0700 (PDT)
Received: by mail-pd0-f176.google.com with SMTP id t12so3765789pdi.7 for <int-area@ietf.org>; Thu, 18 Jul 2013 21:14:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=NztcM9274whLT/WoYkKVHelNA3o+BLZVKDnvE+2+DO4=; b=xi57OTsXtzupMCa5N+16Rs1Sb2LEPuF6RvQxgYnuqqVKoVVdQdAFf8vwaDRIm9DAiD CSUzVLxMMN3hLyBQ3h+dTthEghG5E4WTj05tRE776TjdiGAyiOyOqcSnUynQQ0NSHy6x qexvTuGPqp68ouJ8PVPuzhzu2hB+BrZA61Sre3obxLS+ceBz66jGEO1rXjhccppBMnEP Ct3AuUkGtT/LdP0qt0h+W66ZIEvNaRIXdM+DD7H9Rtd13O9BoYD6t5bAeGu+Q32SoCLl 6690v3XsKoveBGmtYyhbhP5TbvG2PBUH3tUv8p2Cc/K/UKdCmEwOVHga3mE1HXhNOJ4x GJtQ==
X-Received: by 10.68.43.8 with SMTP id s8mr15243350pbl.139.1374207297835; Thu, 18 Jul 2013 21:14:57 -0700 (PDT)
Received: from [192.168.178.23] (127.199.69.111.dynamic.snap.net.nz. [111.69.199.127]) by mx.google.com with ESMTPSA id w8sm14288627pab.12.2013.07.18.21.14.55 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 18 Jul 2013 21:14:57 -0700 (PDT)
Message-ID: <51E8BD49.1050109@gmail.com>
Date: Fri, 19 Jul 2013 16:15:05 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Toerless Eckert <eckert@cisco.com>
References: <45A697A8FFD7CF48BCF2BE7E106F0604090C8B4D@xmb-rcd-x04.cisco.com> <51E87848.2030805@gmail.com> <20130719013510.GI23170@cisco.com>
In-Reply-To: <20130719013510.GI23170@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Jul 2013 04:14:58 -0000

On 19/07/2013 13:35, Toerless Eckert wrote:
> Brian,
> 
> Let me give you a comparison: I think DNS is a system with
> a standardized data-model for information about specific objects,
> primarily hosts and services. The result/action from using DNS is
> most commonly some TCP connection(s). That does not make DNS a
> TSV target. The metadata framework is in my eyes about a system
> with a standardized data-model for traffic-flows and the result/action
> is most commonly some form of QoS for the traffic flows. Go figure.

Well, yes, and flow handling and QoS seems to be a regular topic in
the Transport area. Diffserv and Intserv were both developed in
the Transport area. It's a shame if they aren't aware of this work.

    Brian

> Having said this, we asked to preesent in TSVWG as well, but it does 
> not seem as if it would get onto the TSVWG WG agenda. I think there 
> would be good collaborators to be found from TSV because like DNS
> i would expect that the folks interested in the actions taken
> have an interest to build a data-model to make their actions easier.
> 
> Cheers
>     Toerless
> 
> On Fri, Jul 19, 2013 at 11:20:40AM +1200, Brian E Carpenter wrote:
>> On 19/07/2013 09:41, Reinaldo Penno (repenno) wrote:
>>> Hi Brian,
>>>
>>> Metadata has many uses and not just QoS.
>> Sure, but some of them clearly concern layers above 3.
>>
>>> Therefore we believe int-area to be appropriate. What are your thoughts?
>> I think this is a case where early discussion in TSVWG would avoid
>> problems later. In the end the choice of WG doesn't matter as long as
>> cross-area issues are caught as soon as possible.
>>
>>    Brian
>>
>>> On 7/18/13 4:58 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
>>> wrote:
>>>
>>>> Why is this an intarea topic? To my mind it fits in tsvwg, which is
>>>> currently discussing things like QoS for rtcweb.
>>>>
>>>
>> _______________________________________________
>> Int-area mailing list
>> Int-area@ietf.org
>> https://www.ietf.org/mailman/listinfo/int-area
> .
> 

From mohamed.boucadair@orange.com  Fri Jul 19 00:08:37 2013
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 917A721E8094 for <int-area@ietfa.amsl.com>; Fri, 19 Jul 2013 00:08:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8lTOD9O1-W8n for <int-area@ietfa.amsl.com>; Fri, 19 Jul 2013 00:08:33 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id 4B0CE21F9A26 for <int-area@ietf.org>; Fri, 19 Jul 2013 00:08:32 -0700 (PDT)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm14.si.francetelecom.fr (ESMTP service) with ESMTP id EB51822D3AE; Fri, 19 Jul 2013 09:08:30 +0200 (CEST)
Received: from PUEXCH81.nanterre.francetelecom.fr (unknown [10.101.44.34]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id C138435C05B; Fri, 19 Jul 2013 09:08:30 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.233.200.25]) by PUEXCH81.nanterre.francetelecom.fr ([10.101.44.34]) with mapi; Fri, 19 Jul 2013 09:08:30 +0200
From: <mohamed.boucadair@orange.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "Reinaldo Penno (repenno)" <repenno@cisco.com>, "int-area@ietf.org" <int-area@ietf.org>
Date: Fri, 19 Jul 2013 09:08:29 +0200
Thread-Topic: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
Thread-Index: Ac6Bn0gbxl2mtmX2RumGmT6rK69PKgB822jgAAhZAoAAAX6WIAANU3hgABdWeIA=
Message-ID: <94C682931C08B048B7A8645303FDC9F36EE2DDB748@PUEXCB1B.nanterre.francetelecom.fr>
References: <94C682931C08B048B7A8645303FDC9F36EE2DDB4FE@PUEXCB1B.nanterre.francetelecom.fr> <45A697A8FFD7CF48BCF2BE7E106F0604090C8510@xmb-rcd-x04.cisco.com> <94C682931C08B048B7A8645303FDC9F36EE2DDB59F@PUEXCB1B.nanterre.francetelecom.fr> <92B7E61ADAC1BB4F941F943788C08828048B669B@xmb-aln-x08.cisco.com>
In-Reply-To: <92B7E61ADAC1BB4F941F943788C08828048B669B@xmb-aln-x08.cisco.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.7.19.42417
Subject: Re: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Jul 2013 07:08:37 -0000

Hi Charles,=20

Please see inline.
Cheers,
Med

>-----Message d'origine-----
>De=A0: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
>Envoy=E9=A0: jeudi 18 juillet 2013 22:07
>=C0=A0: BOUCADAIR Mohamed OLNC/OLN; Reinaldo Penno (repenno); int-area@iet=
f.org
>Objet=A0: RE: [Int-area] FW: New Version Notification for draft-eckert-
>intarea-flow-metadata-framework-01.txt
>
>Hi Med,
>
>Thank you for your review and corresponding comments. Please see inline.
>
>> -----Original Message-----
>> From: mohamed.boucadair@orange.com
>> [mailto:mohamed.boucadair@orange.com]
>> Sent: Thursday, July 18, 2013 5:11 AM
>> To: Reinaldo Penno (repenno); Charles Eckel (eckelcu); int-area@ietf.org
>> Subject: RE: [Int-area] FW: New Version Notification for draft-eckert-
>intarea-
>> flow-metadata-framework-01.txt
>>
>> >>
>> >>IMHO, it would be useful if the document elaborates on deployment
>aspects
>> >>and what are the facilitators to ease adoption of such approach. For
>> >>example, why an application relying on HTTPS would sent a non-encrypte=
d
>> >>flow characterization message for analytic purposes? What is the role
>of
>> >>a CPE in such model?
>> >
>> >
>> >[RP] I believe the end-point making the request for flow characteristic=
s
>> >will be the CPE in many cases where the applications is not metadata
>> >aware. In other words, the CPE makes the request on behalf of
>applications.
>> [Med] I'm more interested in this CPE flavor (managed CPE) since it
>avoids
>> relying on applications to benefit from the added value of this approach=
.
>This
>> is worth be discussed in the document too.
>
>[cue] Agreed. This is what we describe as "Proxy originated information" i=
n
>section 3.1.4.1 (http://tools.ietf.org/html/draft-eckert-intarea-flow-
>metadata-framework-01#section-3.1.4.1). Does this address your concern?

[Med] Yes and No. I would prefer if concrete deployment examples are discus=
sed (e.g., managed CPE for instance).=20


From mohamed.boucadair@orange.com  Fri Jul 19 00:57:52 2013
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F84921E810A for <int-area@ietfa.amsl.com>; Fri, 19 Jul 2013 00:57:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SPwC9PGGQJ0k for <int-area@ietfa.amsl.com>; Fri, 19 Jul 2013 00:57:47 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id CD85311E80F5 for <int-area@ietf.org>; Fri, 19 Jul 2013 00:57:46 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm09.si.francetelecom.fr (ESMTP service) with ESMTP id 41C562DC2CC; Fri, 19 Jul 2013 09:57:46 +0200 (CEST)
Received: from puexch31.nanterre.francetelecom.fr (unknown [10.101.44.29]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 1F31923806E; Fri, 19 Jul 2013 09:57:46 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.233.200.25]) by puexch31.nanterre.francetelecom.fr ([10.101.44.29]) with mapi; Fri, 19 Jul 2013 09:57:45 +0200
From: <mohamed.boucadair@orange.com>
To: Toerless Eckert <eckert@cisco.com>
Date: Fri, 19 Jul 2013 09:57:44 +0200
Thread-Topic: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
Thread-Index: Ac6ELdUBUd4pHoqQRQqubi9dAsh31wAIUaow
Message-ID: <94C682931C08B048B7A8645303FDC9F36EE2DDB790@PUEXCB1B.nanterre.francetelecom.fr>
References: <94C682931C08B048B7A8645303FDC9F36EE2DDB4FE@PUEXCB1B.nanterre.francetelecom.fr> <45A697A8FFD7CF48BCF2BE7E106F0604090C8510@xmb-rcd-x04.cisco.com> <94C682931C08B048B7A8645303FDC9F36EE2DDB59F@PUEXCB1B.nanterre.francetelecom.fr> <20130719031237.GM23170@cisco.com>
In-Reply-To: <20130719031237.GM23170@cisco.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.5.21.113319
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Jul 2013 07:57:52 -0000

Dear Toerless,

Please see inline.=20

Cheers,
Med

>-----Message d'origine-----
>De=A0: Toerless Eckert [mailto:eckert@cisco.com]
>Envoy=E9=A0: vendredi 19 juillet 2013 05:13
>=C0=A0: BOUCADAIR Mohamed OLNC/OLN
>Cc=A0: Reinaldo Penno (repenno); Charles Eckel (eckelcu); int-area@ietf.or=
g
>Objet=A0: Re: [Int-area] FW: New Version Notification for draft-eckert-
>intarea-flow-metadata-framework-01.txt
>
>On Thu, Jul 18, 2013 at 02:11:21PM +0200, mohamed.boucadair@orange.com
>wrote:
>> >[RP] I believe the end-point making the request for flow characteristic=
s
>> >will be the CPE in many cases where the applications is not metadata
>> >aware. In other words, the CPE makes the request on behalf of
>applications.
>> [Med] I'm more interested in this CPE flavor (managed CPE) since it
>avoids relying on applications to benefit from the added value of this
>approach. This is worth be discussed in the document too.
>
>See section 3.1.4.1 which talks about proxies. The problem really is where
>the proxied information comes from. If the proxy is doing DPI inspection t=
o
>deduce it or some configured mappings, then it's likely going to be
>unreliable
>(encryption) or suffer from problems in getting it provisioned.

[Med] Section 3.1.4.1 as it is does not provide decent discussion of these =
deployment issues and considerations. Sketching the expected behavior of su=
ch intermediary functions would even be better. This applies also for the o=
ther deployment-related issues I listed in my initial e-mail.

>
>To me these inspecting proxies are a way to get a foot in the door with
>the method while it takes its time to persuade app-developers (or
>middleware
>like browsers) to signal the information explicitly (couple of years ?...)=
.
>
>> [Med] The question is not whether a secure transport is used or not but
>to what extent the flow description is accurate (e.g., send fake flow
>description, systematically request treatment with higher priority, etc.).
>
>Right. That was the intention of 3.1.4.2. Ultimately the network taking
>action on the metadata needs to trust the authenticated identity
>associated with the attributes to not lie about the attributes - OR
>enforce the semantic of the attributes signalled.
>
[Med] this discussion about trust is worth to be elaborated further in the =
document. For sure, this point will be raised by others.

>Cheers
>    Toerless

From repenno@cisco.com  Fri Jul 19 04:33:08 2013
Return-Path: <repenno@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 B938611E80F8 for <int-area@ietfa.amsl.com>; Fri, 19 Jul 2013 04:33:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 nKMqDoP4sq8l for <int-area@ietfa.amsl.com>; Fri, 19 Jul 2013 04:33:01 -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 B979A21E80A6 for <int-area@ietf.org>; Fri, 19 Jul 2013 04:33:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2839; q=dns/txt; s=iport; t=1374233581; x=1375443181; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=yRr9jVkNpNCP/7tKcpRbZTlh2HqOQRv4AkW3azYdsf0=; b=CYhYA7P9ZU4URPjaKud1xyMbPe1eFXnT9a4SpMcxNcwmQXcnnmC06FGy 2xatVy8VNg8W+qIpd+/d/WYRJrYaa8gR1Ebol1KY18baZJLioH6scOOev N00NefN35qA9Gb1TPcqzabWxaYwBiEZ4XZKXO482UfBaQpFpXr52G1Vqz I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFAIYj6VGtJV2c/2dsb2JhbABRCYMGgQXARoEQFnSCJAEBAQR3AhIBCCIZBDkUCAkCBAENBQiICLZWjlQJgQExB4MQbgOIcKA6gVmBOYFxOQ
X-IronPort-AV: E=Sophos;i="4.89,700,1367971200"; d="scan'208";a="236890154"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-5.cisco.com with ESMTP; 19 Jul 2013 11:33:01 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r6JBX1w8031366 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 19 Jul 2013 11:33:01 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.56]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.02.0318.004; Fri, 19 Jul 2013 06:33:00 -0500
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "Toerless Eckert (eckert)" <eckert@cisco.com>
Thread-Topic: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
Thread-Index: Ac6Bn0gbxl2mtmX2RumGmT6rK69PKgB822jgAAhZAoAAAX6WIAAnaaeAAAn1JAAAATsDAA==
Date: Fri, 19 Jul 2013 11:33:00 +0000
Message-ID: <45A697A8FFD7CF48BCF2BE7E106F0604090C9E94@xmb-rcd-x04.cisco.com>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36EE2DDB790@PUEXCB1B.nanterre.francetelecom.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.13.0.110805
x-originating-ip: [10.86.247.83]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <16FA8F4625DB934BAD471EF2ED0A6D1C@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Jul 2013 11:33:08 -0000

Hi Med,

I agree with you that we need to cover in more detail the managed CPE
deployments but I wonder if this is the best document to do it.

Maybe a use-cases draft based on very concrete scenarios would be best.

Thanks,

Reinaldo


On 7/19/13 4:57 AM, "mohamed.boucadair@orange.com"
<mohamed.boucadair@orange.com> wrote:

>Dear Toerless,
>
>Please see inline.
>
>Cheers,
>Med
>
>>-----Message d'origine-----
>>De : Toerless Eckert [mailto:eckert@cisco.com]
>>Envoy=E9 : vendredi 19 juillet 2013 05:13
>>=C0 : BOUCADAIR Mohamed OLNC/OLN
>>Cc : Reinaldo Penno (repenno); Charles Eckel (eckelcu); int-area@ietf.org
>>Objet : Re: [Int-area] FW: New Version Notification for draft-eckert-
>>intarea-flow-metadata-framework-01.txt
>>
>>On Thu, Jul 18, 2013 at 02:11:21PM +0200, mohamed.boucadair@orange.com
>>wrote:
>>> >[RP] I believe the end-point making the request for flow
>>>characteristics
>>> >will be the CPE in many cases where the applications is not metadata
>>> >aware. In other words, the CPE makes the request on behalf of
>>applications.
>>> [Med] I'm more interested in this CPE flavor (managed CPE) since it
>>avoids relying on applications to benefit from the added value of this
>>approach. This is worth be discussed in the document too.
>>
>>See section 3.1.4.1 which talks about proxies. The problem really is
>>where
>>the proxied information comes from. If the proxy is doing DPI inspection
>>to
>>deduce it or some configured mappings, then it's likely going to be
>>unreliable
>>(encryption) or suffer from problems in getting it provisioned.
>
>[Med] Section 3.1.4.1 as it is does not provide decent discussion of
>these deployment issues and considerations. Sketching the expected
>behavior of such intermediary functions would even be better. This
>applies also for the other deployment-related issues I listed in my
>initial e-mail.
>
>>
>>To me these inspecting proxies are a way to get a foot in the door with
>>the method while it takes its time to persuade app-developers (or
>>middleware
>>like browsers) to signal the information explicitly (couple of years
>>?...).
>>
>>> [Med] The question is not whether a secure transport is used or not but
>>to what extent the flow description is accurate (e.g., send fake flow
>>description, systematically request treatment with higher priority,
>>etc.).
>>
>>Right. That was the intention of 3.1.4.2. Ultimately the network taking
>>action on the metadata needs to trust the authenticated identity
>>associated with the attributes to not lie about the attributes - OR
>>enforce the semantic of the attributes signalled.
>>
>[Med] this discussion about trust is worth to be elaborated further in
>the document. For sure, this point will be raised by others.
>
>>Cheers
>>    Toerless


From mohamed.boucadair@orange.com  Fri Jul 19 05:41:15 2013
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3250B11E8124 for <int-area@ietfa.amsl.com>; Fri, 19 Jul 2013 05:41:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y4SycG3BXW1J for <int-area@ietfa.amsl.com>; Fri, 19 Jul 2013 05:41:10 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id E861911E8105 for <int-area@ietf.org>; Fri, 19 Jul 2013 05:41:09 -0700 (PDT)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm14.si.francetelecom.fr (ESMTP service) with ESMTP id 7D36F22CBC0; Fri, 19 Jul 2013 14:41:08 +0200 (CEST)
Received: from PUEXCH81.nanterre.francetelecom.fr (unknown [10.101.44.34]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 526F74C069; Fri, 19 Jul 2013 14:41:08 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.233.200.25]) by PUEXCH81.nanterre.francetelecom.fr ([10.101.44.34]) with mapi; Fri, 19 Jul 2013 14:41:08 +0200
From: <mohamed.boucadair@orange.com>
To: "Reinaldo Penno (repenno)" <repenno@cisco.com>, "Toerless Eckert (eckert)" <eckert@cisco.com>
Date: Fri, 19 Jul 2013 14:41:07 +0200
Thread-Topic: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
Thread-Index: Ac6Bn0gbxl2mtmX2RumGmT6rK69PKgB822jgAAhZAoAAAX6WIAAnaaeAAAn1JAAAATsDAAAB5Zbg
Message-ID: <94C682931C08B048B7A8645303FDC9F36EE2DDB8C6@PUEXCB1B.nanterre.francetelecom.fr>
References: <94C682931C08B048B7A8645303FDC9F36EE2DDB790@PUEXCB1B.nanterre.francetelecom.fr> <45A697A8FFD7CF48BCF2BE7E106F0604090C9E94@xmb-rcd-x04.cisco.com>
In-Reply-To: <45A697A8FFD7CF48BCF2BE7E106F0604090C9E94@xmb-rcd-x04.cisco.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.6.28.101520
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Jul 2013 12:41:15 -0000

Hi Reinaldo,

IMHO, deployment considerations are key aspects if you want this model to f=
ly. Having the material in one document is better (at least in early stages=
 to socialize the proposed framework within IETF).=20

Cheers,
Med

>-----Message d'origine-----
>De=A0: Reinaldo Penno (repenno) [mailto:repenno@cisco.com]
>Envoy=E9=A0: vendredi 19 juillet 2013 13:33
>=C0=A0: BOUCADAIR Mohamed OLNC/OLN; Toerless Eckert (eckert)
>Cc=A0: Charles Eckel (eckelcu); int-area@ietf.org
>Objet=A0: Re: [Int-area] FW: New Version Notification for draft-eckert-
>intarea-flow-metadata-framework-01.txt
>
>Hi Med,
>
>I agree with you that we need to cover in more detail the managed CPE
>deployments but I wonder if this is the best document to do it.
>
>Maybe a use-cases draft based on very concrete scenarios would be best.
>
>Thanks,
>
>Reinaldo
>
>
>On 7/19/13 4:57 AM, "mohamed.boucadair@orange.com"
><mohamed.boucadair@orange.com> wrote:
>
>>Dear Toerless,
>>
>>Please see inline.
>>
>>Cheers,
>>Med
>>
>>>-----Message d'origine-----
>>>De : Toerless Eckert [mailto:eckert@cisco.com]
>>>Envoy=E9 : vendredi 19 juillet 2013 05:13
>>>=C0 : BOUCADAIR Mohamed OLNC/OLN
>>>Cc : Reinaldo Penno (repenno); Charles Eckel (eckelcu); int-area@ietf.or=
g
>>>Objet : Re: [Int-area] FW: New Version Notification for draft-eckert-
>>>intarea-flow-metadata-framework-01.txt
>>>
>>>On Thu, Jul 18, 2013 at 02:11:21PM +0200, mohamed.boucadair@orange.com
>>>wrote:
>>>> >[RP] I believe the end-point making the request for flow
>>>>characteristics
>>>> >will be the CPE in many cases where the applications is not metadata
>>>> >aware. In other words, the CPE makes the request on behalf of
>>>applications.
>>>> [Med] I'm more interested in this CPE flavor (managed CPE) since it
>>>avoids relying on applications to benefit from the added value of this
>>>approach. This is worth be discussed in the document too.
>>>
>>>See section 3.1.4.1 which talks about proxies. The problem really is
>>>where
>>>the proxied information comes from. If the proxy is doing DPI inspection
>>>to
>>>deduce it or some configured mappings, then it's likely going to be
>>>unreliable
>>>(encryption) or suffer from problems in getting it provisioned.
>>
>>[Med] Section 3.1.4.1 as it is does not provide decent discussion of
>>these deployment issues and considerations. Sketching the expected
>>behavior of such intermediary functions would even be better. This
>>applies also for the other deployment-related issues I listed in my
>>initial e-mail.
>>
>>>
>>>To me these inspecting proxies are a way to get a foot in the door with
>>>the method while it takes its time to persuade app-developers (or
>>>middleware
>>>like browsers) to signal the information explicitly (couple of years
>>>?...).
>>>
>>>> [Med] The question is not whether a secure transport is used or not bu=
t
>>>to what extent the flow description is accurate (e.g., send fake flow
>>>description, systematically request treatment with higher priority,
>>>etc.).
>>>
>>>Right. That was the intention of 3.1.4.2. Ultimately the network taking
>>>action on the metadata needs to trust the authenticated identity
>>>associated with the attributes to not lie about the attributes - OR
>>>enforce the semantic of the attributes signalled.
>>>
>>[Med] this discussion about trust is worth to be elaborated further in
>>the document. For sure, this point will be raised by others.
>>
>>>Cheers
>>>    Toerless


From eckert@cisco.com  Thu Jul 18 18:35:16 2013
Return-Path: <eckert@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 5592A11E824D for <int-area@ietfa.amsl.com>; Thu, 18 Jul 2013 18:35:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.239
X-Spam-Level: 
X-Spam-Status: No, score=-10.239 tagged_above=-999 required=5 tests=[AWL=-0.195, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_OBFU_PRESENTLY=0.555]
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 VoLBuVNr+FgG for <int-area@ietfa.amsl.com>; Thu, 18 Jul 2013 18:35:12 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id F1E5211E81B6 for <int-area@ietf.org>; Thu, 18 Jul 2013 18:35:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1791; q=dns/txt; s=iport; t=1374197711; x=1375407311; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=uDZZZU5tZ18IBDKXgaEcHjEhpvzggb9I8ptS+ymbDY0=; b=mU5tuVGkEySWXqY/mNvSo7dnmFDGgKuF5nuk7BtMsYrNPcKiytWAsDIs KYvYjPl4XCMPA3g8y+/ovo92/ClU19otjjkRfjessPAF6ftaCRrua0SRX vYEuO/Dj6QXTzyMQpiazr59UY9YZlxeO8m2Wn2AiCRBSGSLTREaaWl2gl c=;
X-IronPort-AV: E=Sophos;i="4.89,697,1367971200"; d="scan'208";a="83405622"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-1.cisco.com with ESMTP; 19 Jul 2013 01:35:11 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r6J1ZBOZ002917 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Jul 2013 01:35:11 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id r6J1ZAKH001488;  Thu, 18 Jul 2013 18:35:10 -0700
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id r6J1ZA2Q001487; Thu, 18 Jul 2013 18:35:10 -0700
Date: Thu, 18 Jul 2013 18:35:10 -0700
From: Toerless Eckert <eckert@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <20130719013510.GI23170@cisco.com>
References: <45A697A8FFD7CF48BCF2BE7E106F0604090C8B4D@xmb-rcd-x04.cisco.com> <51E87848.2030805@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <51E87848.2030805@gmail.com>
User-Agent: Mutt/1.4.2.2i
X-Mailman-Approved-At: Fri, 19 Jul 2013 07:55:40 -0700
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Jul 2013 01:35:16 -0000

Brian,

Let me give you a comparison: I think DNS is a system with
a standardized data-model for information about specific objects,
primarily hosts and services. The result/action from using DNS is
most commonly some TCP connection(s). That does not make DNS a
TSV target. The metadata framework is in my eyes about a system
with a standardized data-model for traffic-flows and the result/action
is most commonly some form of QoS for the traffic flows. Go figure.

Having said this, we asked to preesent in TSVWG as well, but it does 
not seem as if it would get onto the TSVWG WG agenda. I think there 
would be good collaborators to be found from TSV because like DNS
i would expect that the folks interested in the actions taken
have an interest to build a data-model to make their actions easier.

Cheers
    Toerless

On Fri, Jul 19, 2013 at 11:20:40AM +1200, Brian E Carpenter wrote:
> On 19/07/2013 09:41, Reinaldo Penno (repenno) wrote:
> > Hi Brian,
> > 
> > Metadata has many uses and not just QoS.
> 
> Sure, but some of them clearly concern layers above 3.
> 
> > 
> > Therefore we believe int-area to be appropriate. What are your thoughts?
> 
> I think this is a case where early discussion in TSVWG would avoid
> problems later. In the end the choice of WG doesn't matter as long as
> cross-area issues are caught as soon as possible.
> 
>    Brian
> 
> > On 7/18/13 4:58 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
> > wrote:
> > 
> >> Why is this an intarea topic? To my mind it fits in tsvwg, which is
> >> currently discussing things like QoS for rtcweb.
> >>
> > 
> > 
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area

From brian@innovationslab.net  Fri Jul 19 11:21:08 2013
Return-Path: <brian@innovationslab.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 2F7B411E818D for <int-area@ietfa.amsl.com>; Fri, 19 Jul 2013 11:21:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.72
X-Spam-Level: 
X-Spam-Status: No, score=-102.72 tagged_above=-999 required=5 tests=[AWL=-0.121, 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 rzGs1AgcPndi for <int-area@ietfa.amsl.com>; Fri, 19 Jul 2013 11:21:03 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id DD63B11E8147 for <int-area@ietf.org>; Fri, 19 Jul 2013 11:21:02 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id AE184880E7; Fri, 19 Jul 2013 11:20:54 -0700 (PDT)
Received: from 10252218.rudm1.ra.johnshopkins.edu (addr16212925014.ippl.jhmi.edu [162.129.250.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 6323B130003; Fri, 19 Jul 2013 11:20:54 -0700 (PDT)
Message-ID: <51E98380.5070500@innovationslab.net>
Date: Fri, 19 Jul 2013 14:20:48 -0400
From: Brian Haberman <brian@innovationslab.net>
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: "int-area@ietf.org" <int-area@ietf.org>,  "int-chairs@tools.ietf.org" <int-chairs@tools.ietf.org>
References: <51DEE9E5.5090202@innovationslab.net>
In-Reply-To: <51DEE9E5.5090202@innovationslab.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Int-area] INT ADs' office hours
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "int-ads@tools.ietf.org" <int-ads@tools.ietf.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, 19 Jul 2013 18:21:08 -0000

The IESG breakout room has been identified.  We will have "office hours" 
from 1300 to 1500 on Monday (July 29th) in the Chess Room.

Regards,
Brian

On 7/11/13 1:22 PM, Brian Haberman wrote:
> All,
>       As in the previous few meetings, the INT ADs will be holding
> "office hours" in Berlin.  We will be available on Monday from 1300 to
> 1500 in the yet-to-be-identified IESG breakout room.  Feel free to stop
> by and ask questions or chat about any concerns/ideas you have about an
> INT WG or the area as a whole.
>
> Regards,
> Brian & Ted
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area


From wes@mti-systems.com  Sun Jul 21 06:55:11 2013
Return-Path: <wes@mti-systems.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 37DCF11E80E7 for <int-area@ietfa.amsl.com>; Sun, 21 Jul 2013 06:55:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.463
X-Spam-Level: 
X-Spam-Status: No, score=-2.463 tagged_above=-999 required=5 tests=[AWL=-0.091, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
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 BgOSSbYXs7GT for <int-area@ietfa.amsl.com>; Sun, 21 Jul 2013 06:55:11 -0700 (PDT)
Received: from atl4mhob09.myregisteredsite.com (atl4mhob09.myregisteredsite.com [209.17.115.47]) by ietfa.amsl.com (Postfix) with ESMTP id 150ED11E80F6 for <int-area@ietf.org>; Sun, 21 Jul 2013 06:54:56 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.206]) by atl4mhob09.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id r6LDss3O021986 for <int-area@ietf.org>; Sun, 21 Jul 2013 09:54:54 -0400
Received: (qmail 11410 invoked by uid 0); 21 Jul 2013 13:54:54 -0000
X-TCPREMOTEIP: 69.81.143.143
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.1.122?) (wes@mti-systems.com@69.81.143.143) by 0 with ESMTPA; 21 Jul 2013 13:54:54 -0000
Message-ID: <51EBE826.4070806@mti-systems.com>
Date: Sun, 21 Jul 2013 09:54:46 -0400
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: "int-area@ietf.org" <int-area@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [Int-area] forming an IETF AQM working group
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: Sun, 21 Jul 2013 13:55:11 -0000

We are trying to start a working group in the IETF to focus
on Active Queue Management (AQM) and packet scheduling or
fair queuing algorithms.

There is a mailing list setup at:
https://www.ietf.org/mailman/listinfo/aqm

Anyone interested is free and welcomed to join the discussion.
We especially want to have people with different perspectives
participating, including hardware and software developers for
different types of systems, network operators, academics, etc.

There will also be a Birds of a Feather (BoF) meeting at the
IETF meeting in Berlin (http://www.ietf.org/meeting/87) later
this month, which we wanted to make people aware of.  The
goal of the meeting is to form a working group following the
meeting.

A draft charter that is being discussed can be found here:
http://www.ietf.org/mail-archive/web/aqm/current/msg00165.html

-- 
Wes Eddy
MTI Systems

From jrjahangir@gmail.com  Mon Jul 22 02:14:28 2013
Return-Path: <jrjahangir@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 8199B21F848E for <int-area@ietfa.amsl.com>; Mon, 22 Jul 2013 02:14:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.386
X-Spam-Level: 
X-Spam-Status: No, score=-2.386 tagged_above=-999 required=5 tests=[AWL=-0.014, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, SARE_SUB_OBFU_Q1=0.227]
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 CBVVQqGraYdZ for <int-area@ietfa.amsl.com>; Mon, 22 Jul 2013 02:14:26 -0700 (PDT)
Received: from mail-wg0-x232.google.com (mail-wg0-x232.google.com [IPv6:2a00:1450:400c:c00::232]) by ietfa.amsl.com (Postfix) with ESMTP id 9D60121F8FDC for <int-area@ietf.org>; Mon, 22 Jul 2013 02:06:30 -0700 (PDT)
Received: by mail-wg0-f50.google.com with SMTP id m15so322543wgh.29 for <int-area@ietf.org>; Mon, 22 Jul 2013 02:03:20 -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=sJnK2tz9Kp6//+Ly1Xaagvw61pqXIBU7PS8GRKtfnwc=; b=onWWL894o3lrbB8h2Z2J2NWX005YAsMqWPfNmBhgcbyQ29wIymzYjztsKypTAPGZhu 1ofU0b6K+Jfd/vP4OPJK8NNK0M4cfOdCZw4HbGvUGTujtUB2Z94pCwJXZwyTl0t3/e7N XCBI9oRMbnbKFmzib8LtzUK03BFUhkxjT8z4FSNFzi85Ey8S5D7LRo632qFDTBhz7m/K G1yVpOqpX6rA892cclkWmom1eWx5SwT1Vex1J/H+/Eh1XXAncz8O0Cf9tNm8ohdR435r RIiF4JuHG0pijkMdp3SMU2fdtFNER8RuuWnphlyfqbqHR4EnXH5HiHt29XwhX2uhMF2T rG3A==
MIME-Version: 1.0
X-Received: by 10.180.206.77 with SMTP id lm13mr18072475wic.4.1374483800385; Mon, 22 Jul 2013 02:03:20 -0700 (PDT)
Received: by 10.194.3.72 with HTTP; Mon, 22 Jul 2013 02:03:20 -0700 (PDT)
In-Reply-To: <51EBE826.4070806@mti-systems.com>
References: <51EBE826.4070806@mti-systems.com>
Date: Mon, 22 Jul 2013 15:03:20 +0600
Message-ID: <CAG5EbHKCX2t6aXrkybzcoxU_zeaHs_D5fq0nw3CW+oNvEqgWZg@mail.gmail.com>
From: "Md.Jahangir Hossain" <jrjahangir@gmail.com>
To: Wesley Eddy <wes@mti-systems.com>
Content-Type: multipart/alternative; boundary=001a11c380aeabf26004e215f23f
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] forming an IETF AQM working group
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: Mon, 22 Jul 2013 09:14:28 -0000

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

Thanks Wesley for sharing your information.

Mostly I am working as a Network and Systems integrator and consultant
also provide consultancy to Network and Systems operator in our region
specially  in Bangladesh. if any option to work with this working group
from developing country perspective  then please inform me. i will be glad
to play role into this working group.





Tx-     Thanks  //  Jahangir Hossain


On Sun, Jul 21, 2013 at 7:54 PM, Wesley Eddy <wes@mti-systems.com> wrote:

> We are trying to start a working group in the IETF to focus
> on Active Queue Management (AQM) and packet scheduling or
> fair queuing algorithms.
>
> There is a mailing list setup at:
> https://www.ietf.org/mailman/listinfo/aqm
>
> Anyone interested is free and welcomed to join the discussion.
> We especially want to have people with different perspectives
> participating, including hardware and software developers for
> different types of systems, network operators, academics, etc.
>
> There will also be a Birds of a Feather (BoF) meeting at the
> IETF meeting in Berlin (http://www.ietf.org/meeting/87) later
> this month, which we wanted to make people aware of.  The
> goal of the meeting is to form a working group following the
> meeting.
>
> A draft charter that is being discussed can be found here:
> http://www.ietf.org/mail-archive/web/aqm/current/msg00165.html
>
> --
> Wes Eddy
> MTI Systems
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area
>



-- 




**

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

<div dir=3D"ltr"><div>Thanks Wesley for sharing your information. <br><br><=
/div>Mostly I am working as a Network and Systems integrator and consultant=
=A0 also provide consultancy to Network and Systems operator in our region =
specially=A0 in Bangladesh. if any option to work with this working group f=
rom developing country perspective=A0 then please inform me. i will be glad=
 to play role into this working group.<br>
<br><br><br><br><br>Tx- =A0=A0=A0 Thanks=A0 //=A0 Jahangir Hossain<br><div =
class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Sun, Jul 21, 20=
13 at 7:54 PM, Wesley Eddy <span dir=3D"ltr">&lt;<a href=3D"mailto:wes@mti-=
systems.com" target=3D"_blank">wes@mti-systems.com</a>&gt;</span> wrote:<br=
>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">We are trying to start a =
working group in the IETF to focus<br>
on Active Queue Management (AQM) and packet scheduling or<br>
fair queuing algorithms.<br>
<br>
There is a mailing list setup at:<br>
<a href=3D"https://www.ietf.org/mailman/listinfo/aqm" target=3D"_blank">htt=
ps://www.ietf.org/mailman/listinfo/aqm</a><br>
<br>
Anyone interested is free and welcomed to join the discussion.<br>
We especially want to have people with different perspectives<br>
participating, including hardware and software developers for<br>
different types of systems, network operators, academics, etc.<br>
<br>
There will also be a Birds of a Feather (BoF) meeting at the<br>
IETF meeting in Berlin (<a href=3D"http://www.ietf.org/meeting/87" target=
=3D"_blank">http://www.ietf.org/meeting/87</a>) later<br>
this month, which we wanted to make people aware of. =A0The<br>
goal of the meeting is to form a working group following the<br>
meeting.<br>
<br>
A draft charter that is being discussed can be found here:<br>
<a href=3D"http://www.ietf.org/mail-archive/web/aqm/current/msg00165.html" =
target=3D"_blank">http://www.ietf.org/mail-archive/web/aqm/current/msg00165=
.html</a><br>
<span class=3D""><font color=3D"#888888"><br>
--<br>
Wes Eddy<br>
MTI Systems<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>
</font></span></blockquote></div><br><br clear=3D"all"><br>-- <br><div dir=
=3D"ltr"><div><br><br></div><div>=A0=A0=A0=A0=A0 <br></div><div><br></div><=
b></b><div><pre><br></pre></div></div>
</div></div>

--001a11c380aeabf26004e215f23f--

From wesley.george@twcable.com  Mon Jul 22 13:18:19 2013
Return-Path: <wesley.george@twcable.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 EFB2611E813F for <int-area@ietfa.amsl.com>; Mon, 22 Jul 2013 13:18:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.463
X-Spam-Level: 
X-Spam-Status: No, score=-0.463 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
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 aiVohWc0Lubi for <int-area@ietfa.amsl.com>; Mon, 22 Jul 2013 13:18:13 -0700 (PDT)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 9022811E8153 for <int-area@ietf.org>; Mon, 22 Jul 2013 13:18:06 -0700 (PDT)
X-SENDER-IP: 10.136.163.10
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.89,721,1367985600"; d="scan'208";a="107722332"
Received: from unknown (HELO PRVPEXHUB01.corp.twcable.com) ([10.136.163.10]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 22 Jul 2013 16:16:56 -0400
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.78]) by PRVPEXHUB01.corp.twcable.com ([10.136.163.10]) with mapi; Mon, 22 Jul 2013 16:18:05 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: "int-area@ietf.org" <int-area@ietf.org>
Date: Mon, 22 Jul 2013 16:18:04 -0400
Thread-Topic: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
Thread-Index: Ac6Bn0gbxl2mtmX2RumGmT6rK69PKgB822jgAAhZAoAAAX6WIAANU3hgABdWeIAAsgzSUA==
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD59230439111259@PRVPEXVS15.corp.twcable.com>
References: <94C682931C08B048B7A8645303FDC9F36EE2DDB4FE@PUEXCB1B.nanterre.francetelecom.fr> <45A697A8FFD7CF48BCF2BE7E106F0604090C8510@xmb-rcd-x04.cisco.com> <94C682931C08B048B7A8645303FDC9F36EE2DDB59F@PUEXCB1B.nanterre.francetelecom.fr> <92B7E61ADAC1BB4F941F943788C08828048B669B@xmb-aln-x08.cisco.com> <94C682931C08B048B7A8645303FDC9F36EE2DDB748@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36EE2DDB748@PUEXCB1B.nanterre.francetelecom.fr>
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] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Jul 2013 20:18:19 -0000

I think this is an interesting and potentially useful draft.

In section 3.2.3, acceptable path attributes, I think there needs to be som=
e more granularity available in order to properly express the needs of a gi=
ven application. Specifically, you need to make a distinction between maxim=
um sustained delay and peak, momentary delay (jitter), as often application=
s can be tolerant of one but not the other. You also may need to represent =
a max sustained loss vs a max momentary peak loss, and define a timescale u=
pon which to measure those maximums, since an absolute value for loss (e.g.=
 1%) can mean vastly different things depending on the measurement timescal=
e and type of payload.

You may even want to offer a way to represent near-infinite (tens or hundre=
ds of seconds) delay tolerance, perhaps expressed in terms of a "must be de=
livered by" or expiration date. What I have in mind here is cases where you=
 have bulk background transfers that have relatively high bandwidth require=
ments, but are very tolerant of delay and can be therefore buffered, deferr=
ed, or routed on very sub-optimal paths. For example, if I'm loading conten=
t onto a cache, and it cannot be accessed before a certain date and time du=
e to blackout restrictions, that flow has near-infinite delay tolerance up =
until just before that date and time when it must be available. Armed with =
that knowledge, the network can schedule when it actually does that transfe=
r (and what path it takes) to ensure best utilization of the network's spar=
e capacity.

Thanks,

Wes George


Anything below this line has been added by my company's mail server, I have=
 no control over it.
-----------------

This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From eckelcu@cisco.com  Tue Jul 23 14:16:47 2013
Return-Path: <eckelcu@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 6F75411E8386 for <int-area@ietfa.amsl.com>; Tue, 23 Jul 2013 14:16:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 1EJai1dQcBPu for <int-area@ietfa.amsl.com>; Tue, 23 Jul 2013 14:16:42 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id DCECE11E8235 for <int-area@ietf.org>; Tue, 23 Jul 2013 14:16:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3938; q=dns/txt; s=iport; t=1374614202; x=1375823802; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=EneY5rKFI4dPqL8TOFVpM6EO1Oeek2jizPCH7VN34Wg=; b=Tu4SS5NW03IudEnX2JHmD0+2dYD2ZN7lp+74cwk3x3Z7pOFXhbvgaGiY 8HE/FOznXvlYlew+GZ1AVMz+UXsdaJPIMz4j69UCRoOM937Cd/g/b5TB5 26akctnYvzdB3bS2vt2rGjXanxkOZmRkIJmhaNMz7aj/IYaiTpkt1FKoq o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhgFAO/x7lGtJXG8/2dsb2JhbABbgwY1UMBfgRMWdIIkAQEBAwEBAQE3NAQFBwcEAgEIEQQBAQsUBQQHJwsUCAEIAgQBCQkIiAIFAQy4PgSOS4EBOAaDDG4DlAiVJIFbgTmBcTk
X-IronPort-AV: E=Sophos;i="4.89,730,1367971200"; d="scan'208";a="238478030"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-2.cisco.com with ESMTP; 23 Jul 2013 21:16:41 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r6NLGewB006143 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 23 Jul 2013 21:16:41 GMT
Received: from xmb-aln-x08.cisco.com ([169.254.3.214]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.02.0318.004; Tue, 23 Jul 2013 16:16:40 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "George, Wes" <wesley.george@twcable.com>, "int-area@ietf.org" <int-area@ietf.org>
Thread-Topic: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
Thread-Index: Ac6Bn0gbxl2mtmX2RumGmT6rK69PKgB822jgAAhZAoAAAX6WIAANU3hgABdWeIAAsgzSUAA0bUxQ
Date: Tue, 23 Jul 2013 21:16:40 +0000
Message-ID: <92B7E61ADAC1BB4F941F943788C08828048F4A43@xmb-aln-x08.cisco.com>
References: <94C682931C08B048B7A8645303FDC9F36EE2DDB4FE@PUEXCB1B.nanterre.francetelecom.fr> <45A697A8FFD7CF48BCF2BE7E106F0604090C8510@xmb-rcd-x04.cisco.com> <94C682931C08B048B7A8645303FDC9F36EE2DDB59F@PUEXCB1B.nanterre.francetelecom.fr> <92B7E61ADAC1BB4F941F943788C08828048B669B@xmb-aln-x08.cisco.com> <94C682931C08B048B7A8645303FDC9F36EE2DDB748@PUEXCB1B.nanterre.francetelecom.fr> <2671C6CDFBB59E47B64C10B3E0BD59230439111259@PRVPEXVS15.corp.twcable.com>
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD59230439111259@PRVPEXVS15.corp.twcable.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [171.68.16.40]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Jul 2013 21:16:47 -0000

Hi George,=20

Thanks for your comments. Please see inline.

> -----Original Message-----
> From: int-area-bounces@ietf.org [mailto:int-area-bounces@ietf.org] On Beh=
alf
> Of George, Wes
> Sent: Monday, July 22, 2013 1:18 PM
> To: int-area@ietf.org
> Subject: Re: [Int-area] FW: New Version Notification for draft-eckert-int=
area-
> flow-metadata-framework-01.txt
>=20
> I think this is an interesting and potentially useful draft.
>=20
> In section 3.2.3, acceptable path attributes, I think there needs to be s=
ome
> more granularity available in order to properly express the needs of a gi=
ven
> application. Specifically, you need to make a distinction between maximum
> sustained delay and peak, momentary delay (jitter), as often applications=
 can
> be tolerant of one but not the other.=20

I see your point. We actually considered including jitter as a separate att=
ribute. We decided to leave it out mainly in an attempt to keep the attribu=
te set small, yet sufficient. We can certainly add jitter, though I'd like =
to hear a few more opinions on this.

> You also may need to represent a max
> sustained loss vs a max momentary peak loss, and define a timescale upon
> which to measure those maximums, since an absolute value for loss (e.g. 1=
%)
> can mean vastly different things depending on the measurement timescale
> and type of payload.

Yes, the loss needs to be computed over a time period and/or number of pack=
ets for the percentage to make sense. I was envisioning this as an indicati=
on of momentary peak loss rather than sustained loss, but that is dependent=
 on the chosen time period and packet rate. What do you think would be reas=
onable values for the interval? Do you think it is possible to choose this =
interval such that one loss measurement is sufficient?

> You may even want to offer a way to represent near-infinite (tens or hund=
reds
> of seconds) delay tolerance, perhaps expressed in terms of a "must be
> delivered by" or expiration date. What I have in mind here is cases where=
 you
> have bulk background transfers that have relatively high bandwidth
> requirements, but are very tolerant of delay and can be therefore buffere=
d,
> deferred, or routed on very sub-optimal paths. For example, if I'm loadin=
g
> content onto a cache, and it cannot be accessed before a certain date and
> time due to blackout restrictions, that flow has near-infinite delay tole=
rance up
> until just before that date and time when it must be available. Armed wit=
h that
> knowledge, the network can schedule when it actually does that transfer (=
and
> what path it takes) to ensure best utilization of the network's spare cap=
acity.

Hopefully setting this attribute to the maximum value in the defined range =
is sufficient to accomplish this.

Cheers,
Charles

> Thanks,
>=20
> Wes George
>=20
>=20
> Anything below this line has been added by my company's mail server, I ha=
ve
> no control over it.
> -----------------
>=20
> This E-mail and any of its attachments may contain Time Warner Cable
> proprietary information, which is privileged, confidential, or subject to
> copyright belonging to Time Warner Cable. This E-mail is intended solely =
for
> the use of the individual or entity to which it is addressed. If you are =
not the
> intended recipient of this E-mail, you are hereby notified that any
> dissemination, distribution, copying, or action taken in relation to the =
contents
> of and attachments to this E-mail is strictly prohibited and may be unlaw=
ful. If
> you have received this E-mail in error, please notify the sender immediat=
ely
> and permanently delete the original and any copy of this E-mail and any
> printout.
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area

From amchouki@cisco.com  Wed Jul 24 01:38:59 2013
Return-Path: <amchouki@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 7F73A11E83CE for <int-area@ietfa.amsl.com>; Wed, 24 Jul 2013 01:38:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 mlL4i-2j21NG for <int-area@ietfa.amsl.com>; Wed, 24 Jul 2013 01:38:54 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 0A0EF11E83BC for <int-area@ietf.org>; Wed, 24 Jul 2013 01:38:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=25284; q=dns/txt; s=iport; t=1374655134; x=1375864734; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=DVvTDlVo3WLbRT2lpyGQOgLAxVlq4E7WprUmAxdNcKg=; b=VjPg659yu9a0eDM/eRiacE0LxgoMdaiNnZWtCOJmGaJoPav7yU8FbRXv hIJo/BwflVbxNGfukDtmmh7t8qo/8byB4YtAJ0WZ1tz8ub4wnxLWix1lv RByDHdXvFN3NkYJ/33Sg0tjrBAI7ROUIQIYoakoRpBqnHY2cWWdZ4IzpZ c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApIFADSS71GtJXHA/2dsb2JhbABbgwY1SgaFaqkfiTaIQYEWFnSCJAEBAQQBAQFpAggBAgwEAgEIEQQBAQsWAwQHJwsUCAEIAQEEDgUIARKHdQcFuGqPSTEHBoMMbgOIcpAWkCSBW4E5gio
X-IronPort-AV: E=Sophos;i="4.89,734,1367971200";  d="scan'208,217";a="238496480"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-1.cisco.com with ESMTP; 24 Jul 2013 08:38:52 +0000
Received: from xhc-aln-x06.cisco.com (xhc-aln-x06.cisco.com [173.36.12.80]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r6O8cqqr010080 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 24 Jul 2013 08:38:52 GMT
Received: from xmb-rcd-x12.cisco.com ([169.254.2.124]) by xhc-aln-x06.cisco.com ([173.36.12.80]) with mapi id 14.02.0318.004; Wed, 24 Jul 2013 03:38:31 -0500
From: "Amine Choukir (amchouki)" <amchouki@cisco.com>
To: "<mohamed.boucadair@orange.com> " <mohamed.boucadair@orange.com>
Thread-Topic: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
Thread-Index: Ac6Bn0gbxl2mtmX2RumGmT6rK69PKgB822jgATgX4wA=
Date: Wed, 24 Jul 2013 08:38:31 +0000
Message-ID: <17836813B5664041BC3393186692CAB81162C262@xmb-rcd-x12.cisco.com>
References: <92B7E61ADAC1BB4F941F943788C08828048B4221@xmb-aln-x08.cisco.com> <94C682931C08B048B7A8645303FDC9F36EE2DDB4FE@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36EE2DDB4FE@PUEXCB1B.nanterre.francetelecom.fr>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.148.51.55]
Content-Type: multipart/alternative; boundary="_000_17836813B5664041BC3393186692CAB81162C262xmbrcdx12ciscoc_"
MIME-Version: 1.0
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Jul 2013 08:38:59 -0000

--_000_17836813B5664041BC3393186692CAB81162C262xmbrcdx12ciscoc_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello MED,

Thank you for the comments.

See answer inline.

On Jul 18, 2013, at 11:13 AM, <mohamed.boucadair@orange.com<mailto:mohamed.=
boucadair@orange.com>>
 wrote:

Dear Charles, all,

The idea of an application sending flow characterization messages to the ne=
twork is interesting. This is an idea which is worth to be discussed and ch=
allenged. Thank you for writing this document.

The proposed framework makes sense in some contexts but I'm afraid it does =
not solve the limitations you listed in the document (e.g., avoid some clas=
sification functions in the network). The framework as it is won't simplify=
 the network side since in addition to legacy tools, a new function to inte=
rcept the flow characterization messages will be needed. The benefit of the=
 approach depends on the willing of application developers to signal the fl=
ow characteristic to the network.

IMHO, it would be useful if the document elaborates on deployment aspects a=
nd what are the facilitators to ease adoption of such approach. For example=
, why an application relying on HTTPS would sent a non-encrypted flow chara=
cterization message for analytic purposes? What is the role of a CPE in suc=
h model? How to trust the data sent by an application? These are examples o=
f points which should be further discussed in the document.

[AC ]We can definitely integrate a first set of use cases that help in unde=
rstanding the value of flow characterisation to the network and who plays a=
 role in producing those characteristics. I think we should both include SP=
 and enterprise use cases as the question of trust in those two environment=
s are solved in different ways. We did not include a draft on how to secure=
 the flow characteristics as we felt more discussion was needed to get to a=
 solid proposal including the aspect of single, multi-domain and transport =
specific vs transport independent security.

In the framework and the encoding we envisioned being able to signal from b=
oth endpoints and/or network elements (potentially more than one).


If the purpose of the document is not to claim the limitations you identifi=
ed will be mitigated but instead this framework is an additional tool at di=
sposal for implementers/operators/etc to ease service ordering and delivery=
, then a note should be added to the draft. This will be helpful to avoid a=
ny confusion.

Personally, I'm not a fun of solutions which requires explicit resource inv=
ocation before making use of a subscribed service. This mode should not be =
generalized (it does make sense if a very few services rely on that mode). =
I understand there are deployment cases which would rely on such mode but t=
his should be discussed in the document too.

[AC] As Charles mentioned application can opt to use or not metadata and wi=
ll still work as before if they don't. What the application gain is accurac=
y and granularity in terms of the characterisation of its flows for differe=
ntiated treatment and visibility.

I didn't understood well why the encoding is discussed in this document. Th=
e focus should be on the information model not data models (which are proto=
col-specific).

[AC] The encoding we discuss is transport independent that it is why it is =
referenced in the framework. The way we would like to present how flow char=
acterisation works is shown below. The framework as you said defines the in=
formation model and the use cases. The encoding draft defines how to encode=
 in a transport independent way tags signalled by applications and/or netwo=
rk elements. The transport specific draft maps the framework and the encodi=
ng to the protocol specific logic and messaging. The security draft would b=
e meant to cover transport independent security but this is to be discussed=
.

Hope that clarifies some of your concerns.

Cheers

Amine



                               +-----------------------------+
      +---------------------+  |  +----------------------+   |
      |                     |  |  |                      |   |
      |                     |  |  |                      |   |
      |                     |  |  |                      |   |
      |  security           +--+  |  framework           |   |
      |                     |  |  |                      |   |
      |                     |  |  |                      |   |
      |                     |  |  |                      |   |
      +---------------------+  |  +----------------------+   |
                               |                             |
                               |                             |
                               |  +----------------------+   |
                               |  |                      |   |
                               |  |                      |   |
                               |  |                      |   |
                               |  |   encoding           |   |
                               |  |                      |   |
                               |  |                      |   |
                               |  +----------------------+   |
                               ++------------+--------------++
      +----------------------+  | +----------+-----------+  | +------------=
-----------+
      |                      |  | |                      |  | |            =
           |
      |                      |  | |                      |  | |            =
           |
      |  STUN                +--+ |    PCP               |  +-+    RSVP    =
           |
      |                      |    |                      |    |            =
           |
      |                      |    |                      |    |            =
           |
      +----------------------+    +----------------------+    +------------=
-----------+






Cheers,
Med

-----Message d'origine-----
De : int-area-bounces@ietf.org<mailto:int-area-bounces@ietf.org> [mailto:in=
t-area-bounces@ietf.org<mailto:area-bounces@ietf.org>] De la
part de Charles Eckel (eckelcu)
Envoy=E9 : lundi 15 juillet 2013 23:07
=C0 : int-area@ietf.org<mailto:int-area@ietf.org>
Objet : [Int-area] FW: New Version Notification for draft-eckert-intarea-
flow-metadata-framework-01.txt

We have submitted and would appreciate comments on the following draft. It
provides a framework for applications and network devices to communicate
characteristics and service attributes for traffic flow. One aspect we
anticipate to be of particular interest to this audience is the use of
IPFIX in the information model we defined.

Cheers,
Charles

-----Original Message-----
From: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> [mailto:int=
ernet-drafts@ietf.org<mailto:drafts@ietf.org>]
Sent: Monday, July 15, 2013 1:41 PM
To: Toerless Eckert (eckert); Amine Choukir (amchouki); Reinaldo Penno
(repenno); Charles Eckel (eckelcu)
Subject: New Version Notification for draft-eckert-intarea-flow-metadata-
framework-01.txt


A new version of I-D, draft-eckert-intarea-flow-metadata-framework-01.txt
has been successfully submitted by Toerless Eckert and posted to the
IETF repository.

Filename: draft-eckert-intarea-flow-metadata-framework
Revision: 01
Title: A Framework for Signaling Flow Characteristics between
Applications and the Network
Creation date: 2013-07-15
Group: Individual Submission
Number of pages: 17
URL:             http://www.ietf.org/internet-drafts/draft-eckert-intarea-
flow-metadata-framework-01.txt
Status:          http://datatracker.ietf.org/doc/draft-eckert-intarea-flow-
metadata-framework
Htmlized:        http://tools.ietf.org/html/draft-eckert-intarea-flow-
metadata-framework-01
Diff:            http://www.ietf.org/rfcdiff?url2=3Ddraft-eckert-intarea-
flow-metadata-framework-01

Abstract:
 This document provides a framework for communicating information
 elements (a.k.a. metadata) in a consistent manner between
 applications and the network to provide better visibility of
 application flows, thereby enabling differentiated treatment of those
 flows.  These information elements can be conveyed using various
 signaling protocols, including PCP, RSVP, and STUN.




The IETF Secretariat

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


--_000_17836813B5664041BC3393186692CAB81162C262xmbrcdx12ciscoc_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <22F69FFD5EA78045AE3192CBDF5701A3@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
Hello MED,
<div><br>
</div>
<div>Thank you for the comments.</div>
<div><br>
</div>
<div>See answer inline.</div>
<div><br>
<div>
<div>On Jul 18, 2013, at 11:13 AM, &lt;<a href=3D"mailto:mohamed.boucadair@=
orange.com">mohamed.boucadair@orange.com</a>&gt;</div>
<div>&nbsp;wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">Dear Charles, all,<br>
<br>
The idea of an application sending flow characterization messages to the ne=
twork is interesting. This is an idea which is worth to be discussed and ch=
allenged. Thank you for writing this document.<br>
<br>
The proposed framework makes sense in some contexts but I'm afraid it does =
not solve the limitations you listed in the document (e.g., avoid some clas=
sification functions in the network). The framework as it is won't simplify=
 the network side since in addition
 to legacy tools, a new function to intercept the flow characterization mes=
sages will be needed. The benefit of the approach depends on the willing of=
 application developers to signal the flow characteristic to the network.
<br>
<br>
IMHO, it would be useful if the document elaborates on deployment aspects a=
nd what are the facilitators to ease adoption of such approach. For example=
, why an application relying on HTTPS would sent a non-encrypted flow chara=
cterization message for analytic
 purposes? What is the role of a CPE in such model? How to trust the data s=
ent by an application? These are examples of points which should be further=
 discussed in the document.
<br>
</blockquote>
<div><br>
</div>
[AC ]We can definitely integrate a first set of use cases that help in unde=
rstanding the value of flow characterisation to the network and who plays a=
 role in producing those characteristics. I think we should both include SP=
 and enterprise use cases as the
 question of trust in those two environments are solved in different ways. =
We did not include a draft on how to secure the flow characteristics as we =
felt more discussion was needed to get to a solid proposal including the as=
pect of single, multi-domain and
 transport specific vs transport independent security.</div>
<div><br>
</div>
<div>In the framework and the encoding we envisioned being able to signal f=
rom both endpoints and/or network elements (potentially more than one).</di=
v>
<div>&nbsp;&nbsp;<br>
<blockquote type=3D"cite"><br>
If the purpose of the document is not to claim the limitations you identifi=
ed will be mitigated but instead this framework is an additional tool at di=
sposal for implementers/operators/etc to ease service ordering and delivery=
, then a note should be added to
 the draft. This will be helpful to avoid any confusion.<br>
<br>
Personally, I'm not a fun of solutions which requires explicit resource inv=
ocation before making use of a subscribed service. This mode should not be =
generalized (it does make sense if a very few services rely on that mode). =
I understand there are deployment
 cases which would rely on such mode but this should be discussed in the do=
cument too.
<br>
</blockquote>
<div><br>
</div>
[AC] As Charles mentioned application can opt to use or not metadata and wi=
ll still work as before if they don't. What the application gain is accurac=
y and granularity in terms of the characterisation of its flows for differe=
ntiated treatment and visibility.&nbsp;<br>
<blockquote type=3D"cite"><br>
I didn't understood well why the encoding is discussed in this document. Th=
e focus should be on the information model not data models (which are proto=
col-specific).<br>
</blockquote>
<div><br>
</div>
[AC]&nbsp;The encoding we discuss is transport independent that it is why i=
t is referenced in the framework. The way we would like to present how flow=
 characterisation works is shown below. The framework as you said defines t=
he information model and the use cases.
 The encoding draft defines how to encode in a transport independent way ta=
gs signalled by applications and/or network elements. The transport specifi=
c draft maps the framework and the encoding to the protocol specific logic =
and messaging. The security draft
 would be meant to cover transport independent security but this is to be d=
iscussed.</div>
<div><br>
</div>
<div>Hope that clarifies some of your concerns.</div>
<div><br>
</div>
<div>Cheers</div>
<div><br>
</div>
<div>Amine</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div><font face=3D"Courier"><br>
</font></div>
<div><font face=3D"Courier">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&#43;------=
-----------------------&#43;</font></div>
<div><font face=3D"Courier">&nbsp; &nbsp; &nbsp; &#43;---------------------=
&#43; &nbsp;| &nbsp;&#43;----------------------&#43; &nbsp; |</font></div>
<div><font face=3D"Courier">&nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nb=
sp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp;| &nbsp;| &nbsp; &nbs=
p; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; |=
</font></div>
<div><font face=3D"Courier">&nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nb=
sp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp;| &nbsp;| &nbsp; &nbs=
p; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; |=
</font></div>
<div><font face=3D"Courier">&nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nb=
sp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp;| &nbsp;| &nbsp; &nbs=
p; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; |=
</font></div>
<div><font face=3D"Courier">&nbsp; &nbsp; &nbsp; | &nbsp;security &nbsp; &n=
bsp; &nbsp; &nbsp; &nbsp; &#43;--&#43; &nbsp;| &nbsp;framework &nbsp; &nbsp=
; &nbsp; &nbsp; &nbsp; | &nbsp; |</font></div>
<div><font face=3D"Courier">&nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nb=
sp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp;| &nbsp;| &nbsp; &nbs=
p; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; |=
</font></div>
<div><font face=3D"Courier">&nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nb=
sp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp;| &nbsp;| &nbsp; &nbs=
p; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; |=
</font></div>
<div><font face=3D"Courier">&nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nb=
sp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp;| &nbsp;| &nbsp; &nbs=
p; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; |=
</font></div>
<div><font face=3D"Courier">&nbsp; &nbsp; &nbsp; &#43;---------------------=
&#43; &nbsp;| &nbsp;&#43;----------------------&#43; &nbsp; |</font></div>
<div><font face=3D"Courier">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &n=
bsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; |</font></div>
<div><font face=3D"Courier">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &n=
bsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; |</font></div>
<div><font face=3D"Courier">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp;&#4=
3;----------------------&#43; &nbsp; |</font></div>
<div><font face=3D"Courier">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp;| &=
nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
| &nbsp; |</font></div>
<div><font face=3D"Courier">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp;| &=
nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
| &nbsp; |</font></div>
<div><font face=3D"Courier">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp;| &=
nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
| &nbsp; |</font></div>
<div><font face=3D"Courier">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp;| &=
nbsp; encoding &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; |</font></div>
<div><font face=3D"Courier">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp;| &=
nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
| &nbsp; |</font></div>
<div><font face=3D"Courier">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp;| &=
nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
| &nbsp; |</font></div>
<div><font face=3D"Courier">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp;&#4=
3;----------------------&#43; &nbsp; |</font></div>
<div><font face=3D"Courier">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&#43;&#43;-=
-----------&#43;--------------&#43;&#43;</font></div>
<div><font face=3D"Courier">&nbsp; &nbsp; &nbsp; &#43;---------------------=
-&#43; &nbsp;| &#43;----------&#43;-----------&#43; &nbsp;| &#43;----------=
-------------&#43;</font></div>
<div><font face=3D"Courier">&nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nb=
sp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp;| | &nbsp; &nbs=
p; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp;| =
| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp; |</font></div>
<div><font face=3D"Courier">&nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nb=
sp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp;| | &nbsp; &nbs=
p; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp;| =
| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nb=
sp; |</font></div>
<div><font face=3D"Courier">&nbsp; &nbsp; &nbsp; | &nbsp;STUN &nbsp; &nbsp;=
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&#43;--&#43; | &nbsp; &nbsp;PCP &=
nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp;&#43;-&#43; &nbsp; =
&nbsp;RSVP &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</font></div>
<div><font face=3D"Courier">&nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nb=
sp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp;| &nbsp;=
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nb=
sp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; |</font></div>
<div><font face=3D"Courier">&nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nb=
sp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp;| &nbsp;=
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nb=
sp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; |</font></div>
<div><font face=3D"Courier">&nbsp; &nbsp; &nbsp; &#43;---------------------=
-&#43; &nbsp; &nbsp;&#43;----------------------&#43; &nbsp; &nbsp;&#43;----=
-------------------&#43;</font></div>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
<blockquote type=3D"cite"><br>
Cheers,<br>
Med<br>
<br>
<blockquote type=3D"cite">-----Message d'origine-----<br>
De&nbsp;: <a href=3D"mailto:int-area-bounces@ietf.org">int-area-bounces@iet=
f.org</a> [mailto:int-<a href=3D"mailto:area-bounces@ietf.org">area-bounces=
@ietf.org</a>] De la<br>
part de Charles Eckel (eckelcu)<br>
Envoy=E9&nbsp;: lundi 15 juillet 2013 23:07<br>
=C0&nbsp;: <a href=3D"mailto:int-area@ietf.org">int-area@ietf.org</a><br>
Objet&nbsp;: [Int-area] FW: New Version Notification for draft-eckert-intar=
ea-<br>
flow-metadata-framework-01.txt<br>
<br>
We have submitted and would appreciate comments on the following draft. It<=
br>
provides a framework for applications and network devices to communicate<br=
>
characteristics and service attributes for traffic flow. One aspect we<br>
anticipate to be of particular interest to this audience is the use of<br>
IPFIX in the information model we defined.<br>
<br>
Cheers,<br>
Charles<br>
<br>
-----Original Message-----<br>
From: <a href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org<=
/a> [mailto:internet-<a href=3D"mailto:drafts@ietf.org">drafts@ietf.org</a>=
]<br>
Sent: Monday, July 15, 2013 1:41 PM<br>
To: Toerless Eckert (eckert); Amine Choukir (amchouki); Reinaldo Penno<br>
(repenno); Charles Eckel (eckelcu)<br>
Subject: New Version Notification for draft-eckert-intarea-flow-metadata-<b=
r>
framework-01.txt<br>
<br>
<br>
A new version of I-D, draft-eckert-intarea-flow-metadata-framework-01.txt<b=
r>
has been successfully submitted by Toerless Eckert and posted to the<br>
IETF repository.<br>
<br>
Filename:<span class=3D"Apple-tab-span" style=3D"white-space:pre"> </span>d=
raft-eckert-intarea-flow-metadata-framework<br>
Revision:<span class=3D"Apple-tab-span" style=3D"white-space:pre"> </span>0=
1<br>
Title:<span class=3D"Apple-tab-span" style=3D"white-space:pre"> </span><spa=
n class=3D"Apple-tab-span" style=3D"white-space:pre"></span>A Framework for=
 Signaling Flow Characteristics between<br>
Applications and the Network<br>
Creation date:<span class=3D"Apple-tab-span" style=3D"white-space:pre"> </s=
pan>2013-07-15<br>
Group:<span class=3D"Apple-tab-span" style=3D"white-space:pre"> </span><spa=
n class=3D"Apple-tab-span" style=3D"white-space:pre"></span>Individual Subm=
ission<br>
Number of pages: 17<br>
URL: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;<a href=3D"http://www.ietf.org/internet-drafts/draft-eckert-intarea-">htt=
p://www.ietf.org/internet-drafts/draft-eckert-intarea-</a><br>
flow-metadata-framework-01.txt<br>
Status: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href=3D"ht=
tp://datatracker.ietf.org/doc/draft-eckert-intarea-flow-">http://datatracke=
r.ietf.org/doc/draft-eckert-intarea-flow-</a><br>
metadata-framework<br>
Htmlized: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href=3D"http://tools=
.ietf.org/html/draft-eckert-intarea-flow-">http://tools.ietf.org/html/draft=
-eckert-intarea-flow-</a><br>
metadata-framework-01<br>
Diff: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-eckert-intarea-">http://ww=
w.ietf.org/rfcdiff?url2=3Ddraft-eckert-intarea-</a><br>
flow-metadata-framework-01<br>
<br>
Abstract:<br>
&nbsp;This document provides a framework for communicating information<br>
&nbsp;elements (a.k.a. metadata) in a consistent manner between<br>
&nbsp;applications and the network to provide better visibility of<br>
&nbsp;application flows, thereby enabling differentiated treatment of those=
<br>
&nbsp;flows. &nbsp;These information elements can be conveyed using various=
<br>
&nbsp;signaling protocols, including PCP, RSVP, and STUN.<br>
<br>
<br>
<br>
<br>
The IETF Secretariat<br>
<br>
_______________________________________________<br>
Int-area mailing list<br>
<a href=3D"mailto:Int-area@ietf.org">Int-area@ietf.org</a><br>
https://www.ietf.org/mailman/listinfo/int-area<br>
</blockquote>
_______________________________________________<br>
Int-area mailing list<br>
<a href=3D"mailto:Int-area@ietf.org">Int-area@ietf.org</a><br>
https://www.ietf.org/mailman/listinfo/int-area<br>
</blockquote>
</div>
<br>
</div>
</body>
</html>

--_000_17836813B5664041BC3393186692CAB81162C262xmbrcdx12ciscoc_--

From amchouki@cisco.com  Wed Jul 24 01:41:52 2013
Return-Path: <amchouki@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 550F611E83C8 for <int-area@ietfa.amsl.com>; Wed, 24 Jul 2013 01:41:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 2WfTM4Uz+1RP for <int-area@ietfa.amsl.com>; Wed, 24 Jul 2013 01:41:42 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 4AE3211E83C9 for <int-area@ietf.org>; Wed, 24 Jul 2013 01:41:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1610; q=dns/txt; s=iport; t=1374655302; x=1375864902; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=tH0a3I9KH6hJXiXf5AH0CnpclEvP3mB1O3lNiQvQS4E=; b=eB0HD7Cgayp7iPbBYKMEAmdDxQlwK5+z6iBVDAjT5Z9cd8FGguQuWx/1 E6OPk3A4RbMbGM4j01BSeevamSZ+kw9qed7sUrotNetQEif92iV18loYg 1g6wHXMVz16we4Xie/3GQPoucrC+W2GENosqlg45Zu8HnqJBCRu1R6eJG g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgQFADSS71GtJXHB/2dsb2JhbABbgwY1UMEAgRYWdIIkAQEBAwEBAQE3NAkCBQsCAQgYChQFCyEGCxwJAgQOBQiHdgMJBgyvfw2IWgSNEoI1AjEHgxJuA5V2jhCFJoFbgTmCKg
X-IronPort-AV: E=Sophos;i="4.89,734,1367971200"; d="scan'208";a="238677461"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-7.cisco.com with ESMTP; 24 Jul 2013 08:41:42 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r6O8ffBU019379 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 24 Jul 2013 08:41:41 GMT
Received: from xmb-rcd-x12.cisco.com ([169.254.2.124]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.02.0318.004; Wed, 24 Jul 2013 03:41:41 -0500
From: "Amine Choukir (amchouki)" <amchouki@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Thread-Topic: [Int-area] FW: New Version Notification for draft-eckert-intarea-flow-metadata-framework-01.txt
Thread-Index: AQHOg/E2mEFHesN5dECoZcNLo2Ymoplz3yoA
Date: Wed, 24 Jul 2013 08:41:41 +0000
Message-ID: <17836813B5664041BC3393186692CAB81162C28F@xmb-rcd-x12.cisco.com>
References: <94C682931C08B048B7A8645303FDC9F36EE2DDB4FE@PUEXCB1B.nanterre.francetelecom.fr> <45A697A8FFD7CF48BCF2BE7E106F0604090C8510@xmb-rcd-x04.cisco.com> <94C682931C08B048B7A8645303FDC9F36EE2DDB59F@PUEXCB1B.nanterre.francetelecom.fr> <51E848F4.9010003@gmail.com>
In-Reply-To: <51E848F4.9010003@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.148.51.55]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <333364FEF6911F4EAD7771A33F816258@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] FW: New Version Notification for	draft-eckert-intarea-flow-metadata-framework-01.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Jul 2013 08:41:52 -0000

Hello Brian,

Thank you for the comments.

As Toerless mentioned the framework covers more than the QoS use case. Othe=
r use cases are for example visibility and differentiated routing.

We would definitely like to present this work in TSV as it has definitely s=
ome ties there.

Cheers

Amine
On Jul 18, 2013, at 9:58 PM, Brian E Carpenter <brian.e.carpenter@gmail.com=
>
 wrote:

> On 19/07/2013 00:11, mohamed.boucadair@orange.com wrote:
> ...
>>>> How to trust the data sent by an application? These are examples of
>>>> points which should be further discussed in the document.
>>>=20
>>> [RP] I think this depends on the transport. Some transports like PCP or
>>> STUN have some built-in authentication.
>> [Med] The question is not whether a secure transport is used or not but =
to what extent the flow description is accurate (e.g., send fake flow descr=
iption, systematically request treatment with higher priority, etc.).
>=20
> This of course is why the diffserv model assumes that traffic will
> be reclassified at domain boundaries, since you can't trust what your
> neighbour tells you about QoS requirements. This proposal would be no
> different in the general case; flow metadata needs to be trustworthy.
> If not it will be a recipe for theft of service or DoS.
>=20
> Why is this an intarea topic? To my mind it fits in tsvwg, which is
> currently discussing things like QoS for rtcweb.
>=20
>   Brian
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area


From cjbc@it.uc3m.es  Mon Jul 29 03:55:31 2013
Return-Path: <cjbc@it.uc3m.es>
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 85B7A21F9D75; Mon, 29 Jul 2013 03:55:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 KXzQFZ8YaCLk; Mon, 29 Jul 2013 03:55:25 -0700 (PDT)
Received: from smtp02.uc3m.es (smtp02.uc3m.es [163.117.176.132]) by ietfa.amsl.com (Postfix) with ESMTP id B5DC721F9D11; Mon, 29 Jul 2013 03:55:25 -0700 (PDT)
Received: from smtp02.uc3m.es (localhost [127.0.0.1]) by localhost.uc3m.es (Postfix) with ESMTP id DC73E854DE5; Mon, 29 Jul 2013 12:55:23 +0200 (CEST)
X-uc3m-safe: yes
X-uc3m-safe: yes
Received: from [130.129.85.5] (dhcp-5505.meeting.ietf.org [130.129.85.5]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: cjbc@smtp02.uc3m.es) by smtp02.uc3m.es (Postfix) with ESMTPSA id 6FCC0778A6A; Mon, 29 Jul 2013 12:55:22 +0200 (CEST)
Message-ID: <1375095320.4497.3.camel@acorde.it.uc3m.es>
From: Carlos =?ISO-8859-1?Q?Jes=FAs?= Bernardos Cano <cjbc@it.uc3m.es>
To: dmm@ietf.org, netext@ietf.org, int-area@ietf.org
Date: Mon, 29 Jul 2013 12:55:20 +0200
Organization: Universidad Carlos III de Madrid
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.4.4-3 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-TM-AS-Product-Ver: IMSS-7.1.0.1224-7.0.0.1014-20044.006
X-TM-AS-Result: No--12.033-7.0-31-1
X-imss-scan-details: No--12.033-7.0-31-1
Cc: Fabio Giust <fabio.giust@imdea.org>
Subject: [Int-area] Network-based DMM demo at IETF 87 (Tue 17:00 "Check" room)
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: cjbc@it.uc3m.es
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Jul 2013 10:55:31 -0000

Dear all,

(Apologies for the cross-posting).

We will show a network-based DMM Linux implementation demo tomorrow
(Tuesday, 30th July) at 17h, in "Check" room (2nd floor).

The demo will showcase a particular use-case as an example of the
advantages provided by DMM: Content Distribution Networking (CDN) and
Distributed Mobility Management (DMM).

The setup is composed of three "anchor routers", a "centralized LMA" for
control plane, CDN cache nodes co-located with the anchor routers, some
correspondent nodes (including a video server) and a legacy IPv6 mobile
node. The implementation is based on the following two drafts:

[1] http://tools.ietf.org/html/draft-bernardos-dmm-pmip

[2] http://tools.ietf.org/html/draft-bernardos-dmm-distributed-anchoring

The demo will take about 20 to 30 minutes.

Looking forward to seeing you there and getting your feedback.

Thanks,

Carlos et al.


From cjbc@it.uc3m.es  Tue Jul 30 07:04:46 2013
Return-Path: <cjbc@it.uc3m.es>
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 C2E2E21F9E12; Tue, 30 Jul 2013 07:04:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 HtW5qxSOdqkm; Tue, 30 Jul 2013 07:04:38 -0700 (PDT)
Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.176.133]) by ietfa.amsl.com (Postfix) with ESMTP id A7D2E21F9BF0; Tue, 30 Jul 2013 07:04:38 -0700 (PDT)
Received: from smtp03.uc3m.es (localhost [127.0.0.1]) by localhost.uc3m.es (Postfix) with ESMTP id 178EF11C0C01; Tue, 30 Jul 2013 16:04:37 +0200 (CEST)
X-uc3m-safe: yes
X-uc3m-safe: yes
Received: from [130.129.20.223] (dhcp-14df.meeting.ietf.org [130.129.20.223]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: cjbc@smtp03.uc3m.es) by smtp03.uc3m.es (Postfix) with ESMTPSA id 2850B11C0C00; Tue, 30 Jul 2013 16:04:36 +0200 (CEST)
Message-ID: <1375193074.4549.4.camel@acorde.it.uc3m.es>
From: Carlos =?ISO-8859-1?Q?Jes=FAs?= Bernardos Cano <cjbc@it.uc3m.es>
To: dmm@ietf.org, int-area@ietf.org, netext@ietf.amsl.com
Date: Tue, 30 Jul 2013 16:04:34 +0200
In-Reply-To: <1375095320.4497.3.camel@acorde.it.uc3m.es>
References: <1375095320.4497.3.camel@acorde.it.uc3m.es>
Organization: Universidad Carlos III de Madrid
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.4.4-3 
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-TM-AS-Product-Ver: IMSS-7.1.0.1224-7.0.0.1014-20046.007
X-TM-AS-Result: No--18.594-7.0-31-1
X-imss-scan-details: No--18.594-7.0-31-1
Cc: Fabio Giust <fabio.giust@imdea.org>
Subject: Re: [Int-area] Network-based DMM demo at IETF 87 (Tue 17:00 "Check" room)
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: cjbc@it.uc3m.es
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, 30 Jul 2013 14:04:47 -0000

Hi,

Please note that today's DMM demo at 17h is in the "Check" room, 2nd
floor. If you don't know how to find, please look at the floor plans:

http://www.ietf.org/meeting/87/floor-plans.pdf

Thanks,

Carlos

On Mon, 2013-07-29 at 12:55 +0200, Carlos JesÃºs Bernardos Cano wrote:
> Dear all,
> 
> (Apologies for the cross-posting).
> 
> We will show a network-based DMM Linux implementation demo tomorrow
> (Tuesday, 30th July) at 17h, in "Check" room (2nd floor).
> 
> The demo will showcase a particular use-case as an example of the
> advantages provided by DMM: Content Distribution Networking (CDN) and
> Distributed Mobility Management (DMM).
> 
> The setup is composed of three "anchor routers", a "centralized LMA" for
> control plane, CDN cache nodes co-located with the anchor routers, some
> correspondent nodes (including a video server) and a legacy IPv6 mobile
> node. The implementation is based on the following two drafts:
> 
> [1] http://tools.ietf.org/html/draft-bernardos-dmm-pmip
> 
> [2] http://tools.ietf.org/html/draft-bernardos-dmm-distributed-anchoring
> 
> The demo will take about 20 to 30 minutes.
> 
> Looking forward to seeing you there and getting your feedback.
> 
> Thanks,
> 
> Carlos et al.



From linda.dunbar@huawei.com  Tue Jul 30 08:26: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 9972E21E80CC; Tue, 30 Jul 2013 08:26:41 -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 hGO5ZRb7BU5K; Tue, 30 Jul 2013 08:26:37 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id AF18021E80FC; Tue, 30 Jul 2013 08:26:35 -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 ATY02946; Tue, 30 Jul 2013 15:26:33 +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; Tue, 30 Jul 2013 16:25:44 +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; Tue, 30 Jul 2013 16:25:52 +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; Tue, 30 Jul 2013 08:25:45 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: "nvo3@ietf.org" <nvo3@ietf.org>, Internet Area <int-area@ietf.org>
Thread-Topic: Any feedback or concern of using Proxy Gateway in NVO3 environment? 
Thread-Index: Ac6NORF2DXrf11t3TD6fqN6QyY6vOA==
Date: Tue, 30 Jul 2013 15:25:44 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F645B51FEA@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.138.200]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F645B51FEAdfweml509mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [Int-area] Any feedback or concern of using Proxy Gateway in NVO3 environment?
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, 30 Jul 2013 15:26:41 -0000

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

NVO3 provides an overlay mechanism so that the hosts (or VMs) addresses are=
 hidden from the switches in the core.



However, for the "L2 in IP" case of NVO3, all the overlay edge nodes are st=
ill exposed to all the hosts MAC addresses on the VLANs that are enabled on=
 the edges, which can cause switches' FDB size explosion issue.



p.s. If the number of VMs attached to an edge is very small (e.g. overlay e=
dge in the server), then the number of VLANs enabled on the edge is limited=
. In this scenario, there could be very large number of edges/core nodes fo=
r large DC, which can make IGP in the core challenging.



For a typical Access switch (Top of Rack)  with 40 physical servers attache=
d, where each server has 100 VMs, there are 4000 hosts under the Access Swi=
tch. If indeed hosts/VMs can be moved anywhere, the worst case for the Acce=
ss Switch is when all those 4000 VMs belong to different VLANs, i.e. the ac=
cess switch has 4000 VLANs enabled. If each VLAN has 200 hosts, this access=
 switch's MAC table potentially has 200*4000 =3D 800,000 entries.

https://tools.ietf.org/html/draft-nachum-sarp-06
proposes a proxy gateway method to get around this problem. The main idea o=
f SARP is to represent all VMs (or hosts) under each access domain by their=
 corresponding access (or aggregation) node's MAC address regardless whethe=
r the access (or aggregation) node is the VMs (hosts)' gateway or not. For =
example, when a host "a" under access domain "S" needs to communicate with =
peers on the same VLAN but connected to different access domains, SARP requ=
ires "a" to use remote access node's MAC address rather than peers' MAC add=
resses. By doing so, switches in each domain do not need to maintain a list=
 of MAC addresses for all the VMs (hosts) in different access domains in th=
eir FDBs. Therefore, the switches' FDB size is limited regardless how VLAN =
is spread.

We are going to present SARP in Interarea WG session this Friday. Hope you =
can come to express your feedback or concerns. If you can't come, can you e=
xpress your feedback or concerns to int-area@ietf.com<mailto:int-area@ietf.=
com>?

Thank you very much.

Linda & Tal





--_000_4A95BA014132FF49AE685FAB4B9F17F645B51FEAdfweml509mbxchi_
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:Consolas;
	panose-1:2 11 6 9 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;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
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:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
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;}
@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"MsoPlainText">NVO3 provides an overlay mechanism so that the ho=
sts (or VMs) addresses are hidden from the switches in the core.<o:p></o:p>=
</p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">However, for the &#8220;L2 in IP&#8221; case of N=
VO3, all the overlay edge nodes are still exposed to all the hosts MAC addr=
esses on the VLANs that are enabled on the edges, which can cause switches&=
#8217; FDB size explosion issue.
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">p.s. If the number of VMs attached to an edge is =
very small (e.g. overlay edge in the server), then the number of VLANs enab=
led on the edge is limited. In this scenario, there could be very large num=
ber of edges/core nodes for large
 DC, which can make IGP in the core challenging. <o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">For a typical Access switch (Top of Rack)&nbsp; w=
ith 40 physical servers attached, where each server has 100 VMs, there are =
4000 hosts under the Access Switch. If indeed hosts/VMs can be moved anywhe=
re, the worst case for the Access Switch
 is when all those 4000 VMs belong to different VLANs, i.e. the access swit=
ch has 4000 VLANs enabled. If each VLAN has 200 hosts, this access switch&#=
8217;s MAC table potentially has 200*4000 =3D 800,000 entries.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"text-align:justify;text-justify:inter-ideog=
raph"><a href=3D"https://tools.ietf.org/html/draft-nachum-sarp-06">https://=
tools.ietf.org/html/draft-nachum-sarp-06</a>
<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"text-align:justify;text-justify:inter-ideog=
raph"><span style=3D"font-size:10.5pt;font-family:Consolas">proposes a prox=
y gateway method to get around this problem. The main idea of SARP is to re=
present all VMs (or hosts) under each
 access domain by their corresponding access (or aggregation) node's MAC ad=
dress regardless whether the access (or aggregation) node is the VMs (hosts=
)&#8217; gateway or not. For example, when a host &#8220;a&#8221; under acc=
ess domain &#8220;S&#8221; needs to communicate with peers on
 the same VLAN but connected to different access domains, SARP requires &#8=
220;a&#8221; to use remote access node&#8217;s MAC address rather than peer=
s&#8217; MAC addresses. By doing so, switches in each domain do not need to=
 maintain a list of MAC addresses for all the VMs (hosts)
 in different access domains in their FDBs. Therefore, the switches&#8217; =
FDB size is limited regardless how VLAN is spread.
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-align:justify;text-justify:inter-ideog=
raph"><span style=3D"font-size:10.5pt;font-family:Consolas"><o:p>&nbsp;</o:=
p></span></p>
<p class=3D"MsoNormal" style=3D"text-align:justify;text-justify:inter-ideog=
raph"><span style=3D"font-size:10.5pt;font-family:Consolas">We are going to=
 present SARP in Interarea WG session this Friday. Hope you can come to exp=
ress your feedback or concerns. If you
 can&#8217;t come, can you express your feedback or concerns to <a href=3D"=
mailto:int-area@ietf.com">
int-area@ietf.com</a>?<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-align:justify;text-justify:inter-ideog=
raph"><span style=3D"font-size:10.5pt;font-family:Consolas"><o:p>&nbsp;</o:=
p></span></p>
<p class=3D"MsoNormal" style=3D"text-align:justify;text-justify:inter-ideog=
raph"><span style=3D"font-size:10.5pt;font-family:Consolas">Thank you very =
much.
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-align:justify;text-justify:inter-ideog=
raph"><span style=3D"font-size:10.5pt;font-family:Consolas"><o:p>&nbsp;</o:=
p></span></p>
<p class=3D"MsoNormal" style=3D"text-align:justify;text-justify:inter-ideog=
raph"><span style=3D"font-size:10.5pt;font-family:Consolas">Linda &amp; Tal
<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_4A95BA014132FF49AE685FAB4B9F17F645B51FEAdfweml509mbxchi_--

From charliep@computer.org  Tue Jul 30 09:24:42 2013
Return-Path: <charliep@computer.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 B376921F8BE6 for <int-area@ietfa.amsl.com>; Tue, 30 Jul 2013 09:24:42 -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]
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 DPYPccBWSVvM for <int-area@ietfa.amsl.com>; Tue, 30 Jul 2013 09:24:38 -0700 (PDT)
Received: from elasmtp-junco.atl.sa.earthlink.net (elasmtp-junco.atl.sa.earthlink.net [209.86.89.63]) by ietfa.amsl.com (Postfix) with ESMTP id D728D21F8411 for <int-area@ietf.org>; Tue, 30 Jul 2013 09:24:30 -0700 (PDT)
Received: from [46.189.28.101] (helo=[10.185.10.35]) by elasmtp-junco.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <charliep@computer.org>) id 1V4Cil-0001kB-4D; Tue, 30 Jul 2013 12:24:23 -0400
Message-ID: <51F7E8AC.7060008@computer.org>
Date: Tue, 30 Jul 2013 09:24:12 -0700
From: "Charles E. Perkins" <charliep@computer.org>
Organization: Saratoga Blue Skies
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Internet Area <int-area@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956d5d4673fe7faad86f6284e93d52307f73d6f4a709ec33a5d350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 46.189.28.101
Cc: Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr>, Julien Laganier <jlaganier@JUNIPER.NET>
Subject: [Int-area] What is a wireless link?
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, 30 Jul 2013 16:24:42 -0000

Hello folks,

Emmanuel and I have a draft discussing the nature of wireless links and
adjacency.  As it turns out, it can be a source of great confusion as we 
have
learned in past discussions.

Please take a look at our draft:
http://tools.ietf.org/html/draft-baccelli-manet-multihop-communication-01

If there is interest, we would like to submit it as an Int-Area draft.

The draft underwent extensive discussion in the autoconf working group
and is relevant to work in wireless-oriented working groups such as
[manet] and [roll].  We think it belongs in Int-Area because it does not
deal with routing.

If there is still room on the agenda this week, I would be happy to make
a 5 minute presentation on the draft.

-- 
Regards,
Charlie P.


From touch@isi.edu  Tue Jul 30 10:09:21 2013
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCAE511E80FC for <int-area@ietfa.amsl.com>; Tue, 30 Jul 2013 10:09:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.699
X-Spam-Level: 
X-Spam-Status: No, score=-105.699 tagged_above=-999 required=5 tests=[AWL=0.900, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QrNw7roSiCjT for <int-area@ietfa.amsl.com>; Tue, 30 Jul 2013 10:09:16 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 2F3ED11E81DD for <int-area@ietf.org>; Tue, 30 Jul 2013 10:09:15 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r6UH8R2O015202 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 30 Jul 2013 10:08:27 -0700 (PDT)
Message-ID: <51F7F30B.7090700@isi.edu>
Date: Tue, 30 Jul 2013 10:08:27 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: "Charles E. Perkins" <charliep@computer.org>
References: <51F7E8AC.7060008@computer.org>
In-Reply-To: <51F7E8AC.7060008@computer.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr>, Internet Area <int-area@ietf.org>, Julien Laganier <jlaganier@JUNIPER.NET>
Subject: Re: [Int-area] What is a wireless link?
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, 30 Jul 2013 17:09:21 -0000

You might take a look at RFC 3819, esp. the section on multicast and 
broadcast.

Joe

On 7/30/2013 9:24 AM, Charles E. Perkins wrote:
> Hello folks,
>
> Emmanuel and I have a draft discussing the nature of wireless links and
> adjacency.  As it turns out, it can be a source of great confusion as we
> have
> learned in past discussions.
>
> Please take a look at our draft:
> http://tools.ietf.org/html/draft-baccelli-manet-multihop-communication-01
>
> If there is interest, we would like to submit it as an Int-Area draft.
>
> The draft underwent extensive discussion in the autoconf working group
> and is relevant to work in wireless-oriented working groups such as
> [manet] and [roll].  We think it belongs in Int-Area because it does not
> deal with routing.
>
> If there is still room on the agenda this week, I would be happy to make
> a 5 minute presentation on the draft.
>

From olivier.bonaventure@uclouvain.be  Tue Jul 30 13:28:22 2013
Return-Path: <olivier.bonaventure@uclouvain.be>
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 79C9D11E8234 for <int-area@ietfa.amsl.com>; Tue, 30 Jul 2013 13:28:22 -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 eWjg1s+VN3UK for <int-area@ietfa.amsl.com>; Tue, 30 Jul 2013 13:28:18 -0700 (PDT)
Received: from smtp5.sgsi.ucl.ac.be (smtp.sgsi.ucl.ac.be [130.104.5.67]) by ietfa.amsl.com (Postfix) with ESMTP id 96C4C11E8159 for <int-area@ietf.org>; Tue, 30 Jul 2013 13:28:18 -0700 (PDT)
Received: from dhcp-90b2.meeting.ietf.org (unknown [172.17.0.12]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: obonaventure@smtp5.sgsi.ucl.ac.be) by smtp5.sgsi.ucl.ac.be (Postfix) with ESMTPSA id DAEBA11FF64; Tue, 30 Jul 2013 22:28:10 +0200 (CEST)
X-DKIM: Sendmail DKIM Filter v2.8.3 smtp5.sgsi.ucl.ac.be DAEBA11FF64
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=uclouvain.be; s=selucl; t=1375216091; bh=TwvQSc0bwuqn5OlnBOrKIDIQLsl+dSzoTYFrRvOziLE=; h=Message-ID:Date:From:Reply-To:MIME-Version:To:CC:Subject: Content-Type:Content-Transfer-Encoding; b=ItPR6+Voo5hIKTjnAYHl01ZUPonabgIuor2p+o5AmMC+nOOURMAH9kskdUbvg0bKy v8PKZh5eWBiMG2pBSkN78VS1o1DPT8kxHNn0unWBAbrZ4IJkL4FoKmuzfIoF8JZ5mx jhuD2Efhg2JJOiVTHL+xCzno9bgdeWBDbx7K9uuQ=
Message-ID: <51F82234.6050503@uclouvain.be>
Date: Tue, 30 Jul 2013 22:29:40 +0200
From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Internet Area <int-area@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamav-milter 0.97.7-exp at smtp-5.sipr-dc.ucl.ac.be
X-Virus-Status: Clean
X-Sgsi-Spamcheck: SASL authenticated, 
X-SGSI-MailScanner-ID: DAEBA11FF64.A4CF0
X-SGSI-MailScanner: Found to be clean
X-SGSI-From: olivier.bonaventure@uclouvain.be
X-SGSI-Spam-Status: No
Cc: Gregory Detal <gregory.detal@uclouvain.be>
Subject: [Int-area] Tracking RFC1812 compliance for ICMP replies
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Olivier.Bonaventure@uclouvain.be
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, 30 Jul 2013 20:28:22 -0000

Hello,

The original ICMP specification recommended that every ICMP error 
message included the Internet header and at least the first 8 data bytes 
of the datagram that triggered the error. RFC1812 changed this 
recommendation to the following

 >4.3.2.3 Original Message Header
 >
 >   Historically, every ICMP error message has included the Internet
 >   header and at least the first 8 data bytes of the datagram that
 >   triggered the error.  This is no longer adequate, due to the use of
 >   IP-in-IP tunneling and other technologies.  Therefore, the ICMP
 >   datagram SHOULD contain as much of the original datagram as possible
 >   without the length of the ICMP datagram exceeding 576 bytes.  The
 >   returned IP header (and user data) MUST be identical to that which
 >   was received, except that the router is not required to undo any
 >   modifications to the IP header that are normally performed in
 >   forwarding that were performed before the error was detected (e.g.,
 >   decrementing the TTL, or updating options).

Over the years, several routers have implemented this section of 
4.3.2.3. Since the publication of RFC1812, middleboxes have been 
deployed in various parts of IP networks. Sometimes, these middleboxes 
create problems that are hard to debug. RFC1812 compliant routers would 
ease such debugging by returning large parts of transmitted packets.

We have anecdotal evidence that the following OSes support this part of 
RFC1812 :

  Cisco IOX, Linux, Alcatel, Palto Alto firewalls

while Cisco IOS and Juniper routers do not support this RFC.

We would be interested in getting more information about the state of 
support of this section of RFC1812 on routers. If you are responsible 
for a router OS, we would appreciate if you could let us know since 
which version you send a large ICMP message back if you support it ?

The motivation for this request is that Gregory Detal recently wrote the 
tracebox tool that exploits RFC1812 compliant routers to detect 
middleboxes. It works like traceroute but sends TCP segments that 
contain various types of options and compares the transmitted segment 
with the information found in the returned ICMP messages. If the ICMP 
message is returned by an RFC1812 compliant router, tracebox is able to 
detect any modification performed by intermediate middleboxes.

 From the IETF network (a network which is much cleaner than typical 
enterprise networks from a middlebox viewpoint) we can observe the 
following with tracebox :

sudo tracebox -p 'ip{}/tcp{dst=80}/MPCAPABLE/mss(9000)' bahn.de

tracebox to 81.200.198.6 (bahn.de): 64 hops max
1: rtra.meeting.ietf.org (130.129.8.2) IP::CheckSum
2: 193.159.164.161 (193.159.164.161) IP::TTL IP::CheckSum
3: f-ed5-i.f.de.net.dtag.de (217.5.95.58) IP::TTL IP::CheckSum
4: 80.150.168.30 (80.150.168.30) IP::TTL IP::CheckSum
5: 92.79.213.121 (92.79.213.121) IP::TTL IP::CheckSum
6: 92.79.214.2 (92.79.214.2) IP::TTL IP::CheckSum
7: 92.79.201.226 (92.79.201.226) IP::TTL IP::CheckSum
8: bln-145-254-5-158.arcor-ip.net (145.254.5.158) IP::TTL IP::CheckSum
9: 88.79.13.62 (88.79.13.62) IP::TTL IP::CheckSum
10: 81.200.194.234 (81.200.194.234) IP::TTL IP::CheckSum
11: 81.200.197.9 (81.200.197.9) IP::TTL IP::CheckSum
TCPOptionPad was added
TCPOptionMPTCPCapable was suppressed
12: 81.200.198.6 (81.200.198.6) TCP::CheckSum IP::TTL IP::CheckSum 
TCPOptionMaxSegSize::MaxSegSize

In this example, we sent a huge MSS and add the MPCAPABLE option which 
is used by Multipath TCP in the SYN. tracebox shows that at hop 11 there 
is a middlebox that removes the MPCAPABLE option and later on the MSS 
option is changed. tracebox will be presented at IMC'14 in October and 
the tool will be available in open-source from http://www.tracebox.org

Best regards,


Olivier Bonaventure


-- 
INL, ICTEAM, UCLouvain, Belgium, http://inl.info.ucl.ac.be

From emmanuel.baccelli@gmail.com  Tue Jul 30 14:51:55 2013
Return-Path: <emmanuel.baccelli@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 6648121E80A9 for <int-area@ietfa.amsl.com>; Tue, 30 Jul 2013 14:51:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.259
X-Spam-Level: 
X-Spam-Status: No, score=-1.259 tagged_above=-999 required=5 tests=[AWL=0.718,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 sqW0RU3si1Wt for <int-area@ietfa.amsl.com>; Tue, 30 Jul 2013 14:51:54 -0700 (PDT)
Received: from mail-oa0-x22b.google.com (mail-oa0-x22b.google.com [IPv6:2607:f8b0:4003:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id BA08E21E809D for <int-area@ietf.org>; Tue, 30 Jul 2013 14:51:54 -0700 (PDT)
Received: by mail-oa0-f43.google.com with SMTP id i10so12395849oag.30 for <int-area@ietf.org>; Tue, 30 Jul 2013 14:51:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=FOS/uvN3qn86o0qAAOentKpBQe9wEI4C5S2oo5Yv3JA=; b=WmSTDyRAB5Q3VemT3oUpVxb+6Wo7NljreARQvlvfJwT8PT1mxVKQk3WmQlpAmLudcc VqWcileIZLlcqutkt0bgnIDd9UHTKBXUHH2kJ1ZazdjdN/B2P1B6es0aLcTzoa3VofHC qcijvH3KChWQWMXVR0Iv2LmGV7epn1oQ9k6ibHgfb9pwjwC+nfxxGEdbm5B5OUanNNI7 49T3+Z+D1UyEi8EPLX3TYvYeyfH2lXV5VS5yQ+AYm5SqhyaOFo/WvXkkAB/q30UIwuTI AE79/ckltEM30KDjiZSKR+ZL3+Ko6g9kdLYceGEMeN9Qcd8hW2B9+PNwo16HKz6MRUR5 CcCQ==
MIME-Version: 1.0
X-Received: by 10.60.57.39 with SMTP id f7mr10670627oeq.92.1375221110702; Tue, 30 Jul 2013 14:51:50 -0700 (PDT)
Sender: emmanuel.baccelli@gmail.com
Received: by 10.76.82.133 with HTTP; Tue, 30 Jul 2013 14:51:50 -0700 (PDT)
Received: by 10.76.82.133 with HTTP; Tue, 30 Jul 2013 14:51:50 -0700 (PDT)
In-Reply-To: <51F7F30B.7090700@isi.edu>
References: <51F7E8AC.7060008@computer.org> <51F7F30B.7090700@isi.edu>
Date: Tue, 30 Jul 2013 23:51:50 +0200
X-Google-Sender-Auth: uMxmXDJNJ0Jcx6kE_CSScstIRxM
Message-ID: <CANK0pbYDeARGTAYqKLAWW=Hwmipcgm8OshNqdj8FunLu3FT6xw@mail.gmail.com>
From: Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr>
To: int-area@ietf.org
Content-Type: multipart/alternative; boundary=089e01538288ca8c3004e2c19d43
Subject: Re: [Int-area] What is a wireless link?
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, 30 Jul 2013 21:51:55 -0000

--089e01538288ca8c3004e2c19d43
Content-Type: text/plain; charset=ISO-8859-1

Hi Joe,
the sections you point out do not seem to be applicable to the case of
spontaneous wireless networks which are described in the draft, where
multicast or broadcast does not work in the usual sense (I suggest you look
at the draft).
Best
Emmanuel
On Jul 30, 2013 7:09 PM, "Joe Touch" <touch@isi.edu> wrote:

> You might take a look at RFC 3819, esp. the section on multicast and
> broadcast.
>
> Joe
>
> On 7/30/2013 9:24 AM, Charles E. Perkins wrote:
>
>> Hello folks,
>>
>> Emmanuel and I have a draft discussing the nature of wireless links and
>> adjacency.  As it turns out, it can be a source of great confusion as we
>> have
>> learned in past discussions.
>>
>> Please take a look at our draft:
>> http://tools.ietf.org/html/**draft-baccelli-manet-multihop-**
>> communication-01<http://tools.ietf.org/html/draft-baccelli-manet-multihop-communication-01>
>>
>> If there is interest, we would like to submit it as an Int-Area draft.
>>
>> The draft underwent extensive discussion in the autoconf working group
>> and is relevant to work in wireless-oriented working groups such as
>> [manet] and [roll].  We think it belongs in Int-Area because it does not
>> deal with routing.
>>
>> If there is still room on the agenda this week, I would be happy to make
>> a 5 minute presentation on the draft.
>>
>>

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

<p>Hi Joe, <br>
the sections you point out do not seem to be applicable to the case of spon=
taneous wireless networks which are described in the draft, where multicast=
 or broadcast does not work in the usual sense (I suggest you look at the d=
raft).<br>

Best<br>
Emmanuel</p>
<div class=3D"gmail_quote">On Jul 30, 2013 7:09 PM, &quot;Joe Touch&quot; &=
lt;<a href=3D"mailto:touch@isi.edu" target=3D"_blank">touch@isi.edu</a>&gt;=
 wrote:<br type=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

You might take a look at RFC 3819, esp. the section on multicast and broadc=
ast.<br>
<br>
Joe<br>
<br>
On 7/30/2013 9:24 AM, Charles E. Perkins wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Hello folks,<br>
<br>
Emmanuel and I have a draft discussing the nature of wireless links and<br>
adjacency. =A0As it turns out, it can be a source of great confusion as we<=
br>
have<br>
learned in past discussions.<br>
<br>
Please take a look at our draft:<br>
<a href=3D"http://tools.ietf.org/html/draft-baccelli-manet-multihop-communi=
cation-01" target=3D"_blank">http://tools.ietf.org/html/<u></u>draft-baccel=
li-manet-multihop-<u></u>communication-01</a><br>
<br>
If there is interest, we would like to submit it as an Int-Area draft.<br>
<br>
The draft underwent extensive discussion in the autoconf working group<br>
and is relevant to work in wireless-oriented working groups such as<br>
[manet] and [roll]. =A0We think it belongs in Int-Area because it does not<=
br>
deal with routing.<br>
<br>
If there is still room on the agenda this week, I would be happy to make<br=
>
a 5 minute presentation on the draft.<br>
<br>
</blockquote>
</blockquote></div>

--089e01538288ca8c3004e2c19d43--

From touch@isi.edu  Tue Jul 30 14:56:25 2013
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FDEB21E80CC for <int-area@ietfa.amsl.com>; Tue, 30 Jul 2013 14:56:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.939
X-Spam-Level: 
X-Spam-Status: No, score=-105.939 tagged_above=-999 required=5 tests=[AWL=0.660, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MfqPKCgBobbp for <int-area@ietfa.amsl.com>; Tue, 30 Jul 2013 14:56:20 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id A73E121E80C2 for <int-area@ietf.org>; Tue, 30 Jul 2013 14:56:20 -0700 (PDT)
Received: from [128.9.184.218] ([128.9.184.218]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id r6ULtjNf006719 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 30 Jul 2013 14:55:46 -0700 (PDT)
Message-ID: <51F83664.9050908@isi.edu>
Date: Tue, 30 Jul 2013 14:55:48 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr>
References: <51F7E8AC.7060008@computer.org> <51F7F30B.7090700@isi.edu> <CANK0pbaeXFB2fZRdea7c=bSD88i4aeNyEq_32LcYmwyFz2amNA@mail.gmail.com>
In-Reply-To: <CANK0pbaeXFB2fZRdea7c=bSD88i4aeNyEq_32LcYmwyFz2amNA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Julien Laganier <jlaganier@juniper.net>, Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] What is a wireless link?
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, 30 Jul 2013 21:56:25 -0000

Hi, Emmanuel,

The point of the RFC I cited is that "this is what the Internet 
expects". When your RF link doesn't support it, it will be in trouble 
and need some sort of emulation layer.

Joe

On 7/30/2013 2:42 PM, Emmanuel Baccelli wrote:
> Hi Joe,
> the sections you point out do not seem to be applicable to the case of
> spontaneous wireless networks which are described in the draft, where
> multicast or broadcast does not work in the usual sense (I suggest you
> look at the draft).
> Best
> Emmanuel
>
> On Jul 30, 2013 7:09 PM, "Joe Touch" <touch@isi.edu
> <mailto:touch@isi.edu>> wrote:
>
>     You might take a look at RFC 3819, esp. the section on multicast and
>     broadcast.
>
>     Joe
>
>     On 7/30/2013 9:24 AM, Charles E. Perkins wrote:
>
>         Hello folks,
>
>         Emmanuel and I have a draft discussing the nature of wireless
>         links and
>         adjacency.  As it turns out, it can be a source of great
>         confusion as we
>         have
>         learned in past discussions.
>
>         Please take a look at our draft:
>         http://tools.ietf.org/html/__draft-baccelli-manet-multihop-__communication-01
>         <http://tools.ietf.org/html/draft-baccelli-manet-multihop-communication-01>
>
>         If there is interest, we would like to submit it as an Int-Area
>         draft.
>
>         The draft underwent extensive discussion in the autoconf working
>         group
>         and is relevant to work in wireless-oriented working groups such as
>         [manet] and [roll].  We think it belongs in Int-Area because it
>         does not
>         deal with routing.
>
>         If there is still room on the agenda this week, I would be happy
>         to make
>         a 5 minute presentation on the draft.
>

From touch@isi.edu  Tue Jul 30 15:20:25 2013
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D34011E81ED for <int-area@ietfa.amsl.com>; Tue, 30 Jul 2013 15:20:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.999
X-Spam-Level: 
X-Spam-Status: No, score=-105.999 tagged_above=-999 required=5 tests=[AWL=0.600, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wbUddG7yMcyM for <int-area@ietfa.amsl.com>; Tue, 30 Jul 2013 15:20:17 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 5F0FF11E8159 for <int-area@ietf.org>; Tue, 30 Jul 2013 15:20:17 -0700 (PDT)
Received: from [128.9.184.218] ([128.9.184.218]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r6UMJNjR016226 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 30 Jul 2013 15:19:23 -0700 (PDT)
Message-ID: <51F83BED.9070409@isi.edu>
Date: Tue, 30 Jul 2013 15:19:25 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr>
References: <51F7E8AC.7060008@computer.org> <51F7F30B.7090700@isi.edu> <CANK0pbaeXFB2fZRdea7c=bSD88i4aeNyEq_32LcYmwyFz2amNA@mail.gmail.com> <51F83664.9050908@isi.edu>
In-Reply-To: <51F83664.9050908@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Julien Laganier <julien.ietf@gmail.com>, Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] What is a wireless link?
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, 30 Jul 2013 22:20:25 -0000

Re-sending with corrected email for Julien.

Joe

On 7/30/2013 2:55 PM, Joe Touch wrote:
> Hi, Emmanuel,
>
> The point of the RFC I cited is that "this is what the Internet
> expects". When your RF link doesn't support it, it will be in trouble
> and need some sort of emulation layer.
>
> Joe
>
> On 7/30/2013 2:42 PM, Emmanuel Baccelli wrote:
>> Hi Joe,
>> the sections you point out do not seem to be applicable to the case of
>> spontaneous wireless networks which are described in the draft, where
>> multicast or broadcast does not work in the usual sense (I suggest you
>> look at the draft).
>> Best
>> Emmanuel
>>
>> On Jul 30, 2013 7:09 PM, "Joe Touch" <touch@isi.edu
>> <mailto:touch@isi.edu>> wrote:
>>
>>     You might take a look at RFC 3819, esp. the section on multicast and
>>     broadcast.
>>
>>     Joe
>>
>>     On 7/30/2013 9:24 AM, Charles E. Perkins wrote:
>>
>>         Hello folks,
>>
>>         Emmanuel and I have a draft discussing the nature of wireless
>>         links and
>>         adjacency.  As it turns out, it can be a source of great
>>         confusion as we
>>         have
>>         learned in past discussions.
>>
>>         Please take a look at our draft:
>>
>> http://tools.ietf.org/html/__draft-baccelli-manet-multihop-__communication-01
>>
>>
>> <http://tools.ietf.org/html/draft-baccelli-manet-multihop-communication-01>
>>
>>
>>         If there is interest, we would like to submit it as an Int-Area
>>         draft.
>>
>>         The draft underwent extensive discussion in the autoconf working
>>         group
>>         and is relevant to work in wireless-oriented working groups
>> such as
>>         [manet] and [roll].  We think it belongs in Int-Area because it
>>         does not
>>         deal with routing.
>>
>>         If there is still room on the agenda this week, I would be happy
>>         to make
>>         a 5 minute presentation on the draft.
>>

From charliep@computer.org  Tue Jul 30 21:21:43 2013
Return-Path: <charliep@computer.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 3A6E721E8055 for <int-area@ietfa.amsl.com>; Tue, 30 Jul 2013 21:21:43 -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]
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 MBiGT6mQ3cTH for <int-area@ietfa.amsl.com>; Tue, 30 Jul 2013 21:21:38 -0700 (PDT)
Received: from elasmtp-dupuy.atl.sa.earthlink.net (elasmtp-dupuy.atl.sa.earthlink.net [209.86.89.62]) by ietfa.amsl.com (Postfix) with ESMTP id 4CECF11E80E4 for <int-area@ietf.org>; Tue, 30 Jul 2013 21:21:38 -0700 (PDT)
Received: from [46.189.28.101] (helo=[10.185.10.35]) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <charliep@computer.org>) id 1V4Nud-0008FO-Mh; Wed, 31 Jul 2013 00:21:23 -0400
Message-ID: <51F890B8.9090109@computer.org>
Date: Tue, 30 Jul 2013 21:21:12 -0700
From: "Charles E. Perkins" <charliep@computer.org>
Organization: Saratoga Blue Skies
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
References: <51F7E8AC.7060008@computer.org> <51F7F30B.7090700@isi.edu><CANK0pbaeXFB2fZRdea7c=bSD88i4aeNyEq_32LcYmwyFz2amNA@mail.gmail.com><51F83664.9050908@isi.edu> <51F83BED.9070409@isi.edu>
In-Reply-To: <51F83BED.9070409@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956d5d4673fe7faad8609f1121b0a8329a6357302c03fe86feb350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 46.189.28.101
Cc: Julien Laganier <julien.ietf@gmail.com>, Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] What is a wireless link?
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, 31 Jul 2013 04:21:43 -0000

Hello Joe,

At minimum, you might say that our draft would help
to understand the nature of any such adaptation layer.

However, for work along the lines done in manet and
roll and elsewhere, you might also say that "the internet"
expects "too much".  For instance, making link-layer
addresses come true across a population of mobile
wireless devices might take more bandwidth than is
really available.  Or it could cause more rapid battery
depletion.  These outcomes have been noted in the
past, and it would be a good idea to try to avoid them
in the future.

Regards,
Charlie P.

On 7/30/2013 3:19 PM, Joe Touch wrote:
> Re-sending with corrected email for Julien.
>
> Joe
>
> On 7/30/2013 2:55 PM, Joe Touch wrote:
>> Hi, Emmanuel,
>>
>> The point of the RFC I cited is that "this is what the Internet
>> expects". When your RF link doesn't support it, it will be in trouble
>> and need some sort of emulation layer.
>>
>> Joe
>>
>> On 7/30/2013 2:42 PM, Emmanuel Baccelli wrote:
>>> Hi Joe,
>>> the sections you point out do not seem to be applicable to the case of
>>> spontaneous wireless networks which are described in the draft, where
>>> multicast or broadcast does not work in the usual sense (I suggest you
>>> look at the draft).
>>> Best
>>> Emmanuel
>>>
>>> On Jul 30, 2013 7:09 PM, "Joe Touch" <touch@isi.edu
>>> <mailto:touch@isi.edu>> wrote:
>>>
>>>     You might take a look at RFC 3819, esp. the section on multicast 
>>> and
>>>     broadcast.
>>>
>>>     Joe
>>>
>>>     On 7/30/2013 9:24 AM, Charles E. Perkins wrote:
>>>
>>>         Hello folks,
>>>
>>>         Emmanuel and I have a draft discussing the nature of wireless
>>>         links and
>>>         adjacency.  As it turns out, it can be a source of great
>>>         confusion as we
>>>         have
>>>         learned in past discussions.
>>>
>>>         Please take a look at our draft:
>>>
>>> http://tools.ietf.org/html/__draft-baccelli-manet-multihop-__communication-01 
>>>
>>>
>>>
>>> <http://tools.ietf.org/html/draft-baccelli-manet-multihop-communication-01> 
>>>
>>>
>>>
>>>         If there is interest, we would like to submit it as an Int-Area
>>>         draft.
>>>
>>>         The draft underwent extensive discussion in the autoconf 
>>> working
>>>         group
>>>         and is relevant to work in wireless-oriented working groups
>>> such as
>>>         [manet] and [roll].  We think it belongs in Int-Area because it
>>>         does not
>>>         deal with routing.
>>>
>>>         If there is still room on the agenda this week, I would be 
>>> happy
>>>         to make
>>>         a 5 minute presentation on the draft.
>>>
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area
>


-- 
Regards,
Charlie P.


From alexandru.petrescu@gmail.com  Tue Jul 30 23:59:41 2013
Return-Path: <alexandru.petrescu@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 9E92421F9CAE for <int-area@ietfa.amsl.com>; Tue, 30 Jul 2013 23:59:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.127
X-Spam-Level: 
X-Spam-Status: No, score=-10.127 tagged_above=-999 required=5 tests=[AWL=0.122, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
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 SY2VCsD8unS7 for <int-area@ietfa.amsl.com>; Tue, 30 Jul 2013 23:59:35 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) by ietfa.amsl.com (Postfix) with ESMTP id B6AD021E8051 for <int-area@ietf.org>; Tue, 30 Jul 2013 23:59:24 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id r6V6xMgP007930 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <int-area@ietf.org>; Wed, 31 Jul 2013 08:59:22 +0200
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id r6V6xM9d022176 for <int-area@ietf.org>; Wed, 31 Jul 2013 08:59:22 +0200 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] ([132.166.86.7]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id r6V6xGYF022949 for <int-area@ietf.org>; Wed, 31 Jul 2013 08:59:22 +0200
Message-ID: <51F8B5C4.8000202@gmail.com>
Date: Wed, 31 Jul 2013 08:59:16 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: int-area@ietf.org
References: <51F7E8AC.7060008@computer.org> <51F7F30B.7090700@isi.edu> <CANK0pbYDeARGTAYqKLAWW=Hwmipcgm8OshNqdj8FunLu3FT6xw@mail.gmail.com>
In-Reply-To: <CANK0pbYDeARGTAYqKLAWW=Hwmipcgm8OshNqdj8FunLu3FT6xw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [Int-area] What is a wireless link?
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, 31 Jul 2013 06:59:41 -0000

Le 30/07/2013 23:51, Emmanuel Baccelli a écrit :
> Hi Joe, the sections you point out do not seem to be applicable to
> the case of spontaneous wireless networks which are described in the
> draft, where multicast or broadcast does not work in the usual sense
> (I suggest you look at the draft).

That is right.

On some wireless links that dont have link structure (802.11p, outside
the context of a bssid, no ass'n req/resp) the very meaning of broadcast
is confusing: broadcast reaches whoever is physically nearby (as in "TV
broadcast"), and not necessarily those who are in the same link/bssid
(as in "link broadcast").

Alex

> Best Emmanuel
>
> On Jul 30, 2013 7:09 PM, "Joe Touch" <touch@isi.edu
> <mailto:touch@isi.edu>> wrote:
>
> You might take a look at RFC 3819, esp. the section on multicast and
>  broadcast.
>
> Joe
>
> On 7/30/2013 9:24 AM, Charles E. Perkins wrote:
>
> Hello folks,
>
> Emmanuel and I have a draft discussing the nature of wireless links
> and adjacency.  As it turns out, it can be a source of great
> confusion as we have learned in past discussions.
>
> Please take a look at our draft:
> http://tools.ietf.org/html/__draft-baccelli-manet-multihop-__communication-01
>
>
>
<http://tools.ietf.org/html/draft-baccelli-manet-multihop-communication-01>
>
> If there is interest, we would like to submit it as an Int-Area
> draft.
>
> The draft underwent extensive discussion in the autoconf working
> group and is relevant to work in wireless-oriented working groups
> such as [manet] and [roll].  We think it belongs in Int-Area because
> it does not deal with routing.
>
> If there is still room on the agenda this week, I would be happy to
> make a 5 minute presentation on the draft.
>
>
>
> _______________________________________________ Int-area mailing list
> Int-area@ietf.org https://www.ietf.org/mailman/listinfo/int-area
>



From linda.dunbar@huawei.com  Wed Jul 31 02:16:08 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 3107C21F9D05; Wed, 31 Jul 2013 02:16:08 -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 agkFxxvXVKdo; Wed, 31 Jul 2013 02:16:03 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id E5BA121F9D12; Wed, 31 Jul 2013 02:11:26 -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 AVP16407; Wed, 31 Jul 2013 09:11:25 +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; Wed, 31 Jul 2013 10:11:11 +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; Wed, 31 Jul 2013 10:11:20 +0100
Received: from DFWEML509-MBX.china.huawei.com ([169.254.11.169]) by dfweml405-hub.china.huawei.com ([10.193.5.102]) with mapi id 14.01.0323.007; Wed, 31 Jul 2013 02:11:16 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: "ipv6@ietf.org" <ipv6@ietf.org>, Internet Area <int-area@ietf.org>
Thread-Topic: any concerns of SEND mixed with Proxy Gateway described in draft-nachum-sarp-06? 
Thread-Index: Ac6NzewNJHkq28RwQ12LSg9ChiEyhA==
Date: Wed, 31 Jul 2013 09:11:16 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F645B5269D@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.149.90]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F645B5269Ddfweml509mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [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: Wed, 31 Jul 2013 09:16:08 -0000

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

https://tools.ietf.org/html/draft-nachum-sarp-06 proposes a Proxy Gateway m=
echanism to limit switches' FDB (MAC table) sizes in an environment where h=
osts (or VMs) within one subnet (or VLAN) can spread over many access domai=
ns (or shelves or sites) and each access domain has hosts (VMs) belonging t=
o many subnets (or VLANs).

The main idea of SARP is to represent all VMs (or hosts) under each access =
domain by their corresponding access (or aggregation) node's MAC address re=
gardless whether the access (or aggregation) node is the VMs (hosts)' gatew=
ay or not. For example, when a host "a" under access domain "S" needs to co=
mmunicate with peers on the same VLAN but connected to different access dom=
ains, SARP requires "a" to use remote access node's MAC address rather than=
 peers' MAC addresses. By doing so, switches in each domain do not need to =
maintain a list of MAC addresses for all the VMs (hosts) in different acces=
s domains in their FDBs. Therefore, the switches' FDB size is limited regar=
dless how VLAN is spread.

However, when SEND is used, Access (or Aggregation) switches might not poss=
ess 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).


p.s.

Even though NVO3/TRILL provides an overlay mechanism so that the hosts (or =
VMs) addresses are hidden from the switches in the core, all the overlay ed=
ge nodes are still exposed to all the hosts MAC addresses on the VLANs that=
 are enabled on the edges, which can cause switches' FDB size explosion iss=
ue.



For example:

For a typical Access switch (Top of Rack)  with 40 physical servers attache=
d, where each server has 100 VMs, there are 4000 hosts under the Access Swi=
tch. If indeed hosts/VMs can be moved anywhere, the worst case for the Acce=
ss Switch is when all those 4000 VMs belong to different VLANs, i.e. the ac=
cess switch has 4000 VLANs enabled. If each VLAN has 200 hosts, this access=
 switch's MAC table potentially has 200*4000 =3D 800,000 entries.

Thank you very much for your feedback.


Linda Dunbar


--_000_4A95BA014132FF49AE685FAB4B9F17F645B5269Ddfweml509mbxchi_
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:Consolas;
	panose-1:2 11 6 9 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;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.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"><a href=3D"https://tools.ietf.org/html/draft-nachum-=
sarp-06">https://tools.ietf.org/html/draft-nachum-sarp-06</a> proposes a Pr=
oxy Gateway mechanism to limit switches&#8217; FDB (MAC table) sizes in an =
environment where hosts (or VMs) within one
 subnet (or VLAN) can spread over many access domains (or shelves or sites)=
 and each access domain has hosts (VMs) belonging to many subnets (or VLANs=
).
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The main idea of SARP is to represent all VMs (or ho=
sts) under each access domain by their corresponding access (or aggregation=
) node's MAC address regardless whether the access (or aggregation) node is=
 the VMs (hosts)&#8217; gateway or not.
 For example, when a host &#8220;a&#8221; under access domain &#8220;S&#822=
1; needs to communicate with peers on the same VLAN but connected to differ=
ent access domains, SARP requires &#8220;a&#8221; to use remote access node=
&#8217;s MAC address rather than peers&#8217; MAC addresses. By doing so, s=
witches
 in each domain do not need to maintain a list of MAC addresses for all the=
 VMs (hosts) in different access domains in their FDBs. Therefore, the swit=
ches&#8217; FDB size is limited regardless how VLAN is spread.<o:p></o:p></=
p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">However, when SEND is used, Access (or Aggregation) =
switches might not possess knowledge of the attached hosts (VMs)&#8217; pri=
vate keys.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Are there any concerns/feedback for giving the follo=
wing recommendation in our draft? Any preferences?<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">1) state that SARP is not=
 recommended when SEND is deployed;
<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-left:.5in">2) recommend using RFC649=
6 (Secure Proxy ND Support for SEND).
<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">p.s. <o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">Even though NVO3/TRILL provides an o=
verlay mechanism so that the hosts (or VMs) addresses are hidden from the s=
witches in the core, all the overlay edge nodes are still
 exposed to all the hosts MAC addresses on the VLANs that are enabled on th=
e edges, which can cause switches&#8217; FDB size explosion issue.
<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">For example:
<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">For a typical Access switch (Top of =
Rack)&nbsp; with 40 physical servers attached, where each server has 100 VM=
s, there are 4000 hosts under the Access Switch. If indeed hosts/VMs
 can be moved anywhere, the worst case for the Access Switch is when all th=
ose 4000 VMs belong to different VLANs, i.e. the access switch has 4000 VLA=
Ns enabled. If each VLAN has 200 hosts, this access switch&#8217;s MAC tabl=
e potentially has 200*4000 =3D 800,000 entries.
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-align:justify;text-justify:inter-ideog=
raph"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"text-align:justify;text-justify:inter-ideog=
raph">Thank you very much for your feedback.
<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"text-align:justify;text-justify:inter-ideog=
raph"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Linda Dunbar<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_4A95BA014132FF49AE685FAB4B9F17F645B5269Ddfweml509mbxchi_--

From emmanuel.baccelli@gmail.com  Tue Jul 30 14:42:20 2013
Return-Path: <emmanuel.baccelli@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 C6EC211E81D4 for <int-area@ietfa.amsl.com>; Tue, 30 Jul 2013 14:42:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.139
X-Spam-Level: 
X-Spam-Status: No, score=-1.139 tagged_above=-999 required=5 tests=[AWL=0.838,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 E-3FI2ryRmzX for <int-area@ietfa.amsl.com>; Tue, 30 Jul 2013 14:42:20 -0700 (PDT)
Received: from mail-oa0-x22c.google.com (mail-oa0-x22c.google.com [IPv6:2607:f8b0:4003:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 0D6B011E8152 for <int-area@ietf.org>; Tue, 30 Jul 2013 14:42:19 -0700 (PDT)
Received: by mail-oa0-f44.google.com with SMTP id l20so14111990oag.3 for <int-area@ietf.org>; Tue, 30 Jul 2013 14:42:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=El3hXaHQUZRZpNRAkaTg1wBo1Z93SmdTPbaZmTyD8d4=; b=bIZcph2M896uzDiVzPOBPros2F8b2h+h3qpZo/Xe49bfN2cCqD8ZCKnqecWGlmTR1q OCqN293hwn1Bt3f/owVsqUN0MoO3qWNBKENnF12OdJqAXOT/C3CrAWU6RBpImw6//QW1 5TztM8sH9fa3YGNeR8+3GBbHyhQa57tk9tnAtPbjxnmNyE21dAVu2yV+8elaft9vtXEP oJobZgDYaOEMQNmCFo58JDA2IjjkmteG8yghgtrXel+iUBmyVcDgiDedLAT3p0SihyyI EO74tRkLHzFKiT8p/DU2FNu78y1b+dwydBpu6cc1rJhj22TQ6VScTUEuguBoMdZJGnjM JXpg==
MIME-Version: 1.0
X-Received: by 10.60.38.234 with SMTP id j10mr20448391oek.42.1375220539444; Tue, 30 Jul 2013 14:42:19 -0700 (PDT)
Sender: emmanuel.baccelli@gmail.com
Received: by 10.76.82.133 with HTTP; Tue, 30 Jul 2013 14:42:19 -0700 (PDT)
Received: by 10.76.82.133 with HTTP; Tue, 30 Jul 2013 14:42:19 -0700 (PDT)
In-Reply-To: <51F7F30B.7090700@isi.edu>
References: <51F7E8AC.7060008@computer.org> <51F7F30B.7090700@isi.edu>
Date: Tue, 30 Jul 2013 23:42:19 +0200
X-Google-Sender-Auth: _KuNbZxjVMi5AqBvPo2mm9WlKn0
Message-ID: <CANK0pbaeXFB2fZRdea7c=bSD88i4aeNyEq_32LcYmwyFz2amNA@mail.gmail.com>
From: Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr>
To: Joe Touch <touch@isi.edu>, Suresh Krishnan <suresh.krishnan@ericsson.com>,  Internet Area <int-area@ietf.org>, Julien Laganier <jlaganier@juniper.net>
Content-Type: multipart/alternative; boundary=089e0149c210bdd2fe04e2c17b80
X-Mailman-Approved-At: Wed, 31 Jul 2013 07:22:30 -0700
Subject: Re: [Int-area] What is a wireless link?
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, 30 Jul 2013 21:42:20 -0000

--089e0149c210bdd2fe04e2c17b80
Content-Type: text/plain; charset=ISO-8859-1

Hi Joe,
the sections you point out do not seem to be applicable to the case of
spontaneous wireless networks which are described in the draft, where
multicast or broadcast does not work in the usual sense (I suggest you look
at the draft).
Best
Emmanuel
On Jul 30, 2013 7:09 PM, "Joe Touch" <touch@isi.edu> wrote:

> You might take a look at RFC 3819, esp. the section on multicast and
> broadcast.
>
> Joe
>
> On 7/30/2013 9:24 AM, Charles E. Perkins wrote:
>
>> Hello folks,
>>
>> Emmanuel and I have a draft discussing the nature of wireless links and
>> adjacency.  As it turns out, it can be a source of great confusion as we
>> have
>> learned in past discussions.
>>
>> Please take a look at our draft:
>> http://tools.ietf.org/html/**draft-baccelli-manet-multihop-**
>> communication-01<http://tools.ietf.org/html/draft-baccelli-manet-multihop-communication-01>
>>
>> If there is interest, we would like to submit it as an Int-Area draft.
>>
>> The draft underwent extensive discussion in the autoconf working group
>> and is relevant to work in wireless-oriented working groups such as
>> [manet] and [roll].  We think it belongs in Int-Area because it does not
>> deal with routing.
>>
>> If there is still room on the agenda this week, I would be happy to make
>> a 5 minute presentation on the draft.
>>
>>

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

<p>Hi Joe,<br>
the sections you point out do not seem to be applicable to the case of spon=
taneous wireless networks which are described in the draft, where multicast=
 or broadcast does not work in the usual sense (I suggest you look at the d=
raft).<br>

Best <br>
Emmanuel</p>
<div class=3D"gmail_quote">On Jul 30, 2013 7:09 PM, &quot;Joe Touch&quot; &=
lt;<a href=3D"mailto:touch@isi.edu">touch@isi.edu</a>&gt; wrote:<br type=3D=
"attribution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
You might take a look at RFC 3819, esp. the section on multicast and broadc=
ast.<br>
<br>
Joe<br>
<br>
On 7/30/2013 9:24 AM, Charles E. Perkins wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Hello folks,<br>
<br>
Emmanuel and I have a draft discussing the nature of wireless links and<br>
adjacency. =A0As it turns out, it can be a source of great confusion as we<=
br>
have<br>
learned in past discussions.<br>
<br>
Please take a look at our draft:<br>
<a href=3D"http://tools.ietf.org/html/draft-baccelli-manet-multihop-communi=
cation-01" target=3D"_blank">http://tools.ietf.org/html/<u></u>draft-baccel=
li-manet-multihop-<u></u>communication-01</a><br>
<br>
If there is interest, we would like to submit it as an Int-Area draft.<br>
<br>
The draft underwent extensive discussion in the autoconf working group<br>
and is relevant to work in wireless-oriented working groups such as<br>
[manet] and [roll]. =A0We think it belongs in Int-Area because it does not<=
br>
deal with routing.<br>
<br>
If there is still room on the agenda this week, I would be happy to make<br=
>
a 5 minute presentation on the draft.<br>
<br>
</blockquote>
</blockquote></div>

--089e0149c210bdd2fe04e2c17b80--

From touch@isi.edu  Wed Jul 31 08:34:01 2013
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2241D21F9C7A for <int-area@ietfa.amsl.com>; Wed, 31 Jul 2013 08:33:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.266
X-Spam-Level: 
X-Spam-Status: No, score=-106.266 tagged_above=-999 required=5 tests=[AWL=0.333, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i60bj9fEAZt8 for <int-area@ietfa.amsl.com>; Wed, 31 Jul 2013 08:33:51 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 5AE9E21F9C4E for <int-area@ietf.org>; Wed, 31 Jul 2013 08:33:46 -0700 (PDT)
Received: from [192.168.1.91] (pool-71-105-85-4.lsanca.dsl-w.verizon.net [71.105.85.4]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r6VFX61A008545 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 31 Jul 2013 08:33:16 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset=iso-8859-1
From: Joe Touch <touch@isi.edu>
In-Reply-To: <51F890B8.9090109@computer.org>
Date: Wed, 31 Jul 2013 08:33:07 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <5E7A66F8-CDFA-4B2D-BBB7-338807BAC7D9@isi.edu>
References: <51F7E8AC.7060008@computer.org> <51F7F30B.7090700@isi.edu><CANK0pbaeXFB2fZRdea7c=bSD88i4aeNyEq_32LcYmwyFz2amNA@mail.gmail.com><51F83664.9050908@isi.edu> <51F83BED.9070409@isi.edu> <51F890B8.9090109@computer.org>
To: "Charles E. Perkins" <charliep@computer.org>
X-Mailer: Apple Mail (2.1508)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Julien Laganier <julien.ietf@gmail.com>, Internet Area <int-area@ietf.org>
Subject: Re: [Int-area] What is a wireless link?
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, 31 Jul 2013 15:34:01 -0000

Hi, Charlie,

On Jul 30, 2013, at 9:21 PM, Charles E. Perkins <charliep@computer.org> =
wrote:

> Hello Joe,
>=20
> At minimum, you might say that our draft would help
> to understand the nature of any such adaptation layer.

I agree, but it clearly ought to be put into the context of that RFC, =
which is currently not discussed.

> However, for work along the lines done in manet and
> roll and elsewhere, you might also say that "the internet"
> expects "too much".  For instance, making link-layer
> addresses come true across a population of mobile
> wireless devices might take more bandwidth than is
> really available.  Or it could cause more rapid battery
> depletion.  These outcomes have been noted in the
> past, and it would be a good idea to try to avoid them
> in the future.

Sure, but my view is that this means that some wireless systems are =
(alone) insufficient to be Internet subnets. We've seen this before - =
e.g., ATM required LANE because of a lack of a broadcast capability, and =
emulated it to support ARP.

I'm not sure whether you're also arguing that the Internet expectations =
ought to change. In some cases this makes sense (dealing with adjustable =
BW), but in other cases (lack of broadcast) it argues more that wireless =
can't act as an Internet L2 subnet. Either another layer (in the spirit =
of LANE or AAL) needs to be added to wireless nets to support what the =
Internet expects of L2, or the wireless switches need to act more like =
Internet routers (in which case some wireless nets cannot be Internet =
subnets).

Joe

>=20
> Regards,
> Charlie P.
>=20
> On 7/30/2013 3:19 PM, Joe Touch wrote:
>> Re-sending with corrected email for Julien.
>>=20
>> Joe
>>=20
>> On 7/30/2013 2:55 PM, Joe Touch wrote:
>>> Hi, Emmanuel,
>>>=20
>>> The point of the RFC I cited is that "this is what the Internet
>>> expects". When your RF link doesn't support it, it will be in =
trouble
>>> and need some sort of emulation layer.
>>>=20
>>> Joe
>>>=20
>>> On 7/30/2013 2:42 PM, Emmanuel Baccelli wrote:
>>>> Hi Joe,
>>>> the sections you point out do not seem to be applicable to the case =
of
>>>> spontaneous wireless networks which are described in the draft, =
where
>>>> multicast or broadcast does not work in the usual sense (I suggest =
you
>>>> look at the draft).
>>>> Best
>>>> Emmanuel
>>>>=20
>>>> On Jul 30, 2013 7:09 PM, "Joe Touch" <touch@isi.edu
>>>> <mailto:touch@isi.edu>> wrote:
>>>>=20
>>>>    You might take a look at RFC 3819, esp. the section on multicast =
and
>>>>    broadcast.
>>>>=20
>>>>    Joe
>>>>=20
>>>>    On 7/30/2013 9:24 AM, Charles E. Perkins wrote:
>>>>=20
>>>>        Hello folks,
>>>>=20
>>>>        Emmanuel and I have a draft discussing the nature of =
wireless
>>>>        links and
>>>>        adjacency.  As it turns out, it can be a source of great
>>>>        confusion as we
>>>>        have
>>>>        learned in past discussions.
>>>>=20
>>>>        Please take a look at our draft:
>>>>=20
>>>> =
http://tools.ietf.org/html/__draft-baccelli-manet-multihop-__communication=
-01=20
>>>>=20
>>>>=20
>>>> =
<http://tools.ietf.org/html/draft-baccelli-manet-multihop-communication-01=
>=20
>>>>=20
>>>>=20
>>>>        If there is interest, we would like to submit it as an =
Int-Area
>>>>        draft.
>>>>=20
>>>>        The draft underwent extensive discussion in the autoconf =
working
>>>>        group
>>>>        and is relevant to work in wireless-oriented working groups
>>>> such as
>>>>        [manet] and [roll].  We think it belongs in Int-Area because =
it
>>>>        does not
>>>>        deal with routing.
>>>>=20
>>>>        If there is still room on the agenda this week, I would be =
happy
>>>>        to make
>>>>        a 5 minute presentation on the draft.
>>>>=20
>> _______________________________________________
>> Int-area mailing list
>> Int-area@ietf.org
>> https://www.ietf.org/mailman/listinfo/int-area
>>=20
>=20
>=20
> --=20
> Regards,
> Charlie P.


From touch@isi.edu  Wed Jul 31 08:41:45 2013
Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8032721F9E9D for <int-area@ietfa.amsl.com>; Wed, 31 Jul 2013 08:41:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.35
X-Spam-Level: 
X-Spam-Status: No, score=-106.35 tagged_above=-999 required=5 tests=[AWL=0.250, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FvW4NcL8EFNn for <int-area@ietfa.amsl.com>; Wed, 31 Jul 2013 08:41:38 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 1127F21F9964 for <int-area@ietf.org>; Wed, 31 Jul 2013 08:41:38 -0700 (PDT)
Received: from [192.168.1.91] (pool-71-105-85-4.lsanca.dsl-w.verizon.net [71.105.85.4]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id r6VFeuWx022270 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 31 Jul 2013 08:41:06 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset=iso-8859-1
From: Joe Touch <touch@isi.edu>
In-Reply-To: <51F8B5C4.8000202@gmail.com>
Date: Wed, 31 Jul 2013 08:40:56 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <AB56F251-2746-44CF-BCE6-D003C18B0742@isi.edu>
References: <51F7E8AC.7060008@computer.org> <51F7F30B.7090700@isi.edu> <CANK0pbYDeARGTAYqKLAWW=Hwmipcgm8OshNqdj8FunLu3FT6xw@mail.gmail.com> <51F8B5C4.8000202@gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-Mailer: Apple Mail (2.1508)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: int-area@ietf.org
Subject: Re: [Int-area] What is a wireless link?
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, 31 Jul 2013 15:41:45 -0000

On Jul 30, 2013, at 11:59 PM, Alexandru Petrescu =
<alexandru.petrescu@gmail.com> wrote:

> Le 30/07/2013 23:51, Emmanuel Baccelli a =E9crit :
>> Hi Joe, the sections you point out do not seem to be applicable to
>> the case of spontaneous wireless networks which are described in the
>> draft, where multicast or broadcast does not work in the usual sense
>> (I suggest you look at the draft).
>=20
> That is right.
>=20
> On some wireless links that dont have link structure (802.11p, outside
> the context of a bssid, no ass'n req/resp) the very meaning of =
broadcast
> is confusing: broadcast reaches whoever is physically nearby (as in =
"TV
> broadcast"), and not necessarily those who are in the same link/bssid
> (as in "link broadcast").

Agreed, which is why such wireless either needs to include L3 routers or =
to emulate broadcast (e.g., see ATM LANE for an example). Simply "not =
having" broadcast basically means that an L2 technology cannot operate =
as an Internet subnet.=20

I.e., although even pigeons can be Internet point-to-point links, but =
not everything can be an Internet subnet.

Joe


>=20
> Alex
>=20
>> Best Emmanuel
>>=20
>> On Jul 30, 2013 7:09 PM, "Joe Touch" <touch@isi.edu
>> <mailto:touch@isi.edu>> wrote:
>>=20
>> You might take a look at RFC 3819, esp. the section on multicast and
>> broadcast.
>>=20
>> Joe
>>=20
>> On 7/30/2013 9:24 AM, Charles E. Perkins wrote:
>>=20
>> Hello folks,
>>=20
>> Emmanuel and I have a draft discussing the nature of wireless links
>> and adjacency.  As it turns out, it can be a source of great
>> confusion as we have learned in past discussions.
>>=20
>> Please take a look at our draft:
>> =
http://tools.ietf.org/html/__draft-baccelli-manet-multihop-__communication=
-01
>>=20
>>=20
>>=20
> =
<http://tools.ietf.org/html/draft-baccelli-manet-multihop-communication-01=
>
>>=20
>> If there is interest, we would like to submit it as an Int-Area
>> draft.
>>=20
>> The draft underwent extensive discussion in the autoconf working
>> group and is relevant to work in wireless-oriented working groups
>> such as [manet] and [roll].  We think it belongs in Int-Area because
>> it does not deal with routing.
>>=20
>> If there is still room on the agenda this week, I would be happy to
>> make a 5 minute presentation on the draft.
>>=20
>>=20
>>=20
>> _______________________________________________ Int-area mailing list
>> Int-area@ietf.org https://www.ietf.org/mailman/listinfo/int-area
>>=20
>=20
>=20
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area

