Re: [lamps] Editing help with external references with kramdown / xml2rfc tools

[Daniel Migault <[e-mail]>]

This might be what you are looking at:


informative:
  UNBOUND-ANCHOR:
    author:
    target: https://nlnetlabs.nl/documentation/unbound/unbound-anchor/
    title: unbound-anchor - Unbound anchor utility
  ENT:
    author:
      name: Vincent Levigneron
    target: https://indico.dns-oarc.net/event/25/contributions/403/attachments/378/647/AFNIC_OARC_Dallas.pdf
    title: ENT was here !!!



https://github.com/mglt/draft-mglt-dnsop-dnssec-validator-requirements/edit/master/draft-ietf-dnsop-dnssec-validator-requirements.mkd

________________________________________
From: Spasm <[e-mail]> on behalf of Mike Ounsworth <Mike.Ounsworth=[e-mail]>
Sent: Saturday, February 12, 2022 10:38 AM
To: 'LAMPS'
Subject: [lamps] Editing help with external references with kramdown / xml2rfc tools

Anyone willing to help me get the syntax right for specifying external references in an I-D?

Toolchain: source (.mkd) ----kramdown-rfc2629--->  .xml  ------xml2rfc------>  .txt / .html


I have specified my references like this:

informative:
  I-D.draft-ounsworth-pq-composite-sigs-05:
  Bindel2017:
    title: "Transitioning to a quantum-resistant public key infrastructure"
    author:
      -
        ins: N. Bindel
        name: Nina Bindel
      -
        ins: U. Herath
        name: Udyani Herath
      -
        ins: M. McKague
        name: Matthew McKague
      -
        ins: D. Stebila
        name: Douglas Stebila
    date: 2017

normative:
  RFC1421:
  RFC2119:
  RFC2986:
  RFC4210:
  RFC4648:
  RFC5280:
  RFC5652:
  RFC5958:
  RFC7468:
  RFC8174:
  RFC8411:
  X.690:
      title: "Information technology - ASN.1 encoding Rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER)"
      date: November 2015
      author:
        org: ITU-T
      seriesinfo:
        ISO/IEC: 8825-1:2015


The normatives all render fine.

The informatives are completely absent in the rendered .txt and .html.



The kramdown-rfc2629 tool is placing them in the .xml intermediate like this:

    <references title='Normative References'>

&RFC1421;
&RFC2119;
&RFC2986;
&RFC4210;
&RFC4648;
&RFC5280;
&RFC5652;
&RFC5958;
&RFC7468;
&RFC8174;
&RFC8411;
<reference anchor="X.690" >
  <front>
    <title>Information technology - ASN.1 encoding Rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER)</title>
    <author >
      <organization>ITU-T</organization>
    </author>
    <date year="2015" month="November"/>
  </front>
  <seriesInfo name="ISO/IEC" value="8825-1:2015"/>
</reference>

    </references>

    <references title='Informative References'>

&I-D.draft-ounsworth-pq-composite-sigs-05;
<reference anchor="Bindel2017" >
  <front>
    <title>Transitioning to a quantum-resistant public key infrastructure</title>
    <author initials="N." surname="Bindel" fullname="Nina Bindel">
      <organization></organization>
    </author>
    <author initials="U." surname="Herath" fullname="Udyani Herath">
      <organization></organization>
    </author>
    <author initials="M." surname="McKague" fullname="Matthew McKague">
      <organization></organization>
    </author>
    <author initials="D." surname="Stebila" fullname="Douglas Stebila">
      <organization></organization>
    </author>
    <date year="2017"/>
  </front>
</reference>

    </references>


but xml2rfc gives me this warning and then they don’t appear at all in the rendered .txt and .html

Warning: No <xref> in <rfc> targets <reference anchor='RFC1421'>
Warning: No <xref> in <rfc> targets <reference anchor='RFC4648'>
Warning: No <xref> in <rfc> targets <reference anchor='I-D.ounsworth-pq-composite-sigs'>
Warning: No <xref> in <rfc> targets <reference anchor='Bindel2017'>



Anyone have an idea what I’m doing wrong here?


- - -
Mike Ounsworth
Software Security Architect
(pronouns: he/him)
O: [phone]
[cid:image004.png@01D81FF4.4B63C2A0]

[cid:image003.png@01D81FF2.8323D560]


Any email and files/attachments transmitted with it are confidential and are intended solely for the use of the individual or entity to whom they are addressed. If this message has been sent to you in error, you must not copy, distribute or disclose of the information it contains. Please notify Entrust immediately and delete the message from your system.