[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Fw: RFC 4859 on Codepoint Registry for the Flags Field in the ResourceReservation Protocol-Traffic Engineering (RSVP-TE) SessionAttribute Object

FYI
----- Original Message ----- From: <rfc-editor@rfc-editor.org> 
To: <ietf-announce@ietf.org>; <rfc-dist@rfc-editor.org>
Cc: <mpls@lists.ietf.org>; <rfc-editor@rfc-editor.org>
Sent: Friday, April 27, 2007 2:39 AM
Subject: RFC 4859 on Codepoint Registry for the Flags Field in the ResourceReservation Protocol-Traffic Engineering (RSVP-TE) SessionAttribute Object 




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


       RFC 4859

       Title:      Codepoint Registry for the Flags
                   Field in the Resource Reservation Protocol-Traffic
                   Engineering (RSVP-TE) Session Attribute Object
       Author:     A. Farrel
       Status:     Informational
       Date:       April 2007
       Mailbox:    adrian@olddog.co.uk
       Pages:      5
       Characters: 7511
       Updates/Obsoletes/SeeAlso:   None

       I-D Tag:    draft-ietf-mpls-iana-rsvp-session-flags-01.txt

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

This document provides instructions to IANA for the creation of a new
codepoint registry for the flags field in the Session Attribute
object of the Resource Reservation Protocol Traffic Engineering
(RSVP-TE) signaling messages used in Multiprotocol Label Switching
(MPLS) and Generalized MPLS (GMPLS) signaling.  This memo provides
information for the Internet community.

This document is a product of the Multiprotocol Label Switching
Working Group of the IETF.


INFORMATIONAL: 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.

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.


The RFC Editor Team
USC/Information Sciences Institute

...



_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce