> -----Original Message----- > From: Ben Pfaff [mailto:[email protected]] > Sent: Thursday, 31 August, 2017 18:28 > > > > This is a large change to just update the wire format. Can you make > > it more minimal? > > Actually, let's skip it. I think that we should release OVS 2.8 as is. > We delayed the release mostly to get NSH in, because Jan said that it was > important to them, but then it turns out that the NSH protocol is still > changing? What a waste. I will not make that mistake again.
Hi Ben, It was our mistake that we missed the late change of the NSH draft in June during the crunch time for OVS 2.8 and I apologize for that. I already suggested two weeks ago (https://mail.openvswitch.org/pipermail/ovs-dev/2017-August/337540.html) to release 2.8 as is and document the NSH support as experimental (with support for the pre-June draft version). So I support to follow this route. I believe we can create a much smaller correction which just fixes the wire format without adding any support for the new TTL field. That patch could be delivered on the 2.8 maintenance branch. Full compliance to the final RFC with support for the TTL field, the dec_nsh_ttl action and proper alignment with the net-next kernel datapath uAPI should then be targeted for OVS 2.9. Regards, Jan _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
