Let me try and see if I understand this. Basically what you're asking for is for the Group ID to remain a proxy for the VLAN ID, but not necessarily for the VNID. In the case of an L2VPN, VNID=VLAN. But in the case of L3VPN a VNID may actually represent a group of VLANs.
If so, I agree with your assessment. Anoop On Sat, Mar 21, 2015 at 5:38 PM, Benson Schliesser <[email protected]> wrote: > Speaking as an individual contributor to NVO3: > > In reviewing draft-ietf-nvo3-hpvr2nve-cp-req-02, it seems to me that > there is an assumption that a tNVE will perform local switching of e.g. > inter-VM packets. Based on this assumption, the recommendation seems to be > that the VDP GroupID is mapped to the VNID for a given VN. > > I don't see anything wrong with that particular mode of operation. But I > do also think it would be valuable to decouple things a bit further... > Specifically, I can imagine two modes of operation. One of them is as > described in the draft, where GroupID == VNID. The other might be described > as GroupID == VAP. > > This latter mode might be useful in cases where the nNVE is responsible > for filtering of some kind, in cases where there are network services that > must be processed for inter-TS traffic, etc. In fact it seems to me that we > may want this latter mode to be the default behavior of a split NVE. > > It's not clear to me how these different modes might be communicated via > VDP, and/or via the NVE-NVA control plane, if they need to be > communicated... I'd be interested to hear feedback from the authors and any > other WG contributors that have thought about this topic. > > Thanks, > -Benson > > _______________________________________________ > nvo3 mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/nvo3 >
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
