Hi all, I'm glad to see that this issue is mentioned in the NVo3 chairs' slides as well (i.e., some references to L3VPN technology-based DC VPN approaches are useful). Unfortunately, this issue is not discussed further after the survey of adoption of NVGRE and VXLAN drafts. My doubt is in which WG the L3VPN technology-based DC VPN drafts should be pursued (L3VPN WG or NVo3 WG?).
Best regards, Xiaohu ________________________________________ 发件人: [email protected] [[email protected]] 代表 Xuxiaohu [[email protected]] 发送时间: 2013年7月31日 22:43 到: [email protected]; [email protected] 主题: About gap analysis on L3VPN [RFC4365] Hi all, I noticed that L3VPN [RFC4365] is listed as one of the candidata technologies in the NVo3 gap analysis doc. However, IMHO, the current mechanism defined in RFC4365 alone couldn't support VM mobility which is one of the basic requirements of DC VPN. Hence, I believe it's much worthwhile to have an informational draft describing how to reuse the L3VPN mechanism for DC VPN before performing gap analysis on the L3VPN technology. Best regards, Xiaohu
