Re: [Detnet] WG adoption poll draft-geng-detnet-conf-yang

["Gengxuesong (Geng Xuesong)" <[e-mail]>]

Hi Rodney,

Thank you for reviewing the document and giving comments.
The current DetNet YANG is based on the what has been done in DetNet WG, and the attributes defined there can be found in WG charter/DetNet architecture/ DetNet information model.
At the same time, we keep an eye about what is happening in IEEE, and try to make a careful work division with IEEE when we define the YANG model:
1. The 'ietf-detnet-flow' is for DetNet service establishment in the DetNet domain, corresponding to the configuration of MPLS/IP data plane solution.
2. The 'ietf-detnet-topolgy' is the augmentation of 'ietf-te-topolgy', and all the attributes that have been defined in TE topology can be reused.
Obviously, we cannot use IEEE 802.1 YANG to configure an IP/MPLS network. All these work is the extension of current IETF YANG work. The functions or algorithms you have mentioned, including "PREOF" or "credit-based-shaper", are shared features with both DetNet and TSN, and we are not intended to redefine them, and just to offer a tool about how to use them in an IP/MPLS network;.

I agree that ietf-detnet-topology does not belong to the southbound interface (it was also mentioned in the presentation of IETF 102 ), and we ask for WG comments about whether to put it in a separated draft. I think the current answer is to maintain them in the same one.

It is good to hear your comments, and we would like to corporate with IEEE 802.1 YANG guys to make TSN/DetNet coordinate with each other. More communications are always helpful.

Best Regards

Xuesong

>-----Original Message-----
>From: detnet [mailto:[e-mail]] On Behalf Of Rodney Cummings
>Sent: Friday, September 21, 2018 6:30 AM
>To: Janos Farkas <[e-mail]>; [e-mail]
>Cc: [e-mail]
>Subject: Re: [Detnet] WG adoption poll draft-geng-detnet-conf-yang
>
>Hi folks,
>
>At the moment, I am "no / do not support".
>
>I am confused by what it means for the WG to adopt this draft.
>
>The draft contains YANG for configuration of IEEE 802.1 features in a node
>(bridge, router, etc). This includes 802.1CB ("PREOF"), 802.1Qav (credit-based
>shaper), and so on. There are similar YANG projects in 802.1 for these features.
>
>Therefore, does adoption of this draft mean that IETF DetNet intends to do
>YANG work that overlaps with 802.1 YANG work?
>
>I would hope that the answer is No.
>
>On a different point, I don't think that topology is part of node configuration
>(southbound). Topology is not flow or service related, but it is between the
>Network Operator (controller) and the User... northbound. If I am correct, this
>draft is starting with an incorrect assumption.
>
>Rodney
>
>From: detnet <[e-mail]> On Behalf Of Janos Farkas
>Sent: Tuesday, September 18, 2018 2:02 PM
>To: [e-mail]
>Cc: [e-mail]
>Subject: [Detnet] WG adoption poll draft-geng-detnet-conf-yang
>
>Dear all,
>
>This is start of a two week poll on making draft-geng-detnet-conf-yang-04 a
>working group document. Please send email to the list indicating "yes/support"
>or "no/do not support".  If indicating no, please state your reservations with
>the document.  If yes, please also feel free to provide comments you'd like to
>see addressed once the document is a WG document.
>
>The poll ends Oct 3.
>
>Thanks,
>János and Lou
>
>_______________________________________________
>detnet mailing list
>[e-mail]
>https://www.ietf.org/mailman/listinfo/detnet