Hi Lucas,

First of all, can you tell us a little bit more about the use case for
changing the idle timeout? In which situations do you envision this to be
useful?

After reading through the draft, I was wondering if the negotiation
mechanism could be simplified. In RFC 9000, the idle timeout is calculated
as the minimum value advertised by the client and by the server during the
handshake. You could define a new frame that updates this advertisement:
the new idle timeout would now be the minimum of the peer's value and the
new value sent in the frame.

Cheers,
Marten

On Fri, 14 Nov 2025 at 03:41, Lucas Pardue <[email protected]> wrote:

> Hi folks,
>
> Based on some hallway conversations at IETF 124, I realised that one of
> properties of QUIC connections that is hard to tweak during its lifetime is
> the idle timeout. As we see more use cases emerge for the protocol, it
> seemed like there _might_ be some opportunity to benefit from dynamic
> adjustments.
>
> I'm not wedded to the technical design in 00, and it opens a few questions
> that we have been able to ignore so far.
>
> If you think this is something that might be useful, I'd like to hear more.
>
> Cheers
> Lucas
>
> ----- Original message -----
> From: [email protected]
> To: Lucas Pardue <[email protected]>
> Subject: New Version Notification for
> draft-pardue-quic-idle-timeout-update-00.txt
> Date: Thursday, November 13, 2025 19:31
>
> A new version of Internet-Draft
> draft-pardue-quic-idle-timeout-update-00.txt
> has been successfully submitted by Lucas Pardue and posted to the
> IETF repository.
>
> Name:     draft-pardue-quic-idle-timeout-update
> Revision: 00
> Title:    QUIC Idle Timeout Update
> Date:     2025-11-13
> Group:    Individual Submission
> Pages:    8
> URL:
> https://www.ietf.org/archive/id/draft-pardue-quic-idle-timeout-update-00.txt
> Status:
> https://datatracker.ietf.org/doc/draft-pardue-quic-idle-timeout-update/
> HTML:
> https://www.ietf.org/archive/id/draft-pardue-quic-idle-timeout-update-00.html
> HTMLized:
> https://datatracker.ietf.org/doc/html/draft-pardue-quic-idle-timeout-update
>
>
> Abstract:
>
>    QUIC supports an idle timeout for connections, which can be
>    negotiated once during the connection handshake.  This document
>    defines QUIC extension frames that permit either endpoint to initiate
>    an update to the idle timeout value.
>
>
>
> The IETF Secretariat
>
>
>
>
>

Reply via email to