Talk:Multi-chassis link aggregation group

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
Low	This article has been rated as Low-importance on the project's importance scale.
	This article is supported by Networking task force (assessed as Low-importance).

Copy-paste[edit]

The text looks like it was copied out of some technical journal which is re-inforced when you see verbage such as "A basic use of LAG to “trunk” 4 Ethernet links is shown in the figure below." which refers to a non-existent diagram. -- Whpq 20:10, 3 December 2007 (UTC)[reply]

Summary of Inaccuracies[edit]

1. 802.3ad has been moved to 802.1AX-2008. 2. 802.1AX specifically states that no options for "multipoint aggregation" among "more than two systems" are included. All multipoint LAG operations fall into the non-standard realm of vendor-specific implementations. 3. As noted previously, the content of the article seems to rely on an unattributed source, based on the language and phrasing used throughout.

As I understand it, there are discussions of standardizing MC-LAG from an LACP perspective, but I could not readily find any progress made in this area from an IEEE or IETF perspective.

It's also important to note that any work within the IETF's TRILL working group does not have an direct correlation to the aggregation of the links of a host in a multipoint configuration (such as Cisco's Virtual Port Channel). —Preceding unsigned comment added by Ccie14745 (talk • contribs) 19:09, 2 March 2010 (UTC)[reply]

Ccie14745, regarding your point (2), I cannot find the phrases you quote in a search of 802.1AX-2008; can you provide section numbers? Agreed that the standard does not cover MC-LAG. -- Fiona-bc

2012-03-15 -- Revised text, correct name of the standard, clarified that MC-LAG not covered by the standard, added headings, added references. -- Fiona-bc — Preceding unsigned comment added by Fiona-bc (talk • contribs) 21:49, 15 March 2012 (UTC)[reply]

MC-LAG is usually called MLAG and while the article mentions multiple vendors have products, no brands are mentioned... I know Arista, Brocade, Cisco, Juniper, HP at least have products with some form of MLAG support, probably more exist.

some links I found while googling:

http://www.networkcomputing.com/data-networking-management/when-mlag-is-good-enough/229500378

http://blog.ioshints.info/2011/03/data-center-fabric-architectures.html — Preceding unsigned comment added by 95.97.89.98 (talk) 08:00, 11 September 2012 (UTC)[reply]

Factually incorrect (for about two years now)[edit]

The IEEE 802.1ax-2008 does define MC-LAG; the thing that's not standardized therein are some hash functions that are vendor specific. I'll try to find some secondary refs clarifying this and the purpose of MC-LAG as well, which is clear as mud from current writeup. Someone not using his real name (talk) 02:45, 16 December 2013 (UTC)[reply]

2015-07-02

I added an original diagram and text comparing MC-LAG to LAG in order to elucidate the purpose and function of MC-LAG. Also, I added a list of vendors who have implemented it, along with the names they use to refer to their implementations.

Maybe w're almost ready to do away with one or both of the dispute tags. Curtmcd (talk) 04:30, 3 July 2015 (UTC)[reply]

MC-LAG is standardized as part of IEEE Std. 802.1AX-2014[edit]

The MC-LAG is referred to as Distributed Resilient Network Interconnect (DRNI) in 802.1AX-2014 .

For an overview refer to the IEEE press release at: https://standards.ieee.org/news/2015/ieee_802_1ax.html

15.203.233.83 (talk) 22:23, 7 December 2017 (UTC)[reply]