Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Lucent Technologies (LU) -- Ignore unavailable to you. Want to Upgrade?

To: djane who wrote (3785)	8/25/1998 10:52:00 AM
From: aladin	Read Replies (3) \| Respond to of 21876

djane, << Hasn't ASND also been very early on the MPLS bandwagon compared << to the CSCO focus on tag switching? At the IETF cisco arrived with the Tag Switching proposal, IBM had a similar, but different approach. The committee accepted these proposals and melded them into what is now called MPLS (MultiProtocol Label Switching). Cisco is fully MPLS compliant and was the first vendor shipping code and has done extensive interoperability testing with several partners. ASND does not yet have a product offering in this area. Since we started with TAG, MPLS is still called TAG internally and in our literature - so the confusion is pretty normal :-) John

To: djane who wrote (3785)	8/25/1998 11:03:00 AM
From: Frank A. Coluccio	Read Replies (1) \| Respond to of 21876

Hi djane, >>Hasn't ASND also been very early on the MPLS bandwagon compared to the CSCO focus on tag switching?<< Did you notice that the article called it tag swapping? Interesting article. MPLS is a compromised-derivative in progress of CSCO's original proposed Tag Switching protocol. The other major vendors couldn't just sit back and watch CSCO dictate all of the rules, in their entirety. So, true to IETF form, an RFC was created to seek multiple inputs and opinions re the protocol, and CSCO is still a major force there, whether you call it Tag or MPLS. CSCO is poised to support both: their tag switching now, and the MPLS when the smoke settles. I found this comment interesting in the article: >Juniper also formed a strategic technology relationship with IBM.< It's little wonder as to why this is. CSCO is postured at this time to eat Blue's lunch on the channel side of the mainframe for big host to host communications and other SNA/VTAM bulk data transfers, through their (CSCO) SNA over IP options. Blue's own options don't measure up to the task of tsunami data flows in this space in a way that would be acceptable to data center users, so they need a way to fend off CSCO's encroachment here. FWIW, and Best Regards, Frank Coluccio