draft-ietf-mpls-number-0-bw-te-lsps-04.txt   draft-ietf-mpls-number-0-bw-te-lsps-05.txt 
Networking Working Group JP. Vasseur, Ed. Networking Working Group JP. Vasseur, Ed.
Internet-Draft Cisco Systems, Inc Internet-Draft Cisco Systems, Inc
Intended status: Standards Track Matthew. R. Meyer Intended status: Standards Track Matthew. R. Meyer
Expires: June 11, 2007 Global Crossing Expires: June 15, 2007 Global Crossing
K. Kumaki K. Kumaki
KDDI Corporation KDDI Corporation
Alberto. Tempia Bonda Alberto. Tempia Bonda
Telecom Italia Telecom Italia
December 8, 2006 December 12, 2006
A Link-Type sub-TLV to convey the number of Traffic Engineering Label A Link-Type sub-TLV to convey the number of Traffic Engineering Label
Switch Paths signalled signalled with zero reserved bandwidth across a Switched Paths signalled with zero reserved bandwidth across a link
link draft-ietf-mpls-number-0-bw-te-lsps-05
draft-ietf-mpls-number-0-bw-te-lsps-04
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 41 skipping to change at page 1, line 40
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on June 11, 2007. This Internet-Draft will expire on June 15, 2007.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2006). Copyright (C) The Internet Society (2006).
Abstract Abstract
Several Link-type sub-TLVs have been defined for OSPF and ISIS in the Several Link-type sub-TLVs have been defined for OSPF and IS-IS in
context of Multiprotocol Label Switching (MPLS) Traffic Engineering the context of Multiprotocol Label Switching (MPLS) Traffic
(TE) in order to advertise some link characteristics such as the Engineering (TE) in order to advertise some link characteristics such
available bandwidth, traffic engineering metric, administrative group as the available bandwidth, traffic engineering metric,
and so on. By making statistical assumption on the aggregated administrative group and so on. By making statistical assumption on
traffic carried onto a set of TE Label Switched Paths (LSPs) the aggregated traffic carried onto a set of TE Label Switched Paths
signalled with zero bandwdith (referred to as unconstrained TE LSP in (LSPs) signalled with zero bandwith (referred to as unconstrained TE
this document), and with the knowledge of the number of unconstrained LSP in this document), and with the knowledge of the number of
TE LSPs signalled across a link, algorithms can be designed to load unconstrained TE LSPs signalled across a link, algorithms can be
balance (existing or newly configured) unconstrained TE LSP across a designed to load balance (existing or newly configured) unconstrained
set of equal cost paths. This requires the knowledge of the number TE LSP across a set of equal cost paths. This requires the knowledge
of unconstrained TE LSPs signalled across a link. This document of the number of unconstrained TE LSPs signalled across a link. This
specifies a new Link-type Traffic Engineering sub-TLV used to document specifies a new Link-type Traffic Engineering sub-TLV used
advertise the number of unconstrained TE LSP(s) signalled across a to advertise the number of unconstrained TE LSP(s) signalled across a
link. link.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
Table of Contents Table of Contents
skipping to change at page 7, line 8 skipping to change at page 7, line 8
6. Security Considerations 6. Security Considerations
The function described in this document does not create any new The function described in this document does not create any new
security issues for the OSPF and the IS-IS protocols. Security security issues for the OSPF and the IS-IS protocols. Security
considerations are covered in [RFC2328] and [RFC2470] for the base considerations are covered in [RFC2328] and [RFC2470] for the base
OSPF protocol and in [RFC1194] for IS-IS. OSPF protocol and in [RFC1194] for IS-IS.
7. Acknowledgements 7. Acknowledgements
The authors would like to thank Jean-Louis Le Roux, Adrian Farrel, The authors would like to thank Jean-Louis Le Roux, Adrian Farrel,
Daniel King, Acee Lindem, Loa Anderson and Les Ginsberg for Daniel King, Acee Lindem and Loa Anderson for their useful inputs.
their useful inputs.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC1194] Zimmerman, D., "Finger User Information Protocol", [RFC1194] Zimmerman, D., "Finger User Information Protocol",
RFC 1194, November 1990. RFC 1194, November 1990.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
skipping to change at page 9, line 7 skipping to change at page 9, line 7
Alberto Tempia Bonda Alberto Tempia Bonda
Telecom Italia Telecom Italia
via G. Reiss Romoli 274 via G. Reiss Romoli 274
Torino, 10148 Torino, 10148
ITALIA ITALIA
Email: alberto.tempiabonda@telecomitalia.it Email: alberto.tempiabonda@telecomitalia.it
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2006). Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
 End of changes. 9 change blocks. 
28 lines changed or deleted 26 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/