[quicwg/base-drafts] TLS Intro (#398)
Sean Turner <notifications@github.com> Tue, 14 March 2017 01:48 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 4FEE112940C for <quic-issues@ietfa.amsl.com>; Mon, 13 Mar 2017 18:48:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.383
X-Spam-Level:
X-Spam-Status: No, score=-5.383 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_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-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 NY-PEtd3ksoW for <quic-issues@ietfa.amsl.com>; Mon, 13 Mar 2017 18:48:49 -0700 (PDT)
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext4.iad.github.net [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B93F812946C for <quic-issues@ietf.org>; Mon, 13 Mar 2017 18:48:49 -0700 (PDT)
Date: Mon, 13 Mar 2017 18:48:48 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1489456128; bh=aqt7b81a7qMsSte9tRvaPfQ5WWtzkaoJhHyLfT1b/hY=; h=From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=e/Px6iMHqqfd9EzjovMEau+dvatJ9GaNUh1AtcQ5QzLNYOqm84YPuQXXqid3EZ8hw xXbsVhvPp6dE6zq75rybHCZ4jA+5D7YBZrlljPi5CkBehPx3OZGVhqCHonyIu4FCId 3wmPhA25aXIlg58vFwtpcajyYG7WNFzRf/P++MMs=
From: Sean Turner <notifications@github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/398@github.com>
Subject: [quicwg/base-drafts] TLS Intro (#398)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_58c74c00daf55_5d623fa2955c1c381259a9"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: seanturner
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/3uq8ZW80c_dgsUydVG-ucCKrTxA>
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: Tue, 14 Mar 2017 01:48:51 -0000
Do we really need the normative references to RFC 7230, 7540, QUIC-HTTP in the intro? Since QUIC isn't supposed to be tied directly to HTTP/2 and frankly anybody reading this document would have gotten to QUIC-TLS through QUIC-TRANSPORT (i.e., they drank the koolaid) couldn't we drop the 1st para and work the QUIC-TRANSPORT reference in as follows:
This document describes how QUIC [QUIC-TRANSPORT] can
be secured using Transport Layer Security (TLS) version 1.3
[I-D.ietf-tls-tls13]. TLS 1.3 provides critical latency ...
--
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/398
- [quicwg/base-drafts] TLS Intro (#398) Sean Turner
- Re: [quicwg/base-drafts] TLS Intro (#398) Sean Turner
- Re: [quicwg/base-drafts] TLS Intro (#398) Sean Turner