IETF Logo Mail Archive

Re: [quicwg/base-drafts] Minor TLS draft editorial corrections (#2446)

MikkelFJ <notifications@github.com> Sat, 09 February 2019 20:30 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 0A920130E76 for <quic-issues@ietfa.amsl.com>; Sat, 9 Feb 2019 12:30:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.597
X-Spam-Level:
X-Spam-Status: No, score=-6.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 o0wq6ednXMk6 for <quic-issues@ietfa.amsl.com>; Sat, 9 Feb 2019 12:30:01 -0800 (PST)
Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C71E6130E5B for <quic-issues@ietf.org>; Sat, 9 Feb 2019 12:30:00 -0800 (PST)
Date: Sat, 09 Feb 2019 12:29:59 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1549744199; bh=zICTDBMH0MiDHPyTWIZGU8TyYGEuiPgullePlpQz6Bk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=vJBkuWxWk2NyQdvdmfKOW/lKKiqSwFlCiCapvQSBcbJDfTGfs9L1kx2bjnxrQrPSe BExFgHfybBxraHTPTZro90SYMJf7zjJsDYgUigkqQquMcz7Bcq2cpE8YSpsyQUmZjb +4QdjkVDeV/AoS/kIS3ANVYWuY9BNXcthp2K3iQw=
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab4af64fc877db83758155857dc55902ac4bcec21692cf000000011876fa4792a169ce18577d38@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2446/review/201877065@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2446@github.com>
References: <quicwg/base-drafts/pull/2446@github.com>
Subject: Re: [quicwg/base-drafts] Minor TLS draft editorial corrections (#2446)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c5f38475cfba_66083fa316ad45b4156833"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
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/LSVyGcKn-wWJ4hCk_Au7qz7RZxU>
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: Sat, 09 Feb 2019 20:30:03 -0000

mikkelfj commented on this pull request.



> @@ -269,7 +271,7 @@ At a high level, there are two main interactions between the TLS and QUIC
 components:
 
 * The TLS component sends and receives messages via the QUIC component, with
-  QUIC providing a reliable stream abstraction to TLS.
+  QUIC providing a reliable stream and record abstraction to TLS.
 

Well, not sure about 14, possibly, but the big change was to remove TLS encryption layer piped through already encrypted QUIC. But as I understand it, TLS still maintains its own record structure and framing within the QUIC crypto stream. So in a sense it both is and isn't TLS records.

-- 
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/2446#discussion_r255312408

v2.30.2 | Report a Bug | By Email | System Status