1 / 5

Security Assessment of the IPv6 Flow Label and Its Implications

This document, part of a broader unpublished work on IPv6 security by UK CPNI, analyzes the security implications of the Flow Label field in IPv6. It discusses potential theoretical denial-of-service (DoS) vectors resulting from Flow Label verification as described in RFC 2460, along with covert channels, QoS theft, and information leakage. The proposal includes an algorithm for selecting flow labels that minimizes predictability and reduces collisions, drawing inspiration from RFC 1948 and compliant with RFC 3697.

JasminFlorian
Télécharger la présentation

Security Assessment of the IPv6 Flow Label and Its Implications

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. Security Assessment of the IPv6 Flow Label(draft-gont-6man-flowlabel-security-00) Fernando Gont on behalf of UK CPNI IETF 79 November 7-12, 2010. Beijing,China.

  2. Summary • Document is part of a larger document on IPv6 security being produced by UK CPNI (yet unpublished) • Analyzes the security implications of the Flow Label field • Proposes an algorithm for selecting flow labels

  3. Security Implications of the Flow Label field • Possible (theoretical) DoS vector resulting from Flow Label verification described in RFC 2460 • Covert Channels • QoS theft • Information leaking

  4. Selecting Flow Labels • Requirements: • Flow Labels that are predictable by off-path attackers • Flow Label collisions are reduced • Proposed algorithm (a la RFC 1948, and compliant with RC 3697): Flow Label = counter + hash(Source Address, Destination Address, Secret Key)

  5. Moving forward • Comments? • Adopt as wg item?

More Related