Re: [quicwg/base-drafts] Single Stream of Bytes for CRYPTO Frames (#1592)

ekr <notifications@github.com> Sat, 21 July 2018 13:59 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 779AB12426A for <quic-issues@ietfa.amsl.com>; Sat, 21 Jul 2018 06:59:41 -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 ygw9i71KCsHt for <quic-issues@ietfa.amsl.com>; Sat, 21 Jul 2018 06:59:39 -0700 (PDT)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [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 0A4C1124C04 for <quic-issues@ietf.org>; Sat, 21 Jul 2018 06:59:38 -0700 (PDT)
Date: Sat, 21 Jul 2018 06:59:37 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1532181577; bh=faxl/Hr9K05+5BbPSnsd9yhhDGaXpUET1UAcZWS7XO4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=hNHSxtgriA6QDfmwAhW0kLYh7qxKlyU7yZkKlitxSwCUMOvlaRy0l763bRSrApJNl frCJpE3d1yVELjfG2FDgVS5ZzOJghoOJT853jT933zofksclfUV9XuvhXt4epxFc1X loFTvgagO3miNQnwdRaunLokJYxnMVN3moYoO4bs=
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab8a9d60e965a6bf030d67a0e3299b42de8e8db93f92cf00000001176afe4992a169ce1474a4c7@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1592/406798567@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1592@github.com>
References: <quicwg/base-drafts/issues/1592@github.com>
Subject: Re: [quicwg/base-drafts] Single Stream of Bytes for CRYPTO Frames (#1592)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b533c49ec64c_97d3febaf0d45b46590d0"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
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/kD4GE_J8y8PQ-AljwlOJfSP264k>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.27
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, 21 Jul 2018 13:59:42 -0000

I prefer the "starts at zero" structure. I found it much easier to just
have separate flows and then not have to worry about data coming on one
encryption level that had offsets appropriate to another encryption level.

On Fri, Jul 20, 2018 at 1:08 PM, Nick Banks <notifications@github.com>
wrote:

> I know the design team suggested the CRYPTO frame design. I was part of
> the design team. At the time, in the theoretical sense it all made sense.
> After implementing it, I have seen some issues. Also, I agree one
> implementation experience isn't enough to change things outright, but it's
> enough to open an issue and have the discussion.
>
> I'm not arguing to undo everything. I am just trying to consolidate things
> I see as bloated and overly complex. I very much like the design of
> multiple encryption levels. All I am arguing for is a change in how each
> starts its offset.
>
> If folks still generally believe the current way we have offsets is
> better, then so be it. That is not my experience, so that's why I opened
> the issue.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/quicwg/base-drafts/issues/1592#issuecomment-406713278>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ABD1ofVNBO5BCXpt1c95QpAKPlm4r5Jqks5uIji8gaJpZM4VYkas>
> .
>


-- 
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/1592#issuecomment-406798567