draft-ietf-pce-disco-proto-isis-04.txt   draft-ietf-pce-disco-proto-isis-05.txt 
Network Working Group J.L. Le Roux (Editor) Network Working Group J.L. Le Roux (Editor)
Internet Draft France Telecom Internet Draft France Telecom
Category: Standard Track Intended Status: Standards Track
Expires: November 2007 J.P. Vasseur (Editor) Expires: November 2007 J.P. Vasseur (Editor)
Cisco System Inc. Cisco System Inc.
Yuichi Ikejiri Yuichi Ikejiri
NTT Communications NTT Communications
Raymond Zhang Raymond Zhang
BT Infonet BT Infonet
IS-IS protocol extensions for Path Computation Element (PCE) Discovery IS-IS protocol extensions for Path Computation Element (PCE) Discovery
draft-ietf-pce-disco-proto-isis-04.txt draft-ietf-pce-disco-proto-isis-05.txt
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 41
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 November 3, 2007.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). All rights reserved. Copyright (C) The IETF Trust (2007). All rights reserved.
Abstract Abstract
There are various circumstances where it is highly desirable for a There are various circumstances where it is highly desirable for a
Path Computation Client (PCC) to be able to dynamically and Path Computation Client (PCC) to be able to dynamically and
automatically discover a set of Path Computation Elements (PCE), automatically discover a set of Path Computation Elements (PCE),
along with some information that can be used for PCE selection. When along with some information that can be used for PCE selection. When
skipping to change at page 3, line 5 skipping to change at page 3, line 6
7.1. IS-IS Sub-TLV..............................................15 7.1. IS-IS Sub-TLV..............................................15
7.2. PCED Sub-TLVs registry.....................................15 7.2. PCED Sub-TLVs registry.....................................15
8. Security Considerations....................................15 8. Security Considerations....................................15
9. Manageability Considerations...............................16 9. Manageability Considerations...............................16
9.1. Control of Policy and Functions............................16 9.1. Control of Policy and Functions............................16
9.2. Information and Data Model.................................16 9.2. Information and Data Model.................................16
9.3. Liveness Detection and Monitoring..........................16 9.3. Liveness Detection and Monitoring..........................16
9.4. Verify Correct Operations..................................16 9.4. Verify Correct Operations..................................16
9.5. Requirements on Other Protocols and Functional 9.5. Requirements on Other Protocols and Functional
Components...............................................16 Components...............................................16
9.6. Impact on Network Operations...............................16 9.6. Impact on Network Operations...............................17
10. Acknowledgments............................................17 10. Acknowledgments............................................17
11. References.................................................17 11. References.................................................17
11.1. Normative References.......................................17 11.1. Normative References.......................................17
11.2. Informative References.....................................18 11.2. Informative References.....................................18
12. Editors' Addresses:........................................18 12. Editors' Addresses:........................................18
13. Contributors' Adresses:....................................18 13. Contributors' Adresses:....................................18
14. Intellectual Property Statement............................19 14. Intellectual Property Statement............................19
1. Terminology 1. Terminology
skipping to change at page 3, line 52 skipping to change at page 3, line 53
path computation to be performed by a Path Computation Element. path computation to be performed by a Path Computation Element.
PCE: Path Computation Element: An entity (component, application, PCE: Path Computation Element: An entity (component, application,
or network node) that is capable of computing a network path or or network node) that is capable of computing a network path or
route based on a network graph, and applying computational route based on a network graph, and applying computational
constraints. constraints.
PCE-Domain: In a PCE context this refers to any collection of PCE-Domain: In a PCE context this refers to any collection of
network elements within a common sphere of address management or network elements within a common sphere of address management or
path computational responsibility (referred to as "domain" in path computational responsibility (referred to as "domain" in
[RFC4655]). Examples of PCE-Domains include IGP areas and [RFC4655]). Examples of PCE-Domains include IGP areas and ASes.
Autonomous Systems. This should be distinguished from an IS-IS
routing domain as defined by [ISO]. This should be distinguished from an IS-IS routing domain as
defined by [ISO].
PCEP: Path Computation Element communication Protocol. PCEP: Path Computation Element communication Protocol.
TE LSP: Traffic Engineered Label Switched Path. TE LSP: Traffic Engineered Label Switched Path.
2. Introduction 2. Introduction
[RFC4655] describes the motivations and architecture for a Path [RFC4655] describes the motivations and architecture for a Path
Computation Element (PCE)-based path computation model for Multi Computation Element (PCE)-based path computation model for Multi
Protocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Protocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic
skipping to change at page 15, line 32 skipping to change at page 15, line 32
The IANA is requested to create a new sub-registry of the IS-IS The IANA is requested to create a new sub-registry of the IS-IS
Router Capability sub-TLVs registry, named the "PCED sub-TLVs" Router Capability sub-TLVs registry, named the "PCED sub-TLVs"
registry, and manage sub-TLV type identifiers as follows: registry, and manage sub-TLV type identifiers as follows:
- sub-TLV Type - sub-TLV Type
- sub-TLV Name - sub-TLV Name
- Reference - Reference
This document defines five sub-TLVs as follows (suggested values): This document defines five sub-TLVs as follows (suggested values):
Value TLV name References Sub-TLV Sub-TLV
Type Name References
----- -------- ---------- ----- -------- ----------
1 PCE-ADDRESS This document 1 PCE-ADDRESS This document
2 PATH-SCOPE This document 2 PATH-SCOPE This document
3 PCE-DOMAIN This document 3 PCE-DOMAIN This document
4 NEIG-PCE-DOMAIN This document 4 NEIG-PCE-DOMAIN This document
5 PCE-CAP-FLAGS This document 5 PCE-CAP-FLAGS This document
6 CONGESTION This document 6 CONGESTION This document
New sub-TLV type values may be allocated only by an IETF Consensus New sub-TLV type values may be allocated only by an IETF Consensus
action. action.
skipping to change at page 17, line 35 skipping to change at page 17, line 40
11. References 11. References
11.1. Normative References 11.1. Normative References
[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.
[ISO] "Intermediate System to Intermediate System Intra-Domain [ISO] "Intermediate System to Intermediate System Intra-Domain
Routeing Exchange Protocol for use in Conjunction with the Routeing Exchange Protocol for use in Conjunction with the
Protocol for Providing the Connectionless-mode Network Service Protocol for Providing the Connectionless-mode Network
(ISO 8473)", ISO DP 10589, February 1990. Service (ISO 8473)", ISO DP 10589, February 1990.
[RFC3784] Li, T., Smit, H., "IS-IS extensions for Traffic [RFC3784] Li, T., Smit, H., "IS-IS extensions for Traffic
Engineering", RFC 3784, June 2004. Engineering", RFC 3784, June 2004.
[IS-IS-CAP] Vasseur, J.P. et al., "IS-IS extensions for advertising [IS-IS-CAP] Vasseur, J.P. et al., "IS-IS extensions for advertising
router information", draft-ietf-isis-caps, work in progress. router information", draft-ietf-isis-caps, work in
progress.
[RFC4655] Farrel, A., Vasseur, J.P., Ash, J., "Path Computation
Element (PCE)-based Architecture", RFC4655, august 2006.
[RFC4674] Le Roux, J.L., et al. "Requirements for PCE discovery",
RFC4674, October 2006.
[RFC3567] Li, T. and R. Atkinson, "Intermediate System to [RFC3567] Li, T. and R. Atkinson, "Intermediate System to
Intermediate System (IS-IS) Cryptographic Authentication", RFC 3567, Intermediate System (IS-IS) Cryptographic Authentication",
July 2003. RFC 3567, July 2003.
[PCED-OSPF] Le Roux, Vasseur, et al. "OSPF protocol extensions for [PCED-OSPF] Le Roux, Vasseur, et al. "OSPF protocol extensions for
Path Computation Element (PCE) Discovery", draft-ietf-pce-disco- Path Computation Element (PCE) Discovery", draft-ietf-
proto-ospf, work in progress. pce-disco-proto-ospf, work in progress.
11.2. Informative References 11.2. Informative References
[RFC4655] Farrel, A., Vasseur, J.P., Ash, J., "Path Computation
Element (PCE)-based Architecture", RFC4655, August 2006.
[RFC4657] Ash, J., Le Roux, J.L., "PCE Communication Protocol Generic [RFC4657] Ash, J., Le Roux, J.L., "PCE Communication Protocol Generic
Requirements", RFC4657, September 2006. Requirements", RFC4657, September 2006.
[RFC4674] Le Roux, J.L., et al. "Requirements for PCE discovery",
RFC4674, October 2006.
[PCEP] Vasseur, Le Roux, et al., "Path Computation Element (PCE) [PCEP] Vasseur, Le Roux, et al., "Path Computation Element (PCE)
communication Protocol (PCEP) - Version 1", draft-ietf-pce-pcep, work communication Protocol (PCEP) - Version 1", draft-ietf-pce-
in progress. pcep, work in progress.
[PCED-MIB] Stephan, E., "Definitions of Managed Objects for Path [PCED-MIB] Stephan, E., "Definitions of Managed Objects for Path
Computation Element Discovery", draft-ietf-pce-disc-mib, work in Computation Element Discovery", draft-ietf-pce-disc-mib,
progress. work in progress.
12. Editors' Addresses: 12. Editors' Addresses:
Jean-Louis Le Roux (Editor) Jean-Louis Le Roux (Editor)
France Telecom France Telecom
2, avenue Pierre-Marzin 2, avenue Pierre-Marzin
22307 Lannion Cedex 22307 Lannion Cedex
FRANCE FRANCE
Email: jeanlouis.leroux@orange-ftgroup.com Email: jeanlouis.leroux@orange-ftgroup.com
 End of changes. 14 change blocks. 
26 lines changed or deleted 27 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/