Skip to main content

Early Review of draft-ietf-ccamp-rfc9093-bis-13
review-ietf-ccamp-rfc9093-bis-13-yangdoctors-early-clarke-2025-04-24-00

Request Review of draft-ietf-ccamp-rfc9093-bis-13
Requested revision 13 (document currently at 15)
Type Early Review
Team YANG Doctors (yangdoctors)
Deadline 2025-05-14
Requested 2025-04-23
Requested by Luis M. Contreras
Authors Sergio Belotti , Italo Busi , Dieter Beller , Esther Le Rouzic , Aihua Guo
I-D last updated 2025-07-10 (Latest revision 2025-06-17)
Completed reviews Yangdoctors IETF Last Call review of -04 by Joe Clarke (diff)
Rtgdir IETF Last Call review of -11 by Gyan Mishra (diff)
Yangdoctors Early review of -13 by Joe Clarke (diff)
Genart IETF Last Call review of -15 by Thomas Fossati
Opsdir IETF Last Call review of -15 by Ran Chen
Comments
New review for version -13 is requested since the first one was performed on top of version -04
Assignment Reviewer Joe Clarke
State Completed
Request Early review on draft-ietf-ccamp-rfc9093-bis by YANG Doctors Assigned
Posted at https://mailarchive.ietf.org/arch/msg/yang-doctors/ic4LpfpVXFobHKYhHva60SBjyPo
Reviewed revision 13 (document currently at 15)
Result Ready w/issues
Completed 2025-04-24
review-ietf-ccamp-rfc9093-bis-13-yangdoctors-early-clarke-2025-04-24-00
Hello again, authors!  I've been asked to take another look at this module on
behalf of YANG Doctors.  We discussed some of the previous issues in email, and
I appreciate the changes you have made.  Most of what I found a probably best
described as nits, but I marked this as "with issues" again for the grouping
point I raised last time.

While I acknowledge the intent of these groupings is to also be used with other
structure (e.g., a "grid-type" leaf), I would like to see some explicit text in
the grouping descriptions to clarify that.  While these types/groupings may
only be used in ccamp/teas work, I find it odd that one can't really make use
of them without additional augmentations or structure.

Also, I noticed you mix types with the l0-types: prefix and those without. 
Example:

case single {
            leaf dwdm-n {
              type l0-types:dwdm-n;
              description
                "The given value 'N' is used to determine the
                 nominal central frequency.";
            }
          }

And:

leaf standard-mode {
      type standard-mode;
      config false;
      description
        "G.698.2 standard mode";
    }

Why the discrepancy?

I also notice some differences in choice naming in wdm-label-step.  You've used
grid-type everywhere else, but here you use l0-grid-type.  Probably should
leave out the "l0-".

Similarly, you have some groupings (like l0-tunnel-attributes) named with
"l0-".  Is that required given this will be used with the l0-types: prefix?