---
type: "term"
title: "R-FLOOD (Capacity Exhaustion vs Implementation Defect)"
description: "Global mapping rule: If the primary mechanism is volume or intensity exhausting finite resources, classify as 6 Flooding Attack ."
resource: "tlctc:term:r-flood-capacity-exhaustion-vs-implementation-defect"
tags:
  - "glossary"
---
# R-FLOOD (Capacity Exhaustion vs Implementation Defect)

Global mapping rule: If the primary mechanism is volume or intensity exhausting finite resources, classify as `#6 Flooding Attack`. If the primary mechanism is an implementation defect that causes crash/hang/degradation (including algorithmic complexity), classify as `#2` or `#3` per R-ROLE.

**Reference:** §4.2.5 (R-FLOOD)