draft-ietf-ippm-stamp-yang-05.txt   draft-ietf-ippm-stamp-yang-06.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 27, 2020 W. Luo Expires: April 10, 2021 W. Luo
Ericsson Ericsson
October 25, 2019 October 7, 2020
Simple Two-way Active Measurement Protocol (STAMP) Data Model Simple Two-way Active Measurement Protocol (STAMP) Data Model
draft-ietf-ippm-stamp-yang-05 draft-ietf-ippm-stamp-yang-06
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 27, 2020. This Internet-Draft will expire on April 10, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2020 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
skipping to change at page 2, line 28 skipping to change at page 2, line 28
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 . . . . . . . . . . . . . . . . . 34
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) The Simple Two-way Active Measurement Protocol (STAMP) [RFC8762] can
[I-D.ietf-ippm-stamp] can be used to measure performance parameters be used to measure performance parameters of IP networks such as
of IP networks such as latency, jitter, and packet loss by sending latency, jitter, and packet loss by sending test packets and
test packets and monitoring their experience in the network. The monitoring their experience in the network. The STAMP protocol
STAMP protocol [I-D.ietf-ippm-stamp] in unauthenticated mode is on- [RFC8762] in unauthenticated mode is on-wire compatible with STAMP
wire compatible with STAMP Light, discussed in Appendix I [RFC5357]. Light, discussed in Appendix I [RFC5357]. The STAMP Light is known
The STAMP Light is known to have many implementations though no to have many implementations though no common management framework
common management framework being defined, thus leaving some aspects being defined, thus leaving some aspects of test packet processing to
of test packet processing to interpretation. As one of the goals of interpretation. As one of the goals of STAMP is to support these
STAMP is to support these variations, this document presents their variations, this document presents their analysis; describes common
analysis; describes common STAMP and STAMP model while allowing for STAMP and STAMP model while allowing for STAMP extensions in the
STAMP extensions in the future. This document defines the STAMP data future. This document defines the STAMP data model and specifies it
model and specifies it formally, using the YANG data modeling formally, using the YANG data modeling language [RFC7950].
language [RFC7950].
This version of the interfaces data model conforms to the Network This version of the interfaces data model conforms to the Network
Management Datastore Architecture (NMDA) defined in [RFC8342]. Management Datastore Architecture (NMDA) defined in [RFC8342].
1.1. Conventions used in this document 1.1. Conventions used in this document
1.1.1. Requirements Language 1.1.1. 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.
2. Scope, Model, and Applicability 2. Scope, Model, and Applicability
The scope of this document includes a model of the STAMP as defined The scope of this document includes a model of the STAMP as defined
in [I-D.ietf-ippm-stamp]. in [RFC8762].
o----------------------------------------------------------o o----------------------------------------------------------o
| Config client | | Config client |
o----------------------------------------------------------o o----------------------------------------------------------o
|| || || ||
|| NETCONF/RESTCONF || || NETCONF/RESTCONF ||
|| || || ||
o----------------------o o-------------------------o o----------------------o o-------------------------o
| Config server | | Config server | | Config server | | Config server |
| | | | | | | |
skipping to change at page 10, line 29 skipping to change at page 10, line 29
| +---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@2019-10-20.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 11, line 27 skipping to change at page 11, line 27
description description
"This YANG module specifies a vendor-independent model "This YANG module specifies a vendor-independent model
for the Simple Two-way Active Measurement Protocol (STAMP). for the Simple Two-way Active Measurement Protocol (STAMP).
The data model covers two STAMP logical entities - The data model covers two STAMP logical entities -
Session-Sender and Session-Reflector; characteristics Session-Sender and Session-Reflector; characteristics
of the STAMP test session, as well as measured and of the STAMP test session, as well as measured and
calculated performance metrics. calculated performance metrics.
Copyright (c) 2019 IETF Trust and the persons identified as Copyright (c) 2020 IETF Trust and the persons identified as
the document authors. All rights reserved. the document authors. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD to the license terms contained in, the Simplified BSD
License set forth in Section 4.c of the IETF Trust's Legal License set forth in Section 4.c of the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
revision "2019-10-20" { revision "2020-10-07" {
description description
"Initial Revision. Base STAMP specification is covered"; "Initial Revision. Base STAMP specification is covered";
reference reference
"RFC XXXX: STAMP YANG Data Model."; "RFC XXXX: STAMP YANG Data Model.";
} }
/* /*
* Typedefs * Typedefs
*/ */
typedef session-reflector-mode { typedef session-reflector-mode {
skipping to change at page 32, line 39 skipping to change at page 32, line 39
6. Acknowledgments 6. Acknowledgments
Authors recognize and appreciate valuable comments provided by Adrian Authors recognize and appreciate valuable comments provided by Adrian
Pan and Henrik Nydell. Pan and Henrik Nydell.
7. References 7. References
7.1. Normative References 7.1. Normative References
[I-D.ietf-ippm-stamp]
Mirsky, G., Jun, G., Nydell, H., and R. Foote, "Simple
Two-way Active Measurement Protocol", draft-ietf-ippm-
stamp-09 (work in progress), October 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>.
[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, DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>. <https://www.rfc-editor.org/info/rfc3688>.
[RFC5357] Hedayat, K., Krzanowski, R., Morton, A., Yum, K., and J. [RFC5357] Hedayat, K., Krzanowski, R., Morton, A., Yum, K., and J.
skipping to change at page 34, line 5 skipping to change at page 33, line 46
[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore Architecture and R. Wilton, "Network Management Datastore Architecture
(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
<https://www.rfc-editor.org/info/rfc8342>. <https://www.rfc-editor.org/info/rfc8342>.
[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
<https://www.rfc-editor.org/info/rfc8446>. <https://www.rfc-editor.org/info/rfc8446>.
[RFC8762] Mirsky, G., Jun, G., Nydell, H., and R. Foote, "Simple
Two-Way Active Measurement Protocol", RFC 8762,
DOI 10.17487/RFC8762, March 2020,
<https://www.rfc-editor.org/info/rfc8762>.
7.2. Informative References 7.2. Informative References
[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
<https://www.rfc-editor.org/info/rfc8340>. <https://www.rfc-editor.org/info/rfc8340>.
Appendix A. Example of STAMP Session Configuration Appendix A. Example of STAMP Session Configuration
Figure 5 shows a configuration example of a STAMP-Sender. Figure 5 shows a configuration example of a STAMP-Sender.
 End of changes. 12 change blocks. 
28 lines changed or deleted 27 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/