On 6/28/2018 12:02 PM, Paul Hoffman wrote:
On 28 Jun 2018, at 7:19, Dave Crocker wrote:
On 6/27/2018 3:01 PM, Paul Hoffman wrote:
Due to its nature, the document is a bit difficult to read, but I
don't have any suggestion about how to make it better.
Could you at least provide some
On 28 Jun 2018, at 7:19, Dave Crocker wrote:
On 6/27/2018 3:01 PM, Paul Hoffman wrote:
Due to its nature, the document is a bit difficult to read, but I
don't have any suggestion about how to make it better.
Could you at least provide some description of what it is that you
find difficult?
On 6/27/2018 3:01 PM, Paul Hoffman wrote:
Due to its nature, the document is a bit difficult to read, but I don't
have any suggestion about how to make it better.
Could you at least provide some description of what it is that you find
difficult?
The only problem I have
with the document
Due to its nature, the document is a bit difficult to read, but I don't
have any suggestion about how to make it better. The only problem I have
with the document is that there are lots of informational references
that are not referred to in the body of the text; they are not even
listed in
A number of reviewers of the accompanying draft-ietf-dnsop-attrleaf
suggested to have both drafts WG Last Call reviewed in one go. We think
this makes sense and the last version of the
draft-ietf-dnsop-attrleaf-fix-01 is good for WG Last Call.
This starts a Working Group Last Call for draft-ietf
