Status of This Memo This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.

No abstract

No abstract

In recent years, significant work has been completed on traffic engineering enhancements to the generalized multiprotocol label switching protocol suite [1][2][3]. As a next step, reproducing the current trend of switching layers' integration happening in the data plane, network control is foreseen to go beyond the traditional per layer approach and tend toward an integrated model [4,5]. In these multilayer environments, a single GMPLS control plane drives various distinct switching layers at the same time and as a coherent whole, taking benefit from the "common" property of GMPLS. Beyond this application of supporting network control across different technologies, in this article we catalog the unified traffic engineering paradigms, discuss their applicability, and present their enforcement techniques. Furthermore, we show that the common GMPLS concept has the advantage of low operational complexity, and enables unified TE capabilities such as efficient network resource usage and rapid service provisioning.

This document describes the Equal Cost Multipath (ECMP) behavior of currently deployed MPLS networks. This document makes best practice recommendations for anyone defining an application to run over an MPLS network that wishes to avoid the reordering that can result from transmission of different packets from the same flow over multiple different equal cost paths. These recommendations rely on inspection of the IP version number field in packets. Despite the heuristic nature of the recommendations, they provide a relatively safe way to operate MPLS networks, even if future allocations of IP version numbers were made for some purpose.

No abstract

At first glance, the acronym "OAM" seems to be well-known and wellunderstood. Looking at the acronym a bit more closely reveals a set of recurring problems that are revisited time and again. This document provides a definition of the acronym "OAM" (Operations, Administration, and Maintenance) for use in all future IETF documents that refer to OAM. There are other definitions and acronyms that will be discussed while exploring the definition of the constituent parts of the "OAM" term. Status of This Memo This memo documents an Internet Best Current Practice. 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 BCPs 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/rfc6291. Andersson, et al.

No abstract