RFC 7258 additions due to evolving Internet thread model
draft-arkko-farrell-arch-model-t-7258-additions-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Jari Arkko , Stephen Farrell | ||
| Last updated | 2021-02-21 (Latest revision 2020-08-20) | ||
| RFC stream | (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
Communications security has been at the center of many security improvements in the Internet. The goal has been to ensure that communications are protected against outside observers and attackers. RFC 7258 is the IETF guidance on taking into account pervasive monitoring threats in Internet technology development work. This memo suggests additions to RFC 7258 to cater for the evolving threats. For instance, it may be necessary to also worry about information collected by a legitimate protocol participant being misused for pervasive monitoring purposes.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)