Subject: [CCAMP] comments about draft-ietf-ccamp-wson-yang-20

From: Gert Grammel <[email-masked]>
Date: Mon, 25 Mar 2019 08:57:32 +0000

Few nits:

https://datatracker.ietf.org/doc/draft-ietf-ccamp-wson-yang/?include_text=1 contains the snippet copied further  below:

  1.  FEC type is supposed to be part of the operational-mode definition, while here it is spelled out as a separate parameter, that should be corrected
  2.  The modes are described as "List of all supported vendor-specific mode identifiers". It is my understanding that modes can be vendor-specific or standard, so the description should be updated.
  3.  Is the draft supposed to address also b100G interfaces, including 400G-ZR? The draft references G.698.2 which defines only 100G single-wavelength interfaces. However the current draft also defines also subcarrier, which I couldn’t find in G.698.2. Moreover I would expect that such data would end-up in the operational-mode description.

a.  +--rw max-subcarrier-channel-num?     uint8

Thanks
Gert

  grouping wson-ttp-attributes {
    description
      "WSON tunnel termination point (e.g., tranponder) attributes";

    leaf-list supported-operational-modes {
      type layer0-types:operational-mode;
      description
        "List of all supported vendor-specific
         mode identifiers";
    }

    leaf configured-operational-modes {
      type layer0-types:operational-mode;
      description
        "Vendor-specific mode identifier configured
         on the TTP (TE-tunnel Termination Point)";
    }

    leaf-list supported-fec-types {
      type identityref {
        base layer0-types:fec-type;
      }
       description
         "List of all supported FEC (Forward Error Correction)
          types by this TTP";
    }