Your Federal Quarterly Tax Payments are due April 15th Get Help Now >>

PWE3 Applications OAM Scenarios by dsp14791

VIEWS: 12 PAGES: 8

									PWE3 Applications & OAM
      Scenarios
         S. Delord, P. Niger France Telecom
                    D. Brungard ATT
     Y. Ikejiri, Y. Wada NTT Communications
                  A. Vedrenne Equant
                      L. Zhu Sprint
             K. Kumaki KDDI Corporation
                  Service Provider Context
      Customer                   Service Provider                 Service Provider                  Customer
      location                        POP                              POP                          location

                                                    Transit PSN
                        Access                                                       Access

Customer                                                                                                 Customer
                 CE1
equipment                           PE1                               PE2                     CE2        equipment




Service Providers are looking at delivering End to End services (circuit,
packet-based)

                  Not only does the Service Provider use the Transit PSN but it also needs to rely
                  on two Access/Metro networks to successfully deliver its services


PWs are defined between PE1 and PE2 and ACs are defined over the access
network, PWE3 documents focus on the PW part

This draft takes into consideration the specific problems encountered
by SPs for the deployment and monitoring of E2E services
        Issues that need to be considered in the definition of an E2E
                            Service Architecture
These 2 interfaces can
    be similar or not
  (Eth/Eth, Eth/ATM,                   These 2 Access/Metro
     FR/ATM, etc.)                       Networks may use
                                        different technologies
                                       (MPLS, ATM, Eth, FR)




      Customer                    Service Provider                    Service Provider                  Customer
      location                         POP                                 POP                          location

                                                       Transit PSN
                         Access                                                          Access

Customer                                                                                                     Customer
                 CE1
equipment                            PE1                                    PE2                   CE2        equipment




                                                                                                  CE2 (or CE1) can be
                                                                                                       managed
                                                                                                    by the SP or not
                                                     These networks can
                                                     belong to the same
                                                      SP or different SPs
          What does it bring? (1/2)
This draft introduces some considerations and further requirements concerning
deployment and monitoring of E2E services based on PWs.

There are 3 major items covered:

1/ Background on how SPs handle/divide their networks & for which type of
services

2/ E2E Service Architecture:

    – Consideration of E2E service architecture from CE to CE

    – Details service implementation in the access network and its relation with the backbone
    network at the PE level (Interworking/Transparency)
         What does it bring? (2/2)
3/ Specific focus on Service Supervision:

    – Generic & Specific OAM requirements (References draft- Willis & L2VPN OAM Frwk)
         •Fault Detection
         •Fault Localisation

    – Based on well known definitions (OAM Domains, ME, MEP/MIP) used by IEEE, ITU-T and
    IETF (L2VPN-OAM-Fwk)

    – Defines 3 Generic Models for E2E Service Supervision and applies MEP and MIP points
    to these models

         •Option 1: Using a specific End to End OAM Mechanism
         •Option 2: Using Interworking between OAM Segments
         •Option 3: Using a Client/Server model



These models are "technology agnostic":
    – Applicable to the access network => ATM, FR, Eth, MPLS
    – Applicable to the service (homogenous & heterogenous) => ATM, FR, Eth, TDM
     Current work on OAM in L2VPN & PWE3 WGs
                                                                                                             enumerate the OAM defect
This Draft                         OAM Message                                OAM Procedures
                                                                               For VPWS Iwk
                                                                                                             state mapping from PWE3
                                                                                                             services over PSN to their
                                     Mapping                                                                 native attached services


       Customer                          Service Provider                        Service Provider                         Customer
       location                               POP                                     POP                                 location

                                                                Transit PSN
                             Access                                                                 Access

 Customer                                                                                                                      Customer
                  CE1
 equipment                                     PE1                                   PE2                            CE2        equipment

                                                                                     supports connection verification
                                                               VCCV                  applications for PWs (ICMP, LSP-Ping, BFD)


                        Attachment Circuit                      Pseudo-Wire                    Attachment Circuit

                                                             End to End Homogenous services


                                                            End to End Heterogenous services




             L2VPN OAM                       Definition of MEP/MIP points
                                             Requirements for OAM
                Fwk
  Where does this work fit OAM wise?
This draft tries to provide clarification & applicability guidelines for the ongoing
OAM work

                                              VCCV
                                  References the use of VCCV for
                                     the 3 different scenarios                                    OAM Message
                                                                                                    Mapping
 •Requirements for       Brings
                                                                    Brings in MIPs and MEPs for different
 Pt2Pt Supervision                          This draft              OAM Solutions described in


 •3 different OAM
 scenarios                        Uses MEP and MIP definition for                               OAM Procedures
                                   Different scenarios for Pt2Pt                                 For VPWS Iwk
                                              Services



                                        L2VPN OAM
                                           Fwk
 This draft tries to link together all the documents dealing with OAM in both L2VPN
 & PWE3 WGs.
          Conclusion & Next Steps
This draft presents a common view among SPs by introducing generic OAM
models that complement current work on OAM in both PWE3 & L2VPN WGs.
The L2VPN and PWE3 OAM documents should support these requirements and
models.

Next Steps:

    – L2VPN WG has already acknowledged this draft and will include VPWS related
    requirements (L2VPN OAM Requirements & Framework)
    – Specific requirements on PWE3 OAM work will be identified with PWE3 participants
    – Untill requirements are completely identified in L2VPN and PWE3 we would like to
    maintain this draft as a standalone draft
    – Include MH-PWs


We would like the WG members to have a close look of the document and to give
us feedback so that it can become a WG document later.

								
To top