AERO Minimal Encapsulation
draft-templin-aeromin-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Author | Fred Templin | ||
| Last updated | 2015-05-14 (Latest revision 2014-11-10) | ||
| RFC stream | (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 facility and an encapsulation format for managing tunnels over an enterprise network or other Internetwork. Although AERO can operate with any tunnel encapsulation format, the base document considers IP-in-UDP-in-IP encapsulation as the default. This document presents a minimal encapsulation format for AERO for use when a UDP header is not needed.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)