Talk:IEEE 802.1aq/Archive 1

Good article (on a technical level), but...
You can expect coverage in Wikipedia to be inversely proportional to the real-world success/penetration. (Also, Ashwood-Smith / User:Peterashwoodsmith who is the major contributor to this article has an obvious WP:COI.) Someone not using his real name (talk) 00:45, 16 December 2013 (UTC)

IEEE 802.1aq Technology Popular Page ranking & page views
Statistics Indicate that Shortest Path Bridging has become a popular Technology.

66.140.241.100 (talk) 17:15, 4 December 2014 (UTC)

Structure, trimming
Articles work best if they have "levels" in their structure. I've made a first attempt at this just now, and also done some trimming. (Much more is required though, this article is shocking). Snori (talk) 00:31, 16 October 2015 (UTC)

Product and deployment sections
JMHO - Product and deployment sections provide good multi-vendor documentation and references for acceptance/usage proofs of a relatively new protocol. FL-StateU-IT-9999 (talk) 09:50, 8 February 2015 (UTC)
 * I have trimmed a lot of this out. If you've just bought a bunch of netweork gear Wikipedia should not be where you go to find specific product support. Snori (talk) 00:31, 16 October 2015 (UTC)
 * Agreed Wikipedia is not a support site, but when researching new protocols we need to understand if businesses are using or even benefiting from them or not. This information is very important for that. HP-Engineer99 (talk) 08:07, 28 October 2015 (UTC)

Deployments
Deployment considerations and interoperability best practices are documented in an IETF document titled "SPB Deployment Considerations"
 * 2013 Interop: Networking Leaders Demo Shortest Path Bridging
 * 2014 Interop: InteropNet Goes IPv6, Includes Shortest Path Bridging

Avaya is currently the leading exponent of SPB-based deployments; their enhanced and extended implementation of SPB - including integrated Layer 3 IP Routing and IP Multicast functionality - is marketed under the banner of the "Avaya VENA Fabric Connect" technology. Additionally, Avaya is supporting an IETF Internet Draft that defines a means of extended SPBM-based services to end-devices via conventional Ethernet Switches, leveraging an 802.1AB LLDP-based communications protocol; this capability - marketing by Avaya as "Fabric Attach" technology - allows for the automatic attachment of end-dvices, and includes dynamic configuration of VLAN/I-SID (VSN) mappings.

Avaya have deployed SPB/Fabric Connect solutions for businesses operating across a number of industry verticals:
 * Education, examples include: Leeds Metropolitan University, Macquaire University, Pearland Independent School District, Ajman University of Science & Technology
 * Transportation, examples include: Schiphol Telematics, Rheinbahn, Sendai City Transportation Bureau, NSB
 * Banking & Finance, examples include: Fiducia, Sparebanken Vest
 * Major Events, examples include: 2013 & 2014 Interop (InteropNet Backbone), 2014 Sochi Winter Olympics, Dubai World Trade Center
 * Healthcare, examples include: Oslo University Hospital, Concord Hospital, Franciscan Alliance, Sydney Adventist Hospital
 * Manufacturing, examples include: Fujitsu Technology Solutions
 * Media, examples include: Schibsted, Medienhaus Lensing, Sanlih Entertainment Television
 * Government, examples include: City of Redondo Beach, City of Breda, Bezirksamt Neukölln

Product Support

 * Alcatel-Lucent 7750-SR, OmniSwitch 6900, OmniSwitch 10K


 * Avaya VSP 9000 Series
 * Avaya VSP 8000 Series
 * Avaya VSP 7000 Series
 * Avaya VSP 4000 Series   (VSP 4450GSX-PWR+, VSP 4850GTS, VSP 4850GTS-PWR+, VSP 4850GTS-DC)
 * Avaya ERS 8800 Series / ERS 8600 Series
 * Avaya ERS 4800 Series


 * Enterasys Networks S140 and S180


 * Huawei S9300 (prototype only at the moment)


 * Solana


 * Spirent


 * HP 5900, 5920, 5930, 11900, 12500, 12900


 * IP Infusion's ZebOS network platform


 * IXIA


 * JDSU

Too technical
I found the article interesting, but the very dense use of acronyms and an implied assumption of á priori knowledge made it difficult to read. I'm a CS mayor, and maybe that's why I read the whole thing, but networking is not my strong suite. This article made that very clear, and I wonder how someone from another field would react.

The style feels like it copied from somewhere else, especially the section about deployments which seams, at least to my eye, like an advertisement. With that being said, I again would like state that I really found it quite enlightening and thank whoever wrote this.

Max Nordlund (talk) 22:02, 5 January 2015 (UTC)

I agree - having spent some time in 802.1 committees, I know acronyms become really ingrained, but they really should at least be defined when first used. e.g. "Both SPBV and SPBM inherit key benefits of link state routing" is the first mention of either. Making a quick edit to this line. Ma-Ma-Max Headroom (talk) 20:58, 6 June 2016 (UTC)

Is the "S" included by mistake ?
Shortest Path Bridging Media Access Control (MAC) or (SPBM), (previously known as Provider Backbone Bridge SPBB) provides additional values which capitalize on Provider Backbone Bridge (PBB) capabilities. Should the "S" be in front of "SPBB" if PBB means Provider Backbone Bridge ? --161.185.160.89 (talk) 02:22, 3 March 2017 (UTC) Gregory Raymond T.I.A.

External links modified
Hello fellow Wikipedians,

I have just modified 4 external links on IEEE 802.1aq. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20140513215409/http://www.avaya.com/ru/resource/assets/casestudies/DN7191EN-Sochi.pdf to http://www.avaya.com/ru/resource/assets/casestudies/DN7191EN-Sochi.pdf
 * Added archive https://web.archive.org/web/20101216050519/http://ciol.com/Technology/Networking/Products/Avaya-rolls-out-networking-blueprint-for-data-centre/143333/0/ to http://www.ciol.com/Technology/Networking/Products/Avaya-rolls-out-networking-blueprint-for-data-centre/143333/0/
 * Added archive https://web.archive.org/web/20140302181237/http://www.networkworld.com/news/2013/061813-enterasys-270953.html to http://www.networkworld.com/news/2013/061813-enterasys-270953.html
 * Added archive https://www.webcitation.org/6AtzL8Er1?url=http://www.apricot-apan.asia/__data/assets/powerpoint_doc/0013/32008/APRICOT_SPB_Overview.ppt to http://www.apricot-apan.asia/__data/assets/powerpoint_doc/0013/32008/APRICOT_SPB_Overview.ppt
 * Added tag to http://www.avaya.com/usa/resource/assets/factsheet/Introduction_to_Shortest_Path_Bridging_dn4799.pdf

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 03:33, 10 November 2017 (UTC)