Re: [quicwg/base-drafts] Make intro more accessible (#1789)
ianswett <notifications@github.com> Mon, 24 September 2018 22:51 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 09CE1131154 for <quic-issues@ietfa.amsl.com>; Mon, 24 Sep 2018 15:51:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Level:
X-Spam-Status: No, score=-8.01 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 Omvg0XPJMk3E for <quic-issues@ietfa.amsl.com>; Mon, 24 Sep 2018 15:51:48 -0700 (PDT)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B6D9131127 for <quic-issues@ietf.org>; Mon, 24 Sep 2018 15:51:48 -0700 (PDT)
Date: Mon, 24 Sep 2018 15:51:47 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1537829507; bh=3MKvVOb1kCIsTdNt7XXzz8ZwKKwzy2Fl2zG26s6b92k=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=T90C4fKeaMCpFGqY5GoYs3o/XUWjgwE1w6rHEwd0CREbGDEdDA5TdVZZNAYLOKk9l ZHonkpdYVH5lksI9FKmjKg5XoJk+Zou0SlYh+owkpT6n6G+Ih2nmKts01Q1yUvwbyK IdFkDYGSdO4y6kCFL2bvrXezcscTTVhNIDS8KEw8=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abd2a9959de3d8146ec2ce0c667d2cc19f61ce598192cf0000000117c12c8392a169ce15a77b1e@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/1789/review/158325001@github.com>
In-Reply-To: <quicwg/base-drafts/pull/1789@github.com>
References: <quicwg/base-drafts/pull/1789@github.com>
Subject: Re: [quicwg/base-drafts] Make intro more accessible (#1789)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ba96a83a345c_5c353fb079ad45bc120028"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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/Zm6JmCzL__nl8IRb_Ts2k1zIE-U>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 24 Sep 2018 22:51:50 -0000
ianswett commented on this pull request. > @@ -128,15 +128,16 @@ general-purpose secure transport for multiple applications. * Connection migration and resilience to NAT rebinding -QUIC implements techniques learned from experience with TCP, SCTP and other -transport protocols. QUIC uses UDP as substrate so as to not require changes to -legacy client operating systems and middleboxes to be deployable. QUIC -authenticates all of its headers and encrypts most of the data it exchanges, -including its signaling. This allows the protocol to evolve without incurring a -dependency on upgrades to middleboxes. This document describes the core QUIC -protocol, including the conceptual design, wire format, and mechanisms of the -QUIC protocol for connection establishment, stream multiplexing, stream and -connection-level flow control, connection migration, and data reliability. +QUIC uses UDP as substrate so as to not require changes to legacy client +operating systems and middleboxes to be deployable. QUIC authenticates all of Agreed, this sentence is awkward. How about "QUIC uses UDP as a substrate to avoid changes to legacy client operating systems and middleboxes in order to be deployed." -- 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/pull/1789#discussion_r220013359
- Re: [quicwg/base-drafts] Make intro more accessib… janaiyengar
- [quicwg/base-drafts] Make intro more accessible (… Martin Thomson
- Re: [quicwg/base-drafts] Make intro more accessib… janaiyengar
- Re: [quicwg/base-drafts] Make intro more accessib… MikkelFJ
- Re: [quicwg/base-drafts] Make intro more accessib… ianswett
- Re: [quicwg/base-drafts] Make intro more accessib… hardie