1 / 4

EMSK Usage Guidelines (EAP key derivation for multiple applications)

This document provides guidelines for the usage of the Extensible Messaging and Presence Protocol (EMSK) in deriving keys for multiple applications using the EAP key derivation framework. It discusses the key framework draft, key naming, and examples of EMSK usage to promote the derivation of computationally independent keys for various applications.

starksc
Download Presentation

EMSK Usage Guidelines (EAP key derivation for multiple applications)

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. EMSK Usage Guidelines(EAP key derivation for multiple applications) draft-salowey-eap-key-deriv-02.txt J. Salowey P. Eronen IETF 58

  2. EMSK • 2284bis defines and reserves EMSK. • Several applications have been suggested for it • draft-ietf-eap-keying-01.txt • draft-irtf-aaaarch-handoff-04.txt • draft-salowey-eap-protectedtlv-01.txt • Others

  3. Key Framework Draft • Usage guidelines for the EMS need to be established • Key Naming needs to be fleshed out (deriving names directly from keys may not be such a good idea) • Examples of EMSK usage should promote usage of the EMSK such that computationally independent keys can be derived for several applications (i.e. the guideline draft)

  4. Next Step • Incorporate the EMSK Guideline draft into the key framework draft or reference it.

More Related