at least two independent and inter-operable implementations

Posted Aug 3, 2020 1:10 UTC (Mon) by marcH (subscriber, #57642)
Parent article: Netgpu and the hazards of proprietary kernel modules

> While the current GPU utilized is nvidia, there's nothing in the rest of the patches specific to Nvidia - an Intel or AMD GPU interface could be equally workable.

For the IETF "could" isn't enough:

https://www.ietf.org/how/runningcode/implementation-reports/

> The IETF Standards Process (RFC 2026, updated by RFC 6410) requires at least two independent and inter-operable implementations for advancing a protocol specification to Internet Standard.

Because the devil is always in the details.

at least two independent and inter-operable implementations

Posted Aug 5, 2020 3:36 UTC (Wed) by gdt (subscriber, #6284) [Link] (1 responses)

I would be cautious when presenting IETF processes as an ideal. See rfc8789 for the latest developments; correcting an undesirable outcome where documents which had not achieved "rough consensus" were being published as Informational RFCs.

at least two independent and inter-operable implementations

Posted Aug 5, 2020 6:07 UTC (Wed) by marcH (subscriber, #57642) [Link]

> I would be cautious when presenting IETF processes as an ideal.

Good thing I gave only a very narrow quote then.

> ... where documents which had not achieved "rough consensus" were being published as Informational RFCs.

My quote refers to the Standards Track.