< draft-ietf-ippm-twamp-yang-04.txt		draft-ietf-ippm-twamp-yang-05.txt >
	IPPM WG R. Civil		IPPM WG R. Civil
	Internet-Draft Ciena Corporation		Internet-Draft Ciena Corporation
	Intended status: Standards Track A. Morton		Intended status: Standards Track A. Morton
	Expires: February 23, 2018 AT&T Labs		Expires: April 21, 2018 AT&T Labs
	R. Rahman		R. Rahman
	M. Jethanandani		M. Jethanandani
	Cisco Systems		Cisco Systems
	K. Pentikousis, Ed.		K. Pentikousis, Ed.
	Travelping		Travelping
	August 22, 2017		October 18, 2017
	Two-Way Active Measurement Protocol (TWAMP) Data Model		Two-Way Active Measurement Protocol (TWAMP) Data Model
	draft-ietf-ippm-twamp-yang-04		draft-ietf-ippm-twamp-yang-05
	Abstract		Abstract
	This document specifies a data model for client and server		This document specifies a data model for client and server
	implementations of the Two-Way Active Measurement Protocol (TWAMP).		implementations of the Two-Way Active Measurement Protocol (TWAMP).
	We define the TWAMP data model through Unified Modeling Language		We define the TWAMP data model through Unified Modeling Language
	(UML) class diagrams and formally specify it using YANG.		(UML) class diagrams and formally specify it using YANG.
	Status of This Memo		Status of This Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at https://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	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."
	This Internet-Draft will expire on February 23, 2018.		This Internet-Draft will expire on April 21, 2018.
	Copyright Notice		Copyright Notice
	Copyright (c) 2017 IETF Trust and the persons identified as the		Copyright (c) 2017 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 date of		(https://trustee.ietf.org/license-info) in effect on the 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 restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
	skipping to change at page 2, line 33 ¶		skipping to change at page 2, line 33 ¶
	4.1. Control-Client . . . . . . . . . . . . . . . . . . . . . 8		4.1. Control-Client . . . . . . . . . . . . . . . . . . . . . 8
	4.2. Server . . . . . . . . . . . . . . . . . . . . . . . . . 11		4.2. Server . . . . . . . . . . . . . . . . . . . . . . . . . 11
	4.3. Session-Sender . . . . . . . . . . . . . . . . . . . . . 12		4.3. Session-Sender . . . . . . . . . . . . . . . . . . . . . 12
	4.4. Session-Reflector . . . . . . . . . . . . . . . . . . . . 13		4.4. Session-Reflector . . . . . . . . . . . . . . . . . . . . 13
	5. Data Model . . . . . . . . . . . . . . . . . . . . . . . . . 15		5. Data Model . . . . . . . . . . . . . . . . . . . . . . . . . 15
	5.1. YANG Tree Diagram . . . . . . . . . . . . . . . . . . . . 15		5.1. YANG Tree Diagram . . . . . . . . . . . . . . . . . . . . 15
	5.2. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 18		5.2. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 18
	6. Data Model Examples . . . . . . . . . . . . . . . . . . . . . 45		6. Data Model Examples . . . . . . . . . . . . . . . . . . . . . 45
	6.1. Control-Client . . . . . . . . . . . . . . . . . . . . . 45		6.1. Control-Client . . . . . . . . . . . . . . . . . . . . . 45
	6.2. Server . . . . . . . . . . . . . . . . . . . . . . . . . 47		6.2. Server . . . . . . . . . . . . . . . . . . . . . . . . . 47
	6.3. Session-Sender . . . . . . . . . . . . . . . . . . . . . 48		6.3. Session-Sender . . . . . . . . . . . . . . . . . . . . . 49
	6.4. Session-Reflector . . . . . . . . . . . . . . . . . . . . 49		6.4. Session-Reflector . . . . . . . . . . . . . . . . . . . . 50
	7. Security Considerations . . . . . . . . . . . . . . . . . . . 52		7. Security Considerations . . . . . . . . . . . . . . . . . . . 53
	8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 53		8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 54
	9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 53		9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 54
	10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 53		10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 54
	11. References . . . . . . . . . . . . . . . . . . . . . . . . . 54		11. References . . . . . . . . . . . . . . . . . . . . . . . . . 55
	11.1. Normative References . . . . . . . . . . . . . . . . . . 54		11.1. Normative References . . . . . . . . . . . . . . . . . . 55
	11.2. Informative References . . . . . . . . . . . . . . . . . 55		11.2. Informative References . . . . . . . . . . . . . . . . . 56
	Appendix A. Detailed Data Model Examples . . . . . . . . . . . . 56		Appendix A. Detailed Data Model Examples . . . . . . . . . . . . 57
	A.1. Control-Client . . . . . . . . . . . . . . . . . . . . . 56		A.1. Control-Client . . . . . . . . . . . . . . . . . . . . . 57
	A.2. Server . . . . . . . . . . . . . . . . . . . . . . . . . 58		A.2. Server . . . . . . . . . . . . . . . . . . . . . . . . . 59
	A.3. Session-Sender . . . . . . . . . . . . . . . . . . . . . 60		A.3. Session-Sender . . . . . . . . . . . . . . . . . . . . . 61
	A.4. Session-Reflector . . . . . . . . . . . . . . . . . . . . 61		A.4. Session-Reflector . . . . . . . . . . . . . . . . . . . . 62
	Appendix B. TWAMP Operational Commands . . . . . . . . . . . . . 63		Appendix B. TWAMP Operational Commands . . . . . . . . . . . . . 64
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 63		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 64
	1. Introduction		1. Introduction
	The Two-Way Active Measurement Protocol (TWAMP) [RFC5357] is used to		The Two-Way Active Measurement Protocol (TWAMP) [RFC5357] is used to
	measure network performance parameters such as latency, bandwidth,		measure network performance parameters such as latency, bandwidth,
	and packet loss by sending probe packets and measuring their		and packet loss by sending probe packets and measuring their
	experience in the network. To date, TWAMP implementations do not		experience in the network. To date, TWAMP implementations do not
	come with a standard management framework and, as such, configuration		come with a standard management framework and, as such, configuration
	depends on proprietary mechanisms developed by the corresponding		depends on proprietary mechanisms developed by the corresponding
	TWAMP vendor. This document addresses this gap by formally		TWAMP vendor. This document addresses this gap by formally
	skipping to change at page 4, line 42 ¶		skipping to change at page 4, line 42 ¶
	[Fig. 5] [Fig. 6]		[Fig. 5] [Fig. 6]
	Figure 1: Annotated TWAMP logical model		Figure 1: Annotated TWAMP logical model
	As per [RFC5357], a TWAMP implementation may follow a simplified		As per [RFC5357], a TWAMP implementation may follow a simplified
	logical model, in which the same node acts both as Control-Client and		logical model, in which the same node acts both as Control-Client and
	Session-Sender, while another node acts at the same time as TWAMP		Session-Sender, while another node acts at the same time as TWAMP
	Server and Session-Reflector. Figure 2 illustrates this simplified		Server and Session-Reflector. Figure 2 illustrates this simplified
	logical model and indicates the interaction between the TWAMP		logical model and indicates the interaction between the TWAMP
	configuration client and server using, for instance, NETCONF		configuration client and server using, for instance, NETCONF
	[RFC6241] or RESTCONF [I-D.ietf-netconf-restconf].		[RFC6241] or RESTCONF [RFC8040].
	o-------------------o o-------------------o		o-------------------o o-------------------o
	| Config client | | Config client |		| Config client | | Config client |
	o-------------------o o-------------------o		o-------------------o o-------------------o
	|| ||		|| ||
	NETCONF || RESTCONF NETCONF || RESTCONF		NETCONF || RESTCONF NETCONF || RESTCONF
	|| ||		|| ||
	o-------------------o o-------------------o		o-------------------o o-------------------o
	| Config server | | Config server |		| Config server | | Config server |
	| [Fig. 3, 5] | | [Fig. 4, 6] |		| [Fig. 3, 5] | | [Fig. 4, 6] |
	skipping to change at page 15, line 51 ¶		skipping to change at page 15, line 51 ¶
	artificial line breaks in some tree diagram nodes.		artificial line breaks in some tree diagram nodes.
	module: ietf-twamp		module: ietf-twamp
	+--rw twamp		+--rw twamp
	+--rw client! {control-client}?		+--rw client! {control-client}?
	| +--rw admin-state boolean		| +--rw admin-state boolean
	| +--rw mode-preference-chain* [priority]		| +--rw mode-preference-chain* [priority]
	| | +--rw priority uint16		| | +--rw priority uint16
	| | +--rw mode? twamp-modes		| | +--rw mode? twamp-modes
	| +--rw key-chain* [key-id]		| +--rw key-chain* [key-id]
	| | +--rw key-id binary		| | +--rw key-id string
	| | +--rw secret-key? binary		| | +--rw secret-key? binary
	| +--rw ctrl-connection* [name]		| +--rw ctrl-connection* [name]
	| +--rw name string		| +--rw name string
	| +--rw client-ip? inet:ip-address		| +--rw client-ip? inet:ip-address
	| +--rw server-ip inet:ip-address		| +--rw server-ip inet:ip-address
	| +--rw server-tcp-port? inet:port-number		| +--rw server-tcp-port? inet:port-number
	| +--rw control-packet-dscp? inet:dscp		| +--rw control-packet-dscp? inet:dscp
	| +--rw key-id? string		| +--rw key-id? string
	| +--rw max-count? uint8		| +--rw max-count? uint8
	| +--ro client-tcp-port? inet:port-number		| +--ro client-tcp-port? inet:port-number
	| +--ro server-start-time? uint64		| +--ro server-start-time? uint64
			| +--ro repeat-count? uint64
	| +--ro state? \		| +--ro state? \
	control-client-connection-state		control-client-connection-state
	| +--ro selected-mode? twamp-modes		| +--ro selected-mode? twamp-modes
	| +--ro token? binary		| +--ro token? binary
	| +--ro client-iv? binary		| +--ro client-iv? binary
	| +--rw test-session-request* [name]		| +--rw test-session-request* [name]
	| +--rw name string		| +--rw name string
	| +--rw sender-ip? inet:ip-address		| +--rw sender-ip? inet:ip-address
	| +--rw sender-udp-port? union		| +--rw sender-udp-port? union
	| +--rw reflector-ip inet:ip-address		| +--rw reflector-ip inet:ip-address
	skipping to change at page 16, line 45 ¶		skipping to change at page 16, line 46 ¶
	| +--ro sid? string		| +--ro sid? string
	+--rw server! {server}?		+--rw server! {server}?
	| +--rw admin-state boolean		| +--rw admin-state boolean
	| +--rw server-tcp-port? inet:port-number		| +--rw server-tcp-port? inet:port-number
	| +--rw servwait? uint32		| +--rw servwait? uint32
	| +--rw control-packet-dscp? inet:dscp		| +--rw control-packet-dscp? inet:dscp
	| +--rw count? uint8		| +--rw count? uint8
	| +--rw max-count? uint8		| +--rw max-count? uint8
	| +--rw modes? twamp-modes		| +--rw modes? twamp-modes
	| +--rw key-chain* [key-id]		| +--rw key-chain* [key-id]
	| | +--rw key-id binary		| | +--rw key-id string
	| | +--rw secret-key? binary		| | +--rw secret-key? binary
	| +--ro ctrl-connection* \		| +--ro ctrl-connection* \
	[client-ip client-tcp-port server-ip server-tcp-port]		[client-ip client-tcp-port server-ip server-tcp-port]
	| +--ro client-ip inet:ip-address		| +--ro client-ip inet:ip-address
	| +--ro client-tcp-port inet:port-number		| +--ro client-tcp-port inet:port-number
	| +--ro server-ip inet:ip-address		| +--ro server-ip inet:ip-address
	| +--ro server-tcp-port inet:port-number		| +--ro server-tcp-port inet:port-number
	| +--ro state? server-ctrl-connection-state		| +--ro state? server-ctrl-connection-state
	| +--ro control-packet-dscp? inet:dscp		| +--ro control-packet-dscp? inet:dscp
	| +--ro selected-mode? twamp-modes		| +--ro selected-mode? twamp-modes
	skipping to change at page 17, line 51 ¶		skipping to change at page 18, line 4 ¶
	dynamic-port-number		dynamic-port-number
	+--ro reflector-ip inet:ip-address		+--ro reflector-ip inet:ip-address
	+--ro reflector-udp-port \		+--ro reflector-udp-port \
	dynamic-port-number		dynamic-port-number
	+--ro parent-connection-client-ip? inet:ip-address		+--ro parent-connection-client-ip? inet:ip-address
	+--ro parent-connection-client-tcp-port? \		+--ro parent-connection-client-tcp-port? \
	inet:port-number		inet:port-number
	+--ro parent-connection-server-ip? inet:ip-address		+--ro parent-connection-server-ip? inet:ip-address
	+--ro parent-connection-server-tcp-port? \		+--ro parent-connection-server-tcp-port? \
	inet:port-number		inet:port-number
	+--ro test-packet-dscp? inet:dscp		+--ro test-packet-dscp? inet:dscp
	+--ro sent-packets? uint32		+--ro sent-packets? uint32
	+--ro rcv-packets? uint32		+--ro rcv-packets? uint32
	+--ro last-sent-seq? uint32		+--ro last-sent-seq? uint32
	+--ro last-rcv-seq? uint32		+--ro last-rcv-seq? uint32
	Figure 7: YANG Tree Diagram.		Figure 7: YANG Tree Diagram.
	5.2. YANG Module		5.2. YANG Module
	This section presents the YANG module for the TWAMP data model		This section presents the YANG module for the TWAMP data model
	defined in this document.		defined in this document.
	<CODE BEGINS> file "ietf-twamp@2017-02-22.yang"		<CODE BEGINS> file "ietf-twamp@2017-10-16.yang"
	module ietf-twamp {		module ietf-twamp {
	namespace		namespace
	urn:ietf:params:xml:ns:yang:ietf-twamp;		urn:ietf:params:xml:ns:yang:ietf-twamp;
	prefix		prefix
	ietf-twamp;		ietf-twamp;
	import ietf-inet-types {		import ietf-inet-types {
	prefix inet;		prefix inet;
	}		}
	skipping to change at page 18, line 46 ¶		skipping to change at page 18, line 48 ¶
	model for the Two-Way Active Measurement Protocol (TWAMP).		model for the Two-Way Active Measurement Protocol (TWAMP).
	The data model covers four TWAMP logical entities, namely,		The data model covers four TWAMP logical entities, namely,
	Control-Client, Server, Session-Sender, and Session-Reflector,		Control-Client, Server, Session-Sender, and Session-Reflector,
	as illustrated in the annotated TWAMP logical model (Fig. 1		as illustrated in the annotated TWAMP logical model (Fig. 1
	of draft-ietf-ippm-twamp-yang).		of draft-ietf-ippm-twamp-yang).
	This YANG module uses features to indicate which of the four		This YANG module uses features to indicate which of the four
	logical entities are supported by a TWAMP implementation.";		logical entities are supported by a TWAMP implementation.";
	revision 2017-02-22 {		revision 2017-10-16 {
	description		description
	"Revision appearing in draft-ietf-ippm-twamp-yang-03.		"Revision appearing in draft-ietf-ippm-twamp-yang-05.
	Covers RFC 5357, RFC 5618, RFC 5938, RFC 6038, RFC 7717, and		Covers RFC 5357, RFC 5618, RFC 5938, RFC 6038, RFC 7717, and
	draft-ietf-ippm-metric-registry";		draft-ietf-ippm-metric-registry";
	reference		reference
	draft-ietf-ippm-twamp-yang;		draft-ietf-ippm-twamp-yang;
	}		}
	/*		/*
	* Typedefs		* Typedefs
	skipping to change at page 24, line 4 ¶		skipping to change at page 24, line 6 ¶
	feature session-sender {		feature session-sender {
	description		description
	"Indicates that the device supports configuration of the		"Indicates that the device supports configuration of the
	TWAMP Session-Sender logical entity.";		TWAMP Session-Sender logical entity.";
	}		}
	feature session-reflector {		feature session-reflector {
	description		description
	"Indicates that the device supports configuration of the		"Indicates that the device supports configuration of the
	TWAMP Session-Reflector logical entity.";		TWAMP Session-Reflector logical entity.";
	}		}
	/*		/*
	* Reusable node groups		* Reusable node groups
	*/		*/
	grouping key-management {		grouping key-management {
	list key-chain {		list key-chain {
	key key-id;		key key-id;
	leaf key-id {		leaf key-id {
	type binary {		type string {
	length 1..80;		length 1..80;
	}		}
	description		description
	"KeyID used for a TWAMP-Control connection. As per		"KeyID used for a TWAMP-Control connection. As per
	Section 3.1 of RFC 4656, KeyID is 'a UTF-8 string, up to		Section 3.1 of RFC 4656, KeyID is 'a UTF-8 string, up to
	80 octets in length' and is used to select which 'shared		80 octets in length' and is used to select which 'shared
	shared secret the [Control-Client] wishes to use to		shared secret the [Control-Client] wishes to use to
	authenticate or encrypt'.";		authenticate or encrypt'.";
	}		}
	leaf secret-key {		leaf secret-key {
	skipping to change at page 25, line 28 ¶		skipping to change at page 25, line 31 ¶
	grouping count {		grouping count {
	leaf count {		leaf count {
	type uint8 {		type uint8 {
	range "10..31";		range "10..31";
	}		}
	default 10;		default 10;
	description		description
	"Parameter communicated to the Control-Client as part of the		"Parameter communicated to the Control-Client as part of the
	Server Greeting message and used for deriving a key from a		Server Greeting message and used for deriving a key from a
	shared secret as per Section 3.1 of RFC 4656: MUST be a		shared secret as per Section 3.1 of RFC 4656: MUST be a
	power of 2 and at least 1024; SHOULD be increased as more		power of 2 and at least 1024. It is configured by providing
	computing power becomes common.";		said power. For example, configuring 15 here means count
			2^15 = 32768. The default is 10, meaning 2^10 = 1024.";
	}		}
	description		description
	"Reusable data structure for count which is used both in the		"Reusable data structure for count which is used both in the
	Server container.";		Server container.";
	}		}
	grouping max-count {		grouping max-count {
	leaf max-count {		leaf max-count {
	type uint8 {		type uint8 {
	range "10..31";		range "10..31";
	skipping to change at page 35, line 27 ¶		skipping to change at page 35, line 31 ¶
	to be measured.		to be measured.
	All members of the pm-reg-list MUST have the same		All members of the pm-reg-list MUST have the same
	stream characteristics, such that they combine		stream characteristics, such that they combine
	to specify all metrics that shall be measured on		to specify all metrics that shall be measured on
	a single stream.";		a single stream.";
	reference		reference
	"ietf-ippm-metric-registry:		"ietf-ippm-metric-registry:
	Registry for Performance Metrics";		Registry for Performance Metrics";
	}		}
			leaf repeat-count {
			type uint64;
			config false;
			description
			"Indicates how many times the test session has been
			repeated. When a test is running, this value will be
			greater than 0. If the repeat parameter is non-zero,
			this value is smaller than or equal to the repeat
			parameter.";
			}
	leaf state {		leaf state {
	type test-session-state;		type test-session-state;
	config false;		config false;
	description		description
	"Indicates the TWAMP-Test session state (accepted or		"Indicates the TWAMP-Test session state (accepted or
	indication of an error); see Section 3.5 of		indication of an error); see Section 3.5 of
	RFC 5357.";		RFC 5357.";
	}		}
	leaf sid {		leaf sid {
	type string;		type string;
	skipping to change at page 54, line 12 ¶		skipping to change at page 55, line 12 ¶
	Email: vero.zheng@huawei.com		Email: vero.zheng@huawei.com
	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,		Requirement Levels", BCP 14, RFC 2119,
	DOI 10.17487/RFC2119, March 1997,		DOI 10.17487/RFC2119, March 1997,
	<http://www.rfc-editor.org/info/rfc2119>.		<https://www.rfc-editor.org/info/rfc2119>.
	[RFC3432] Raisanen, V., Grotefeld, G., and A. Morton, "Network		[RFC3432] Raisanen, V., Grotefeld, G., and A. Morton, "Network
	performance measurement with periodic streams", RFC 3432,		performance measurement with periodic streams", RFC 3432,
	DOI 10.17487/RFC3432, November 2002, <https://www.rfc-		DOI 10.17487/RFC3432, November 2002,
	editor.org/info/rfc3432>.		<https://www.rfc-editor.org/info/rfc3432>.
	[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,		[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
	DOI 10.17487/RFC3688, January 2004, <https://www.rfc-		DOI 10.17487/RFC3688, January 2004,
	editor.org/info/rfc3688>.		<https://www.rfc-editor.org/info/rfc3688>.
	[RFC4656] Shalunov, S., Teitelbaum, B., Karp, A., Boote, J., and M.		[RFC4656] Shalunov, S., Teitelbaum, B., Karp, A., Boote, J., and M.
	Zekauskas, "A One-way Active Measurement Protocol		Zekauskas, "A One-way Active Measurement Protocol
	(OWAMP)", RFC 4656, DOI 10.17487/RFC4656, September 2006,		(OWAMP)", RFC 4656, DOI 10.17487/RFC4656, September 2006,
	<https://www.rfc-editor.org/info/rfc4656>.		<https://www.rfc-editor.org/info/rfc4656>.
	[RFC5357] Hedayat, K., Krzanowski, R., Morton, A., Yum, K., and J.		[RFC5357] Hedayat, K., Krzanowski, R., Morton, A., Yum, K., and J.
	Babiarz, "A Two-Way Active Measurement Protocol (TWAMP)",		Babiarz, "A Two-Way Active Measurement Protocol (TWAMP)",
	RFC 5357, DOI 10.17487/RFC5357, October 2008,		RFC 5357, DOI 10.17487/RFC5357, October 2008,
	<https://www.rfc-editor.org/info/rfc5357>.		<https://www.rfc-editor.org/info/rfc5357>.
	[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for		[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
	the Network Configuration Protocol (NETCONF)", RFC 6020,		the Network Configuration Protocol (NETCONF)", RFC 6020,
	DOI 10.17487/RFC6020, October 2010,		DOI 10.17487/RFC6020, October 2010,
	<http://www.rfc-editor.org/info/rfc6020>.		<https://www.rfc-editor.org/info/rfc6020>.
	[RFC6038] Morton, A. and L. Ciavattone, "Two-Way Active Measurement		[RFC6038] Morton, A. and L. Ciavattone, "Two-Way Active Measurement
	Protocol (TWAMP) Reflect Octets and Symmetrical Size		Protocol (TWAMP) Reflect Octets and Symmetrical Size
	Features", RFC 6038, DOI 10.17487/RFC6038, October 2010,		Features", RFC 6038, DOI 10.17487/RFC6038, October 2010,
	<https://www.rfc-editor.org/info/rfc6038>.		<https://www.rfc-editor.org/info/rfc6038>.
	[RFC7717] Pentikousis, K., Ed., Zhang, E., and Y. Cui,		[RFC7717] Pentikousis, K., Ed., Zhang, E., and Y. Cui,
	"IKEv2-Derived Shared Secret Key for the One-Way Active		"IKEv2-Derived Shared Secret Key for the One-Way Active
	Measurement Protocol (OWAMP) and Two-Way Active		Measurement Protocol (OWAMP) and Two-Way Active
	Measurement Protocol (TWAMP)", RFC 7717,		Measurement Protocol (TWAMP)", RFC 7717,
	DOI 10.17487/RFC7717, December 2015, <https://www.rfc-		DOI 10.17487/RFC7717, December 2015,
	editor.org/info/rfc7717>.		<https://www.rfc-editor.org/info/rfc7717>.
	11.2. Informative References		11.2. Informative References
	[I-D.ietf-ippm-metric-registry]		[I-D.ietf-ippm-metric-registry]
	Bagnulo, M., Claise, B., Eardley, P., Morton, A., and A.		Bagnulo, M., Claise, B., Eardley, P., Morton, A., and A.
	Akhter, "Registry for Performance Metrics", draft-ietf-		Akhter, "Registry for Performance Metrics", draft-ietf-
	ippm-metric-registry-12 (work in progress), June 2017.		ippm-metric-registry-12 (work in progress), June 2017.
	[I-D.ietf-netconf-restconf]
	Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
	Protocol", draft-ietf-netconf-restconf-18 (work in
	progress), October 2016.
	[I-D.unify-nfvrg-challenges]		[I-D.unify-nfvrg-challenges]
	Szabo, R., Csaszar, A., Pentikousis, K., Kind, M., Daino,		Szabo, R., Csaszar, A., Pentikousis, K., Kind, M., Daino,
	D., Qiang, Z., and H. Woesner, "Unifying Carrier and Cloud		D., Qiang, Z., and H. Woesner, "Unifying Carrier and Cloud
	Networks: Problem Statement and Challenges", draft-unify-		Networks: Problem Statement and Challenges", draft-unify-
	nfvrg-challenges-04 (work in progress), July 2016.		nfvrg-challenges-04 (work in progress), July 2016.
	[I-D.unify-nfvrg-devops]		[I-D.unify-nfvrg-devops]
	Meirosu, C., Manzalini, A., Steinert, R., Marchetto, G.,		Meirosu, C., Manzalini, A., Steinert, R., Marchetto, G.,
	Pentikousis, K., Wright, S., Lynch, P., and W. John,		Pentikousis, K., Wright, S., Lynch, P., and W. John,
	"DevOps for Software-Defined Telecom Infrastructures",		"DevOps for Software-Defined Telecom Infrastructures",
	draft-unify-nfvrg-devops-06 (work in progress), July 2016.		draft-unify-nfvrg-devops-06 (work in progress), July 2016.
	[NSC] John, W., Pentikousis, K., et al., "Research directions in		[NSC] John, W., Pentikousis, K., et al., "Research directions in
	network service chaining", Proc. SDN for Future Networks		network service chaining", Proc. SDN for Future Networks
	and Services (SDN4FNS), Trento, Italy IEEE, November 2013.		and Services (SDN4FNS), Trento, Italy IEEE, November 2013.
	[RFC2898] Kaliski, B., "PKCS #5: Password-Based Cryptography		[RFC2898] Kaliski, B., "PKCS #5: Password-Based Cryptography
	Specification Version 2.0", RFC 2898,		Specification Version 2.0", RFC 2898,
	DOI 10.17487/RFC2898, September 2000, <https://www.rfc-		DOI 10.17487/RFC2898, September 2000,
	editor.org/info/rfc2898>.		<https://www.rfc-editor.org/info/rfc2898>.
	[RFC4086] Eastlake 3rd, D., Schiller, J., and S. Crocker,		[RFC4086] Eastlake 3rd, D., Schiller, J., and S. Crocker,
	"Randomness Requirements for Security", BCP 106, RFC 4086,		"Randomness Requirements for Security", BCP 106, RFC 4086,
	DOI 10.17487/RFC4086, June 2005, <https://www.rfc-		DOI 10.17487/RFC4086, June 2005,
	editor.org/info/rfc4086>.		<https://www.rfc-editor.org/info/rfc4086>.
	[RFC5618] Morton, A. and K. Hedayat, "Mixed Security Mode for the		[RFC5618] Morton, A. and K. Hedayat, "Mixed Security Mode for the
	Two-Way Active Measurement Protocol (TWAMP)", RFC 5618,		Two-Way Active Measurement Protocol (TWAMP)", RFC 5618,
	DOI 10.17487/RFC5618, August 2009, <https://www.rfc-		DOI 10.17487/RFC5618, August 2009,
	editor.org/info/rfc5618>.		<https://www.rfc-editor.org/info/rfc5618>.
	[RFC5938] Morton, A. and M. Chiba, "Individual Session Control		[RFC5938] Morton, A. and M. Chiba, "Individual Session Control
	Feature for the Two-Way Active Measurement Protocol		Feature for the Two-Way Active Measurement Protocol
	(TWAMP)", RFC 5938, DOI 10.17487/RFC5938, August 2010,		(TWAMP)", RFC 5938, DOI 10.17487/RFC5938, August 2010,
	<https://www.rfc-editor.org/info/rfc5938>.		<https://www.rfc-editor.org/info/rfc5938>.
	[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,		[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
	and A. Bierman, Ed., "Network Configuration Protocol		and A. Bierman, Ed., "Network Configuration Protocol
	(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,		(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
	<http://www.rfc-editor.org/info/rfc6241>.		<https://www.rfc-editor.org/info/rfc6241>.
	[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration		[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
	Protocol (NETCONF) Access Control Model", RFC 6536,		Protocol (NETCONF) Access Control Model", RFC 6536,
	DOI 10.17487/RFC6536, March 2012, <https://www.rfc-		DOI 10.17487/RFC6536, March 2012,
	editor.org/info/rfc6536>.		<https://www.rfc-editor.org/info/rfc6536>.
	[RFC7426] Haleplidis, E., Ed., Pentikousis, K., Ed., Denazis, S.,		[RFC7426] Haleplidis, E., Ed., Pentikousis, K., Ed., Denazis, S.,
	Hadi Salim, J., Meyer, D., and O. Koufopavlou, "Software-		Hadi Salim, J., Meyer, D., and O. Koufopavlou, "Software-
	Defined Networking (SDN): Layers and Architecture		Defined Networking (SDN): Layers and Architecture
	Terminology", RFC 7426, DOI 10.17487/RFC7426, January		Terminology", RFC 7426, DOI 10.17487/RFC7426, January
	2015, <https://www.rfc-editor.org/info/rfc7426>.		2015, <https://www.rfc-editor.org/info/rfc7426>.
			[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
			Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
			<https://www.rfc-editor.org/info/rfc8040>.
	Appendix A. Detailed Data Model Examples		Appendix A. Detailed Data Model Examples
	This appendix extends the example presented in Section 6 by		This appendix extends the example presented in Section 6 by
	configuring more fields such as authentication parameters, DSCP		configuring more fields such as authentication parameters, DSCP
	values and so on.		values and so on.
	A.1. Control-Client		A.1. Control-Client
	<?xml version="1.0" encoding="utf-8"?>		<?xml version="1.0" encoding="utf-8"?>
	<data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">		<data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
End of changes. 31 change blocks.
	54 lines changed or deleted		65 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/