[Docs] [txt|pdf|xml] [Tracker] [Email] [Nits]

Versions: 00

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


                       NVGRE Router Alert Option
                 draft-singh-nvo3-nvgre-router-alert-00

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.

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          NVGRE 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.  Ingress NVGRE End Point Procedure  . . . . . . . . . . . .  6
     3.2.  Egress NVGRE End Point 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          NVGRE 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          NVGRE Router Alert Option               May 2013


1.  Introduction

   NVGRE [I-D.draft-sridharan-virtualization-nvgre]is a tunneling
   mechanism to overlay Layer 2 networks on top of Layer 3 networks.
   NVGRE tunnel consists for two NVGRE End Points (Ingress/Egress)
   between virtual and physical networks.  End Point can be any Physical
   Server or netowrk device.  In most common deployments the NVGRE End
   Points are on hypervisor(s).  The primary function of this endpoint
   is to encapsulate/decapsulate Ethernet data frames to and from the
   GRE tunnel, and apply isolation policy scoped on VSID.  In most cases
   the end point of the NVGRE tunnel 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.

   NVGRE end point encapsulates End System data at the GRE tunnel
   origination node and carries it over L3 network to the GRE tunnel
   terminating node, where NVGRE 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 NVGRE originating end point needs to encapsulate some
   control information for a given NVGRE tunnel, and this control
   information needs to be analyzed and processed at the terminating
   NVGRE end point.

   This document defines a mechanism whereby Originating NVGRE end point
   can add additional information to the GRE header, based upon which
   the Terminating NVGRE end point can decide to analyze the payload
   under GRE encapsulated packet, rather then forwarding it to the
   destination End System.



















Singh, et al.           Expires November 25, 2013               [Page 4]


Internet-Draft          NVGRE Router Alert Option               May 2013


2.  Terminology

   Terminology used in this document:

   NVGRE: Network Virtualization using GRE.

   NVGRE End Point: Ingress/egress points between the virtual and the
   physical networks.  Any physical server, physical/virtual access
   switch or network device can be a NVGRE endpoint.

   VSID: Virtual Subnet ID.

   NVGRE Segment: NVGRE tunnel which is responsible for carrying data
   between two different End Systems, e.g.  VMs.  All frames going
   within a NVGRE Segment would have same VSID

   End System: Could be VM etc. - System whose data is expected to go
   over NVGRE Segment.

   OAM: Operations, Administration, and Maintenance

   Other terminologies are as defined in
   [I-D.draft-sridharan-virtualization-nvgre].




























Singh, et al.           Expires November 25, 2013               [Page 5]


Internet-Draft          NVGRE Router Alert Option               May 2013


3.  Approach

   If the Originating NVGRE end point decides to generate control
   information, which needs to go over a given NVGRE segment and if the
   Terminating NVGRE end point needs to analyze and process it, then
   following procedures have to be followed at Originating and
   Terminating NVGRE End Point(s):-

3.1.  Ingress NVGRE End Point Procedure

   When creating the NVGRE header for a given NVGRE segment, the
   Originating NVGRE end point MUST set Router Alert Bit (proposed) as
   one of the bits in Reserved0 filed of NVGRE header.  The VSID for
   this frame MUST be the same as for the given NVGRE segment which
   carries the data traffic of the End System.


       GRE Header:
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |0| |1|0| Reserved0     RA| Ver |   Protocol Type 0x6558        |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |               Virtual Subnet ID (VSID)        |   Reserved    |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

       RA: Router Alter Bit (Proposed)

3.2.  Egress NVGRE End Point Procedure

   On receiving NVGRE frame, the Terminating NVGRE end point would do
   the usual NVGRE processing as defined in
   [I-D.draft-sridharan-virtualization-nvgre], but if the RA Bit
   (proposed) in Reserved0 filed 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          NVGRE Router Alert Option               May 2013


4.  Management Considerations

   None
















































Singh, et al.           Expires November 25, 2013               [Page 7]


Internet-Draft          NVGRE Router Alert Option               May 2013


5.  Security Considerations

   TBD
















































Singh, et al.           Expires November 25, 2013               [Page 8]


Internet-Draft          NVGRE Router Alert Option               May 2013


6.  Acknowledgements

   The authors want to thank Diego Garcia Del Rio and Suresh Boddapati
   of Nuage Networks for significant contribution and feedback.















































Singh, et al.           Expires November 25, 2013               [Page 9]


Internet-Draft          NVGRE Router Alert Option               May 2013


7.  IANA Considerations

   Router Alter Bit (RA): IANA is request to assign 1 Bit in the
   Reserved0 field of NVGRE Header to communicate NVGRE Router Alert
   information.














































Singh, et al.           Expires November 25, 2013              [Page 10]


Internet-Draft          NVGRE 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-sridharan-virtualization-nvgre]
              Sridharan, M., Duda, K., Greenberg, A., Lin, G., Pearson,
              M., Thaler, P., Tumuluri, C., Venkataramiah, N., and Y.
              Wang, "NVGRE: Network Virtualization using Generic Routing
              Encapsulation", February 2013.

   [RFC2784]  Farinacci, D., Li, T., Hanks, S., Meyer, D., and P.
              Traina, "Generic Routing Encapsulation (GRE)", RFC 2784,
              March 2000.

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          NVGRE 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]


Html markup produced by rfcmarkup 1.128b, available from https://tools.ietf.org/tools/rfcmarkup/