[hrpc] Re: I-D Action: draft-irtf-hrpc-ipvc-02.txt
Timothy Holborn <timothy.holborn@gmail.com> Tue, 04 November 2025 06:32 UTC
Return-Path: <timothy.holborn@gmail.com>
X-Original-To: hrpc@mail2.ietf.org
Delivered-To: hrpc@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 4C8158239F9A for <hrpc@mail2.ietf.org>; Mon, 3 Nov 2025 22:32:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lfw7FoYLehFf for <hrpc@mail2.ietf.org>; Mon, 3 Nov 2025 22:32:49 -0800 (PST)
Received: from mail-pj1-x1031.google.com (mail-pj1-x1031.google.com [IPv6:2607:f8b0:4864:20::1031]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 830418239F8D for <hrpc@irtf.org>; Mon, 3 Nov 2025 22:32:49 -0800 (PST)
Received: by mail-pj1-x1031.google.com with SMTP id 98e67ed59e1d1-3418ad69672so34186a91.3 for <hrpc@irtf.org>; Mon, 03 Nov 2025 22:32:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1762237968; x=1762842768; darn=irtf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=4l5FFTWVw4DACjy8zzQaIF9asNOn/w2vKANFfYmThck=; b=kn9vGp6GS/azMPo1AODeHsQzW7XiIhOQHWF2VEd2GCOC5RKrf23GO0jhK4g4DNERFb +cY6oG22Ji/JpvSxQiSKbTzyTQM2Jcy4I55PgJOuYPzo+ur/rZMQE1tjQph6QLGKchiz 5O4rJXOEP83/Xts5R9jcGm3XBO0s+lSaJAZChEkjGbdd/6TrSxf4rKpcaQwsr7tUx+CW 8e5HRdLrs7e1HU1MvkQ/EdDnI6Upir8Y6wFgCdumjp/gvaNRJ1Zct9pa6hQzdoUQ1cnM oLBSSF5DaN2vy/TcQ3eHnbSK2yfmq/1G5f9bheP72+2q2rrG0Jq+ryFvywlXAAXc7ibe kmUw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1762237968; x=1762842768; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=4l5FFTWVw4DACjy8zzQaIF9asNOn/w2vKANFfYmThck=; b=UM6xwddBPzC7kVh3C7D6ePoKelrzIm42tXkpOcFt9WwuOJBcs9OLv3kkkq+bTJtQP3 GhVAf3MVo/mqH4BhmexU4lptezjKrlYFNHpeh6W5Q3FWN9Uiif/30mdKJnvjRbSaTEsS 6gcpqE9lSXbACaTYhcXwL2H+rd0eFamSDMzUsqks7kIKwhjUEnIdL8Wf2YjR1iLMG+tD wMz4olnAcUprnsUiMCiZ83P9VgPSrYzqw5UkfaVEFDBUXBFdQgz8Ugf5QxU4cHeC7nTV 6kIW33qr1kq+wCEm6YG28iX3pqYgtSBv3r1I0ftnlJnzUqTny2dcTTomxgD29bOsgqyc jn3g==
X-Gm-Message-State: AOJu0Yy4oRqacSpsc8351ZR3nOcQGyMJJetQdcgHVt2zk3e47w66SrXm tpNfYNAEQyMt5xAg9eun/AsQjP7RHoZc7b/2RUzO2Tes9OFDnkvErP2RUzeKdhialz+k72LVmfb dxVTqLttryDAl8dYN5UOcSX5vFHMK3i8=
X-Gm-Gg: ASbGncuSnstpHFQ5P29/CeKZpY16PFiUvQoO8sQZDBy0KNRxWtH/6xYIUeWigV4lUGA 6cFjlsekxyED05g719KyoNqMRAp/9MFDJXLz6B138H5l0N++reYUtWrWOqyxq34msVGJSCQwJc1 Hn9JiavZMOjHrxAds9nlaEi6/LwvK73ic19PVQymYJqewbRWB1pUUUFTsF9P3RYcFQVRCjUUGbV BfH/cfhsCresJJ+lwG9D1Mk53l5yfC0eN+S7BbZ2ZidfPiYuqUfsGP91/fLtH3fTn01eqkxW98A Em+SCgMmIpPS1xtBpImpI3U+w64sSNm9nikBc3CET07PTNFGALw=
X-Google-Smtp-Source: AGHT+IETrLlpCR0lwMEdL6kpb1WX29BO8HqySEtWZ6RZusNJIS9xGEzW56+1XwggS8qPSw7xxx6ily5CV98IpxkngRA=
X-Received: by 2002:a17:90b:582b:b0:341:88d5:a74e with SMTP id 98e67ed59e1d1-34188d5ab69mr319100a91.29.1762237968253; Mon, 03 Nov 2025 22:32:48 -0800 (PST)
MIME-Version: 1.0
References: <176220488619.317396.1815205362434083224@dt-datatracker-5df8666cb-7l4w5> <9cde13fa-8f71-4071-9422-1a65a7db1fdf@riseup.net> <8eb2ba82-6e58-4567-b819-727e3de31fab@netmagic.com> <CABMXHrEDA4=mBobes1q3G84d1Ra3adh_GNRMROsui1EnyVR86A@mail.gmail.com> <CAM1Sok3uBUj4EjYMjoPm6ZdP558Qq=N=um6Hx2jMJDLvqONxmg@mail.gmail.com> <e0a1070d-1315-47c0-9310-9fb8e512f3bd@riseup.net>
In-Reply-To: <e0a1070d-1315-47c0-9310-9fb8e512f3bd@riseup.net>
From: Timothy Holborn <timothy.holborn@gmail.com>
Date: Tue, 04 Nov 2025 17:32:34 +1100
X-Gm-Features: AWmQ_blB9IrLNjuPqEiOUo6x8Y1ah_0du9hK8WfXPMQAu1wU7VpBJI2kBr_LawI
Message-ID: <CAM1Sok1DsoPJ5pGcOOO=beoj8G1ntacLBLmn8ewR44fB+bsV9w@mail.gmail.com>
To: Sofia Celi <cherenkov@riseup.net>
Content-Type: multipart/alternative; boundary="0000000000001b87be0642bf0020"
Message-ID-Hash: 37HCOQEE7G4KIDBTRFVQQRDGQMVWA7YW
X-Message-ID-Hash: 37HCOQEE7G4KIDBTRFVQQRDGQMVWA7YW
X-MailFrom: timothy.holborn@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-hrpc.irtf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Hrpc <hrpc@irtf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [hrpc] Re: I-D Action: draft-irtf-hrpc-ipvc-02.txt
List-Id: hrpc discussion list <hrpc.irtf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/ufGg08fhQciB5vQssbq1lNGP70U>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hrpc>
List-Help: <mailto:hrpc-request@irtf.org?subject=help>
List-Owner: <mailto:hrpc-owner@irtf.org>
List-Post: <mailto:hrpc@irtf.org>
List-Subscribe: <mailto:hrpc-join@irtf.org>
List-Unsubscribe: <mailto:hrpc-leave@irtf.org>
🙏 On Tue, 4 Nov 2025, 1:46 pm Sofia Celi, <cherenkov@riseup.net> wrote: > This is very interesting, Timothy. > > > IMHO: the https://www.ohchr.org/en/instruments-listings <https:// > > www.ohchr.org/en/instruments-listings> provides texts, that should > have > > existing legislative supports of some kind in various jurisdictions, > > although often without deliberations having been made previously with > > respect to the implications of internet,which in relation to the notion > > of the humanitarian need for a (safe) home (indeed, not unlike that of > > many species), is very broad... > > Do you think we should propose also the idea of "safe digital space", > "safe devices"? I'm happy to start drafting something on those regards.. > I'll have to think more about it... As to give the considerations the proper - present day - consideration. > > There are also a variety of very important use-cases involving > > children. people have the right to be in a happy relationship and/or > > leave. evidence systems are of enormous importance for courts of law, > > sought to make decisions about the lives of young-ones.. there's some > > stats, but often far more data than published statistical products, > > etc. which makes it a difficult problem to address... > > > > Agreed. We are also starting a draft on digital abuse in the children > case. I hope I can share by next week. See: https://www.ohchr.org/en/instruments-mechanisms/instruments/convention-rights-child Therein, human rights & particularly also, those of children. Related thoughts (although perhaps also, a bit tangential); Many of the sorts of things needed to better support the human rights of children, also end up helping to address problems that adults of various forms of cohorts also experience problems with. Whether it be personal biometric as an extension of their being (face, DNA, stuff that's easier than our "mindware" and related AI (institutional/corporate - both foreign, Domestic and interop internationally) or rights frameworks/ fabrics, that are more complex than traditional Intellectual Property Law applications upon info sphere assets. https://en.wikipedia.org/wiki/Infosphere The work on credentials (verifiable credentials or whatever their called nowadays) was intended to work with RWW or what's commonly referred to as solid or indeed also, other "mydata" solutions (and/or similar). Therein, work on defining rights frameworks might consider that memories don't actually get deleted and shape our world views, through our experiences. Therein, relationships evolve overtime. So, say a couple grows together from a date of meeting, then shares many of their IoT keys, related possessions - maybe makes some naughty media together.. then later, they break up. IoT permissions all changed. But if they had an agreement between one another, the whatever the terms were remain in place even if the relationship changes (or, as directed by law or a court of law, etc). The work on "ADP" that I started but haven't progressed yet https://m.youtube.com/watch?v=ZDH5eaIF_zc&t=2024s https://datatracker.ietf.org/doc/slides-119-hotrfc-sessa-09-agent-discovery-protocol/ https://mediaprophet.github.io/init-draft-standards-wip/ADP/ (All poorly drafted ATM) Was also intended to then be expanded to support agreement between agents (ie: people) https://mediaprophet.github.io/init-draft-standards-wip/agreements/ (Also, poorly drafted ATM). Which was then intended to work with rsf versions of human rights agreements & similar. Some other poorly constructed notes https://mediaprophet.github.io/init-draft-standards-wip/ Some of the work to create rdf versions of the human rights instruments is, https://github.com/webcivics/ontologies Noting, that often their worded to speak to the responsibilities of the state; rather than, the responsibilities we have between one-another, and by extension also, those whom guardianship relations pertain to... These tools are then thought helpful to make safe(r) social media landscapes for everyone, including children. But, if definitions assume existing web 2.0 platforms, then some potential solutions are unlikely to work - perhaps until there's strong alternatives / competition. My view has historically been that there's some stuff that's in the IETF wheelhouse, some in the W3C wheelhouse and perhaps we need a new SDO effort for ontological design work (feminine led?) in particular., which then also means educating about ontology & building bridges across the liberal arts.. As were aspects of consideration relating to "human centric internet", et.al . I'll hopefully have more time over the next week or so to put into efforts to help you (plan to be living in a tent, so we will have to see), but importantly, I think there's some non-trivial complexities that deserve time, etc. as to better support the outcomes desired whilst also seeking to mitigate unintended consequences. Hard work. > Thank you, > Best wishes 🙏🕊️ Tim. > > > > On Tue, 4 Nov 2025 at 09:14, Mallory Knodel <mallory.knodel@nyu.edu > > <mailto:mallory.knodel@nyu.edu>> wrote: > > > > Hi, > > > > History of the draft started with “attacker you know” to be a boss, > > a parent, etc etc and we intentionally narrowed it so that we could > > have some specificity with respect to threat model. This as an > > attempt to move beyond the well understood on-path attack model > > present in most other WG/RH docs. > > > > We do have the opportunity to start other and very much related work > > as you suggest, Tim. > > > > -Mallory > > > > On Mon, Nov 3, 2025 at 17:06 Tony Rutkowski > > <trutkowski.netmagic@gmail.com > > <mailto:trutkowski.netmagic@gmail.com>> wrote: > > > > While well directed, it is not clear how these mitigations are > > related > > in any special way to "Internet protocols" - whatever those > > are. The > > needs are pervasive across contemporary ICT technologies. > > > > You might be aware that a number of industry, government and > > academic > > parties published TR 103 936, "Cyber Security > (CYBER); Implementing > > Design practices to mitigate consumer IoT-enabled coercive > > control" last > > year (which is not cited in the ID). See > > https://urldefense.proofpoint.com/v2/url? > > > u=https-3A__www.etsi.org_deliver_etsi-5Ftr_103900-5F103999_103936_01.01.01-5F60_tr-5F103936v010101p.pdf&d=DwIDaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=krANNudPSfUTEf2kXiduBUqRjXhDsKNCASr1kibHLfs&m=NKPwoKXUWbOeq0XFJFoZo0-nDErU3WJXw_LjGoLOpFvjaVJPtbI6w-dL29RUGPaW&s=DaJsm8PvLNbEOT85x9otD_bDvTB29BdzgSce2pSU1f8&e= > < > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.etsi.org_deliver_etsi-5Ftr_103900-5F103999_103936_01.01.01-5F60_tr-5F103936v010101p.pdf&d=DwIDaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=krANNudPSfUTEf2kXiduBUqRjXhDsKNCASr1kibHLfs&m=NKPwoKXUWbOeq0XFJFoZo0-nDErU3WJXw_LjGoLOpFvjaVJPtbI6w-dL29RUGPaW&s=DaJsm8PvLNbEOT85x9otD_bDvTB29BdzgSce2pSU1f8&e= > > > > > > > > Further, an aggregation of the same parties are updating the > > provisions. See attached which in the process of being > > approved. All > > hrpc participants are welcome to participate. > > > > --tony r > > > > > > On 11/3/2025 4:23 PM, Sofia Celi wrote: > > > Hi, all, > > > > > > As just noted: we have the new draft version. Please, do send > > > feedback. An open item we had is whether we should add an > ML/AI > > > considerations section to it. > > > > > > Thank you, > > > > > > On 03/11/2025 21:21, internet-drafts@ietf.org > > <mailto:internet-drafts@ietf.org> wrote: > > >> Internet-Draft draft-irtf-hrpc-ipvc-02.txt is now available. > > It is a > > >> work item > > >> of the Human Rights Protocol Considerations (HRPC) RG of the > > IRTF. > > >> > > >> Title: Intimate Partner Violence Digital Considerations > > >> Authors: Sofia Celi > > >> Juliana Guerra > > >> Mallory Knodel > > >> Name: draft-irtf-hrpc-ipvc-02.txt > > >> Pages: 18 > > >> Dates: 2025-11-03 > > >> > > >> 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 security compromises > > go beyond > > >> active and passive on-path attacks [RFC7624]. With a > > focus on > > >> protocols, the document describes tactics of the IPV > > attacker and > > >> potential counter-measures. > > >> > > >> The IETF datatracker status page for this Internet-Draft is: > > >> https://urldefense.proofpoint.com/v2/url? > > > u=https-3A__datatracker.ietf.org_doc_draft-2Dirtf-2Dhrpc-2Dipvc_&d=DwIDaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=krANNudPSfUTEf2kXiduBUqRjXhDsKNCASr1kibHLfs&m=NKPwoKXUWbOeq0XFJFoZo0-nDErU3WJXw_LjGoLOpFvjaVJPtbI6w-dL29RUGPaW&s=qZgfKeIdJOG_YBz8OGNaI3oq7tx5Nstfl6oBO4bnraM&e= > < > https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dirtf-2Dhrpc-2Dipvc_&d=DwIDaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=krANNudPSfUTEf2kXiduBUqRjXhDsKNCASr1kibHLfs&m=NKPwoKXUWbOeq0XFJFoZo0-nDErU3WJXw_LjGoLOpFvjaVJPtbI6w-dL29RUGPaW&s=qZgfKeIdJOG_YBz8OGNaI3oq7tx5Nstfl6oBO4bnraM&e= > > > > >> > > >> There is also an HTML version available at: > > >> https://urldefense.proofpoint.com/v2/url? > > > u=https-3A__www.ietf.org_archive_id_draft-2Dirtf-2Dhrpc-2Dipvc-2D02.html&d=DwIDaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=krANNudPSfUTEf2kXiduBUqRjXhDsKNCASr1kibHLfs&m=NKPwoKXUWbOeq0XFJFoZo0-nDErU3WJXw_LjGoLOpFvjaVJPtbI6w-dL29RUGPaW&s=70iWdS1H_jdkESagSBRwQMrUOQKpfAT5jtdsdsecwu0&e= > < > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_archive_id_draft-2Dirtf-2Dhrpc-2Dipvc-2D02.html&d=DwIDaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=krANNudPSfUTEf2kXiduBUqRjXhDsKNCASr1kibHLfs&m=NKPwoKXUWbOeq0XFJFoZo0-nDErU3WJXw_LjGoLOpFvjaVJPtbI6w-dL29RUGPaW&s=70iWdS1H_jdkESagSBRwQMrUOQKpfAT5jtdsdsecwu0&e= > > > > >> > > >> A diff from the previous version is available at: > > >> https://urldefense.proofpoint.com/v2/url? > > > u=https-3A__author-2Dtools.ietf.org_iddiff-3Furl2-3Ddraft-2Dirtf-2Dhrpc-2Dipvc-2D02&d=DwIDaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=krANNudPSfUTEf2kXiduBUqRjXhDsKNCASr1kibHLfs&m=NKPwoKXUWbOeq0XFJFoZo0-nDErU3WJXw_LjGoLOpFvjaVJPtbI6w-dL29RUGPaW&s=6BqETLWecAxK1Z7WCXM51j3x_mncYUfB-YDPbll2N2g&e= > < > https://urldefense.proofpoint.com/v2/url?u=https-3A__author-2Dtools.ietf.org_iddiff-3Furl2-3Ddraft-2Dirtf-2Dhrpc-2Dipvc-2D02&d=DwIDaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=krANNudPSfUTEf2kXiduBUqRjXhDsKNCASr1kibHLfs&m=NKPwoKXUWbOeq0XFJFoZo0-nDErU3WJXw_LjGoLOpFvjaVJPtbI6w-dL29RUGPaW&s=6BqETLWecAxK1Z7WCXM51j3x_mncYUfB-YDPbll2N2g&e= > > > > >> > > >> Internet-Drafts are also available by rsync at: > > >> rsync.ietf.org::internet-drafts > > >> > > >> > > >> _______________________________________________ > > >> hrpc mailing list -- hrpc@irtf.org <mailto:hrpc@irtf.org> > > >> To unsubscribe send an email to hrpc-leave@irtf.org > > <mailto:hrpc-leave@irtf.org> > > >_______________________________________________ > > hrpc mailing list -- hrpc@irtf.org <mailto:hrpc@irtf.org> > > To unsubscribe send an email to hrpc-leave@irtf.org > > <mailto:hrpc-leave@irtf.org> > > > > _______________________________________________ > > hrpc mailing list -- hrpc@irtf.org <mailto:hrpc@irtf.org> > > To unsubscribe send an email to hrpc-leave@irtf.org <mailto:hrpc- > > leave@irtf.org> > > > > > > _______________________________________________ > > hrpc mailing list -- hrpc@irtf.org > > To unsubscribe send an email to hrpc-leave@irtf.org > > -- > Sofía Celi > @claucece > Cryptographic research and implementation at Brave and University of > Bristol. 🏳️🌈 > Reach me out at: cherenkov@riseup.net > Website: https://sofiaceli.com/ > > _______________________________________________ > hrpc mailing list -- hrpc@irtf.org > To unsubscribe send an email to hrpc-leave@irtf.org >
- [hrpc] I-D Action: draft-irtf-hrpc-ipvc-02.txt internet-drafts
- [hrpc] Re: I-D Action: draft-irtf-hrpc-ipvc-02.txt Sofia Celi
- [hrpc] Re: I-D Action: draft-irtf-hrpc-ipvc-02.txt Timothy Holborn
- [hrpc] Re: I-D Action: draft-irtf-hrpc-ipvc-02.txt Tony Rutkowski
- [hrpc] Re: I-D Action: draft-irtf-hrpc-ipvc-02.txt Mallory Knodel
- [hrpc] Re: I-D Action: draft-irtf-hrpc-ipvc-02.txt Timothy Holborn
- [hrpc] Re: I-D Action: draft-irtf-hrpc-ipvc-02.txt Sofia Celi
- [hrpc] Re: I-D Action: draft-irtf-hrpc-ipvc-02.txt Timothy Holborn
- [hrpc] Re: I-D Action: draft-irtf-hrpc-ipvc-02.txt Sofia Celi