From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Arun Ajith S <aajith@arista.com>, netdev@vger.kernel.org
Cc: davem@davemloft.net, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, dsahern@kernel.org,
yoshfuji@linux-ipv6.org, kuba@kernel.org, pabeni@redhat.com,
corbet@lwn.net, prestwoj@gmail.com, gilligan@arista.com,
noureddine@arista.com, gk@arista.com
Subject: Re: [PATCH net-next v5] net/ipv6: Introduce accept_unsolicited_na knob to implement router-side changes for RFC9131
Date: Fri, 15 Apr 2022 14:38:58 +0700 [thread overview]
Message-ID: <4586921d-5fc4-b63f-8264-a6fd63c592b6@gmail.com> (raw)
In-Reply-To: <20220415054219.38078-1-aajith@arista.com>
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
next prev parent reply other threads:[~2022-04-15 7:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 5:42 Arun Ajith S
2022-04-15 7:38 ` Bagas Sanjaya [this message]
2022-04-15 8:26 ` Arun Ajith S
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4586921d-5fc4-b63f-8264-a6fd63c592b6@gmail.com \
--to=bagasdotme@gmail.com \
--cc=aajith@arista.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=gilligan@arista.com \
--cc=gk@arista.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=noureddine@arista.com \
--cc=pabeni@redhat.com \
--cc=prestwoj@gmail.com \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®