Re: [Last-Call] [Ext] Re: [httpapi] Last Call: <draft-ietf-httpapi-rfc7807bis-04.txt> (Problem Details for HTTP APIs) to Proposed Standard

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Amanda,

> On 10 Nov 2022, at 1:55 pm, Amanda Baber <amanda.baber@xxxxxxxx> wrote:
> 
> [AB] While we don't have an obvious mechanism to provide stable URLs with this level of precision today, we do have the intention to provide permanent links to registries and registrations in our roadmap for our next-generation registry system, currently under development. Within our current system,  we can't provide links to specific registrations, and cannot guarantee that links to registries within a registry group (e.g. https://www.iana.org/assignments/core-parameters#content-formats within the CORE Parameters group) won't end up defaulting to the larger group (https://www.iana.org/assignments/core-parameters). With that said, if there are unique considerations for individual registries, please talk to us about potential interim approaches until we have something holistic in place.

That's great, thanks. 

It might be good to have a community discussion of some form about the requirements and proposed design of those changes, especially if people are going to do things like rely on those identifiers to be stable.  What's the best forum for that? I was thinking of submitting a draft with some thoughts to GENDISPATCH - is that workable?

Cheers,


--
Mark Nottingham   https://www.mnot.net/

-- 
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call



[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux