Identifying Addresses of IPv6 Tunnel Packets at Tunnel Exit-point
draft-liu-6man-ident-tunnel-packet-addr-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jianping Wu , Cong Liu , Yong Cui | ||
| Last updated | 2014-04-24 (Latest revision 2013-10-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
In the networks where IPv6 tunneling is used, it is not specific about how a tunnel end-node identifies the received tunnel packets by checking the destination and source addresses. when the tunnel end- node is configured with multiple IPv6 addresses or multiple IPv6 tunnel instances, such identification is necessary. This document describes the problem and defines the behavior of IPv6 tunnel end- nodes about identifying tunnel packets.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)