On Tue, Mar 5, 2019 at 1:34 AM Warren Kumari <[email protected]> wrote:

>
>
> On Mon, Mar 4, 2019 at 11:05 AM Paul Wouters <[email protected]> wrote:
>
>> On Mon, 4 Mar 2019, Warren Kumari wrote:
>>
>> > So, my plan is to 1: ask the authors to please swap the Y to an N as
>> below and 2: progress the document with the hope that this
>> > section will survive the publication process.
>>
>> But I do not hope that.
>>
>> > The March telechats are often really full - ADs who are leaving the
>> IESG try and get old / stuck work finished and off their
>> > plate - and so this would likely only show up on the 2019-04-11
>> telechat -- so if anyone really objects to this being (attempted
>> > to be) left in, please shout.
>>
>> I think it should not be in the document. For one, it will be quickly
>> outdated information over the years as implementations release new
>> versions. Second, it will lead to people putting these sections in for
>> marketing. I think RFCs should avoid naming products whenever possible.
>>
>> I'm happy to do a new rev that includes an improved "remove me" note to
>> IANA and the pdns update.
>>
>>
> That works for me too...
>

I was hoping to see this update before the draft cutoff; as that didn't
happen, I've decided to start the ballot, and have added a note to explain
that this is intended to be removed -- please remember to add the "Please
remove" whenever you address the IESG comments (of which I'm sure there
will be some)

W



> W
>
>
>
>> Paul
>>
>
>
> --
> I don't think the execution is relevant when it was obviously a bad idea
> in the first place.
> This is like putting rabid weasels in your pants, and later expressing
> regret at having chosen those particular rabid weasels and that pair of
> pants.
>    ---maf
>


-- 
I don't think the execution is relevant when it was obviously a bad idea in
the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair of
pants.
   ---maf
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop

Reply via email to