Re: HTTP Alternative Services Best Practices?

Ryan Hamilton <rch@google.com> Wed, 18 December 2019 00:01 UTC

Return-Path: <rch@google.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C322B120073 for <quic@ietfa.amsl.com>; Tue, 17 Dec 2019 16:01:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.5
X-Spam-Level:
X-Spam-Status: No, score=-17.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NTE4QbwfcGBA for <quic@ietfa.amsl.com>; Tue, 17 Dec 2019 16:01:24 -0800 (PST)
Received: from mail-wm1-x335.google.com (mail-wm1-x335.google.com [IPv6:2a00:1450:4864:20::335]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5914120026 for <quic@ietf.org>; Tue, 17 Dec 2019 16:01:22 -0800 (PST)
Received: by mail-wm1-x335.google.com with SMTP id p17so5947wmb.0 for <quic@ietf.org>; Tue, 17 Dec 2019 16:01:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=lm7GpqAcJic0aCPdMu4GbEb2IxuEkyzSmFgQ+QZhjSA=; b=Jt2EApxKcNR8YVdbn4O0YGZgt73tNZDK/QyzRiPYhmhlvW9slTjFSDZaoJOBaTy+z8 6FJ0j/h+FPdFZRuIu26+LOZMAMOH2w6jWL98RecW53lBTsR3e+wuXggX1ji2+5in154G +kcjHNWRgbh7OmdUYeYTiolBzFNyfIEUUGRUX4ejR2K6iT8gEInEa1oycUY7NgNqPqZe WUh499YdKXk3RLXy7yhljlNVZYa43iUAGtLf0fjidykWeRE6Ebp552relthZqss+OszG 4jLRkqOVf9vGFQgJRI5QI80j7t4N0si5frzEZREnKuB3IPWnX5N+lX8UVe3ydYp8Ahhp 7iEA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=lm7GpqAcJic0aCPdMu4GbEb2IxuEkyzSmFgQ+QZhjSA=; b=iW4pFPw6G98xkUNbiWj7QSfdkpPAiRlNNc2C6bdAvhcuoDyYEI1E9hpWP3dDzZFyJs wMqh+3GfTTqKJ/KQsEWCKKKeGAtAHVmSkCI5ln2V4l+qwn9pNl/OwirRJ+A2OLLSgl1X SEE/UJxFR8YibqBO/zKqlsFIcJYmJUTPjKFoKxRJj4EwbGrkhaO5pqFuNUHtcWD1VGke 9LdrXERbXeXpDyNe+iOcgTF2E9UYp6H5hhzD5dsFFYiBUn9oT8tuK3Pf+o+Gtd6U6+MC RSkd4niPK6v2/yvMa8DWxjMd1aLsEQMFFFwJUKEdV2LafbKOc40mAWupz3hPQ0hWaEOW iuvQ==
X-Gm-Message-State: APjAAAX5obea5y4yhGWmlHONl7g6cY7U1dEIT3md3ZedXXdCHoxec7ax JUDvga+WYGz6GiSZFgQg+lOVF3nSoDbiZn+4zNX6FQ==
X-Google-Smtp-Source: APXvYqzHGB9/kU8p/SRGEk3uTEeZUblhOeDtr2+kYec2PTxqgugs71+Tz0HjybiZ0BsRVw4mNzCn8k7vpdiuApJWkWY=
X-Received: by 2002:a05:600c:2c7:: with SMTP id 7mr302420wmn.87.1576627281040; Tue, 17 Dec 2019 16:01:21 -0800 (PST)
MIME-Version: 1.0
References: <CALGR9oaCNigDAZP=ue-sORxCJFzkVynhaJszjjY_ohN56ewy8g@mail.gmail.com> <CAJ_4DfQDgaouwoMyG1f2v4_CndWWNpqft+9=zbOfeM_ek7mSHA@mail.gmail.com> <DM6PR22MB20105A0DA471BB9419E6BDEADA500@DM6PR22MB2010.namprd22.prod.outlook.com>
In-Reply-To: <DM6PR22MB20105A0DA471BB9419E6BDEADA500@DM6PR22MB2010.namprd22.prod.outlook.com>
From: Ryan Hamilton <rch@google.com>
Date: Tue, 17 Dec 2019 16:01:08 -0800
Message-ID: <CAJ_4DfTYnJ9-cZbnofABTrfPTXxNuNzxwzjxd-CuqvR6Ha0Ogg@mail.gmail.com>
Subject: Re: HTTP Alternative Services Best Practices?
To: Mike Bishop <mbishop@evequefou.be>
Cc: Lucas Pardue <lucaspardue.24.7@gmail.com>, QUIC WG <quic@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="0000000000000811cc0599ef257f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/r5OLsG15wq7fK2g6L_uMDtq5j_I>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Dec 2019 00:01:28 -0000

On Tue, Dec 17, 2019 at 11:27 AM Mike Bishop <mbishop@evequefou.be> wrote:

> Saying that “persist=false would be deleterious” is a bit simplistic.
>

Yes, totally fair.

[snip] The right answer here is that you need to know which type of Alt-Svc
> you’re issuing.
>

Completely agree! All of which suggests some sort of Alt-Svc best
practices/guidance doc would be helpful here.