[Asdf] draft-ietf-asdf-sdf: preparing -18

[Carsten Bormann <[e-mail]>]

On github, there are three issues outstanding that are actionable against draft-ietf-asdf-sdf-17:

https://github.com/ietf-wg-asdf/SDF/issues/147

This is purely editorial: Get some more consistency on where we use typewriter fonts.

https://github.com/ietf-wg-asdf/SDF/issues/148

This called for an example on how JSON Pointer syntax (and the fragment syntax we carry JSON pointers in) sometimes requires some encoding.

https://github.com/ietf-wg-asdf/SDF/issues/149

This called for a more complete security considerations section.

We now have pull requests for each of these issues:

#147 ➔
https://github.com/ietf-wg-asdf/SDF/pull/153
(hundreds of tiny changes, quite boring)

#148 ➔
https://github.com/ietf-wg-asdf/SDF/pull/152
(a new paragraph explaining and giving the example, improved referencing)

#149 ➔
https://github.com/ietf-wg-asdf/SDF/pull/151
(security considerations that are, if you ask me, quite comprehensive now)

If you want, you can look at these now and provide some feedback (on github or here).

We are planning to submit a -18 that merges these pull requests tomorrowish.
That should then complete the processing of our WGLC and post-WGLC feedback.
You of course can do any review of these latest changes in the new I-D as well.

Grüße, Carsten