1 / 8

FCAST update TESLA update

FCAST update TESLA update. IETF 76 – Hiroshima, November 2009 V. Roca (INRIA). FCAST update. Modifications WRT July's -05 version. a lot of cleanup, especially W.R.T. NORM…

dora
Télécharger la présentation

FCAST update TESLA update

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. FCAST updateTESLA update IETF 76– Hiroshima, November 2009 V. Roca (INRIA)

  2. FCAST update

  3. Modifications WRT July's -05 version • a lot of cleanup, especially W.R.T. NORM… • removed the possibility of having a streamlined meta-data in the original compound if NORM_INFO is used (since NORM_INFO support is optional) • clarified that the NORM_INFO compound object's checksum only encompasses the header • clarified that padding is not used when there's no Object Data in a compound object (NORM_INFO and "empty CIO list") • added NORM_INFO example (annex A.2) • Fcast-CIO-Complete and Fcast-CIO-ID meta-data entries of a CIO are now optional. Goal is to simplify the simple case of a session consisting of a single, complete, carousel instance (the CIO contains no meta-data, just the object list)

  4. And now? • FCAST: a simple, elegant and efficient solution for both protocol families (ALC/LCT and NORM) • officially a WG Item • even if -06 is still individual I-D • go into WGLC ?

  5. TESLA update

  6. Quick reminder on TESLA • a loss-tolerant, high-throughput, per packet, source authentication and integrity verification protocol • for "source → receivers" flow only • for ALC/LCT and NORM • with NORM, another mechanism is needed for feedback • along with group MAC/digital signatures, it provides a comprehensive set of techniques • see <draft-ietf-rmt-simple-auth-for-alc-norm-02.txt>, now in WGLC, please review ;-)

  7. Quick reminder on TESLA… (cont') • TESLA/Group MAC/digital signatures EXT_AUTH header extensions all start with an ASID (Auth. Scheme ID) field • several authentication schemes can be used jointly in the same session (e.g. NORM)

  8. Situation • TESLA is an MSEC document • passed WGLC (end 2008) • version -10 accepted by IESG last week • now in "RFC Editor Queue" state • Main recent modifications during IESG review: • removed several TESLA messages for the sake of simplicity • however it remains relatively complex  • corrected a major mistake in key derivation description • + many details

More Related