Re: [Uri-review] Request for Review and Registration of New URI Scheme "ai"

["Martin J. Dürst" <[e-mail]>]

Hello Collin, others,

A few more comments on top of Ted's, written in a somewhat more direct 
style.

It's unclear to me why AI data is in any way special. Protocols such as 
HTTP or WS don't care what data they carry, and data shouldn't care what 
protocols it's been carried by. As an example, Web Sockets is used (I 
guess) for search results, for stock price data, for gaming data, and so 
on, but there's no need for anything other than a ws: scheme. Same for http.

On the other hand, if AI would surface the need for a new protocol, 
there's no need to limit this to AI; there's a high chance that such a 
protocol may be useful for other applications, too. In that case, the 
scheme name "ai" would be inappropriate.

Your scheme proposal doesn't contain any kind of authority information 
(that would usually be some domain name). So it's unclear how data could 
be made available by multiple parties, or how the party making the data 
available could be identified. This is different both from 
"type-of-generative-ai" and from "specific-model".

[Of course, it might be the case that this is only intended for the use 
by a single party providing data, but that's not what URI schemes are for.]

If indeed there is a need for an application-specific URI scheme for AI, 
that may not be limited to your proposal. It would therefore be 
premature to use such a short scheme name for this specific proposal; 
maybe "wsai:" or "aiws:" or something along these lines would be more 
appropriate (assuming that there's a need for an application-specific 
URI scheme at all, which I strongly doubt (see my first point)).

Regards,   Martin.

On 2023-10-07 14:34, Collin Paran wrote:
> Dear IANA and URI Review Mailing List Members,
> 
> I am writing to request a review and registration of a new URI Scheme, "ai", designed for facilitating communication in generative A.I. applications. The scheme is inspired by WebSockets and allows the passing of JSON data for streaming words, video data, or images between generative A.I. entities.
> 
> Please find below the URI Scheme Registration Template as per the guidelines provided in RFC 4395.
> 
> URI Scheme Name: ai
> 
> Status: Provisional
> 
> URI Scheme Syntax:
>      * `ai://<type-of-generative-ai>/<specific-model>/<action>?<parameters>`
> URI Scheme Semantics:
>      * The `ai` scheme is aimed at enabling real-time or near-real-time communication for streaming data among generative Artificial Intelligence (A.I.) applications and protocols.
> Encoding Considerations:
>      * UTF-8 encoding for multilingual support and binary format for multimedia data encapsulated in JSON objects.
> Applications/Protocols that use this URI scheme name:
>      * Generative A.I. applications and protocols requiring real-time or near-real-time communication for streaming data.
> Interoperability Considerations:
>      * Compatibility with existing WebSocket implementations and a standard JSON format for data communication.
> Security Considerations:
>      * Usage of Artificial Intelligence Secure (AIS) which is also interoperable with wss (WebSocket Secure) for encrypted communication and authentication mechanisms for authorized access.
> Contact:
>      * Collin Paran, [e-mail] mailto:[e-mail]
> Author/Change Controller:
>      * Collin Paran, [e-mail] mailto:[e-mail]
> References:
>      * Pending public release.
> I am looking forward to receiving feedback from the community and I am open to making any necessary revisions to ensure the `ai` scheme aligns with the established guidelines and standards. I am also eager to engage in discussions on the `[e-mail]` mailing list and other relevant forums as appropriate.
> 
> Thank you for your time and consideration.
> 
> Warm regards,
> 
> Collin Paran
> [e-mail]
>   
> 
> 
> _______________________________________________
> Uri-review mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/uri-review