Re: [Detnet-dp-dt] Quick notes from 4/11/17 call

Hi Yuanlong,

Comments inline.

> On Apr 12, 2017, at 6:31 PM, Jiangyuanlong <jiangyuanlong@huawei.com> wrote:
> 
> Hi Jouni,
> 
> Many thanks for the notes. It is quite a good progress IMO.
> But could you give some more hints on the point "incoming PW labels have to be the same to trigger the duplicate detection”?

In Chicago discussion we agreed that incoming PWs for a given detnet flow need to have the same PW labels to trigger PREF. Labels can be different on each segment and direction, though. This is what we agreed.

> I missed the discussion on this point, but as shown in my previous slides:
> 1. Multiple PW labels can be mapped to the same duplicate detection module.
> 2. If a DA-S-PE receives the same PW label from both DA-T-PE and its peer DA-S-PE, the traffic from them will be indistinguishable, and traffic from the peer DA-S-PE will be looped on the S-PE in some cases. As a result, duplicate detection on the peer S-PE will become more challenging.

The labels below PW label are still different when a packet arrives from DA-T-PE and peering DA-S-PE. I do not see the issue.
Also, what are “some cases” for looping you refer here?

Thanks,
	Jouni

> 
> Thanks,
> Yuanlong
> 
> -----Original Message-----
> From: Detnet-dp-dt [mailto:detnet-dp-dt-bounces@ietf.org] On Behalf Of Jouni Korhonen
> Sent: Thursday, April 13, 2017 4:36 AM
> To: Detnet-dp-dt@ietf.org
> Subject: [Detnet-dp-dt] Quick notes from 4/11/17 call
> 
> Present: Jouni, Janos, Balazs, David, Loa, Norm, Yuanlong
> 
> Agenda:
> * recap of the IETF98 corridor discussions & descisions
> * list of things to do
> 
> Discussion & decision:
> * Jouni sent out RFC6621 pointer for Simplified Multicast Forwarding that does duplicate detection and elimination
> * Solutions draft:
> - update the PW encapsulation i.e., no Flow-ID and incoming PW labels have to be the same to trigger the duplicate detection. 
> - IPv6 use flow label for detnet flow identification, new extension header for seqnum.
> - on IPv6 path stitching policy routing, multicast with with proper distribution tree and segment routing were discussed as possible alternatives instead of tunneling. Needs more discussion.
> - no good solution for IPv4. Just left it out. One can use PWs to transport IPv4 as a packet PW.
> - CoS/QoS update to be done. CoS is “easier” to start with.. first describe how the TC or DSCP bits need to be brought all the down to the most outer level.
> * Alternatives draft (now expired):
> - update the conclusions to state PW + IPv6 (native IP mode) are way to go. No good solution for IPv4.
> * Problem Statement:
> - Norm will ship an update.
> * Webex time will change. It will be Tuesday 6AM Pacific starting from next call.
> * solutions and alternative draft updates hopefully out this week.
> 
> Next call:
> no call next week 4/18/17.
> 
> -- 
> Jouni Korhonen, Broadcom, Core Switching Group
> +1-408-391-7160
> 
> 
> 
> _______________________________________________
> Detnet-dp-dt mailing list
> Detnet-dp-dt@ietf.org
> https://www.ietf.org/mailman/listinfo/detnet-dp-dt
> _______________________________________________
> Detnet-dp-dt mailing list
> Detnet-dp-dt@ietf.org
> https://www.ietf.org/mailman/listinfo/detnet-dp-dt