Metro Ethernet Forum (MEF)

Download Report

Transcript Metro Ethernet Forum (MEF)

Metro Ethernet UNI
Standards Update
Gary Southwell
VP of Product Marketing
Internet Photonics
MEF Marketing Collateral co-chair
[email protected]
030602.1
Agenda
UNI – Purpose
UNI – Overview of Requirements
UNI – Architectural Fit
UNI – Enabled services
Status & next steps/activities
030602.2
Ethernet Services
Standardization
UNI
Services
Metro Ethernet Forum
Network Implementation
IEEE 802.1 and IETF PPVPN
OA&M
Metro Ethernet Forum
030602.3
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
030602.4
Ethernet Services Model,
Phase 1
Customer User Network
Edge
Interface
(CE)
(UNI)
User Network Customer
Interface
Edge
(UNI)
(CE)
Metro
Ethernet
Network
Service
Attributes
A service is what the CE sees (UNI-to-UNI).
The technology used inside the MEN is not visible.
030602.5
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
030602.6
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
030602.7
E-Line Service
Point-to-Point
Ethernet Virtual Circuits
Servers
UNI
IP Phone
IP PBX
Data
Metro
Ethernet
Network
CE
CE
1 or more
UNIs
Video
UNI
CE
030602.8
E-LAN Service
Multipoint-to-Multipoint Ethernet
Virtual Circuit
Servers
IP Phone
UNI
UNI
Data
IP PBX
CE
CE
Metro
Ethernet
Network
CE
UNI
UNI
CE
030602.9
UNI Reference Point
• UNI divided into
two subsets
– UNI-C describes the
end customer UNI
– UNI-N describes the
end customer UNI
UNI Reference Point
Customer Subscriber
Network
Edge
Ethernet
PHY
UNI-C
Provider
Edge
MEN
UNI-N
Demark
030602.10
UNI Reference Model
UNI Control Plane
UNI Data Plane
• Ethernet frameflow
• Tagging
802.1Q tagging
• Traffic Management
• Static service discovery
• Dynamic connection setup
UNI Management Plane
• QoS mgmt
• OAM
• Protection & Restoration
• Provisioning
• 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
030602.11
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
030602.12
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).
030602.13
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
030602.14
Ethernet Services Control Function
UNI-C
Management
Managementplane
plane
tenrehtE
kniL sseccA
Control
Controlplane
plane
Data
Dataplane
plane
UNI-N
Management
Managementplane
plane
Control
Controlplane
plane
Data
Dataplane
plane
FCSE
CE
tenrehtE
lautriV
noitcennoC
• 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
030602.15
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
030602.16
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
030602.17
Point-to-Point EVC
Exactly two UNIs are associated.
030602.18
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.
030602.19
Service Multiplexing
B
Service
Multiplexing
A
C
EVC1
EVC2
EVC3
• Multiple EVCs at a UNI
D
• Efficient use of CE port
• Multiple revenue streams per SP UNI
030602.20
UNI Service Model
Public Network
And Services
NNI
MEN
Provider Network
Access Link
Layer 3
Services
ESCF
CE
UNI (Control)
Layer 2
Services
Voice
Services
UNI (Data)
CE
Bi-directional
UNI EVC
Bi-directional
Ethernet
Virtual
Connection
CE
Video
Services
ESCF
030602.21
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
030602.22
UNI EVC Control Example
Control Message:
ESCF to CUET - New Service Connection
Service Attributes:
Connection ID=123
Service Type=VPLS
Duplex Mode=Full
QoS Profile=EF
BW=100Mbps
Etc..
UNI Control
CUET
ESCF
Or EMF
MEN
Provider
Network
CUET - ESCF
UNI Virtual Connection “ 123”
• Customer Equipment configuration control
030602.23
UNI Modes
PVC
1. Start with Static UNI-C config…100% of
installed base compatible
•
•
No chgs to Customer device config.
E.g. assigned VLANs)
2. Introduce auto provisioning
•
•
DCE Access to CE via LMI to learn what it is
connected to and configures CE
automatically
E.g. configured VLANs
030602.24
UNI Modes
SVC
(Full Definition still pending)
1. UNI-C requests via signaling what
EVCs it desires connectivity with
2. Negotiates the service parameters if
applicable
3. Provides for backward comaptibility
030602.25
Ethernet OA&M
CE
CE
OA&M
OA&M
OA&M
•
•
•
•
Availability
Status Monitoring
Scalability
Extensibility
• Security
• Tunnel and
Transport Independence
• Layer 3 Independence
030602.26
Status
• Ethernet UNI 1.0 in draft
• UNI 1 Interoperability Agreement
work in process
• UNI 2 - work in process
030602.27
Thank You
030602.28