Transcript PPT Version

Network Localized Mobility
Management using DHCP
draft-templin-autoconf-netlmm-dhcp-04
[email protected]
IETF67 – NETLMM wg
NETLMM Domain
Backhaul Network
Access Rtrs (ARs)
Mobility Anchor
Point(s) (MAPs)
Access Networks
Mobile Nodes (MNs)
NETLMM Using DHCP
• Three different MN types supported:
– DHCP-only
– SLAAC-only
– DHCP+SLAAC
• ARs configure both DHCP client/relay
• MAP(s) configure DHCP server
AR Client/Relay Configuration
• DHCP client/relay co-resident - use loopback interface
• Relay performs ordinary relaying; manages IP
forwarding table
• Client responsible for:
– reliable message exchanges
– network-initiated handovers
– Proxy-DHCP for SLAAC-only MNs
Client
Access
network
eth0
lo0
Relay
netfilter
Access Router
Backhaul
network
eth1
Model of Operation
• MNs use DHCP and/or SLAAC and observe
NETLMM MN-AR interface spec
• ARs/MAPs use ordinary DHCP message
exchanges
• ARs/MAPs manage ip forwarding tables based
on address/prefix delegations
• Host-initiated handovers driven by MN
• Network-initiated handovers driven by AR
• Proxy-DHCP for SLAAC-only Mobile Nodes
• (Rudimentary) mechanism for setting up ARMAP relationships - can be made more robust
Host-Initiated Message Exchange
MN
New AR
MAP
Old AR
|
|
|
|
| Router Advertisement |
|
|
|
(or L2 event)
|
|
|
|<---------------------|
|
|
|
DHCP Request
|
|
|
|--------------------->| Relayed DHCP Request |
|
|
|--------------------->| create route to
|
|
|
| MN via new AR
|
|
|
|
|
|
|
DHCP Reply
| DHCP Reconfigure |
| Relayed DHCP Reply |<---------------------|------------------->|
|<---------------------|create routes
| DHCP Info-request |
|
|to MN
|<-------------------|
|
|
|
DHCP Reply
|
|
|
|------------------->|
|
|
|
delete routes|
|
|
|
to MN|
|
|
|
|
...
|
|
|
|
|
| data packet
|
|
Tunneled Packet
| for MN
|
Forwarded Packet
|<=====================|
|<---------------------|
|
Network-Initiated Message
Exchange
MN
New AR
MAP
Old AR
|
|
|
|
| NS(DAD) or L2 event |
DHCP Info-request |
|
|--------------------->|--------------------->|update routes to
|
|
|
|MN via new AR
|
|
|
|
|
|
|
DHCP Reply
| DHCP Reconfigure |
|
|<---------------------|------------------->|
|
|create routes
| DHCP Info-request |
|
|to MN
|<-------------------|
|
|
|
DHCP Reply
|
|
|
|------------------->|
|
|
|
delete routes|
|
|
|
to MN|
|
|
|
|
...
|
|
|
|
|
| data packet
|
|
Tunneled Packet
| for MN
|
Forwarded Packet
|<=====================|
|<---------------------|
|
Motivation
• deliver best solution to address customer’s
requirements, but:
– no early visibility into DT effort
– PMIP not yet on radar screen
– need to assure proper link-model operation for
customer’s use-case
• re-use of widely-deployed mechanisms already
deployed by customer
• prefer standard solutions, but customer will have
their solution in any event
Status
•
•
•
•
‘draft-templin-autoconf-netlmm-dhcp-04’
support for both IPv4 and IPv6
uses standard DHCPv4/v6 messaging
DHCPv6 requires RAAN; SRSN options
(in WGLC for Proposed Standard)
• two independent implementations of -02
draft for DHCPv4 (Boeing and MITRE)