Thanks everyone for their feedback. I've now changed the document flow
according to the NEW structure outlined above, and will publish a -05
shortly.
best,
Alex
On Fri, Apr 13, 2018 at 2:18 AM, Daniel Kahn Gillmor
wrote:
> On Thu 2018-04-12 10:11:34 +0200, Alexander
On Thu 2018-04-12 10:11:34 +0200, Alexander Mayrhofer wrote:
> I think it totally depends on the viewpoint (operational vs.
> "research-oriented"). Please share your preferred option - keep with
> CURRENT or restructure for NEW.
I prefer NEW (i like having the recommendation up front) but would
Alexander Mayrhofer writes:
> I think it totally depends on the viewpoint (operational vs.
> "research-oriented"). Please share your preferred option - keep with
> CURRENT or restructure for NEW.
I prefer the NEW option of putting the recommendation before the
discussion of other possibilities.
> On 12 Apr 2018, at 09:50, Shane Kerr wrote:
>
> Alex,
>
> I think that the new way probably makes slightly more sense.
>
> So I prefer the NEW order.
+1 for the NEW order although I might suggest calling Section 4.2 something
like “Other Strategies Evaluated"
Alex,
I think that the new way probably makes slightly more sense.
So I prefer the NEW order.
Cheers,
--
Shane
Alexander Mayrhofer:
> All,
>
> the OPSDIR review from Joe Clarke suggests a re-ordering of the
> document flow in order to better appeal to folks with operational
> background. I'm
All,
the OPSDIR review from Joe Clarke suggests a re-ordering of the
document flow in order to better appeal to folks with operational
background. I'm considering changing the structure of the document,
but i would appreciate yes/no indications from the group before i
proceed. This would not
Reviewer: Joe Clarke
Review result: Has Nits
I have been asked to review this document on behalf of the ops directorate.
This document is intended for experimental status, and describes a number of
strategies to take when performing EDNS(0) padding. It recommends one
(experimental) option to