Protocol Extension Requirements of Generalized IPv6 Tunnel
draft-li-rtgwg-gip6-protocol-ext-requirements-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Zhenbin Li , Tianran Zhou , Shuping Peng , yixinxin | ||
| Last updated | 2023-05-10 (Latest revision 2022-11-06) | ||
| 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
IPv6 provides extension header mechanism for additional functions. There are emerging features based on the extension headers, such as SRv6, Slicing, Alternate Marking, IOAM, DetNet, APN. However network devices have different capabilities of IPv6 extension header processing which has much effect on the deployment of these features. This document analyses the issues found during the deployment of the above new features using IPv6 extension headers and the protocol extension requirements for IPv6 capability advertisement are defined.
Authors
Zhenbin Li
Tianran Zhou
Shuping Peng
yixinxin
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)