Intimate Partner Violence Digital Considerations
draft-irtf-hrpc-ipvc-00
| Document | Type |
Expired Internet-Draft
(hrpc RG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Sofia Celi , Juliana Guerra , Mallory Knodel | ||
| Last updated | 2024-04-20 (Latest revision 2023-10-18) | ||
| Replaces | draft-celi-irtf-hrpc-ipvc | ||
| RFC stream | Internet Research Task Force (IRTF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources |
GitHub Repository
Mailing list discussion |
||
| Stream | IRTF state | (None) | |
| Consensus boilerplate | Unknown | ||
| Document shepherd | (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
This document aims to inform how Internet protocols and their implementations might better mitigate technical attacks at the user endpoint by describing technology-based practices to perpetrate intimate partner violence (IPV). IPV is a pervasive reality that is not limited to, but can be exacerbated with, the usage of technology. The IPV context enables the attacker to access one, some or all of: devices, local networks, authentication mechanisms, identity information, and accounts. These kinds of technical compromise exist in addition to on-path attacks, both active and passive [RFC7624]. In this document we describe the tactics the IPV attacker uses and what kind of counter-measures can be designed in IETF protocols.
Authors
Sofia Celi
Juliana Guerra
Mallory Knodel
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)