> -----Original Message----- > From: Joe Touch [mailto:to...@isi.edu] > Sent: Friday, June 17, 2016 11:33 PM > To: Tom Herbert; Xuxiaohu > Cc: n...@ietf.org; int-area@ietf.org > Subject: Re: [nvo3] [Int-area] Fwd: New Version Notification for > draft-ietf-nvo3-gue-03.txt > > > > On 6/17/2016 8:06 AM, Tom Herbert wrote: > > The problem was that VXLAN defined unknown flag bits to be ignored > > upon receive. So if a legacy VLXAN device ever received a VXLAN-GPE > > packet (P-bit set) it would be misinterpreted as a VLXAN packet. > > Effectively this makes VXLAN-GPE a new protocol not a different > > version of VXLAN. > > Right - the issue is that the new protocol is not a *subset* of the older one.
If it was a totally new protocol, why call it VXLAN-GPE instead of GPE? Furthermore, what's the meaning of the P-bit in the VXLAN-GPE header since a dedicated port number has been allocated? Xiaohu > That was not the case for VXLAN/VXLAN-GPE, but is for GUE/IP-in-UDP. > > Joe _______________________________________________ Int-area mailing list Int-area@ietf.org https://www.ietf.org/mailman/listinfo/int-area
