[art] Re: [Uri-review] Review Request] draft-sogomonian-ai-uri-scheme — AI URI Scheme for Autonomous Systems

Arm Arm <waterbottling@icloud.com> Tue, 28 October 2025 15:56 UTC

Return-Path: <waterbottling@icloud.com>
X-Original-To: art@mail2.ietf.org
Delivered-To: art@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 04E497D82329 for <art@mail2.ietf.org>; Tue, 28 Oct 2025 08:56:04 -0700 (PDT)
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, 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, MIME_QP_LONG_LINE=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=icloud.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 opiwI8xyHb3h for <art@mail2.ietf.org>; Tue, 28 Oct 2025 08:56:02 -0700 (PDT)
Received: from outbound.mr.icloud.com (p-west2-cluster2-host1-snip4-3.eps.apple.com [57.103.68.186]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id F0D6A7D82310 for <art@ietf.org>; Tue, 28 Oct 2025 08:56:01 -0700 (PDT)
Received: from outbound.mr.icloud.com (unknown [127.0.0.2]) by p00-icloudmta-asmtp-us-west-2a-100-percent-2 (Postfix) with ESMTPS id A0142180016B; Tue, 28 Oct 2025 15:55:51 +0000 (UTC)
Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=icloud.com; s=1a1hai; bh=oNFfrvIIYyNThi0rvsxCn+M90e7kHUb1/Zgt9djFnng=; h=Content-Type:From:Mime-Version:Subject:Date:Message-Id:To:x-icloud-hme; b=TcNkZY+T+ex1Y7K4qd+ulA0B5TbMf3zCdJIXDPd1TBS37hBNy/gkmios4l9Mmf8c1NYuOhmTFLz0vM0Nh8FRMDSS8HEu5GmgwX22CqWzf2SjdRfqHwIrVEO2zyspKgsYhGsD6LwhwMzoAqVJeSE6I0McSIvea2RvYSuLi1ThmszW6OE3ohEsB1m8cCwjqKjZLGGWm2YW3HWMZuzK0x6kf0u1X/5j9JVyY/CKrwvZ0hGtmwzzDUPuzIob3D923GOBPXNypeifRHs9fu7ceRWfzLMT1jHpWx/C/XfEygnjLIp78gHFYRm8D2UHEkdn9IMNU2zjp62d/BPPqous+VCa9A==
Received: from smtpclient.apple (unknown [17.57.152.38]) by p00-icloudmta-asmtp-us-west-2a-100-percent-2 (Postfix) with ESMTPSA id EDC781801BE7; Tue, 28 Oct 2025 15:55:50 +0000 (UTC)
Content-Type: multipart/alternative; boundary="Apple-Mail-685EE659-C015-44A7-9EAE-02E4545713AD"
Content-Transfer-Encoding: 7bit
From: Arm Arm <waterbottling@icloud.com>
Mime-Version: 1.0 (1.0)
Date: Tue, 28 Oct 2025 08:55:39 -0700
Message-Id: <BC61CF1B-80A4-4D51-B119-33BB1982D74F@icloud.com>
References: <75F6CF00-9208-4CEA-BED6-A2B28EB80C46@icloud.com>
In-Reply-To: <75F6CF00-9208-4CEA-BED6-A2B28EB80C46@icloud.com>
To: Rich Salz <rsalz=40akamai.com@dmarc.ietf.org>
X-Mailer: iPhone Mail (22G86)
X-Proofpoint-GUID: u0fZbnk8B1bgs9CeINyDsH_40cgO8I9d
X-Proofpoint-ORIG-GUID: u0fZbnk8B1bgs9CeINyDsH_40cgO8I9d
X-Proofpoint-Spam-Details-Enc: AW1haW4tMjUxMDI4MDEzNSBTYWx0ZWRfX61E6sTcXVNBe CKPYe30sl/3wcAuFiYmAEevkumckyO0PUlXRf/4cHN8lcp5PzwhBbs3CNLgqszTTK1mcHI6zCxu PmhCqalhNobuWvn5e51L6RJe40tL0wIBBOUcJXllHdvgPIjFXxbSnwou/bLHfFqAzk8daDcA/4i 7uhqDRYgCfbY/e461Tav+5peAxfXQte7ei+aTWcKA4zu4ZGaOZ1u3a+EIt/Crg5uBDypv2zVrUT VVjvnwZCQr0ju8DSX4PnFu0qNasNOTh03o/96UBRMywCQdMxLQzmS6hO0qs/ULKeIdr+RIF3Q=
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1121,Hydra:6.1.9,FMLib:17.12.80.40 definitions=2025-10-28_06,2025-10-22_01,2025-03-28_01
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 phishscore=0 spamscore=0 bulkscore=0 mlxlogscore=999 malwarescore=0 suspectscore=0 adultscore=0 clxscore=1015 mlxscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.22.0-2506270000 definitions=main-2510280135
X-JNJ: AAAAAAABH0NsfPGsL2AaaeMD54Y+qjSbEpKKQCmHPSs1D1nnaJ3NRKA1W6xKynD+phnEvj2NDjbgNGuiAq5WQigUd/uJVKFCiefVruHM1hvEwsj+rFMeo6LYLCyP91d8LQp5pwWD7UL6+mj30+o7Wuayebcg+FxPZ3j/V4xXJ/YOgaVqeinPS7rv4l5PglvEDqGeFcQY1uo4U6nPyxopcWTse8MFBjZkbP/wOP/McAxqn7XepqY5KT5cf+Ji0/l3NRHfvxAYQeO4dfpMUcqQk89IJWpIV6Op+5HEyrGrKZ8SPqDLdZ+Fq/ShOVdkDOZEQlNORXd+mYn6qOSrcfatg+VHcho9hFOnE5dSTRyGmYz4TLKYUcjhWaQKNeWYiKUfMMJ69Ojt4xjiGA8wHii7ykcdikWe0JGzFFaERH3L8AYOfJl5lJjbu/LR7MRgUN3IhZVT6Noyr8paPAXIEUtugtRcd8zQBye0iIVEfDgkBrqueiaHnWRfUW7o6hmduJ3sMkWKRCah19TkQ5KpI6JkKnt3ptzQq9pOn8oOrm2hEFv1EtadXyC9/WzDDZRY+iu0iyrHtJRMavDvS8K2980VtODnU6Px6y9VG9jtZCw34hgzDfJBFZGwfArta6orD5XkdbnakWHlvJlKEL2Qy4Cod/wxpT6MlC5WUXTR7vXYVsiYwU97CfXJFgt1UOXL3na2UWFQa6DSK8BbBQ==
Message-ID-Hash: 4WZPS2GGYSBMV2LDO3MACBQYYZW3DZRI
X-Message-ID-Hash: 4WZPS2GGYSBMV2LDO3MACBQYYZW3DZRI
X-MailFrom: waterbottling@icloud.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-art.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: art <art@ietf.org>, uri-review@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [art] Re: [Uri-review] Review Request] draft-sogomonian-ai-uri-scheme — AI URI Scheme for Autonomous Systems
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/ss-g3OHTtwHwyBDl0cKQPWAMIWY>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Owner: <mailto:art-owner@ietf.org>
List-Post: <mailto:art@ietf.org>
List-Subscribe: <mailto:art-join@ietf.org>
List-Unsubscribe: <mailto:art-leave@ietf.org>

Hi all,



Thank you very much for the valuable and constructive feedback on my draft. I greatly appreciate the time and expertise each of you contributed.



Based on your comments, I am now preparing:



✅ A revised version of the URI Scheme draft

✅ A companion document titled:

“AIIP – Artificial Intelligence Internet Protocol”

which will define:

• Protocol semantics and authority resolution

• Message interaction and content negotiation

• Security, provenance, and interoperability requirements

• Alignment with DNS authorities

• Autonomous systems/robotics use cases



✅ Expanded and corrected examples, including proper authority formatting

✅ Clarified I18N handling and DNS naming rules

✅ Naming analysis including longer scheme options (e.g., aiip) to avoid collisions



IETF submission status update:

The submission system is currently temporarily closed during the IETF meeting week. I will upload the updated versions as soon as submissions reopen after November 1, 2025, per datatracker notice.



Your guidance is helping ensure this work follows community expectations and established best practices — thank you again for helping strengthen this foundation.



If you have any additional ideas or concerns as the architecture document takes shape, I would be very happy to incorporate them.



Best regards,

Aram Sogomonian

Author – AIIP / AI URI Scheme

waterbottling@icloud.com


Sent from my iPhone

> On Oct 28, 2025, at 07:42, Arm Arm <waterbottling@icloud.com> wrote:
> 
> 
> 
> 
> Hi Rich,
> 
> Thank you again for the very helpful direction.
> 
> I agree that the protocol definition must come before reserving a URI prefix.
> I am currently preparing an updated companion document that will:
> 
> 
> define the AIIP protocol itself: message format, invocation model, security and provenance requirements
> rename the document to “Artificial Intelligence Internet Protocol (AIIP)”
> include HTTPS gateway integration, robots/autonomous system invocation, and provenance of execution
> 
> 
> 
> Once that is published and reviewed, I will revise the URI scheme draft to align with the protocol semantics before requesting provisional registration.
> 
> Thank you again for the constructive feedback and guidance.
> 
> Best regards,
> Aram Sogomonian
> 
> Sent from my iPhone
> 
>>> On Oct 28, 2025, at 07:17, Salz, Rich <rsalz=40akamai.com@dmarc.ietf.org> wrote:
>>> 
>> 
>> You are correct that this version does not yet define the AIIP protocol. I am currently preparing a companion document titled “Architecture for the Artificial Intelligence Internet Protocol (AIIP)”
>> 
>> Yes, I looked at that draft before I wrote my earlier email.  “Architecture” doesn’t seem like the best word to describe a protocol.  Consider dropping the first two words from the current title.
>> 
>> It seems premature to ask for a URI prefix without a full definition of the protocol.