Abstract: Apparatus and method are provided for distributing service domain reachability information across domain boundaries, thereby allowing domain management systems to determine routing for cross-domain services even when the domains have different technologies or administrators. A Service Domain Manager within each domain advertises to neighbouring domains which services it supports. A domain which receives such advertisements forwards the advertisement on to other domains. Each SDM builds a routing information table which specifies the service, the domain, the next hop, and optionally user defined metrics. The routing information table does not include end-point addresses, in order to keep the size of the table manageable. In this way, the NMS of each domain obtains an end-to-end view of service routes.

Abstract: Apparatus and method are provided for enabling establishment of cross-domain services, including exchange of reachability information between domains, routing of services across domains, and differential labeling. The network element control and management planes are supplemented by additional components that enable the control and management planes of each domain to inter-communicate in a peer-to-peer manner. Adjacencies are established between domains, and service reachability information is exchanged between domains. Network Service Applications within the management planes can then establish services across the domains by inter-communicating.

Abstract: Apparatus, methods, and related data structures for validating a routing configuration in a communication system are disclosed. Routing information in a communication system is passively collected, illustratively from routing protocol advertisement messages. A routing configuration of the communication system is validated based on the collected routing information. Validation may involve comparing information associated with electronic addresses in an address space of the communication system with the collected routing information, and also or instead comparing an intended routing configuration with an explicit routing configuration, for example. A data structure may include information indicating an electronic address and information indicating a result of validating a routing configuration associated with the electronic address.