1 / 28

Metro Ethernet UNI Standards Update by Gary Southwell, VP of Product Marketing at Internet Photonics

This comprehensive standards update by Gary Southwell, the VP of Product Marketing at Internet Photonics, covers the latest information on Metro Ethernet UNI. The purpose, requirements, and architectural fit of UNI are discussed, along with enabled services status and future steps. Ethernet services model, customer edge, and service attributes are explained, focusing on how UNI serves as the network subscriber edge demarcation point for a MEN. Topics include UNI-C and UNI-N subsets, UNI reference model, UNI data plane, control plane, and management plane. The text explores UNI data plane elements like Ethernet frame flow, tagging, traffic management, UNI control plane functions such as service discovery and dynamic connection setup, and UNI management plane features like QoS management and protection/restoration capabilities. The roles of Ethernet Services Control Function, Ethernet Virtual Connection, and EVCs & Closed User Groups are detailed, highlighting the importance of EVC associations and service multiplexing. The document also touches on UNI service models, traffic/performance control, and EVC control examples.

maryramirez
Download Presentation

Metro Ethernet UNI Standards Update by Gary Southwell, VP of Product Marketing at Internet Photonics

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Metro Ethernet UNI Standards Update Gary Southwell VP of Product Marketing Internet Photonics MEF Marketing Collateral co-chair gsouthwell@internetphotonics.com

  2. Agenda UNI – Purpose UNI – Overview of Requirements UNI – Architectural Fit UNI – Enabled services Status & next steps/activities

  3. ServicesMetro Ethernet Forum Network ImplementationIEEE 802.1 and IETF PPVPN OA&MMetro Ethernet Forum Ethernet Services Standardization UNI

  4. Metro Ethernet UNI • Purpose • Provides a network subscriber edge demarcation point for a MEN • Requirements Define demarcation for service • connectivity, • signaling, • Provisioning • Fault detection/resolution • Monitoring and management

  5. Ethernet Services Model,Phase 1 CustomerEdge (CE) User NetworkInterface(UNI) User NetworkInterface(UNI) CustomerEdge (CE) MetroEthernetNetwork ServiceAttributes A service is what the CE sees (UNI-to-UNI). The technology used inside the MEN is not visible.

  6. User Network Interface (UNI) The demarcation point between Service Provider and Subscriber Responsibilities • Dedicated to a single Subscriber • Standard Ethernet (IEEE 802.3 – 2002) • More than 100 million devices available as CE • Examples: • RJ 45 Socket on Service Provider owned Ethernet switch • RJ45 plug on Service Provider owned cable

  7. Service Definitions • Ethernet Line Service (E-Line) • Point-to-Point EVC • Any valid set of other service attributes • Ethernet LAN Service (E-LAN) • Multipoint-to-Multipoint EVC • Any valid set of other service attributes • Examples for typical scenarios, e.g., LAN Extension, Internet Access, Headquarters to Branch Offices

  8. Point-to-Point Ethernet Virtual Circuits Servers UNI IP Phone IP PBX Metro Ethernet Network CE Data CE 1 or more UNIs Video UNI CE E-Line Service

  9. Multipoint-to-Multipoint Ethernet Virtual Circuit Servers IP Phone UNI UNI Data IP PBX CE Metro Ethernet Network CE UNI CE CE UNI E-LAN Service

  10. UNI Reference Point • UNI divided into two subsets • UNI-C describes the end customer UNI • UNI-N describes the end customer UNI

  11. UNI Reference Model • UNI data plane • defines the means of transporting information across the UNI reference point • UNI control plane • defines the means for the customer and the MEN provider to make use of the UNI data plane • UNI management plane • controls the operation of the UNI data and control plane

  12. UNI Data Plane • Ethernet frame flow • IEEE 802.3 frames (only) • Tagging • Allows customer equipment (CE) to send 802.1q tagged frames across the UNI for segmentation purposes • Traffic Mgmt • Binds the subscriber transmissions to traffic policies as set by an SLA

  13. UNI Control Plane • a static service discovery function that allows no or auto-configuration of the CE (PVC mode) • a dynamic connection setup function that allows dynamic establishment of Ethernet services (SVC mode).

  14. UNI Management Plane • QOS Mgmt • Allows provisioning of service attributes thought traffic identifiers • Protection & restoration • Allows links from the (CE) into the MEN to be protected by various means • OAM • Connectivity verification, performance monitoring and SLA stats gathering

  15. Ethernet Services Control Function • A UNI-N - Demarc Component (ESCF) • ESCF • SP’s network equipment that provides the functional element required to meter, police and shape the flow to and from the SP’s Demarc • 1st point where policy is enforced in the MEN

  16. Ethernet Virtual Connection(EVC) • Association of two or more UNIs • Frames can only be exchanged among the associated UNIs • A frame sent into the SP network via a particular UNI MUST NOT be delivered out of the SP network via that UNI

  17. EVCS & Closed User Groups • EVCS can form closed user groups (CUGS) • Marked by VLANs or other means of identification • Frames can only be exchanged among the associated UNIs • Note UNIs can support multiple CUGs

  18. Point-to-Point EVC Exactly two UNIs are associated.

  19. Multipoint-to-Multipoint EVC • Two* or more UNIs are associated • A flooded, broadcast or multicast ingress frame is typically replicated and delivered to all of the other UNIs * A MP2MP EVC with two UNIs is different than a P2P EVC since additional UNIs can be added at any time.

  20. Service Multiplexing B ServiceMultiplexing A C EVC1 EVC2 EVC3 D • Multiple EVCs at a UNI • Efficient use of CE port • Multiple revenue streams per SP UNI

  21. UNI Service Model

  22. UNI Traffic and Performance Control examples • Ingress policing based on a two rate, three color Token Bucket model • Similar to the CIR, Bc, Be of Frame Relay • Allows Subscriber to buy bandwidth with high granularity • Performance parameters, e.g., Frame Delay, Frame Loss, Availability • Definitions for the basis of a Service Level Specification in a Service Level Agreement

  23. UNI EVC Control Example • Customer Equipment configuration control

  24. UNI Modes PVC • Start with Static UNI-C config…100% of installed base compatible • No chgs to Customer device config. • E.g. assigned VLANs) • Introduce auto provisioning • DCE Access to CE via LMI to learn what it is connected to and configures CE automatically • E.g. configured VLANs

  25. UNI Modes SVC (Full Definition still pending) • UNI-C requests via signaling what EVCs it desires connectivity with • Negotiates the service parameters if applicable • Provides for backward comaptibility

  26. Ethernet OA&M CE CE OA&M OA&M OA&M • Availability • Status Monitoring • Scalability • Extensibility • Security • Tunnel and Transport Independence • Layer 3 Independence

  27. Status • Ethernet UNI 1.0 in draft • UNI 1 Interoperability Agreement work in process • UNI 2 - work in process

  28. Thank You

More Related