[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <da0b93d4-f6d7-eafe-77c5-1844261e0bdf@gmail.com>
Date: Mon, 22 Apr 2019 08:55:31 -0600
From: David Ahern <dsahern@...il.com>
To: Tom Herbert <tom@...ntonium.net>
Cc: Tom Herbert <tom@...bertland.com>,
"David S . Miller" <davem@...emloft.net>, netdev@...r.kernel.org
Subject: Re: [PATCH v5 net-next 5/6] ip6tlvs: Add netlink interface
On 4/22/19 6:33 AM, Tom Herbert wrote:
>
>
> On Sun, Apr 21, 2019, 11:43 PM David Ahern <dsahern@...il.com
> <mailto:dsahern@...il.com>> wrote:
>
> On 4/19/19 4:36 PM, Tom Herbert wrote:
> > Add a netlink interface to manage the TX TLV parameters. Managed
> > parameters include those for validating and sending TLVs being sent
> > such as alignment, TLV ordering, length limits, etc.
> >
>
> Why generic netlink for managing IPv6 extensions?
>
>
> Hi David,
>
> It allows control over permissions to use specific options. Also, admin
> can add TLVs in the system without requiring specific kernel support.
> The latter in combination with datagram interfaces made bringing up Path
> MTU option at IETF hackathon a breeze (much easier time than FreeBSD
> guys were having :-) ).
>
Hi Tom: I was asking why can't this be done with rtnetlink? How does the
genl interface make this easier / better?
Powered by blists - more mailing lists