+1. Network operators lose flexibility with Global VNIDs. Virtual topology will be fine tuned on top of VNIDs by squeezing a square peg (ACLs) into a round hole (where it's otherwise not needed). I think local context IDs will make a come back once we regain our sanity. :).
On Tuesday, July 23, 2013, Kireeti Kompella wrote: > Hi Xuxiaohu, > > Sorry for the previous empty email. > > On Jul 23, 2013, at 4:51, Xuxiaohu <[email protected] <javascript:;>> > wrote: > > > The reason that I started this discussion is to make sure whether the > Virtual Network Context Identification contained in the data packet is > REALLY required to be globally unique in some cases. > > No. There's nothing useful that I know that one can do with global IDs in > the data plane that one cannot do with local IDs, and local IDs are easier > to allocate and manage. So, I'd be going the other way and advocate locally > significant VNIDs for VXLAN and NVGRE, not global IDs for VPNs. (And I do) > > Kireeti > _______________________________________________ > nvo3 mailing list > [email protected] <javascript:;> > https://www.ietf.org/mailman/listinfo/nvo3 >
