RFC 4003 on GMPLS Signaling Procedure for Egress Control

A new Request for Comments is now available in online RFC libraries.

        RFC 4003

        Title:      GMPLS Signaling Procedure for Egress Control
        Author(s):  L. Berger
        Status:     Standards Track
        Date:       February 2005
        Mailbox:    lberger@movaz.com
        Pages:      5
        Characters: 10306
        Updates:    3473

        I-D Tag:    draft-ietf-enum-webft-01.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4003.txt

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 document is a product of the Common Control and Measurement Plane
Working Group of the IETF.

This is now a Proposed Standard Protocol.

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.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.