> On 29 Jan 2024, at 8:04 pm, Dan Garcia Carrillo <garcia...@uniovi.es> wrote: > >> - I was a bit surprised that the spec didn't update the coap spec to put the >> new resource under /.well-known/coap/eap -- but that's up to the authors. > > Some time ago we reach to the well-known community asking about this. > > Our initial proposal was /.well-known/eap. > The suggestion was, as it is CoAP-specific they suggested coap-eap, which was > fine for us. > Nonetheless, your proposal is interesting and we would like to ask you how to > proceed with this. > Since all we see in the IANA page > (https://www.iana.org/assignments/well-known-uris/well-known-uris.xhtml) are > direct suffixes of /.well-known/, but we haven't seen how to define and > specify a suffix of a suffix. In this case, a suffix of /.well-known/coap
The only entry in the registry would be /coap -- it's up to the COAP community as to how that name space is managed. You could update the COAP RFC that registers it, or you could establish a registry to manage the name space. See eg 'masque', 'cmp', and 'brski' in the registry. >> - It would be good if the specification would identify the URI scheme(s) >> that it can be used with (per 8615 s 3). >> > This would follow the previous point. If you could, please indicate how to > proceed with this specific procedure, would be great. Just specify what URI schemes the name is expected to be used with -- if it's just coap, say that. If you don't specify anything, it's presumed that it's' meaningful for all URL schemes. Cheers, -- Mark Nottingham https://www.mnot.net/ _______________________________________________ Ace mailing list Ace@ietf.org https://www.ietf.org/mailman/listinfo/ace
