Framework for GMPLS and PCE Control of G.709 Optical Transport Networks
draft-ietf-ccamp-gmpls-g709-framework-15

Thank you for writing this document, and it is generally ready to move forward. However, I was concerned with one minor detail which seems that there is some unclarity with a term.

First, the document says:

   LO ODU: Lower Order ODU. The LO ODUj (j can be 0, 1, 2, 2e, 3, 4,
   flex.) represents the container transporting a client of the OTN that
   is either directly mapped into an OTUk (k = j) or multiplexed into a
   server HO ODUk (k > j) container.

   HO ODU: Higher Order ODU. The HO ODUk (k can be 1, 2, 2e, 3, 4.)
   represents the entity transporting a multiplex of LO ODUj tributary
   signals in its OPUk area.

and then later, it says:

   With the evolution and
   deployment of OTN technology many new features have been specified in
   ITU-T recommendations, including for example, new ODU0, ODU2e, ODU4
   and ODUflex containers as described in [G709-2012].

But it is unclear if this is referring to LO or HO ODUs or both, or something else. Could this be clarified, or did I missunderstand something?

In 4.1. Connection management of the ODU

   In this case, an operator may choose to allow the underlined OCh

Could "underlined" be a typo for "underlying"? I didn't see anything in Figure 4 that looked like underlying ...

   layer to be visible to the ODU routing/path computation process in
   which case the topology would be as shown in Figure 4. In Figure 3
   below, instead, a cloud representing OCh capable switching nodes is
   represented. In Figure 3, the operator choice is to hide the real OCh
   layer network topology.


           Link #5            +---------+            Link #4
     +------------------------|         |-----------------------+
     |                   +----| ODXC    |----+                  |
     |                 +-++   +---------+   ++-+                |
     |         Node f  |  |     Node E      |  |  Node g        |
     |                 +-++                 ++-+                |
     |                   |       +--+        |                  |
   +-+-----+        +----+----+--|  |--+-----+---+        +-----+-+
   |       |Link #1 |         |  +--+  |         |Link #3 |       |
   |       +--------+         | Node h |         +--------+       |
   | ODXC  |        | ODXC    +--------+ ODXC    |        | ODXC  |
   +-------+        +---------+ Link #2+---------+        +-------+
     Node A            Node B            Node C             Node D


     Figure 4 - OCh Visible Topology for LO ODUj connection management

Later in the same section, the word "underlying" is used, so I'm guessing "underlined" was a typo.

   In the examples (i.e., Figure 3 and Figure 4), we have considered the
   case in which LO ODUj connections are supported by OCh connection,
   and the case in which the supporting underlying connection can be
   also made by a combination of HO ODU/OCh connections.

Is Malcolm's affiliation in the Contributors section correct? I was remembering him being at ZTE, although people do move.