[<prev] [next>] [day] [month] [year] [list]
Message-ID: <920434b5-f557-2ee3-d64a-6aa08d861297@gmail.com>
Date: Sat, 13 Jun 2020 18:33:09 -0600
From: David Ahern <dsahern@...il.com>
To: Dinesh Dutt <didutt@...il.com>,
Andrea Mayer <andrea.mayer@...roma2.it>
Cc: David Ahern <dsahern@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Shrijeet Mukherjee <shrijeet@...il.com>,
Jakub Kicinski <kuba@...nel.org>,
Shuah Khan <shuah@...nel.org>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org,
Donald Sharp <sharpd@...ulusnetworks.com>,
Roopa Prabhu <roopa@...ulusnetworks.com>,
Stefano Salsano <stefano.salsano@...roma2.it>,
Paolo Lungaroni <paolo.lungaroni@...t.it>,
Ahmed Abdelsalam <ahabdels@...il.com>
Subject: Re: [RFC,net-next, 0/5] Strict mode for VRF
On 6/13/20 4:39 PM, Dinesh Dutt wrote:
> Understand Andrea. I guess I didn't say it well. What I meant to say was
> that the strict mode is the default expected behavior in a classical router.
>
it has to be off by default for backwards compatibility.
Powered by blists - more mailing lists