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

Nick Banks <notifications@github.com> Fri, 20 July 2018 18:55 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 82EAF130DF1 for <quic-issues@ietfa.amsl.com>; Fri, 20 Jul 2018 11:55:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.009
X-Spam-Level:
X-Spam-Status: No, score=-8.009 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, 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 WeUf9rdBdM_W for <quic-issues@ietfa.amsl.com>; Fri, 20 Jul 2018 11:55:30 -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 6C6CE130DCE for <quic-issues@ietf.org>; Fri, 20 Jul 2018 11:55:30 -0700 (PDT)
Date: Fri, 20 Jul 2018 11:55:29 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1532112929; bh=VwhkHyZLIlByxQiGVH/wjHz0cfB2BPzByqaoBnL9kqQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=oOonaIvKDXYUV0yZ28wvYjq15aP0LogCLhx+Ec5KyxPIFaMpa5lSolg4I0NGS1agd xF1hXMm5cA4W8aWb5bC2vsXIy6sfGzILEW1zM/RIBQCIWjxCOJ6dqeZchXFOMxBjIX 1MLpnBjVSACR9+v/vIxHlHejLrnMZWn36KNjmytM=
From: Nick Banks <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab777810ad399c5b3e176209aa6112fbcdc8d79d9e92cf000000011769f22192a169ce1474a4c7@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/406696243@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_5b523021c500a_251e3faee76d45b8189597"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: nibanks
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/DOgViDDAAh-h1UeA_L9N_1cIEak>
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: Fri, 20 Jul 2018 18:55:35 -0000

I wouldn't say we had exactly that, as now we are much more explicit with encryption level (as there are 4 different ones). Why do you say that was a pain point? I feel that is a much cleaner and explicit design to implement.

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