Two-Way Active Measurement Protocol (TWAMP) Light Data Model
draft-mirsky-ippm-twamp-light-yang-01
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
|
|
|---|---|---|---|
| Authors | Greg Mirsky , Tamas Elteto | ||
| Last updated | 2016-01-05 | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | I-D Exists | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
draft-mirsky-ippm-twamp-light-yang-01
Network Working Group G. Mirsky
Internet-Draft T. Elteto
Intended status: Standards Track Ericsson
Expires: July 8, 2016 January 5, 2016
Two-Way Active Measurement Protocol (TWAMP) Light Data Model
draft-mirsky-ippm-twamp-light-yang-01
Abstract
This document specifies the data model for implementations of
Session-Sender and Session-Reflector for Two-Way Active Measurement
Protocol (TWAMP) Light mode using YANG.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 8, 2016.
Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Mirsky & Elteto Expires July 8, 2016 [Page 1]
Internet-Draft TWAMP Light data model January 2016
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Conventions used in this document . . . . . . . . . . . . 2
1.1.1. Requirements Language . . . . . . . . . . . . . . . . 2
2. Scope, Model, and Applicability . . . . . . . . . . . . . . . 3
2.1. Data Model Parameters . . . . . . . . . . . . . . . . . . 3
2.2. Session-Sender . . . . . . . . . . . . . . . . . . . . . 3
2.3. Session-Reflector . . . . . . . . . . . . . . . . . . . . 3
3. Data Model . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 4
3.2. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 4
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
5. Security Considerations . . . . . . . . . . . . . . . . . . . 9
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
7.1. Normative References . . . . . . . . . . . . . . . . . . 10
7.2. Informative References . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction
The Two-Way Active Measurement Protocol (TWAMP) [RFC5357] can be used
to measure performance parameters of IP networks such as latency,
jitter, and packet loss by sending test packets and monitoring their
experience in the network. The [RFC5357] defines two protocols,
TWAMP Control and TWAMP Test, and a profile of TWAMP Test, TWAMP
Light. The TWAMP Light is known to have many implementations though
no common management framework being defined, thus leaving some
aspects of test packet processing to interpretation. The goal of
this document is to collect analyze these variations; describe common
model while allowing for extensions in the future. This document
defines such a TWAMP data model and specifies it formally using the
YANG data modeling language [RFC6020].
1.1. Conventions used in this document
1.1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
[RFC2119].
Mirsky & Elteto Expires July 8, 2016 [Page 2]
Internet-Draft TWAMP Light data model January 2016
2. Scope, Model, and Applicability
The scope of this document includes model of the TWAMP Light as
defined in Appendix I of [RFC5357] as well as model of accepted
Errata. The former mode of TWAMP Light will be referred in this
document as Stateless and the latter - Stateful. This document
benefits from earlier attempt to define TWAMP MIB in
[I-D.elteto-ippm-twamp-mib] and from TWAMP YANG model defined in
[I-D.cmzrjp-ippm-twamp-yang].
Figure 1 updates TWAMP-Light reference model presented in Appendix I
[RFC5357] for the scenario when instantiation of a TWAMP-Test session
between Session-Sender and Session-Reflector controlled by
communication between a Configuration Client as a manager and
Configuration Servers as agents of the configuration session.
o----------------------------------------------------------o
| Config client |
o----------------------------------------------------------o
|| ||
|| NETCONF/RESTCONF ||
|| ||
o-------------------o o-------------------o
| Config server | | Config server |
| | | |
+-------------------+ +-------------------+
| Session-Sender | <--- TWAMP-Test ---> | Session-Reflector |
+-------------------+ +-------------------+
Figure 1: TWAMP Light Reference Model
2.1. Data Model Parameters
2.2. Session-Sender
TBA
2.3. Session-Reflector
TBA
3. Data Model
Creating TWAMP-Light data model presents number of challenges and
among them is identification of a test-session at Session-Reflector.
A Session-Reflector MAY require only as little as its IP and UDP port
Mirsky & Elteto Expires July 8, 2016 [Page 3]
Internet-Draft TWAMP Light data model January 2016
number in received TWAMP-Test packet to spawn new test session. More
so, to test processing of Class-of-Service along the same route in
Equal Cost Multi-Path environment Session-Sender may run TWAMP test
sessions concurrently using the same source IP address, source UDP
port number, destination IP address, and destination UDP port number.
Thus the only parameter that can be used to differentiate these test
sessions would be DSCP value. The DSCP field may get re-marked along
the path and without use of [I-D.ietf-ippm-type-p-monitor] that will
go undetected, but by using five-tuple instead of four-tuple as a key
we can ensure that TWAMP test packets that are considered as
differesnt test sessions follow the same path even in ECMP
environments.
3.1. Tree Diagram
TBA
3.2. YANG Module
<CODE BEGINS> file "ietf-twamp-light@2016-0105"
module ietf-twamp-light {
namespace "urn:ietf:params:xml:ns:yang:ietf-twamp-light";
//namespace need to be assigned by IANA
prefix "ietf-twamp-light";
import ietf-inet-types {
prefix inet;
}
organization
"IETF IPPM (IP Performance Metrics) Working Group";
contact
"draft-mirsky-ippm-twamp-light-yang@tools.ietf.org";
description "TWAMP Light Data Model";
revision "2016-01-05" {
description "01 version. RFC5357 is covered,
including Appendix I and the Errata.";
reference "draft-mirsky-ippm-twamp-light-yang";
}
feature sessionSenderLight {
description "This feature relates to the device functions as the
TWAMP Light Session-Sender.";
}
Mirsky & Elteto Expires July 8, 2016 [Page 4]
Internet-Draft TWAMP Light data model January 2016
feature sessionReflectorLight {
description "This feature relates to the device functions as the
TWAMP Light Session-Reflector.";
}
grouping maintenanceStatistics {
description "Maintenance statistics grouping";
leaf sentPackets {
type uint32;
default 0;
config "false";
description "Packets sent";
}
leaf rcvPackets {
type uint32;
default 0;
config "false";
description "Packets received";
}
leaf lastSentSeq {
type uint32;
default 0;
config "false";
description "Last sent sequence number";
}
leaf lastRcvSeq {
type uint32;
default 0;
config "false";
description "Last received sequence number";
}
}
grouping sessionLightParameters {
description "Parameters common among Session-Sender and
Session-Reflector.";
leaf senderIp {
type inet:ip-address;
description "Sender IP address";
}
leaf senderUdpPort {
type inet:port-number;
description "Sender UDP port number";
}
leaf reflectorIp {
type inet:ip-address;
description "Reflector IP address";
}
Mirsky & Elteto Expires July 8, 2016 [Page 5]
Internet-Draft TWAMP Light data model January 2016
leaf reflectorUdpPort {
type inet:port-number;
description "Reflector UDP port number";
}
leaf dscp {
type inet:dscp;
description "The DSCP value to be placed in the header of TWAMP
UDP
test packets generated by the Session-Sender. Whether
Session-Reflector uses this value depends upon its local
configuration.";
}
}
container twampLightSessionSender {
if-feature sessionSenderLight;
description "TWAMP-Light Session-Sender container";
list testSession {
key "senderIp senderUdpPort reflectorIp reflectorUdpPort dscp";
ordered-by system;
description "This structure is a container of test session
managed objects.";
leaf numberOfPackets {
type uint32;
description "The overall number of UDP test packets to be
transmitted by the sender for this test session.";
}
leaf packetPaddingSize {
type uint32;
default 27;
description "Size of the Packet Padding. Suggested to run
Path MTU Discovery
to avoid packet fragmentation in IPv4
and packet backholing in IPv6.";
}
leaf sessionAuthenticationMode {
type enumeration {
enum unathenticated {
description "Unauthenticated TWAMP-Light
test session";
}
enum authenticated {
description "Authenticated TWAMP-Light test session";
}
Mirsky & Elteto Expires July 8, 2016 [Page 6]
Internet-Draft TWAMP Light data model January 2016
enum encrypted {
description "Encrypted TWAMP-Light test session";
}
}
default unathenticated;
description "Authentication mode of the TWAMP-Light test
session."
;
}
leaf interval {
type uint32;
description "Time interval between transmission of two
consecuitive packets in the test session.";
}
leaf senderSessionState {
type enumeration {
enum active {
description "Test session is active.";
}
enum ready {
description "Test session is idle.";
}
}
default ready;
config "false";
description "State of the particulat TWAMP-Light test
session at the sender.";
}
uses maintenanceStatistics;
uses sessionLightParameters;
}
}
container twampLightSessionReflector {
if-feature sessionReflectorLight;
description "TWAMP-Light Session-Reflector container";
leaf reflectorLightState {
type boolean;
mandatory "true";
description "Whether this network element is enabled to
act as TWAMP-Light Reflector";
}
leaf refwait {
type uint32 {
range 1..604800;
Mirsky & Elteto Expires July 8, 2016 [Page 7]
Internet-Draft TWAMP Light data model January 2016
}
units seconds;
default 900;
description "REFWAIT(TWAMP test session timeout in seconds),
the default value is 900";
}
leaf reflectorLightMode {
type enumeration {
enum stateful {
description "When the Session-Reflector Light is stateful,
i.e. is aware of test session state.";
}
enum stateless {
description "when the Session-Reflector is statelss.";
}
}
default stateless;
description "Whether Session-Sender copies sequence number
of received TWAMP-Test packet, i.e. Stateless, or counts
reflected TWAMP-Test packets and restarts counter based on
external event.";
}
leaf dscpHandlingMode {
type enumeration {
enum copyReceivedValue {
description "Use DSCP value copied from received TWAMP
test packet of the test session.";
}
enum useConfiguredValue {
description "Use DSCP value configured for this test
session on the Session-Reflector.";
}
}
default copyReceivedValue;
description "Session-Reflector handling of DSCP:
- use value copied from received TWAMP-Test packet;
- use value explicitly configued.";
}
list testSession {
key "senderIp senderUdpPort reflectorIp reflectorUdpPort dscp";
ordered-by system;
description "This structure is a container of test session
managed objects.";
uses maintenanceStatistics;
uses sessionLightParameters;
Mirsky & Elteto Expires July 8, 2016 [Page 8]
Internet-Draft TWAMP Light data model January 2016
}
}
}
}
<CODE ENDS>
4. IANA Considerations
This document registers a URI in the IETF XML registry [RFC3688].
Following the format in [RFC3688], the following registration is
requested to be made.
URI: urn:ietf:params:xml:ns:yang:ietf-twamp-light
Registrant Contact: The IPPM WG of the IETF.
XML: N/A, the requested URI is an XML namespace.
This document registers a YANG module in the YANG Module Names
registry [RFC6020].
name: ietf-twamp-light
namespace: urn:ietf:params:xml:ns:yang:ietf-twamp-light
prefix: twamp
reference: RFC XXXX
5. Security Considerations
The configuration, state, action data defined in this document may be
accessed via the NETCONF protocol [RFC6241]. SSH [RFC6242] is
mandatory secure transport that is the lowest NETCONF layer. The
NETCONF access control model [RFC6536] provides means to restrict
access for particular NETCONF users to a pre-configured subset of all
available NETCONF protocol operations and content.
But, in general, this TWAMP Light YANG module does not change any
underlying security issues that already may exhist in
[I-D.elteto-ippm-twamp-mib].
6. Acknowledgements
Mirsky & Elteto Expires July 8, 2016 [Page 9]
Internet-Draft TWAMP Light data model January 2016
7. References
7.1. Normative References
[I-D.cmzrjp-ippm-twamp-yang]
Civil, R., Morton, A., Zheng, L., Rahman, R.,
Jethanandani, M., and K. Pentikousis, "Two-Way Active
Measurement Protocol (TWAMP) Data Model", draft-cmzrjp-
ippm-twamp-yang-02 (work in progress), October 2015.
[I-D.elteto-ippm-twamp-mib]
Elteto, T. and G. Mirsky, "Two-Way Active Measurement
Protocol (TWAMP) Management Information Base (MIB)",
draft-elteto-ippm-twamp-mib-01 (work in progress), January
2014.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004,
<http://www.rfc-editor.org/info/rfc3688>.
[RFC5357] Hedayat, K., Krzanowski, R., Morton, A., Yum, K., and J.
Babiarz, "A Two-Way Active Measurement Protocol (TWAMP)",
RFC 5357, DOI 10.17487/RFC5357, October 2008,
<http://www.rfc-editor.org/info/rfc5357>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010,
<http://www.rfc-editor.org/info/rfc6020>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<http://www.rfc-editor.org/info/rfc6241>.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
<http://www.rfc-editor.org/info/rfc6242>.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536,
DOI 10.17487/RFC6536, March 2012,
<http://www.rfc-editor.org/info/rfc6536>.
Mirsky & Elteto Expires July 8, 2016 [Page 10]
Internet-Draft TWAMP Light data model January 2016
7.2. Informative References
[I-D.ietf-ippm-type-p-monitor]
Hedin, J., Mirsky, G., and S. Baillargeon, "Differentiated
Service Code Point and Explicit Congestion Notification
Monitoring in Two-Way Active Measurement Protocol
(TWAMP)", draft-ietf-ippm-type-p-monitor-03 (work in
progress), November 2015.
Authors' Addresses
Greg Mirsky
Ericsson
Email: gregory.mirsky@ericsson.com
Tamas Elteto
Ericsson
Email: tamas.elteto@ericsson.com
Mirsky & Elteto Expires July 8, 2016 [Page 11]