Internet Threat Model - A Reconsideration
draft-mcfadden-threat-model-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Mark McFadden , Jim Reid | ||
| Last updated | 2023-04-27 (Latest revision 2022-10-24) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
RFC3552/BCP72 describes an Internet Threat model that has been used in Internet protocol design. More than twenty years have passed since RFC3552 was written and the structure and topology of the Internet have changed dramatically. With those changes comes a question: has the Internet Threat Model changed? Or, is the model described in RFC3552 still mostly accurate? This draft attempts to describe a non-exhaustive list of the most likely updates and changes in the current threat environment. This paper has the goal of suggesting a way forward for describing the contemporary threat model and how it might inform security aspects of protocol design.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)