CIR, CBS, EIR, and EBS are encoded as 32-bit IEEE single-precision floating-point numbers (per RFC4506/XDR) to accommodate the wide range of Ethernet bandwidth values (from low-rate services to high-speed ports) within a fixed-size field.

mpls, routing

The Ethernet SENDER_TSPEC/FLOWSPEC objects may also be used for signaling Ethernet LSPs beyond MEF EPL/EVPL services; when used this way, the Generalized Label Request Switching Type must be L2SC and LSP Encoding Type must be Ethernet.

mpls, routing

A TLV value field whose length is not a multiple of four MUST be zero-padded with trailing zeros so that the TLV is four-octet aligned.

mpls, routing

An LSR receiving a Path message with the EXTENDED_CLASSTYPE object that detects a mismatch in index values MUST send a PathErr with error code 'Extended Class-Type Error' and error value 'Class-Type mismatch'.

mpls, routing

CIR value MUST be greater than or equal to 0; when CIR > 0, CBS MUST be greater than or equal to the maximum frame size. EIR MUST be greater than or equal to 0; when EIR > 0, EBS MUST be greater than or equal to the maximum frame size.

mpls, routing

If the MTU field is received with a value smaller than the minimum Ethernet frame transfer unit size, the node MUST generate a PathErr with error code 'Traffic Control Error' and error value 'Bad Tspec value'.

mpls, routing

Intermediate and egress nodes MUST verify they can support the requested Switching Granularity, MTU, and TLV values; if not, they MUST generate a PathErr with error code 'Traffic Control Error' and error value 'Service unsupported'.

mpls, routing

The Ethernet SENDER_TSPEC object MUST include at least one TLV and MAY include more than one TLV.

mpls, routing

The Ethernet SENDER_TSPEC object SHOULD be forwarded and delivered unchanged to both intermediate and egress nodes.

mpls, routing

The Index field value MUST correspond to at least one of the Class-Type values included in the CLASSTYPE object or the EXTENDED_CLASSTYPE object; by default it MUST be set to 0.

mpls, routing

The MTU field in the Ethernet SENDER_TSPEC MUST NOT take a value smaller than 46 bytes for Ethernet v2 or 38 bytes for IEEE 802.3.

mpls, routing

When signaling an Ethernet LSP, the Generalized LABEL_REQUEST Switching Type field MUST be set to 51 (L2SC) and the LSP Encoding Type field MUST be set to 2 (Ethernet).

mpls, routing

The Bandwidth Profile TLV Profile field is an 8-bit flag vector: bit 0 is the Coupling Flag (CF) selecting between two rate enforcement algorithm modes, and bit 1 is the Color Mode (CM) flag indicating color-blind (0) or color-aware (1) operation per MEF10.2.

mpls, routing

The Ethernet FLOWSPEC object (Class-Num=9, Class-Type=6) has the same format as the Ethernet SENDER_TSPEC object and carries reservation request information flowing upstream toward the ingress node.

mpls, routing

The Ethernet SENDER_TSPEC object (Class-Num=12, Class-Type=6) carries the traffic specification for an Ethernet LSP, including a 16-bit Switching Granularity field, a 16-bit MTU field, and one or more TLVs describing bandwidth profile parameters.

mpls, routing

The Index field (8 bits) in the Bandwidth Profile TLV references bandwidth allocated for a given traffic class. Its value MUST correspond to at least one Class-Type value in the CLASSTYPE or EXTENDED_CLASSTYPE object; by default it MUST be set to 0.

mpls, routing

The Switching Granularity field is 16 bits and indicates the Ethernet link type: value 0 means provided in signaling (see RFC6004), value 1 is Ethernet Port (port-based service), value 2 is Ethernet Frame (EVC-based service), and value 255 is reserved.

mpls, routing

There is no ADSPEC object associated with the Ethernet SENDER_TSPEC object; either the ADSPEC is omitted or an IntServ ADSPEC with Default General Characterization Parameters and Guaranteed Service fragment is used per RFC2210.

mpls, routing

IANA allocated two new Class Types in the RSVP Parameters registry: C-Type 6 for Ethernet SENDER_TSPEC under Class Number 9 (FLOWSPEC) and Class Number 12 (SENDER_TSPEC).

registry, mpls

IANA created the 'Ethernet Bandwidth Profiles' sub-registry under GMPLS Signaling Parameters for bit flags in the Bandwidth Profile TLV, allocated by IETF Standards Action; initial entries are bit 0 (CF) and bit 1 (CM).

registry, mpls

IANA created the 'Ethernet Sender TSpec TLVs / Ethernet Flowspec TLVs' sub-registry under GMPLS Signaling Parameters, with types 0-3 defined, 4-239 unassigned (Standards Action), 240-254 vendor-specific, 255 reserved.

registry, mpls

IANA created the 'Ethernet Switching Granularities' sub-registry under GMPLS Signaling Parameters with values 0-2 defined, 3-239 unassigned (Standards Action), 240-254 vendor-specific, 255 reserved, and 256-65535 not assigned.

registry, mpls

This document introduces no new security considerations beyond those in RFC3473. GMPLS security is described in RFC3471 Section 11 and RFC3209 for RSVP-TE; further details are in RFC5920 (Security Framework for MPLS and GMPLS Networks).

security, mpls

The Ethernet Bandwidth Profile TLV (Type=2, Length=24) encodes an 8-bit Profile flags field, 8-bit Index, 16-bit Reserved, and four 32-bit IEEE single-precision floating-point fields: CIR, CBS, EIR, and EBS.

mpls, routing

The Ethernet SENDER_TSPEC object header encodes a 16-bit Length, Class-Num (12), C-Type (6), 16-bit Switching Granularity, 16-bit MTU, followed by variable-length TLVs. Each TLV has a 16-bit Type, 16-bit Length, and variable Value field zero-padded to four-octet alignment.

mpls, routing