Re: [quicwg/base-drafts] clarify how to detect a misbehaving peer (43943c1)

MikkelFJ <> Wed, 19 June 2019 13:19 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 57F0A1205DA for <>; Wed, 19 Jun 2019 06:19:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.463
X-Spam-Status: No, score=-6.463 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_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, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 8c4eV7R2gYr3 for <>; Wed, 19 Jun 2019 06:19:23 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id BA8821204A7 for <>; Wed, 19 Jun 2019 06:19:23 -0700 (PDT)
Date: Wed, 19 Jun 2019 06:19:22 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1560950362; bh=3I32h98XhK+r/LlZo5aSqkjz7hhRqvVNq7hShsIbdH8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=OD4t8W2k5Bq8zsIZ1iOvryoG3BzY817pyc5x73EXkhXSlIJ++Q9HEGH/jbjwX5tjE GHwCkznFKuLvSMetwPkesUBXLdoC5eJmEvYgWnFK36wgAh1sr6q7pdNTJ9A0UY6UYw wj7O02SaI4IZDPi8IJ7WAjDgwSrdp5g5ux5tjos8=
From: MikkelFJ <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/commit/43943c1290aac062ff52171f7053d09e611a7d07/>
In-Reply-To: <quicwg/base-drafts/commit/>
References: <quicwg/base-drafts/commit/>
Subject: Re: [quicwg/base-drafts] clarify how to detect a misbehaving peer (43943c1)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d0a365aacec4_753b3f9d8bacd95c29422d"; 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
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 19 Jun 2019 13:19:32 -0000

That is fine. I'm wondering if we should warn about DoS attack if this detection is done sloppily?

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: