Q.12/15 thanks the CCAMP working group for the liaison of the Internet-Draft,
we look forward to continuing the dialog on the development of this document.
In response to the questions that you raised: The experts of Q.12/15 reviewed
the current version of the draft to ensure that the ASON description of the
GMPLS terms are accurate. We used the informal definitions of the GMPLS terms
provided in the draft, supplemented by some clarifications provided by Mr.
Adrian Farrel at the meeting, as the basis for our review. We have the
following suggestions to resolve the points that were raised in the liaison:
Item 1: CCAMP proposes the following text: "ITU-T [should be ASON] terms for
resource: ï€ Connection point (cp) in the context of link discovery and
resource management (allocation, binding into cross-connects, etc.); ï€
Link connection or trail termination in the context of routing, path
computation and signaling." We suggest the following revision to the text:
"ASON terms for resource: ï€ In the context of link discovery and resource
management (allocation, binding into cross-connects, etc.) a GMPLS resource is
one end of a link connection, ï€ In the context of routing, path
computation and signaling, a GMPLS resource is a link connection or trail
Note that ASON does use the concept of a link end in the form of a subnetwork
point pool (SNPP). CCAMP proposes the following text: "In ASON, a GMPLS
unidirectional data link end is a collection of connection points from the same
client layer that are supported by a single trail termination (access point)."
We suggest the following addition to clarify the relationship between ASON SNPP
and GMPLS data link end: "A GMPLS unidirectional data link end is a collection
of connection points from the same client layer that are supported by a single
trail termination (access point). This is a constrained form of an SNPP."
The relationship between ASON links and their supporting server trail(s) was
discussed with Mr. Adrian Farrel to clarify the ASON model.
After discussing CCAMPâ€™s concern we suggest the following modified text that
captures the notion that the interface is between a server layer trail and a
client layer subnetwork without constraining the server layer to be a physical
layer. "A GMPLS interface is the set of trail termination and adaptation
functions between one or more server layer trails and a specific client layer
subnetwork (which commonly is a matrix in a network element)."