VxLAN Router Alert Option
draft-singh-nvo3-vxlan-router-alert-02
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Kanwar Singh , Pradeep Jain , Diego Garcia del Rio , Wim Henderickx , Ravi Shekhar , Reshad Rahman | ||
Last updated | 2016-04-04 (Latest revision 2015-09-21) | ||
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 VxLAN terminating VTEP to more closely examine the contents of the packet encapsulated under VxLAN header. This option is useful for case(s) where a given frame encapsulated within a given VXLAN segment responsible for carrying data between two different End Systems contains some control information (e.g OAM information, any control plane protocol packet etc.) that may require special handling/processing by terminating VTEP.
Authors
Kanwar Singh
Pradeep Jain
Diego Garcia del Rio
Wim Henderickx
Ravi Shekhar
Reshad Rahman
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)