Re: [quicwg/base-drafts] Padding requirement seems to be incorrect. (#3053)
ekr <notifications@github.com> Thu, 10 October 2019 21:34 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 AE822120808 for <quic-issues@ietfa.amsl.com>; Thu, 10 Oct 2019 14:34:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Level:
X-Spam-Status: No, score=-6.454 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_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, 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 YpZcfbaBqkPj for <quic-issues@ietfa.amsl.com>; Thu, 10 Oct 2019 14:34:25 -0700 (PDT)
Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D74912080B for <quic-issues@ietf.org>; Thu, 10 Oct 2019 14:34:25 -0700 (PDT)
Date: Thu, 10 Oct 2019 14:34:24 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1570743264; bh=ncCW0kOTj9kbI0p33JkPfOroo8LZuk5BVlvVT9OOAc0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=HSmSjMuv1seK2nxYjHDauWHeARIamacXIRx7uP16aS9lkleReJO1LXb4CfRKbeN9s /eluOifHckwf4I8NPWtN4fTkt33LT5C9+WrPEGwpzosavm/Rf9uhtPhZ88ZeIvclET KyCEyFpLF+DwuqqFT2LcxAY2t25BDEsp5VdgyxbM=
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK5DHPA35OTPDMKMDPN3VTSHBEVBNHHB3EM4KU@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3053/540809958@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3053@github.com>
References: <quicwg/base-drafts/issues/3053@github.com>
Subject: Re: [quicwg/base-drafts] Padding requirement seems to be incorrect. (#3053)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d9fa3e09df9b_6c573facb04cd9601390bb"; 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/q2BB2sLDO0qcRbkdJ5K05Comh4A>
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: Thu, 10 Oct 2019 21:34:29 -0000
I don't understand what "pads the datagram as though no other packets were present" is supposed to mean, then. The way neqo does this is that it puts the packets in the datagram and then pads the rest, without any regard to what keys the server might have. -- 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/3053#issuecomment-540809958
- [quicwg/base-drafts] Padding requirement seems to… Kazuho Oku
- Re: [quicwg/base-drafts] Padding requirement seem… Martin Thomson
- Re: [quicwg/base-drafts] Padding requirement seem… MikkelFJ
- Re: [quicwg/base-drafts] Padding requirement seem… ianswett
- Re: [quicwg/base-drafts] Padding requirement seem… David Schinazi
- Re: [quicwg/base-drafts] Padding requirement seem… Kazuho Oku
- Re: [quicwg/base-drafts] Padding requirement seem… Martin Thomson
- Re: [quicwg/base-drafts] Padding requirement seem… Martin Thomson
- Re: [quicwg/base-drafts] Padding requirement seem… MikkelFJ
- Re: [quicwg/base-drafts] Padding requirement seem… Kazuho Oku
- Re: [quicwg/base-drafts] Padding requirement seem… ekr
- Re: [quicwg/base-drafts] Padding requirement seem… David Schinazi
- Re: [quicwg/base-drafts] Padding requirement seem… ekr
- Re: [quicwg/base-drafts] Padding requirement seem… David Schinazi
- Re: [quicwg/base-drafts] Padding requirement seem… MikkelFJ
- Re: [quicwg/base-drafts] Padding requirement seem… ekr
- Re: [quicwg/base-drafts] Padding requirement seem… Martin Thomson
- Re: [quicwg/base-drafts] Padding requirement seem… ekr
- Re: [quicwg/base-drafts] Padding requirement seem… MikkelFJ
- Re: [quicwg/base-drafts] Padding requirement seem… Mike Bishop
- Re: [quicwg/base-drafts] Padding requirement seem… ekr
- Re: [quicwg/base-drafts] Padding requirement seem… Martin Thomson
- Re: [quicwg/base-drafts] Padding requirement seem… ekr
- Re: [quicwg/base-drafts] Padding requirement seem… Martin Thomson
- Re: [quicwg/base-drafts] Padding requirement seem… Lars Eggert
- Re: [quicwg/base-drafts] Padding requirement seem… Martin Thomson