Re: [nvo3] Extensions in nvo3 encapsulations

Hi Tom, see inline below. Lizhong On Sat, Aug 20, 2016 at 6:53 AM, Tom Herbert wrote: > Hi Lizhong, thanks for the feedback! Some replies inline. > > On Fri, Aug 19, 2016 at 8:07 AM, Lizhong Jin wrote: > > Hi Tom, > > Thank > >> Six fundamental

Re: [nvo3] Extensions in nvo3 encapsulations

Hi Lizhong, thanks for the feedback! Some replies inline. On Fri, Aug 19, 2016 at 8:07 AM, Lizhong Jin wrote: > Hi Tom, > Thank >> Six fundamental extensions have been defined for GUE >> >> 1) VNID (draft-hy-nvo3-gue-4-nvo-03) >> 2) Checksum (draft-herbert-gue-extensions-00)

Re: [nvo3] Extensions in nvo3 encapsulations

Hi Tom, thinking out of the box - what will break if you slightly change the order in which the packets are processed at the VTEP/PE/NVE? >From the VM perspective, you insert a new L2 module before the packets are sent down to the virtual circuit. In this module you have e.g. MACSec for

Re: [nvo3] Extensions in nvo3 encapsulations

that by defining a new flag and corresponding optional field. Extensibility is important for a protocol to retain long. Lucy -Original Message- From: nvo3 [mailto:nvo3-boun...@ietf.org] On Behalf Of Tom Herbert Sent: Thursday, August 18, 2016 6:25 PM To: nvo3@ietf.org Subject: [nvo3] Extensions in nvo3

[nvo3] Extensions in nvo3 encapsulations

Alia has asked that we provide some more information as to what the motivations for extensions are for nvo3 and to what form they should take. Here is some high level explanation with respect to GUE. Six fundamental extensions have been defined for GUE 1) VNID (draft-hy-nvo3-gue-4-nvo-03) 2)