Luyuan, > If you followed the Taiwan meeting and all the activities going on in Routing > area around DC, > this is the continued work for vpn4dc. In the last IETF in Paris, it was said > that nvo3 > would expand its original scope to include vpn, so we brought the work here.
I did follow the Taiwan meeting, and I'm aware of all of this, although I was a bit surprised to see the VPN4DC draft turn up in nvo3 rather than go back to l3vpn, as I have a somewhat different perspective, which dates back to before the Taipei meetings. The nvo3 effort started out as overlay-focused, and it was pointed out that overlays are a type of VPN. That observation is correct, as all three of "virtual", "private" and "network" apply to the overlay VNs in nvo3. One of the results was that the first IETF session devoted to nvo3 was held as the second l2vpn WG session in Taipei, and another result was use of the VPN acronym in the nvo3 WG charter. I think it's a bit of a stretch to jump from there to a conclusion that all VPN work in data centers is therefore within the scope of nvo3. To take an obvious example, if there was interest in data-center-specific work for IPsec VPNs, that work would be done in the Security Area's ipsecme WG, and attempts to do it in nvo3 would result in long versions of the work "No" from the Security ADs :-). I agree that the vpn4dc work is potentially in the scope of nvo3 (and I believe I effectively said so at the microphone in Paris in response to a question from Thomas Morin), but I would really like to better understand how and why this work moved to nvo3 as the WG of primary focus instead of where it started in the l3vpn WG back in Taipei. Thanks, --David ---------------------------------------------------- David L. Black, Distinguished Engineer EMC Corporation, 176 South St., Hopkinton, MA 01748 +1 (508) 293-7953 FAX: +1 (508) 293-7786 [email protected] Mobile: +1 (978) 394-7754 ---------------------------------------------------- _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
