[deepspace] Re: Call for adoption: draft-many-tiptop-quic-profile-03 (Ends 2026-09-02)

[Carles Gomez Montenegro <[e-mail]>]

Hi,

I have reviewed the draft, and I support adoption.

In my opinion, the draft provides a good basis for a document describing
how QUIC can be used or configured for deep-space environments.

Kind regards,

Carles



<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Libre
de virus.www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Fri, 28 Aug 2026 at 13:39, Per Andersson <[e-mail]> wrote:

> Hi,
>
> I support the adoption of this document.
>
> It gives a thorough basis for deep space communications
> using QUIC. I especially appreciate Sections 7 and 8 with
> actual numbers and examples of applicability.
>
>
> --
> Per
>
>
>
>
> On Thu, Aug 20, 2026 at 6:38 AM Padma Pillay-Esnault via Datatracker
> <[e-mail]> wrote:
> >
> > During the IETF 126 WG session, a poll indicated support for this work.
> This message starts a tiptop WG Call for Adoption of:
> > draft-many-tiptop-quic-profile-03
> >
> > This Working Group Call for Adoption ends on 2026-09-02
> >
> > Abstract:
> >    Deep space communications involve long delays (e.g., the Earth to
> >    Mars one-way delay is ~4-20 minutes) and often intermittent
> >    communications.  In this context, the default transport parameters of
> >    QUIC stacks, tuned for the terrestrial Internet, are not suitable for
> >    deep space.  This document defines a QUIC profile for deep space.  It
> >    provides guidance on how to estimate and set transport parameters,
> >    advice to space mission operators and application developers on how
> >    to configure QUIC for the deep space use case, and guidance to QUIC
> >    stack developers on properly exposing the required transport
> >    parameters in their API.
> >
> > Please reply to this message and indicate whether or not you support
> adoption
> > of this Internet-Draft by the tiptop WG. Comments to explain your
> preference
> > are greatly appreciated. Please reply to all recipients of this message
> and
> > include this message in your response.
> >
> > Authors, and WG participants in general, are reminded of the Intellectual
> > Property Rights (IPR) disclosure obligations described in BCP 79 [2].
> > Appropriate IPR disclosures required for full conformance with the
> provisions
> > of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
> > Sanctions available for application to violators of IETF IPR Policy can
> be
> > found at [3].
> >
> > Thank you.
> > [1] https://datatracker.ietf.org/doc/bcp78/
> > [2] https://datatracker.ietf.org/doc/bcp79/
> > [3] https://datatracker.ietf.org/doc/rfc6701/
> >
> > The IETF datatracker status page for this Internet-Draft is:
> > https://datatracker.ietf.org/doc/draft-many-tiptop-quic-profile/
> >
> > There is also an HTML version available at:
> > https://www.ietf.org/archive/id/draft-many-tiptop-quic-profile-03.html
> >
> > A diff from the previous version is available at:
> >
> https://author-tools.ietf.org/iddiff?url2=draft-many-tiptop-quic-profile-03
> >
> > --
> > deepspace mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
>
> --
> deepspace mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
>