Re: Last Call: Change the status of ADSP (RFC 5617) to Historic

[Eliot Lear <[e-mail]>]

Dave,

If someone is willing to write the document and explain why ADSP has
been moved to Historic, that's good for capturing lessons learned.  I
don't think it's required for the status change, but a bonus.

Eliot

On 11/20/13 6:25 PM, Dave Crocker wrote:
> On 11/20/2013 9:13 AM, Barry Leiba wrote:
>>    it should be done with a document that explains the
>> deployment situation and explains why the reclassification is
>> appropriate despite that.
> ...
>> John has a reasonable point about writing up an explanation, and we
>> have had volunteers to do so.
>
>
> The IETF has some history moving documents to Historic status.  I have
> not noticed that it has a track record of requiring documents to
> explain the actions for these earlier examples.
>
> If indeed we've been doing it, what are these precedents?  If we
> haven't, why start now?
>
> What is the compelling community requirement that demands this
> significant bit of extra work be imposed as a barrier to change in
> status?
>
> Extra work needs to have compelling extra benefit.
>
> d/