Extensible In-band Processing (EIP) Headers Definitions
draft-eip-headers-definitions-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Stefano Salsano , Andrea Mayer | ||
| Last updated | 2026-09-19 (Latest revision 2026-03-18) | ||
| 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
This document discusses the format of EIP protocol elements and the transport of EIP in different IPv6-based protocol headers. In particular, this document defines the standalone EIP formats for the IPv6 Hop-by-Hop Options Header and for the Segment Routing Header, and it defines the generic format of EIP Information Elements. Other approaches to transport EIP, including integration with the IOAM framework through the Global Opaque Block (GOB), are described in separate documents. Caveat: this document is still in brainstorming stage, it is distributed to stimulate discussion.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)