draft-ietf-ippm-stamp-yang-06.txt   draft-ietf-ippm-stamp-yang-07.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: April 10, 2021 W. Luo Expires: 1 October 2021 W.S. Luo
Ericsson Ericsson
October 7, 2020 30 March 2021
Simple Two-way Active Measurement Protocol (STAMP) Data Model Simple Two-way Active Measurement Protocol (STAMP) Data Model
draft-ietf-ippm-stamp-yang-06 draft-ietf-ippm-stamp-yang-07
Abstract Abstract
This document specifies the data model for implementations of This document specifies the data model for implementations of
Session-Sender and Session-Reflector for Simple Two-way Active Session-Sender and Session-Reflector for Simple Two-way Active
Measurement Protocol (STAMP) mode using YANG. Measurement Protocol (STAMP) mode 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
skipping to change at page 1, line 34 skipping to change at page 1, line 34
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 April 10, 2021. This Internet-Draft will expire on 1 October 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2021 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/
(https://trustee.ietf.org/license-info) in effect on the date of license-info) in effect on the date of publication of this document.
publication of this document. Please review these documents Please review these documents carefully, as they describe your rights
carefully, as they describe your rights and restrictions with respect and restrictions with respect to this document. Code Components
to this document. Code Components extracted from this document must extracted from this document must include Simplified BSD License text
include Simplified BSD License text as described in Section 4.e of as described in Section 4.e of the Trust Legal Provisions and are
the Trust Legal Provisions and are provided without warranty as 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
1.1. Conventions used in this document . . . . . . . . . . . . 2 1.1. Conventions used in this document . . . . . . . . . . . . 2
1.1.1. Requirements Language . . . . . . . . . . . . . . . . 2 1.1.1. Requirements Language . . . . . . . . . . . . . . . . 3
2. Scope, Model, and Applicability . . . . . . . . . . . . . . . 3 2. Scope, Model, and Applicability . . . . . . . . . . . . . . . 3
2.1. Data Model Parameters . . . . . . . . . . . . . . . . . . 3 2.1. Data Model Parameters . . . . . . . . . . . . . . . . . . 3
2.1.1. STAMP-Sender . . . . . . . . . . . . . . . . . . . . 3 2.1.1. STAMP-Sender . . . . . . . . . . . . . . . . . . . . 3
2.1.2. STAMP-Reflector . . . . . . . . . . . . . . . . . . . 4 2.1.2. STAMP-Reflector . . . . . . . . . . . . . . . . . . . 4
3. Data Model . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Data Model . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 4 3.1. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 5
3.2. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 10 3.2. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 10
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31
5. Security Considerations . . . . . . . . . . . . . . . . . . . 31 5. Security Considerations . . . . . . . . . . . . . . . . . . . 31
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 32 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 32
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 32 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 32
7.1. Normative References . . . . . . . . . . . . . . . . . . 32 7.1. Normative References . . . . . . . . . . . . . . . . . . 32
7.2. Informative References . . . . . . . . . . . . . . . . . 34 7.2. Informative References . . . . . . . . . . . . . . . . . 33
Appendix A. Example of STAMP Session Configuration . . . . . . . 34 Appendix A. Example of STAMP Session Configuration . . . . . . . 34
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 35 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 35
1. Introduction 1. Introduction
The Simple Two-way Active Measurement Protocol (STAMP) [RFC8762] can The Simple Two-way Active Measurement Protocol (STAMP) [RFC8762] can
be used to measure performance parameters of IP networks such as be used to measure performance parameters of IP networks such as
latency, jitter, and packet loss by sending test packets and latency, jitter, and packet loss by sending test packets and
monitoring their experience in the network. The STAMP protocol monitoring their experience in the network. The STAMP protocol
[RFC8762] in unauthenticated mode is on-wire compatible with STAMP [RFC8762] in unauthenticated mode is on-wire compatible with STAMP
skipping to change at page 3, line 47 skipping to change at page 4, line 10
state of the particular STAMP test session. state of the particular STAMP test session.
RPCs stamp-sender-start and stamp-sender-stop respectively start and RPCs stamp-sender-start and stamp-sender-stop respectively start and
stop the referenced session by the session-id of the STAMP. stop the referenced session by the session-id of the STAMP.
2.1.1.1. Controls for Test Session and Performance Metric Calculation 2.1.1.1. Controls for Test Session and Performance Metric Calculation
The data model supports several scenarios for a STAMP Session-Sender The data model supports several scenarios for a STAMP Session-Sender
to execute test sessions and calculate performance metrics: to execute test sessions and calculate performance metrics:
The test mode in which the test packets are sent unbound in time * The test mode in which the test packets are sent unbound in time
as defined by the parameter 'interval' in the stamp-session-sender as defined by the parameter 'interval' in the stamp-session-sender
container frequency is referred to as continuous mode. container frequency is referred to as continuous mode.
Performance metrics in the continuous mode are calculated at a Performance metrics in the continuous mode are calculated at a
period defined by the parameter 'measurement-interval'. period defined by the parameter 'measurement-interval'.
The test mode that has a specific number of the test packets * The test mode that has a specific number of the test packets
configured for the test session in the 'number-of-packets' configured for the test session in the 'number-of-packets'
parameter is referred to as a periodic mode. The STAMP-Sender MAY parameter is referred to as a periodic mode. The STAMP-Sender MAY
repeat the test session with the same parameters. The 'repeat' repeat the test session with the same parameters. The 'repeat'
parameter defines the number of tests and the 'repeat-interval' - parameter defines the number of tests and the 'repeat-interval' -
the interval between the consecutive tests. The performance the interval between the consecutive tests. The performance
metrics are calculated after each test session when the interval metrics are calculated after each test session when the interval
defined by the 'session-timeout' expires. defined by the 'session-timeout' expires.
2.1.2. STAMP-Reflector 2.1.2. STAMP-Reflector
skipping to change at page 5, line 46 skipping to change at page 6, line 4
| +--rw session-id uint32 | +--rw session-id uint32
| +--rw dscp-handling-mode? session-dscp-mode | +--rw dscp-handling-mode? session-dscp-mode
| +--rw dscp-value? inet:dscp | +--rw dscp-value? inet:dscp
| +--rw sender-ip? union | +--rw sender-ip? union
| +--rw sender-udp-port? union | +--rw sender-udp-port? union
| +--rw reflector-ip? union | +--rw reflector-ip? union
| +--rw reflector-udp-port? inet:port-number | +--rw reflector-udp-port? inet:port-number
| +--rw reflector-timestamp-format? timestamp-format | +--rw reflector-timestamp-format? timestamp-format
| +--rw security! {stamp-security}? | +--rw security! {stamp-security}?
| +--rw key-chain? kc:key-chain-ref | +--rw key-chain? kc:key-chain-ref
Figure 2: STAMP Configuration Tree Diagram
Figure 2: STAMP Configuration Tree Diagram
module: ietf-stamp module: ietf-stamp
+--ro stamp-state +--ro stamp-state
+--ro stamp-session-sender-state {session-sender}? +--ro stamp-session-sender-state {session-sender}?
| +--ro test-session-state* [session-id] | +--ro test-session-state* [session-id]
| +--ro session-id uint32 | +--ro session-id uint32
| +--ro sender-session-state? enumeration | +--ro sender-session-state? enumeration
| +--ro current-stats | +--ro current-stats
| | +--ro start-time yang:date-and-time | | +--ro start-time yang:date-and-time
| | +--ro packet-padding-size? uint32 | | +--ro packet-padding-size? uint32
skipping to change at page 10, line 25 skipping to change at page 10, line 30
Figure 3: STAMP State Tree Diagram Figure 3: STAMP State Tree Diagram
rpcs: rpcs:
+---x stamp-sender-start +---x stamp-sender-start
| +---w input | +---w input
| +---w session-id uint32 | +---w session-id uint32
+---x stamp-sender-stop +---x stamp-sender-stop
+---w input +---w input
+---w session-id uint32 +---w session-id uint32
Figure 4: STAMP RPC Tree Diagram Figure 4: STAMP RPC Tree Diagram
3.2. YANG Module 3.2. YANG Module
<CODE BEGINS> file "ietf-stamp@2020-10-07.yang" <CODE BEGINS> file "ietf-stamp@2020-10-07.yang"
module ietf-stamp { module ietf-stamp {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-stamp"; namespace "urn:ietf:params:xml:ns:yang:ietf-stamp";
//namespace need to be assigned by IANA //namespace need to be assigned by IANA
prefix "ietf-stamp"; prefix "ietf-stamp";
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
reference "RFC 6991: Common YANG Types."; reference "RFC 6991: Common YANG Types.";
} }
skipping to change at page 30, line 48 skipping to change at page 30, line 50
input { input {
leaf session-id { leaf session-id {
type uint32; type uint32;
mandatory true; mandatory true;
description description
"The session to be stopped"; "The session to be stopped";
} }
} }
} }
} }
<CODE ENDS>
<CODE ENDS>
4. IANA Considerations 4. IANA Considerations
This document registers a URI in the IETF XML registry [RFC3688]. This document registers a URI in the IETF XML registry [RFC3688].
Following the format in [RFC3688], the following registration is Following the format in [RFC3688], the following registration is
requested to be made. requested to be made.
URI: urn:ietf:params:xml:ns:yang:ietf-stamp URI: urn:ietf:params:xml:ns:yang:ietf-stamp
Registrant Contact: The IPPM WG of the IETF. Registrant Contact: The IPPM WG of the IETF.
skipping to change at page 34, line 45 skipping to change at page 34, line 43
<reflector-udp-port/> <!-- use default 862 --> <reflector-udp-port/> <!-- use default 862 -->
<sender-timestamp-format/> <sender-timestamp-format/>
<!-- No authentication --> <!-- No authentication -->
<first-percentile/> <!-- use default 95 --> <first-percentile/> <!-- use default 95 -->
<second-percentile/> <!-- use default 99 --> <second-percentile/> <!-- use default 99 -->
<third-percentile/> <!-- use default 99.9 --> <third-percentile/> <!-- use default 99.9 -->
</stamp-session-sender> </stamp-session-sender>
</stamp> </stamp>
</data> </data>
Figure 5: XML instance of STAMP Session-Sender configuration Figure 5: XML instance of STAMP Session-Sender configuration
<?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">
<stamp xmlns="urn:ietf:params:xml:ns:yang:ietf-stamp"> <stamp xmlns="urn:ietf:params:xml:ns:yang:ietf-stamp">
<stamp-session-reflector> <stamp-session-reflector>
<session-enable>enable</session-enable> <session-enable>enable</session-enable>
<ref-wait/> <!-- use default 900 seconds --> <ref-wait/> <!-- use default 900 seconds -->
<!-- use default 'stateless' --> <!-- use default 'stateless' -->
<reflector-mode-state/> <reflector-mode-state/>
<session-id></session-id> <session-id></session-id>
skipping to change at page 35, line 36 skipping to change at page 35, line 36
</stamp> </stamp>
</data> </data>
Figure 6: XML instance of STAMP Session-Reflector configuration Figure 6: XML instance of STAMP Session-Reflector configuration
Authors' Addresses Authors' Addresses
Greg Mirsky Greg Mirsky
ZTE Corp. ZTE Corp.
Email: gregimirsky@gmail.com Email: gregimirsky@gmail.com, gregory.mirsky@ztetx.com
Xiao Min Xiao Min
ZTE Corp. ZTE Corp.
Email: xiao.min2@zte.com.cn Email: xiao.min2@zte.com.cn
Wei S Luo Wei S Luo
Ericsson Ericsson
Email: wei.s.luo@ericsson.com Email: wei.s.luo@ericsson.com
 End of changes. 18 change blocks. 
27 lines changed or deleted 22 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/