Re: Enough is Enough.

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

Ofer,

The rules under which I-Ds are submitted and published are clear:
"Internet-Drafts that
 have been removed (for any reason) from the Internet-Drafts
 directories shall be archived by the IETF Secretariat for the sole
 purpose of preserving an historical record of Internet standards
 activity..." [BCP9, RFC2026]
The IETF Trust can, and has, built legal precision around the rights
in I-Ds but they cannot, and have not, changed the rule that they
are archived. 

Regards
   Brian Carpenter

On 25-Oct-20 05:07, Ofer Inbar wrote:
> On Sat, Oct 24, 2020 at 05:39:33PM +0200,
> Toerless Eckert <[e-mail]> wrote:
>> Technically, the key reason for not removing the drafts to me is that
>> only because Khaled was posting the drafts to the IETF did he get cycles from
>> the IETF community that was expressed through many public and (from what i
>> read) also private emails. And it could be seen as a disrespect to those
>> that did spend cycles on reading those drafts and providing feedback to
>> remove the drafts. Especially given how the public exchanges about the
>> draft are archived and those archives would not be comprehensible if the
>> references documents where removed.
> 
> You made it seem like a secondary point, but for me personally, the
> main reason not to remove drafts is to make it possible for people
> reading the list archives or looking into history later on, to see
> what was being discussed at the time and read it directly.
> 
> For that reason, I would feel quite uncomfortable if I saw drafts
> being removed from the archives merely because the submitter wished to
> stop working with the IETF.  Having the drafts present does not
> prevent the submitter from ceasing to work with the IETF.  Knowing
> that that's all it takes to get a draft removed, would make me feel
> about any future draft "this might just disappear later", which
> changes the way people might relate to all future proposals.
>   -- Cos
> 
>