draft-ietf-mpls-explicit-resource-control-bundle-07.txt   draft-ietf-mpls-explicit-resource-control-bundle-08.txt 
Network Working Group Anca Zamfir Network Working Group Anca Zamfir
Internet Draft Zafar Ali Internet Draft Zafar Ali
Expires: November 24, 2010 Cisco Systems Expires: April 24, 2011 Cisco Systems
Category: Standards Track Dimitri Papadimitriou Category: Experimental Dimitri Papadimitriou
Alcatel-Lucent Alcatel-Lucent
May 25, 2010 October 25, 2010
Component Link Recording and Resource Control for TE Link Bundles Component Link Recording and Resource Control for TE Link Bundles
draft-ietf-mpls-explicit-resource-control-bundle-07.txt draft-ietf-mpls-explicit-resource-control-bundle-08.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with This Internet-Draft is submitted to IETF in full conformance with
the provisions of BCP 78 and BCP 79. This document may contain the provisions of BCP 78 and BCP 79. This document may contain
material from IETF Documents or IETF Contributions published or material from IETF Documents or IETF Contributions published or
made publicly available before November 10, 2008. The person(s) made publicly available before November 10, 2008. The person(s)
controlling the copyright in some of this material may not have controlling the copyright in some of this material may not have
granted the IETF Trust the right to allow modifications of such granted the IETF Trust the right to allow modifications of such
material outside the IETF Standards Process. Without obtaining material outside the IETF Standards Process. Without obtaining
an adequate license from the person(s) controlling the copyright an adequate license from the person(s) controlling the copyright
in such materials, this document may not be modified outside the in such materials, this document may not be modified outside the
IETF Standards Process, and derivative works of it may not be IETF Standards Process, and derivative works of it may not be
created outside the IETF Standards Process, except to format it created outside the IETF Standards Process, except to format it
for publication as an RFC or to translate it into languages other for publication as an RFC or to translate it into languages other
than English. than English.
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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet- documents at any time. It is inappropriate to use Internet-
Drafts as reference material or to cite them other than as "work Drafts as reference material or to cite them other than as "work
in progress." 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 November 24, 2010. This Internet-Draft will expire on April 24, 2011.
Abstract Abstract
Record Route is a useful administrative tool that has been used Record Route is a useful administrative tool that has been used
extensively by the service providers. However, when TE links are extensively by the service providers. However, when TE links are
bundled, identification of label resource in Record Route Object bundled, identification of label resource in Record Route Object
(RRO) is not enough for the administrative purpose. Network service (RRO) is not enough for the administrative purpose. Network service
Component Link Record. & Resource Control for TE Link Bundles Component Link Record. & Resource Control for TE Link Bundles
providers would like to know the component link within a TE link that providers would like to know the component link within a TE link that
skipping to change at page 2, line 44 skipping to change at page 3, line 4
4. Signaling Component Interface Identifier in ERO................6 4. Signaling Component Interface Identifier in ERO................6
4.1 Processing of Component Interface Identifier ERO Subobject.7 4.1 Processing of Component Interface Identifier ERO Subobject.7
5. Forward Compatibility Note.....................................9 5. Forward Compatibility Note.....................................9
6. Security Considerations........................................9 6. Security Considerations........................................9
7. IANA Considerations...........................................10 7. IANA Considerations...........................................10
8. References....................................................10 8. References....................................................10
8.1 Normative Reference.......................................10 8.1 Normative Reference.......................................10
8.2 Informative Reference.....................................11 8.2 Informative Reference.....................................11
9. Author's Addresses............................................11 9. Author's Addresses............................................11
10. Copyright Notice.............................................12 10. Copyright Notice.............................................12
11. Legal........................................................12
Component Link Record. & Resource Control for TE Link Bundles Component Link Record. & Resource Control for TE Link Bundles
1. Terminology 1. Terminology
TE Link: Unless specified otherwise, it refers to a bundled Traffic TE Link: Unless specified otherwise, it refers to a bundled Traffic
Engineering link as defined in [RFC4201]. Furthermore, the terms TE Engineering link as defined in [RFC4201]. Furthermore, the terms TE
Link and bundled TE Link are used interchangeably in this draft. Link and bundled TE Link are used interchangeably in this draft.
Component (interface) link: refers (locally) to a component link as Component (interface) link: refers (locally) to a component link as
part of a bundled TE link. A component link is numbered/ unnumbered part of a bundled TE link. A component link is numbered/ unnumbered
skipping to change at page 12, line 6 skipping to change at page 12, line 6
Email: ancaz@cisco.com Email: ancaz@cisco.com
Zafar Ali Zafar Ali
Cisco systems, Inc., Cisco systems, Inc.,
Email: zali@cisco.com Email: zali@cisco.com
Dimitri Papadimitriou Dimitri Papadimitriou
Email: dimitri.papadimitriou@alcatel-lucent.be Email: dimitri.papadimitriou@alcatel-lucent.be
Component Link Record. & Resource Control for TE Link Bundles Component Link Record. & Resource Control for TE Link Bundles
10. Copyright Notice 10. Copyright
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the (http://trustee.ietf.org/license-info) in effect on the date of
date of publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and carefully, as they describe your rights and restrictions with
restrictions with respect to this document. Code Components respect to this document. Code Components extracted from this
extracted from this document must include Simplified BSD License document must include Simplified BSD License text as described
text as described in Section 4.e of the Trust Legal Provisions in Section 4.e of the Trust Legal Provisions and are provided
and are provided without warranty as described in the BSD without warranty as described in the Simplified BSD License.
License.
11. Legal
This documents and the information contained therein are provided
on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
WARRANTY THAT THE USE OF THE INFORMATION THEREIN WILL NOT
INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY
OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement Acknowledgement
Funding for the RFC Editor function is provided by the IETF Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA). Administrative Support Activity (IASA).
 End of changes. 14 change blocks. 
54 lines changed or deleted 41 lines changed or added

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