From: Hangbin Liu <liuhangbin@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, "David S . Miller" <davem@davemloft.net>,
David Ahern <dsahern@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Ido Schimmel <idosch@idosch.org>,
Nikolay Aleksandrov <razor@blackwall.org>,
Roopa Prabhu <roopa@nvidia.com>, Florian Westphal <fw@strlen.de>,
Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
Jiri Pirko <jiri@resnulli.us>,
Marc Muehlfeld <mmuehlfe@redhat.com>
Subject: Re: [PATCHv3 net-next 05/10] docs: bridge: add STP doc
Date: Wed, 29 Nov 2023 15:43:24 +0800 [thread overview]
Message-ID: <ZWbrnK9VKczMrCMb@Laptop-X1> (raw)
In-Reply-To: <20231128144840.5d3ced05@hermes.local>
On Tue, Nov 28, 2023 at 02:48:40PM -0800, Stephen Hemminger wrote:
> On Tue, 28 Nov 2023 16:49:38 +0800
> Hangbin Liu <liuhangbin@gmail.com> wrote:
>
> > +STP is a Layer 2 protocol that operates at the Data Link Layer of the OSI
> > +model. It was originally developed as IEEE 802.1D and has since evolved into
> > +multiple versions, including Rapid Spanning Tree Protocol (RSTP) and
> > +`Multiple Spanning Tree Protocol (MSTP)
> > +<https://lore.kernel.org/netdev/20220316150857.2442916-1-tobias@waldekranz.com/>`_.
> > +
The STP was originally developed as IEEE 802.1D. So how about keep this part,
>
> Last time I checked, IEEE folded RSTP into the standard in 2004.
> https://en.wikipedia.org/wiki/IEEE_802.1D
and add a new paragraph like:
The 802.1D-2004, removed the original Spanning Tree Protocol, instead
incorporating the Rapid Spanning Tree Protocol (RSTP). By 2014, all the
functionality defined by IEEE 802.1D has been incorporated into either
IEEE 802.1Q-2014 (Bridges and Bridged Networks) or IEEE 802.1AC (MAC Service
Definition). 802.1D is expected to be officially withdrawn in 2022.
Thanks
Hangbin
next prev parent reply other threads:[~2023-11-29 7:43 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 8:49 [PATCHv3 net-next 00/10] Doc: update bridge doc Hangbin Liu
2023-11-28 8:49 ` [PATCHv3 net-next 01/10] docs: bridge: update doc format to rst Hangbin Liu
2023-11-28 22:46 ` Stephen Hemminger
2023-11-29 7:34 ` Hangbin Liu
2023-11-29 4:16 ` Florian Fainelli
2023-11-28 8:49 ` [PATCHv3 net-next 02/10] net: bridge: add document for IFLA_BR enum Hangbin Liu
2023-11-29 18:37 ` Vladimir Oltean
2023-11-28 8:49 ` [PATCHv3 net-next 03/10] net: bridge: add document for IFLA_BRPORT enum Hangbin Liu
2023-11-28 8:49 ` [PATCHv3 net-next 04/10] docs: bridge: Add kAPI/uAPI fields Hangbin Liu
2023-11-28 22:47 ` Stephen Hemminger
2023-11-29 4:11 ` Florian Fainelli
2023-11-28 8:49 ` [PATCHv3 net-next 05/10] docs: bridge: add STP doc Hangbin Liu
2023-11-28 22:48 ` Stephen Hemminger
2023-11-29 7:43 ` Hangbin Liu [this message]
2023-11-29 15:10 ` Stephen Hemminger
2023-11-29 18:46 ` Vladimir Oltean
2023-11-29 4:21 ` Florian Fainelli
2023-11-29 18:48 ` Vladimir Oltean
2023-11-28 8:49 ` [PATCHv3 net-next 06/10] docs: bridge: add VLAN doc Hangbin Liu
2023-11-29 4:12 ` Florian Fainelli
2023-11-29 18:40 ` Vladimir Oltean
2023-11-28 8:49 ` [PATCHv3 net-next 07/10] docs: bridge: add multicast doc Hangbin Liu
2023-11-29 4:15 ` Florian Fainelli
2023-11-28 8:49 ` [PATCHv3 net-next 08/10] docs: bridge: add switchdev doc Hangbin Liu
2023-11-29 4:16 ` Florian Fainelli
2023-11-28 8:49 ` [PATCHv3 net-next 09/10] docs: bridge: add netfilter doc Hangbin Liu
2023-11-29 4:18 ` Florian Fainelli
2023-11-28 8:49 ` [PATCHv3 net-next 10/10] docs: bridge: add other features Hangbin Liu
2023-11-29 4:09 ` Florian Fainelli
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=ZWbrnK9VKczMrCMb@Laptop-X1 \
--to=liuhangbin@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=fw@strlen.de \
--cc=idosch@idosch.org \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=mmuehlfe@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.com \
--cc=stephen@networkplumber.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