On Oct 1, 2013, at 11:03 AM, Jarno Rajahalme wrote: > > On Oct 1, 2013, at 10:07 AM, Pritesh Kothari (pritkoth) <pritk...@cisco.com> > wrote: > >> >> On Sep 30, 2013, at 5:46 PM, Jesse Gross wrote: >> >>> On Fri, Sep 20, 2013 at 1:04 AM, pritesh <pritesh.koth...@cisco.com> wrote: >>>> This patch adds support for Network Service Headers (nsh) over VXLAN >>>> as mentioned in [1]. Here changes are made to datapath to add nsh >>>> headers whenever a vxlan port with destination port as 9030 is created. >>>> IANA port allocation for nsh over vxlan is yet to be done. >>> >>> I'm pretty concerned about using a magic UDP port, especially since >>> one hasn't been allocated yet (we went through the same situation with >>> VXLAN itself). Is there a way that we can just insert/remove this >>> header on a flow basis? >> >> you mean adding/removing headers when nsh specific parameters (nsp/nsi) >> are set while creating/editing a port? or should i just add a toggle nsh=true >> instead of port number till it is finalized? >> > > Or just insert NSH when the relevant attributes are set for the flow. In data > path, instead of using the port number to determine wether the NSH header > should be included, use the TUNNEL_NSP flag. On reception it would be good if > the presence of NSH could be detected from the headers/payload without a > special UDP port number, so that same tunnel port could be used for receiving > NSH from some tunnels, and non-NSH payloads from others. This seems trivially > doable with GRE, but I'm not entirely sure if that is possible with vxlan > (without the special UDP port, that is).
actually this is great idea, will do this and post v2 of these patches soon. also this way i can easily extend the nsh headers from vxlan to gre and lisp. Regards, Pritesh > > Jarno _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
