Hi Kent, Balázs,
On 27.03.20 19:15, Kent Watsen wrote:
On Mar 27, 2020, at 1:36 PM, Balázs Lengyel
<[email protected]> wrote:
https://tools.ietf.org/html/draft-ietf-netmod-artwork-folding-12
<https://tools.ietf.org/html/draft-ietf-netmod-artwork-folding-12> contains a section with
<CODE BEGINS> <CODE ENS>.
Looking at -12, I see "<CODE ENDS>” (not <CODE ENS>), is this just a typo in
your message?
However rfcstrip cannot extract this part. Is that a problem?
It seems that the <CODE BEGINS> line is messed up:
OLD:
<CODE BEGINS>
NEW:
<CODE BEGINS> file "rfcfold"
Fixes it.
Do you know of a written explanation on how to use the <CODE BEGINS> ...
<CODE ENDS> markers? I tried to find one without success. I found only
usage hints, and the licensing connection.
RFC 8407 says:
The "<CODE BEGINS>" tag SHOULD be followed by a string identifying
the file name specified in Section 5.2 of [RFC7950]."
The predecessor RFC 6087 contains similar text. Thus it seems the
netmod WG convention is to specify a file name. The rfcstrip utility
mentioned in RFC 8407 requires the file name, although the file name
seems to be optional.
But some RFCs do not specify a file name for code sections. Some
random examples are RFC 5662, RFC 6287, RFC 7861, and RFC 8290. Those
are from WGs other than netmod, though.
Just curious. :-)
Thanks,
Erik
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
