Re: [Teas] WG Last Call: draft-ietf-teas-actn-vn-yang-19

["Wubo (lana)" <[e-mail]>]

Hi Dhruv,

Thanks for the reply.
For type 1 and type 2, all components, including VNs, VNAPs, and VN-members, are mapped to relevant nodes in the TE topology. So I think “vn-type” is useful for the CNC to determine the operations of TYPE1 and TYPE2. Otherwise, the TE topology always needs to be queried before the operations. And per the definition of VN, the VN type seems a key attribute of the VN.

Thanks,
Bo

From: Dhruv Dhody <[e-mail]>
Sent: Tuesday, October 24, 2023 11:27 AM
To: Wubo (lana) <[e-mail]>
Cc: Vishnu Pavan Beeram <[e-mail]>; TEAS WG <[e-mail]>; TEAS WG Chairs <[e-mail]>; Qin Wu <[e-mail]>
Subject: Re: [Teas] WG Last Call: draft-ietf-teas-actn-vn-yang-19

Hi Bo,



On Tue, Oct 24, 2023 at 8:18 AM Wubo (lana) <[e-mail]<mailto:[e-mail]>> wrote:
Hi Dhruv,

Thanks for addressing my comments.
I have one more question: Is there an explicit way to know the setting of VN type1 and VN type2? For example, “vn-type”? Or do these two types not need to be distinguished and can be switched in the realization?


Good question! As one of our aims was to keep this model generic (at the same time fully applicable to ACTN), we decided to not include an explicit VN-type and let that be implicit based on the TE topology details set by the CNC. If the CNC provides an underlay path in TE-topology's connectivity matrix, it is Type 2, otherwise it is type 1.

Thanks!
Dhruv

Thanks,
Bo

From: Dhruv Dhody <[e-mail]<mailto:[e-mail]>>
Sent: Monday, October 23, 2023 1:42 PM
To: Wubo (lana) <[e-mail]<mailto:[e-mail]>>
Cc: Vishnu Pavan Beeram <[e-mail]<mailto:[e-mail]>>; TEAS WG <[e-mail]<mailto:[e-mail]>>; TEAS WG Chairs <[e-mail]<mailto:[e-mail]>>; Qin Wu <[e-mail]<mailto:[e-mail]>>
Subject: Re: [Teas] WG Last Call: draft-ietf-teas-actn-vn-yang-19

Hi Bo,

Thanks for your review...

On Thu, Oct 19, 2023 at 9:58 AM Wubo (lana) <lana.wubo=[e-mail]<mailto:[e-mail]>> wrote:
Hi all,

Sorry for the late reply. I support WGLC. I have reviewed the document and have a few minor editorial comments:
1. Figure 2 and 3: The basic components of the VN are AP/VNAP and vn-member. If the mapping between L1-L8 and AP/VNAP can be showed in Figure 2 and Figure 3, it is more clear to me to understand the relationship of VN and abstract node (AN).

Dhruv: Since these examples are focusing on single VN, I don't think there would be any added advantage.


2. YANG model: It is recommended that the “abstract-node“ under ”vn-ap” to add some description on what scenarios is needed, which seems redundant with ‘ltp’.

Dhruv: A reference to the abstract topology makes the correlation easier and it is not mandatory.


3. JSON Example: The text description of VN3 (Type 1) does not correspond to the JSON example. It seems to me:
OLD:
VN Member: 104 (L1 to L4)/107 (L1 to L7) {multi-dest}
VN Member: 204 (L2 to L4)/304 (L3 to L4) {multi-src}
NEW:
VN Member: 103 (L1 to L3)/107 (L1 to L7) {multi-dest}
VN Member: 108 (L1 to L8)/308 (L3 to L8) {multi-src}


Dhruv: I updated the text and JSON as well to reflect the example correctly. Thanks for spotting this!

Regards,
Dhruv


Thanks，
Bo

发件人: Teas <[e-mail]<mailto:[e-mail]>> 代表 Vishnu Pavan Beeram
发送时间: 2023年9月12日 20:19
收件人: TEAS WG <[e-mail]<mailto:[e-mail]>>
抄送: TEAS WG Chairs <[e-mail]<mailto:[e-mail]>>
主题: [Teas] WG Last Call: draft-ietf-teas-actn-vn-yang-19

All,

This starts a two-week working group last call on
https://datatracker.ietf.org/doc/draft-ietf-teas-actn-vn-yang/

The working group last call ends on September 26th, 2023.
Please send your comments to the working group mailing list.

Positive comments, e.g., "I've reviewed this document
and believe it is ready for publication", are welcome!
This is useful and important, even from authors.

Note: IPR has been disclosed on this document

Thank you,
Pavan, Lou and Oscar
_______________________________________________
Teas mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/teas