Tracing process in IPv6 VPN Tunneling Networks
draft-peng-6man-tracing-option-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Yuanyang Yin , Shuping Peng , zhaoranxiao | ||
| Last updated | 2022-12-30 (Latest revision 2022-06-28) | ||
| RFC stream | (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 specifies the tracing process in IPv6 VPN tunneling networks for diagnostic purposes. An IPv6 Tracing Option is specified to collect and carry the required key information in an effective manner to correctly construct ICMPv4 and ICMPv6 Time Exceeded messages at the corresponding nodes, i.e. PE and P nodes, respectively.
Authors
Yuanyang Yin
Shuping Peng
zhaoranxiao
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)