The MPLS-OPS Archive

Cell Relay Retreat>MPLS-OPS Archive>month:2004-Aug> msg00130



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

Re: MPLS aware NICs

  • From: Eric Osborne <eosborne@cisco.com>
  • Date: Fri, 20 Aug 2004 08:50:18 -0400
  • CC: "McCallum, Robert" <robert.mccallum@thus.net>, 'Bjørn_Mork' <bjorn@mork.no>, "Bell, John" <john.bell@thus.net>, mpls-ops@mplsrc.com
  • Resent-Date: Fri, 20 Aug 2004 09:10:09 -0400
  • To: Puddinhead Wilson <puddinghead_wilson007@yahoo.co.uk>
  • User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803)
  • X-BrightmailFiltered: true
  • X-Enigmail-Supports: pgp-inline, pgp-mime
  • X-Enigmail-Version: 0.85.0.0

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Puddinhead Wilson wrote:
| fine,
|
| but if someone asked you where you could find them ,
| would you be nice enough to tell them :)?
|

I don't believe they exist.  Usually that type of stuff is done in
software; grab some of the Linux stuff that does MPLS or roll your own.




eric

| -thanks
|
|  --- "McCallum, Robert" <robert.mccallum@thus.net>
| wrote:
|
|>Thinks about what this end device would need to do
|>to be able to do that
|>properly.
|>
|>Have a sizable routing table.
|>Hold a full LIB for the whole network.
|>RSVP signalling.
|>
|>Are we going to bring in FRR as well?
|>
|>All of the above can be done oddly enough on devices
|>called routers.  Leave
|>the end device to be noddy and let the magic get
|>done on boxes that it
|>should be done on.
|>
|>I still don't see any benefit from an mpls nic.
|>
|>Robert McCallum
|>CCIE #8757 R&S
|>01415663448
|>07818002241
|>
|>
|>>-----Original Message-----
|>>From: Bjørn Mork [mailto:bjorn@mork.no]
|>>Sent: 20 August 2004 12:33
|>>To: Bell, John
|>>Cc: McCallum, Robert; 'Puddinhead Wilson';
|>
|>mpls-ops@mplsrc.com
|>
|>>Subject: Re: [MPLS-OPS]: MPLS aware NICs
|>>
|>>
|>>"Bell, John" <john.bell@thus.net> writes:
|>>
|>>
|>>>	None that I'm aware of. As Steinar says, you'd
|>
|>have to
|>
|>>run a routing
|>>
|>>>protocol on your workstation/server for it to
|>
|>make any
|>
|>>sense. Equally,
|>>
|>>>making an NIC MPLS-aware means writing an MPLS
|>
|>stack in
|>
|>>software, so I
|>>
|>>>suppose  some guys in a Uni lab may write their
|>
|>own MPLS-aware NIC
|>
|>>>stack as a project, and run "routed" on a Linux
|>
|>box, just to
|>
|>>>understand whats happening. But there will never
|>
|>be a commercial
|>
|>>>reason to do it, as you need to turn your server
|>
|>into a software
|>
|>>>router. As we all know, this is a crappy idea
|>
|>when there
|>
|>>are perfectly
|>>
|>>>good (i.e a million times better) hardware
|>
|>routers around :-)
|>
|>>Let's say you want to do policy routing on your
|>
|>edge,
|>
|>>redirecting some packets to one or more servers
|>
|>located at a
|>
|>>central server farm.  To do this you need tunnels
|>
|>from the
|>
|>>edge routers to these servers.  Why not use MPLS
|>
|>tunnels?
|>
|>>The servers will have to terminate the tunnels no
|>
|>matter what
|>
|>>protocol is used.  But they don't have to do any
|>
|>forwarding,
|>
|>>and they don't really have to participate in the
|>
|>routing exchange.
|>
|>>I'd say that popping a label is much preferred to
|>
|>unwrapping
|>
|>>ipsec or gre or whatever, even if you don't
|>
|>qualify as a router ;-)
|>
|>>
|>>Bjørn
|>>
|>
|>
|
|
|
| 	
| 	
| 		
| ___________________________________________________________ALL-NEW
Yahoo! Messenger - all new features - even more fun!
http://uk.messenger.yahoo.com
|
| -------
| The MPLS-OPS Mailing List
| Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
| Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (MingW32)

iD8DBQFBJfOKYR4YGS5xhWIRAlGlAJwMFWLw0t3WGfqyU1fTLlETxpglagCfVhZb
EA+OJqQun0gWcVH10/sn9pw=
=IYKx
-----END PGP SIGNATURE-----

-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplsrc.com/mpls-ops_archive.shtml