AERO Minimal Encapsulation
draft-templin-aeromin-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Fred Templin | ||
| Last updated | 2016-07-21 (Latest revision 2016-01-08) | ||
| 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
Asymmetric Extended Route Optimization (AERO) specifies both a control messaging and data packet forwarding facility for managing tunnels over an enterprise network or other Internetwork. Although AERO can operate with any tunnel encapsulation format, the base document considers Generic UDP Encapsulation (GUE) as the default. This document presents minimal encapsulation formats for AERO using other encapsulation types.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)