Surety is performing system maintenance this weekend. Electronic date stamps on new Prior Art Database disclosures may be delayed.
Browse Prior Art Database

Label Switched Path (LSP) Attribute in the Explicit Route Object (ERO) (RFC7570)

IP.com Disclosure Number: IPCOM000242382D
Original Publication Date: 2015-Jul-01
Included in the Prior Art Database: 2015-Jul-10
Document File: 30 page(s) / 34K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

C. Margaria: AUTHOR [+5]


Generalized MPLS (GMPLS) Traffic Engineering (TE) Label Switched Paths (LSPs) can be route constrained by making use of the Explicit Route Object (ERO) and related subobjects as defined in [RFC3209], [RFC3473], [RFC3477], [RFC4873], [RFC4874], [RFC5520], and [RFC5553]. Several documents have identified the need for attributes that can be targeted at specific hops in the path of an LSP, including [RFC6163], [WSON-SIG], [RFC7571], or [OBJ-FUN]. This document provides a generic mechanism for use by these other documents.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 8% of the total text.

Internet Engineering Task Force (IETF)                  C. Margaria, Ed. Request for Comments: 7570                                       Juniper Category: Standards Track                                  G. Martinelli ISSN: 2070-1721                                                    Cisco                                                                 S. Balls                                                                B. Wright                                                               Metaswitch                                                                July 2015

  Label Switched Path (LSP) Attribute in the Explicit Route Object (ERO)


   RFC 5420 extends RSVP-TE to specify or record generic attributes that    apply to the whole of the path of a Label Switched Path (LSP).  This    document defines an extension to the RSVP Explicit Route Object (ERO)    and Record Route Object (RRO) to allow them to specify or record    generic attributes that apply to a given hop.

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/rfc7570.

Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are provided without warranty as    described in the Simplified BSD License.

Margaria, et al.             Standards Track                    [Page 1]
 RFC 7570               General ERO LSP Parameters              July 2015

 Table of Contents

   1.  Introduction  . . ....