Page 566 - Handbook of Modern Telecommunications
P. 566

Network Organization and Governance                                        4-97

                            TABl E 4.5.4  Service-Level Agreements
                             SLA ID for Clients  Client 1 SLA ID = 01  Client 2 SLA ID = 01
                                                 SID1      SID1
                                                 SID2
                                                 SID3
                                                           Client 2 Sl A ID = 02


                                                           SID2


                                                           Client 2 Sl A ID = 03


                                                           SID3



              •   Provider A router and provider B router must exchange routing information with each other. The
                 alternatives are:
                 •   Policy Based Routing (bad scalability due to the fact of the need of many manual entries,
                    very CPU intensive, acceptable performance can only be guaranteed by high-performance
                    hardware)
                 •   Static routing
                 •   RIP (technically making sense)
                 •   OSPF is meaningful, when IP VPNs and MPLS are well supported
                 •   EBGP (technically meaningful)
              •   Measurement and testing points for QoS control are located on the router ports that are toward to
                 the peering point; this makes it possible for routers to measure themselves.
              •   Due to the fact that the peering point represents the ingress point onto the “other” network, the
                 ingoing packet will be repeatedly identified. This includes the following:
                 •   Traffic specification, e.g., policy selection
                 •   Class of Service decision, e.g., priority queuing
                 •   Call Admission Control
              •   Inserting firewalls into this path must be excluded; over firewalls, no quality guarantees may be
                 given.

             4.5.3.3.7  Establishing and Unifying Management Concepts
            In case of multiple service providers, it is mandatory to administer and handle managed objects on the
            basis of unified guidelines. The following functional areas should be addressed by enterprises, repre-
            sented by their overseers, and by all service providers, and their subcontractors.
              The structure consists of a basis management platform and application areas.
              The basis platform provides functions that are required by all management applications. It helps to
            coordinate all management tasks. The following functional grouping is recommended:

              •   Infrastructure (hardware, software, directory services, time services, and asset management)
              •   Basis services (internal communication, graphical user interface, Web server functions, data-
                 base services)
              •   Support services for operations (installation, backup, workforce management, order processing,
                 recovery, housekeeping, software distribution)
   561   562   563   564   565   566   567   568   569   570   571