RE: draft-wang-6man-flow-label-reflection

"Aijun Wang" <wangaijun@tsinghua.org.cn> Sat, 15 November 2014 01:06 UTC

Return-Path: <wangaijun@tsinghua.org.cn>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C42B11AD4B9 for <ipv6@ietfa.amsl.com>; Fri, 14 Nov 2014 17:06:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.589
X-Spam-Level:
X-Spam-Status: No, score=-1.589 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HOST_MISMATCH_COM=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gstMjmYTW5zV for <ipv6@ietfa.amsl.com>; Fri, 14 Nov 2014 17:06:16 -0800 (PST)
Received: from tsinghua.org.cn (mail.alumail.com [211.151.65.103]) by ietfa.amsl.com (Postfix) with ESMTP id 901A51ACE6B for <ipv6@ietf.org>; Fri, 14 Nov 2014 17:06:15 -0800 (PST)
Received: from ctbriwangaij (unknown [219.142.69.77]) by app1 (Coremail) with SMTP id Z0GX06B7LwEXlWZUWHAhAA==.44503S4; Sat, 15 Nov 2014 07:50:00 +0800 (CST)
From: Aijun Wang <wangaijun@tsinghua.org.cn>
To: 'Jeroen Massar' <jeroen@massar.ch>, 'Sheng Jiang' <jiangsheng@huawei.com>, '6man WG' <ipv6@ietf.org>
References: <5465C0AC.10801@massar.ch> <5D36713D8A4E7348A7E10DF7437A4B923AF75421@nkgeml512-mbx.china.huawei.com>, <546681A0.9070703@massar.ch> <5D36713D8A4E7348A7E10DF7437A4B923AF75695@nkgeml512-mbx.china.huawei.com> <5466928E.6070800@massar.ch>
In-Reply-To: <5466928E.6070800@massar.ch>
Subject: RE: draft-wang-6man-flow-label-reflection
Date: Sat, 15 Nov 2014 09:05:56 +0800
Message-ID: <008801d00070$580df030$0829d090$@org.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AdAAWdpmT5qQur6BRoik4MzkQhukMAAFVI5A
Content-Language: zh-cn
X-CM-TRANSID: Z0GX06B7LwEXlWZUWHAhAA==.44503S4
X-Coremail-Antispam: 1U3129KBjvJXoW7AF18uw4DCw43Kr48AFW5ZFb_yoW8Xr45pr 13Gr17Kr1DJFyjy3yktw1rKr1Fvr48Jr1UJw15tF10y3y5Ar1UJF4DJw1rJ34UXrWrXa45 trWUuw4DGa13ZFDanT9S1TB71UUUUUUv73VFW2AGmfu7bjvjm3AaLaJ3UjIYCTnIWjBvb7 Iv0xC_Jr1l5I8CrVACY4xI64kE6c02F40Ex7xfM7kC6x804xWl14x267AKxVW8JVW5JwAF xVCF77xC6IxKo4kEV4yl1I0EscIYIxCEI4klw4CSwwAv7VCjz48v1sIEY20_GF1lx4CE17 CEb7AF67AKxVWUXVWUAjIFyTuYvjfUF38nUUUUU
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/P6XDkjafrDAzgpSQqruxLstsGw8
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Nov 2014 01:06:18 -0000

Hi, Jeroen:

Service Provider wants to apply the same policy to the upstream and
downstream of one session, or more accurately, apply the policy to
downstream of one session based on the recognition of it upstream packet.
The flow label can be used to identify the unique session between one pair
of IPv6 hosts, and alleviate the burden for the network device to recognize
the downstream packet, for example, http response packet. We think this is
one appropriate use case for the flow label.

Best Regards. 

-----Original Message-----
From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Jeroen Massar
Sent: Saturday, November 15, 2014 7:39 AM
To: Sheng Jiang; 6man WG
Subject: Re: draft-wang-6man-flow-label-reflection

On 2014-11-14 23:48, Sheng Jiang wrote:
> 
> 
>> ________________________________________
>> From: Jeroen Massar [jeroen@massar.ch]
>>
>> The word "Flow Label" is hidden in the ECMP calculation.
> 
> Even there is failure in ECMP use case, it does not mean failure for other
use cases.

As the load balancing use case is the number one reason for the Flow Label
to have an existance, which other use cases would that be?

Greets,
 Jeroen

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------