Encapsulation of Simple TWAMP (STAMP) for Pseudowires in MPLS Networks
draft-gandhi-mpls-stamp-pw-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Rakesh Gandhi , Patrice Brissette , Eddie Leyton | ||
| Last updated | 2022-01-13 (Latest revision 2021-07-12) | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| 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
Pseudowires (PWs) are used in MPLS networks for various services including carrying layer 2 and layer 3 data packets. This document describes the procedure for encapsulation of the Simple Two-Way Active Measurement Protocol (STAMP) defined in RFC 8762 and its optional extensions defined in RFC 8972 for PWs in MPLS networks. The procedure uses PW Generic Associated Channel (G-ACh) to encapsulate the STAMP test packets with or without an IP/UDP header.
Authors
Rakesh Gandhi
Patrice Brissette
Eddie Leyton
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)