<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.zhang-nvo3-active-active-nve" target="https://datatracker.ietf.org/doc/html/draft-zhang-nvo3-active-active-nve-01">
   <front>
      <title>Multi-homing of NVEs</title>
      <author initials="M." surname="Zhang" fullname="Mingui Zhang">
         <organization>Huawei</organization>
      </author>
      <author initials="Y." surname="Li" fullname="Yizhou Li">
         <organization>Huawei</organization>
      </author>
      <author initials="M." surname="Durrani" fullname="Muhammad Durrani">
         <organization>Cisco</organization>
      </author>
      <author initials="M." surname="Cullen" fullname="Margaret Cullen">
         <organization>Painless Security</organization>
      </author>
      <date month="October" day="15" year="2015" />
      <abstract>
	 <t>   Multi-homing of NVEs is a desirable feature to NVO3 since it provides
   Tenant Systems with reliable connection, load-balance, etc. The major
   issue of the multi-homing of NVEs is that it introduces one-to-many
   mapping from Tenant System (inner) addresses to NVE (outer)
   addresses.

   This document identifies the requirements for multi-homing of NVEs
   and specifies corresponding solutions to meet these requirements. The
   key is to let remote NVEs be aware of the group of NVEs that are
   offering multi-homing to Tenant Systems, therefore the remote NVE can
   cope with the one-to-many mapping correctly.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-zhang-nvo3-active-active-nve-01" />
   
</reference>
