Control and Monitoring Differentiated Service Code Point in Two-Way Active Measurement Protocol (TWAMP)
draft-bailmir-ippm-twamp-dscp-ctrl-mon-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Greg Mirsky , Steve Baillargeon | ||
| Last updated | 2017-08-25 (Latest revision 2017-02-21) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes an optional extension for Two-Way Active Measurement Protocol (TWAMP) allowing control and monitoring of the Differentiated Service Code Point (DSCP) field in forward and reverse directions within single test session with the TWAMP-Test protocol. This document, if accepted, will be an update to the TWAMP core protocol specified in RFC 5357 and DSCP Monitoring mode defined in RFC 7750 .
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)