I think the issue with it is that it assumes you are arriving to work on TCP/IP or something like that. The organization is bigger now. Many groups operate differently, so there is not as much uniform advice.
thanks,
Rob
On Thu, Jan 25, 2024 at 12:05 Paul Wouters <paul@xxxxxxxxx> wrote:
On Jan 25, 2024, at 13:50, Brian E Carpenter <brian.e.carpenter@xxxxxxxxx> wrote:
>
> I fully support the draft. The Tao has outlived its usefulness as an RFC
I agree.
As for those believing a single long document is the best way to consume content these days, I advise you to try out TikTok to get a better idea of modern content consumption methods.
I love the historic and nostalgic bits but those should have its own place outside of a “quick 101 IETF how to”. The tao is huge.
Paul
> On 26-Jan-24 05:54, Deen, Glenn wrote:
> ...
>
>> I’m surprised something as core to the IETF as the TAO is going direct to last call so quickly and hasn’t had broader discussion/review.
>
> I don't understand that comment. This discussion has been going on for at least 18 months, and specifically since this message on the public list devoted to the Tao:
>
> https://mailarchive.ietf.org/arch/msg/tao-discuss/DedMWVvKwm7TA3zM7Fvy45DoW78
>
> and I think the draft itself explains and justifies the change.
>
> Regards
> Brian Carpenter
> --
> last-call mailing list
> last-call@xxxxxxxx
> https://www.ietf.org/mailman/listinfo/last-call
--
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call
-- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
