Talk:Multiprotocol Label Switching

This is the talk page for discussing improvements to the Multiprotocol Label Switching article.
This is not a forum for general discussion of the article's subject.

Put new text under old text. Click here to start a new topic.
New to Wikipedia? Welcome! Learn to edit; get help.

Article policies

Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL

Archives: Index, 1: 2 years

Telecommunications High‑importance

	Telecommunication portal This article is within the scope of WikiProject Telecommunications, a collaborative effort to improve the coverage of Telecommunications 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.TelecommunicationsWikipedia:WikiProject TelecommunicationsTemplate:WikiProject TelecommunicationsTelecommunications
High	This article has been rated as High-importance on the project's importance scale.

Computing: Networking Low‑importance

	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
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 High-importance).

Needs diagram

Something like http://ipcisco.com/wp-content/uploads/mpls/MPLS_Header_color.JPG. ~KvnG 10:27, 25 June 2013 (UTC)[reply]

Label indication

It's not clear to me from this article how the presence of the label is indicated in the various layer 2 protocols? For example, VLAN tags in ethernet frames are indicated by the value in the TPID field that looks like an ethertype. Anyone got and can add this info for MPLS? Graham.Fountain | Talk 17:54, 12 March 2014 (UTC)[reply]

Okay, I found this information for myself: Ethertype values, 0x8847 and 0x8848. I'll see if I can add this to the article when I get a round tuit. Graham.Fountain | Talk 11:30, 13 March 2014 (UTC)[reply]

IP/MPLS instead of MPLS

Large parts of this article are only specific for IP/MPLS, the MPLS version that is intended for core networks, and is based on dynamical MPLS routing.

The distinction between IP/MPLS and MPLS is lacking.

Another profile of MPLS is called MPLS-TP and is intended for transport networks. This relies on statically provisioned end-to-end paths (LSP and pseudowires) throughout the MPLS network.

Better would be to move large parts of this page to a new page concerning IP/MPLS, and have this MPLS-page to refer to it and to the existing MPLS-TP page.

déRahier ^talk⁺^contrib 14:04, 9 February 2015 (UTC)[reply]

Is this comparison with ATM right?

In particular, MPLS dispenses with the cell-switching and signaling-protocol baggage of ATM. MPLS recognizes that small ATM cells are not needed in the core of modern networks, since modern optical networks are so fast (as of 2008, at 40 Gbit/s and beyond) that even full-length 1500 byte packets do not incur significant real-time queuing delays (the need to reduce such delays — e.g., to support voice traffic — was the motivation for the cell nature of ATM).
I thought the size of ATM voice packets was not to reduce the transport queuing delay, but to reduce the queuing delay as the voice packet is generated or used, which is caused by the voice sample rate not the transport rate. For example, the 64 kb/s sampling rate of the standard G.711 voice codec, with packets at 6ms, gives a packet size of 48 bytes, which fits the ATM payload size of 48 octets per cell. This has nothing to do with the transport rate, just the sampling rate and the (old) latency requirements of the PSTN, so mentioning the speed of modern optical networks here is a bit misleading. What is relevant is that the fraction of traffic which is non-PSTN/voice is increasing. I have no references for this. There are no references in the quoted paragraph either. If someone who is an expert and who knows the references sees my point, perhaps they could edit the quoted paragraph in the article, and put in references even if I am mistaken. JustGonnaFixIt (talk) 17:17, 26 October 2015 (UTC)[reply]

Competitor Protocols

This line: "The major goal of MPLS development was the increase of routing speed. This goal is no longer relevant," appears dubious to me. The whole paragraph has had a cit request for nearly 3 years, and no one has provided any substantiation. It may be that something relevant is being said here, but the paragraph does not explain how a technology such as Application-specific integrated circuits obviates the MPLS goal of routing speed. Am I just missing the point here? Or can this go? -- Sirfurboy (talk) 14:49, 4 December 2019 (UTC)[reply]

Citations: added ✅. Symbol (talk) 17:36, 4 December 2019 (UTC)[reply]