[Teas] Re: Éric Vyncke's No Objection on draft-ietf-teas-gmpls-controller-inter-work-15: (with COMMENT)

["Eric Vyncke (evyncke)" <[e-mail]>]

Dear Yi Lin,

Thanks for the revised -16.

It addresses indeed 2 of my non-blocking comments.

About section 5.3, still non-blocking (i.e., feel free to ignore) what about the following text:

OLD:
   These protocols provide a powerful mechanism for notification of topology
   changes to the client.

NEW:

   These protocols provide a powerful mechanism for notification (in addition to provisioning and monitoring) of topology

   changes to the client.

Regards

-éric

From: Linyi (Yi) <[e-mail]>
Date: Friday, 23 August 2024 at 00:56
To: Eric Vyncke (evyncke) <[e-mail]>, The IESG <[e-mail]>
Cc: [e-mail] <[e-mail]>, [e-mail] <[e-mail]>, [e-mail] <[e-mail]>, [e-mail] <[e-mail]>, [e-mail] <[e-mail]>
Subject: Re: Éric Vyncke's No Objection on draft-ietf-teas-gmpls-controller-inter-work-15: (with COMMENT)
Dear Éric Vyncke,

Many thanks for the review and comments.

Please see the new version (-16) of this draft and the diff between -15 and -16 below, and see our replies with [Authors] inline.

https://datatracker.ietf.org/doc/html/draft-ietf-teas-gmpls-controller-inter-work-16
https://author-tools.ietf.org/iddiff?url1=draft-ietf-teas-gmpls-controller-inter-work-15&url2=draft-ietf-teas-gmpls-controller-inter-work-16&difftype=--html

Thank you.

B.R.
Yi LIN

HUAWEI France
Marco Polo A2, 790 Avenue Maurice Donat, 06250 Mougins France
http://www.huawei.com
---------------------------------------------------------------------------------------------
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!

-----邮件原件-----
发件人: Éric Vyncke via Datatracker <[e-mail]>
发送时间: 2024年8月7日 18:18
收件人: The IESG <[e-mail]>
抄送: [e-mail]; [e-mail]; [e-mail]; [e-mail]; [e-mail]; [e-mail]
主题: Éric Vyncke's No Objection on draft-ietf-teas-gmpls-controller-inter-work-15: (with COMMENT)

Éric Vyncke has entered the following ballot position for
draft-ietf-teas-gmpls-controller-inter-work-15: No Objection

When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-teas-gmpls-controller-inter-work/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------


# Éric Vyncke, INT AD, comments for
draft-ietf-teas-gmpls-controller-inter-work-15

Thank you for the work put into this document. The document is rather complex
and not too easy to read if you are not an expert in this field. I am therefore
trusting the responsible AD and the routing directorate for the correctness.

Please find below some non-blocking COMMENT points, and one nit.

Special thanks to Vishnu Pavan Beeram for the shepherd's detailed write-up
including the WG consensus and the justification of the intended status.

I hope that this review helps to improve the document,

Regards,

-éric

# COMMENTS (non-blocking)

## Section 2

It would help the reader if informative references were provided with
abbreviations (if applicable).
[Authors] the references were added to the abbreviations which we think are applicable.

## Section 5.3

`notification of topology changes`, AFAIK restconf/netconf can also be used to
*provision* devices.
[Authors] do you mean using RESTCONF/NETCONF to configure the devices in the network, in addition to topology information collection?
Because Section 5 is about routing options, which is focusing on network topology information collection, we would like to propose to only mention "notification of topology changes" in the text, if you agree.


# NITS (non-blocking / cosmetic)

## IS-IS vs. ISIS

AFAIK, the usual way is to use "IS-IS".
[Authors] OK