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

Hi Collin,

As a top level comment, I think you might want to review RFC 7595 again,
especially section 3, for its comments on what makes a good, long live URI
scheme.

I also think it might help the mailing list members evaluate the proposal
and provide feedback if you could give a bit more detail on how you
anticipate this URI being used.  What real time systems do you anticipate
producing it and consuming it and to what purpose? You say the scheme
"allows the passing of JSON data for streaming words, video data, or images
between generative A.I. entities.", but presumably this refers to the
system itself.  Is the role of the identifiers within the passed data or as
a set references to the data?

Unpacking a bit more, it is unclear why  a URI related to AI would be
limited to generative AI; with that limit, a more constrained name might be
useful.

For this:  <type-of-generative-ai> is there an existing registry of
generative AI types you plan to reference?  If you are maintaining a list,
where would it be available to those wanting to mint URIs under this scheme?

Similar questions occur to me for both <specific-model> and <action>; are
these registered tokens (to foster common understandings) or freeform
strings chosen by the person minting the URI?

None of the productions of above are defined in a grammar like ABNF, and
that would be useful for those who will encounter and parse them.

There are no security considerations given, and this is required by RFC
7595, even for provisional registrations.

regards,

Ted Hardie

On Sat, Oct 7, 2023 at 6:37 AM Collin Paran <collin@professai.com> 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, collin@professai.com
>
> *Author/Change Controller:*
>
>    - Collin Paran, collin@professai.com
>
> *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 `uri-review@ietf.org` mailing list and other relevant
> forums as appropriate.
>
> Thank you for your time and consideration.
>
> Warm regards,
>
> Collin Paran
> collin@professai.com
>
> _______________________________________________
> Uri-review mailing list
> Uri-review@ietf.org
> https://www.ietf.org/mailman/listinfo/uri-review
>