> On 4 May 2017, at 12:47 pm, Pete Resnick <presnick@xxxxxxxxxxxxxxxx> wrote: > > As I said earlier, I think it's perfectly appropriate to make sure that we're not endorsing any of these practices in this document, so I have no problem "over-communicating", for example in 2.6.5. And so long as "appropriate context" doesn't mean "we must explain in excruciating detail the wrongness of each and every wrong thing about these practices", I'm fine giving a little context. I just worry from some of the comments that some folks don't want to make mention of any practice without both an explicit rejection of the practice (beyond the context setting at the beginning of the document that it is not the purpose of the document to endorse, but instead simply catalog, these practices) and a statement of alternatives to each of the practices. I think that's unreasonable to ask of this sort of document. So long as it says up front that it is not endorsing any practice, and there is nothing in the description of any particular practice that could be mistaken for an endorsement, that's enough. I'm not advocating going deep into the weeds. OTOH I chafe at the idea of a catalogue that has the theme "useful things that your network can do" that has things like header enrichment thrown in with *no* context -- which is the current state in -11. Looking forward to the next revision. Cheers, -- Mark Nottingham https://www.mnot.net/