Re: [httpapi] Towards a hal+json RFC

The media type registration for application/vnd.hal+json already exists here https://www.iana.org/assignments/media-types/application/vnd.hal+json I do not believe it would be appropriate to include it again in the RFC.  The reason to include in the RFC, would be if there was a desire to register a new media type in the standards tree. E.g. application/hal+json.  However, Independent Submissions track documents cannot be used to do Standard tree registrations.

If there is a desire to register application/hal+json in the standards tree, we will need to wait until this document gets approved https://www.ietf.org/archive/id/draft-ietf-mediaman-standards-tree-00.html

And yes, next steps are to email rfc-ise@rfc-editor.org<mailto:rfc-ise@rfc-editor.org> to start the independent submissions process.

Darrel

________________________________
From: httpapi <httpapi-bounces@ietf.org> on behalf of Mike Kelly <mikekelly321@gmail.com>
Sent: Friday, November 3, 2023 7:32 AM
To: Kévin Dunglas <kevin@dunglas.fr>
Cc: Darrel Miller <Darrel.Miller@microsoft.com>; httpapi@ietf.org <httpapi@ietf.org>
Subject: Re: [httpapi] Towards a hal+json RFC

Hi Kevin, I don’t know why but I assumed the media type registration was a given and that section is intended for other considerations. Am I mistaken?

Sent via Superhuman iOS<https://sprh.mn/?vip=mikekelly321@gmail.com>

On Fri, Nov 3 2023 at 11:14 am, Kévin Dunglas <kevin@dunglas.fr<mailto:kevin@dunglas.fr>> wrote:
Hi,

I'm glad to see that HAL (which is in our "API Platform" framework by the way) will finally be a RFC!

Regarding IANA considerations, shouldn't you mention the new media type in this section? The corresponding registry is https://www.iana.org/assignments/media-types/media-types.xhtml.

Cheers,

On Wed, Oct 4, 2023 at 1:39 PM Mike Kelly <mikekelly321@gmail.com<mailto:mikekelly321@gmail.com>> wrote:
I figured it out and completed the remaining sections (I've assumed for now that there are no IANA considerations, which I assume I can ammend if this is corrected during the process?). Latest version is here:

https://datatracker.ietf.org/doc/draft-kelly-json-hal/10/

Assuming my assumption about IANA considerations is correct should I fire an email to rfc-ise?

Cheers,
M

On Tue, Oct 3, 2023 at 3:28 PM Mike Kelly <mikekelly321@gmail.com<mailto:mikekelly321@gmail.com>> wrote:
Alright. What sort of “security considerations” apply to a media type like hal? Processing is already covered by json?

On Tue, 3 Oct 2023 at 14:52, Darrel Miller <Darrel.Miller@microsoft.com<mailto:Darrel.Miller@microsoft.com>> wrote:
Ok, so step 1 is to have an ID.  Which you have here https://datatracker.ietf.org/doc/html/draft-kelly-json-hal

The next step is to email rfc-ise@rfc-editor.org<mailto:rfc-ise@rfc-editor.org> with the information listed on this page https://www.rfc-editor.org/about/independent/  However, I see two things that need to be taken care of first.  One is your security considerations needs to be completed and the other is we need to figure out what needs to be done about the IANA section.  If you work on the Security Considerations, I'll do some reading about IANA requirements.

Darrel

________________________________
From: Mike Kelly <mikekelly321@gmail.com<mailto:mikekelly321@gmail.com>>
Sent: Tuesday, October 3, 2023 9:01 AM
To: Darrel Miller <Darrel.Miller@microsoft.com<mailto:Darrel.Miller@microsoft.com>>
Cc: httpapi@ietf.org<mailto:httpapi@ietf.org> <httpapi@ietf.org<mailto:httpapi@ietf.org>>

Subject: Re: [httpapi] Towards a hal+json RFC

Alright sounds good to me. What do I need to do right now to get this started? :)

On Tue, 3 Oct 2023 at 13:59, Darrel Miller <Darrel.Miller@microsoft.com<mailto:Darrel.Miller@microsoft.com>> wrote:
This isn't a high traffic list and I think there are probably a few people on this list that would be interested in discovering more about the independent submissions process, so I have no concerns if we keep the discussions on list.  But feel free to email directly too.

And just as a caveat, I haven't gone through this process before, so we will be learning together [🙂]

Darrel

________________________________
From: Mike Kelly <mikekelly321@gmail.com<mailto:mikekelly321@gmail.com>>
Subject: Re: [httpapi] Towards a hal+json RFC

Hey Darrel, thanks so much for this. Very clear. Yes it does sound like independent submission would be more appropriate. I think it also suits my sensibilities better..! That being the case would it be better to this off the mailing list as I could do with your guidance on how this process works.

Cheers,
M

--
httpapi mailing list
httpapi@ietf.org<mailto:httpapi@ietf.org>
https://www.ietf.org/mailman/listinfo/httpapi