Simple Two-way Active Measurement Protocol Extensions for Hop-by-Hop OAM Data Collection
draft-wang-ippm-stamp-hbh-extensions-02
IP Performance Measurement Group Y. Wang
Internet-Draft T. Zhou
Intended status: Standards Track Huawei
Expires: May 19, 2021 H. Yang
China Mobile
C. Liu
China Unicom
November 15, 2020
Simple Two-way Active Measurement Protocol Extensions for Hop-by-Hop OAM
Data Collection
draft-wang-ippm-stamp-hbh-extensions-02
Abstract
This document defines optional TLVs which are carried in Simple Two-
way Active Measurement Protocol (STAMP) test packets to enhance the
STAMP base functions. Such extensions to STAMP enable OAM data
measurement and collection at every node and link along a STAMP test
packet's delivery path without maintaining a state for each
configured STAMP-Test session at every devices.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
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 https://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 May 19, 2021.
Wang, et al. Expires May 19, 2021 [Page 1]
Internet-Draft draft-wang-ippm-stamp-hbh-extensions-02 November 2020
Copyright Notice
Copyright (c) 2020 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
(https://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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. TLV Extensions to STAMP . . . . . . . . . . . . . . . . . . . 3
3.1. IOAM Tracing Data TLV . . . . . . . . . . . . . . . . . . 3
3.2. Forward HbH Delay TLV . . . . . . . . . . . . . . . . . . 5
3.3. Backward HbH Delay TLV . . . . . . . . . . . . . . . . . 7
3.4. HbH Packet Loss TLV . . . . . . . . . . . . . . . . . . . 9
3.5. HbH Bandwidth Utilization TLV . . . . . . . . . . . . . . 11
3.6. HbH Timestamp Information TLV . . . . . . . . . . . . . . 12
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
5. Security Considerations . . . . . . . . . . . . . . . . . . . 14
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
7.1. Normative References . . . . . . . . . . . . . . . . . . 15
7.2. Informative References . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction
Simple Two-way Active Measurement Protocol (STAMP) [RFC8762] enables
the measurement of both one-way and round-trip performance metrics,
such as delay, delay variation, and packet loss. In the STAMP
session, the bidirectional packet flow is transmitted between STAMP
Session-Sender and STAMP Session-Reflector. The STAMP Session-
Reflector receives test packets transmitted from Session-Sender and
acts according to the configuration. However, the performance of
intermediate nodes and links that STAMP test packets traverse are
invisible. In addition, the STAMP instance must be configured at
every intermediate node to measure the performance per node and link
that test packets traverse, which increases the complexity of OAM in
large-scale networks.
Wang, et al. Expires May 19, 2021 [Page 2]
Show full document text