[Anima] possible last minute changes to anima-bootstrapping-keyinfra (was Re: Handling of endpoint path names (from BRSKI-AE discussion today))

[Michael Richardson <[e-mail]>]

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
2) I no longer need /.well-known/est to point to the new document.  Should I
   say this?
3) Am I creating the /.well-known/brski Registry correctly?
   I didn't see any other WK that have sub-registries.

This URL works:
  https://ietf.org/rfcdiff?url1=draft-ietf-anima-bootstrapping-keyinfra-41&url2=https://raw.githubusercontent.com/anima-wg/anima-bootstrap/brski-est-rename/dtbootstrap-anima-keyinfra.txt

But, includes a few small typos which were sent to the RFC-editor.

This should be the better DIFF:
  https://ietf.org/rfcdiff?url1=draft-ietf-anima-bootstrapping-keyinfra-42&url2=https://raw.githubusercontent.com/anima-wg/anima-bootstrap/brski-est-rename/dtbootstrap-anima-keyinfra.txt

but the DT/cache refuses to believe -42 exists yet, but maybe in 30 minutes
it will be okay.

--
Michael Richardson <[e-mail]>, Sandelman Software Works
 -= IPv6 IoT consulting =-