Browse Prior Art Database

GMPLS Signaling Procedure for Egress Control (RFC4003)

IP.com Disclosure Number: IPCOM000050532D
Original Publication Date: 2005-Feb-01
Included in the Prior Art Database: 2005-Feb-10
Document File: 6 page(s) / 10K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

L. Berger: AUTHOR

Abstract

This document clarifies the procedures for the control of the label used on an output/downstream interface of the egress node of a Label Switched Path (LSP). This control is also known as "Egress Control". Support for Egress Control is implicit in Generalized Multi-Protocol Label Switching (GMPLS) Signaling. This document clarifies the specification of GMPLS Signaling and does not modify GMPLS signaling mechanisms and procedures.

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

Network Working Group                                          L. Berger

Request for Comments: 4003                                Movaz Networks

Updates: 3473                                              February 2005

Category: Standards Track

              GMPLS Signaling Procedure for Egress Control

Status of This Memo

   This document specifies an Internet standards track protocol for the

   Internet community, and requests discussion and suggestions for

   improvements.  Please refer to the current edition of the "Internet

   Official Protocol Standards" (STD 1) for the standardization state

   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2005).

Abstract

   This document clarifies the procedures for the control of the label

   used on an output/downstream interface of the egress node of a Label

   Switched Path (LSP).  This control is also known as "Egress Control".

   Support for Egress Control is implicit in Generalized Multi-Protocol

   Label Switching (GMPLS) Signaling.  This document clarifies the

   specification of GMPLS Signaling and does not modify GMPLS signaling

   mechanisms and procedures.

1.  Background

   The ability to control the label used on the output/downstream

   interface of an egress node was one of the early requirements for

   GMPLS.  In the initial GMPLS documents, this was called "Egress

   Control".  As the GMPLS documents progressed, the ability to control

   a label on an egress interface was generalized to support control of

   a label on any interface.  This generalization is seen in Section 6

   of [RFC3471] and Section 5.1 of [RFC3473].  When this functionality

   was generalized, the procedures to support control of a label at the

   egress were also generalized.  Although the result was intended to

   cover egress control, this intention is not clear to all.  This note

   reiterates the procedures to cover control of a label used on an

   egress output/downstream interface.

Berger                      Standards Track                     [Page 1]

RFC 4003      GMPLS Signaling Procedure for Egress Control February 2005

   For context, the following is the text from the GMPLS signalling

   document dated June 2000 about how ERO (Explicit Route Object) for

   egress control:

      6. Egress Control

      The LSR at the head-end of an LSP can control the termination of

      the LSP by using the ERO.  To terminate an LSP on a particular

      outgoing interface of the egress LSR, the head-end may specify the

      IP address of that interface as the last element in the ERO,

      provided that interface has an associated IP address.

      There are case...