Re: [nvo3] Requesting Next Protocol = 0 for Ethernet [ draft-ietf-nvo3-vxlan-gpe-01.txt ]

On Mon, Nov 16, 2015 at 1:45 PM, Surendra Kumar (smkumar) wrote: > > Agree. I was just implying that the cost equivalent of discriminating v6/v4 > via the IP.ver field may already be paid even today. > Yes, a stack must verify that the version number matches the protocol

Re: [nvo3] Requesting Next Protocol = 0 for Ethernet [ draft-ietf-nvo3-vxlan-gpe-01.txt ]

Agree. I was just implying that the cost equivalent of discriminating v6/v4 via the IP.ver field may already be paid even today. Surendra. -Original Message- From: Joe Touch [mailto:to...@isi.edu] Sent: Monday, November 16, 2015 11:54 AM To: Surendra Kumar (smkumar)

Re: [nvo3] Requesting Next Protocol = 0 for Ethernet [ draft-ietf-nvo3-vxlan-gpe-01.txt ]

On 11/15/2015 12:47 PM, Surendra Kumar (smkumar) wrote: > I suspect some implementations may check the version even today. It's not about checking the version number. It's that the version number is what should be used to differentiate different versions of IP, not the outer (lower) layer