Internet Control Message Protocol (ICMPv6) Reflection
draft-mh-6man-icmpv6-reflection-01
| Document | Type |
Replaced Internet-Draft
(6man WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Tal Mizrahi , hexiaoming , Tianran Zhou , Ron Bonica , Xiao Min | ||
| Last updated | 2025-01-06 (Latest revision 2024-10-09) | ||
| Replaced by | draft-ietf-6man-icmpv6-reflection | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Proposed Standard | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-6man-icmpv6-reflection | |
| Consensus boilerplate | Yes | ||
| 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 the ICMPv6 Reflection utility. ICMPv6 Reflection uses a request-response handshake that is similar to ICMPv6 Echo, except that after a request is sent, the corresponding reply includes the request message itself or a subset of its fields as specified in the request. Specifically, the IPv6 header of the request message and its IPv6 extension headers, if they are present, can be included in the reply. Network operators can use ICMPv6 Reflection to determine how IPv6 extension headers have been altered by transit nodes.
Authors
Tal Mizrahi
hexiaoming
Tianran Zhou
Ron Bonica
Xiao Min
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)