[dtn] [Editorial Errata Reported] RFC9173 (7002)
RFC Errata System <rfc-editor@rfc-editor.org> Tue, 21 June 2022 04:12 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: dtn@ietfa.amsl.com
Delivered-To: dtn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E34C7C157B41 for <dtn@ietfa.amsl.com>; Mon, 20 Jun 2022 21:12:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.657
X-Spam-Level:
X-Spam-Status: No, score=-1.657 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RqyuMVFQ_VPt for <dtn@ietfa.amsl.com>; Mon, 20 Jun 2022 21:12:35 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66FA8C157B3E for <dtn@ietf.org>; Mon, 20 Jun 2022 21:12:35 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 3815BEC276; Mon, 20 Jun 2022 21:12:35 -0700 (PDT)
To: rfc-editor@rfc-editor.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: ebirrane@gmail.com, edward.birrane@jhuapl.edu, alex.white@jhuapl.edu, sarah.heiner@jhuapl.edu, dtn@ietf.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20220621041235.3815BEC276@rfcpa.amsl.com>
Date: Mon, 20 Jun 2022 21:12:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dtn/XP6b1JphRqCccunISVxVGtCINps>
Subject: [dtn] [Editorial Errata Reported] RFC9173 (7002)
X-BeenThere: dtn@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Delay Tolerant Networking \(DTN\) discussion list at the IETF." <dtn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dtn>, <mailto:dtn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dtn/>
List-Post: <mailto:dtn@ietf.org>
List-Help: <mailto:dtn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dtn>, <mailto:dtn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jun 2022 04:12:36 -0000
The following errata report has been submitted for RFC9173, "Default Security Contexts for Bundle Protocol Security (BPSec)". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid7002 -------------------------------------- Type: Editorial Reported by: Ed Birrane <ebirrane@gmail.com> Section: A.4.4.1 Original Text ------------- This BCB has two targets: the payload block and BIB. Corrected Text -------------- This BCB has two targets: the payload block and BIB. NOTE: This example implies using a single Initialization Vector (IV) for two separate encryptions (a BIB and the payload). This violates the requirement in Section 4.3.1 that the "initialization vector ... MUST NOT be reused for multiple encryptions using the same encryption key.". When using the BCB-AES-GCM security context containing a specified Initialization Vector, each BCB should have only one security target. Notes ----- This is listed as "editorial" and not technical because the error appears in a non-normative portion of the document. Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party can log in to change the status and edit the report, if necessary. -------------------------------------- RFC9173 (draft-ietf-dtn-bpsec-default-sc-11) -------------------------------------- Title : Default Security Contexts for Bundle Protocol Security (BPSec) Publication Date : January 2022 Author(s) : E. Birrane, III, A. White, S. Heiner Category : PROPOSED STANDARD Source : Delay/Disruption Tolerant Networking Area : Transport Stream : IETF Verifying Party : IESG
- [dtn] [Editorial Errata Reported] RFC9173 (7002) RFC Errata System