[Teas] Re: AD review for draft-ietf-teas-gmpls-controller-inter-work-13

["Linyi (Yi)" <[e-mail]>]

Dear Jim and Pavan,



Thank you for your review, comments and suggestions, which we have addressed below (with remarks as needed).

We have performed a full review, squashed several additional editorial bugs, and improved the  English where possible. We have also provided some additional terminology clarity for some readers unfamiliar with optical transport terms.



You can find a diff of the document, with our recent updates addressing your comments here: Diff: draft-ietf-teas-gmpls-controller-inter-work-13.txt - draft-ietf-teas-gmpls-controller-inter-work-14.txt<https://author-tools.ietf.org/iddiff?url1=draft-ietf-teas-gmpls-controller-inter-work-13&url2=draft-ietf-teas-gmpls-controller-inter-work-14&difftype=--html>



Below you will find a quick summary of changes specific to your comment and/or suggestion.



1)      Jim’s comments:

118     Generalized Multi-Protocol Label Switching (GMPLS) [RFC3945] extends



Jim> No need to expand on GMPLS as it is a well-known abbreviation as stated here -> https://www.rfc-editor.org/materials/abbrev.expansion.txt.

[Yi] OK



132     nodes. One of the examples is the Abstraction and Control of Traffic



Jim> s/‘One of the examples’/‘One example’

[Yi] OK



152   2. Overview



154     In this section, overviews of GMPLS control plane and centralized

155     controller system are discussed as well as the interactions between



Jim> s/system/systems

[Yi] OK



216           +-------------+      +-------------+       +-------------+

217           |Controller(N)|      |Controller(G)|       |Controller(G)|

218           |    (PNC)    |      |    (PNC)    |       |    (PNC)    |

219           +-------------+      +-------------+       +-------------+



Jim> What do (N) and (G) represent above? I assume GMPLS and non-GMPLS? It looks like you clarify this later in the document so perhaps simply provide a pointer here so that the figure is understandable.

[Yi] Yes, Controller(N) is for non-GMPLS domain, and Controller(G) is for GMPLS domain. Added the explanations under the figure.



222         NETCONF|  |PCEP       NETCONF|  |PCEP       NETCONF|  |PCEP



Jim> Please expand on PCEP and add reference.

[Yi] Added the expansion and reference for PCEP in the second paragraph under the figure, where PCEP is the first time mentioned in the text.



433     technology-specific signaling. The RSVP-TE extensions for OTN, WSON,



Jim> please expand acronyms OTN and WSON

[Yi] OK



467     interface) in the hierachy of the controllers (e.g. MPI and SBI for



Jim> s/hierachy/hierarchy

[Yi] OK



2)      Pavan’s comments (sent on March 13th, 2024):

Section 1, Second Paragraph

s/provision services to corresponding nodes /provision services on corresponding nodes [Yi] OK



Section1, Third Paragraph

s/describes how GMPLS control interworks /describes how GMPLS control plane interworks [Yi] OK



Section 2.1, Second Paragraph

s/for GMPLS control [RFC3945]/ for GMPLS control plane [RFC3945] [Yi] OK



Section 2.2

Please add appropriate references/expansions when NETCONF, YANG, RESTCONF, PCEP and PCC are first introduced.

[Yi] Added expansions to NETCONF, PCEP and PCC (RFC8040 and RFC7950 do not provide the expansions to RESTCONF and YANG), and added reference to NETCONF, YANG, RESTCONF and PCEP



Section 2.2

s/ utilizing the, e.g., [RFC8795] Yang model /utilizing the [RFC8795] Yang model s/ exploit, e.g., [TE-Tunnel] Yang model / exploit the [TE-Tunnel] Yang model [Yi] OK (I think both changes are in Section 2.3)



Section 4.1

Please expand OTN and WSON (at first occurrence) [Yi] OK



Section 7.2, Second Paragraph

s/hierachy/hierarchy

[Yi] OK



Section 7.3.1

Please expand VNTM and NMS (at first occurrence) [Yi] OK




B.R.
Yi LIN

HUAWEI France
Marco Polo A2, 790 Avenue Maurice Donat, 06250 Mougins France
http://www.huawei.com<https://urldefense.com/v3/__http:/www.huawei.com/__;!!D9dNQwwGXtA!Xsp-O9h6SXnygDOPTfzFdS9Kukr7nZ_NNzPlwoW_94XFXCB4iZRMiocCqd0kO4xWTSGP9ctwHB7XGJyZ$>
---------------------------------------------------------------------------------------------
This e-mail and its attachments contain confidential information from HUAWEI, which
is intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender
by phone or email immediately and delete it!

发件人: James Guichard <[e-mail]>
发送时间: 2024年5月31日 21:03
收件人: [e-mail]
抄送: [e-mail]
主题: AD review for draft-ietf-teas-gmpls-controller-inter-work-13

Hi Authors,

Thank you for this document. Please see my review comments for v-13 of the document. I have used line numbers from idnits to help with your review:


118     Generalized Multi-Protocol Label Switching (GMPLS) [RFC3945] extends



Jim> No need to expand on GMPLS as it is a well-known abbreviation as stated here -> https://www.rfc-editor.org/materials/abbrev.expansion.txt.



132     nodes. One of the examples is the Abstraction and Control of Traffic



Jim> s/‘One of the examples’/‘One example’



152   2. Overview



154     In this section, overviews of GMPLS control plane and centralized

155     controller system are discussed as well as the interactions between



Jim> s/system/systems



216           +-------------+      +-------------+       +-------------+

217           |Controller(N)|      |Controller(G)|       |Controller(G)|

218           |    (PNC)    |      |    (PNC)    |       |    (PNC)    |

219           +-------------+      +-------------+       +-------------+



Jim> What do (N) and (G) represent above? I assume GMPLS and non-GMPLS? It looks like you clarify this later in the document so perhaps simply provide a pointer here so that the figure is understandable.



222         NETCONF|  |PCEP       NETCONF|  |PCEP       NETCONF|  |PCEP



Jim> Please expand on PCEP and add reference.



433     technology-specific signaling. The RSVP-TE extensions for OTN, WSON,



Jim> please expand acronyms OTN and WSON



467     interface) in the hierachy of the controllers (e.g. MPI and SBI for



Jim> s/hierachy/hierarchy

Thanks!

Jim