[Rfc-markdown] kramdown-rfc updates from 1.6.38 to 1.6.41

[Carsten Bormann <[e-mail]>]

Since July’s 1.6.37, there have been a number of small fixes and 
improvements on kramdown-rfc.
Here are some quick release notes:

1.6.41: Generate anchors for auto-generated references sections

So you can link to the auto-generated references sections in your 
document, these now have anchors:

sec-normative-references
and
sec-informative-references

(sec stands for section).
These anchors currently are hard-wired; if this turns out to be a problem,
we'll add a configuration option to the front YAML.

There currently is no way to get an anchor for the v2v3-generated
umbrella section "References"; simply reference the two subsections
instead if needed.




1.6.40: Enable adding annotations to imported bibxml references

You always could add annotations to your own bib entries:

  WEI:
    title: "6LoWPAN: the Wireless Embedded Internet"
    author:
      - name: Zach Shelby
      - name: Carsten Bormann
    date: 2009
    seriesinfo:
      ISBN: 9780470747995
    ann: The reference book on `6LoWPAN`.

However, adding annotations wasn't possible for canned references from
bib.ietf.org, as the XML from there would need to be merged with the
new information from the referencong document.

Annotations are often not about the reference itself, but about its
relevance for the citing document, so it is natural to want to add an
annotation to a canned reference.

The XML work has been done, so you can now slap an annotation on a
canned reference:

  RFC8610:
    ann: >
      CDDL defines its prelude in Appendix D.

This can be combined with other items that were available before:

  RFC8610:
    display: CDDL
    ann: >
      ...

The XML mangling currently only works for annotations; other parts of
canned references cannot be amended/extended yet.
Please let us know if you have a use case.

Annotations do not work for referencegroups yet (BCPxxx, STDxxx);
this is a limitation of xml2rfc.


1.6.39: Add {::boilerplate RFC7942(info)?}

You can now include the boilerplate from RFC 7942 (implementation status) by
simply saying

{::boilerplate rfc7942}
or
{::boilerplate rfc7942info}

The latter adds a sentence with a reference to Section 2.1 of RFC7942 
in front of the fixed boilerplate.



1.6.38: kramdown-rfc-extract-sourcecode fixes

Various fixes to the kramdown-rfc-extract-sourcecode tool.

Grüße, Carsten