From: Hangbin Liu <liuhangbin@gmail.com>
To: Jay Vosburgh <jay.vosburgh@canonical.com>
Cc: Aahil Awatramani <aahila@google.com>, netdev@vger.kernel.org
Subject: Re: [PATCH 1/2 net-next v2] bonding: Extending LACP MUX State Machine to include a Collecting State.
Date: Wed, 10 Jan 2024 10:26:18 +0800 [thread overview]
Message-ID: <ZZ4AShj0fWSiw29D@Laptop-X1> (raw)
In-Reply-To: <26173.1704830028@famine>
On Tue, Jan 09, 2024 at 11:53:48AM -0800, Jay Vosburgh wrote:
> >> 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.
Got it. Thanks for the comments.
Cheers
Hangbin
next prev parent reply other threads:[~2024-01-10 2:26 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
2024-01-10 2:26 ` Hangbin Liu [this message]
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=ZZ4AShj0fWSiw29D@Laptop-X1 \
--to=liuhangbin@gmail.com \
--cc=aahila@google.com \
--cc=jay.vosburgh@canonical.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).