Hi Robert
Thanks for your YANG doctors review. Please see the response to your comment in line. Once you give us a green signal, we will upload the draft as we have agreed on.
Best regards,
Young
On Thu, Jul 25, 2019 at 9:56 PM Robert Wilton via Datatracker <noreply@xxxxxxxx> wrote:
Reviewer: Robert Wilton
Review result: Ready with Nits
I have reviewed this document as part of the YANG doctors directorate's
ongoing effort to review all IETF documents being processed by the IESG. These
comments were written with the intent of improving the operational aspects of
the IETF drafts. Comments that are not addressed in last call may be included
in AD reviews during the IESG review. Document editors and WG chairs should
treat these comments just like any other last call comments.
Nits:
1) Doc title: Perhaps change to "A YANG Data Model for TE Layer 0 Types", also
changing the short name from "Layer0 Types" to "TE Layer 0 Types".
YL>> I think we should stay as is. The reason for this is that layer 0 types are applicable mainly for TE but not limited to. We can envision the groupings defined in this document can be applicable for configuring physical network components. I would add in the abstract. "The applicability of this document is mainly for TE, but not limited to."
2) Abstract:
"in YANG" => "in the YANG"
YL>> Agree.
Add the comment to the abstract:
The YANG data model in this document conforms to the Network
Management Datastore Architecture defined in RFC 8342.
YL>> Agree.
3) Section 1.1 is probably not required, or at least the document doesn't
appear to use RFC2119 language.
YL>> Agree.
4) Section 1.3. Prefix and Module naming:
The module description states that the types are for TE.
Hence, would a module name of "ietf-te-layer0-types", with a module prefix of
"te-l0-types" be better?
YL>> As mentioned above, we;d like to keep the module name as is. In Introduction, we can change some wording to make sure this document's applicability is larger than TE.
Old:
The derived types and groupings are designed to
be the common types applicable for modeling Traffic Engineering (TE) for Layer
0 optical networks in model(s) defined outside of this document.
New:
The derived types and groupings are designed to
be the common types applicable for modeling Traffic Engineering (TE) features as
well as non-TE features (e.g., physical network configuration aspect) for Layer
0 optical networks in model(s) defined outside of this document.
5) Section 3.1 A lot of the types have "flexi-grid" in the type name by
"flex-grid" in the description. Perhaps it would be appropriate to change
"flex-grid" to "flexi-grid" or "flexible-grid"?
YL>> Will change globally to "flexi-grid".
YANG Module:
(1) The main comment is that you should define typedefs in a couple of places:
(1-i) For the dwdm-n frequency definition (used by leafs dwdn-n in groupings
wson-link-label and wson-path-label, and leaf flexi-n in grouping
flexi-grid-link-label):
The description for this typedef (which can be removed from the description in
the leaves) should probably be:
"The given value 'N' is used to determine the nominal
central frequency.
The nominal central frequency, 'f' is defined by,
f = 193.1 THz + N x 0.00625 THz,
where 193.1 THz is the ITU-T 'anchor frequency' for
transmission over the C band";
(1-ii) For the cwdn-n frequency definition (used by leafs cwdm-n in groupings
wsol-link-label and wson-path-label):
The description for this typedef (which can be removed from the description in
the leaves) should probably be:
"The given value 'N' is used to compute the channel
wavelength as per the formula:
Wavelength (nm) = 1471 + N x 20";
The typedef's reference statement should be "ITU-T G.694.2" (perhaps also with
the date it is published as MM/YYYY)
(1-iii) It might also be worth defining a typedef for the subcarrier-dwdn-n
leaf, even though the type is only used is one place.
YL>> We can define typedef fo the first two cases. For (1-iii), we may keep it as is.
Minor comments:
(2) I note that your sample values in frequency-thz are not in the canonical
value (e.g. the canonical value would be "193.125" rather than "193.12500"). I
think that this is OK, but wanted to point it out.
YL>> This is not too big a deal. We can change to 193.125 (which is typical); also change
fraction-digits to 3 to match with the example.
(3) Your fequency-Ghz is to 5 fractional digits, e.g. allowing "193125..12345"
Ghz. I.e. this is 1000 times more precise than the Thz value. Is this
intentional? If you keep it as it is, then I would consider change the example
value to "193125.0".
YL>> I agree. This may be an overkill. I will change the fraction-digits to "1" and show the
example as you suggested.
(4) "flexi Grid node" => "Flexi-grid node"
YL>>Agree.
(5) "identity random-wavelength-assignment" => Check line length of
description, probably could be expanded.
YL>> I think so. I will change this as well.
(6) "Layer0 grid type." => "Layer 0 grid type"
YL>> Agree.
(7) "Termination type." => "Termination type"
YL>> Agree.
(8) In several places "Termination" at end of description => "termination"
YL>> Agree.
(9) "identity term-phys" => description to "Physical layer termination", indent
all description and reference strings to 2 spaces after the begining of the
word 'description'/'reference' word. Also need to fix in "identity fec-type"
reference statement,
YL>> Agree.
(10) "Section Layer Termination" => "Section layer termination"
YL>> Agree.
(11) Some of the reference statements should be expanded from just the RFC
number to also the RFC name.
YL>> Agree.
(12) The description of subcarrier-dwdn-n leaf-list should probably be
something like:
description
"List of subcarrier channels for the super channel.
The given value 'N' is used to determine the nominal
central frequency.
The nominal central frequency, 'f', is defined by,
f = 193.1 THz + N x 'channel spacing (THz)',
where 193.1 THz is the ITU-T 'anchor frequency' for
transmission over the C band";
reference "ITU-T G.694.1";
YL>> Thanks for making the description clearer. I think we need to modify as follows:
description
"List of subcarrier channels for the super channel.
The given value 'N' for each subcarrier channel
"List of subcarrier channels for the super channel.
The given value 'N' for each subcarrier channel
is used to determine the nominal
central frequency.
The nominal central frequency, 'f', is defined by,
f = 193.1 THz + N x 'channel spacing (THz)',
where 193.1 THz is the ITU-T 'anchor frequency' for
transmission over the C band,
central frequency.
The nominal central frequency, 'f', is defined by,
f = 193.1 THz + N x 'channel spacing (THz)',
where 193.1 THz is the ITU-T 'anchor frequency' for
transmission over the C band,
N is a
positive or negative integer including 0";
reference "ITU-T Recommendation G.694.1: Spectral girds for WDM applications:
DWDM frequency grid";
(13) leaf "priority" description "priority" => "Priority"
YL>> Agree.
(14) grouping flexi-grid-channel description, "where M is an integer greater or
equal to 1" => "where M is a positive integer"
YL>> OK.
(15) "onsidered" => "considered"
YL>> Agree.
(16) Remove extra space in hte URI in the IANA considerations.
YL>> Agree.
Thanks,
Rob
