Re: [Isis-wg] [nvo3] Simplify the deployment of NVo3 data encapsulations in enterprise campus networks?//FW: New Version Notification for draft-xu-nvo3-isis-cp-02.txt

Hi Saumya,

Thanks for your further comments. Please see my response inline.

From: Saumya Dikshit (sadikshi) [mailto:sadikshi@cisco.com]
Sent: Tuesday, July 05, 2016 5:29 PM
To: Xuxiaohu; nvo3@ietf.org; isis-wg@ietf.org
Subject: Re: [nvo3] Simplify the deployment of NVo3 data encapsulations in enterprise campus networks?//FW: New Version Notification for draft-xu-nvo3-isis-cp-02.txt

Hi Xiaohu,
Please see inline.

From: Xuxiaohu <xuxiaohu@huawei.com<mailto:xuxiaohu@huawei.com>>
Date: Tuesday, July 5, 2016 at 1:41 PM
To: sadikshi <sadikshi@cisco.com<mailto:sadikshi@cisco.com>>, "nvo3@ietf.org<mailto:nvo3@ietf.org>" <nvo3@ietf.org<mailto:nvo3@ietf.org>>, "isis-wg@ietf.org<mailto:isis-wg@ietf.org>" <isis-wg@ietf.org<mailto:isis-wg@ietf.org>>
Subject: RE: [nvo3] Simplify the deployment of NVo3 data encapsulations in enterprise campus networks?//FW: New Version Notification for draft-xu-nvo3-isis-cp-02.txt

Hi Saumya,

From: nvo3 [mailto:nvo3-bounces@ietf.org] On Behalf Of Saumya Dikshit (sadikshi)
Sent: Monday, July 04, 2016 4:39 PM
To: Xuxiaohu; nvo3@ietf.org<mailto:nvo3@ietf.org>; isis-wg@ietf.org<mailto:isis-wg@ietf.org>
Subject: Re: [nvo3] Simplify the deployment of NVo3 data encapsulations in enterprise campus networks?//FW: New Version Notification for draft-xu-nvo3-isis-cp-02.txt

Hi Xiaohu,

Even though the reference is to campus deployment, there could be a generic requirement of routing (l3-gateway),
which may eventually require IP/MAC bindings to be published. Is there any plan to include that in the draft.

The current version only considers Layer2 overlay. Layer3 overlay may be considered in future versions.
<Saumya> And that may require, a new TLV definition, as the existing one "MAC-Reachability (MAC-RI) TLV" may not suffice.
Just thinking aloud if that can be considered as a complete solution provided by any NVO3 construct/encapsulation.

[Xiaohu] No need for a new TLV definition. The existing Extended IP Reachability TLVs can be reused for layer3 overlay routing exchange purpose.

>>>>(only a single protocol to be deployed that's IS-IS)
Does it refers to single protocol in overlay and underlay ? I think its highly subjective to the exact requirements.

IS-IS has been widely used  in campus networks for many years. Layer2 overlay control plane could be realized through a tiny extension to IS-IS (i.e., the VN membership auto-discovery based upon a single sub-TLV). Note that the control-plane based MAC learning is optional rather than mandatory.
<Saumya> As I understand, the distribution of Overlay information (VN-memebership), will be tightly coupled with the underlay network tied up to same instance of ISIS and
can end up populating non-NVO3 devices in the ISIS network.

[Xiaohu] Your observation is correct that VN-membership info would be received by non-NVE devices. However, according to the ISIS specification, IS-IS routers would ignore unknown TLVs in the LSP and pass them on to other neighbors unchanged. Therefore, non-NVE routers don't need processing the VN membership info TLVs at all. Therefore, from the incremental deployment perspective, only those NVE devices need to be upgraded.

Best regards,
Xiaohu

Thanks
Saumya.

On 7/4/16, 12:36 PM, "nvo3 on behalf of Xuxiaohu" <nvo3-bounces@ietf.org<mailto:nvo3-bounces@ietf.org> on behalf of xuxiaohu@huawei.com<mailto:xuxiaohu@huawei.com>> wrote:

Hi all,

Due to the success of the NVo3 data encapsulations technology in data center networks, more and more enterprises are considering the adoption of this technology in their campus networks so as to replace the old spanning tree protocols.  Although BGP or Software Defined Network (SDN) controller could still be used as the control plane protocol in campus networks, both of them seem a bit heavyweight, especially for small and even medium sized campus networks.

This draft proposes to use IS-IS as a lightweight control plane protocol for NVo3 overlay networks. In this way, the network provisioning is dramatically simplified (only a single protocol to be deployed that's IS-IS), which is much significant to campus network operators. BTW, it leverages the MAC-Reachability (MAC-RI) TLV as defined in RFC6165 to realize on-demand control-plane based MAC learning on a per-VN basis, most importantly, without any dependence on the multicast capability of the underlay networks.

Any comments are welcome.

Best regards,
Xiaohu

-----Original Message-----
From: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> [mailto:internet-drafts@ietf.org]
Sent: Friday, July 01, 2016 3:17 PM
To: Himanshu Shah; Himanshu C. Shah; Xuxiaohu; Fan Yongbing; Yongbing Fan
Subject: New Version Notification for draft-xu-nvo3-isis-cp-02.txt
A new version of I-D, draft-xu-nvo3-isis-cp-02.txt has been successfully
submitted by Xiaohu Xu and posted to the IETF repository.
Name:draft-xu-nvo3-isis-cp
Revision:02
Title:NVo3 Control Plane Protocol Using IS-IS
Document date:2016-07-01
Group:Individual Submission
Pages:8
URL:
https://www.ietf.org/internet-drafts/draft-xu-nvo3-isis-cp-02.txt
Status:         https://datatracker.ietf.org/doc/draft-xu-nvo3-isis-cp/
Htmlized:       https://tools.ietf.org/html/draft-xu-nvo3-isis-cp-02
Diff:           https://www.ietf.org/rfcdiff?url2=draft-xu-nvo3-isis-cp-02
Abstract:
    This document describes the use of IS-IS as a light-weight control
    plane protocol for Network Virtualization over L3 (NVo3) overlay
    networks.  This light-weight control plane protocol is intended for
    small and even medium sized enterprise campus networks where the NVo3
    technology is to be used.
Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.
The IETF Secretariat

_______________________________________________
nvo3 mailing list
nvo3@ietf.org<mailto:nvo3@ietf.org>
https://www.ietf.org/mailman/listinfo/nvo3