ccamp-2----Page:9
1 2 3 4 5 6 7 8 9 10 11
|
Q14 Comments on CCAMP ASON Signal. Reqt. (cont.) Main comments (cont.) Does "agnostic to any UNI” mean that the solution should be capable of supporting both ITU-T-based UNI (G.7713.2) and other UNIs such as GMPLS Overlay? This is not an ASON-derived requirement. (Draft – Sec. 4) "interworking aspects…are strictly the responsibility of the non-GMPLS control domain" is not an ASON-derived requirement. (Draft – Sec. 4) The draft does not discuss support of the E-NNI, although this should be considered an ASON-derived requirement, as well as support of the UNI. (Draft – Sec. 4) The draft provides insufficient description of G.8080 UNI Transport Resource Address support (esp. the potential for this to be a non-Ipv4 or Ipv6 address) Separation of control plane and data plane should be clearer in the document, especially when referring to identifiers. G.8080 defines the ASON control plane as applying to a single layer. Some examples in the draft involve multiple layers. While not precluded by implementations, a suggested replacement example is contained in the marked up copy that is single layer. |