Subject: BCP0129 RFC 4929 on Change Process for Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Protocols and Procedures

From: [email-masked]
Date: Tue, 26 Jun 2007 16:03:28 -0700 (PDT)

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

        BCP 129        

        RFC 4929

        Title:      Change Process for Multiprotocol Label 

                    Switching (MPLS) and Generalized MPLS (GMPLS) 

                    Protocols and Procedures 

        Author:     L. Andersson, Ed.,

                    A. Farrel, Ed.

        Status:     Best Current Practice

        Date:       June 2007

        Mailbox:    [email-masked], 

                    [email-masked]

        Pages:      23

        Characters: 56742

        Updates:    

        See-Also:   BCP0129

        I-D Tag:    draft-andersson-rtg-gmpls-change-08.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4929.txt

This document provides guidelines for applying or extending the

MPLS or GMPLS ((G)MPLS) protocol suites and clarifies the IETF's

(G)MPLS working groups' responsibility for the (G)MPLS protocols.

This document is directed to multi-vendor fora and Standards

Development Organizations (SDOs) to provide an understanding of

(G)MPLS work in the IETF and documents the requisite use of IETF

review procedures when considering (G)MPLS applications or

protocol extensions in their work.  This document does not modify

IETF processes.  This document specifies an Internet Best Current 

Practices for the Internet Community, and requests discussion and 

suggestions for improvements.

This document specifies an Internet Best Current Practices for the

Internet Community, and requests discussion and suggestions for

improvements.  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 [email-masked].  Requests to be

added to or deleted from the RFC-DIST distribution list should

be sent to [email-masked].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending

an EMAIL message to [email-masked] with the message body 

help: ways_to_get_rfcs. For example:

        To: [email-masked]

        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 [email-masked].  Unless

specifically noted otherwise on the RFC itself, all RFCs are for

unlimited distribution.

Submissions for Requests for Comments should be sent to

[email-masked].  Please consult RFC 2223, Instructions to RFC

Authors, for further information.

The RFC Editor Team

USC/Information Sciences Institute

...

_______________________________________________
IETF-Announce mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/ietf-announce

ed from the RFC-DIST distribution list should

be sent to [email-masked].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending

an EMAIL message to [email-masked] with the message body 

help: ways_to_get_rfcs. For example:

        To: [email-masked]

        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 [email-masked].  Unless

specifically noted otherwise on the RFC itself, all RFCs are for

unlimited distribution.

Submissions for Requests for Comments should be sent to

[email-masked].  Please consult RFC 2223, Instructions to RFC

Authors, for further information.

The RFC Editor Team

USC/Information Sciences Institute

...

_______________________________________________
IETF-Announce mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/ietf-announce