Q14 Response to ASON Routing Requirements The draft provides an excellent start on joint work on routing to support ASON Proposed clarification text for the draft is contained in Main comments Should broaden the scope by reference to G.805 Should move backwards compatibility statement to informative appendix. Routing protocol extension for supporting ASON must not interference with SCN messages routing. Definition of control domain and associated reference points should be consistent between the routing and signaling requirement drafts Q14 assumes Carrier’s networks are themselves components of a top-level RA There shouldn’t be direct communication between peer RAs in a level, instead only via a higher level containing RA Text proposed to clarify that the number of hierarchical levels to be supported by a routing protocol is implementation specific |