Assignment of the 'OAM Alert Label' for Multiprotocol Label Switching Architecture (MPLS) Operation and Maintenance (OAM) Functions
draft-ohta-mpls-label-value-03

The information below is for an old version of the document that is already published as an RFC
Document Type RFC Internet-Draft (individual in sub area)
Author Hiroshi Ohta 
Last updated 2013-03-02 (latest revision 2002-09-13)
Stream Internet Engineering Task Force (IETF)
Formats plain text pdf htmlized bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 3429 (Informational)
Consensus Boilerplate Unknown
Telechat date
Responsible AD Scott Bradner
Send notices to <hiro@spin.ad.jp>
A new Request for Comments is now available in online RFC libraries.

        RFC 3429
                            
        Title:      Assignment of the 'OAM Alert Label' for
                    Multiprotocol Label Switching Architecture (MPLS)
                    Operation and Maintenance (OAM) Functions
        Author(s):  H. Ohta
        Status:     Informational
        Date:       November 2002
        Mailbox:    ohta.hiroshi@lab.ntt.co.jp
        Pages:      6
        Characters: 10903
        Updates/Obsoletes:SeeAlso:    None
                            
        I-D Tag:    draft-ohta-mpls-label-value-03.txt

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

This document describes the assignment of one of the reserved label
values defined in RFC 3032 (MPLS label stack encoding) to the
'Operation and Maintenance (OAM) Alert Label' that is used by
user-plane Multiprotocol Label Switching Architecture (MPLS) OAM
functions for identification of MPLS OAM packets.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  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.echo 
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.