Thank you for the comments. Mark Nottingham <[email protected]> wrote: >> On 4 Aug 2020, at 10:07 pm, Michael Richardson <[email protected]> wrote: >> >> >> Hi Mark, this concerns some desired changes to /.well-known/est. >> >> Specifically, to move the things we did in anima-bootstrapping-keyinfra out >> of /.well-known/est into a new /.well-known/brski. >> The WG has not concluded to do this as yet, as the above document has passed >> IESG review and is in MISREF at the RFC-EDITOR. >> >> The thread starts at: >> https://mailarchive.ietf.org/arch/msg/anima/jjusQdqzS3G4WbczolCxF0_YmQQ/ >> >> I have prepared sample changes which I'd like your opinion on. >> >> 1) I am now registering /.well-known/brski
> Sure, we have a process for that ;) Easiest thing to do is to create an
issue here:
> https://github.com/protocol-registries/well-known-uris
>> 2) I no longer need /.well-known/est to point to the new document.
Should I
>> say this?
> Yes. Best thing to do is to include it in the request above.
>> 3) Am I creating the /.well-known/brski Registry correctly?
>> I didn't see any other WK that have sub-registries.
> How you manage the namespace under your well-known URI is totally up to
> you. That looks reasonable to me, although if you don't think it's
> likely there will be additions for a while, you could just say 'update
> this document to register additional paths'.
We have new drafts that we are considering adopting now.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | IoT architect [
] [email protected] http://www.sandelman.ca/ | ruby on rails [
signature.asc
Description: PGP signature
_______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
