Transcript metronet-6

North American and California IPv6
Task Force MetroNet6 Project
Presented by: Peter Kirstein for Jim Bound
([email protected])
CTO, IPv6 Forum www.ipv6forum.com
Chair North American IPv6 Task Force
www.nav6tf.org
HP Senior Fellow
Overview
• MetroNet6 – A Wireless MESH Network to support
First Responders (the bottom line).
• Project Deployment Analysis and View
• Summary
• Acknowledgments
September 2006
2
MetroNet6 Evolution
• Essential first idea and vision developed by principals from
NAv6TF www.nav6tf.org Jim Bound and Larry Levine (also
Director CEDREC FT Monmouth U.S. Army) in 2001 after 911 as
means to use IPv6 to enhance First Responder
communications for RFI New York City Mass Transit Network,
supported by the IPv6 Forum www.ipv6forum.com
• Idea was presented to U.S. Congress by NAv6TF in 2003, but
was unable to achieve wide support.
• California IPv6 Task Force (CAv6TF) www.cav6tf.org took
ownership of the project and enhanced technical work in 2005
led by Geof Lambert and George Usi and a team of volunteer
Subject Matter Experts (SMEs) within the NAv6TF and CAv6TF.
• NAv6TF Moonv6 www.moonv6.org project U.S. wide network
was added to the design center to emulate First Responder
command control network 2006.
• NAv6TF and CAv6TF began working with U.S. and California
Government, and local Sacramento First Responder contacts
and officially started the current MetroNet6 in 2005.
• Please see current CAv6TF MetroNet6 Web Page:
– http://www.cav6tf.org/html/metronet6.html
September 2006
3
What is MetroNet6?
• MetroNet6 is a proposal to develop a prototype end-toend secure Wireless MESH network for first responders
and across their metropolitan area of operations
emergency support infrastructure, using IEEE 802.11.x,
IEEE 802.16x, Satellite Communications and the Internet
Protocol, Suite support IPv6 and Mobile IPv6 to provide
security, discovery, connectivity, legacy support, and
end-to-end interoperability, supporting an Emergency
Management Network (EMN)
– Communications within specific first responder
networks.
– Communications between multiple first responder
independent networks.
– Communications within area of operations
Metropolitan EMN Internet Network command control.
– Communications between Metropolitan EMN Internet
Network city-to-city-command control.
– Communications between Metropolitan EMN Internet
Network state-to-state-command control.
September 2006
4
Who are the stakeholders?
• Federal Government Home Land Security supporting
EMN Internet Network.
• State Government supporting EMN Internet Network.
• Regional Government supporting EMN Internet
Network.
• First Responders
– Police
– Fire Department
– EMS Rescue
– Hospitals and Doctors
– State National Guard
– Other crisis management support infrastructure (ie:
Dept of Forestry)
– Other law enforcement agencies
September 2006
5
What is a Wireless 802.11x Infrastructure
Network?
Access Point
Network
Discussion == IEEE 802.11
Network advantages, current
state of the art, security, and
future directions.
September 2006
6
What is a Wireless Cellular or
IEEE 802.16 WIMAX network?
Comm. T ower
Comm. T ower
Comm. T ower
Discussion == 3G-4G Cellular and
IEEE 802.16 Network advantages,
similarities, current state of the art,
security, and future directions.
September 2006
7
What is a Wireless Satcom net?
Supports multiple forms
of communications to
end nodes via wireless
or broadband.
Satellite
Satellite dish
Satellite
Satellite dish
Comm. T ower
September 2006
8
What is a Wireless Ad Hoc network?
• Self organizing, healing, adaptive.
• Base Station is within the node for
waveform communications
• Neighbors can only hear next hop
neighbors.
• Topology maps must be maintained by
each node.
• Node must be a router and a host.
• Various routing protocols defined known
as MANET.
Wireless Link Media
• New proposals to use Node Discovery from
IPv6 for topology sharing between nodes.
• To access an external network one node
must be a gateway.
September 2006
9
What is a MESH Wireless Ad Hoc network?
• Self organizing, healing, and adaptive sub Ad Hoc
Networks connected to a Base Station.
• Base Station supports multiple network link medias
(e.g. WIMAX, Cellular, Satcom Ground Station, access
to Broadband).
• Base Station can be extended via line of sight or
Satcom.
• Neighbors access all neighbors through the Base
Station and other Ad Hoc Networks through routing
topology.
• Base Stations can be replicated for High Availability.
• Access to an external network can be learned from
routing advertisements.
Comm. T ower
• Benefits of IEEE Infrastructure and Ad Hoc Mode.
• All networks may be seamless mobile where IP
location is changing relative to the entire MESH
network.
September 2006
10
Wireless MESH Ad Hoc Network
Technical Summary
• A Wireless MESH ad hoc Network is a set of
connected ad hoc and fixed network locations that
are connected in a MESH topology where the
backbone for communications is done
predominantly over a Wireless link media waveform,
and can be managed to be dynamic so it can
contract and expand as required. The key difference
is that all of the ad hoc and fixed networks are
viewed and connected as one MESH IP network
autonomous system, thus can support a set of
network infrastructure services across the MESH
topology.
September 2006
11
Wireless MESH Network Architecture
Layers – As Hastily Formed Network (HFN)
Fireman
911 Stations
HFN IP Subnets
HFN IP Network Comm
Backbone Network
Satcom, WIMAX,
Cellular (HFN Command
Control Center)
HFN Network Utility
Information Services
Civilian
Agencies
Federal
Agencies
Police
National
Guard
• HFN IP Subnets
EMS
Vehicles
Doctors and
Hospitals
Shelters
• HFN IP Network
Communications
Backbone (core), and
interface to any existing
network infrastructure.
• HFN IP and Waveform
Gateways to the HFN IP
Subnets and Backbone
• HFN Users and Radio
Nets
September 2006
12
Wireless MESH Ad Hoc Network
Base Industry Technology Enablers
• Next Generation Networks
– All IP Convergence
– Fixed to Seamless Mobile Networking
Convergence
– IPv6 Transition, Mobile IPv6, IPsec End-to-End
– Wireless WAN Backbone Proliferation
– Sensor Networks
• Net Centricity
– Network Services view not a platform view
– Principles: Connectivity, Interoperability, Security,
Discovery, and End-to-End communications.
September 2006
13
Wireless MESH IT Network Services Infrastructure
Satcom
and
WIMAX
Local Mobility
Manager Server,
Router, IPsec, and
AAA, supporting
IPv6
Subscriber, Policy, AAA,
IPsec, DNS, and Security
Services
Regional
Voice, Video, and Gaming
Mobility Access
Services, Mobile
Manager Server,
Correspondent Nodes
Router
IPv6 Access
Router
Comm. TComm.
ower T ower
Comm. T ower
Cell Base
Stations
Internet
Core/Edge
Comm. T ower
802.11 AP’s
Server Content and
Gateway Services
Other
Provider
Services
Mobile Nodes, Sensors, and Ad Hoc Networks
Internet Protocol Control Plane
Layer 2 Control Plane Signals
September 2006
14
General MetroNet6 Network Architecture
Services
Satellite dish
Data
Comm. T ower
Ethernet
Access Network A
Wireless Link Media
Services
First responder
Mobile Ad-hoc
Network A
Comm. Tower
Hub
Provider Network A Infrastructure
September 2006
15
Communications between multiple
first responder independent networks
Services
Satellite dish
Data
Police Unit
Comm. T ower
Wireless Link Media
Services
Ethernet
Access Network A
Comm. Tower
First responder
Mobile Ad-hoc
Network A
Hub
ovider Network A Infrastructure (Police)
Services
Satellite dish
Data
Wireless Link Media
Comm. T ower
Services
Ethernet
Comm. Tower
Fire Dept Unit
Access Network B
First responder
Mobile Ad-hoc
Network B
Hub
ovider Network B Infrastructure (Fire Department)
September 2006
16
Communications within area of operations
Metropolitan EMN Internet Network command
control
Services
Comm. Tower
Hub
Metropolitan City 1 Internet Area of Operations
Services
Services
Metropolitan EMN
Gateway Network
Comm. Tower
Comm. Tower
Hub
Hub
Provider Network A Infrastructure
Network A Access and
Mobile Ad Hoc Networks
Provider Network B Infrastructure
Network B Access and
Mobile Ad Hoc Networks
September 2006
17
Communications between metropolitan EMN
Internet Network city-to-city-command control
Services
Sacramento, CA
NAv6TF Moonv6 www.moonv6.org
Peering Site
Comm. Tower
Hub
Metropolitan City 1 Internet Area of Operations
Metropolitan city-to-city
EMN Gateway Network
Services
Palo Alto, CA
NAv6TF Moonv6 www.moonv6.org
Peering Site
Comm. Tower
Hub
Metropolitan City 2 Internet Area of Operations
September 2006
18
Communications between Metropolitan EMN
Internet Network state-to-state-command control
Services
California
NAv6TF Moonv6
www.moonv6.org
Peering Sites
Services
Comm. Tower
Comm. Tower
Hub
Hub
Metropolitan City 1 Internet Area of Operations
Metropolitan City 2 Internet Area of Operations
Metropolitan state-to-state
EMN Gateway Network
University of New Hampshire +
Internet2
NAv6TF Moonv6 www.moonv6.org
Peering Site
Services
Comm. Tower
Hub
Metropolitan City 3 Internet Area of Operations
September 2006
19
MetroNet6 Proposal Initial Outline Criteria
•
•
•
•
•
•
•
•
•
•
•
•
Previous slides define high-level use cases and network topology design
center.
Internet Protocol Layer would use IPv6 as dominant for End-2-End node
communications and routing protocol (all nodes capable of IPv4 and IPv6)
Security will be critical and IPsec should be used as first order of defense, but
other ambient security methods will be required within MetroNet6.
Link Layer would use IEEE 802.1x protocols
Seamless Network Mobility would use Mobile IPv6 and enhancements as
defined in IETF Network Mobility group (NEMO).
But, first responders must be able to operate without NEMO infrastructure too.
NAv6TF Moonv6 backbone would be used for inter-city and inter-state network
communications.
First responder specific networks would have to define and select a Mobile Ad
Hoc Networking routing protocol, with support from CAv6TF and NAv6TF
networking Subject Matter Experts (SMEs).
Various Internet Networks would need to be defined and designed, with
support from CAv6TF and NAv6TF networking SMEs.
IPv6 Transition mechanisms will be required to interoperate with legacy
operations and applications that have not moved to IPv6, with support from
CAv6TF and NAv6TF networking SMEs.
Wireless and broadband networking infrastructure would have to be defined
and determined to support MetroNet6 various network topologies, with support
from NAv6TF Moonv6 SMEs.
Secure transmissions and authentication of users.
September 2006
20
MetroNet6 Wireless MESH Network Properties
Overview
•
•
•
•
•
•
•
Network is usually wireless.
Network is not permanent.
Network must be self-forming and
self-healing.
Access to services from External
Internet Network may be direct or
through an Access or Gateway
network.
Access Network and Internet
Network may also be mobile.
Greatest connectivity and
interoperability achieved with the
Internet Protocol suite for
networking layers, and to support
seamless routing.
Network must be able to hear broad
wireless router advertisements
beacons (e.g. Geocast, Anycast)
•
•
•
•
•
•
Each node on the network may be a
router.
Each node on the network will
usually be powered by batteries.
The link environment the nodes
operate can be affected by local
interference and terrain.
Each node on the network will often
communicate over a radio network
infrastructure.
The radio network infrastructure
must interoperate with the Internet
Protocol Suite for maximum open
systEMN connectivity and
interoperability.
Using IEEE 802.1x provides open
link media standard and off-theshelf commercial devices, and
evolution towards Next Generation
Networks.
September 2006
21
Project Management – (PMI®)
•
Objective Statement:
Plan, fund, develop, build, and test a convergent and Internet-Protocolinteroperable Metropolitan wire line and wire less pilot Network,
(MetroNet6 SACRAMENTO testbed) for First Responders with standards
for voice, video, graphics, workflow intelligence, cellular, and other
forms of data communications under a 24x7x365 availability criteria and
24-hour Return to Operation control limit with a budget of $800,000 and
10,000 staff hours by September 30, 2007.
•
Deliverables
• Open standards outlining IP (TCP/IP) interoperability for first responders
• IPv6/IPv4 IP-based connectivity cloud with a 24-hour Real-Time-Ops plan
• Wireless MESH network, supporting Mobile Ad Hoc Networks with a realtime-recovery plan.
• First responder IP-based interoperability IP platform for county-tocounty, state-to-state, and state-to-federal standards designed by
Internet pioneers.
• Cellular and convergent IP communications in a mobile/portable form
factor for first responders and disaster victims.
• Rugged and mobile computing device standards with multimedia
functions and possible IPv6 expansion capabilities
September 2006
22
Collaborative Projects California OES
• California Office of Emergency Services Research
– OES currently working on ERMN (Emergency
Response Management Network)
– OASIS project – Statewide Satellite System
– RIMS – Response Information Management
System
– ERMN – Emergency Response Management
Network
• MetroNet6 layer being considered here
September 2006
23
Resource Requirements
• Integration of technologies by enabling technology
vendors.
• Schedule is set for project with RFI for all three layers of
design soon to be released.
• Human Resources will be regional, national, and global.
Sacramento based resources , CISSPs, CISMs, and
Stakeholders.
• MoonV6 will provide backbone include Calfornia IPv6 Task
Force SMEs, backbone engineerstransit of IPv6 traffic
• Project Ramp Estimation 800K (readiness assessments
and expenses) for 2007 Capital & Operational Expenditures
• To complete pilot Sacramento to Palo Alto, (assumes no
outside assistance or adoption) estimated 3 million
• Enabling Technology Providers will provide core
networking equipment – some donation offers already
flowing in from SMEs and manufacturers.
September 2006
24
MetroNet6 Initial Deployment Model
September 2006
25
Summary
• End-2-End interoperability in three layers:
– Core Network
– Mobile Network
– Applications E2E
• MetroNet6 completion date targeted for December
2008
• Project Pilot in Sacramento California managed by
CAv6TF.
September 2006
26
Acknowledgements
• George Usi – NAv6TF and CAv6TF SME and MetroNet6
Project Leader.
• Geof Lambert – NAv6TF Vice Chair, Chair NAv6TF, and
Director MetroNet6
• Yanick Pouffary – IPv6 Forum Fellow, and NAv6TF
Technology Director
• Larry Levine – Original Co-Designer and NAv6TF Steering
Committee Advisor
• The many NAv6TF and CAv6TF volunteer SMEs that
participated in many meetings and architecture
discussions.
• U.S. Federal, State, and Local Government persons that
have taken the time to listen to the MetroNet6 vision.
September 2006
27