draft-ietf-ippm-stamp-01.txt   draft-ietf-ippm-stamp-02.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: September 2, 2018 ZTE Corporation Expires: March 10, 2019 ZTE Corporation
H. Nydell H. Nydell
Accedian Networks Accedian Networks
R. Foote R. Foote
Nokia Nokia
March 1, 2018 September 6, 2018
Simple Two-way Active Measurement Protocol Simple Two-way Active Measurement Protocol
draft-ietf-ippm-stamp-01 draft-ietf-ippm-stamp-02
Abstract Abstract
This document describes a Simple Two-way Active Measurement Protocol This document describes a Simple Two-way Active Measurement Protocol
which enables measurement of both one-way and round-trip performance which enables measurement of both one-way and round-trip performance
metrics like delay, delay variation and packet loss. 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
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 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 September 2, 2018. This Internet-Draft will expire on March 10, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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 37 skipping to change at page 2, line 37
6. Security Considerations . . . . . . . . . . . . . . . . . . . 12 6. Security Considerations . . . . . . . . . . . . . . . . . . . 12
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
8.1. Normative References . . . . . . . . . . . . . . . . . . 13 8.1. Normative References . . . . . . . . . . . . . . . . . . 13
8.2. Informative References . . . . . . . . . . . . . . . . . 14 8.2. Informative References . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction 1. Introduction
Development and deployment of Two-Way Active Measurement Protocol Development and deployment of Two-Way Active Measurement Protocol
(TWAMP) [RFC5357] and its extensions, e.g. [RFC6038] that defined (TWAMP) [RFC5357] and its extensions, e.g., [RFC6038] that defined
features such as Reflect Octets and Symmetrical Size for TWAMP, features such as Reflect Octets and Symmetrical Size for TWAMP
provided invaluable experience. Several independent implementations provided invaluable experience. Several independent implementations
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 noticeable performance measurements. At the same time, there has been
interest in using a simpler mechanism for active performance noticeable interest in using a simpler mechanism for active
monitoring that can provide deterministic behaviour and inherit performance monitoring that can provide deterministic behavior and
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]). This document defines active Broadband Forum ([BBF.TR-390]). This document defines active
performance measurement test protocol, Simple Two-way Active performance measurement test protocol, Simple Two-way Active
Measurement Protocol (STAMP), that enables measurement of both one- Measurement Protocol (STAMP), that enables measurement of both one-
way and round-trip performance metrics like delay, delay variation way and round-trip performance metrics like delay, delay variation
and packet loss. and packet loss.
2. Conventions used in this document 2. Conventions used in this document
skipping to change at page 4, line 18 skipping to change at page 4, line 18
Reflector. STAMP Session-Reflector receives Session-Sender's packet Reflector. STAMP Session-Reflector receives Session-Sender's packet
and acts according to the configuration and optional control and acts according to the configuration and optional control
information communicated in the Session-Sender's test packet. STAMP information communicated in the Session-Sender's test packet. STAMP
defines two different test packet formats, one for packets 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 three transmitted by the STAMP-Session-Reflector. STAMP supports three
modes: unauthenticated, authenticated, and encrypted. modes: unauthenticated, authenticated, and encrypted.
Unauthenticated STAMP test packets are compatible on the wire with Unauthenticated STAMP test packets are compatible on the wire with
unauthenticated TWAMP-Test [RFC5357] packet formats. unauthenticated TWAMP-Test [RFC5357] 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 to 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.
4.1. Session-Sender Behavior and Packet Format 4.1. Session-Sender Behavior and Packet Format
4.1.1. Session-Sender Packet Format in Unauthenticated Mode 4.1.1. Session-Sender Packet Format in Unauthenticated Mode
Because STAMP supports symmetrical test packets, STAMP Session-Sender Because STAMP supports symmetrical test packets, STAMP Session-Sender
packet has minimum size of 44 octets in unauthenticated mode, see packet has a minimum size of 44 octets in unauthenticated mode, see
Figure 2, and 48 octets in authenticated or encrypted modes , see Figure 2, and 48 octets in authenticated or encrypted modes, see
Figure 4. Figure 4.
For unauthenticated mode: For unauthenticated mode:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number | | Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Timestamp | | Timestamp |
skipping to change at page 6, line 12 skipping to change at page 6, line 12
o Error Estimate is two octets long field with format displayed in o Error Estimate is two octets long field with format displayed in
Figure 3 Figure 3
0 1 0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|S|Z| Scale | Multiplier | |S|Z| Scale | Multiplier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: Error Estimate Format Figure 3: Error Estimate Format
where S, Scale and Multiplier fields are interpreted as they have where S, Scale, and Multiplier fields are interpreted as they have
been defined in section 4.1.2 [RFC4656]; and Z field - as has been been defined in section 4.1.2 [RFC4656]; and Z field - as has been
defined in section 2.3 [RFC8186]: defined in section 2.3 [RFC8186]:
* 0 - NTP 64 bit format of a timestamp; * 0 - NTP 64 bit format of a timestamp;
* 1 - PTPv2 truncated format of a timestamp. * 1 - PTPv2 truncated format of a timestamp.
The STAMP Session-Sender and Session-Reflector MAY use, not use, The STAMP Session-Sender and Session-Reflector MAY use, not use,
or set value of the Z field in accordance with the timestamp or set value of the Z field in accordance with the timestamp
format in use. This optional field is to enhance operations but format in use. This optional field is to enhance operations, but
local configuration or defaults could be used in its place. local configuration or defaults could be used in its place.
o Must-be-Zero (MBZ) field in the session-sender unauthenticated o Must-be-Zero (MBZ) field in the session-sender unauthenticated
packet is 27 octets long. It MUST be all zeroed on transmission packet is 27 octets long. It MUST be all zeroed on the
and ignored on receipt. transmission and ignored on receipt.
o Server Octets field is two octets long field. It MUST follow the o Server Octets field is two octets long field. It MUST follow the
27 octets long MBZ field. The Reflect Octets capability defined 27 octets long MBZ field. The Reflect Octets capability defined
in [RFC6038]. The value in the Server Octets field equals to the in [RFC6038]. The value in the Server Octets field equals to the
number of octets the Session-Reflector is expected to copy back to number of octets the Session-Reflector is expected to copy back to
the Session-Sender starting with the Server Octets field. Thus the Session-Sender starting with the Server Octets field. Thus
the minimal non-zero value for the Server Octets field is two and the minimal non-zero value for the Server Octets field is two.
value of one is invalid. If none of Payload to be copied the Therefore, the value of one is invalid. If none of Payload to be
value of the Server Octets field MUST be set to zero on transmit. copied, the value of the Server Octets field MUST be set to zero
on transmit.
o Remaining Packet Padding is optional field of variable length. o Remaining Packet Padding is an optional field of variable length.
The number of octets in the Remaining Packet Padding field is the The number of octets in the Remaining Packet Padding field is the
value of the Server Octets field less the length of the Server value of the Server Octets field less the length of the Server
Octets field. Octets field.
o Comp.MBZ is variable length field used to achieve alignment on o Comp.MBZ is variable length field used to achieve alignment on a
word boundary. Thus the length of Comp.MBZ field may be only 0, word boundary. Thus the length of Comp.MBZ field may be only 0,
1, 2 or 3 octets. The value of the field MUST be zeroed on 1, 2 or 3 octets. The value of the field MUST be zeroed on
transmission and ignored on receipt. transmission and ignored on receipt.
The unauthenticated STAMP Session-Sender packet MAY include Type- The unauthenticated STAMP Session-Sender packet MAY include Type-
Length-Value encodings that immediately follow the Comp. MBZ field. Length-Value encodings that immediately follow the Comp. MBZ field.
o Type field is two octets long. The value of the Type field is the o Type field is two octets long. The value of the Type field is the
codepoint allocated by IANA Section 5 that identifies data in the codepoint allocated by IANA Section 5 that identifies data in the
Value field. Value field.
o Length is two octets long field and its value is the length of the o Length is two octets long field, and its value is the length of
Value field in octets. the Value field in octets.
o Value field contains the application specific information. The o Value field contains the application specific information. The
length of the Value field MUST be four octets aligned. length of the Value field MUST be four octets aligned.
4.1.2. Session-Sender Packet Format in Authenticated and Encrypted 4.1.2. Session-Sender Packet Format in Authenticated and Encrypted
Modes Modes
For authenticated and encrypted modes: For authenticated and encrypted modes:
0 1 2 3 0 1 2 3
skipping to change at page 8, line 6 skipping to change at page 8, line 6
| | | |
| HMAC (16 octets) | | HMAC (16 octets) |
| | | |
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: STAMP Session-Sender test packet format in authenticated or Figure 4: STAMP Session-Sender test packet format in authenticated or
encrypted modes encrypted modes
The field definitions are the same as the unauthenticated mode, The field definitions are the same as the unauthenticated mode,
listed in Section 4.1.1. In addition, Commp.MBZ field is variable listed in Section 4.1.1. Also, Comp.MBZ field is variable length
length filed to align the packet on 16 octets boundary. Also, the filed to align the packet on 16 octets boundary. Also, the packet
packet includes a key-hashed message authentication code (HMAC) includes a key-hashed message authentication code (HMAC) ([RFC2104])
([RFC2104]) hash at the end of the PDU. hash at the end of the PDU.
The STAMP Session-Sender-packet format (Figure 4) is the same in The STAMP Session-Sender-packet format (Figure 4) is the same in
authenticated and encrypted modes. The encryption and authentication authenticated and encrypted modes. The encryption and authentication
operations are, however, different and protect the data as following: operations are, however, different and protect the data as follows:
in authenticated mode the Sequence Number is protected while the in the authenticated mode the Sequence Number is protected while
Timestamp and the Error Estimate are sent in clear text; the Timestamp and the Error Estimate are sent in clear text;
in encrypted mode all fields, including the timestamp and Error in encrypted mode all fields, including the timestamp and Error
Estimate, are protected to provide maximum data confidentiality Estimate, are protected to provide maximum data confidentiality
and integrity protection. and integrity protection.
Sending the Timestamp in clear text in authenticated mode allows more Sending the Timestamp in clear text in authenticated mode allows more
consistent reading of time by a Session-Sender on the transmission of consistent reading of time by a Session-Sender on the transmission of
the test packet. Reading of the time in encrypted mode must be the test packet. Reading of the time in encrypted mode must be
followed by its encryption which introduces variable delay thus followed by its encryption which introduces variable delay thus
affecting calculated timing metrics. affecting calculated timing metrics.
4.2. Session-Reflector Behavior and Packet Format 4.2. Session-Reflector Behavior and Packet Format
The Session-Reflector receives the STAMP test packet, verifies it, The Session-Reflector receives the STAMP test packet, verifies it,
prepares and transmits the reflected test packet. prepares and transmits the reflected test packet.
Two modes of STAMP Session-Reflector characterize expected behavior Two modes of STAMP Session-Reflector characterize the expected
and, consequently, performance metrics that can be measured: behavior and, consequently, performance metrics that can be measured:
o Stateless - STAMP Session-Reflector does not maintain test state o Stateless - STAMP Session-Reflector does not maintain test state
and will reflect back the received sequence number without and will reflect the received sequence number without
modification. As a result, only round-trip packet loss can be modification. As a result, only round-trip packet loss can be
calculated while the reflector is operating in stateless mode. calculated while the reflector is operating in stateless mode.
o Stateful - STAMP Session-Reflector maintains test state o Stateful - STAMP Session-Reflector maintains test state thus
determining forward loss, gaps recognized in the received sequence enabling the ability to determine forward loss, gaps recognized in
number. This means both near-end (forward) and far-end (backward) the received sequence number. As a result, both near-end
packet loss can be computed. This implies that the STAMP Session- (forward) and far-end (backward) packet loss can be computed.
Reflector MUST keep a state for each accepted STAMP-test session, This implies that the STAMP Session-Reflector MUST keep a state
uniquely identifying STAMP-test packets to one such session for each accepted STAMP-test session, uniquely identifying STAMP-
instance, and enabling adding a sequence number in the test reply test packets to one such session instance, and enabling adding a
that is individually incremented on a per-session basis. sequence number in the test reply that is individually incremented
on a per-session basis.
4.2.1. Session-Reflector Packet Format in Unauthenticated Mode 4.2.1. Session-Reflector Packet Format in Unauthenticated Mode
For unauthenticated mode: For unauthenticated mode:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number | | Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 10, line 7 skipping to change at page 10, line 7
o Sequence Number is four octets long field. The value of the o Sequence Number is four octets long field. The value of the
Sequence Number field is set according to the mode of the STAMP Sequence Number field is set according to the mode of the STAMP
Session-Reflector: Session-Reflector:
* in the stateless mode the Session-Reflector copies the value * in the stateless mode the Session-Reflector copies the value
from the received STAMP test packet's Sequence Number field; from the received STAMP test packet's Sequence Number field;
* in the stateful mode the Session-Reflector counts the received * in the stateful mode the Session-Reflector counts the received
STAMP test packets in each test session and uses that counter STAMP test packets in each test session and uses that counter
to set value of the Sequence Number field. to set the value of the Sequence Number field.
o Timestamp and Receiver Timestamp fields are each 8 octets long. o Timestamp and Receiver Timestamp fields are each eight octets
The format of these fields, NTP or PTPv2, indicated by the Z flag long. The format of these fields, NTP or PTPv2, indicated by the
of the Error Estimate field as described in Section 4.1. Z flag of the Error Estimate field as described in Section 4.1.
o Error Estimate has the same size and interpretation as described o Error Estimate has the same size and interpretation as described
in Section 4.1. in Section 4.1.
o Session-Sender Sequence Number, Session-Sender Timestamp, and o Session-Sender Sequence Number, Session-Sender Timestamp, and
Session-Sender Error Estimate are copies of the corresponding Session-Sender Error Estimate are copies of the corresponding
fields in the STAMP test packet send by the Session-Sender. fields in the STAMP test packet sent by the Session-Sender.
o Ses(sion)-Sender TTL is one octet long field and its value is the o Ses(sion)-Sender TTL is one octet long field, and its value is the
copy of the TTL field from the received STAMP test packet. copy of the TTL field from the received STAMP test packet.
o Packet Padding (reflected) is optional variable length field. The o Packet Padding (reflected) is optional variable length field. The
length of the Packet Padding (reflected) field MUST be equal to length of the Packet Padding (reflected) field MUST be equal to
the value of the Server Octets field (Figure 2). If the value is the value of the Server Octets field (Figure 2). If the value is
non-zero, the Session-Reflector copies octets starting with the non-zero, the Session-Reflector copies octets starting with the
Server Octets field. Server Octets field.
o Comp.MBZ is variable length field used to achieve alignment on o Comp.MBZ is variable length field used to achieve alignment on a
word boundary. Thus the length of Comp.MBZ field may be only 0, word boundary. Thus the length of Comp.MBZ field may be only 0,
1, 2 or 3 octets. The value of the field MUST be zeroed on 1, 2 or 3 octets. The value of the field MUST be zeroed on
transmission and ignored on receipt. transmission and ignored on receipt.
4.2.2. Session-Reflector Packet Format in Authenticated and Encrypted 4.2.2. Session-Reflector Packet Format in Authenticated and Encrypted
Modes Modes
For authenticated and encrypted modes: For authenticated and encrypted modes:
0 1 2 3 0 1 2 3
skipping to change at page 12, line 7 skipping to change at page 12, line 7
Figure 6: STAMP Session-Reflector test packet format in authenticated Figure 6: STAMP Session-Reflector test packet format in authenticated
or encrypted modes or encrypted modes
The field definitions are the same as the unauthenticated mode, The field definitions are the same as the unauthenticated mode,
listed in Section 4.2.1, and includes a key-hashed message listed in Section 4.2.1, and includes a key-hashed message
authentication code (HMAC) ([RFC2104]) hash at the end of the PDU. authentication code (HMAC) ([RFC2104]) hash at the end of the PDU.
4.3. Interoperability with TWAMP Light 4.3. Interoperability with TWAMP Light
One of important requirements to STAMP is ability to interwork with One of the important requirements to STAMP is the ability to
TWAMP Light device. There are two possible combinations for such use interwork with TWAMP Light device. There are two possible
case: combinations for such use case:
o STAMP Session-Sender with TWAMP Light Session-Reflector; o STAMP Session-Sender with TWAMP Light Session-Reflector;
o TWAMP Light Session-Sender with STAMP Session-Reflector. o TWAMP Light Session-Sender with STAMP Session-Reflector.
In the former case, Session-Sender MAY not be aware that its Session- In the former case, Session-Sender MAY not be aware that its Session-
Reflector does not support STAMP. For example, TWAMP Light Session- Reflector does not support STAMP. For example, TWAMP Light Session-
Reflector may not support use of UDP port 862 as defined in Reflector may not support the use of UDP port 862 as defined in
[I-D.ietf-ippm-port-twamp-test]. But because STAMP Session-Sender [I-D.ietf-ippm-port-twamp-test]. But because STAMP Session-Sender
MUST be able to send test packets to destination UDP port number from MUST be able to send test packets to destination UDP port number from
the Dynamic and/or Private Ports range 49152-65535, test management the Dynamic and/or Private Ports range 49152-65535, test management
system should find port number that both devices can use. And if any system should find port number that both devices can use. And if any
of TLV-based STAMP extensions are used, the TWAMP Light Session- of TLV-based STAMP extensions are used, the TWAMP Light Session-
Reflector will view them as Packet Padding field. The Session-Sender Reflector will view them as Packet Padding field. The Session-Sender
SHOULD use the default format for its timestamps - NTP. And it MAY SHOULD use the default format for its timestamps - NTP. And it MAY
use PTPv2 timestamp format. use PTPv2 timestamp format.
In the latter scenario, test management system should set STAMP In the latter scenario, the test management system should set STAMP
Session-Reflector to use UDP port number from the Dynamic and/or Session-Reflector to use UDP port number from the Dynamic and/or
Private Ports range. As for Packet Padding field that the TWAMP Private Ports range. As for Packet Padding field that the TWAMP
Light Session-Sender includes in its transmitted packet, the STAMP Light Session-Sender includes in its transmitted packet, the STAMP
Session-Reflector will process it according to [RFC6038] and return Session-Reflector will process it according to [RFC6038] and return
reflected packet of the symmetrical size. The Session-Reflector MUST reflected packet of the symmetrical size. The Session-Reflector MUST
use the default format for its timestamps - NTP. use the default format for its timestamps - NTP.
5. IANA Considerations 5. IANA Considerations
This document doesn't have any IANA action. This section may be This document doesn't have any IANA action. This section may be
skipping to change at page 13, line 15 skipping to change at page 13, line 15
8. References 8. References
8.1. Normative References 8.1. Normative References
[BBF.TR-390] [BBF.TR-390]
"Performance Measurement from IP Edge to Customer "Performance Measurement from IP Edge to Customer
Equipment using TWAMP Light", BBF TR-390, May 2017. Equipment using TWAMP Light", BBF TR-390, May 2017.
[I-D.ietf-ippm-port-twamp-test] [I-D.ietf-ippm-port-twamp-test]
Morton, A. and G. Mirsky, "OWAMP and TWAMP Well-Known Port Morton, A. and G. Mirsky, "OWAMP and TWAMP Well-Known Port
Assignments", draft-ietf-ippm-port-twamp-test-00 (work in Assignments", draft-ietf-ippm-port-twamp-test-01 (work in
progress), January 2018. progress), March 2018.
[IEEE.1588.2008] [IEEE.1588.2008]
"Standard for a Precision Clock Synchronization Protocol "Standard for a Precision Clock Synchronization Protocol
for Networked Measurement and Control Systems", for Networked Measurement and Control Systems",
IEEE Standard 1588, March 2008. IEEE Standard 1588, March 2008.
[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,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
 End of changes. 31 change blocks. 
58 lines changed or deleted 60 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/