[quicwg/base-drafts] Should the following text be formatted using <aside>? (comment 7) (Issue #4973)

Lucas Pardue <notifications@github.com> Fri, 25 March 2022 17:40 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 CB9BB3A1758 for <quic-issues@ietfa.amsl.com>; Fri, 25 Mar 2022 10:40:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.695
X-Spam-Level:
X-Spam-Status: No, score=-1.695 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, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-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 gaDSLXc5ecxP for <quic-issues@ietfa.amsl.com>; Fri, 25 Mar 2022 10:40:31 -0700 (PDT)
Received: from smtp.github.com (out-21.smtp.github.com [192.30.252.204]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95FDE3A173D for <quic-issues@ietf.org>; Fri, 25 Mar 2022 10:40:31 -0700 (PDT)
Received: from github-lowworker-ca235ff.ash1-iad.github.net (github-lowworker-ca235ff.ash1-iad.github.net [10.56.110.15]) by smtp.github.com (Postfix) with ESMTP id 2E052521A02 for <quic-issues@ietf.org>; Fri, 25 Mar 2022 10:40:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1648230030; bh=s+f9dXHnCAVhxngg3TuMrAZgWOrOuLwuJRrF0X8VlWc=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=QpnUHTBU9jqzQFIuJnRtiP4DbL2QBn0uuPYO+acTZKqea5J1s1upDcCxecZxa+9Xo wxMY0DRghNxkvMjqlKmvYi9f9ej4mYq4YYC5rIE/XBA3g0bXp0iEOwWCVCee7WfSwF YGNJ9eZZ79Ikmj2++h8Xjc4eLj0qdEz6zm8aydIw=
Date: Fri, 25 Mar 2022 10:40:30 -0700
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK47NUJLXS5UQTJEOOGAJMYQ5EVBNHHEMZM6JM@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/4973@github.com>
Subject: [quicwg/base-drafts] Should the following text be formatted using <aside>? (comment 7) (Issue #4973)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_623dfe8e2023b_67dbc6fc1572c7"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
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/rMIfqBOaaHfCRcDbw46K8kjLg9o>
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: Fri, 25 Mar 2022 17:40:36 -0000

Should the following text be formatted using <aside>?  See the definition at <https://authors.ietf.org/rfcxml-vocabulary#aside>.

Original:

       Note:  Padding schemes only provide limited protection against an
          attacker with these capabilities, potentially only forcing an
          increased number of guesses to learn the length associated with a
          given guess.  Padding schemes also work directly against
          compression by increasing the number of bits that are transmitted.

Original:

       Note:  Simply removing entries corresponding to the field from the
          dynamic table can be ineffectual if the attacker has a reliable
          way of causing values to be reinstalled.  For example, a request
          to load an image in a web browser typically includes the Cookie
          header field (a potentially highly valued target for this sort of
          attack), and websites can easily force an image to be loaded,
          thereby refreshing the entry in the dynamic table.



-- 
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/4973
You are receiving this because you are subscribed to this thread.

Message ID: <quicwg/base-drafts/issues/4973@github.com>