Subject: Re: [Detnet] I-D Action: draft-ietf-detnet-yang-02.txt

From: Lou Berger <[email-masked]>
Date: Sun, 30 Jun 2019 11:13:37 -0400

Hi,

I was hoping others would comment on this first, but I guess I'll jump in.

I think our yang modeling should follow the architecture, the flow 
information model and the data plane solution documents.

I think this means that are four basic elements are

(App flow)
Service sub-layer
Forwarding sub-layer
(Sub-network)

The two sublayers are part of detnet and should be fully described in the 
models. The said the data plane solutions allows for different technologies 
to realize each sub-layer and we are currently defining two different 
technologies.  I think this means that the Subway or is need a general 
structure that covers detnet abstract elements, but also allows for 
technology specifics. I suggest ensuring that the structure covers both the 
current IP and mpls data plane definitions, and the elements identified in 
those documents that require configuration.

The same concepts largely apply for the app flow subnetwork portions, i.e., 
there should be a general structure that allows for technology specifics. 
Hereto, I suggested  that the structure covers both the current IP over 
mpls and mpls over UDP definitions, and the elements identified in those 
documents that require configuration.

See below for more specific comments.

----------
On May 27, 2019 2:36:31 AM "Gengxuesong (Geng Xuesong)" 
<[email-masked]> wrote:

> Dear WG,
>
>
>
> After several discussions with other authors and chairs, we decided to 
> update the YANG Model, which aligns with the new serious of Data Plane 
> drafts, as follows:
>
> 1. There are four configuration 
> instances, including "DetNet Proxy Instance", "Service Sub-layer Instance", 
> "Forwarding Sub-layer Instance", "TSN Sub-network Instance". When the 
> device is configured, these instances are used following the order of the 
> layer stack defined in the architecture:
>

I don't really understand how proxy fits in the middle of a detnet.

I'd say the four elements and the overall model match what we have in the 
architecture, and what I have listed above: app flow, service and 
forwarding sublayers, and (technology agnostic) sub-layer.

> 2. There are four elements in every configuration instance: operations, 
> in-segment, out-segment, as discussed in IETF 104.
>
> The overall structure is like:
>
>
> If the WG agrees with the structure, we will work on update the draft and 
> publish 03 version as soon as possible.
>
>

The different node rolls identified in the architecture, need to covered in 
the overall model, but need not be explicitly identified. For example some 
nodes, will be service aware while others only support the forwarding sub 
layer. I'd like to see the update resulting from my comment above before 
making more detail comments though.

Lou
(As contributor)

>
> Any comments or suggests are welcome.
>
>
>
> Best Regards
> Xuesong
>
>
>
>>-----Original Message-----
>
>>From: detnet [mailto:[email-masked]] On Behalf Of
>
>>[email-masked]
>
>>Sent: Tuesday, March 26, 2019 12:47 AM
>
>>To: [email-masked]
>
>>Cc: [email-masked]
>
>>Subject: [Detnet] I-D Action: draft-ietf-detnet-yang-02.txt
>
>>
>
>>
>
>>A New Internet-Draft is available from the on-line Internet-Drafts directories.
>
>>This draft is a work item of the Deterministic Networking WG of the IETF.
>
>>
>
>>        Title           : Deterministic Networking (DetNet) Configuration
>
>>YANG Model
>
>>        Authors         : Xuesong Geng
>
>>                          Mach(Guoyi) Chen
>
>>                          Zhenqiang Li
>
>>                          Reshad Rahman
>
>>       Filename        : draft-ietf-detnet-yang-02.txt
>
>>       Pages           : 46
>
>>       Date            : 2019-03-25
>
>>
>
>>Abstract:
>
>>   This document contains the specification for Deterministic Networking
>
>>   flow configuration YANG Model.  The model allows for provisioning of
>
>>   end-to-end DetNet service along the path without dependency on any
>
>>   signaling protocol.
>
>>
>
>>   The YANG module defined in this document conforms to the Network
>
>>   Management Datastore Architecture (NMDA).
>
>>
>
>>
>
>>
>
>>The IETF datatracker status page for this draft is:
>
>>https://datatracker.ietf.org/doc/draft-ietf-detnet-yang/
>
>>
>
>>There are also htmlized versions available at:
>
>>https://tools.ietf.org/html/draft-ietf-detnet-yang-02
>
>>https://datatracker.ietf.org/doc/html/draft-ietf-detnet-yang-02
>
>>
>
>>A diff from the previous version is available at:
>
>>https://www.ietf.org/rfcdiff?url2=draft-ietf-detnet-yang-02
>
>>
>
>>
>
>>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.
>
>>
>
>>Internet-Drafts are also available by anonymous FTP at:
>
>>ftp://ftp.ietf.org/internet-drafts/
>
>>
>
>>_______________________________________________
>
>>detnet mailing list
>
>>[email-masked]
>
>>https://www.ietf.org/mailman/listinfo/detnet
>
>
> ----------
> _______________________________________________
> detnet mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/detnet
>