1. NVO3 Data Plane Discussion

2. Examples of extension types
Tunnel stitching – facilitate next hop tunnel choice
Inband OAM
Security for header
Header checksum
Remote checksum offload
Fragmentation
Payload Transform
Vendor defined extensions

3. Handling extensions
Data plane should make it easy to skip over extensions to examine inner headers and process payload.
NVO3 DP header should have a length field for overall extension length
Maintain 4 byte alignment
Should allow for some extensions to be critical
Which devices need to process which extensions?
vswitch, gateway, transit nodes (e.g. routers in underlay)
Extensions for non-end devices (e.g. tunnel stitching) should be first after the NVO3 DP header

4. Some questions
Do extensions need to be carried end-to-end over NVO3 overlay network part of path, e.g. between halves of a split NVE or WAN segment between two NVO3 overlay networks? If so how?
Security: Does header need separate protection from payload? How is the header protected?
Is criticality based on extension type (i.e. always the same for that type of extension) ?
Upper bound on extension size (128? 256?)

5. Non-extension question
VNI size – 24 bits enough of need 32?
Possibly 24 in header and use