Network Working Group L. Zheng Internet-Draft Huawei Technologies Intended status: Standards Track S. Aldrin Expires: January 3, 2016 Google G. Zheng Huawei Technologies G. Mirsky Ericsson R. Rahman Cisco Systems July 2, 2015 Yang Data Model for LSP-PING draft-zheng-mpls-lsp-ping-yang-cfg-01.txt Abstract When an LSP fails to deliver user traffic, the failure cannot always be detected by the MPLS control plane. RFC4379 defines a mechanism that would enable users to detect such failure and to isolate faults. YANG [RFC6020] is a data definition language that was introduced to define the contents of a conceptual data store that allows networked devices to be managed using NETCONF RFC[6241]. This document defines a YANG data model that can be used to configure and manage LSP-Ping. Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on January 3, 2016. Zheng, et al. Expires January 3, 2016 [Page 1] Internet-Draft LSP-Ping Yang July 2015 Copyright Notice Copyright (c) 2015 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Support of Long Running Command with NETCONF . . . . . . 3 1.2. Contributors . . . . . . . . . . . . . . . . . . . . . . 3 2. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Design of the Data Model . . . . . . . . . . . . . . . . . . 4 3.1. Configuration of Control Information . . . . . . . . . . 4 3.2. Configuration of Schedule Parameters . . . . . . . . . . 5 3.3. Display of Result Information . . . . . . . . . . . . . . 6 4. Data Hierarchy . . . . . . . . . . . . . . . . . . . . . . . 7 5. Interaction with other MPLS OAM Tools Models . . . . . . . . 10 6. LSP-Ping Yang Module . . . . . . . . . . . . . . . . . . . . 10 7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 20 7.1. Configuration of Control Information . . . . . . . . . . 20 7.2. Configuration of Schedule Parameters . . . . . . . . . . 21 7.3. Display of Result Information . . . . . . . . . . . . . . 21 8. Security Considerations . . . . . . . . . . . . . . . . . . . 23 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 23 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 23 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 24 11.1. Normative References . . . . . . . . . . . . . . . . . . 24 11.2. Informative References . . . . . . . . . . . . . . . . . 24 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 25 1. Introduction When an LSP fails to deliver user traffic, the failure cannot always be detected by the MPLS control plane. [RFC4379] defines a mechanism that would enable users to detect such failure and to isolate faults. YANG [RFC6020] is a data definition language that was introduced to define the contents of a conceptual data store that allows networked devices to be managed using NETCONF [RFC6241]. This document defines Zheng, et al. Expires January 3, 2016 [Page 2] Internet-Draft LSP-Ping Yang July 2015 a YANG data model that can be used to configure and manage LSP-Ping [RFC4379]. The rest of this document is organized as follows. Section 2 presents the scope of this document. Section 3 provides the design of the LSP-Ping configuration data model in details by containers. Section 4 presents the complete data hierarchy of LSP-Ping YANG model. Section 5 discusses the interaction between LSP-Ping data model and other MPLS tools data models. Section 6 specifies the YANG module and section 7 lists examples which conform to the YANG module specified in this document. Finally, security considerations are discussed in Section 8. 1.1. Support of Long Running Command with NETCONF LSP Ping is one of examples of what can described as "long-running operation". Unlike most of configuration operations that result in single response execution of an LSP Ping triggers multiple responses from a node under control. The question of implementing long-running operation in NETCONF is still open and possible solutions being discussed: 1. Consecutive Remote Processing Calls (RPC) to poll for results; 2. Model presented in[RFC4560] ; 3. The one outlined in [I-D.mahesh-netconf-persistent]. The problem of long-running operation as well can be considered as a case of controlling and obtaining results from a Measurement Agent (MA) as defined in [I-D.ietf-lmap-framework]. 1.2. Contributors Yanfeng Zhang (Huawei Technologies) contributed to the definition of the YANG module in Section 6. 2. Scope The fundamental mechanism of LSP-Ping is defined in [RFC4379]. Extensions of LSP-Ping has been developed over the years. There are for example extensions for performing LSP ping over P2MP MPLS LSPs [RFC6425] and trace-route over MPLS tunnels [RFC6424] etc. These extensions will be considered in update of this document. Zheng, et al. Expires January 3, 2016 [Page 3] Internet-Draft LSP-Ping Yang July 2015 3. Design of the Data Model This YANG data model is defined to be used to configure and manage LSP-Ping and it provides the following features: 1. Configuration of control information of a LSP-Ping test; 2. Configuration of schedule parameters of a LSP-Ping test; 3. Display of result information of a LSP-Ping test. The top level container lsp-pings holds the configuration of control information, schedule parameters and result information for multi instances of LSP-Ping test. 3.1. Configuration of Control Information Container lsp-pings:lsp-ping:control-info defines the configuration parameters which control a LSP-Ping test. Examples are the target- fec-type/target-fec of the echo request packet and the reply mode of the echo reply packet. Values of some parameters may be auto- assigned by the system, but in several cases there is a requirement for configuration of these parameters. Examples of such parameters are source address and outgoing interface. The data hierarchy for control information configuration is presented below: Zheng, et al. Expires January 3, 2016 [Page 4] Internet-Draft LSP-Ping Yang July 2015 module: ietf-lspping +--rw lsp-pings +--rw lsp-ping* [lsp-ping-name] +--rw lsp-ping-name string +--rw control-info | +--rw target-fec-type? target-fec-type | +--rw (target-fec)? | | +--:(ip-prefix) | | | +--rw ip-address? inet:ip-address | | +--:(bgp) | | | +--rw bgp? inet:ip-address | | +--:(tunnel) | | | +--rw tunnel-interface? uint32 | | +--:(l3vpn) | | | +--rw l3vpn-id? uint32 | | | +--rw l3vpn-ip-address? inet:ip-address | | +--:(pwe3) | | | +--rw vc? uint32 | | +--:(vpls) | | +--rw vpls? string | +--rw reply-mode? reply-mode | +--rw timeout? uint32 | +--rw timeout-units? units | +--rw interval? uint32 | +--rw interval-units? units | +--rw probe-count? uint32 | +--rw data-size? uint32 | +--rw data-fill? string | +--rw description? string | +--rw source-address-type? inet:ip-version | +--rw source-address? inet:ip-address | +--rw ttl? uint32 | +--rw (outbound)? | +--:(interface) | | +--rw interface-name? string | +--:(nexthop) | +--rw nexthop? inet:ip-address 3.2. Configuration of Schedule Parameters Container lsp-pings:lsp-ping:schedule-parameters defines the schedule parameters of a LSP-Ping test, which basically describes when to start and when to end the test. Four start modes and three end modes are defined respectively. To be noted that, the configuration of "interval" and "probe-count" parameter defined in container lsp- pings:lsp-ping:control-info could also determine when the test ends implicitly. All these three parameters are optional. If "interval" Zheng, et al. Expires January 3, 2016 [Page 5] Internet-Draft LSP-Ping Yang July 2015 and "probe-count" are not configured by the user, the default values will be used by the system. If "end-test" is configured by the user, the actual end time of the LSP-Ping test is the smaller one between the configuration value of "end-test" and the time implicitly determined by the configuration value of "interval"/"probe-count". The data hierarchy for schedule information configuration is presented below: module: ietf-lspping +--rw lsp-pings +--rw lsp-ping* [lsp-ping-name] +--rw lsp-ping-name string +--rw control-info ... +--rw schedule-parameters | +--rw (start-test)? | | +--:(now) | | | +--rw start-test-now? empty | | +--:(at) | | | +--rw start-test-at? yang:date-and-time | | +--:(delay) | | | +--rw start-test-delay? uint32 | | | +--rw start-test-delay-units? units | | +--:(daily) | | +--rw start-test-daily? yang:date-and-time | +--rw (end-test)? | +--:(at) | | +--rw end-test-at? yang:date-and-time | +--:(delay) | | +--rw end-test-delay? uint32 | | +--rw end-test-delay-units? units | +--:(lifetime) | +--rw end-test-lifetime? uint32 | +--rw lifetime-units? units 3.3. Display of Result Information Container lsp-pings:lsp-ping:result-info shows the result of the current LSP-Ping test. Both the statistical result e.g. min-rtt, max rtt, and per test probe result e.g. return code, return subcode, are shown. The data hierarchy for display of result information is presented below: Zheng, et al. Expires January 3, 2016 [Page 6] Internet-Draft LSP-Ping Yang July 2015 module: ietf-lspping +--rw lsp-pings +--rw lsp-ping* [lsp-ping-name] +--rw lsp-ping-name string +--rw control-info ... +--rw schedule-parameters ... +--ro result-info +--ro operational-status? operational-status +--ro source-address-type? inet:ip-version +--ro source-address? inet:ip-address +--ro target-fec-type? target-fec-type +--ro (target-fec)? | +--:(ip-prefix) | | +--ro ip-address? inet:ip-address | +--:(bgp) | | +--ro bgp? inet:ip-address | +--:(tunnel) | | +--ro tunnel-interface? uint32 | +--:(l3vpn) | | +--ro l3vpn-id? uint32 | | +--ro l3vpn-ip-address? inet:ip-address | +--:(pwe3) | | +--ro vc? uint32 | +--:(vpls) | +--ro vpls? string +--ro min-rtt? uint32 +--ro max-rtt? uint32 +--ro average-rtt? uint32 +--ro probe-responses? uint32 +--ro sent-probes? uint32 +--ro sum-of-squares? uint32 +--ro last-good-probe? yang:date-and-time +--ro probe-results +--ro probe-result* [probe-index] +--ro probe-index uint32 +--ro return-code? uint8 +--ro return-sub-code? uint8 +--ro rtt? uint32 +--ro result-type? result-type 4. Data Hierarchy The complete data hierarchy of LSP-Ping YANG model is presented below. Zheng, et al. Expires January 3, 2016 [Page 7] Internet-Draft LSP-Ping Yang July 2015 module: ietf-lspping +--rw lsp-pings +--rw lsp-ping* [lsp-ping-name] +--rw lsp-ping-name string +--rw control-info | +--rw target-fec-type? target-fec-type | +--rw (target-fec)? | | +--:(ip-prefix) | | | +--rw ip-address? inet:ip-address | | +--:(bgp) | | | +--rw bgp? inet:ip-address | | +--:(tunnel) | | | +--rw tunnel-interface? uint32 | | +--:(l3vpn) | | | +--rw l3vpn-id? uint32 | | | +--rw l3vpn-ip-address? inet:ip-address | | +--:(pwe3) | | | +--rw vc? uint32 | | +--:(vpls) | | +--rw vpls? string | +--rw reply-mode? reply-mode | +--rw timeout? uint32 | +--rw timeout-units? units | +--rw interval? uint32 | +--rw interval-units? units | +--rw probe-count? uint32 | +--rw data-size? uint32 | +--rw data-fill? string | +--rw description? string | +--rw source-address-type? inet:ip-version | +--rw source-address? inet:ip-address | +--rw ttl? uint32 | +--rw (outbound)? | +--:(interface) | | +--rw interface-name? string | +--:(nexthop) | +--rw nexthop? inet:ip-address +--rw schedule-parameters | +--rw (start-test)? | | +--:(now) | | | +--rw start-test-now? empty | | +--:(at) | | | +--rw start-test-at? yang:date-and-time | | +--:(delay) | | | +--rw start-test-delay? uint32 | | | +--rw start-test-delay-units? units | | +--:(daily) | | +--rw start-test-daily? yang:date-and-time Zheng, et al. Expires January 3, 2016 [Page 8] Internet-Draft LSP-Ping Yang July 2015 | +--rw (end-test)? | +--:(at) | | +--rw end-test-at? yang:date-and-time | +--:(delay) | | +--rw end-test-delay? uint32 | | +--rw end-test-delay-units? units | +--:(lifetime) | +--rw end-test-lifetime? uint32 | +--rw lifetime-units? units +--ro result-info +--ro operational-status? operational-status +--ro source-address-type? inet:ip-version +--ro source-address? inet:ip-address +--ro target-fec-type? target-fec-type +--ro (target-fec)? | +--:(ip-prefix) | | +--ro ip-address? inet:ip-address | +--:(bgp) | | +--ro bgp? inet:ip-address | +--:(tunnel) | | +--ro tunnel-interface? uint32 | +--:(l3vpn) | | +--ro l3vpn-id? uint32 | | +--ro l3vpn-ip-address? inet:ip-address | +--:(pwe3) | | +--ro vc? uint32 | +--:(vpls) | +--ro vpls? string +--ro min-rtt? uint32 +--ro max-rtt? uint32 +--ro average-rtt? uint32 +--ro probe-responses? uint32 +--ro sent-probes? uint32 +--ro sum-of-squares? uint32 +--ro last-good-probe? yang:date-and-time +--ro probe-results +--ro probe-result* [probe-index] +--ro probe-index uint32 +--ro return-code? uint8 +--ro return-sub-code? uint8 +--ro rtt? uint32 +--ro result-type? result-type Zheng, et al. Expires January 3, 2016 [Page 9] Internet-Draft LSP-Ping Yang July 2015 5. Interaction with other MPLS OAM Tools Models TBA 6. LSP-Ping Yang Module file "ietf-lspping@2015-07-02.yang" module ietf-lspping { namespace "urn:ietf:params:xml:ns:yang:ietf-lspping"; //namespace need to be assigned by IANA prefix "lspping"; import ietf-inet-types { prefix inet; } import ietf-yang-types{ prefix yang; } organization "IETF Multiprotocl Label Switching Working Group"; contact "draft-zheng-mpls-lsp-ping-yang-cfg"; description "MPLS LSP-PING Yang Module"; revision "2015-07-02" { description "01 version, as per RFC4379"; reference "draft-zheng-mpls-lsp-ping-yang-cfg"; } typedef target-fec-type { type enumeration { enum ip-prefix { value "0"; description "IPv4/IPv6 LSP's destination"; } enum bgp { value "1"; description "BGP IPv4/IPv6 LSP's destination"; } enum tunnel { value "2"; description "Tunnel interface"; } enum l3vpn { value "3"; description "L3VPN instance and remote address"; } enum pwe3 { value "4"; description "PWE3"; Zheng, et al. Expires January 3, 2016 [Page 10] Internet-Draft LSP-Ping Yang July 2015 } enum vpls { value "5"; description "VPLS"; } } description "Target FEC type."; } typedef reply-mode { type enumeration { enum do-not-reply { value "1"; description "Do not reply"; } enum reply-via-udp { value "2"; description "Reply via an IPv4/IPv6 UDP packet"; } enum reply-via-udp-router-alert { value "3"; description "Reply via an IPv4/IPv6 UDP packet with Router Alert"; } enum reply-via-control-channel { value "4"; description "Reply via application level control channel"; } } description "Reply mode."; } typedef units { type enumeration { enum seconds { description "Seconds"; } enum milliseconds { description "Milliseconds"; } enum microseconds { description "Microseconds"; } enum nanoseconds { description "Nanoseconds"; } } Zheng, et al. Expires January 3, 2016 [Page 11] Internet-Draft LSP-Ping Yang July 2015 description "Time units"; } typedef operational-status { type enumeration { enum enabled { value "1"; description "The Test is active."; } enum disabled { value "2"; description "The test has stopped."; } enum completed { value "3"; description "The test is completed."; } } description "Operational state of a LSP Ping test."; } typedef result-type { type enumeration { enum success { value "1"; description "The test probe is successed."; } enum fail { value "2"; description "The test probe has failed."; } enum timeout { value "3"; description "The test probe is timeout."; } } description "Result of each LSP Ping test probe."; } container lsp-pings { description "Multi instance of LSP Ping test."; list lsp-ping { key "lsp-ping-name"; description "LSP Ping test"; leaf lsp-ping-name { type string { length "1..31"; } Zheng, et al. Expires January 3, 2016 [Page 12] Internet-Draft LSP-Ping Yang July 2015 mandatory "true"; description "LSP Ping test name."; } container control-info { description "Control information of the LSP Ping test."; leaf target-fec-type { type target-fec-type; description "Specifies the address type of Target FEC."; } choice target-fec { case ip-prefix { leaf ip-address { type inet:ip-address; description "IPv4/IPv6 Prefix."; } } case bgp { leaf bgp { type inet:ip-address; description "BGP IPv4/IPv6 Prefix."; } } case tunnel { leaf tunnel-interface { type uint32; description "Tunnel interface"; } } case l3vpn { leaf l3vpn-id{ type uint32; description "Layer3 VPN ID."; } leaf l3vpn-ip-address { type inet:ip-address; description "Layer3 VPN IPv4 Prefix."; } } case pwe3 { leaf vc { type uint32; description "VC"; } } case vpls { leaf vpls { type string; description "VPLS"; Zheng, et al. Expires January 3, 2016 [Page 13] Internet-Draft LSP-Ping Yang July 2015 } } description "Specifies the address of Target FEC"; } leaf reply-mode { type reply-mode; description "Specifies the reply mode."; } leaf timeout { type uint32; description "Specifies the time-out value for a LSP Ping operation."; } leaf timeout-units { type units; description "Time-out units."; } leaf interval { type uint32; default 1; description "Specifies the interval to send a LSP Ping echo request packet(probe) as part of one LSP Ping test."; } leaf interval-units { type units; default seconds; description "Interval units."; } leaf probe-count { type uint32; default 5; description "Specifies the number of probe sent of one LSP Ping test."; } leaf data-size { type uint32; description "Specifies the size of the data portion to be transmitted in a LSP Ping operation, in octets."; } leaf data-fill { type string{ length "0..1564"; } description "Used together with the corresponding data-size value to determine how to fill the data portion of a probe packet."; } leaf description { Zheng, et al. Expires January 3, 2016 [Page 14] Internet-Draft LSP-Ping Yang July 2015 type string{ length "1..31"; } description "A descriptive name of the LSP Ping test."; } leaf source-address-type { type inet:ip-version; description "Specifies the type of the source address."; } leaf source-address { type inet:ip-address; description "Specifies the source address."; } leaf ttl { type uint32; default 255; description "Time to live."; } choice outbound { case interface { leaf interface-name{ type string{ length "1..255"; } description "Specifies the outgoing interface."; } } case nexthop{ leaf nexthop { type inet:ip-address; description "Specifies the nexthop."; } } description "Specifies the out interface or nexthop"; } } container schedule-parameters { description "LSP Ping test schedule parameter"; choice start-test{ case now { leaf start-test-now { type empty; description "Start test now."; } } case at { leaf start-test-at { Zheng, et al. Expires January 3, 2016 [Page 15] Internet-Draft LSP-Ping Yang July 2015 type yang:date-and-time; description "Start test at a specific time."; } } case delay { leaf start-test-delay { type uint32; description "Start after a specific delay."; } leaf start-test-delay-units { type units; default seconds; description "Delay units."; } } case daily { leaf start-test-daily { type yang:date-and-time; description "Start test daily."; } } description "Specifies when the test begins to start, include 4 schedule method: start now(1), start at(2), start delay(3), start daily(4)."; } choice end-test{ case at { leaf end-test-at{ type yang:date-and-time; description "End test at a specific time."; } } case delay { leaf end-test-delay { type uint32; description "End after a specific delay."; } leaf end-test-delay-units { type units; default seconds; description "Delay units."; } } case lifetime { leaf end-test-lifetime { type uint32; description "Set the test lifetime."; Zheng, et al. Expires January 3, 2016 [Page 16] Internet-Draft LSP-Ping Yang July 2015 } leaf lifetime-units { type units; default seconds; description "Lifetime units."; } } description "Specifies when the test ends, include 3 schedule method: end at(1), end delay(2), end lifetime(3)."; } } container result-info { config "false"; description "LSP Ping test result information."; leaf operational-status { type operational-status; description "Operational state of a LSP Ping test"; } leaf source-address-type { type inet:ip-version; description "The source address type."; } leaf source-address { type inet:ip-address; description "The source address of the test."; } leaf target-fec-type { type target-fec-type; description "The Target FEC address type."; } choice target-fec { case ip-prefix { leaf ip-address { type inet:ip-address; description "IPv4/IPv6 Prefix."; } } case bgp { leaf bgp { type inet:ip-address; description "BGP IPv4/IPv6 Prefix."; } } case tunnel { leaf tunnel-interface { type uint32; Zheng, et al. Expires January 3, 2016 [Page 17] Internet-Draft LSP-Ping Yang July 2015 description "Tunnel interface"; } } case l3vpn { leaf l3vpn-id{ type uint32; description "Layer3 VPN ID."; } leaf l3vpn-ip-address { type inet:ip-address; description "Layer3 VPN IPv4 Prefix."; } } case pwe3 { leaf vc { type uint32; description "VC"; } } case vpls { leaf vpls { type string; description "VPLS"; } } description "The Target FEC address"; } leaf min-rtt { type uint32; description "The minimum LSP Ping round-trip-time (RTT) received."; } leaf max-rtt { type uint32; description "The maximum LSP Ping round-trip-time (RTT) received."; } leaf average-rtt { type uint32; description "The current average LSP Ping round-trip-time (RTT)."; } leaf probe-responses { type uint32; description "Number of responses received for the corresponding LSP Ping test."; } leaf sent-probes { Zheng, et al. Expires January 3, 2016 [Page 18] Internet-Draft LSP-Ping Yang July 2015 type uint32; description "Number of probes sent for the corresponding LSP Ping test."; } leaf sum-of-squares { type uint32; description "The sum of the squares for all replys received."; } leaf last-good-probe { type yang:date-and-time; description "Date and time when the last response was received for a probe."; } container probe-results { description "Result info of test probes."; list probe-result { key "probe-index"; description "Result info of each test probe."; leaf probe-index { type uint32; description "Probe index"; } leaf return-code { type uint8; description "The Return Code set in the echo reply."; } leaf return-sub-code { type uint8; description "The Return Sub-code set in the echo reply."; } leaf rtt { type uint32; description "The round-trip-time (RTT) received."; } leaf result-type { type result-type; description "The probe result type."; } } } } } } } Zheng, et al. Expires January 3, 2016 [Page 19] Internet-Draft LSP-Ping Yang July 2015 7. Examples The following examples shows the netconf RPC communication between client and server for one LSP-Ping test case. 7.1. Configuration of Control Information Configure the control-info for sample-test-case. Request from netconf client: sample-test-case ip-prefix 112.80.248.74 reply-via-udp 1 seconds 1 seconds 6 enabled 64 this is a lsp ping test ipv4 112.90.83.122 56 Reply from netconf server: Zheng, et al. Expires January 3, 2016 [Page 20] Internet-Draft LSP-Ping Yang July 2015 7.2. Configuration of Schedule Parameters Set the schedule-parameters for sample-test-case to start the test. Request from netconf client: sample-test-case Reply from netconf server: 7.3. Display of Result Information Get the result-info of sample-test-case. Request from netconf client: sample-test-case Reply from netconf server: Zheng, et al. Expires January 3, 2016 [Page 21] Internet-Draft LSP-Ping Yang July 2015 sample-test-case completed ipv4 112.90.83.122 ip-prefix 112.80.248.74 10 56 36 6 6 8882 2015-07-01T10:36:56 0 0 3 10 success 1 0 3 56 success 2 0 3 35 success 3 0 3 38 success 4 Zheng, et al. Expires January 3, 2016 [Page 22] Internet-Draft LSP-Ping Yang July 2015 0 3 36 success 5 0 3 41 success 8. Security Considerations The configuration and state data defined in this document is designed to be accessed via the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the secure transport layer and the mandatory-to- implement secure transport is SSH [RFC6242]. The authors recommend to implement the NETCONF access control model [RFC6536] to restrict access for particular NETCONF users to a pre-configured subset of all available NETCONF protocol operations and content. There are a number of config true nodes defined in the YANG module which are writable/creatable/deletable. These data nodes may be considered sensitive or vulnerable in some network environments. Write operations to these data nodes without proper protection can have a negative effect on network operations. 9. IANA Considerations The IANA is requested to as assign a new namespace URI from the IETF XML registry. URI:TBA 10. Acknowledgements We would also like to thank XXX. Zheng, et al. Expires January 3, 2016 [Page 23] Internet-Draft LSP-Ping Yang July 2015 11. References 11.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures", RFC 4379, February 2006. [RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", RFC 6020, October 2010. 11.2. Informative References [I-D.ietf-lmap-framework] Eardley, P., Morton, A., Bagnulo, M., Burbridge, T., Aitken, P., and A. Akhter, "A framework for Large-Scale Measurement of Broadband Performance (LMAP)", draft-ietf- lmap-framework-14 (work in progress), April 2015. [I-D.mahesh-netconf-persistent] Jethanandani, M., "NETCONF and persistent responses", draft-mahesh-netconf-persistent-00 (work in progress), October 2014. [RFC4560] Quittek, J. and K. White, "Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations", RFC 4560, June 2006. [RFC6241] Enns, R., Bjorklund, M., Schoenwaelder, J., and A. Bierman, "Network Configuration Protocol (NETCONF)", RFC 6241, June 2011. [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure Shell (SSH)", RFC 6242, June 2011. [RFC6424] Bahadur, N., Kompella, K., and G. Swallow, "Mechanism for Performing Label Switched Path Ping (LSP Ping) over MPLS Tunnels", RFC 6424, November 2011. [RFC6425] Saxena, S., Swallow, G., Ali, Z., Farrel, A., Yasukawa, S., and T. Nadeau, "Detecting Data-Plane Failures in Point-to-Multipoint MPLS - Extensions to LSP Ping", RFC 6425, November 2011. Zheng, et al. Expires January 3, 2016 [Page 24] Internet-Draft LSP-Ping Yang July 2015 [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration Protocol (NETCONF) Access Control Model", RFC 6536, March 2012. Authors' Addresses Lianshu Zheng Huawei Technologies China Email: vero.zheng@huawei.com Sam K. Aldrin Google USA Email: aldrin.ietf@gmail.com Guangying Zheng Huawei Technologies China Email: zhengguangying@huawei.com Greg Mirsky Ericsson USA Email: gregory.mirsky@ericsson.com Reshad Rahman Cisco Systems Canada Email: rrahman@cisco.com Zheng, et al. Expires January 3, 2016 [Page 25]