1 / 11

Ethernet TSPEC and MEF Parameters

Ethernet TSPEC and MEF Parameters. draft-ietf-mef-ethernet-traffic-parameters-01.txt dimitri.papadimitriou@alcatel.be. Clarification Points. Point 1: Port vs Frame mode Point 2: VLAN Label. Port vs Frame mode (1). Switching Type (ST) in Label Request object = interface switching

knut
Download Presentation

Ethernet TSPEC and MEF Parameters

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. Ethernet TSPEC and MEF Parameters draft-ietf-mef-ethernet-traffic-parameters-01.txt dimitri.papadimitriou@alcatel.be

  2. Clarification Points • Point 1: Port vs Frame mode • Point 2: VLAN Label

  3. Port vs Frame mode (1) • Switching Type (ST) in Label Request object = interface switching • Ethernet => L2SC (value 51) LABEL REQUEST object format: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Length | Class-Num ( ) | C-Type ( ) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | LSP Encoding |Switching Type | GPID | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

  4. Port vs Frame mode (2) • Frame mode: individual Ethernet frame switching decision based on Ethernet MAC frame header e.g. VLAN • Port mode: Ethernet frame relayed from input to output port (independently of Ethernet MAC header) - framing only

  5. Port vs Frame mode (3) Ethernet SENDER_TSPEC object format: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Length | Class-Num (12)| C-Type (6) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Switching Granularity | MTU | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | ~ TLVs ~ | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Switching Granularity (16 bits) indicates the type of link that comprises the requested Ethernet LSP. Defined values: Value Switching Granularity ----- --------------------- 1 Ethernet Port 2 Ethernet Frame

  6. Label • Port mode => port label (encoded over 32 bits) = component interface identifier • Frame mode => VLAN label (encoded over 12 bits - right justified)

  7. Label object and values • RFC4606 - VCAT case => multiple label values as part of Resv message • <label> set of one or more LABEL objects • CE-PE signaling (UNI) request for multiple labels => multiple TLV 129 in TSPEC (replaces multiplier field of SONET/SDH T_SPEC)

  8. Constraint set of labels • Per RFC 3473 include <label set> in Path message • <label_set> composed by a list of one or more LABEL_SET objects

  9. Question • Need to document these applicability statements in this I-D ? • My opinion: YES

  10. Update • mCoS LSP = single LSP (control plane) with multiple CoS (data plane) • index field in TLV 129 correspond to at least one of the index value included in the extended ClassType (CT) object [RFC4124], [MCOS] • WHY: base DS-TE nice but increase overhead of CP

  11. Next Step • Revision (soon after meeting) • Then LC • Liaison to OIF and other bodies looking at reusing “GMPLS” for Ethernet LSPs • Comments ?

More Related