Skip to main content

Last Call Review of draft-ietf-ccamp-rfc9093-bis-04
review-ietf-ccamp-rfc9093-bis-04-yangdoctors-lc-clarke-2023-04-04-00

Request Review of draft-ietf-ccamp-rfc9093-bis
Requested revision No specific revision (document currently at 11)
Type Last Call Review
Team YANG Doctors (yangdoctors)
Deadline 2023-04-21
Requested 2023-03-30
Requested by Luis M. Contreras
Authors Sergio Belotti , Italo Busi , Dieter Beller , Esther Le Rouzic , Aihua Guo
I-D last updated 2023-04-04
Completed reviews Yangdoctors Last Call review of -04 by Joe Clarke (diff)
Rtgdir Last Call review of -11 by Gyan Mishra
Comments
Clustered with draft-ietf-ccamp-optical-impairment-topology-yang
Assignment Reviewer Joe Clarke
State Completed
Request Last Call review on draft-ietf-ccamp-rfc9093-bis by YANG Doctors Assigned
Posted at https://mailarchive.ietf.org/arch/msg/yang-doctors/eJxSzC2xQgxHZ497pydF4V5Aidk
Reviewed revision 04 (document currently at 11)
Result Ready w/issues
Completed 2023-04-04
review-ietf-ccamp-rfc9093-bis-04-yangdoctors-lc-clarke-2023-04-04-00
I have been asked to review this document on behalf of YANG Doctors.  While I
do not have domain experience in layer 0 optical, I found the document and YANG
module fairly easy to get through.  Since this document is a bis for RFC9093, I
did a pyang check to make sure that there are no backwards-incompatible changes
between the 9093 version and this one.  I did not find any.  The new module
adds new types, identities, and nodes.

In terms of issues, the leafref and must in the transceiver-mode are relative
back to the transceiver-capabilities grouping, which uses the transceiver-mode
grouping.  But what if transceiver-mode is used outside of this context?  Those
references may break.

In terms of nits, I found an inconsistent use of first-letter capitalization
and period termination in descriptions.  I also noted that both the document
and the module lack an overall summary of changes between this version and the
9093 version (and I'm just setting the interrupt bit to make sure the authors
address that).  There is also an inconsistent use of quotes around various
units.

I notice that there are some config true nodes that are a union with "empty" as
being one of the options.  Some of the nodes explain when to use empty, but
others do not.  I think it would be good to be consistent with the "empty"
explanation.