[quicwg/base-drafts] Payload length in header encrypted with sequence number (#1293)
Christian Huitema <notifications@github.com> Sat, 14 April 2018 00:52 UTC
Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 141661204DA for <quic-issues@ietfa.amsl.com>; Fri, 13 Apr 2018 17:52:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.605
X-Spam-Level:
X-Spam-Status: No, score=-1.605 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_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, 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 iAHdH-NmHS_8 for <quic-issues@ietfa.amsl.com>; Fri, 13 Apr 2018 17:52:20 -0700 (PDT)
Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E422912D944 for <quic-issues@ietf.org>; Fri, 13 Apr 2018 17:52:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=JCgy404ZuYqz/a1hg9tfcAfjzU8=; b=kJBw5U2s83Czvo+7 IsGKaU9oXen6Ggiwpw/43Cqeyls7wxXzcYsSsRIF5dfU8B4rrSFLfW7990czEsO6 h64nMVwY/Xx1E/3SP9Pl6qNCpdG6s0E1yY5Q6AwlPT77SqdXyVJsxMcm0hHN53Wo 1ZTyYjvVC//fEN5JwgfKsWaL0V4=
Received: by filter0043p1las1.sendgrid.net with SMTP id filter0043p1las1-29166-5AD150C1-14 2018-04-14 00:52:17.398886121 +0000 UTC
Received: from smtp.github.com (out-2.smtp.github.com [192.30.252.193]) by ismtpd0045p1mdw1.sendgrid.net (SG) with ESMTP id aFoc-iEwTzCM3xFE9CqUMA for <quic-issues@ietf.org>; Sat, 14 Apr 2018 00:52:17.145 +0000 (UTC)
Date: Sat, 14 Apr 2018 00:52:17 +0000
From: Christian Huitema <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abf82330b9fc88b37298e1ab7b3c9620c693c42c1292cf0000000116e912c092a169ce12bb9fbb@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1293@github.com>
Subject: [quicwg/base-drafts] Payload length in header encrypted with sequence number (#1293)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ad150c0e36f1_51a53f8ca635ef2c34088"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: huitema
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3WyU4P9NAqH4x+GfebDtpXD9GP4Jryvpo4rj 0jGiCSYMZ11xpmoD+WsX+vuFr75pF+gJEpgqPbqufrh0f85maS50ecNYaVATR+SZWJoF7zaZDxC/yi XoSq5zgzplq0BCBKyHbUCUVpB3msYjRjsc3eyfDj7tQh5m7e7t6bdIm1i1lANIJjk9StF/8ol+P/Ur k=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/xK6aeykoAsbrcMkJElto2Ewl5DU>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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, 14 Apr 2018 00:52:22 -0000
There is an interesting feature interaction between PN encryption and the encoding of the payload length in the header. The current specification of PN encryption (PR #1079) specifies encrypting the 16 byte field starting at the offset of the packet number. The current specification of the long header places the payload length *after* the packet number. So the payload length gets encrypted with the packet number. And that's a royal pain, because that means the payload length cannot be assessed before decrypting the packet number. -- 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/1293
- [quicwg/base-drafts] Payload length in header enc… Christian Huitema
- Re: [quicwg/base-drafts] Payload length in header… Christian Huitema
- Re: [quicwg/base-drafts] Payload length in header… Mike Bishop
- Re: [quicwg/base-drafts] Payload length in header… Christian Huitema
- Re: [quicwg/base-drafts] Payload length in header… Christian Huitema
- Re: [quicwg/base-drafts] Payload length in header… Christian Huitema
- Re: [quicwg/base-drafts] Payload length in header… Christian Huitema