Subject: Flow Label Reflection //FW: New Version Notification for draft-wang-6man-flow-label-reflection-01.txt

From: Sheng Jiang <[email-masked]>
Date: Tue, 10 Mar 2015 02:37:15 +0000

Hi, 6man,

We have submitted an update version of our flow label reflection proposal according to previous discussion. This mechanism would like the network operators to efficiently correlate bidirection communication of one session together. It simplifies the network traffic recognition process in network operations and helps to make the policy for both directions of traffic of one session consistent. It has been implemented in the stable Linux Kernel.

All reviews and comments are appreciated.

Many thanks and best regards,

Sheng

>-----Original Message-----
>From: [email-masked] [mailto:[email-masked]]
>Sent: Monday, March 09, 2015 2:11 PM
>To: Aijun Wang; Aijun Wang; Sheng Jiang; Sheng Jiang
>Subject: New Version Notification for
>draft-wang-6man-flow-label-reflection-01.txt
>
>
>A new version of I-D, draft-wang-6man-flow-label-reflection-01.txt
>has been successfully submitted by Sheng Jiang and posted to the
>IETF repository.
>
>Name:		draft-wang-6man-flow-label-reflection
>Revision:	01
>Title:		IPv6 Flow Label Reflection
>Document date:	2015-03-08
>Group:		Individual Submission
>Pages:		11
>URL:
>http://www.ietf.org/internet-drafts/draft-wang-6man-flow-label-reflection-0
>1.txt
>Status:
>https://datatracker.ietf.org/doc/draft-wang-6man-flow-label-reflection/
>Htmlized:
>http://tools.ietf.org/html/draft-wang-6man-flow-label-reflection-01
>Diff:
>http://www.ietf.org/rfcdiff?url2=draft-wang-6man-flow-label-reflection-01
>
>Abstract:
>   The current definition of the IPv6 Flow Label focuses mainly on how
>   the packet source forms the value of this field and how the forwarder
>   in-path treats it.  In network operations, there are needs to
>   correlate an upstream session and the corresponding downstream
>   session together.  This document propose a flow label reflection
>   mechanism that network devices copy the flow label value from
>   received packets to the corresponding flow label field in return
>   packets.  This mechanism could simplify the network traffic
>   recognition process in network operations and make the policy for
>   both directions of traffic of one session consistent.
>
>
>
>
>Please note that it may take a couple of minutes from the time of submission
>until the htmlized version and diff are available at tools.ietf.org.
>
>The IETF Secretariat