Re: Alternative Server Address Frames -01
Marten Seemann <martenseemann@gmail.com> Wed, 29 July 2026 15:12 UTC
Return-Path: <martenseemann@gmail.com>
X-Original-To: quic@mail2.ietf.org
Delivered-To: quic@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 3BB481208E527 for <quic@mail2.ietf.org>; Wed, 29 Jul 2026 08:12:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1785337932; bh=MV2EfNdVB/t72cXMejmKUdQ820H/VNwtesSqd5NX8Ow=; h=References:In-Reply-To:From:Date:Subject:To:Cc; b=m3jYCNeAZ2rEmGbe6FTe7VhJELWV3ShR9qVTpLzr1MOTlL+AQWRdeRn4yjBx0lV9a 6rrNQILyZ7QaAqMR+Icf/jsftsYOeDCtGvjtx93/3OFo3Tw9VK0yKM7W5bu6Yf9sOL hsIFtwPg88jA6Utt8M50tkKa5ds+e5JQO6RduzB0=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KQt-8DTTlqFF for <quic@mail2.ietf.org>; Wed, 29 Jul 2026 08:12:11 -0700 (PDT)
Received: from mail-yw1-x112c.google.com (mail-yw1-x112c.google.com [IPv6:2607:f8b0:4864:20::112c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 7E0F31208E51F for <quic@ietf.org>; Wed, 29 Jul 2026 08:12:11 -0700 (PDT)
Received: by mail-yw1-x112c.google.com with SMTP id 00721157ae682-81062fdeaf5so31354827b3.0 for <quic@ietf.org>; Wed, 29 Jul 2026 08:12:11 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1785337931; cv=none; d=google.com; s=arc-20260327; b=AJTlolNRKLdHnYB1h4pLmMnc/iQfTSGo9yAGNqANmtsdQeAZNZ2jRCV91s95wNOQzZ /OSjvfMG+ojx0GOOoGxQUOge7opYre45nB6Tm9vt1L7dTQGvXafNeHCAlHFYb8TVPwje HmI6jowU9Fovxfwza3u1TBDH/82RH6MTRnP5QxyVFSIYt9/EonY0rMGW2tTV40LmM+Rc KFrfSkQR4B69tWOJwbV6NbDb4XnumVHD1nUuugRGUiznY9S+DkzkARqrfAganIC+6Zvs HtDpYP6mAE9+KqD67h51AK34YcbHTf8PZCVFyh1mYIIlIb5MeAJzRywlZyoTiIqpkUEt CO/g==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20260327; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:dkim-signature; bh=7fyGB03G85dD2XZo3zCP9ZV6NXKWqzyKLClNa6oWzKw=; fh=IcoJ1ckbu2j6xITbxV05eyl1PMr2W74aU/Tu03ZEzuU=; b=n8xGQL27AW9vd15KXJ1AMLMBmb8kPtMz6l0bAN3JVO+Dlq2Etnetfb8nzi8oze+4r8 oxy4u2XhxnO9ErIWm4FQ1bXWfdhVJp+HSVlpmeZAJOCdYE4VtkSOCRCST6rT4boWd5NM Sazls/kvZmqfWyO9I+qrg76Xr2rGo+b12WnpB4Egjw+M2Ljd7e/5ZOPwq8qiVXgxuVgS SuIYT/8Vonsy2TFWkm1LLg/zEzOV62UGx2LktQUGfuVIMLFxLmE54TbfQxCVyC8HwaGV 2gFLF3IbmdDjuONuYENiMBVqieYXNvT4qcIu3rj9ZJiJh+avYNs/HPAHUoZT+Apv1bHf MEQw==; darn=ietf.org
ARC-Authentication-Results: i=1; mx.google.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1785337931; x=1785942731; darn=ietf.org; h=content-type:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:from:to:cc:subject:date:message-id:reply-to :content-type; bh=7fyGB03G85dD2XZo3zCP9ZV6NXKWqzyKLClNa6oWzKw=; b=IP2po+MX/aQZH4klkkCzskFclmMJOO9vaJ0TQ3I9dZLlUH4de9YhL6xKGOGg99C6lb jr2R0xcbc3MRh4Wzuoc7bwxBvyJG4KUhe1xeadhhnPVwppeZ7kL4SVsEbJBZtm419oQz LuyfhL394UF5AtHo4W6zCxe7vBRAvOIWFhpUj4x8L0DIf515gOtEogS6CU5e7l+Y5Zl2 TeikzpmfL5bCsvfra0QAisT8q0B/JGEWO5TCjop7ENdw6bx4AhW7f+PmVxmDRwQXatSW He0mdFBE8IHjij7ptcw7oa67HCTCompmXishS3i2nrGtfuAqKnfm6j0Fmsyx/7heyu1b DHVQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1785337931; x=1785942731; h=content-type:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:x-gm-gg:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to:content-type; bh=7fyGB03G85dD2XZo3zCP9ZV6NXKWqzyKLClNa6oWzKw=; b=VMI+AD7Fa2vGg81NBocSgI48i74vIQpAQgi09Xd5XuT1zkfoCesPjNA8+JnrmxPypT Wvy0a9LwsHPkFOdeMeNKLu7CWajE+JxQ2WHP/AVHr2b1Dox08AhP7MTz3slCi1Dgzlab 5R1LyMj8NRUa4Qnc+SWXT/dE+APUBN8hiBKN1knlYodzCm0RhbGCNWSP1mwNCgNTH6+o KPvYsGIdd4prnhAfADNI5v0KMv6ld1K1nWfh9+YPYYd7PIMlxd/sD37QRZPLuzA76qRr whpMl4RS05KgmtwfS+TvXWUD1GzcCjpzFc9PyynSaW/ypMgzHr7I6vZTo8ip8ZuFsm6H IHmw==
X-Gm-Message-State: AOJu0YxSJpjUir51kKowzmSiF7b6vRwtEe9uG160xbuRffD437nP2TtV HzBrqIBQETHcnrOQnkn+Ak/XsG0WLOGY+VTFiazf1ZighlRjcXf09AnsMv7GlBchj5xwx0BR55J jFbFbo4CMcQJuH7FWnLcXvNFKuLu7jDc=
X-Gm-Gg: AR+sD11Cvdq+4p/7jzplXXXlUH+xACY9beMSdhxYXVjMaFjHlpwgR62OK3CKVEUcbGT 88cNuyThcD+UMADfdtnF2A6UaVM5QnJ2pNNqREETi9E6znEDj5i5bQCVmCfo8f9hgL19PS+Enrd r5EnT1N7Z+WlwTVn4U4QjDKP0yOeLEigh2VavLkxKi0GKYgP7B5bd7HANhUiFJlMnNtU6iOZnSM 9ifrHHV/hV16+eWweDJZPkG3FpDp/XqUZsA4wBPuT4R/S6Y9NEcR02BtYQin/InMrJVVEw7WRUe /lRu+vHwr1TpiHoM031UOZsjXEKUa3/uQehK1uf6FPfjP5T8LJSSH8+8o5HKNmQqz/upThSu5L0 Mcca3
X-Received: by 2002:a05:690c:6e8b:b0:812:9e6d:d47c with SMTP id 00721157ae682-81fa798940bmr12442857b3.10.1785337930812; Wed, 29 Jul 2026 08:12:10 -0700 (PDT)
MIME-Version: 1.0
References: <CAOYVs2qZVkCzj3zN+pJ9neYBhRmM7w-Sf10qGkDd5wL6Cw6xcw@mail.gmail.com> <ZR0P278MB0443CD44BE6FF462D3E35342C8CA2@ZR0P278MB0443.CHEP278.PROD.OUTLOOK.COM>
In-Reply-To: <ZR0P278MB0443CD44BE6FF462D3E35342C8CA2@ZR0P278MB0443.CHEP278.PROD.OUTLOOK.COM>
From: Marten Seemann <martenseemann@gmail.com>
Date: Wed, 29 Jul 2026 23:11:59 +0800
X-Gm-Features: AUfX_mwHGO8YSjoinWlwcn-117J07s9a3BwGv-8EZShXFcbdrfCKBYzcHYB7Vns
Message-ID: <CAOYVs2rR6fw2O1w83MDy2VftbBdaZ5yymDLXdGU5WRyktRwNtQ@mail.gmail.com>
Subject: Re: Alternative Server Address Frames -01
To: Zäschke Tilmann <tilmann.zaeschke@inf.ethz.ch>
Content-Type: multipart/alternative; boundary="0000000000002b91660657c1619d"
Message-ID-Hash: FY4VYOBAMQQOBWMAKI53WNRNF7IUOLCF
X-Message-ID-Hash: FY4VYOBAMQQOBWMAKI53WNRNF7IUOLCF
X-MailFrom: martenseemann@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-quic.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: QUIC WG <quic@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Hi_zT_HDAKc1tciGUlglSH37SNw>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Owner: <mailto:quic-owner@ietf.org>
List-Post: <mailto:quic@ietf.org>
List-Subscribe: <mailto:quic-join@ietf.org>
List-Unsubscribe: <mailto:quic-leave@ietf.org>
> Section 5, page 4. "Priority Hint values have meaning only relative to other values on the same side of the CURRENT_PATH entry; values on opposite sides are unrelated." Why is that? On a client, a naive implementation may just want to put all recommendations into a ranked list and then choose the best one. However, having a single ranked list is difficult if priority values are unrelated. Maybe the design decision could be clarified, why are priorities are separate for each side of the sentinel? These are fundamentally two very different kinds of addresses; it does not make sense to order them globally. Any address above the sentinel is one that the server is requesting the client to migrate to immediately, so the relative priorities of the backup addresses become irrelevant. > Section 5, page 4. "Entries on each side MUST appear in ascending Priority Hint order." If entries are ordered by priority. If the priority is implicitly given by the order, why do we need an additional field with a priority hint? The priority field exists to allow equal priorities. For example, a server might have both a Wi-Fi and a cellular interface. All addresses associated with the Wi-Fi interface (IPv4 and IPv6) could share the same priority, while all addresses associated with the cellular interface would be given a different (most likely lower) priority. > Section 7, page 5. "This extension complements the Multipath extension for QUIC by allowing the server to contribute more information to the client for alternative paths." I am not sure how this would work with QUIC multipath (QUIC-MP). In QUIC-MP you may have multiple paths. However, the CURRENT_PATH sentinel represents only a single path for which alternatives are given. If I have two paths, A and B, how can a server communicate preferred alternatives for each path? Or is the idea that alternatives are only valid for the path on which they are sent? Maybe that could be clarified? You’re right that the interactions with multipath are not fully fleshed out yet. In the most primitive form the server is simply asking the client to establish a new path; what happens with that path once it is established is left to the two endpoints. They could use the new path in addition to existing ones, or have it replace one or more of them. I’m not sure this needs to be specified in the present extension, since all of those options can already be expressed with the frames defined by QUIC multipath. On Wed, 29 Jul 2026 at 21:45, Zäschke Tilmann <tilmann.zaeschke@inf.ethz.ch> wrote: > Hi Marten, > > This draft is very interesting, but I do have some questions: > > > - Section 5, page 4. > "Priority Hint values have meaning only relative to other values on > the same side of the CURRENT_PATH entry; values on opposite sides are > unrelated." > Why is that? On a client, a naive implementation may just want to put > all recommendations into a ranked list and then choose the best one. > However, having a single ranked list is difficult if priority values are > unrelated. Maybe the design decision could be clarified, why are > priorities are separate for each side of the sentinel? > - Section 5, page 4. > "Entries on each side MUST appear in ascending Priority Hint order." > If entries are ordered by priority. If the priority is implicitly > given by the order, why do we need an additional field with a priority > hint? > - Section 7, page 5. > "This extension complements the Multipath extension for QUIC by > allowing the server to contribute more information to the client for > alternative paths." > I am not sure how this would work with QUIC multipath (QUIC-MP). In > QUIC-MP you may have multiple paths. However, the CURRENT_PATH sentinel > represents only a single path for which alternatives are given. > If I have two paths, A and B, how can a server communicate preferred > alternatives for each path? > Or is the idea that alternatives are only valid for the path on which > they are sent? Maybe that could be clarified? > > > Please let me know if you prefer the discussion on GitHub or somewhere > else. > > Thanks and kind regards, > Tilmann Zäschke > > ------------------------------ > *From:* Marten Seemann <martenseemann@gmail.com> > *Sent:* Wednesday, July 22, 2026 0:47 > *To:* QUIC WG <quic@ietf.org> > *Subject:* Alternative Server Address Frames -01 > > > Hi all, > > After a couple of very helpful conversations at the IETF meeting in > Vienna, we published -01 of the Alternative Server Address Frames draft: > > > https://datatracker.ietf.org/doc/draft-munizaga-quic-alternative-server-address/01/ > > The frame format has changed. An ALTERNATIVE_ADDRESS frame now advertises > the complete set of available server addresses, indicating whether an > address is preferred over the current path or is intended as a backup. > > The purpose remains to let a server advertise alternative addresses to > which the client can migrate. NAT traversal and hole punching remain out of > scope, though I expect my NAT traversal draft to use this draft as a > building block. > > Cheers, > Marten > >
- Alternative Server Address Frames -01 Marten Seemann
- Re: Alternative Server Address Frames -01 Zäschke Tilmann
- Re: Alternative Server Address Frames -01 Marten Seemann
- Re: Alternative Server Address Frames -01 Zäschke Tilmann
- Re: Alternative Server Address Frames -01 Christian Huitema
- Re: Alternative Server Address Frames -01 Zäschke Tilmann
- Re: Alternative Server Address Frames -01 Marten Seemann
- Re: Alternative Server Address Frames -01 Zäschke Tilmann