search

p4lang / p4-applications

P4 Applications WG repo
107 stars 45 forks source link

Add bit indicating whether orig packet used VXLAN or VXLAN-GPE encap #58

Closed mickeyspiegel closed 4 years ago

mickeyspiegel commented 5 years ago

Include guidelines suggesting that the sink should ignore this bit in mixed v1.0 / v1.1 environments.

jklr commented 4 years ago

@mickeyspiegel This is a reminder of the AR from the May meeting: All text around 1.0/1.x interoperability needs to be modified as this is now going into version 2.0. Mickey to revise, Mukesh to review and merge.

mickeyspiegel commented 4 years ago

Open Issues:

  1. Should we reduce the INT-Type field to 4 bits as JK recently proposed?
  2. Should we move the G bit to the Type byte, or leave it in the Reserved byte?

Note that the VXLAN GPE shim header format in draft-ietf-nvo3-vxlan-gpe-09 defines:

   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      Type     |    Length     |    Reserved   | Next Protocol |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

where Type: This field MAY be used to identify different messages of this protocol. Reserved: The use of this field is reserved to the protocol defined in this message.

jklr commented 4 years ago

@mickeyspiegel as for the shim hdr format, I think the consensus from the last meeting is to follow the GPE convention, deviating from the INT convention.