[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4586921d-5fc4-b63f-8264-a6fd63c592b6@gmail.com>
Date: Fri, 15 Apr 2022 14:38:58 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Arun Ajith S <aajith@...sta.com>, netdev@...r.kernel.org
Cc: davem@...emloft.net, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org, dsahern@...nel.org,
yoshfuji@...ux-ipv6.org, kuba@...nel.org, pabeni@...hat.com,
corbet@....net, prestwoj@...il.com, gilligan@...sta.com,
noureddine@...sta.com, gk@...sta.com
Subject: Re: [PATCH net-next v5] net/ipv6: Introduce accept_unsolicited_na
knob to implement router-side changes for RFC9131
On 4/15/22 12:42, Arun Ajith S wrote:
> +accept_unsolicited_na - BOOLEAN
> + Add a new neighbour cache entry in STALE state for routers on receiving an
> + unsolicited neighbour advertisement with target link-layer address option
> + specified. This is as per router-side behavior documented in RFC9131.
> + This has lower precedence than drop_unsolicited_na.
> +
> + ==== ====== ====== ==============================================
> + drop accept fwding behaviour
> + ---- ------ ------ ----------------------------------------------
> + 1 X X Drop NA packet and don't pass up the stack
> + 0 0 X Pass NA packet up the stack, don't update NC
> + 0 1 0 Pass NA packet up the stack, don't update NC
> + 0 1 1 Pass NA packet up the stack, and add a STALE
> + NC entry
> + ==== ====== ====== ==============================================
> +
Hi,
Building htmldocs with this patch, there are no more warnings from v4, but
I don't see the table above generated in the output. I guess due to
whitespace-mangling issues on your mailer, because the table syntax alignment
(the =-s) don't match the contents/cells.
Thanks.
--
An old man doll... just what I always wanted! - Clara
Powered by blists - more mailing lists