DIME WG IETF-69

1. DIME WGIETF-69 Diameter Proxy Mobile IPv6: Support For Mobility Access Gateway and Local Mobility Anchor to Diameter Server Interaction draft-ietf-korhonen-dime-pmip6-00 July, 2007 Jouni Korhonen, Julien Bournelle & Kuntal Chowdhury

2. Background & solution • NetLMM WG is working on a PMIPv6 protocol, its IPv4 enhancements and MIP6-PMIP6 transition • Deployments need/benefit/require AAA backend support for PMIPv6 bootstrapping, management and accounting • This I-D aims to provide Diameter support for • MAG (NAS) to AAA interface • LMA (HA) to AAA interface

3. Solution cont’d +--------+ | HAAA & | Diameter +-----+ | Policy |<-------->| LMA | | Profile| +-----+ +--------+ | <--- LMA-Address ^ | | // \\ +---|------------- //---\\----------------+ ( | IPv4/IPv6 // \\ ) ( | Network // \\ ) +---|-----------//---------\\-------------+ | // \\ Diameter // <- Tunnel1 \\ <- Tunnel2 | // \\ | |- MAG-Address1 |- MAG-Address2 | +----+ +----+ +---->|MAG1| |MAG2| +----+ +----+ | | | | [MN1] [MN2] • Extends MIP6 Integrated bootstrapping • Is not specific to PMIP6 as the only mobility service • Includes AAA based mobility mode selection • Includes AAA based capability advertisement and authorization • Support assignment of local prefixes also

4. New AVPs • PMIP6-MAG-Address AVP • Type of Address and contains the IP address of the MAG • PMIP6-LMA-Address AVP • Type of Address and contains the IP address of the LMA. This AVP is included inside the MIP6-Agent-Info grouped AVP [ietf-dime-mip6-integrated-05] • PMIP6-LMA-FQDN AVP • Type of DiameterIdentity and contains the FQDN of the LMA. This AVP is included inside the Mobility-Agent-Info grouped AVP [ietf-dime-mip6-integrated-05]

5. New AVPs cont’d • PMIP6-IPv4-Home-Address AVP • Type Address and contains the IPv4-HoA of the MN • PMIP6-DHCP-Address AVP • Type Address and contains the IP address of the DHCPv4 and/or DHCPv6 server assigned to the MAG serving the newly attached MN • PMIP6-Home-Prefix AVP • Type Address and contains the MN-NHP. The low 64 bits of the IPv6 address must be all zeroes • The PMIP6-Home-Prefix AVP may also be used on the LMA to AAA interface. In this scenario the AVP contains the prefix the LMA has assigned to the MN. The LMA may also delegate assignment of the MN-HNP to the AAA

6. Capability advertisement and authorization • During the access authentication a MAG/NAS should include its mobility service related capabilities into the MIP6-Feature-Vector AVP [ietf-dime-mip6-integrated-05] • Then the AAA authorizes those that are supported by the LMA (in MSA/MSP) and the subscription profile • The feature vector may also include information about other mobility services than PMIP6 • Following new capabilities are defined: Token | Value | Description ----------------------------------+----------------------+------------ PMIP6_SUPPORTED | 0x0000000100000000 | [RFC TBD] IP4_HOA_SUPPORTED | 0x0000000200000000 | [RFC TBD] LOCAL_MAG_ROUTING_SUPPORTED | 0x0000000400000000 | [RFC TBD] RO_SUPPORTED | 0x0000000800000000 | [RFC TBD]

7. Open Issues • RADIUS interworking • We need to have some practical guidance & solution for RADIUS interworking.. • ’Mobility Mode’ selection needs to be studied further • Currently the I-D provides an AAA based solution that allows mobility mode selection • Address configuration modes need to be verified • No way to tell whether stateless or stateful address configuration should be used • Current I-D allows also AAA to manage prefixes • Some people like this and some think that _only_ a LMA should do it • It is unclear whether optimization other than RO would need support from AAA. This needs to be investigated • Accounting part needs more work • MN-HoA DNS update on behalf of the MN?

8. Next steps Cross checking (again) against all the PMIP6 I-Ds and MIP6 bootstraping I-Ds Adopt as a WG Work Item?!

9. Questions? Feedback?