draft-ietf-ippm-stamp-option-tlv-00.txt   draft-ietf-ippm-stamp-option-tlv-01.txt 
Network Working Group G. Mirsky Network Working Group G. Mirsky
Internet-Draft X. Min Internet-Draft X. Min
Intended status: Standards Track ZTE Corp. Intended status: Standards Track ZTE Corp.
Expires: January 25, 2020 G. Jun Expires: March 23, 2020 G. Jun
ZTE Corporation ZTE Corporation
H. Nydell H. Nydell
Accedian Networks Accedian Networks
R. Foote R. Foote
Nokia Nokia
July 24, 2019 A. Masputra
Apple Inc.
September 20, 2019
Simple Two-way Active Measurement Protocol Optional Extensions Simple Two-way Active Measurement Protocol Optional Extensions
draft-ietf-ippm-stamp-option-tlv-00 draft-ietf-ippm-stamp-option-tlv-01
Abstract Abstract
This document describes optional extensions to Simple Two-way Active This document describes optional extensions to Simple Two-way Active
Measurement Protocol (STAMP) which enable measurement performance Measurement Protocol (STAMP) which enable measurement performance
metrics in addition to ones supported by the STAMP base metrics in addition to ones supported by the STAMP base
specification. specification.
Status of This Memo Status of This Memo
skipping to change at page 1, line 39 skipping to change at page 1, line 41
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 January 25, 2020. This Internet-Draft will expire on March 23, 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
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 . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions used in this document . . . . . . . . . . . . . . 2 2. Conventions used in this document . . . . . . . . . . . . . . 3
2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Requirements Language . . . . . . . . . . . . . . . . . . 3 2.2. Requirements Language . . . . . . . . . . . . . . . . . . 3
3. Theory of Operation . . . . . . . . . . . . . . . . . . . . . 3 3. Theory of Operation . . . . . . . . . . . . . . . . . . . . . 3
4. TLV Extensions to STAMP . . . . . . . . . . . . . . . . . . . 4 4. TLV Extensions to STAMP . . . . . . . . . . . . . . . . . . . 4
4.1. Extra Padding TLV . . . . . . . . . . . . . . . . . . . . 6 4.1. Extra Padding TLV . . . . . . . . . . . . . . . . . . . . 6
4.2. Location TLV . . . . . . . . . . . . . . . . . . . . . . 6 4.2. Location TLV . . . . . . . . . . . . . . . . . . . . . . 6
4.3. Timestamp Information TLV . . . . . . . . . . . . . . . . 8 4.3. Timestamp Information TLV . . . . . . . . . . . . . . . . 8
4.4. Class of Service TLV . . . . . . . . . . . . . . . . . . 9 4.4. Class of Service TLV . . . . . . . . . . . . . . . . . . 9
4.5. Direct Measurement TLV . . . . . . . . . . . . . . . . . 10 4.5. Direct Measurement TLV . . . . . . . . . . . . . . . . . 10
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 4.6. Access Report TLV . . . . . . . . . . . . . . . . . . . . 11
5.1. STAMP TLV Registry . . . . . . . . . . . . . . . . . . . 11 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
5.2. Synchronization Source Sub-registry . . . . . . . . . . . 12 5.1. STAMP TLV Registry . . . . . . . . . . . . . . . . . . . 12
5.3. Timestamping Method Sub-registry . . . . . . . . . . . . 13 5.2. Synchronization Source Sub-registry . . . . . . . . . . . 13
6. Security Considerations . . . . . . . . . . . . . . . . . . . 14 5.3. Timestamping Method Sub-registry . . . . . . . . . . . . 14
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 14 5.4. Access ID Sub-registry . . . . . . . . . . . . . . . . . 15
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 5.5. Return Code Sub-registry . . . . . . . . . . . . . . . . 16
8.1. Normative References . . . . . . . . . . . . . . . . . . 14 6. Security Considerations . . . . . . . . . . . . . . . . . . . 17
8.2. Informative References . . . . . . . . . . . . . . . . . 15 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
8.1. Normative References . . . . . . . . . . . . . . . . . . 17
8.2. Informative References . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18
1. Introduction 1. Introduction
Simple Two-way Active Measurement Protocol (STAMP) Simple Two-way Active Measurement Protocol (STAMP)
[I-D.ietf-ippm-stamp] supports the use of optional extensions that [I-D.ietf-ippm-stamp] supports the use of optional extensions that
use Type-Length-Value (TLV) encoding. Such extensions are to enhance use Type-Length-Value (TLV) encoding. Such extensions are to enhance
the STAMP base functions, such as measurement of one-way and round- the STAMP base functions, such as measurement of one-way and round-
trip delay, latency, packet loss, as well as ability to detect packet trip delay, latency, packet loss, as well as ability to detect packet
duplication and out-of-order delivery of the test packets. This duplication and out-of-order delivery of the test packets. This
specification provides definitions of optional STAMP extensions, specification provides definitions of optional STAMP extensions,
skipping to change at page 3, line 28 skipping to change at page 3, line 37
GPS Global Positioning System GPS Global Positioning System
GLONASS Global Orbiting Navigation Satellite System GLONASS Global Orbiting Navigation Satellite System
LORAN-C Long Range Navigation System Version C LORAN-C Long Range Navigation System Version C
MBZ Must Be Zeroed MBZ Must Be Zeroed
CoS Class of Service CoS Class of Service
PMF Performance Measurement Function
2.2. Requirements Language 2.2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
3. Theory of Operation 3. Theory of Operation
skipping to change at page 6, line 23 skipping to change at page 6, line 36
~ Extra Padding ~ ~ Extra Padding ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: Extra Padding TLV Figure 3: Extra Padding TLV
where fields are defined as the following: where fields are defined as the following:
o Extra Padding Type - TBA1 allocated by IANA Section 5.1 o Extra Padding Type - TBA1 allocated by IANA Section 5.1
o Length - 2 octets long field equals length on the Extra Padding o Length - two octets long field equals length on the Extra Padding
field in octets. field in octets.
o Extra Padding - a pseudo-random sequence of numbers. The field o Extra Padding - a pseudo-random sequence of numbers. The field
MAY be filled with all zeroes. MAY be filled with all zeroes.
The Extra Padding TLV is similar to the Packet Padding field in The Extra Padding TLV is similar to the Packet Padding field in
TWAMP-Test packet [RFC5357]. The in STAMP the Packet Padding field TWAMP-Test packet [RFC5357]. The in STAMP the Packet Padding field
is used to ensure symmetrical size between Session-Sender and is used to ensure symmetrical size between Session-Sender and
Session-Reflector test packets. Extra Padding TLV MUST be used to Session-Reflector test packets. Extra Padding TLV MUST be used to
create STAMP test packets of larger size. create STAMP test packets of larger size.
skipping to change at page 7, line 27 skipping to change at page 7, line 33
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Dest.port | Src.Port | Reserved B | | Dest.port | Src.Port | Reserved B |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: Session-Reflector Location TLV Figure 4: Session-Reflector Location TLV
where fields are defined as the following: where fields are defined as the following:
o Location Type - TBA2 allocated by IANA Section 5.1 o Location Type - TBA2 allocated by IANA Section 5.1
o Length - 2 octets long field equals length on the Value field in o Length - two octets long field equals length on the Value field in
octets. Length field value MUST be 20 octets for the IPv4 address octets. Length field value MUST be 20 octets for the IPv4 address
family. For the IPv6 address family value of the Length field family. For the IPv6 address family value of the Length field
MUST be 44 octets. All other values are invalid. MUST be 44 octets. All other values are invalid.
o Source MAC - 6 octets 48 bits long field. The session-reflector o Source MAC - 6 octets 48 bits long field. The session-reflector
MUST copy Source MAC of received STAMP packet into this field. MUST copy Source MAC of received STAMP packet into this field.
o Reserved A - two octets long field. MUST be zeroed on o Reserved A - two octets long field. MUST be zeroed on
transmission and ignored on reception. transmission and ignored on reception.
skipping to change at page 8, line 40 skipping to change at page 8, line 46
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sync. Src In | Timestamp In | Sync. Src Out | Timestamp Out | | Sync. Src In | Timestamp In | Sync. Src Out | Timestamp Out |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5: Timestamp Information TLV Figure 5: Timestamp Information TLV
where fields are defined as the following: where fields are defined as the following:
o Timestamp Information Type - TBA3 allocated by IANA Section 5.1 o Timestamp Information Type - TBA3 allocated by IANA Section 5.1
o Length - 2 octets long field, equals four octets. o Length - two octets long field, equals four octets.
o Sync Src In - one octet long field that characterizes the source o Sync Src In - one octet long field that characterizes the source
of clock synchronization at the ingress of Session-Reflector. of clock synchronization at the ingress of Session-Reflector.
There are several of methods to synchronize the clock, e.g., There are several of methods to synchronize the clock, e.g.,
Network Time Protocol (NTP) [RFC5905], Precision Time Protocol Network Time Protocol (NTP) [RFC5905], Precision Time Protocol
(PTP) [IEEE.1588.2008], Synchronization Supply Unit (SSU) or (PTP) [IEEE.1588.2008], Synchronization Supply Unit (SSU) or
Building Integrated Timing Supply (BITS), or Global Positioning Building Integrated Timing Supply (BITS), or Global Positioning
System (GPS), Global Orbiting Navigation Satellite System System (GPS), Global Orbiting Navigation Satellite System
(GLONASS) and Long Range Navigation System Version C (LORAN-C). (GLONASS) and Long Range Navigation System Version C (LORAN-C).
The value is one of Section 5.2. The value is one of Section 5.2.
skipping to change at page 9, line 51 skipping to change at page 10, line 7
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DSCP1 | DSCP2 |ECN| Reserved | | DSCP1 | DSCP2 |ECN| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 6: Class of Service TLV Figure 6: Class of Service TLV
where fields are defined as the following: where fields are defined as the following:
o Class of Service Type - TBA4 allocated by IANA Section 5.1 o Class of Service Type - TBA4 allocated by IANA Section 5.1
o Length - 2 octets long field, equals four octets. o Length - two octets long field, equals four octets.
o DSCP1 - The Differentiated Services Code Point (DSCP) intended by o DSCP1 - The Differentiated Services Code Point (DSCP) intended by
the Session-Sender. To be used as the return DSCP from the the Session-Sender. To be used as the return DSCP from the
Session-Reflector. Session-Reflector.
o DSCP2 - The received value in the DSCP field at the Session- o DSCP2 - The received value in the DSCP field at the Session-
Reflector in the forward direction. Reflector in the forward direction.
o ECN - The received value in the ECN field at the Session-Reflector o ECN - The received value in the ECN field at the Session-Reflector
in the forward direction. in the forward direction.
skipping to change at page 11, line 23 skipping to change at page 11, line 23
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Session-Reflector Tx counter (R_TxC) | | Session-Reflector Tx counter (R_TxC) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 7: Direct Measurement TLV Figure 7: Direct Measurement TLV
where fields are defined as the following: where fields are defined as the following:
o Direct Measurement Type - TBA5 allocated by IANA Section 5.1 o Direct Measurement Type - TBA5 allocated by IANA Section 5.1
o Length - 2 octets long field equals length on the Value field in o Length - two octets long field equals length on the Value field in
octets. Length field value MUST be 12 octets. octets. Length field value MUST be 12 octets.
o Session-Sender Tx counter (S_TxC) is four octets long field. o Session-Sender Tx counter (S_TxC) is four octets long field.
o Session-Reflector Rx counter (R_RxC) is four octets long field. o Session-Reflector Rx counter (R_RxC) is four octets long field.
MUST be zeroed by the Session-Sender and filled by the Session- MUST be zeroed by the Session-Sender and filled by the Session-
Reflector. Reflector.
o Session-Reflector Tx counter (R_TxC) is four octets long field. o Session-Reflector Tx counter (R_TxC) is four octets long field.
MUST be zeroed by the Session-Sender and filled by the Session- MUST be zeroed by the Session-Sender and filled by the Session-
Reflector. Reflector.
4.6. Access Report TLV
A STAMP Session-Sender MAY include Access Report TLV (Figure 8) to
indicate changes to the access network status to the Session-
Reflector. The definition of an access network is outside the scope
of this document.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Access Report Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Access ID | Return Code | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 8: Access Report TLV
where fields are defined as follows:
o Access Report Type - TBA6 allocated by IANA Section 5.1.
o Length - two octets long field, equals four octets.
o Access ID - one octet long field that identifies the access
network, e.g., 3GPP (Radio Access Technologies specified by 3GPP)
or Non-3GPP (accesses that are not specified by 3GPP) [TS23501].
The value is one of Section 5.4.
o Return Code - one octet long field that identifies the report
signal, e.g., available, unavailable. The value is one of
Section 5.5.
o Reserved - two octets long field, must be zeroed on transmission
and ignored on receipt.
The STAMP Session-Sender that includes the Access Report TLV sets the
value of the Access ID field according to the type of access network
it reports on. Also, the Session-Sender sets the value of the Return
Code field to reflect the operational state of the access network.
The mechanism to determine the state of the access network is outside
the scope of this specification. A STAMP Session-Reflector that
received the test packet with the Access Report TLV MUST include the
Access Report TLV in the reflected test packet. The Session-
Reflector MUST set the value of the Access ID and Return Code fields
equal to the values of the corresponding fields from the test packet
it has received.
The Access Report TLV is used by the Performance Measurement Function
(PMF) components of the Access Steering, Switching and Splitting
feature for 5G networks [TS23501]. The PMF component in the User
Equipment acts as the STAMP Session-Sender, and the PMF component in
the User Plane Function acts as the STAMP Session-Reflector.
5. IANA Considerations 5. IANA Considerations
5.1. STAMP TLV Registry 5.1. STAMP TLV Registry
IANA is requested to create the STAMP TLV Type registry. All code IANA is requested to create the STAMP TLV Type registry. All code
points in the range 1 through 32759 in this registry shall be points in the range 1 through 32759 in this registry shall be
allocated according to the "IETF Review" procedure as specified in allocated according to the "IETF Review" procedure as specified in
[RFC8126]. Code points in the range 32760 through 65279 in this [RFC8126]. Code points in the range 32760 through 65279 in this
registry shall be allocated according to the "First Come First registry shall be allocated according to the "First Come First
Served" procedure as specified in [RFC8126]. Remaining code points Served" procedure as specified in [RFC8126]. Remaining code points
skipping to change at page 12, line 20 skipping to change at page 13, line 20
| | unassigned | | | | unassigned | |
| 32768 - 65279 | Optional TLV, | First Come First Served | | 32768 - 65279 | Optional TLV, | First Come First Served |
| | unassigned | | | | unassigned | |
| 65280 - 65519 | Experimental | This document | | 65280 - 65519 | Experimental | This document |
| 65520 - 65534 | Private Use | This document | | 65520 - 65534 | Private Use | This document |
| 65535 | Reserved | This document | | 65535 | Reserved | This document |
+---------------+-------------------------+-------------------------+ +---------------+-------------------------+-------------------------+
Table 1: STAMP TLV Type Registry Table 1: STAMP TLV Type Registry
This document defines the following new values in STAMP TLV Type This document defines the following new values in the STAMP TLV Type
registry: registry:
+-------+-----------------------+---------------+ +-------+-----------------------+---------------+
| Value | Description | Reference | | Value | Description | Reference |
+-------+-----------------------+---------------+ +-------+-----------------------+---------------+
| TBA1 | Extra Padding | This document | | TBA1 | Extra Padding | This document |
| TBA2 | Location | This document | | TBA2 | Location | This document |
| TBA3 | Timestamp Information | This document | | TBA3 | Timestamp Information | This document |
| TBA4 | Class of Service | This document | | TBA4 | Class of Service | This document |
| TBA5 | Direct Measurement | This document | | TBA6 | Access Report | This document |
+-------+-----------------------+---------------+ +-------+-----------------------+---------------+
Table 2: STAMP Types Table 2: STAMP Types
5.2. Synchronization Source Sub-registry 5.2. Synchronization Source Sub-registry
IANA is requested to create Synchronization Source sub-registry as IANA is requested to create Synchronization Source sub-registry as
part of STAMP TLV Type registry. All code points in the range 1 part of STAMP TLV Type registry. All code points in the range 1
through 127 in this registry shall be allocated according to the through 127 in this registry shall be allocated according to the
"IETF Review" procedure as specified in [RFC8126]. Code points in "IETF Review" procedure as specified in [RFC8126]. Code points in
skipping to change at page 13, line 18 skipping to change at page 14, line 18
| 0 | Reserved | This document | | 0 | Reserved | This document |
| 1- 127 | Unassigned | IETF Review | | 1- 127 | Unassigned | IETF Review |
| 128 - 239 | Unassigned | First Come First Served | | 128 - 239 | Unassigned | First Come First Served |
| 240 - 249 | Experimental | This document | | 240 - 249 | Experimental | This document |
| 250 - 254 | Private Use | This document | | 250 - 254 | Private Use | This document |
| 255 | Reserved | This document | | 255 | Reserved | This document |
+-----------+--------------+-------------------------+ +-----------+--------------+-------------------------+
Table 3: Synchronization Source Sub-registry Table 3: Synchronization Source Sub-registry
This document defines the following new values in Synchronization This document defines the following new values in the Synchronization
Source sub-registry: Source sub-registry:
+-------+---------------------+---------------+ +-------+---------------------+---------------+
| Value | Description | Reference | | Value | Description | Reference |
+-------+---------------------+---------------+ +-------+---------------------+---------------+
| 1 | NTP | This document | | 1 | NTP | This document |
| 2 | PTP | This document | | 2 | PTP | This document |
| 3 | SSU/BITS | This document | | 3 | SSU/BITS | This document |
| 4 | GPS/GLONASS/LORAN-C | This document | | 4 | GPS/GLONASS/LORAN-C | This document |
| 5 | Local free-running | This document | | 5 | Local free-running | This document |
skipping to change at page 14, line 18 skipping to change at page 15, line 18
| 0 | Reserved | This document | | 0 | Reserved | This document |
| 1- 127 | Unassigned | IETF Review | | 1- 127 | Unassigned | IETF Review |
| 128 - 239 | Unassigned | First Come First Served | | 128 - 239 | Unassigned | First Come First Served |
| 240 - 249 | Experimental | This document | | 240 - 249 | Experimental | This document |
| 250 - 254 | Private Use | This document | | 250 - 254 | Private Use | This document |
| 255 | Reserved | This document | | 255 | Reserved | This document |
+-----------+--------------+-------------------------+ +-----------+--------------+-------------------------+
Table 5: Timestamping Method Sub-registry Table 5: Timestamping Method Sub-registry
This document defines the following new values in Timestamping This document defines the following new values in the Timestamping
Methods sub-registry: Methods sub-registry:
+-------+---------------+---------------+ +-------+---------------+---------------+
| Value | Description | Reference | | Value | Description | Reference |
+-------+---------------+---------------+ +-------+---------------+---------------+
| 1 | HW assist | This document | | 1 | HW Assist | This document |
| 2 | SW local | This document | | 2 | SW local | This document |
| 3 | Control plane | This document | | 3 | Control plane | This document |
+-------+---------------+---------------+ +-------+---------------+---------------+
Table 6: Timestamping Methods Table 6: Timestamping Methods
5.4. Access ID Sub-registry
IANA is requested to create Access ID sub-registry as part of STAMP
TLV Type registry. All code points in the range 1 through 127 in
this registry shall be allocated according to the "IETF Review"
procedure as specified in [RFC8126]. Code points in the range 128
through 239 in this registry shall be allocated according to the
"First Come First Served" procedure as specified in [RFC8126].
Remaining code points are allocated according to Table 7:
+-----------+--------------+-------------------------+
| Value | Description | Reference |
+-----------+--------------+-------------------------+
| 0 | Reserved | This document |
| 1- 127 | Unassigned | IETF Review |
| 128 - 239 | Unassigned | First Come First Served |
| 240 - 249 | Experimental | This document |
| 250 - 254 | Private Use | This document |
| 255 | Reserved | This document |
+-----------+--------------+-------------------------+
Table 7: Access ID Sub-registry
This document defines the following new values in the Access ID sub-
registry:
+-------+-------------+---------------+
| Value | Description | Reference |
+-------+-------------+---------------+
| 1 | 3GPP | This document |
| 2 | Non-3GPP | This document |
+-------+-------------+---------------+
Table 8: Access IDs
5.5. Return Code Sub-registry
IANA is requested to create Return Code sub-registry as part of STAMP
TLV Type registry. All code points in the range 1 through 127 in
this registry shall be allocated according to the "IETF Review"
procedure as specified in [RFC8126]. Code points in the range 128
through 239 in this registry shall be allocated according to the
"First Come First Served" procedure as specified in [RFC8126].
Remaining code points are allocated according to Table 7:
+-----------+--------------+-------------------------+
| Value | Description | Reference |
+-----------+--------------+-------------------------+
| 0 | Reserved | This document |
| 1- 127 | Unassigned | IETF Review |
| 128 - 239 | Unassigned | First Come First Served |
| 240 - 249 | Experimental | This document |
| 250 - 254 | Private Use | This document |
| 255 | Reserved | This document |
+-----------+--------------+-------------------------+
Table 9: Return Code Sub-registry
This document defines the following new values in the Return Code
sub-registry:
+-------+---------------------+---------------+
| Value | Description | Reference |
+-------+---------------------+---------------+
| 1 | Network available | This document |
| 2 | Network unavailable | This document |
+-------+---------------------+---------------+
Table 10: Return Codes
6. Security Considerations 6. Security Considerations
Use of HMAC in authenticated mode may be used to simultaneously Use of HMAC in authenticated mode may be used to simultaneously
verify both the data integrity and the authentication of the STAMP verify both the data integrity and the authentication of the STAMP
test packets. test packets.
7. Acknowledgments 7. Acknowledgments
Authors much appreciate the thorough review and thoughful comments Authors much appreciate the thorough review and thoughful comments
received from Tianran Zhou. received from Tianran Zhou.
8. References 8. References
8.1. Normative References 8.1. Normative References
[I-D.ietf-ippm-stamp] [I-D.ietf-ippm-stamp]
Mirsky, G., Jun, G., Nydell, H., and R. Foote, "Simple Mirsky, G., Jun, G., Nydell, H., and R. Foote, "Simple
Two-way Active Measurement Protocol", draft-ietf-ippm- Two-way Active Measurement Protocol", draft-ietf-ippm-
stamp-06 (work in progress), April 2019. stamp-07 (work in progress), August 2019.
[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>.
[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>.
skipping to change at page 15, line 41 skipping to change at page 18, line 17
[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.
[RFC5905] Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch, [RFC5905] Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch,
"Network Time Protocol Version 4: Protocol and Algorithms "Network Time Protocol Version 4: Protocol and Algorithms
Specification", RFC 5905, DOI 10.17487/RFC5905, June 2010, Specification", RFC 5905, DOI 10.17487/RFC5905, June 2010,
<https://www.rfc-editor.org/info/rfc5905>. <https://www.rfc-editor.org/info/rfc5905>.
[TS23501] 3GPP (3rd Generation Partnership Project), "Technical
Specification Group Services and System Aspects; System
Architecture for the 5G System; Stage 2 (Release 16)",
3GPP TS23501, 2019.
Authors' Addresses Authors' Addresses
Greg Mirsky Greg Mirsky
ZTE Corp. ZTE Corp.
Email: gregimirsky@gmail.com Email: gregimirsky@gmail.com
Xiao Min Xiao Min
ZTE Corp. ZTE Corp.
skipping to change at page 16, line 17 skipping to change at page 19, line 4
Nanjing, Jiangsu 210012 Nanjing, Jiangsu 210012
P.R.China P.R.China
Phone: +86 18105183663 Phone: +86 18105183663
Email: guo.jun2@zte.com.cn Email: guo.jun2@zte.com.cn
Henrik Nydell Henrik Nydell
Accedian Networks Accedian Networks
Email: hnydell@accedian.com Email: hnydell@accedian.com
Richard Foote Richard Foote
Nokia Nokia
Email: footer.foote@nokia.com Email: footer.foote@nokia.com
Adi Masputra
Apple Inc.
One Apple Park Way
Cupertino, CA 95014
USA
Email: adi@apple.com
 End of changes. 23 change blocks. 
28 lines changed or deleted 162 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/