One document matched: draft-mirsky-ippm-twamp-light-yang-00.xml
<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd"[
<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC2629 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2629.xml">
<!ENTITY RFC6020 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6020.xml">
<!ENTITY RFC3688 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3688.xml">
<!ENTITY RFC5357 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5357.xml">
<!ENTITY RFC6241 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6241.xml">
<!ENTITY RFC6242 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6242.xml">
<!ENTITY RFC6536 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6536.xml">
<!ENTITY I-D.cmzrjp-ippm-twamp-yang SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.draft-cmzrjp-ippm-twamp-yang-01.xml">
<!ENTITY I-D.ietf-ippm-type-p-monitor SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.draft-ietf-ippm-type-p-monitor-02.xml">
]>
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="3"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<rfc category="std" ipr="trust200902" docName="draft-mirsky-ippm-twamp-light-yang-00">
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<front>
<title abbrev='TWAMP Light data model'>Two-Way Active Measurement Protocol (TWAMP) Light Data Model</title>
<author initials='G.' surname="Mirsky" fullname='Greg Mirsky'>
<organization>Ericsson</organization>
<address>
<email>gregory.mirsky@ericsson.com</email>
</address>
</author>
<author initials='T.' surname="Elteto" fullname='Tamas Elteto'>
<organization>Ericsson</organization>
<address>
<email>tamas.elteto@ericsson.com</email>
</address>
</author>
<date day="6" month="July" year="2015"/>
<area>Transport</area>
<workgroup>Network Working Group</workgroup>
<keyword>Internet-Draft</keyword>
<keyword>IPPM</keyword>
<keyword>TWAMP </keyword>
<keyword>YANG</keyword>
<abstract>
<t>
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.
</t>
</abstract>
</front>
<middle>
<section anchor="intro" title="Introduction">
<t>
The Two-Way Active Measurement Protocol (TWAMP) <xref target="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 <xref target="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 <xref target="RFC6020"/>.
</t>
<section title="Conventions used in this document">
<!--
<section title="Terminology">
<t>IPPM: IP Performance Measurement
</t>
<t>TWAMP: Two-Way Active Measurement Protocol
</t>
</section>
-->
<section title="Requirements Language">
<t>
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
<xref target="RFC2119"/>.
</t>
</section>
</section>
</section>
<section anchor="scope-model-applicability" title="Scope, Model, and Applicability">
<t>
The scope of this document includes model of the TWAMP Light as defined in Appendix I of
<xref target="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 <xref target="I-D.elteto-ippm-twamp-mib"/> and from
TWAMP YANG model defined in <xref target="I-D.cmzrjp-ippm-twamp-yang"/>.
</t>
<t>
<xref target="TWAMP-light"/> updates TWAMP-Light reference model presented in Appendix I <xref target="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.
</t>
<figure align="left" anchor="TWAMP-light"
title="TWAMP Light Reference Model">
<artwork>
<![CDATA[
o----------------------------------------------------------o
| Config client |
o----------------------------------------------------------o
|| ||
|| NETCONF/RESTCONF ||
|| ||
o-------------------o o-------------------o
| Config server | | Config server |
| | | |
+-------------------+ +-------------------+
| Session-Sender | <--- TWAMP-Test ---> | Session-Reflector |
+-------------------+ +-------------------+
]]>
</artwork>
</figure>
<section anchor="data-model-parameters" title="Data Model Parameters">
<t>
</t>
</section>
<section anchor="session-sender" title="Session-Sender">
<t>
TBA
</t>
</section>
<section anchor="session-reflector" title="Session-Reflector">
<t>
TBA
</t>
</section>
</section>
<section anchor="data-model" title="Data Model">
<t>
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 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 <xref target="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.
</t>
<section anchor="tree-diagram" title="Tree Diagram">
<t>TBA
</t>
</section>
<section anchor="yang-module" title="YANG Module">
<t>
<figure>
<artwork>
<![CDATA[
module twampLight {
namespace "urn:ietf:params:xml:ns:yang:ietf-twamp";
//namespace need to be assigned by IANA
prefix "twampLight";
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 "2015-07-06" {
description "Initial version. RFC5357 is covered,
including Appendix I and the Errata.";
}
feature sessionSenderLight {
description "This feature relates to the device functions as the
TWAMP Light Session-Sender.";
}
feature sessionReflectorLight {
description "This feature relates to the device functions as the
TWAMP Light Session-Reflector.";
}
grouping maintenanceStatistics {
leaf sentPackets {
config "false";
default 0;
type uint32;
}
leaf rcvPackets {
config "false";
default 0;
type uint32;
}
leaf lastSentSeq {
config "false";
default 0;
type uint32;
}
leaf lastRcvSeq {
config "false";
default 0;
type uint32;
}
}
grouping sessionLightParameters {
description "Parameters common among Session-Sender and
Session-Reflector.";
leaf senderIp {
type inet:ip-address;
}
leaf senderUdpPort {
type inet:port-number;
}
leaf reflectorIp {
type inet:ip-address;
}
leaf reflectorUdpPort {
type inet:port-number;
}
leaf 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.";
type inet:dscp;
}
}
container twampLightSessionSender {
if-feature sessionSender;
list testSession {
key "senderIp senderUdpPort reflectorIp reflectorUdpPort dscp";
ordered-by system;
status current;
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;
enum authenticated;
enum encrypted;
}
default unathenticated;
description "Authentication mode of the TWAMP Light test
session."
}
leaf interval {
type uint32 {
description "Time interval between transmission of two
consequitive pakcets 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";
}
uses maintenanceStatistics;
uses sessionLightParameters;
}
}
container twampLightSessionReflector {
if-feature sessionReflector;
leaf refwait {
config "true";
type uint32 {
range 1..604800;
}
units seconds;
default 900;
description "REFWAIT(TWAMP test session timeout in seconds),
the default value is 900";
}
leaf reflectorLightMode {
type enumeration {
enum stateful {
status current;
description "When the Session-Reflector Light is stateful,
i.e. is aware of test session state.";
}
enum stateless {
status current;
description "when the Session-Reflector is statelss.";
}
}
default stateless;
status current;
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 {
status current;
description "Use DSCP value copied from received TWAMP
test packet of the test session.";
}
enum useConfiguredValue {
status current;
description "Use DSCP value configured for this test
session on the Session-Reflector.";
}
}
status current;
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;
status current;
description "This structure is a container of test session
managed objects.";
uses maintenanceStatistics;
uses sessionLightParameters;
}
}
}
}
]]></artwork>
</figure>
</t>
</section>
</section>
<section anchor="iana-consider" title="IANA Considerations">
<t>
This document registers a URI in the IETF XML registry <xref target="RFC3688"/>.
Following the format in <xref target="RFC3688"/>, the following registration is
requested to be made.
</t>
<t>
URI: urn:ietf:params:xml:ns:yang:ietf-twamp-light
</t>
<t>
Registrant Contact: The IPPM WG of the IETF.
</t>
<t>
XML: N/A, the requested URI is an XML namespace.
</t>
<t>
This document registers a YANG module in the YANG Module Names
registry <xref target="RFC6020"/>.
</t>
<t>
name: ietf-twamp-light
</t>
<t>
namespace: urn:ietf:params:xml:ns:yang:ietf-twamp-light
</t>
<t>
prefix: twamp
</t>
<t>
reference: RFC XXXX
</t>
</section>
<section anchor="security" title="Security Considerations">
<t>
The configuration, state, action data defined in
this document may be accessed via the NETCONF protocol
<xref target="RFC6241"/>. SSH <xref target="RFC6242"/> is mandatory secure transport
that is the lowest NETCONF layer.
The NETCONF access control model <xref target="RFC6536"/> provides means to restrict
access for particular NETCONF users to a pre-configured subset of all
available NETCONF protocol operations and content.
</t>
<!--
<t>
There are a number of data nodes defined in the TWAMP Light YANG
module that are writable/creatable/deletable. These data nodes may be considered sensitive
or vulnerable in some network environments. Write operations (e.g.,
edit-config) to these data nodes without proper protection can have a
negative effect on network operations.
</t>
-->
<t>
But, in general, this TWAMP Light YANG module does not change
any underlying security issues that already may exhist in
<xref target="I-D.elteto-ippm-twamp-mib"/>.
</t>
</section>
<section title="Acknowledgements">
<t>
</t>
</section>
</middle>
<back>
<references title="Normative References">
<?rfc include="reference.RFC.2119"?>
<?rfc include='reference.I-D.elteto-ippm-twamp-mib'?>
&I-D.cmzrjp-ippm-twamp-yang;
&RFC6020;
&RFC3688;
&RFC5357;
&RFC6241;
&RFC6242;
&RFC6536;
</references>
<references title="Informative References">
&I-D.ietf-ippm-type-p-monitor;
</references>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-23 09:35:36 |