Re: Master-Slave terminology Re: [Piuparts-devel] piuparts.d.o stalled?
There’s no such thing as rejected in IETF. The timestamp is artificially set to 6 months from the I-D published date. Expired draft could mean many things:
- there was not enough consensus to proceed
- draft editors lost interest
- draft editors didn’t have time to update the draft in time
- or perhaps the document was not suited to be published by IETF
The only thing I can say is that the document was not adopted by any working group and that it expired due lack of updates.
Ondrej
--
Ondřej Surý <ondrej@sury.org>
> On 13 Feb 2020, at 11:50, Miriam Ruiz <miriam@debian.org> wrote:
>
> El mié., 12 feb. 2020 a las 21:07, Nicolas Dandrimont
> (<olasd@debian.org>) escribió:
>>
>> * Ulrike Uhlig <ulrike@debian.org> [2020-02-12 17:46:15 +0100]:
>>> I'd like to attract your attention to this very fine document:
>>>
>>> https://tools.ietf.org/id/draft-knodel-terminology-00.html#rfc.section.1.1
>>
>> Thanks for the pointer to this document; I hope the authors succeed in putting
>> it through the RFC process.
>
> I'm sorry I'm not familiar with the bureaucratic procedures of the
> IETF and the RFC process, but I couldn't avoid to see that the text
> says "This Internet-Draft will expire on April 25, 2019".
>
> Does that mean that it was rejected, or is it just a reference
> timestamp with no direct relevance in the process?
>
> Greetings and thanks,
> Miry
>
Reply to: