Re: [rfc-i] archiving outlinks in RFCs

[Brian E Carpenter <[e-mail]>]

Eliot,
On 28-Apr-23 08:42, Eliot Lear wrote:
> 
> On 27.04.23 22:20, Brian E Carpenter wrote:
>> I think that automating the errata creation is a good idea. The point
>> is to trigger human intervention when it's appropriate, and that
>> should be a stream choice rather than an RPC choice. In many cases an
>> automated redirect to an archive copy will be all that's needed.
> 
> I am not ready to say that.  I would like to see if there is a generic
> policy that could apply to all RFCs.  That will provide the reader with
> a consistent experience.

I'm sure that there's a generic *default* policy that would apply to
*most* RFCs, but there might be corner cases. My thinking is to apply
the generic policy automatically, but to use the errata mechanism to
alert the content owner (i.e. the stream). If the stream does nothing
before $TIMEOUT, the default policy would apply.

As for what a corner case might be, I don't know, that's why it's
a corner case.

     Brian