[IPv6]Re: I-D Action: draft-peng-6man-cw-option-00.txt

[彭少富 <[e-mail]>]

Hi Brian,

Thanks for your comments. Please see inline.

Regards,
PSF




Original


From: BrianECarpenter <[e-mail]>
To: 6man <[e-mail]>;[e-mail] <[e-mail]>;
Date: 2025年12月24日 06:48
Subject: [IPv6]Re: I-D Action: draft-peng-6man-cw-option-00.txt

Hi,
 
The Introduction of this draft says:
 
> Multiple customer flows may encapsulate the same Flow Label.  
 
If that is true, RFC 6437 has not been implemented correctly in the original flow, since one flow == one flow label. Perhaps you mean this:
 
"Multiple customer flows may be encapsulated in outer IPv6 packets that use the same Flow Label, regardless of the Flow Label of the encapsulated packets." 
 
#PSF: Actually mean this. I will modify the text in the next version.


Also, when the flow label is in use, the normal 5-tuple should be replaced by a 3-tuple {source address, destination address, flow label} or even by a 6-tuple including the flow label. In any case, there's no reaon why the original flow label shouldn't be available.
 
#PSF: The goal of this draft is to identify customer flow only based on outer IPv6 header encapsulated by ingress PE, so 3-tuple (of outer IPv6 header) seems to meet this goal. 
However, the Flow Label is mainly used for load distribution, and the allocated Flow Label value (von Neumann algorithm as mentioned in RFC6437) can not guarantee absolutely unique (although uqnique with high probability). 
The impact of not guaranteeing uniqueness on load distribution is not serious, but it is serious for the flow-specific treatment that this document aims to achieve, e.g, packet replication, elimination, reordering.
So, Flow Label is not suitable for this document.


That doesn't, of course, provide the other parameters that you require.
 
I think you also need to clarify that destination options cannot in practice be used across the global Internet, so the scope of your proposal is a single provider.
 
#PSF: Yes, it is not for large groups of domains such as the Internet. Will clarify it in the next version.


Regards/Ngā mihi
    Brian Carpenter
 
On 23-Dec-25 20:04, [e-mail] wrote:
> Internet-Draft draft-peng-6man-cw-option-00.txt is now available.
>  
>     Title:   Control Word Option
>     Author:  Shaofu Peng
>     Name:    draft-peng-6man-cw-option-00.txt
>     Pages:   6
>     Dates:   2025-12-22
>  
> Abstract:
>  
>     This document introduces new IPv6 options for DOH, to carry flow
>     identifier, sequence number, and other customer service mapped
>     information that is encapsulated by the provider network, to support
>     flow-specific treatment, such as statistics, monitoring, QoS,
>     redundancy elimination and reordering, etc.
>  
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-peng-6man-cw-option/
>  
> There is also an HTMLized version available at:
> https://datatracker.ietf.org/doc/html/draft-peng-6man-cw-option-00
>  
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts
>  
>  
> _______________________________________________
> I-D-Announce mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[e-mail]
List Info: https://mailman3.ietf.org/mailman3/lists/[e-mail]/
--------------------------------------------------------------------