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

Mike Bishop <notifications@github.com> Wed, 01 February 2017 18:16 UTC

Return-Path: <noreply@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 E261712953D for <quic-issues@ietfa.amsl.com>; Wed, 1 Feb 2017 10:16:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.655
X-Spam-Level:
X-Spam-Status: No, score=-7.655 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-1.156, RCVD_IN_SORBS_SPAM=0.5, 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 JbC6k4oD8ch6 for <quic-issues@ietfa.amsl.com>; Wed, 1 Feb 2017 10:16:36 -0800 (PST)
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext2.iad.github.net [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D4B4B12953A for <quic-issues@ietf.org>; Wed, 1 Feb 2017 10:16:35 -0800 (PST)
Date: Wed, 01 Feb 2017 10:16:35 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1485972995; bh=tti2gfUqFsHUAfWkhG0xJ9YzZAlP51GsQ99IkO+KIR0=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=TMNeHzpAYhMFq2kkyd90pQPKe32V+t0U6lcXVQOJ5D5VKQQhlOqR77aXj/ab811qO NmOJ9++19sznwZZIlpqWFTxkrJ2+rgG04I4WkYnJEbYiNnkLOfyi6EU8uQCEuL5Fek JnOAeI7/uzPAGr0/MPGZjiHnfgVOl2S9K/ZV3L3I=
From: Mike Bishop <notifications@github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/253/276736069@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_5892260334f42_71b93fc37252f13c18609a"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/53Vt84tCae1KbN0_FeSCCC9017c>
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 18:16:38 -0000

Oh, and @LPardue:  RFC 2818 says in Section 2.3:

>  When HTTP/TLS is being run over a TCP/IP connection, the default port   is 443. This does not preclude HTTP/TLS from being run over another   transport. TLS only presumes a reliable connection-oriented data   stream.

RFC 7230 updates this by saying:

>    The "https" URI scheme is hereby defined for the purpose of minting   identifiers according to their association with the hierarchical   namespace governed by a potential HTTP origin server listening to a   given TCP port for TLS-secured connections ([RFC5246]).
>
>   All of the requirements listed above for the "http" scheme are also   requirements for the "https" scheme, except that TCP port 443 is the   default if the port subcomponent is empty or not given....

-- 
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-276736069