NVO3 K. Singh
Internet-Draft P. Jain
Intended status: Standards Track F. Balus
Expires: November 25, 2013 Nuage Networks.
W. Henderickx
Alcatel-Lucent, Inc.
May 24, 2013
VxLAN Router Alert Option
draft-singh-nvo3-vxlan-router-alert-00
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) that
may require special handling/processing by terminating VTEP.
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 25, 2013.
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
Singh, et al. Expires November 25, 2013 [Page 1]
Internet-Draft VxLAN Router Alert Option May 2013
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Approach . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.1. Originating VTEP Procedure . . . . . . . . . . . . . . . . 6
3.2. Terminating VTEP Procedure . . . . . . . . . . . . . . . . 6
4. Management Considerations . . . . . . . . . . . . . . . . . . 7
5. Security Considerations . . . . . . . . . . . . . . . . . . . 8
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
8.1. Normative References . . . . . . . . . . . . . . . . . . . 11
8.2. Informative References . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12
Singh, et al. Expires November 25, 2013 [Page 2]
Internet-Draft VxLAN Router Alert Option May 2013
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC2119 [RFC2119].
When used in lower case, these words convey their typical use in
common language, and are not to be interpreted as described in
RFC2119 [RFC2119].
Singh, et al. Expires November 25, 2013 [Page 3]
Internet-Draft VxLAN Router Alert Option May 2013
1. Introduction
VXLAN [I-D.draft-mahalingam-dutt-dcops-vxlan]is a tunneling mechanism
to overlay Layer 2 networks on top of Layer 3 networks. In most
cases the end point of the tunnel (VTEP) is intended to be at the
edge of the network, typically connecting an access switch to an IP
transport network. The access switch could be a physical or a
virtual switch located within the hypervisor on the server which is
connected to End System which is a VM.
VXLAN segment encapsulates End System data at Originating VTEP and
carries it over L3 network to the Terminating VTEP, where VXLAN
header is interpreted, removed and data is passed on to the End
System.
There could be some scenarios like for case of OAM, where the network
element at originating VTEP needs to encapsulate some control
information for a given VXLAN segment, and this control information
needs to be analyzed and processed at the terminating VTEP for that
VXLAN segment.
This document defines a mechanism whereby Originating VTEP can add
additional information to the VXLAN header, based upon which the
Terminating VTEP can decide to analyze the payload under VXLAN
packet, rather then forwarding it to the destination End System.
Singh, et al. Expires November 25, 2013 [Page 4]
Internet-Draft VxLAN Router Alert Option May 2013
2. Terminology
Terminology used in this document:
VXLAN: Virtual eXtensible Local Area Network.
VTEP: VXLAN Tunnel End Point.
VM: Virtual Machine.
End System: Could be VM etc. - System whose data is expected to go
over VXLAN Segment.
OAM: Operations, Administration, and Maintenance
Other terminologies are as defined in
[I-D.draft-mahalingam-dutt-dcops-vxlan].
Singh, et al. Expires November 25, 2013 [Page 5]
Internet-Draft VxLAN Router Alert Option May 2013
3. Approach
If the Originating VTEP decides to generate control informtaion,
which needs to go over a given VXLAN segment and if the Terminating
VTEP needs to analyze and process it, then following procedures have
to be followed at Originating and Terminating VTEP(s):-
3.1. Originating VTEP Procedure
When creating the VXLAN header for a given VXLAN segment, the
Originating VTEP MUST set Router Alert Bit in the Flag bits in VXLAN
header. The VNI for this frame MUST be the same as for the given
VXLAN segment which carries the data traffic of the End System.
VXLAN Header:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|R|R|R|R|I|R|R|RA| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| VXLAN Network Identifier (VNI) | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
RA: Router Alter Bit (Proposed)
3.2. Terminating VTEP Procedure
On receiving VXLAN frame, the Terminating VTEP would do the usual
VXLAN processing as defined in
[I-D.draft-mahalingam-dutt-dcops-vxlan], but if the RA Bit in Flags
is Set it MUST send the rest of the inner frame for further
processing to the above application. The details of the applications
and how it would process the inner frame is outside the scope of this
document. This frame MUST not be sent to the target End System.
Singh, et al. Expires November 25, 2013 [Page 6]
Internet-Draft VxLAN Router Alert Option May 2013
4. Management Considerations
None
Singh, et al. Expires November 25, 2013 [Page 7]
Internet-Draft VxLAN Router Alert Option May 2013
5. Security Considerations
TBD
Singh, et al. Expires November 25, 2013 [Page 8]
Internet-Draft VxLAN Router Alert Option May 2013
6. Acknowledgements
The authors want to thank Diego Garcia Del Rio and Suresh Boddapati
of Nuage Networksfor significant contribution and feedback.
Singh, et al. Expires November 25, 2013 [Page 9]
Internet-Draft VxLAN Router Alert Option May 2013
7. IANA Considerations
Router Alter Bit (RA): IANA is request to assing 1 Bit in Flags field
of VXLAN Header to communicate VXLAN Router Alert information.
Singh, et al. Expires November 25, 2013 [Page 10]
Internet-Draft VxLAN Router Alert Option May 2013
8. References
8.1. Normative References
[I-D.draft-lasserre-nvo3-framework]
Lasserre, M., Balus, F., Morin, T., Bitar, N., and Y.
Rekhter, "Framework for DC Network Virtualization",
September 2011.
[I-D.draft-mahalingam-dutt-dcops-vxlan]
Mahalingam, M., Dutt, D., Agarwal, P., Kreeger, L.,
Sridhar, T., Bursell, M., and C. Wright, "VXLAN: A
Framework for Overlaying Virtualized Layer 2 Networks
over Layer 3 Networks", May 2013.
8.2. Informative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
Singh, et al. Expires November 25, 2013 [Page 11]
Internet-Draft VxLAN Router Alert Option May 2013
Authors' Addresses
Kanwar Singh
Nuage Networks.
755 Ravendale Drive
Mountain View, CA 94043
USA
Email: kanwar@nuagenetworks.net
Pradeep Jain
Nuage Networks.
755 Ravendale Drive
Mountain View, CA 94043
USA
Email: pradeep@nuagenetworks.net
Florin Balus
Nuage Networks.
755 Ravendale Drive
Mountain View, CA 94043
USA
Email: florin@nuagenetworks.net
Wim Henderickx
Alcatel-Lucent, Inc.
Copernicuslaan 50, 2018
ANTWERP 2018
BELGIUM
Email: Wim.Henderickx@alcatel-lucent.com
Singh, et al. Expires November 25, 2013 [Page 12]