The Future of Home Networking: An Incremental Approach NANOG 58 // New Orleans // 4 June 2013 Chris Grundemann
The Future of Home Networking: An Incremental Approach
NANOG 58 // New Orleans // 4 June 2013 Chris Grundemann
Home LAN 2
Home LAN 1
Yesterday’s Home Network
Internet Service Provider
Wi-‐Fi Range Extension
NAT
NAT
6/4/13 Chris Grundemann 2
Emerging use cases for the home network • MulSple SSIDs – User and provider managed
• Femto cell – Cellular services
• Smart grid • Security, Monitoring, & AutomaSon • MulS-‐homing • IP content sharing – Inside and outside the home
• TelecommuSng – Corporate IT requirements
• Ever increasing IP devices • Heterogeneous link layer technologies 6/4/13 Chris Grundemann 3
Tomorrow’s Home Network
Home LAN 2
Home LAN 1
Internet Service Provider
Wi-‐Fi Range Extension
MulSple SSIDs: Private, Guest, Community,
ISP Branded, Etc. Guest LAN
Home LAN 4 ZigBee Network
Home LAN 3
Home AutomaSon Gateway
IP Sensor Gateway
Home Entertainment
Gateway Key assump=on: Home users will not be configuring advanced
networks
6/4/13 Chris Grundemann 4
The Importance of Home Networks • Failure causes service calls • Plaaorm for all IP services
6/4/13 Chris Grundemann 5
PHASE I RFC6204(bis)
6/4/13 Chris Grundemann 6
Add IPv6 to Home Networks
• IPv6 is being deployed today (thankfully) • Home networks are growing today
• A soluSon is needed today (or sooner) – Based on RFC 6204/bis
6/4/13 Chris Grundemann 7
Phase I Example (and Issues)
6/4/13 Chris Grundemann 8
PHASE II HIPnet
6/4/13 Chris Grundemann 9
6/4/13 Chris Grundemann 10
• A self-‐configuring home router architecture
– Flexible – Scalable – Autonomous
– Proven Protocols
HIPnet is a SoluSon to Complex Home Networks
Common Principles Guide HIPnet
• Home networks will become more complex, home users will not
• Invoking a god box leads to religious wars • New protocols bring new problems
• Use IPv6, support IPv4 • We have enough addresses
6/4/13 Chris Grundemann 11
HIPnet Meets Current Needs with ExisSng FuncSonality
6/4/13 Chris Grundemann 12
• Self-‐Organizing: DirecSonless Routers • Addressing: Recursive Prefix DelegaSon • RouSng: Hierarchical RouSng • Bonus: MulSple Address Family Support
• Prototype demonstrated at IETF 86!
DirecSonless Home Routers
6/4/13 Chris Grundemann 13
Up DetecSon
R1 R2 R3
RS
RA DHCP Req.
Offer
ULA GUA
ULA GUA
GUA GUA
“UP”
Default route
6/4/13 Chris Grundemann 14
DeterminisSc Up Interface SelecSon Criteria
• Valid GUA preferred • Internal prefix preferred over external • Largest prefix • Link type/bandwidth • First response • Lowest numerical prefix
6/4/13 Chris Grundemann 15
More Complicated Up DetecSon Example
R1
R2 R3
R4
Internet
PD req.
/60
/64
/64
UP
6/4/13 Chris Grundemann 16
DirecSonless Routers Example: Rearranging the Network
R1
R2 R3
R4
Internet
RS
RS RA
No RA
UP
UP
Also, see following slides for case where R4 ends up on same LAN as R1, R2, R3
6/4/13 Chris Grundemann 17
Internet Service Provider
HIPnet Creates a Logical Hierarchy from a Physically Arbitrary Network
R1
R2
R3
R4
R5
Physical ConnecSon
IP ConnecSon 18 6/4/13 Chris Grundemann
Recursive Prefix DelegaSon
Home LAN 2
Home LAN 1
Internet Service Provider
Guest LAN
Home LAN 4 ZigBee Network
Home LAN 3
/56
/60 /60
/64 /64
6/4/13 Chris Grundemann 19
Width vs. Depth
6/4/13 Chris Grundemann 20
R1
Rn Rn Rn Rn Rn
Width = 3 Width = 5
Width vs. Depth
6/4/13 Chris Grundemann 21
R1
Depth = 4 Rn
Rn
Rn
Width OpSmizaSon
• Fit PD to width and depth of network – Provide greatest flexibility
• Algorithmically selected bit-‐boundary – Physical port count as width proxy
6/4/13 Chris Grundemann 22
Hiearchical RouSng Table
Up
Down
::/0 Default Router
IA_PD Downstream IR’s “Up Interface” IP
6/4/13 Chris Grundemann 23
MulSple Address Family Support: Link ID
GUA IPv6 Address 48b -‐ ISP 64b – Interface ID 16b – Link ID
48b -‐ ULA
IPv4 “10.”
/64
/24
6/4/13 Chris Grundemann 24
Basic MulShoming Support
• Special purpose IP connecSon – IP Video, etc.
• Backup connecSon – acSve/standby
• “True” mulShoming – acSve/acSve (limited)
(More info in backup slides) 6/4/13 Chris Grundemann 25
PHASE III More Efficient USlizaSon
6/4/13 Chris Grundemann 26
Add a RouSng Protocol
6/4/13 Chris Grundemann 27
Internet Service Provider
R1
Physical ConnecSon
IP ConnecSon
R3
R5
R4 R2
PHASE IV Going Even Further
6/4/13 Chris Grundemann 28
InteresSng IGP Enhancements
• Use OSPFv3 to assign prefix’ – draq-‐arkko-‐homenet-‐prefix-‐assignment
• Use IGP adjacencies to find borders – draq-‐kline-‐homenet-‐default-‐perimeter
6/4/13 Chris Grundemann 29
Beser MulShoming
• Use Source Address Dependent RouSng (SADR) – draq-‐troan-‐homenet-‐sadr
• Use a middlebox and a mulShoming service provider (MSP) – draq-‐haddad-‐homenet-‐mulShomed
• Use a new rouSng protocol: Two Dimensional-‐IP (TwoD-‐IP) – draq-‐xu-‐homenet-‐twod-‐ip-‐rouSng
6/4/13 Chris Grundemann 30
CONCLUSION So what?
6/4/13 Chris Grundemann 31
• Do nothing (Phase I) – Service calls – Broken service discovery – Single router IPv6 – Unknown environment
• HIPnet (Phase II) – Self-‐configuring – Whole home networking – Common plaaorm for IP services
6/4/13 Chris Grundemann 32
Help Ensure the Future!
• Support the HIPnet Internet-‐Draq – draq-‐grundemann-‐homenet-‐hipnet
• Support the HIPnet open source project – [email protected]
• Build a commercial HIPnet soluSon – eRouter is HIPnet compliant
• HIPnet – Ask for it by name – Industry alignment – Vendor engagement
6/4/13 Chris Grundemann 33