Talk:Spanning Tree Protocol/Archive 1: Difference between revisions

Revision as of 03:01, 25 November 2023

Revision as of 15:33, 24 November 2024

Line 152:

:A MAC address is a 48-bit field. Usually it is represented in number form where in any common notation, the most significant digit is leftmost and the least significant digit is rightmost. The entire number has the significance that is assigned to it on a certain point. For STP it is compared numerically, for identifying an L2 interface it is not. The byte and bit order that is used on Ethernet isn't relevant here, STPs are specified by IEEE 802.'''1'''. --[[User:Zac67|Zac67]] ([[User talk:Zac67|talk]]) 21:38, 28 October 2022 (UTC)

:There's what appears to be a compete explanation in [[Spanning Tree Protocol#Root bridge and the bridge ID]] ~[[User:Kvng|Kvng]] ([[User talk:Kvng|talk]]) 14:35, 31 October 2022 (UTC)

== Explicit definition of "Segments" ==

I think it might be useful to add a description of what "segments" on an ethernet network are. Nowadays, I think of things in terms of fully switched networks - whereas a network "segment" is a shared medium (thin ethernet over coax; twisted pair on an old hub) with many nodes and bridges on it. If you do not have a good understanding of this concept it's hard to grok the point of Designated ports.

Hmm, do dumb switches forward spanning-tree frames? If so, I guess a dumb switch would be considered a segment in this context.

If a bit about dumb switches is added, it would be prudent to add a note of caution. I've definitely seen cases where a dumb switch, or perhaps an intelligent switch that had STP disabled, has caused a broadcast storm when dually linked to a LAN running STP. [[User:Danpritts]] <span style="font-size: smaller;" class="autosigned">—Preceding [[Wikipedia:Signatures|undated]] comment added 19:50, 8 May 2013 (UTC)</span><!--Template:Undated--> <!--Autosigned by SineBot-->

:I have added links to [[network segment]]. I have also replaced occurrences of ''LAN segment'' with ''network segment''. ~[[User:Kvng|Kvng]] ([[User talk:Kvng|talk]]) 02:05, 25 November 2023 (UTC)

== RSTP as it's own ==

I am reading a paper and didn't know what '''RSTP''' was, so I fed it into wikipedia search. Luckily, there is only 1 "RSTP" acronym so far as the "RSTP" page points here as well. RSTP had a 100% hit while '''Rapid Spanning Tree Protocol''' came in 2nd at 2.9%. I ''found my answer right there in the search results'' and immediately knew "''oh, that's what RSTP''" stands for. If it was hidden away in the Spanning Tree Protocol page... I don't think I would have found it as easily! ("Spanning Tree" has a 1.1% search result). I vote to keep the separate page and not merge, it is good to be categorized in "Network protocols" though. --[[User:BrianWiese|BrianWiese]] 19:28, 20 March 2006 (UTC)

I also think this should be merged with STP

:remark by [[User:Jishnua]]

:please sign your comment, makes discussion easier ;-)

:In the current state, the articles could be merged... However, i had the idea to extend the RSTP en MSTP articles some day (or hoping someone else would do it). RSTP and MSTP are compatible and extensions of STP indeed, some parts of the text on protocol operations would be the same, or refer to the other article; however, an more extended description of the RSTP en MSTP protocol operation and properties would make de STP article lengthy, and maybe it IS usefull to have some "stand alone" description of the protocols. --[[User:LimoWreck|LimoWreck]] 00:48, 14 December 2005 (UTC)

I agree!

Sergio

Yes, Do it!!

Yeah, I had no idea what is was...please add it, it fits well.

Harry Cavallero

'''Merge Them'''

Most people will be looking for information on Spanning Tree, without realizing that in most network RSTP is the default version of spanning tree that is used. Both MSTP and RSPT should be merged into this article as the concept are very similar, and are evolutions on the basic STP protocol. By merging them together the reader will have the benefit of not only understanding the RSTP protocol, but the foundation of the protocol, and all related issues to do with it.

Sal Veya

Don't merge them - the mian article can explian the progression and the individual articles can provide more detail. Everyone is capable of clicking on the other pages. [[User:195.195.0.77|195.195.0.77]] 14:27, 19 October 2006 (UTC)

The RSTP page IMHO is so short and mostly people will be looking for STP so I think they should be merged and if someday the RSTP section becomes so huge that it deserves individual article, people will call for that --krampo 14:00, 3 November 2006 (UTC)

Don't merge them, please. Like another user above, I came here looking for RSTP specifically, & I wasn't even sure of its expansion. I think it deserves a page of its own. --[[User:Arungoodboy|Arungoodboy]] 05:42, 5 December 2006 (UTC)

:[[Rapid Spanning Tree Protocol]] redirects to this article. ~[[User:Kvng|Kvng]] ([[User talk:Kvng|talk]]) 02:07, 25 November 2023 (UTC)

== Problems in Article ==

In the opening paragraph of the article there is a sentence that doesn't make sense to me. However, I don't know enough about the topic to really correct it, so I'm hoping that by noting it here, somebody else can make the fix. The part I'm confused by is:<blockquote>First, there would be a broadcast storm caused by broadcast packets looping. <b>Second, the traditional source-based ___location system used by switches to operate correctly.</B> The result of this would be to cripple the network.</blockquote>The middle sentence is incomplete; it seems to be missing something. It's just a dangling subject, without an action. Anyone want to clue me in? If someone can give me the technical info I'll rewrite it, but I don't understand STP well enough to know what's being meant here. --[[User:Kadin2048|Kadin2048]] 21:37, 1 November 2006 (UTC)

* The reference to broadcast storms in the article is arguably incorrect. The LAN is flooded as a result of bridge loops, but a "broadcast storm" is defined by IETF and Cisco as network flooding as a result of an incorrect broadcast packet. So mentioning it here suggests that the problem is more restrictive than it is, i.e., if you avoid broadcasting you won't have the problem. But that's not the case - the flooding occurs whether you have broadcasting or not. The incorrectness of the mac-address-table will also occur, but since that's a problem internal to the bridges and not likely to be understandable to a lay reader without considerable explanation, I think the introduction should restrict itself to flooding as the big problem with bridge loops. [[User:Ngriffeth|Ngriffeth]] ([[User talk:Ngriffeth|talk]]) 15:29, 11 April 2008 (UTC)

*:At some point the article was changed to ues [[broadcast radiation]] terminology. ~[[User:Kvng|Kvng]] ([[User talk:Kvng|talk]]) 02:10, 25 November 2023 (UTC)

=== The Poem ===

Is it just me, or do the links mess up the poem? I know wikifying stuff is the way, it just seems so out of place in the poem. [[User:Nichlas|Nichlas]] 15:13, 16 January 2007 (UTC)