Traffic Engineering through MPLS in Service Provider Networks

MPLS was originally designed to make IP routers are as fast as ATM switches for handling traffic. Just as in any other technology. MPLS has a specialized terminology all its own. An MPLS domain is the collection of routers running MPLS under the control of a single Administrator. An LSP (label-switc...

Full description

Saved in:
Bibliographic Details
Published in:International journal of computer applications 2013-01, Vol.72 (11), p.1-6
Main Authors: Devi, Y Rama, Ramadasu, B, Raj Gopal, B H
Format: Article
Language:English
Subjects:
Egress
Entrances
IP (Internet Protocol)
Routers
Running
Terminology
Traffic engineering
Traffic flow
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
cited_by
cites
container_end_page 6
container_issue 11
container_start_page 1
container_title International journal of computer applications
container_volume 72
creator Devi, Y Rama
Ramadasu, B
Raj Gopal, B H
description MPLS was originally designed to make IP routers are as fast as ATM switches for handling traffic. Just as in any other technology. MPLS has a specialized terminology all its own. An MPLS domain is the collection of routers running MPLS under the control of a single Administrator. An LSP (label-switched path) is a one-way (unidirectional) Flow of traffic, carrying packets from beginning to end. Packets must enterThe LSP at the beginning (ingress) of the path, and can only exit the LSP At the end (egress). Packets cannot be injected into an LSP at an intermediate hop. Generally, an LSP remains within a single MPLS domain. That is, the Entrance and exit of the LSP, and all routers in between, are ultimately in control of the same administrative authority. This ensures that MPLS LSP Traffic engineering is not done haphazardly or at cross purposes but is implemented in a coordinated fashion.
doi_str_mv 10.5120/12535-8916
format article
fullrecord <record><control><sourceid>proquest_cross</sourceid><recordid>TN_cdi_proquest_miscellaneous_1417892821</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><sourcerecordid>3010823951</sourcerecordid><originalsourceid>FETCH-LOGICAL-c1326-574c46bfcf5fe797852999c1a8872990c3ce3eadf29c61a6458bc6142f9b762d3</originalsourceid><addsrcrecordid>eNpdkMtKQzEURYMoWGonfkHAiQhXb97JwIGU-oCqhdZxSNOkTW1vatJb8e9NrQPxTM4aLDabDcA5qq8ZwvUNwoywSirEj0CnVqKwlOL4D5-CXs7LuhxRmCvaAbeTZLwPFg6aeWicS6GZw-0ixXa-gM-j4RiGBo5d2gXr4CjFXZi5BF_c9jOm93wGTrxZZdf7_V3wdj-Y9B-r4evDU_9uWFlEMK-YoJbyqbeeeSeUkAwrpSwypVKh2hLriDMzj5XlyHDK5LQAxV5NBccz0gWXh9xNih-ty1u9Dtm61co0LrZZI4qEVFhiVNSLf-oytqkp7TQiggpMJKPFujpYNsWck_N6k8LapC-Nar0fU_-Mqfdjkm_fYmPb</addsrcrecordid><sourcetype>Aggregation Database</sourcetype><iscdi>true</iscdi><recordtype>article</recordtype><pqid>1374723854</pqid></control><display><type>article</type><title>Traffic Engineering through MPLS in Service Provider Networks</title><source>Freely Accessible Science Journals - check A-Z of ejournals</source><creator>Devi, Y Rama ; Ramadasu, B ; Raj Gopal, B H</creator><creatorcontrib>Devi, Y Rama ; Ramadasu, B ; Raj Gopal, B H</creatorcontrib><description>MPLS was originally designed to make IP routers are as fast as ATM switches for handling traffic. Just as in any other technology. MPLS has a specialized terminology all its own. An MPLS domain is the collection of routers running MPLS under the control of a single Administrator. An LSP (label-switched path) is a one-way (unidirectional) Flow of traffic, carrying packets from beginning to end. Packets must enterThe LSP at the beginning (ingress) of the path, and can only exit the LSP At the end (egress). Packets cannot be injected into an LSP at an intermediate hop. Generally, an LSP remains within a single MPLS domain. That is, the Entrance and exit of the LSP, and all routers in between, are ultimately in control of the same administrative authority. This ensures that MPLS LSP Traffic engineering is not done haphazardly or at cross purposes but is implemented in a coordinated fashion.</description><identifier>ISSN: 0975-8887</identifier><identifier>EISSN: 0975-8887</identifier><identifier>DOI: 10.5120/12535-8916</identifier><language>eng</language><publisher>New York: Foundation of Computer Science</publisher><subject>Egress ; Entrances ; IP (Internet Protocol) ; Routers ; Running ; Terminology ; Traffic engineering ; Traffic flow</subject><ispartof>International journal of computer applications, 2013-01, Vol.72 (11), p.1-6</ispartof><rights>Copyright Foundation of Computer Science 2013</rights><oa>free_for_read</oa><woscitedreferencessubscribed>false</woscitedreferencessubscribed></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><link.rule.ids>314,780,784,27924,27925</link.rule.ids></links><search><creatorcontrib>Devi, Y Rama</creatorcontrib><creatorcontrib>Ramadasu, B</creatorcontrib><creatorcontrib>Raj Gopal, B H</creatorcontrib><title>Traffic Engineering through MPLS in Service Provider Networks</title><title>International journal of computer applications</title><description>MPLS was originally designed to make IP routers are as fast as ATM switches for handling traffic. Just as in any other technology. MPLS has a specialized terminology all its own. An MPLS domain is the collection of routers running MPLS under the control of a single Administrator. An LSP (label-switched path) is a one-way (unidirectional) Flow of traffic, carrying packets from beginning to end. Packets must enterThe LSP at the beginning (ingress) of the path, and can only exit the LSP At the end (egress). Packets cannot be injected into an LSP at an intermediate hop. Generally, an LSP remains within a single MPLS domain. That is, the Entrance and exit of the LSP, and all routers in between, are ultimately in control of the same administrative authority. This ensures that MPLS LSP Traffic engineering is not done haphazardly or at cross purposes but is implemented in a coordinated fashion.</description><subject>Egress</subject><subject>Entrances</subject><subject>IP (Internet Protocol)</subject><subject>Routers</subject><subject>Running</subject><subject>Terminology</subject><subject>Traffic engineering</subject><subject>Traffic flow</subject><issn>0975-8887</issn><issn>0975-8887</issn><fulltext>true</fulltext><rsrctype>article</rsrctype><creationdate>2013</creationdate><recordtype>article</recordtype><recordid>eNpdkMtKQzEURYMoWGonfkHAiQhXb97JwIGU-oCqhdZxSNOkTW1vatJb8e9NrQPxTM4aLDabDcA5qq8ZwvUNwoywSirEj0CnVqKwlOL4D5-CXs7LuhxRmCvaAbeTZLwPFg6aeWicS6GZw-0ixXa-gM-j4RiGBo5d2gXr4CjFXZi5BF_c9jOm93wGTrxZZdf7_V3wdj-Y9B-r4evDU_9uWFlEMK-YoJbyqbeeeSeUkAwrpSwypVKh2hLriDMzj5XlyHDK5LQAxV5NBccz0gWXh9xNih-ty1u9Dtm61co0LrZZI4qEVFhiVNSLf-oytqkp7TQiggpMJKPFujpYNsWck_N6k8LapC-Nar0fU_-Mqfdjkm_fYmPb</recordid><startdate>20130101</startdate><enddate>20130101</enddate><creator>Devi, Y Rama</creator><creator>Ramadasu, B</creator><creator>Raj Gopal, B H</creator><general>Foundation of Computer Science</general><scope>AAYXX</scope><scope>CITATION</scope><scope>7SC</scope><scope>8FD</scope><scope>JQ2</scope><scope>L7M</scope><scope>L~C</scope><scope>L~D</scope></search><sort><creationdate>20130101</creationdate><title>Traffic Engineering through MPLS in Service Provider Networks</title><author>Devi, Y Rama ; Ramadasu, B ; Raj Gopal, B H</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-c1326-574c46bfcf5fe797852999c1a8872990c3ce3eadf29c61a6458bc6142f9b762d3</frbrgroupid><rsrctype>articles</rsrctype><prefilter>articles</prefilter><language>eng</language><creationdate>2013</creationdate><topic>Egress</topic><topic>Entrances</topic><topic>IP (Internet Protocol)</topic><topic>Routers</topic><topic>Running</topic><topic>Terminology</topic><topic>Traffic engineering</topic><topic>Traffic flow</topic><toplevel>online_resources</toplevel><creatorcontrib>Devi, Y Rama</creatorcontrib><creatorcontrib>Ramadasu, B</creatorcontrib><creatorcontrib>Raj Gopal, B H</creatorcontrib><collection>CrossRef</collection><collection>Computer and Information Systems Abstracts</collection><collection>Technology Research Database</collection><collection>ProQuest Computer Science Collection</collection><collection>Advanced Technologies Database with Aerospace</collection><collection>Computer and Information Systems Abstracts – Academic</collection><collection>Computer and Information Systems Abstracts Professional</collection><jtitle>International journal of computer applications</jtitle></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext</fulltext></delivery><addata><au>Devi, Y Rama</au><au>Ramadasu, B</au><au>Raj Gopal, B H</au><format>journal</format><genre>article</genre><ristype>JOUR</ristype><atitle>Traffic Engineering through MPLS in Service Provider Networks</atitle><jtitle>International journal of computer applications</jtitle><date>2013-01-01</date><risdate>2013</risdate><volume>72</volume><issue>11</issue><spage>1</spage><epage>6</epage><pages>1-6</pages><issn>0975-8887</issn><eissn>0975-8887</eissn><abstract>MPLS was originally designed to make IP routers are as fast as ATM switches for handling traffic. Just as in any other technology. MPLS has a specialized terminology all its own. An MPLS domain is the collection of routers running MPLS under the control of a single Administrator. An LSP (label-switched path) is a one-way (unidirectional) Flow of traffic, carrying packets from beginning to end. Packets must enterThe LSP at the beginning (ingress) of the path, and can only exit the LSP At the end (egress). Packets cannot be injected into an LSP at an intermediate hop. Generally, an LSP remains within a single MPLS domain. That is, the Entrance and exit of the LSP, and all routers in between, are ultimately in control of the same administrative authority. This ensures that MPLS LSP Traffic engineering is not done haphazardly or at cross purposes but is implemented in a coordinated fashion.</abstract><cop>New York</cop><pub>Foundation of Computer Science</pub><doi>10.5120/12535-8916</doi><tpages>6</tpages><oa>free_for_read</oa></addata></record>
fulltext fulltext
identifier ISSN: 0975-8887
ispartof International journal of computer applications, 2013-01, Vol.72 (11), p.1-6
issn 0975-8887
0975-8887
language eng
recordid cdi_proquest_miscellaneous_1417892821
source Freely Accessible Science Journals - check A-Z of ejournals
subjects Egress
Entrances
IP (Internet Protocol)
Routers
Running
Terminology
Traffic engineering
Traffic flow
title Traffic Engineering through MPLS in Service Provider Networks
url http://sfxeu10.hosted.exlibrisgroup.com/loughborough?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2024-12-25T20%3A59%3A40IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-proquest_cross&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.genre=article&rft.atitle=Traffic%20Engineering%20through%20MPLS%20in%20Service%20Provider%20Networks&rft.jtitle=International%20journal%20of%20computer%20applications&rft.au=Devi,%20Y%20Rama&rft.date=2013-01-01&rft.volume=72&rft.issue=11&rft.spage=1&rft.epage=6&rft.pages=1-6&rft.issn=0975-8887&rft.eissn=0975-8887&rft_id=info:doi/10.5120/12535-8916&rft_dat=%3Cproquest_cross%3E3010823951%3C/proquest_cross%3E%3Cgrp_id%3Ecdi_FETCH-LOGICAL-c1326-574c46bfcf5fe797852999c1a8872990c3ce3eadf29c61a6458bc6142f9b762d3%3C/grp_id%3E%3Coa%3E%3C/oa%3E%3Curl%3E%3C/url%3E&rft_id=info:oai/&rft_pqid=1374723854&rft_id=info:pmid/&rfr_iscdi=true