""Howard C. Berkowitz""  wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Priscilla,
>
> To decide on whether ISIS and MPLS are relevant to enterprises, I
> believe you have to look more deeply into the enterprise's structure
> and internal competencies.  There are a substantial number of Fortune
> 100 companies, universities, etc., that consciously organize an
> "internal ISP" to deal with their various departments.  Enterprises
> with absolutely mission-critical Internet presence (e.g., Amazon)
> tend to do this as well.
>
> If an enterprise does set up an internal service provider, than
> service provider technologies are very relevant to that internal
> function, while the various department may run their own IGP domains.
> You also may have a core network function plus complex Internet
> connectivity that is owned by the enterprise, but managed by a
> commercial service provider.


CL: Me too. :->

CL: I named names in my private answer, but I've talked MPLS to two
different very large companies in the medical field in the last year. One
was an insurance company that was probably just yanking my chain. But the
other was highly articulate in expressing their requirements and their
rationale. This particualr customer even used the words "service provider"
in describing their corpaorate network, which included a number of data
centers, warehouses, office complexes, and a very large number of business
partner extranets.

CL: my employer has also installed an MPLS network for a major government
entity here in California.

CL: my fellow engineers tell me they are hearing a lot more about MPLS in
their discussions with customers.

CL: I don't hear much about IS-IS. Large customers tend to have OSPF.
Sometimes EIGRP. With smaller customers we tend to knee-jerk install EIGRP.






>
>
>
> Howard




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=58625&t=58493
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to