SI
SI
discoversearch

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 : Ascend Communications (ASND) -- Ignore unavailable to you. Want to Upgrade?


To: djane who wrote (49695)7/13/1998 1:45:00 AM
From: djane  Respond to of 61433
 
Convergence Monster Mash [Discussion of LU and ERICY purchase of ASND]

techweek.com

With Cisco battling Lucent and AT&T-TCI facing off
against Sprint et al, small companies take cover

by Amara D. Angelica

The long-predicted convergence of datacom and telecom is here. Two formerly
incompatible technologies-the Internet for data and telephone-switching
systems for voice-are merging. The result will radically change business
communications, lowering wide-area-networking costs and creating new services
and career paths.

Cisco, Lucent, and Ascend have announced new products that bring these
technologies together and raise the bar in the highly competitive networking
business. In early June, Cisco announced four ATM switches for service
providers such as MCI, Sprint, and AT&T. Lucent and Ascend have also made
important new-product announcements over the past month.

Cisco, the world's largest data communications hardware company, has grown
into the "gorilla" of its marketplace, according to Silicon Valley consultant
Geoffrey Moore, co-author of The Gorilla Game (see "Cisco: the Making of a
Gorilla," Feb. 23 issue). A gorilla refers to a company whose technology is so
dominant that it defines its field-such as Microsoft in operating systems or Intel
in ICs.

But with its foray into ATM technology, Cisco seems to have grown from gorilla
into Godzilla, devouring companies left and right and challenging telecom giants
Lucent Technologies and Nortel. In fact, Cisco CEO John Chambers recently told
Computer Reseller News that it plans to add another 10 to 15 acquisitions to the
24 it has bitten off since 1993.

Several rapidly emerging technologies are driving the lucrative multibillion-dollar
enterprise ATM market: "voice over IP" (low-cost telephone calls via the Internet),
"video over IP," virtual private networks (see "The rush is on for Virtual Private
Networks," June 1 issue), and network commerce services.

To provide each of these services, service providers need to integrate
conventional IP (Internet protocol) technologies (such as routers, which are used
by both enterprises and Internet service providers to route Internet traffic) with
ATM (see "ATM vs. IP," page 19). ATM is already well on its way-a $686 million
market in FY '97, according to Portola-based market research firm Dell'Oro Group,
led by Fore, Cisco, Bay Networks, 3Com, and IBM, in descending order by
enterprise-switch revenues. The worldwide ATM market is projected at $8 billion
by 2002, according to San Jose-based Dataquest.


"ATM has turned the corner in terms of being accepted as a viable technology for
service integration in wide area networks," says Tim Smith, Dataquest principal
analyst, WAN. "One only needs to look at the recent Sprint and Bell Atlantic
announcements for evidence of ATM's growing acceptance with large service
providers."

Sprint plans to use ATM as a cornerstone of its new low-cost ION service (see
"Sprint Drops a Big Pin," page 1). Bell Atlantic plans to offer ATM services to all
of its business customers (see ba.com.

IP+ATM

But ATM by itself is limited because it can't efficiently handle IP (Internet) traffic.
This is a major priority for leaders in both the IP and ATM camps as they fight for
global datacom/telecom domination.

On the datacom networking side, San Jose-based Cisco ($6.4 billion 1997
revenues) is aggressively attacking the telephone-switch market, which is long the
exclusive province of telecom vendors. Cisco also claims it has developed a more
effective way to integrate IP with ATM.

On the telecom side, Canadian manufacturer Nortel has agreed to acquire Santa
Clara-based Bay Networks ($2.1 billion revenues in '97) to launch Nortel in the
router market-Cisco's bread and butter. Lucent Technologies is not far behind.

Preparing their own IP-ATM integration battle plans are Pittsburgh,
Pennsylvania-based Fore Systems; Newbridge Networks of Herndon, Va.; and two
other major Bay Area router vendors: Santa Clara-based 3Com ($3.2 billion in '97)
and Alameda-based Ascend ($1.1 billion in '97). Ascend is a rumored candidate for
acquisition by European telco-equipment giant Ericsson, which has recently
established a presence in North America.

According to Smith, Ericsson has not been a strong ATM player in the U.S., so
Ericsson would bring little value to Ascend's position here. "Ericsson has been
stronger outside the US, particularly in Western Europe, and this could be of
greater value to Ascend," Smith says. "The real impact of this acquisition would
be to create a large, experienced central-office provider with a strong ATM
portfolio to compete with Lucent, Cisco, Siemens, and Nortel for the service
provisioning business.
Given recent industry events, Newbridge must be
considered as one of the next logical candidates for acquisition."In early June,
Cisco staked out new territory with its new line of "IP+ATM" products. These
enable service providers to connect enterprise customers' IP networks with
high-powered ATM networks. "These new products are fairly impressive," says
Smith. "Cisco has taken a price leadership position while offering increased
functionality. They're like the Chicago Bulls-until somebody shows they can
beat them, they have to be considered among the favorites."

These new products fall into two categories: "edge" switches, which connect to
enterprises or telephone-company central offices (CO); and "core" switches,
which connect edge switches to each other and to a backbone network. The
switches offer "tag switching" (an implementation of the emerging Multi-Protocol
Label Switching or MPLS standard), which are new techniques that allow IP
routing and forwarding on ATM-based networks.

The Cisco MGX 8800 edge switch handles DS-0 (64 Kbps) up to OC48c (2.5
Gbps) interfaces, with up to 45 Gbps of total switching capacity. It
supports a full range of service interfaces, including voice over IP, IP
routing and forwarding, SNA, and frame relay. Cisco claims DS-1 (1.5
Mbps) prices at one-half of the competition. Sprint and U.S. West are
planning to deploy the MGX 8800.

The BPX 8680 is a similar product but for very large service-provider sites,
supporting up to 16,000 DS-l lines.

The BPX 8650 core switch allows for immediate upgrade of Cisco's 8650
core switch for IP+ATM services.

The Cisco TGX 8750 core switch, due out next year, will handle up to
OC-48 speed and will scale up to terabit speeds.

On May 4, Cisco acquired Class Data Systems Ltd. (Israel, with a Cupertino office),
which has developed a "policy server" with integrated directory services. This hot
software allows any application to reserve ATM bandwidth without requiring net
managers to rewrite code.

The recent announcements by Cisco, Lucent, and Ascend "illustrate the tenacity
with which the largest players in the networking business are targeting each
other's traditional areas of strength," says Smith.

"The service provisioning marketplace will not be for the faint of heart. Cisco's
continuing development of larger, more functional multiservice platforms aimed at
large service providers directly challenges Lucent's dominance in the central
office. And Lucent's announcement of IP-based networking products directly
challenges Cisco's dominance in all things IP."

Cisco has another reason to worry: Lucent has filed a patent-infringement suit
against Cisco. The complaint, which "has no merit," according to Cisco CFO Larry
Carter, involves routers, frame relay network equipment, and ATM equipment.
That goes to the heart of Cisco's strategy of expanding further into the Internet
and telephone marketplaces.

Also, we all know what happened to Godzilla in the end.

Nortel-Bay Networks join-in prayer

Northern Telecom's $9.1 billion acquisition of Bay Networks is either a smart,
market-based transaction or a "Hail Mary" pass. Or both. It all depends on which
analyst you ask. But regardless of the reason, they agree the merger has
destabilized the industry's strategic balance and is certain to accelerate
tele/datacom mergermania.

Northern Telecom [Nortel], based in Mississauga, Ontario, Canada, and Bay
Networks of Santa Clara say their merger was based on the need for an
"end-to-end solution." Their joint announcement vaguely defined this solution as
"mission-critical Internet Protocol (IP) integrated networks that will reach anyone,
anytime, at any place in the world."

In reality, Nortel needs Bay's IP and packet-based technology to supplement its
circuit-switched systems, and Bay needs a larger partner now that it has clearly
lost the market-share battle with Cisco.

"It's a very smart move for Nortel, although I don't buy the hype behind their
reasoning," says Christine Heckart, vice president of Telechoice, a Tulsa-based
consulting and research firm.

Heckart says that Nortel, which has long battled with Lucent for the top position
in the older, circuit-switched telephone equipment business, has grown concerned
over moves by Cisco to branch out from its enterprise data communications
dominance into the telecommunications industry.

"If I am Nortel and see Cisco as a new competitor," Heckart explains, "then it
makes sense for me to buy the number-two enterprise WAN [wide area network]
provider. It gives me an instant footprint here and the opportunity to provide an
end-to-end solution."

Good old competition may have also figured into the equation, says Heckart. She
points out that currently, Lucent resells a significant amount of Bay Networks
equipment. "They [Nortel] could see the Bay purchase as a way to deprive Lucent
of products they need."

Heckart says an uneasy relationship could still exist with Lucent continuing to
resell Bay Networks equipment, but probably only if Bay remained as a brand. A
Nortel spokesman tells TechWeek that Bay would remain as a brand, at least for
the time being.


Regardless of whether or not Bay remains a brand, the merger can only whet
Lucent's appetite to buy its own end-to-end solution. Sources say Lucent has
been kicking the tires of both Ascend Communications and 3Com. But Lucent isn't
the only tire kicker in the arena. Ericsson and others have also been looking at
these and other datacom firms.


From its dominant datacom perch, Cisco sees the mergers as inevitable.

Don Listwin, executive vice president of the service-provider line of business at
Cisco Systems, tells TechWeek that: "As data, voice, and video begin to come
together, it's clear to the market that the Internet will drive this convergence.
Certainly, industry consolidation will occur, particularly as Old World companies
look for ways to compete in this Internet-driven economy. Cisco anticipated this
new competition and believes that our leadership in data networking positions us
well in this New World."

Cisco has no comment on the observations of Sand Hill Road insiders whose
less-charitable assessment characterizes the merger as a Hail Mary pass with a lot
of praying at both Bay and Nortel. These sources say they believe Bay is
desperate now that Cisco has pulled so far ahead of them. For its part, Nortel
realizes it has a solid position in circuit-switching equipment, which is rapidly
becoming obsolete.

"Their [Nortel's] biggest competitor isn't Lucent," says one investment banker.
"It's progress."


Look for more prayers and mergers over the coming weeks. And buzzwords.

-Lewis Perdue

More information on ATM

ATM For Dummies, Gadecki and Heckart, IDG Books, 1997: If "ATM" means
"automated teller machine" to you, this is the place to start. A bit out of date, but a
very readable, practical resource for managers and decision-makers.

IP Applications with ATM, Amoss and Minoli, McGraw Hill, 1998, plunges into
ATM internals. It lacks a management overview, but this is the most current and
complete technical treatise on ATM for networking professionals.

Demystifying ATM/ADSL, Busby, Wordware Publishing (due out this fall), offers
good coverage of ADSL and a thorough introduction to basic telecommunications
engineering, but it fails to explain ATM in depth.

ATM Forum (http://atmforum.com) is an organization dedicated to establishing
standards, educating, and promoting ATM, mainly to networking engineers.

Cisco ATM Solutions (http://www.cisco.com/warp/public/730) includes white
papers and other useful resources.

ATM vs IP

There are three big communications concerns in every enterprise: bandwidth,
access, and cost. Originally developed by Bell Labs and France Telecom, ATM
(asynchronous transfer mode) offers a solution for each of these concerns.

Previously, service providers had to use different networks for various information
types, such as voice, data, and video. ATM is now emerging as a more efficient
way for enterprises and service providers (national and regional telephone
companies as well as large Internet service providers) to efficiently send various
types of information over a single, high-capacity wide area network (WAN).

ATM software runs on "switches." These are special-purpose computers similar
to telephone switches (located in telephone company central offices). But ATM
switches are able to handle various types of information (not just voice) over
virtual connections to desired destinations-computers in other parts of the
world, in another building, or the road, etc.

ATM achieves its high efficiency by using a fixed-length 53-byte "cell" instead of
packets or frames of varying length, as in other networking solutions. The cell's
predictable length and destination eliminates wasted time required for hardware
and software to constantly check for packet or frame length and destination. ATM
is also asynchronous (thus the name), which means that various data streams
(data files, voice, etc.) share the transmission resource (fiber optic circuits, etc.) as
needed.

This contrasts with traditional time-division multiplexing (TDM), or "synchronous
transfer mode" (STM), which is used in most data-communication systems. STM
allocates a predefined slice of time to each information stream-regardless of
whether or not there's actual data to be sent at that moment. Not very efficient.

Another big plus with ATM is that it allows for establishing a "traffic contract"
that specifies a "quality of service" (QoS) level for each type of information. For
example, voice and video require a high-availability dedicated virtual channel to
avoid annoying dropouts and delays. But for a file transfer, an as-available QoS
channel is fine.

ATM was originally hyped by vendors as an end-to-end solution right down to
the desktop, but most experts now believe that ATM's overhead and complexity
limit it to WANs and large campus (multiple-building) networks transmitting a
variety of types of information.

The Internet works in a manner diametrically opposite to ATM. ATM virtual
circuits are "connection-oriented" (every cell in a session is transmitted over a
predefined, fixed route). TCP/IP, the Internet protocol, on the other hand, is
"connectionless"-routers forward data packets over various unpredictable paths
(depending on circuit loading) to the destination, where they are temporarily
stored and reassembled into the original information.

This process is very effective for routing around problem circuits, but it's often
painfully slow and inefficient, with unpredictable quality of service, as anyone
who has tried to talk over the Internet or listened to a RealAudio program quickly
discovers.

What about sending IP (Internet protocol) information over ATM? This has been
possible for some time now. But new techniques, such as Cisco's tag switching,
use instructions in the cell header that allow IP information to be efficiently sent
via ATM channels.

The combination of IP and ATM gives users the best of both worlds: compatibility
with the Internet while offering ATM's high-efficiency transmission and specified
quality of service for hot new services like voice over IP, video over IP, and virtual
private networks.

back to home page

Home | Article Archive | Job Search | Resources | Company | Subscriptions

c 1998, TechWeek and Metro States Media, Inc.



To: djane who wrote (49695)7/13/1998 2:23:00 AM
From: djane  Respond to of 61433
 
6/98 Netwatcher Management Briefing [Discussion of ASND suitors and CSI vs. MPLS]

datacomm-us.com

Excerpt: ""But the only "niche play" that has any chance of developing into a really big market is the MPLS-dependent IP
VPN market opportunity, with over $300 billion in total worldwide sales potential over the next 8 years. Only
Ascend, of the WAN-oriented second tier, has any recognized and credible MPLS position, and even Ascend
hasn't been able to really make that position appealing to the media."

June 1998 Volume 16.6

Netwatcher (ISSN 0890-5800) is a monthly publication of CIMI Corporation. Subscription information is
available here . Copyright c 1998, CIMI Corporation. All rights reserved. No publication or reproduction of
this document is permitted without the express written consent of CIMI Corporation.

Management Briefing

The problem with logical analysis is that the world isn't necessarily logical. We mentioned Bay's possible
acquisition by either Lucent or Nortel in our last issue. We thought (though that issue didn't say so) that
Lucent would be the better deal. Naturally, Nortel did the deed.

The acquisition, and particularly its timing, portend great events in the data networking space. There will
probably be other acquisitions, some logical and some less so, and possibly some sinkings of key players. As
buyers of, or vendors in, the data networking market, you (our reader) have a vested interest in the future, and
so we're going to try to lay it out for you.

Let's start with the merger itself. Bay is a strong enterprise player, primarily in the LAN space. It has recently
been working to create a unified direction for all its data products, which would (if successful) pull through
higher-margin WAN products into the enterprise space, and also promote its products to carriers.

Nortel is primarily a carrier WAN player, with some enterprise successes to throw in. They have an enterprise
data group, recently formed, to which Bay will be added and which Bay CEO House will lead. There has not
been any strong indication that the Nortel carrier and data people are on the same wavelength.

Our big concern about the merger is that Bay's strengths are in a part of the data market where Nortel has no
particular record of success. The LAN market is becoming a channel marketing play, and Lucent was in fact
one of Bay's channels. Can Nortel replace Lucent's contribution to Bay's sales? Can Nortel even run an
enterprise organization? If House departs, the whole thing could fall apart.

We believe that Bay's willingness to sell out in the summer of 1998, before Lucent's restrictions on asset
pooling would have likely made it a suitor, suggest that the firm did not believe it could sustain a strong profit
record in the next couple of quarters. Bay management clearly also believed that the company could not remain
strong in the future.

The Second World's Viability

The most compelling thing the Bay acquisition suggests is that the entire second tier of the vendor space in
the data marketplace isn't viable in an independent sense. Cisco, Nortel, and Lucent are the first tier. The
second tier was led by Bay, and also includes 3Com, Ascend, Newbridge, and Cabletron. These firms are too
big to be niche players, and the Bay acquisition suggests that even the best of those players wasn't good
enough. At the low end of that tier, and thus possibly survivable as a niche player, are Xylan, GDC, and Fore.

For all the remaining second-tier players, the choices are:

Shrink down to a niche player, small enough to be viable in market areas the big guys won't pursue too
aggressively. Nobody seems to get little willingly, so we're of the view that this strategy happens by
accident to some who try for other options (for others who try, the result is death).
Pull off a near-miraculous repositioning into some new market area, one with enough revenue potential
to permit continued growth. Frankly, we don't know of any.
Get bought out. The Nortel acquisition will probably stimulate Lucent, Ericsson, Alcatel, Fujitsu,
Samsung, and others to consider buying a second-tier firm.
Merge with one or more of the second-tier remainder to try to put something massive together.
Die off.

In our view, the greatest pressure will fall on the firms who have no strong WAN position, because WAN
products are commanding better profit margins. Thus, Cabletron and 3Com are two firms to watch closely.
3Com has good distribution channels, but would have to endure at least three to five quarters of slow progress
before lower LAN prices kick in true volume growth. Cabletron has no clear future options we can see.


Some kind of partnership or merger among these players (our fourth option of this section) would seem a
logical step. 3Com and Newbridge had a marketing alliance for the Newbridge Carrier Scale Internetworking
(CSI) activity, but that never seemed to get started, and CSI now seems positioned suicidally against MPLS.
Making this relationship more than paper, or creating other merger combinations from among the second tier,
will probably get considered by the players only when it's too late.

The players with more options are Ascend (the best candidate of the lot), Newbridge, Xylan, and Fore.
Because all these vendors are potentially strong WAN plays (even Xylan, whose switches are forming the
basis for some carrier transparent LAN services), all of them could sustain themselves long enough to either
cut a good deal with a partner, or even build a better market niche that would sustain future growth.

But the only "niche play" that has any chance of developing into a really big market is the MPLS-dependent IP
VPN market opportunity, with over $300 billion in total worldwide sales potential over the next 8 years. Only
Ascend, of the WAN-oriented second tier, has any recognized and credible MPLS position, and even Ascend
hasn't been able to really make that position appealing to the media.


The next year will tell the tale. It's likely that we'll see some major changes in this group of vendors (and their
ownership) by then.

Who Might Buy Them?

The big question now is who would buy a second-tier player, and for what reason. There are a number of
scenarios that can be played out, but Lucent and the offshore telephone competitors figure in them all.

One obvious thing that could happen is for Lucent to counter the Nortel move by buying an enterprise player
out of the second tier. Cabletron, whose products are distributed by Nortel, is mentioned as a
possibility-there'd be a kind of irony to each of the big US telecom players buying each other's data partners.
Ironic, but dumb in our view. If Lucent wanted a LAN player, it would seem they'd have encouraged Bay to
hold out till the fall, when they could bid. Then again, we're trying to be logical here.

A better buy option for Lucent would be Ascend. Lucent could then suddenly be an incumbent in nearly
every RBOC frame/cell network, a player in the ATM/IP market, and a real threat to Cisco's growth. Can Lucent
cast off its "Not Invented Here" shackles and make this move? Frankly, we don't know.

There are already other people looking hard at Ascend, including (so it is rumored) Ericsson and Alcatel. The
former is in particular need given the fact that its alliance with Bay and GDC on MPLS is likely to founder on
the acquisition of Bay by Nortel.


Siemens is also said to be gunning for a partner, and there are rumors it would like to both buy Newbridge and
buy Cabletron or 3Com. This would make more sense than some of the other acquisitions, but Siemens has
never been strong in the US data market, and there is serious doubt whether the Teutonic mindset would adapt
to the somewhat disorderly US marketplace.

In our view, an acquisition of second-tier players by either Ericsson or Alcatel could create a viable data
player. It's possible that the complex Siemens multi-question might do the same. Lucent/Ascend would be a
killer deal. The rest of the combinations would be unlikely to create any real market change.

The real risk here is for the major players. Cisco has yet to make a real transition to carrier-dominated data
services, and so is vulnerable to successful exploitation of the carrier base (particularly the RBOCs) Nortel and
Lucent. Real success by either one would make Cisco a perpetual also-ran.


Lucent has to see the Nortel move as pivotal. If they counter the move by trying to enter the LAN/enterprise
market in greater strength, they'll be setting up a kind of phony war between themselves in an inconsequential
space-the WAN market is going to the carriers in the long run. Failure in this phony war would be treated as
failure, period, and would probably discredit the failed player overall. Thus, by fighting a battle with Nortel
here, Lucent could lose a lot and probably not gain much even by winning.

The big risk for Nortel has already been taken. It's ominous that they announced a proprietary IP-over-ATM
strategy recently, having just acquired Bay (whose MPLS announcement was the first from a big player). Not
only does that take some heat off arch-competitor Newbridge, it seems to show that Nortel is determined to
have its own view prevail in the IP market, which would be a disaster.

Stay tuned; more interesting things are coming.



To: djane who wrote (49695)7/13/1998 2:29:00 AM
From: djane  Respond to of 61433
 
6/98 Netwatcher "In the Know" on MPLS and ATM [ASND references]

datacomm-us.com

Many technology advancements are driven by vendors who want to change the status quo. In the IP space,
there is no more eager group than the ATM vendors, whose dreams of gigabucks arising from wholesale
conversion of networking to ATM have been dashed in the late 1990s. In this last of our MPLS features, we're
going to examine how MPLS relates to virtual circuit technology in general, and to ATM in particular.

Labels and VCs: Two Options

One of the properties of label-linked MPLS routes is that they can be readily mapped to virtual circuits. In fact,
that capability may prove to be one of the most important aspects of MPLS design.

There are two models one could presume for MPLS in a virtual circuit environment. One model says that the
virtual circuit network appears as a kind of "MPLS black box" that exhibits MPLS properties at the edge, but
not necessarily internally. The other is the more formalized MPLS model, in which virtual circuit devices exhibit
uniform MPLS properties throughout the network.

The black box model of MPLS is the most generalized for vendors and users, but provides less assurance of
multi-vendor interoperability. In this model, a network of virtual circuit devices is created using whatever
topology and routing architecture the vendor finds convenient. At the edge, the network presents an MPLS
interface and responds to MPLS LDP messages and labeled packets as though the network were a distributed
MPLS node. The network may (and probably will) also present router functionality at the edge, accepting and
generating topology updates using a protocol like RIP or OSPF. The "view" of itself it presents to those
protocols is that of a single, multi-connected, device.

The formalized MPLS model of virtual circuit networking with MPLS requires that the virtual circuit nodes be
MPLS-capable, and also be routing-capable to the extent that some model of route determination must be
developed to provide steering of the LDP messages that create the label-linked routes. Since it is unlikely that
the route-threading process will span only the virtual circuit portion of the network, it is likely that the route
determination architecture of the virtual circuit network would have to be the same as that of the rest of the
MPLS network.

Black-box MPLS, because it is based on ATM networking inside the vendor's cloud of devices, tends to retain
a lot of connection-oriented properties. Both Ascend and Nortel, who have VPN-over-ATM strategies that could be (at least in Ascend's case) mapped to MPLS, create a kind of IP layer around a virtual circuit network core. This makes their VPNs behave like frame relay networks with router features added (which happens to be
how buyers want VPNs to behave).


Formalized MPLS networks, because they make each ATM node behave like a router, tend to create VPNs that
look more like router VPNs. We must note that this tendency isn't institutionalized in the design, just
preferenced in the orientation.

Black Box Virtual Circuits

In the black box virtual circuit model of MPLS, the first step is to establish the virtual circuit network as a
virtual router for those protocols that MPLS will explicitly use (for LDP threading of routes, for example, or for
reconnect or route gateway functions). We've talked about MPLS topology management and routing before,
so all we need say here is that something has to route the "MPLS-equivalent virtual circuits" inside the black
box of the network. It can be MPLS-related (as Ascend's IP Navigator), totally ATM-centric (PNNI) or
something in between.


Whatever the strategy for route management and route determination, the process of threading an MPLS route
through a black box implementation would be similar:

1.The LDP message would arrive at the black box edge node as a normal LDP message. If there is a route
stack associated with it, a black box network would appear as a single node/entry in that stack.
2.The edge node would pop its entry off the stack (if necessary) and determine the edge node at which it
supports the thread's next hop, either through stack processing or through address lookup.
3.The edge node would invoke an internal route threading (set up a virtual circuit) to that destination
point, and forward the LDP message over it to that point. The internal identifier of this VC would be
equated to the incoming label in a table at the source edge node, and to the destination label at the exit
node, connecting the internal route thread to the external flow.
4.The exit edge point would emit the LDP message to its correct MPLS neighbor, using the exit label.

The only place where there's variability of function here is the middle. How the edge node knows the
reachability of its neighbors is dependent on the topology approach taken in the black box network. Likewise,
how the virtual circuit is set up and threaded depends on the connection and routing architecture of the black
box network.

Processing a labeled packet is straightforward once a route has been established:

1.The labeled packet arrives at an MPLS source edge node, bearing an incoming label.
2.The source edge node would look the incoming label up in its table to identify the virtual circuit to
which the label-linked route is associated.
3.The labeled packet would be shunted onto the indicated virtual circuit to the exit edge node.
4.At the exit edge node, the incoming label would be looked up on the exit label table. It would then be
replaced by the exit label, and the packet forwarded according to MPLS exit rules.

Note that in this model, there is no structural linkage between a virtual circuit ID and an MPLS route label. The
correlation is maintained in the edge nodes of the black box network. There is also no requirement that any
discipline in particular be used to create the virtual circuit. This contrasts with the next option, the formalized
MPLS integration with virtual circuit networks.

In general, we expect switch vendors to adopt a "black box" MPLS model. This is due in part to the fact that
most will have routing and topology management functions already in place, designed for virtual circuit
routing. Often these will provide better QoS-based routing than could be obtained by using a per-node MPLS
formalism based on IP metrics. Another factor is the likelihood that switch vendors would want to differentiate
themselves based on MPLS support features, something difficult to do if everyone slavishly adopts the same
set of standards. Finally, switches (unlike routers) are not popularly expected to be box-by-box interoperable
with one another; no X.25, frame, or ATM products are today, and no standards exist for interoperation at this
level.

Virtual Circuit Threading With Formal MPLS

MPLS documents indicate that the VC ID of frame relay or ATM can be used as a label. This means that the
MPLS procedures operate in every frame/cell node in parallel with or in place of standard frame/cell routing
procedures. The process of call setup is displaced by the process of label-linked route setup, and the process
of VC switching becomes the process of label switching.

To make this process work, the ATM or frame switch must first "watch" a particular VC for administrative
traffic. This channel would be used to propagate the LDP message sets, to eliminate the need for the switch to
examine the contents of transit label-linked routes.

An LDP threading process would have to work pretty much the same here as for an individual MPLS node.
The "label", however, would be the VPI/VCI or DLCI of the frame or cell, so there would be no need to prepend
an encapsulation header to contain it.

It is highly doubtful that virtual circuit identification based on globally significant VC identifiers would be
useful with MPLS, given the fact that the number of label-linked routes that could be expected in a network
could be massive. The next question would be whether the VCID would have to be node-significant, or could
be assigned on a port basis.

As far as can be determined based on current documents, MPLS expects labels to be unique for a given node,
though this assumption doesn't appear to be rooted in any specific requirement. Thus, it would appear that
there are two ways the VCID could be handled:

1.An MPLS VC device could assign labels globally, meaning that the VCID address space would have to
contain the total number of routes that pass through the node. This might be practical with ATM,
which has a larger address space, but is not likely to work with frame relay, which is limited to less than
a thousand VCIDs.
2.An MPLS VC device could assign a label exactly as it assigns a VCID now, meaning within a port. This
would mean that the source port number would have to be concatenated with the VCID to create a
unique label for lookup on a common label table, or that the label table would have to be maintained by
port.

Logic seems to favor the latter approach, but it isn't completely clear whether abandoning the concept of a
node-unique label is completely safe. Certainly, a label assigned by node/trunk more closely follows virtual
circuit assignment practices today, and would likely be more compatible with current equipment design as a
result.

Some Special Issues for VC-Mapped MPLS

Three issues appear to arise in any implementation of MPLS integrated with virtual circuit devices:

How will the implementation handle VC merge procedures?
How will the implementation handle multicast?
Will the implementation support "default routing", meaning the handling of packets through normal
routing table functions, not MPLS label switch procedures?

VC merge is a challenge for any ATM-based MPLS implementation because the normal model of ATM data
encapsulation (AAL5) doesn't support merging the cell streams of two unlike information sources and
recovering the original packets intact. It lacks a message/cell sequence number, for one thing, and for another,
such a number would be useful only if we could assume that disparate sources could be expected to come up
with message numbers that would be unique.

We should note that there is no necessary connection between VC merge and frame relay or ATM. In theory,
any MPLS node could offer VC merge, but since the only thing that would be conserved in a non-frame/cell
device is the number of labels, it isn't clear whether there is any benefit. The MPLS spec does call for VC merge
in a generic sense, however, and most MPLS devices will probably offer it.

An alternative to a packet black box for VC merge in ATM networks is the use of virtual paths to aggregate
routes. In this approach, a node sources a VP to each destination node. When label-linked routes merge at a
node, the VCs are merged onto the VP that is associated with the destination. This process can create
problems if the number of destination nodes are high, however.

Packet-merge black boxes may be necessary in any case. As it happens, the issue of multicasting also creates a
potential packet-handling requirement. If MPLS is to support multicasting, it must replicate packets at each
fork in the multicast tree, putting a copy on each outbound path. This could be done through normal VC
point-to-multipoint procedures, but special management of the trees would be required.

The last issue, the handling of packets using standard Level 3 procedures, may also argue for packet-aware
components in virtual circuit devices. That label route threading may be dependent on IP routing tables is a
truth previously noted. It is also true that IP routing will be required to link an MPLS fabric of routes to a
connectionless DMARK supporting a non-MPLS end user. Finally, it is likely that best-efforts IP services
would be provided using standard IP routing even in a network with MPLS support available throughout.

As we've noted before, packet awareness in the last sense covered here could be provided either by making
each node MPLS-packet-IP aware, or by creating a black box network that appeared as a virtual MPLS node.
The other strategies, however, would require some explicit packet awareness in each ATM or frame relay node
in order to be supported effectively. In the balance, we believe it is safe to assume that some form of IP
awareness will be added to all frame/cell networks, and that a portion of this will probably be distributed to
each node.

Conclusion

Nothing reflects the schism in MPLS viewpoint as much as the relationship between MPLS and ATM. Many
will criticize vendors like Ascend who elect the black box strategy-"non-standard" is a label the press loves
to apply to things-but there is good reason for ATM players to take this route.
The IETF appears determined
to promote the traffic management view of MPLS, and that view would compromise the service value-add that
MPLS could bring. Since that service value-add is the key value proposition for adding ATM to IP networks,
ATM vendors can't afford to let router-heads take it away.

The battle for the hearts and minds of the marketplace will start here, with the ATM/MPLS boundary. New
players will find this the most attractive place to launch products, and older players will find it the border of
their kingdom and thus the frontier to be defended.

Nobody's doing a great job of offense or defense yet, but we expect to see some changes over the summer,
and certainly by the fall trade show cycle.



To: djane who wrote (49695)7/13/1998 2:36:00 AM
From: djane  Respond to of 61433
 
Williams set to deliver flexible services [Nice ASND references]

New service network features let users control bandwidth, billing and management

nwfusion.com

By Tim Greene
Network World, 6/22/98

Tulsa, Okla. - Williams Communications Group
is promising to give network service users
something they have precious little of today:
flexibility.

The company is building a network that will let
Williams offer users features such as the ability to
check on the status of circuits and rapidly change
the amount of bandwidth they are getting. In
addition, Williams customers will be able to get
up-to-the-minute details on what they are being
charged. "That is very helpful. It can help you
budget. Rather than waiting for a bill to come 30
days later or hear about high usage 10 days after
the fact," said Greg Britz, systems integration
engineer at Burlington Northern Santa Fe Corp.

Changing bandwidth at will could let customers
shift into penny-pinching mode, ratcheting down
the size of circuits when demand drops, Britz
said. "There could be some significant
advantages there. If you want to control the
budget, that's very attractive."

All of this will be possible because Williams is
building its network from scratch, taking
advantage of the latest networking gear that
supports new services and also reduces the
carrier's costs.

Williams was the former owner of Wiltel, a
fiber-based network-service company that
WorldCom, Inc. bought in 1995. As Williams
planned to get back into the business, it
considered building a network just like Wiltel's,
with a traditional infrastructure that included
overlay frame relay and ATM networks.

Ultimately, the firm ruled that network design
out. "Most of the traffic on the Wiltel network
was voice, and data was becoming the
predominant traffic," said Wayne Price, manager
of Network Development for Williams. The
company decided to build its network with the
ability to handle voice as well as data.

The growth in data was attributable to the
growth in IP traffic, and some in the company
said they should build an IP-only network that
carried IP packets over a Synchronous Optical
Network (SONET) OC-48 infrastructure, Price
said. But they ruled the IP-only network out as
well.

"There is still a big demand for DS-1 and DS-3
private lines as well as frame relay - and video is
coming. IP couldn't support those services. We
decided to build our network based on ATM
because it was the best technology to provide a
multiservice network," Price said.

Because Williams was starting with a clean slate,
it tried to avoid being hamstrung by using gear
that could rapidly become obsolete. For
example, Williams decided it could do without
digital access and cross-connect systems
(DACS) because those functions are picked up
by ATM switches. DACSes connect customer
lines to the appropriate trunks within carrier
networks.

Similarly, SONET muxes are being incorporated
in those switches. That means fewer boxes to
manage and maintain (see graphic). Using ATM
switches instead also represented an 80%
reduction in capital costs for building the
network, Price said.

Eliminating DACSes has other benefits, Price
said. Traditionally, carrier network engineers
would use DACSes to reroute traffic around
failures. "A DACS is not a smart device. It is not
a switch. It is more of a provisioning tool. It
doesn't handle commands very quickly," Price
said.

Even with a service restoration plan in place for
failures, it would take 10 to 30 minutes to
reconfigure a big DACS, while an ATM switch
would detect a failure and reroute automatically
within milliseconds, Price said.

Beyond network simplification, the CX 550
ATM switches Williams is buying from Ascend
Communications, Inc. support new service
management and billing features customers want.

For example, customers can be given the ability
to change the minimum guaranteed bandwidth on
a frame relay circuit without Williams intervening.
They can also get new billing options beyond the
flat fees customers now pay for many data
circuits.


Contact Senior
Editor Tim Greene

Feedback | Network World, Inc. | Sponsor Index
Marketplace Index | How to Advertise | Copyright

Home | NetFlash | This Week | Industry/Stocks
Buyer's Guides/Tests | Net Resources | Opinions | Careers
Seminars & Events | Product Demos/Info
Audio Primers | IntraNet



To: djane who wrote (49695)7/13/1998 2:47:00 AM
From: djane  Respond to of 61433
 
Carriers, Service Providers Gear Up For Demand Blitz [ASND references]

techweb.com

July 13, 1998, Issue: 723
Section: Bandwidth Boom: The Present 1998 To 2000

Salvatore Salamone

Demand for access is skyrocketing. And that will have an immediate impact
on central offices during the next two years.

To meet the insatiable demand for access, carriers and network service
providers face a dual challenge. Companies want both faster and more
dedicated links. Probe Research Inc., which tracks the telecommunications
industry, predicts that the number of dedicated access lines needed for
corporate Internet access will nearly quadruple to 480,000 in 2002,
compared to the approximately 140,000 in use last year.

This combination of more Internet users and corporations outsourcing remote
access to service providers is fueling a demand for modem ports within central
offices.

For instance, a study on virtual private networking (VPN) conducted last year
by consultancy Infonetics Research Inc. found that the worldwide market for
equipment, integration services and service provider VPN services will grow
by more than 100 percent per year, topping $10 billion by 2001. The bulk of
the growth will be in VPN services which require dial-access ports in central
offices in order to work.


To meet this range of demands, central office equipment vendors are
approaching the market in many ways. For instance, traditional telecom switch
vendors Lucent Technologies Inc. and Northern Telecom each acquired a
remote access concentrator vendor in the past year. Lucent snapped up
Livingston Enterprises Inc.'s PortMaster line, and Nortel acquired Aptis
Communications Inc. for its CVX family of remote access concentrators and
its VPN expertise.

Other switch vendors have partnered with internetworking companies to get
the necessary technology into the central office. For example, Siemens AG is
working with 3Com. And many vendors are working with Ascend
Communications Inc. and Cisco.


"For a while the standard line was that data mucked up central offices, causing
switch congestion," says Raymond Lopez, a consultant at Rosewall and
Associates, a consulting firm that designs and installs remote access systems.
"Now the strategy is 180 degrees different. It's 'Let's get this equipment as
tightly integrated with the [central office] equipment as we can.' "

That point rings true. In May, when Lucent announced its own
high-performance IP switch, the PacketStar IP Switch, the company was
making a statement that it could compete directly with the major
internetworking vendors when it comes to dealing with the growing volume of
data being handled in central offices. "We own this market," Bill O'Shea,
president of Lucent Technologies Data Networking Systems said at the press
briefing.

Not to be outdone by the central office supplier crowd, access equipment
vendors such as Adtran Inc., Advanced Computer Communications Inc. and
Assured Access Technology Inc.-which traditionally have serviced the carrier
market-introduced equipment that will offer higher dedicated line-port
densities than ever before. The new equipment also supports a broader range
of services-including DSL, frame relay, ISDN, T1 and ATM-from a single
chassis.

At the same time, the traditional data networking companies aren't sitting idly
by. Anticipating the demand for remote access ports for both dedicated lines
and dial access in the next two years, Ascend, Bay Networks, Cisco and
3Com jumped on the bandwagon, announcing higher port-density products.

The upshot for carriers is more ports in less central office space. And these
equipment companies are not just offering more ports, they're also offering
more types of service from the same device. For instance, most of the
equipment companies support DSL, frame relay, ISDN and ATM from a
single chassis-based system.

The move to support more services in a port also applies to dial-access ports.
Many vendors are using software-based modems based on digital signal
processors, which can automatically detect the nature of the call and load the
appropriate software. Such software modem ports can often support analog
phone calls, an ISDN BRI call, or a call from any one of the three types of
560-Kbps modems (x2, 56Kflex or V.90).

Copyright r 1998 CMP Media Inc.