Francesa, thanks for your review. Dave, thanks for your responses. I entered a
DISCUSS ballot based on the issue raised about unused citations.
Typically the abstract does contain an explanation of the document(s) being
updated. In this case the list is so long that I’m not sure it’s worth it.
Henrik,
Thanks for the quick followup...
On 9/26/2018 1:08 PM, Henrik Levkowetz wrote:
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:
yeah, sorry. played with the combinatorials
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]"
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
Hi. Thanks for the detailed comments.
Some responses...
On 9/24/2018 3:00 AM, Francesca Palombini wrote:
The use of underscored node names is specific to each RRTYPE that is
being scoped.
As an non-expert in the area, I would have appreciate a ref to a document
introducing RRTYPE.
Reviewer: Francesca Palombini
Review result: Ready with Nits
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please treat these comments just
like any other last call comments.
