Hi Dave,
Responding only to the xml2rfc issue, not to the document content:
On 2018-09-26 21:24, Dave Crocker wrote:
> On 9/24/2018 6:16 AM, Dave Crocker wrote:
>>>
>>> + Those registered by IANA in the "Service Name and Transport
>>> Protocol Port Number Registry [RFC6335]"
>>>
>>> Move the end quote after Registry.
>>
>> ok. Good catch.
>
>
> Interesting. Just discovered that this probably qualifies as a bug in
> the xml2rfc processor tool at the IETF site.
I beg to differ. More below:
>
> (I only submitted the xml, which I think is formally ok.)
>
> Here's the xml for that paragraph:
>
> <t>Those registered by IANA in the "<xref
> target="RFC6335">Service Name and Transport
> Protocol Port Number Registry</xref>" The
> underscore is prepended to the service
> parameters to avoid collisions with DNS labels
> that occur in nature, and the order is reversed
> to make it possible to do delegations, if
> needed, to different zones (and therefore
> providers of DNS).</t>
I think xml2rfc does the right thing. The quotes are provided by
you, the author, not the processor, and you've enclosed the element
completely in the quotes:
"<xref target="RFC6335">
Service Name and Transport Protocol Port Number Registry
</xref>"
which as expected gives the <xref/> expansion enclosed in quotes:
"Service Name and Transport Protocol Port Number Registry [RFC6335]"
The expansion of the <xref/> does not, and should not, change because
it's surrounded it by quotes.
If this was wanted:
"Service Name and Transport Protocol Port Number Registry" [RFC6335]
this should have been specified:
<xref target="RFC6335">
"Service Name and Transport Protocol Port Number Registry"
</xref>
xml2rfc is not a do-what-I-mean-not-what-I-say piece of code quite yet ,;-)
Henrik
Attachment:
signature.asc
Description: OpenPGP digital signature
