From: Jay Vosburgh <jay.vosburgh@canonical.com>
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: Aahil Awatramani <aahila@google.com>,
David Dillow <dave@thedillows.org>,
Mahesh Bandewar <maheshb@google.com>,
Andy Gospodarek <andy@greyhouse.net>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Martin KaFai Lau <martin.lau@kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
Daniel Borkmann <daniel@iogearbox.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2 net-next v2] bonding: Extending LACP MUX State Machine to include a Collecting State.
Date: Tue, 09 Jan 2024 11:53:48 -0800 [thread overview]
Message-ID: <26173.1704830028@famine> (raw)
In-Reply-To: <ZZtwKFu4GQLQ5AXM@Laptop-X1>
Hangbin Liu <liuhangbin@gmail.com> wrote:
>On Thu, Jan 04, 2024 at 05:38:52PM -0800, Jay Vosburgh wrote:
>> >+coupled_control
>> >+
>> >+ Specifies whether the LACP state machine's MUX in the 802.3ad mode
>> >+ should have separate Collecting and Distributing states.
>> >+
>> >+ The default value is 1. This setting does not separate the Collecting
>> >+ and Distributing states, maintaining the bond in coupled control.
>> >+
>>
>> Please reference the standard in the description; this is
>> implementing the independent control state machine per IEEE 802.1AX-2008
>> 5.4.15 in addition to the existing coupled control state machine.
>
>The status of IEEE 802.1AX-2008[1] is "Superseded Standard". Maybe we should
>use IEEE 802.1AX-2020[2].
>
>[1] https://standards.ieee.org/ieee/802.1AX/4176/
>[2] https://standards.ieee.org/ieee/802.1AX/6768/
I'm fine to still reference the 2008 (or 2014) standard even
though it's superseded; the 2020 standard is much more complicated, and
I find it harder to follow (particularly for the coupled / independent
control sections, the older standard explains them more clearly in my
reading). Bonding does not implement any of the new things added for
the 2020 version, so we're not really missing anything.
That said, as long as the citations are for the correct section
(the numbering is not consistent between versions) any version is
acceptable.
-J
---
-Jay Vosburgh, jay.vosburgh@canonical.com
next prev parent reply other threads:[~2024-01-09 19:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 0:06 [PATCH 1/2 net-next v2] bonding: Extending LACP MUX State Machine to include a Collecting State Aahil Awatramani
2024-01-05 0:06 ` [PATCH 2/2 " Aahil Awatramani
2024-01-05 1:35 ` Jay Vosburgh
2024-01-11 20:32 ` Aahil Awatramani
2024-01-05 1:38 ` [PATCH 1/2 " Jay Vosburgh
2024-01-08 3:46 ` Hangbin Liu
2024-01-09 19:06 ` Aahil Awatramani
2024-01-09 19:53 ` Jay Vosburgh [this message]
2024-01-10 2:26 ` Hangbin Liu
2024-01-11 20:31 ` Aahil Awatramani
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=26173.1704830028@famine \
--to=jay.vosburgh@canonical.com \
--cc=aahila@google.com \
--cc=andy@greyhouse.net \
--cc=daniel@iogearbox.net \
--cc=dave@thedillows.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=maheshb@google.com \
--cc=martin.lau@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).