Return-Path: X-Original-To: ai-control@mail2.ietf.org Delivered-To: ai-control@mail2.ietf.org Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 15F12D370A34 for ; Mon, 30 Mar 2026 06:21:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1774876901; bh=W64/4vlB9rP05CEp7HrhLJI2f+Krq8rVygSjW66fTts=; h=From:To:Subject:Date:References:In-Reply-To; b=PphrsI4LEL6SCo5JrAR94KWWcf0M7lADprUg+UQwqzDtNdfzfIdA7IAiebVj3xplZ pDO96AunYmApXsyVVUSwjjXxD76a6hNLnUU0FQ76syRB2PJCs3nXJZf5sibEMxqm8E 6ewRmeMyNoS8hMW4G51svywmo+sUAJqFU+QaLvL4= X-Virus-Scanned: amavisd-new at ietf.org X-Spam-Flag: NO X-Spam-Score: -2.096 X-Spam-Level: X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 CYSPY7rLeD0t for ; Mon, 30 Mar 2026 06:21:40 -0700 (PDT) Received: from OSPPR02CU001.outbound.protection.outlook.com (mail-norwayeastazon11023119.outbound.protection.outlook.com [40.107.159.119]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 35494D370A25 for ; Mon, 30 Mar 2026 06:21:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=oN3Apa536ggnaEYR35lBxMtjBW/Tej5K6ZIq+xV5fwHDoGTh9TKYE1fnH2tiDPJTqeNQGAR4s7dJhSxlnGZun0/ur3cs38BdeObOmAIYImPClk8X1fOUzTyJOYpLpbp+y/Ye75V/+8L1zWIJkw7HXmbiUWv/wDVX6FfMNj8mZe+9jDGATh74nOWDqKrCDj2b5itWfN4D+zyDKMWtOe29gVpccGYv5OGMlXmQKFvYjWnLkTBcQF1dqgXmHM5avrhBfxQ/OaxPFmME8kykjdNOZZJVDBLlgKnt7WvCRUtujO9i3mZoWIztADXdtjKSDhhdRSW0LLHjQEAXhTgUrB4qiA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=W64/4vlB9rP05CEp7HrhLJI2f+Krq8rVygSjW66fTts=; b=WVZHsIPLC4h7EmZSsonrs3qH1YN7zom3fsNmcusCP4a6uMt3vpHjGqSXcFnhwJABellHjfscLwHV2zwu+q45oqx75Vt9df+TvuT8zJHGMgWNAdjMr2Xrh/fYywp7hRtb36JNfkuWlnVk/aQRI79vpyeoBos7yFxJTq9ZB/ywKPpXz2evyUDFqIzy87Roc21AOnAsMETp7+QdyUIs5+4exoehWYKGgUPMM37AG4tLbZCX6SvLRH+DrfE80Mo3rnsw1IK5PZBmX8LjTRviYA4nzRn6Z1CMLeGanLplPX51BkiE0Tj3KseHrJHHkEbLzdd+btiz7mUg3I/NLvE4W2a22A== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=github.com; dmarc=pass action=none header.from=github.com; dkim=pass header.d=github.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=W64/4vlB9rP05CEp7HrhLJI2f+Krq8rVygSjW66fTts=; b=PUbmgoeN0hyKuy6kFaJ325k1iCTiLXN29WcJ0WvLvxXYNGmF7cAfiDGFL/Kfx7stB0m02yHd6QlmCF58xLHgkMS0GkkvmhtDsPeMq/phenTtPUoLYSSMU5JXVsdlm3nDVl0n7+qAowDBIkkeKeed1QKFcJAxWurSw+7R0ZRaBII= Received: from PA6PR83MB0600.EURPRD83.prod.outlook.com (2603:10a6:102:3d7::19) by AS4PR83MB0524.EURPRD83.prod.outlook.com (2603:10a6:20b:4f2::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.9769.15; Mon, 30 Mar 2026 13:21:30 +0000 Received: from PA6PR83MB0600.EURPRD83.prod.outlook.com ([fe80::5a56:50e5:d8e2:7a65]) by PA6PR83MB0600.EURPRD83.prod.outlook.com ([fe80::5a56:50e5:d8e2:7a65%4]) with mapi id 15.20.9769.014; Mon, 30 Mar 2026 13:21:30 +0000 From: Felix Reda To: Thomas Aynaud , "ai-control@ietf.org" Thread-Topic: Proposal: AI Preference Attachments for Source Code and VCS (Seeking Co-editors) Thread-Index: ODsqiZD602PxK4atYoJOvDJGaGhUscMre0iv Date: Mon, 30 Mar 2026 13:21:29 +0000 Message-ID: References: <666290675.117986838.1774857278525.JavaMail.zimbra@inria.fr> In-Reply-To: <666290675.117986838.1774857278525.JavaMail.zimbra@inria.fr> Accept-Language: en-US, de-DE Content-Language: en-GB X-MS-Has-Attach: X-MS-TNEF-Correlator: msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=True;MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47;MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2026-03-30T13:14:58.1058284Z;MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=Internal;MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ContentBits=0;MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Method=Standard x-ms-reactions: allow authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=github.com; x-ms-publictraffictype: Email x-ms-traffictypediagnostic: PA6PR83MB0600:EE_|AS4PR83MB0524:EE_ x-ms-office365-filtering-correlation-id: 6287f7be-5041-48f5-e3fa-08de8e5f4126 x-ms-exchange-senderadcheck: 1 x-ms-exchange-antispam-relay: 0 x-microsoft-antispam: BCL:0;ARA:13230040|10070799003|366016|4022899009|1800799024|376014|38070700021|13003099007|7053199004|56012099003|18002099003|22082099003|8096899003|3613699012; x-microsoft-antispam-message-info: Guo79dSXpAX/Ob7aj1xdlBRpN9COqsbrj5K4ZLBpg15OLnfD503humPbq14ElJzvwYgxCI512sY3bYAQ+efI3MUtldg2YA8ygptOtah6U2CQAwja9lGWawAyzwDT85HeBLi3VEg54zYp/qBFGd6KKwUT6KZ8ORuRsKZBAiA441LZrUUShueCiA0BJgJbCMZoxi6lRMeshD05Iy8X8jgYd3oGk6+AovmUEmbj5LG4YY2or2q8gvwb0MztctDzm5htVjaS+mHy8/KwTh/19iNWSfZTA/zKYUgbNkAXDLY3C52sy2eMRmRy9yidtYbYfvb2mXuoNj0KvoPrIOksult1gx8mDni3zTTs9iWIKWwUkJFbs1C3DV3jqe29G3t79644jIl5MFCarHFARMc43+VNmzwzmgS3jvhq7EtVsX2euqhJIOiM6//h/L+NRwFKVWmqrcSTe7zLyou+tU5Ocn9FL64oiIDkB8OlD57eq9pxl1RYn45fVxK+FwRSculscTDZi8lsxjd3Ie1AZoq/+eLrGdFuxxV19djQtmaR9ijQOiCVx6oolhqaUhG17UrWVNvP10gRlCtIV4G+0v5rEWd23RVTe4WZanNhUGtfrJ4bPaxmsj1wdgNgbK/64+Y6zlELx9n1+iZbLOqLog+8PdyZ5YbvVG5eAytW7QGzZP6XIsC6qoCUO+1nQAtrl0k5PhwmkbJ4lgyabGs1fa4GJ11G9TxNiM3j8PYIP1qiacjf0NETfGpjYt/YFVYls5JR/1brkFUISa0RtVNhIDdgiU4s+w== x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:PA6PR83MB0600.EURPRD83.prod.outlook.com;PTR:;CAT:NONE;SFS:(13230040)(10070799003)(366016)(4022899009)(1800799024)(376014)(38070700021)(13003099007)(7053199004)(56012099003)(18002099003)(22082099003)(8096899003)(3613699012);DIR:OUT;SFP:1102; x-ms-exchange-antispam-messagedata-chunkcount: 1 x-ms-exchange-antispam-messagedata-0: =?Windows-1252?Q?EXD4R5XD+ZeNYpvngGv0KXtgW0Zpoyi3/iCn4wBW0wVLv0+WJbwGhODC?= =?Windows-1252?Q?c+4sSkFxPjxqx7wcWZgFXLxMIHaYZHviXxpmHNINW/OPwD0HsVChVSR0?= =?Windows-1252?Q?Yn42GVOEgkMx3d4AhHTdiA3NdzCh4DRQBehk1Cj1DT7ZtMqugzGlBzVl?= =?Windows-1252?Q?J0nJneCLLrNmhl2e1q64zbwF8Fsor/0rsjstgoHtC5jSOC3e0tqB82m0?= =?Windows-1252?Q?WgOIvSK+0zHOoovFNVF5OYnxd5iBHU9EERwpRjQma1mT4rjI0UzBEKg8?= =?Windows-1252?Q?eiCuzZe9jIah3wyS3sf2FpfZuUOCnVF3bnPYM2Aml7qnOQwiHkluQOnX?= =?Windows-1252?Q?aHJQ6YJjuNRBy4aZG00jh1eDEnx5vEmP053G5WEyrFuDcfmKWiyAncVj?= =?Windows-1252?Q?3CHTE/jf400/Wqbr5e2Jtd/fFSVdV77MSUyPlP8R7RT0vfUIaj9gND01?= =?Windows-1252?Q?eGR8/Rk+b1siNqK9o7BUN1zlEdsxE/Isp3feZLX+idyeweXwQAPVc43U?= =?Windows-1252?Q?HeJzFZ1HMaXRImPp3EEH5koxl6f8WYMFysqJGzh6jYLwhqfznI7Yq868?= =?Windows-1252?Q?zcl3esFI5e8T9qfUL1VQ/0XQ572qNT9OnPvKZEddGVaf9gTTaTBi3oA1?= =?Windows-1252?Q?sdNsHHXJTVF0fFdVyt/GBB1vFpdOIKvQwJrEUSC4QyxccCsvhJnYRij4?= =?Windows-1252?Q?o+XyqDLc3cndaGiI7KQsJJTPnRS+bUy5cxE8yMKbyXS2xcb46yc7FUnF?= =?Windows-1252?Q?f0wCzVbcWbo/bH3Z7kz2qoXklevLZqXIyOb8M40OEqMsYPPRrRA2LRr1?= =?Windows-1252?Q?Xguza+QvyDvHpWaObhIFS3ShIrqafxBg3faTiWoiKVBIqfYr2fYKdT0g?= =?Windows-1252?Q?WhbtVdn3N/lHV0yazdfnQtf3FJUvdtYlIVoRmpdlSPquxnKu/QPjoZhF?= =?Windows-1252?Q?EWp2JBQfFd2pdq0EDOlyPvOB1G4pcNT1C+riqe4TzuD3n1CUEpinak/x?= =?Windows-1252?Q?xbwkVpurmx5wSU3+6BoltYpFZX/mIihcv8iKzA1w6dwLGhgfLJrYKFGG?= =?Windows-1252?Q?cAIRYypi0lhlI5DGMoIK16Gl0rZ1MGfcxbsLEhxxWCRGjND1tMl8cdCN?= =?Windows-1252?Q?QWHA/fa5kW+05XpwUb7/FIBpBoQHTmXZ8abmA/P05m1TvfiP7+k2bQuj?= =?Windows-1252?Q?UP/sbxih3jF9pczfSkHxNCgl9n1cKbclaouVyME6CV+Aja4gRWGDpfMs?= =?Windows-1252?Q?H0IIn3C0rchl35N8gKZQfEuuHKOeQPP6mcXgySyPqbJ7ptuUIcM4T1gO?= =?Windows-1252?Q?QiZuXuRoTlTGQ/V9HO94fEY6YBwuru3hJBADUj+l3tUFAA0akaMZIBQ5?= =?Windows-1252?Q?cTkOw36dhDQAx1WQ1BJ0oG498PUsnnmc4c4putbuxai1UJjLfJfiPCUd?= =?Windows-1252?Q?AK3txkuuARehVURU0ivrbG2f6sZGo6Rbf/GwsyZkpYYtvGswnHcltsdu?= =?Windows-1252?Q?gpRNmtBP92sRAfUKdTQx2QgyjI0f/4RpPp9Tf59vgLEQvtdASBlyPalp?= =?Windows-1252?Q?Y8W0G2MBQ9byOT4e9MZo9RJjg8qb/L8iTinqieZ66NDLzGblzEwparO5?= =?Windows-1252?Q?tYLAjZ1iiC9YFYKxAPHByhEN0DoNxJM2B8f2DnHFUufdSydKG1G9tD2L?= =?Windows-1252?Q?HBDrKEJoCcaudSPSN1BbyPJelLzAvoTfC28T1jtVMUnU0GAV6z2d9gsX?= =?Windows-1252?Q?gnWAI09+J72teoANMROjkjinpyb2Wb5EQOy2GGxqoO4lzuo9oGQ9q6Ji?= =?Windows-1252?Q?KgimnaLDKA9wbvUXbGyzwHBzrqyfAtVcaInIhZNyE7qGEh6c2Q4/wP5K?= =?Windows-1252?Q?0/vadiGCgpHbHelMviPGnhD+LtDBYiJMzds=3D?= Content-Type: multipart/alternative; boundary="_000_PA6PR83MB06006EF9C5B9937472046D28DC52APA6PR83MB0600EURP_" MIME-Version: 1.0 X-OriginatorOrg: github.com X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: PA6PR83MB0600.EURPRD83.prod.outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: 6287f7be-5041-48f5-e3fa-08de8e5f4126 X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Mar 2026 13:21:29.8863 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47 X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: JN3JjFiJ3KzujdsPfouk6H4IJkeE3e8P12kQ9EPSs3i2LigRmOjLOE8P32K4CUXDmbDa62RYL1a6/g3idHII+g== X-MS-Exchange-Transport-CrossTenantHeadersStamped: AS4PR83MB0524 Message-ID-Hash: 77R6MOGIO6ITCCIKNAXI4Z25CTMEWIRR X-Message-ID-Hash: 77R6MOGIO6ITCCIKNAXI4Z25CTMEWIRR X-MailFrom: felixreda@github.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.9rc6 Precedence: list Subject: =?utf-8?q?=5Bai-control=5D_Re=3A_Proposal=3A_AI_Preference_Attachments_for_S?= =?utf-8?q?ource_Code_and_VCS_=28Seeking_Co-editors=29?= List-Id: AI Control Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --_000_PA6PR83MB06006EF9C5B9937472046D28DC52APA6PR83MB0600EURP_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Dear Thomas, Thanks a lot for driving this work forward. I had the opportunity to commen= t on an early draft of this proposal and I support its approach. Software c= ode has particularities that require a different approach from robots.txt, = as developers rarely have access to the robots.txt file of the domains thro= ugh which their code is distributed. At the same time, I really appreciate = that this proposal focuses on the attachment mechanism and is open to adopt= ing any vocabulary of preferences that this working group is ultimately goi= ng to agree on. As regards to the question of the working group charter, I am not 100% sure= , because the description of the charter supports this work ("The Working G= roup will focus on attaching preferences to content either by including pre= ferences in content metadata or by signaling preferences using the protocol= that delivers content"), while the deliverables are more narrowly tailored= to "means of attaching or associating those preferences with content in IE= TF-defined protocols and formats=93. Perhaps the chairs can provide clarity= here. Either way, without wanting to distract one bit from the important work on = the vocabulary, I hope members of this group with an interest in software p= references will engage with the proposal and help develop it. Best, Felix From: Thomas Aynaud Date: Monday, 30. March 2026 at 09:54 To: ai-control@ietf.org Subject: [EXTERNAL] [ai-control] Proposal: AI Preference Attachments for So= urce Code and VCS (Seeking Co-editors) Hi everyone, As the working group continues to make excellent progress on draft-ietf-aip= ref-attach, we=92ve been looking closely at how to apply these mechanisms t= o software source code and version control systems. In Section 1.3.1 of the current attachment draft, it is noted that embeddin= g preferences directly into content is highly effective but requires format= -specific methods. We believe source code fits precisely into this scope. A fundamental difference between source code and other media is how copyrig= ht owners traditionally communicate usage rights. In the software ecosystem= , there is a decades-long precedent of declaring reuse permissions inside t= he artifact itself (e.g., via LICENSE files or SPDX headers). If an AI preference is declared exclusively via the Content-Usage HTTP head= er (Section 2) or robots.txt (Section 3), it does not follow this establish= ed developer workflow. Furthermore, because code is distributed via git clo= ne, package managers, or archive downloads, transport-layer metadata is inh= erently stripped. The preference vanishes the moment the repository is clon= ed, or used in any of the various phases of software development, not to me= ntion vendoring. To bridge this gap, Software Heritage and partners that are involved in the= CodeCommons project (see https://codecommons.org) have drafted a specifica= tion for an in-repository attachment mechanism that survives at rest. Working Specification: https://gitlab.softwareheritage.org/teams/codecommon= s/cc-public-resources/-/tree/main/specifications/aiprefs We are bringing this to the list with two goals: 1. To get the working group's initial feedback on the technical approach of= an in-repo file constraint. 2. To ask if this software-specific attachment mechanism is within the scop= e of the IETF working group, and if so, whether anyone with experience auth= oring IETF drafts would be interested in co-editing this document with us. = We have the core specification mapped out in GitLab, but we would greatly a= ppreciate a co-editor to help translate this into the formal IETF XML/RFC f= ormat for an official -00 submission. If the chairs conclude that this prop= osal is outside the scope of the AIPREF working group, we would appreciate = advice on appropriate venues to advance this specification. Thanks for your time and the great work on the core drafts so far, -- Thomas Aynaud -- ai-control mailing list -- ai-control@ietf.org To unsubscribe send an email to ai-control-leave@ietf.org --_000_PA6PR83MB06006EF9C5B9937472046D28DC52APA6PR83MB0600EURP_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
Dear Thomas,

Thanks a lot for driving this work forward. I had the opportunity to commen= t on an early draft of this proposal and I support its approach. Software c= ode has particularities that require a different approach from robots.txt, = as developers rarely have access to the robots.txt file of the domains through which their code is distribu= ted. At the same time, I really appreciate that this proposal focuses on th= e attachment mechanism and is open to adopting any vocabulary of preference= s that this working group is ultimately going to agree on.

As regards to the question of the working group charter, I am not 100% sure= , because the description of the charter supports this work ("The Work= ing Group will focus on attaching preferences to content either by includin= g preferences in content metadata or by signaling preferences using the protocol that delivers content"), = while the deliverables are more narrowly tailored to "means of attachi= ng or associating those preferences with content in IETF-defined protocols = and formats=93. Perhaps the chairs can provide clarity here.

Either way, without wanting to distract one bit from the important work on = the vocabulary, I hope members of this group with an interest in software p= references will engage with the proposal and help develop it.

Best,
Felix

From: Thomas Aynaud <thomas.aynaud@inria.fr>
Date: Monday, 30. March 2026 at 09:54
To: ai-control@ietf.org <ai-control@ietf.org>
Subject: [EXTERNAL] [ai-control] Proposal: AI Preference Attachments= for Source Code and VCS (Seeking Co-editors)

Hi everyone,

As the working group continues to make excellent progress on draft-ietf-aip= ref-attach, we=92ve been looking closely at how to apply these mechanisms t= o software source code and version control systems.

In Section 1.3.1 of the current attachment draft, it is noted that embeddin= g preferences directly into content is highly effective but requires format= -specific methods. We believe source code fits precisely into this scope.
A fundamental difference between source code and other media is how copyrig= ht owners traditionally communicate usage rights. In the software ecosystem= , there is a decades-long precedent of declaring reuse permissions inside t= he artifact itself (e.g., via LICENSE files or SPDX headers).

If an AI preference is declared exclusively via the Content-Usage HTTP head= er (Section 2) or robots.txt (Section 3), it does not follow this establish= ed developer workflow. Furthermore, because code is distributed via git clo= ne, package managers, or archive downloads, transport-layer metadata is inherently stripped. The preference= vanishes the moment the repository is cloned, or used in any of the variou= s phases of software development, not to mention vendoring.

To bridge this gap, Software Heritage and partners that are involved in the= CodeCommons project (see https://codecommons.org) have drafted a specification for an in-re= pository attachment mechanism that survives at rest.

Working Specification: https://gitlab.softwareheritage.org/teams/codecommons/cc-public-resources/-= /tree/main/specifications/aiprefs

We are bringing this to the list with two goals:

1. To get the working group's initial feedback on the technical approach of= an in-repo file constraint.
2. To ask if this software-specific attachment mechanism is within the scop= e of the IETF working group, and if so, whether anyone with experience auth= oring IETF drafts would be interested in co-editing this document with us. = We have the core specification mapped out in GitLab, but we would greatly appreciate a co-editor to help transla= te this into the formal IETF XML/RFC format for an official -00 submission.= If the chairs conclude that this proposal is outside the scope of the AIPR= EF working group, we would appreciate advice on appropriate venues to advance this specification.

Thanks for your time and the great work on the core drafts so far,

--
Thomas Aynaud

--
ai-control mailing list -- ai-control@ietf.org
To unsubscribe send an email to ai-control-leave@ietf.org
--_000_PA6PR83MB06006EF9C5B9937472046D28DC52APA6PR83MB0600EURP_--