Re: [EXTERNAL] Re: HTTP Alternative Services Best Practices?

Lucas Pardue <lucaspardue.24.7@gmail.com> Tue, 17 December 2019 23:07 UTC

Return-Path: <lucaspardue.24.7@gmail.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 56C42120100 for <quic@ietfa.amsl.com>; Tue, 17 Dec 2019 15:07:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level:
X-Spam-Status: No, score=-1.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 AxFZkgLZKUaH for <quic@ietfa.amsl.com>; Tue, 17 Dec 2019 15:07:27 -0800 (PST)
Received: from mail-ua1-x930.google.com (mail-ua1-x930.google.com [IPv6:2607:f8b0:4864:20::930]) (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 5FD4B120058 for <quic@ietf.org>; Tue, 17 Dec 2019 15:07:27 -0800 (PST)
Received: by mail-ua1-x930.google.com with SMTP id 73so340399uac.6 for <quic@ietf.org>; Tue, 17 Dec 2019 15:07:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=4BWl+UWx5pSJpWoU1Ryaz8bpMxQfnx3K4NzTZmLYDKU=; b=MANu+5FiVQItQob3Dqo1Q1jnmtxK8gGYmrHXkP66lWfCFB8q+ZGSmV1E3vxS836Dc+ I/ovBboHQZemxInLet7kNpgnblwCkT4MgDlJYezU6N9fxgsYnOcPoSev0mFVjlri0+IQ UwCYwk92mKB5q7mqkYfjovZ7n8EQGMS4rUaVMhgjSvX5pDu2XgcC2HolnK+SruoB/MEO ALEIZS1aGG9GNFrIp/2GdvljHb6PUpW1ALdr33ByWv7Nn3X5eikTcLbiTY0rmXp/GuTo lUZ4OHWzJeTD9Ps0OSeacJjM2BDuk17YX07mupIGsq1SJQjFK6vthMm2Tc/s04r32UtT H1bw==
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=4BWl+UWx5pSJpWoU1Ryaz8bpMxQfnx3K4NzTZmLYDKU=; b=Tp5eALaDBHzwUPJ1jny4IE8GMw10N0YymeLTvtA2enadmPQ0fxQOQ/gCkxosIyFtAc EYhkusC37kcsPMBKis1QOF8+hhO1DUFX5Ju6C55AsWY8erHCkraz62bnHxDfmd02g1EA E83mxrKldcq9AceM35VUabkvEd8VGUCr7/vX6pl7N0i/knJZA0BulVZ6zpy3OtzrYLM3 rWbM9vd1M6jrv2CCS9xlxI0r3L+TuhHOt5ivNn/F5cFFPOiM7qCrYSJbPFKzb6aZx98S zW1sIh5S2dy3QZQJqa4oIJzstSIyEix/AOp0s9z2GeovBxRr4SXw6gXPmk5o1WVALp13 6ppw==
X-Gm-Message-State: APjAAAWcGWHNrRd+704W9yutwurppTsacDnWj7xyWDxJZzVkGwWjh/oI VoU/S2O2asWfqxz/WlJ2TfmExTP3SofHcZ6aQBg=
X-Google-Smtp-Source: APXvYqwuTSZoLqcB1GpRC22oPpwQpTdfNaCoHFJzbzAMUHsabssQPOKL/SKxVAZDwz03QXkALFRE7VA1acDI7crUOAY=
X-Received: by 2002:a9f:2c8b:: with SMTP id w11mr5468559uaj.69.1576624046260; Tue, 17 Dec 2019 15:07:26 -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> <CALGR9oYAURH4KnzHKmASQdOA6-rH+V-v2Ro2cekVQpnzZS-XNA@mail.gmail.com> <DM5PR21MB084181A43FC4A8CFEEB35151FD500@DM5PR21MB0841.namprd21.prod.outlook.com>
In-Reply-To: <DM5PR21MB084181A43FC4A8CFEEB35151FD500@DM5PR21MB0841.namprd21.prod.outlook.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Tue, 17 Dec 2019 23:07:18 +0000
Message-ID: <CALGR9oY6DzjsH46AT6C4BXTx0MtH0JCsBsgrBeWRcjA4rXKGVA@mail.gmail.com>
Subject: Re: [EXTERNAL] Re: HTTP Alternative Services Best Practices?
To: Cory Nelson <Cory.Nelson@microsoft.com>
Cc: Mike Bishop <mbishop@evequefou.be>, Ryan Hamilton <rch=40google.com@dmarc.ietf.org>, QUIC WG <quic@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="00000000000038c85d0599ee6466"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/1R9yLOVdXeD9bHrJR8NF5pvV93A>
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: Tue, 17 Dec 2019 23:07:28 -0000

Hi Cory,

I think your questions are probably good implementation-oriented ones but
less about BCP to my mind. If there is something worth documenting, my
instinct is a separate document that compliments RFC7838.

To answer:

On Tue, 17 Dec 2019, 22:46 Cory Nelson, <Cory.Nelson@microsoft.com> wrote:

> Two questions I had while implementing Alt-Svc, and ended up looking at
> other implementations for guidance:
>
>
>
> Is it valid to have Alt-Svc: clear followed by, on another line, more
> Alt-Svc to replace the old services?
>
RFC7838 says about Alt-Svc:

"The field value consists either of a list of values, each of which
indicates one alternative service, or the keyword "clear"."

So I think it is clear that it is invalid to have both clear and an
alt-value. But what might be less clear is the expected failure mode if
this does actually occur.

> Is it valid for an authority to extend their lease by sending an Alt-Svc
> for themselves?
>
If you mean is it valid for a selected alternative to advertise itself and
therefore keep itself fresh, then yes, the alternative is fully
authoritative and I think that this is captured in the specification.

Cheers
Lucas

>