One document matched: draft-singh-nvo3-nvgre-router-alert-00.xml
<?xml version="1.0" encoding="US-ASCII"?>
<!-- edited with XMLSPY v5 rel. 4 U (http://www.xmlspy.com) by Fred Baker (private) -->
<!DOCTYPE rfc SYSTEM "http://xml.resource.org/authoring/rfc2629.dtd">
<?rfc toc="yes"?>
<?rfc tocompact="no"?>
<?rfc tocdepth="6"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<rfc category="std" docName="draft-singh-nvo3-nvgre-router-alert-00"
ipr="trust200902">
<front>
<title abbrev="NVGRE Router Alert Option">NVGRE Router Alert Option</title>
<author fullname="Kanwar Singh" initials="K." surname="Singh">
<organization>Nuage Networks.</organization>
<address>
<postal>
<street>755 Ravendale Drive</street>
<city>Mountain View, CA</city>
<code>94043</code>
<country>USA</country>
</postal>
<email>kanwar@nuagenetworks.net</email>
</address>
</author>
<author fullname="Pradeep Jain" initials="P." surname="Jain">
<organization>Nuage Networks.</organization>
<address>
<postal>
<street>755 Ravendale Drive</street>
<city>Mountain View, CA</city>
<code>94043</code>
<country>USA</country>
</postal>
<email>pradeep@nuagenetworks.net</email>
</address>
</author>
<author fullname="Florin Balus" initials="F." surname="Balus">
<organization>Nuage Networks.</organization>
<address>
<postal>
<street>755 Ravendale Drive</street>
<city>Mountain View, CA</city>
<code>94043</code>
<country>USA</country>
</postal>
<email>florin@nuagenetworks.net</email>
</address>
</author>
<author fullname="Wim Henderickx" initials="W."
surname="Henderickx">
<organization>Alcatel-Lucent, Inc.</organization>
<address>
<postal>
<street>Copernicuslaan 50, 2018 </street>
<city>ANTWERP</city>
<code>2018</code>
<country>BELGIUM</country>
</postal>
<email>Wim.Henderickx@alcatel-lucent.com</email>
</address>
</author>
<date day="24" month="May" year="2013" />
<area>Internet Area</area>
<workgroup>NVO3</workgroup>
<abstract>
<t>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.</t>
</abstract>
</front>
<middle>
<t>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 <xref
target="RFC2119" />.</t>
<t>When used in lower case, these words convey their typical use in common
language, and are not to be interpreted as described in RFC2119 <xref
target="RFC2119" />.</t>
<section title="Introduction">
<t>NVGRE <xref target="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. </t>
<t>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.</t>
<t>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.</t>
<t>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.</t>
</section>
<section title="Terminology">
<t>Terminology used in this document:</t>
<t>NVGRE: Network Virtualization using GRE.</t>
<t>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.</t>
<t>VSID: Virtual Subnet ID.</t>
<t>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</t>
<t>End System: Could be VM etc. - System whose data is expected to go over
NVGRE Segment.</t>
<t>OAM: Operations, Administration, and Maintenance</t>
<t>Other terminologies are as defined in
<xref target="I-D.draft-sridharan-virtualization-nvgre" />.
</t>
</section>
<section title="Approach">
<t>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):-</t>
<section title="Ingress NVGRE End Point Procedure">
<t>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.</t>
<figure>
<artwork>
GRE Header:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0| |1|0| Reserved0 RA| Ver | Protocol Type 0x6558 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Virtual Subnet ID (VSID) | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
RA: Router Alter Bit (Proposed)
</artwork>
</figure>
</section>
<section title="Egress NVGRE End Point Procedure">
<t>On receiving NVGRE frame, the Terminating NVGRE end point would do the usual
NVGRE processing as defined in <xref target="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.</t>
</section>
</section>
<section title="Management Considerations">
<t>None</t>
</section>
<section anchor="Security" title="Security Considerations">
<t>TBD</t>
</section>
<section anchor="Ack" title="Acknowledgements">
<t>The authors want to thank Diego Garcia Del Rio and Suresh Boddapati
of Nuage Networks for significant contribution and feedback.</t>
</section>
<section anchor="IANA" title="IANA Considerations">
<t>Router Alter Bit (RA): IANA is request to assign 1 Bit in the
Reserved0 field of NVGRE Header to communicate NVGRE Router Alert
information.</t>
</section>
</middle>
<back>
<references title="Normative References">
<reference anchor="I-D.draft-sridharan-virtualization-nvgre">
<front>
<title>NVGRE: Network Virtualization using Generic Routing Encapsulation</title>
<author fullname="Murari Sridharan" initials="M" surname="Sridharan">
<organization></organization>
</author>
<author fullname="Kenneth Duda" initials="K" surname="Duda">
<organization></organization>
</author>
<author fullname="Ilango Ganga initials="I" surname="Ganga">
<organization></organization>
</author>
<author fullname="Albert Greenberg" initials="A" surname="Greenberg">
<organization></organization>
</author>
<author fullname="Geng Lin" initials="G" surname="Lin">
<organization></organization>
</author>
<author fullname="Mark Pearson" initials="M" surname="Pearson">
<organization></organization>
</author>
<author fullname="Patricia Thaler" initials="P" surname="Thaler">
<organization></organization>
</author>
<author fullname="Chait Tumuluri" initials="C" surname="Tumuluri">
<organization></organization>
</author>
<author fullname="Narasimhan Venkataramiah" initials="N" surname="Venkataramiah">
<organization></organization>
</author>
<author fullname="Yu-Shun Wang" initials="Y" surname="Wang">
<organization></organization>
</author>
<date day="25" month="February" year="2013" />
<abstract>
<t>.</t>
</abstract>
</front>
</reference>
<?rfc include='reference.RFC.2784'?>
<reference anchor="I-D.draft-lasserre-nvo3-framework">
<front>
<title>Framework for DC Network Virtualization</title>
<author fullname="Marc Lasserre" initials="M" surname="Lasserre">
<organization></organization>
</author>
<author fullname="Florin Balus" initials="F" surname="Balus">
<organization></organization>
</author>
<author fullname="Thomas Morin" initials="T" surname="Morin">
<organization></organization>
</author>
<author fullname="Nabil Bitar" initials="N" surname="Bitar">
<organization></organization>
</author>
<author fullname="Yakov Rekhter" initials="Y" surname="Rekhter">
<organization></organization>
</author>
<date day="15" month="September" year="2011" />
<abstract>
<t>.</t>
</abstract>
</front>
</reference>
<!--
<reference anchor="I-D.draft-lasserre-nvo3-framework">
<seriesInfo name="Internet-Draft"
value="draft-lasserre-nvo3-framework-03" />
<format target="http://tools.ietf.org/id/draft-lasserre-nvo3-framework-03"
type="TXT" />
<author fullname="Marc Lasserre" initials="M" surname="Lasserre">
<organization></organization>
</author>
<author fullname="Florin Balus" initials="F" surname="Balus">
<organization></organization>
</author>
<author fullname="Thomas Morin" initials="T" surname="Morin">
<organization></organization>
</author>
<author fullname="Nabil Bitar" initials="N" surname="Bitar">
<organization></organization>
</author>
<author fullname="Yakov Rekhter" initials="Y" surname="Rekhter">
<organization></organization>
</author>
</reference>
-->
</references>
<references title="Informative References">
<?rfc include='reference.RFC.2119'?>
</references>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-23 17:00:57 |