1. Network Localized Mobility Management using DHCP
draft-templin-autoconf-netlmm-dhcp-04
IETF67 – NETLMM wg

2. NETLMM Domain Backhaul Network Access Rtrs (ARs) Mobility Anchor
Point(s) (MAPs)
Access Networks
Mobile Nodes (MNs)

3. 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

4. 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
Relay
lo0
Access Router
Backhaul
network
Access
network
netfilter
eth0
eth1

5. 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 AR-MAP relationships - can be made more robust

6. Host-Initiated Message Exchange

7. Network-Initiated Message Exchange

8. 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

9. 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)