[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Protocol Action: 'Encoding of Attributes for Multiprotocol Label Switching (MPLS) Label Switched Path (LSP) Establishment Using RSVP-TE' to Proposed Standard
The IESG has approved the following document:
- 'Encoding of Attributes for Multiprotocol Label Switching (MPLS) Label
Switched Path (LSP) Establishment Using RSVP-TE '
<draft-ietf-ccamp-rfc4420bis-03.txt> as a Proposed Standard
This document is the product of the Common Control and Measurement Plane
Working Group.
The IESG contact persons are Ross Callon and David Ward.
A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ccamp-rfc4420bis-03.txt
Technical Summary
This document replaces and obsoletes RFC 4420. The only change is
in the encoding of the Type-Length-Variable (TLV) data structures.
This allows consistency with the use of TLV data structures in other
related documents, and therefore essentially corrects a bug in 4420.
Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs) may
be established using the Resource Reservation Protocol Traffic
Engineering (RSVP-TE) extensions. This protocol includes an object
(the SESSION_ATTRIBUTE object) that carries a Flags field used to
indicate options and attributes of the LSP. That Flags field has
eight bits allowing for eight options to be set. Recent proposals in
many documents that extend RSVP-TE have suggested uses for each of
the previously unused bits.
This document defines a new object for RSVP-TE messages that allows
the signaling of further attribute bits and also the carriage of
arbitrary attribute parameters to make RSVP-TE easily extensible to
support new requirements. Additionally, this document defines a way
to record the attributes applied to the LSP on a hop-by-hop basis.
The object mechanisms defined in this document are equally applicable
to Generalized MPLS (GMPLS) Packet Switch Capable (PSC) LSPs and to
GMPLS non-PSC LSPs.
Working Group Summary
This document corrects a bug in RFC4220 which was found during
interoperability testing. Once this bug was found, there was no
controversy regarding how to fix this.
Document Quality
Current implementations are compatible with this document
(and therefore no longer compatible with one detail in RFC4220).
Personnel
Deborah Brungard is the dFrom ietf-announce-bounces at ietf.org Mon Nov 10 11:32:19 2008
Return-Path: <ietf-announce-bounces at ietf.org>
X-Original-To: ietf-announce-web-archive at megatron.ietf.org
Delivered-To: ietfarch-ietf-announce-web-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id C5A8A28C106;
Mon, 10 Nov 2008 11:32:18 -0800 (PST)
X-Original-To: ietf-announce at ietf.org
Delivered-To: ietf-announce at core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30)
id BC1BB3A6A9F; Mon, 10 Nov 2008 11:32:17 -0800 (PST)
X-idtracker: yes
From: The IESG <iesg-secretary at ietf.org>
To: IETF-Announce <ietf-announce at ietf.org>
Subject: Protocol Action: 'Encoding of Attributes for
Multiprotocol Label Switching (MPLS) Label Switched Path (LSP)
Establishment Using RSVP-TE' to Proposed Standard
Message-Id: <20081110193217.BC1BB3A6A9F at core3.amsl.com>
Date: Mon, 10 Nov 2008 11:32:17 -0800 (PST)
Cc: ccamp mailing list <ccamp at ops.ietf.org>,
Internet Architecture Board <iab at iab.org>,
ccamp chair <ccamp-chairs at tools.ietf.org>,
RFC Editor <rfc-editor at rfc-editor.org>
X-BeenThere: ietf-announce at ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>,
<mailto:ietf-announce-request at ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ietf-announce>
List-Post: <mailto:ietf-announce at ietf.org>
List-Help: <mailto:ietf-announce-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>,
<mailto:ietf-announce-request at ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-announce-bounces at ietf.org
Errors-To: ietf-announce-bounces at ietf.org
The IESG has approved the following document:
- 'Encoding of Attributes for Multiprotocol Label Switching (MPLS) Label
Switched Path (LSP) Establishment Using RSVP-TE '
<draft-ietf-ccamp-rfc4420bis-03.txt> as a Proposed Standard
This document is the product of the Common Control and Measurement Plane
Working Group.
The IESG contact persons are Ross Callon and David Ward.
A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ccamp-rfc4420bis-03.txt
Technical Summary
This document replaces and obsoletes RFC 4420. The only change is
in the encoding of the Type-Length-Variable (TLV) data structures.
This allows consistency with the use of TLV data structures in other
related documents, and therefore essentially corrects a bug in 4420.
Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs) may
be established using the Resource Reservation Protocol Traffic
Engineering (RSVP-TE) extensions. This protocol includes an object
(the SESSION_ATTRIBUTE object) that carries a Flags field used to
indicate options and attributes of the LSP. That Flags field has
eight bits allowing for eight options to be set. Recent proposals in
many documents that extend RSVP-TE have suggested uses for each of
the previously unused bits.
This document defines a new object for RSVP-TE messages that allows
the signaling of further attribute bits and also the carriage of
arbitrary attribute parameters to make RSVP-TE easily extensible to
support new requirements. Additionally, this document defines a way
to record the attributes applied to the LSP on a hop-by-hop basis.
The object mechanisms defined in this document are equally applicable
to Generalized MPLS (GMPLS) Packet Switch Capable (PSC) LSPs and to
GMPLS non-PSC LSPs.
Working Group Summary
This document corrects a bug in RFC4220 which was found during
interoperability testing. Once this bug was found, there was no
controversy regarding how to fix this.
Document Quality
Current implementations are compatible with this document
(and therefore no longer compatible with one detail in RFC4220).
Personnel
Deborah Brungard ocument shepherd. Ross Callon is the
responsible AD.
RFC Editor Note
Please update section 3 as follows:
OLD
Length
Indicates the total length of the TLV, i.e., 4 + the length of
the value field in octets. A value field whose length is not a
multiple of four MUST be zero-padded so that the TLV is four-
octet aligned.
Value
The data for the TLV padded as described above.
NEW
Length
Indicates the total length of the TLV in octets. That is the
combined length of the Type, Length, and Value fields, i.e.,
four plus the length of the Value field in octets.
The entire TLV MUST be padded with between zero and three
trailing zeros to make it four-octet aligned. The Length field
does not count any padding.
Value
The data carried in the TLV.
_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce
is the document shepherd. Ross Callon is the
responsible AD.
RFC Editor Note
Please update section 3 as follows:
OLD
Length
Indicates the total length of the TLV, i.e., 4 + the length of
the value field in octets. A value field whose length is not a
multiple of four MUST be zero-padded so that the TLV is four-
octet aligned.
Value
The data for the TLV padded as described above.
NEW
Length
Indicates the total length of the TLV in octets. That is the
combined length of the Type, Length, and Value fields, i.e.,
four plus the length of the Value field in octets.
The entire TLV MUST be padded with between zero and three
trailing zeros to make it four-octet aligned. The Length field
does not count any padding.
Value
The data carried in the TLV.
_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce