NVGRE Router Alert Option
draft-singh-nvo3-nvgre-router-alert-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Kanwar Singh , Pradeep Jain , Florin Balus , Wim Henderickx | ||
| Last updated | 2013-11-25 (Latest revision 2013-05-24) | ||
| 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 proposal describes a new option to achieve a mechanism which alerts NVGRE egress End Point to more closely examine the contents of the packet encapsulated under NVGRE header. This option is useful for case(s) where a given frame encapsulated within a given NVGRE segment responsible for carrying data between two different End Systems contains some control information (e.g OAM information) that may require special handling/processing at NVGRE egress End Point.
Authors
Kanwar Singh
Pradeep Jain
Florin Balus
Wim Henderickx
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)