2022-03-08 Technical WG Agenda and Notes

Update on preliminary discussion with the RFC Independent Stream Editor

• BCP (Best Current Practice) 190 (RFC 8820)
• Conflict with reserving path "prefix"
• Conflict with reserving query string

On 04.03.22 06:56, Independent Submissions Editor (Eliot Lear) wrote:
The question really is... is an web server or client supposed to
behave in any special way when they see ark: somewhere buried in a
URL?  This is precisely what .well-known was meant to protect against.
...
I want to go into more detail here.  The point of BCP 190 is to preserve
namespaces to the owner of an origin.  That is- you don't get to
structure them if you are not the owner.  That includes queries.  The
exception we have for that is .well-known.  This is why I am very
concerned about the current state of your draft.

Some initial thoughts (jak's). This means that the IETF might not allow example.org/ark:12345/67890 and the ?info inflection unless they were expressed as something like

     example.org/.well-known/ark/12345/67890       and

     example.org/.well-known/ark-info/12345/67890

I (jak) don't think it means that one site, eg, n2t.net, couldn't recommend publishing as

     n2t.net/ark:12345/67890

and letting it redirect to local services that use the .well-known/ark... convention.

New spec transition planning

• New spec blog post draft – go ahead anyway, or talk about new spec transition independent of the RFC process?