Re: [Detnet] New Version Notification for draft-pthubert-detnet-ipv6-hbh-01.txt

Hi Pascal,

thanks for the draft. I have some questions for clarification on it.
In general:
1, Do You propose to use IPv6/UDP tunneling between DetNet relay nodes?
"... the DetNet information ... and can be added by a service instance as part of the 
>>> encapsulation by the Ingress of the DetNet path <<<." 

2, Are the proposed options encoded in the tunnel IPv6 header?
" It can then be accessed by the intermediate DetNet routers
>>> without <<< the need of a deep packet inspection (e.g., >>> beyond UDP <<<)."

3, All that DetNet functions need are FlowId and Sequence information. 
Could You please clarify the role of the path option for DetNet functions?
Or path option is used by RAW (and not DetNet) specific functions?

In particular:
4, If a tunnel is used, why not to encode the information in Destination Options header?
Sequence information is not used by DetNet Transit nodes.
" In that context, it makes sense to consider >>> Hop-by-Hop Options <<< to transport the 
information that is relevant to DetNet."

5, Why are new sequence counter formats needed? 
" ... and it is possible that the value 0 is reserved when wrapping, to the option offers both 
possibilities, wrapping to either 0 or to 1."

6, Could You please clarify why time stamp is needed? For which DetNet function?
" This specification also allows to use a time stamp for the packet redundancy information, ..."

7, R-Tag format and sequencing function is defined by 802.1CB-2017. It is incremented by 1 
when a packet is sent. Have I missed something here?
"... though it >>> cannot <<< be assumed that the R-Tag is sequentially incremented; ..."

8, Is the hybrid model used by a RAW function?
" This specification also allows for an >> hybrid model <<< with a coarse
grained packet sequence within a coarse grained time stamp."

9, What DetNet state is meant her?
" When present, it is the information that MUST be used to select the >>> DetNet state <<< 
at the DetNet forwarding sublayer.

Thanks
Bala'zs

-----Original Message-----
From: detnet <detnet-bounces@ietf.org> On Behalf Of Pascal Thubert (pthubert)
Sent: Tuesday, June 8, 2021 2:23 PM
To: DetNet WG <detnet@ietf.org>
Cc: raw@ietf.org; draft-hinden-6man-hbh-processing@ietf.org
Subject: [Detnet] FW: New Version Notification for draft-pthubert-detnet-ipv6-hbh-01.txt

Dear DetNet

This new draft is an effort to equalize the work at RAW and DetNet in terms of path signaling in the IPv6 dataplane, and provide the same capabilities in the MPLS and the IPv6 for sequencing.
It recognizes and leverages the recent evolution at 6MAN which makes the HBH OH more and more usable in the greater internet.

Comments welcome!

Pascal

-----Original Message-----
From: internet-drafts@ietf.org <internet-drafts@ietf.org> 
Sent: mardi 8 juin 2021 14:16
To: Pascal Thubert (pthubert) <pthubert@cisco.com>
Subject: New Version Notification for draft-pthubert-detnet-ipv6-hbh-01.txt

A new version of I-D, draft-pthubert-detnet-ipv6-hbh-01.txt
has been successfully submitted by Pascal Thubert and posted to the IETF repository.

Name:		draft-pthubert-detnet-ipv6-hbh
Revision:	01
Title:		IPv6 Hop-by-Hop Options for DetNet
Document date:	2021-06-08
Group:		Individual Submission
Pages:		10
URL:            https://www.ietf.org/archive/id/draft-pthubert-detnet-ipv6-hbh-01.txt
Status:         https://datatracker.ietf.org/doc/draft-pthubert-detnet-ipv6-hbh/
Html:           https://www.ietf.org/archive/id/draft-pthubert-detnet-ipv6-hbh-01.html
Htmlized:       https://datatracker.ietf.org/doc/html/draft-pthubert-detnet-ipv6-hbh
Diff:           https://www.ietf.org/rfcdiff?url2=draft-pthubert-detnet-ipv6-hbh-01

Abstract:
   RFC 8938, the Deterministic Networking Data Plane Framework relies on
   the 6-tuple to identify an IPv6 flow.  But the full DetNet operations
   require also the capabilities to signal meta-information such as a
   sequence within that flow, and to transport different types of
   packets along the same path with the same treatment, e.g.,
   Operations, Administration, and Maintenance packets and/or multiple
   flows with fate and resource sharing.  This document introduces new
   Hop-by-Hop header options that can signal that information to the
   intermediate relays.

The IETF Secretariat

_______________________________________________
detnet mailing list
detnet@ietf.org
https://www.ietf.org/mailman/listinfo/detnet