< draft-ietf-ippm-stamp-06.txt		draft-ietf-ippm-stamp-07.txt >
	Network Working Group G. Mirsky		Network Working Group G. Mirsky
	Internet-Draft ZTE Corp.		Internet-Draft ZTE Corp.
	Intended status: Standards Track G. Jun		Intended status: Standards Track G. Jun
	Expires: October 25, 2019 ZTE Corporation		Expires: January 7, 2020 ZTE Corporation
	H. Nydell		H. Nydell
	Accedian Networks		Accedian Networks
	R. Foote		R. Foote
	Nokia		Nokia
	April 23, 2019		July 6, 2019
	Simple Two-way Active Measurement Protocol		Simple Two-way Active Measurement Protocol
	draft-ietf-ippm-stamp-06		draft-ietf-ippm-stamp-07
	Abstract		Abstract
	This document describes a Simple Two-way Active Measurement Protocol		This document describes a Simple Two-way Active Measurement Protocol
	which enables the measurement of both one-way and round-trip		which enables the measurement of both one-way and round-trip
	performance metrics like delay, delay variation, and packet loss.		performance metrics like delay, delay variation, and packet loss.
	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
	skipping to change at page 1, line 37 ¶		skipping to change at page 1, line 37 ¶
	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 https://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 October 25, 2019.		This Internet-Draft will expire on January 7, 2020.
	Copyright Notice		Copyright Notice
	Copyright (c) 2019 IETF Trust and the persons identified as the		Copyright (c) 2019 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
	(https://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
	skipping to change at page 2, line 49 ¶		skipping to change at page 2, line 49 ¶
	exist, have been deployed and provide important operational		exist, have been deployed and provide important operational
	performance measurements. At the same time, there has been		performance measurements. At the same time, there has been
	noticeable interest in using a simpler mechanism for active		noticeable interest in using a simpler mechanism for active
	performance monitoring that can provide deterministic behavior and		performance monitoring that can provide deterministic behavior and
	inherit separation of control (vendor-specific configuration or		inherit separation of control (vendor-specific configuration or
	orchestration) and test functions. One of such is Performance		orchestration) and test functions. One of such is Performance
	Measurement from IP Edge to Customer Equipment using TWAMP Light from		Measurement from IP Edge to Customer Equipment using TWAMP Light from
	Broadband Forum [BBF.TR-390] used as the reference TWAMP Light that,		Broadband Forum [BBF.TR-390] used as the reference TWAMP Light that,
	according to [RFC8545], includes sub-set of TWAMP-Test functions in		according to [RFC8545], includes sub-set of TWAMP-Test functions in
	combination with other applications that provide, for example,		combination with other applications that provide, for example,
	control and security. This document defines active performance		control and security. This document defines an active performance
	measurement test protocol, Simple Two-way Active Measurement Protocol		measurement test protocol, Simple Two-way Active Measurement Protocol
	(STAMP), that enables measurement of both one-way and round-trip		(STAMP), that enables measurement of both one-way and round-trip
	performance metrics like delay, delay variation, and packet loss.		performance metrics like delay, delay variation, and packet loss.
	2. Conventions used in this document		2. Conventions used in this document
	2.1. Terminology		2.1. Terminology
	AES Advanced Encryption Standard		AES Advanced Encryption Standard
	skipping to change at page 4, line 20 ¶		skipping to change at page 4, line 20 ¶
	|| ||		|| ||
	|| ||		|| ||
	+----------------------+ +-------------------------+		+----------------------+ +-------------------------+
	| STAMP Session-Sender | <--- STAMP---> | STAMP Session-Reflector |		| STAMP Session-Sender | <--- STAMP---> | STAMP Session-Reflector |
	+----------------------+ +-------------------------+		+----------------------+ +-------------------------+
	Figure 1: STAMP Reference Model		Figure 1: STAMP Reference Model
	4. Theory of Operation		4. Theory of Operation
	STAMP Session-Sender transmits test packets toward STAMP Session-		STAMP Session-Sender transmits test packets over UDP transport toward
	Reflector. STAMP Session-Reflector receives Session-Sender's packet		STAMP Session-Reflector. STAMP Session-Reflector receives Session-
	and acts according to the configuration and optional control		Sender's packet and acts according to the configuration and optional
	information communicated in the Session-Sender's test packet. STAMP		control information communicated in the Session-Sender's test packet.
	defines two different test packet formats, one for packets		STAMP defines two different test packet formats, one for packets
	transmitted by the STAMP-Session-Sender and one for packets		transmitted by the STAMP-Session-Sender and one for packets
	transmitted by the STAMP-Session-Reflector. STAMP supports two		transmitted by the STAMP-Session-Reflector. STAMP supports two
	modes: unauthenticated and authenticated. Unauthenticated STAMP test		modes: unauthenticated and authenticated. Unauthenticated STAMP test
	packets, defined in Section 4.1.1 and Section 4.2.1, ensure		packets, defined in Section 4.1.1 and Section 4.2.1, ensure
	interworking between STAMP and TWAMP Light as described in		interworking between STAMP and TWAMP Light as described in
	Section 4.4 packet formats.		Section 4.4 packet formats.
	By default, STAMP uses symmetrical packets, i.e., size of the packet		By default, STAMP uses symmetrical packets, i.e., size of the packet
	transmitted by Session-Reflector equals the size of the packet		transmitted by Session-Reflector equals the size of the packet
	received by the Session-Reflector.		received by the Session-Reflector.
	skipping to change at page 12, line 27 ¶		skipping to change at page 12, line 27 ¶
	known UDP port number allocated for the OWAMP-Test/TWAMP-Test		known UDP port number allocated for the OWAMP-Test/TWAMP-Test
	Receiver port, the security considerations and measures to mitigate		Receiver port, the security considerations and measures to mitigate
	the risk of the attack using the registered port number documented in		the risk of the attack using the registered port number documented in
	Section 6 [RFC8545] equally apply to STAMP. Because of the control		Section 6 [RFC8545] equally apply to STAMP. Because of the control
	and management of a STAMP test being outside the scope of this		and management of a STAMP test being outside the scope of this
	specification only the more general requirement is set:		specification only the more general requirement is set:
	To mitigate the possible attack vector, the control and management		To mitigate the possible attack vector, the control and management
	of a STAMP test session MUST use the secured transport.		of a STAMP test session MUST use the secured transport.
			Load of STAMP test packets offered to a network MUST be carefully
			estimated, and the possible impact on the existing services MUST
			be thoroughly analyzed before launching the test session.
	Use of HMAC-SHA-256 in the authenticated mode protects the data		Use of HMAC-SHA-256 in the authenticated mode protects the data
	integrity of the STAMP test packets.		integrity of the STAMP test packets.
	7. Acknowledgments		7. Acknowledgments
	Authors express their appreciation to Jose Ignacio Alvarez-Hamelin		Authors express their appreciation to Jose Ignacio Alvarez-Hamelin
	and Brian Weis for their great insights into the security and		and Brian Weis for their great insights into the security and
	identity protection, and the most helpful and practical suggestions.		identity protection, and the most helpful and practical suggestions.
	Also, our sincere thanks to David Ball for his thorough review and		Also, our sincere thanks to David Ball for his thorough review and
	helpful comments.		helpful comments.
End of changes. 7 change blocks.
	10 lines changed or deleted		14 lines changed or added
This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/