> On Jul 21, 2016, at 4:56 PM, Bocci, Matthew (Nokia - GB) > <[email protected]> wrote: > 2) Does anyone have a significant technical objection to selecting VXLAN-GPE > as the single NVO3 Standards track document? Please be as concrete and > detailed as possible as to your technical objection.
I object to VXLAN-GPE because of the three proposed encapsulations, it is the only one without any extensibility mechanism. Given the number of extensions to VXLAN (some of which are overlapping), it seems like extensibility is a clear need. In addition, both Geneve and GUE have had extensions introduced since their initial definition. It does not seem the need for further extensions is likely to end in the near future. > 3)Does anyone have a significant technical objection to selecting GUE as the > single NVO3 Standards track document? Please be as concrete and detailed as > possible as to your technical objection. I object to GUE due to its inability to have a significant number of extensions in a regular and interoperable way. The base flags structure is limited (note 7 of 16 flags have already been used before the document has been published) and requires specific knowledge in the dataplane of all prior defined extensions to even parse a given field. The draft does have private data but since this is unstructured and untyped, it will be very difficult to make it interoperable between different users. In the past, ways around this have been proposed such as a flag indicating that an extended set of flags are present or overlaying the private data with some structure (such as TLVs). However, having multiple extension mechanisms in a single protocol seems overly complex and likely to result in incomplete implementations. I am also concerned that there currently appears to be significantly fewer implementations of GUE compared to the other two protocols, which could be seen as an indication of industry interest. _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
