[ovs-dev] [RFC v3 3/5] ovn: Add a new OVN field icmp4.frag_mtu

[Ben Pfaff]

On Thu, Mar 21, 2019 at 01:53:39AM +0530, Numan Siddique wrote:
> On Wed, Mar 20, 2019, 11:43 PM Ben Pfaff <blp at ovn.org> wrote:
> 
> > On Wed, Mar 20, 2019 at 05:06:36PM +0530, Numan Siddique wrote:
> > > On Tue, Feb 12, 2019 at 8:41 AM Ben Pfaff <blp at ovn.org> wrote:
> > > > I don't understand why icmp4.frag_mtu is so heavily special-cased that
> > > > it only works inside nested actions.
> > >
> > > The idea of this patch is to add new OVN fields which can't be translated
> > > to OVS fields.
> > > We cannot use icmp4.frag_mtu  as a normal action.
> > >
> > > Eg.
> > >
> > > match=..., action=(eth.src = 30:54:00:00:00:03;  icmp4.code = 3;
> > > icmp4.frag_mtu = 1442; ...)
> > >
> > > We can use these fields only with in OVN actions which gets translated to
> > > "controller" OVS action.
> > > When ovn-controller gets the packet-in, it can set these fields.
> >
> > The assignment itself could be translated to a controller OVS action.
> >
> 
> Now I understand. Thanks. I will work on it.

Thanks.

For what it's worth, when it's possible and efficient enough, I like to
have things be general-purpose: then you enable people with new ideas to
use what you've built in clever new ways, and you also don't have to
explain restrictions to people, especially when the restrictions are
ones that only make sense in the solution domain rather than the problem
domain.