MyTerms Contract Negotiation Protocol (MCNP)
bofreq-curtis-myterms-contract-negotiation-protocol-mcnp-00
| Document | Type | Proposed BOF request | |
|---|---|---|---|
| Title | MyTerms Contract Negotiation Protocol (MCNP) | ||
| Last updated | 2026-05-21 | ||
| State | Proposed | ||
| Editor | Benjamin Curtis | ||
| Responsible leadership | |||
| Send notices to | (None) |
Name: MyTerms Contract Negotiation Protocol (MCNP)
Description
The purpose of MyTerms is to provide individuals with means to proffer their own terms respecting personal privacy in ways that can be read, acknowledged and agreed to by machines operated by others in the networked world.
MyTerms agreement methods were recently approved by IEEE, and with ongoing conversations with many potential partners and engagement with EU regulators (described in more detail in the mailing list post), we wish to work with IETF on formalizing a protocol that can implement the signing of Verifiable Contractual Agreements (VCAs) via a machine negotiation based on user-selected contractual agreements at extremely high volumes.
After discussions with chairs of existing WGs in Shenzhen at IETF 125, including conversations with Orie Steele and Charles Eckert about ART dispatch, we are requesting a BoF at IETF 126 to formalize further conversations. The goal of the MCNP BoF is to determine interest in, and the path forward within, IETF for future work.
Required Details
- Status: non-WG forming
- Responsible AD: ART
- BOF proponents:
- Ben Curtis <ietf@nowsci.com>
- Thomas Howe <ghostofbasho@gmail.com>
- Number of people expected to attend: 15
- Length of session (1 or usually 2 hours): 1 hour
- Conflicts (whole Areas and/or WGs)
- Chair Conflicts: ART
- Technology Overlap: ART
- Key Participant Conflict: ART
Information for IAB/IESG
To allow evaluation of your proposal, please include the following items:
- Any protocols or practices that already exist in this space: None that cover contractual methodologies
- Which (if any) modifications to existing protocols or practices are required: None
- Which (if any) entirely new protocols or practices are required: MCNP
- Open source projects (if any) implementing this work:
- Reference implementations exists in
- MyKey (https://mykey.me/)
- FedID (https://fedid.me/)
- Multiple interested and integrating parties mentioned in the Mailing List, including OpenVTC (the Linux Foundation project for Kernel Developers and other communities)
Tentative Agenda
- Administrative [5 minutes]
- Purpose of BoF [5 minutes]
- MyTerms 101 [25 minutes]
- Overview of MyTerms
- Agreement structures
- Verifiable Contractual Agreements (VCAs)
- Draft review
- Hosting and negotiation agreements
- Signing agreements
- Discovery
- Open discussion [20 minutes]
- What pathways to continue the IEEE work in IETF exist?
- What WGs does this relates to, or should we be WG-forming going forward?
- Are there any other projects or initiatives that are relevant?
- Closing remarks and next steps [5 minutes]
Links to the mailing list, draft charter if any (for WG-forming BoF), relevant Internet-Drafts, etc.
- Mailing List: https://mailarchive.ietf.org/arch/browse/art/
- Introduction message on the list: https://mailarchive.ietf.org/arch/msg/art/JgWNwxW5T1XZHjlU03SozPWyGX8/
- Relevant Internet-Drafts: