Generalized Multiprotocol Label Switching (GMPLS) Control of Ethernet Provider Backbone Traffic Engineering (PBB-TE)

Abstract

This specification is complementary to the GMPLS Ethernet Label Switching Architecture and Framework and describes the technologyspecific aspects of GMPLS control for Provider Backbone Bridge Traffic Engineering (PBB-TE). The necessary GMPLS extensions and mechanisms are described to establish Ethernet PBB-TE point-to-point (P2P) and point-to-multipoint (P2MP) connections. This document supports, but does not modify, the standard IEEE data plane. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6060.

Configuration of Proactive Operations, Administration, and Maintenance (OAM) Functions for MPLS-Based Transport Networks Using RSVP-TE

“…In particular, a network element could be overloaded if an attacker were to request high frequency liveliness monitoring of a large number of LSPs, targeting a single network element as discussed in [RFC7260] and [RFC6060].…”

GMPLS RSVP-TE Extensions for Ethernet Operations, Administration, and Maintenance (OAM) Configuration

“…This document does not introduce any additional security issues to those discussed in [RFC7260] and [RFC6060].…”

“…In the IETF, the work related to GMPLS Ethernet Label Switching (GELS) extended the GMPLS control plane to support the establishment of explicitly routed Ethernet connections [RFC5828] [RFC6060]. We refer to GMPLS-established Ethernet connections as "Ethernet LSPs".…”

Revised Definition of the GMPLS Switching Capability and Type Fields

“…The second issue is that the Switching Capability field value is used in Interior Gateway Protocols (IGPs) to indicate the format of the Switching Capability-specific information (SCSI) field, and that an implicit mapping of type to SCSI format is impractical for implementations that support multiple switching technologies. These issues led to the introduction of two new types for Ethernet in [RFC6004] and [RFC6060], namely:…”