cfrg / draft-irtf-cfrg-hpke

Hybrid Public Key Encryption
Other
48 stars 29 forks source link

Use section references #249

Closed cabo closed 2 years ago

sftcd commented 2 years ago

FWIW, I don't think changes like these are worth further extending an already month-long AUTH-48. (It was Jan 7 when this draft moved to AUTH-48.)

S.

On 08/02/2022 09:19, cabo wrote:

You can view, comment on, or merge this pull request online at:

https://github.com/cfrg/draft-irtf-cfrg-hpke/pull/249

-- Commit Summary --

  • Use section references

-- File Changes --

 M draft-irtf-cfrg-hpke.md (12)

-- Patch Links --

https://github.com/cfrg/draft-irtf-cfrg-hpke/pull/249.patch https://github.com/cfrg/draft-irtf-cfrg-hpke/pull/249.diff

cabo commented 2 years ago

Of course not. I was just trying to show how to get the markdown-generated XML closer to the XML manually edited by the RFC editor.

chris-wood commented 2 years ago

@cabo out of curiosity, if this is what the RFC editor's expect in the XML, then why isn't this style of reference the default?

cabo commented 2 years ago

Well, kramdown-rfc does what you tell it to do. v2 did not have section references, so the "default" (= meaning of a simple reference) is to reference the bibliography entry. v3 added section references. The XML for that is arcane, so Martin Thomson and I added markdown support for essentially typing what you want, and with luck, kramdown-rfc knows what XML needs to be generated for that. But that is only done if you put the "Section ... of" etc. into the {{..}}, to maintain backward compatibility with existing documents.

(I don't know, and didn't check here, if the RFC editor actually transforms old style references into section references; I just saw that at least one existing reference generates incorrect output so I fixed all of them -- triggered by the word "section" in the mail exchange :-)