|
IPLAN Team
IPLAN Team Chair
|
|
Mark Schnell
Device Abstraction and GW Interface Team Chair
Device Interface Team Chair
Cisco Systems
Cisco:
- We are the world wide leader in networking equipment. As such,
anytime additional applications and uses of the network are developed
Cisco benefits.
Technology Center:
- The Technology Center is a unique group inside Cisco. We are are
not a Business Unit (BU). We do not have a P&L to manage. We are a
corporate resource. We are a engineering team that is paired with
business development team. Our macro goal is to "make the Internet
bigger".
-
We do this by...
- Locating and qualifying new, emerging or changing markets
- Identifying and seeding relevant new technologies into Cisco
- Building ecosystems around Cisco products and technology
- Supporting product development for partners and investment
companies
- Complementing the engineering efforts of Cisco Business
Units"
- We have a 3-5 year time horizon for our large 'focus areas'.
- We are an experienced, multi-discipline group with broad technical
experience. (SW, HW, datacom, telecom, compliers, gaming, video
encoding, data bases, encryption, ...)
-
Examples of our work (both big & little projects) include:
- The 1st VoIP developments in Cisco back around 1997 (partnered
with a BU for path to market)
- DSL & cable modem reference designs
- TCP/IP stack for Sony PS2
- Many wireless projects (.11, cellular, GPS, mesh, RFID,
ZigBee)
- Vehicular (i.e. small, robust) routers
- VoIP call control systems
- Standards (video, mobileIP, RF link metrics, anti-SPAM, ...)
-
-
Personal Biography:
- I have an EE degree (BS & masters)
- I've spent 14 years in telecom at Nortel and 7 years in datacom
at Cisco.
- My training is HW design. Over the years I have developed
numerous boards, chips and systems.
- I consider my role to be one of system design. Look for general
solutions not the specific ones. To see the forest inspire of the
trees. To take a half step back to see the real problems, issues
& solutions. To see the possible components of a solution and
assess their applicability, but to not get lost in all the details
(i.e. to be able to scope the appropriate level detail needed in a
particular situation.)
|
|