Re: agent draft updated

Indeed, independent submissions cannot normally create new registries.
That's OK, though, because you don't actually need them. The purpose of the
independently-submitted information document would be to document the
existing protocol, both for the benefit of the community already using it
and as a starting point for standardization work. Such a document can
simply list the code points already used or reserved (the tables already in
your draft) and need not actually create any registries. The registry
creation can wait for publication of the eventual IETF-stream document.

-- Jeff

On Tue, Aug 22, 2023 at 10:43 PM Damien Miller <[email protected]> wrote:

> On Wed, 16 Aug 2023, Jeffrey Hutzelman wrote:
>
> > I would suggest that before standardizing the agent protocol, we should
> > first document the existing one. IMHO this is best done as an
> informational
> > RFC submitted via the independent submission stream
> > (see https://www.rfc-editor.org/about/independent/).
> > Once that is done, if there is any new work to do, and you are willing to
> > cede change control to the IETF, then it would seem appropriate to do a
> > follow-on document, perhaps on the standards track. I don't think the SSH
> > community has the energy to form a new working group, but we've had good
> > luck on this mailing list with using the process for non-wg documents.
>
> Thanks, though maybe I'm misinterpreting the guidelines for independent
> submission, but the text mentions that this process is not suitable for
> drafts that require IANA changes.
>
> This draft definitely does. Is that a problem?
>
> -d