Re: [quicwg/base-drafts] HTTP/QUIC without Alt-Svc? (#253)

Martin Thomson <notifications@github.com> Wed, 01 February 2017 01:56 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E627D1296FD for <quic-issues@ietfa.amsl.com>; Tue, 31 Jan 2017 17:56:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.814
X-Spam-Level:
X-Spam-Status: No, score=-3.814 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 8Or59X_Azk_f for <quic-issues@ietfa.amsl.com>; Tue, 31 Jan 2017 17:56:41 -0800 (PST)
Received: from o11.sgmail.github.com (o11.sgmail.github.com [167.89.101.202]) (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 D241A1296FB for <quic-issues@ietf.org>; Tue, 31 Jan 2017 17:56:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=2Mj5qS5U5IVXeyZqvMNtXRz3RSY=; b=F9S9b4R2UVKeGAqs zovNpOsr2izSpiiFLGv5KYqFBzMCvq+OfB38rgM7iS49nVoDV6fMLKDzh/aPdJrJ 8Kxcug2Mtm4InY4SFiPK+3V7wMsGz5BarCerB8mGb+rOsCxO0zjiH/0m4uwCq0Xa v4theKqPJ87ruG0g22K8oZENUfk=
Received: by filter0982p1mdw1.sendgrid.net with SMTP id filter0982p1mdw1-18449-58914057-3B 2017-02-01 01:56:39.622440579 +0000 UTC
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [192.30.253.17]) by ismtpd0001p1iad1.sendgrid.net (SG) with ESMTP id 1Re72c-kStSbA6ArzJ2mfQ for <quic-issues@ietf.org>; Wed, 01 Feb 2017 01:56:39.556 +0000 (UTC)
Date: Tue, 31 Jan 2017 17:56:39 -0800
From: Martin Thomson <notifications@github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/253/276551881@github.com>
In-Reply-To: <quicwg/base-drafts/issues/253@github.com>
References: <quicwg/base-drafts/issues/253@github.com>
Subject: Re: [quicwg/base-drafts] HTTP/QUIC without Alt-Svc? (#253)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5891405771040_1ca33f94955e513c845a7"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0/5y5HvMcAY/49VOziU5ENqXm4SkEj9dwTL0 N+JHWQnqRw3kb4vu9P4DA0az4bPRiADY+6kqDnAjcmAWRC2RL1smUDN60alY6gW1/DZBTBPqhrPEdp LOLtudgFwkQQkgpeU8e1KyUK04r2hW/ZelMv1kNl/DunAaVplcKFAp9Mv7q/A98rF9wCBjTneTC13m M=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/FWg6awWoajo9oEOr1bP6nwZgNb4>
Cc: Subscribed <subscribed@noreply.github.com>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: quic@ietf.org
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 01:56:43 -0000

Other protocols have their own bootstrapping problems.  Too much depends on context to be sure.  For instance, migrating something like FTP might be tricky and something akin to Alt-Svc might be the most practical approach.  On the other hand, migrating RTP probably won't have problems in this area because it uses a signaling protocol for setup (RTP would have a host of other problems, of course).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/253#issuecomment-276551881