1 / 3

Secure Establishment of Security Associations for Mobility Protocols

Delve into the options for the establishment of security associations between a Mobile Node and a network node in various mobility protocols. Explore authentication, key derivation, certificate provisioning, and frameworks for a comprehensive approach to security. Consider using BAD and Mobility Header messages for enhanced security functionality.

alexis
Télécharger la présentation

Secure Establishment of Security Associations for Mobility Protocols

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. Some thoughts on MN – AR SA establishment • Many mobility protocols need security association (not necessarily Ipsec) between a Mobile Node and a network node, typically an access router • Examples: Context Transfer, Fast Handover, CARD • The mobility protocols themselves cannot establish a security association • What are the options?

  2. Options for SA establishment • AAA based access authentication? • Used in 3GPP2 • A way to derive keys which can be used later for Mobile IPv6 BU • SEND-based • Public hotspots? • IKE? • Issue: Certificate provisioning between MN and an arbitrary visited network router • EAP-based keying? • EAP-over-any-access-network? • Keep Type-specific authentication mechanism open • Note: specifying a single mechanism appears not worthwhile. Instead, a framework may be the best option available

  3. Framework • Assuming that a framework is the way to go forward, what are the specific requirements? • An option such as BAD is almost necessary • BAD would work readily with Mobility Header messages • Perhaps it is a good idea to have all MN – AR messaging to use MH messages? • We need a reference (ID, RFC) which can be used to address the security considerations of mobility protocols

More Related