The MPLS-OPS Archive

Cell Relay Retreat>MPLS-OPS Archive>month:2005-Jan> msg00044



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

Re: MPLS on Interface/ recursive VPNS

  • From: Devendra.Vyas@relianceinfo.com
  • Date: Sat, 22 Jan 2005 08:50:05 +0530
  • Cc: mpls-ops@mplsrc.com
  • Resent-Date: Fri, 21 Jan 2005 22:42:44 -0500
  • X-MIMETrack: Serialize by Router on RILWHUB010/SVR/RIL(Release 6.5|September 26, 2003) at01/22/2005 08:50:13 AM
  • X-SpamProbe: GOOD 0.0000000 c1161ce9c6b1aa3187674eaebc407be9

OK.

so then how does MPLS decide whether -

packet x needs to be stamped (or not)?

what trigger converts the potential push into actual?

suppose there is an MPLS cloud - running IGP,MPLS and LDP and there are no TE-LSP'S and NO VPN's...

and within the cloud i ftp from router x to router y --will that traffic be label switched?





> what exactly are the implications of enabling MPLS on an interface....

It normally means the interface can *potentially* be used to push/pop/
swap MPLS labels, ie. facing another P or PE router.

> does it mean that every incoming packet will be stamped with a label ?

Absolutely not.

> and every incoming labelled packet will be label switched

An MPLS enabled interface will normally handle a mix of labeled and
unlabeled packets. Incoming unlabeled packets can be regular IP traffic
(routing, Internet in a global routing table, etc) and various other
types (e.g. Cisco CDP).

Steinar Haug, Nethelp consulting, sthaug@nethelp.no
 ------- The MPLS-OPS Mailing List Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml Archive: http://www.mplsrc.com/mpls-ops_archive.shtml