--- 1/draft-ietf-mpls-tp-nm-req-03.txt 2009-09-04 11:12:21.000000000 +0200 +++ 2/draft-ietf-mpls-tp-nm-req-04.txt 2009-09-04 11:12:21.000000000 +0200 @@ -1,20 +1,20 @@ Network Working Group Hing-Kam Lam Internet Draft Alcatel-Lucent Expires: March, 2010 Scott Mansfield Intended Status: Standards Track Eric Gray Ericsson - August 31, 2009 + September 1, 2009 MPLS TP Network Management Requirements - draft-ietf-mpls-tp-nm-req-03.txt + draft-ietf-mpls-tp-nm-req-04.txt Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. @@ -24,76 +24,76 @@ documents at any time. It is inappropriate to use Internet- Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html - This Internet-Draft will expire on March 31, 2010. + This Internet-Draft will expire on March 1, 2010. Abstract This document specifies the requirements for the management of equipment used in networks supporting an MPLS Transport Profile (MPLS-TP). The requirements are defined for specification of network management aspects of protocol mechanisms and procedures that constitute the building blocks out of which the MPLS transport profile is constructed. That is, these requirements indicate what management capabilities need to be available in MPLS for use in managing the MPLS-TP. This document is intended to identify essential network management capabilities, not to specify what functions any particular MPLS implementation supports. Table of Contents - 1. Introduction........................................3 - 1.1. Terminology.....................................4 - 2. Management Interface Requirements......................6 + 1. Introduction..............................................3 + 1.1. Terminology..........................................4 + 2. Management Interface Requirements.........................6 3. Management Communication Channel (MCC) Requirements.......6 4. Management Communication Network (MCN) Requirements.......6 - 5. Fault Management Requirements..........................8 - 5.1. Supervision Function.............................8 - 5.2. Validation Function..............................9 - 5.3. Alarm Handling Function..........................10 - 5.3.1. Alarm Severity Assignment....................10 - 5.3.2. Alarm Suppression ..........................10 - 5.3.3. Alarm Reporting............................10 - 5.3.4. Alarm Reporting Control.....................11 - 6. Configuration Management Requirements..................11 - 6.1. System Configuration............................11 - 6.2. Control Plane Configuration......................12 - 6.3. Path Configuration..............................12 - 6.4. Protection Configuration.........................13 - 6.5. OAM Configuration...............................13 - 7. Performance Management Requirements....................14 - 7.1. Path Characterization Performance Metrics..........14 - 7.2. Performance Measurement Instrumentation............16 - 7.2.1. Measurement Frequency.......................16 - 7.2.2. Measurement Scope ..........................16 - 8. Security Management Requirements......................16 - 8.1. Management Communication Channel Security..........16 - 8.2. Signaling Communication Channel Security...........17 - 8.3. Distributed Denial of Service ....................17 - 9. Security Considerations..............................18 - 10. IANA Considerations................................18 - 11. Acknowledgments....................................18 - 12. References........................................18 - 12.1. Normative References...........................18 - 12.2. Informative References..........................19 - Author's Addresses.....................................21 - Copyright Statement....................................21 - Acknowledgment........................................22 - Appendix A - Communication Channel (CCh) Examples..........23 + 5. Fault Management Requirements.............................8 + 5.1. Supervision Function.................................8 + 5.2. Validation Function..................................9 + 5.3. Alarm Handling Function.............................10 + 5.3.1. Alarm Severity Assignment......................10 + 5.3.2. Alarm Suppression .............................10 + 5.3.3. Alarm Reporting................................11 + 5.3.4. Alarm Reporting Control........................11 + 6. Configuration Management Requirements....................11 + 6.1. System Configuration................................12 + 6.2. Control Plane Configuration.........................12 + 6.3. Path Configuration..................................12 + 6.4. Protection Configuration............................13 + 6.5. OAM Configuration...................................13 + 7. Performance Management Requirements......................14 + 7.1. Path Characterization Performance Metrics...........14 + 7.2. Performance Measurement Instrumentation.............16 + 7.2.1. Measurement Frequency..........................16 + 7.2.2. Measurement Scope .............................16 + 8. Security Management Requirements.........................16 + 8.1. Management Communication Channel Security...........17 + 8.2. Signaling Communication Channel Security............17 + 8.3. Distributed Denial of Service ......................17 + 9. Security Considerations..................................18 + 10. IANA Considerations.....................................18 + 11. Acknowledgments.........................................18 + 12. References..............................................18 + 12.1. Normative References...............................18 + 12.2. Informative References.............................19 + Author's Addresses..........................................21 + Copyright Statement.........................................21 + Acknowledgment..............................................22 + Appendix A - Communication Channel (CCh) Examples...........23 1. Introduction This document specifies the requirements for the management of equipment used in networks supporting an MPLS Transport Profile (MPLS-TP). The requirements are defined for specification of network management aspects of protocol mechanisms and procedures that constitute the building blocks out of which the MPLS transport profile is constructed. That is, these requirements indicate what management capabilities need to be available in MPLS for use in managing the MPLS-TP. This document is intended @@ -976,21 +976,21 @@ 1. The CCh may be provided by a link in a physically distinct network. That is, a link that is not part of the transport network that is being managed. For example, the nodes in the transport network may be interconnected in two distinct physical networks: the transport network and the DCN. This is a "physically distinct out-of-band CCh". 2. The CCh may be provided by a link in the transport network - that is terminated at the ends of the DCC and which is capable + that is terminated at the ends of the CCh and which is capable of encapsulating and terminating packets of the management protocols. For example, in MPLS-TP a single-hop LSP might be established between two adjacent nodes, and that LSP might be capable of carrying IP traffic. Management traffic can then be inserted into the link in an LSP parallel to the LSPs that carry user traffic. This is a "physically shared out-of-band CCh." 3. The CCh may be supported as its native protocol on the @@ -1008,21 +1008,21 @@ bytes does not reduce the capacity of the associated data channel. This is an "overhead-based CCh". This alternative is not available in MPLS-TP because there is no overhead available. 5. The CCh may provided by a dedicated channel associated with the data link. For example, the generic associated label (GAL) - [13] may be used to label DCC traffic being exchanged on a data + [13] may be used to label CCh traffic being exchanged on a data link between adjacent transport nodes, potentially in the absence of any data LSP between those nodes. This is a "data link associated CCh". It is very similar to case 2, and by its nature can only span a single hop in the transport network. 6. The CCh may be provided by a dedicated channel associated with a data channel. For example, in MPLS-TP the GAL [13] may be