50 likes | 206 Views
MEF Ethernet Traffic Parameters draft-dimitri-mef-ethernet-traffic-parameters-00.txt. IETF65 - Dallas - Mar’06 <dpapadimitriou@psg.com>. Why ?. Demand from OIF Provide traffic parameters for Ethernet service provisioning across domain boundaries
E N D
MEF EthernetTraffic Parametersdraft-dimitri-mef-ethernet-traffic-parameters-00.txt IETF65 - Dallas - Mar’06 <dpapadimitriou@psg.com>
Why ? • Demand from OIF • Provide traffic parameters for Ethernet service provisioning across domain boundaries • Presented in CCAMP but status to be revisited depending on GELS evolution Ethernet LSP l2sc l2sc
Overview • Per [RFC3471], inclusion of technology specific parameters in SENDER_ TSPEC and FLOWSPEC specific objects • Ethernet traffic parameters [MEF.10] used when in Label Request object • LSP Switching Type: L2SC • LSP encoding type: Ethernet • SENDER_TSPEC/FLOWSPEC object • Ethernet link type (switching granularity) • MTU value • Bandwidth Profile: set of traffic parameters • Committed Rate: described in terms of the CIR (Committed Information Rate) and CBS (Committed Burst Size) • Excess Rate: described in terms of the EIR (Excess Information Rate) and EBS (Excess Burst Size) • Color mode (CM): "color-aware" or "color-blind" property is employed by the bandwidth profile • Coupling flag (CF): choice between two modes of operations of the rate enforcement algorithm
Sender_Tspec Format Ethernet SENDER_TSPEC object (Class-Num = 12, Class-Type = TBA) 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 (TBA) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Switching Granularity | MTU | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | ~ TLVs ~ | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Specific TLV defined for Bandwidth Profile: <profile>: 8-bit vector of flags <CIR>, <CBS>, <EIR>, <EBS> each over 32 bits, unit of bytes and encoded as IEEE single-precision floating-point number [RFC1832]
Next Steps • Need for signaling multiple CoS per EVC ? • Requires combination with DS-TE • Status of document will depend on GELS evolution • As of today “informational” status