1 / 8

Enabling Binding Update via access authorization

Enabling Binding Update via access authorization. Charles Perkins, Basavaraj Patil IETF 82 [ netext ] WG / Taipei November 16, 2011. The problem. Mobile devices often have to carry out two separate authentications before receiving packets at from home network

kalb
Download Presentation

Enabling Binding Update via access authorization

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Enabling Binding Update via access authorization Charles Perkins, BasavarajPatil IETF 82 [netext] WG / Taipei November 16, 2011

  2. The problem Mobile devices often have to carry out two separate authentications before receiving packets at from home network • Access authorization at local access network • Binding Update to home network This typically makes smooth handovers impossible.

  3. A solution • Enable access authorization to be relayed by the Home Agent which can then perform the Binding Update • For access authorizations using EAP, this can be done very simply by defining a new format for authentication data that is the same as the required EAP authentication data

  4. EAP Authentication Data [EAPAD] • The EAP Authentication Data [EAPAD] subtype has exactly the format defined in RFC 3748 for an EAP message. • This enables the LMA to unwrap the EAP message for delivery to AAA, acting as a simple AAA relay • LMA uses the EAP reply status to determine whether to apply the Binding Update

  5. Binding Acknowledgement Authentication Data • LMA needs to complete the authentication sequence by returning PBAck to the MAG. • The PBAck Authentication Data option uses, similarly to the PBU previously described, data as defined by RFC 3748 • When MAG receives the data, then it can complete the EAP sequence, say according to 802.1x

  6. Combined Auth/Reg in PMIP6 MN LMA AP AR/MAG AAA 802.11 Assoc (Access blocked) EAPOL-Start LMA acts as a AAA proxy/relay EAP-Req/Identity PBU with EAPAD RADIUS Access Req EAP-Method PBA with EAPAD Binding created EAP Success RA or DHCP

  7. Combined Auth/Reg in MIP6 MN HA AP AR AAA 802.11 Assoc (Access blocked) EAPOL-Start HA acts as a AAA proxy/relay (Extract/Process BU) EAP-Req/Identity Include BU inside the EAP message RADIUS Access Req EAP-Method Binding created EAP Success Assumption: MN obtains CoA from AR prior to start of EAP

  8. Role of NAI • The MN should naturally be identified by its NAI, and MN-NAI extension applied to PBU / PBAck. The NAI should identify which home agent / LMA is appropriate for the home address of the mobile node. • If there are thousands of home agent for the same AAA, then a local AAA relay can be configured with this information instead of configuring each MAG separately.

More Related