[babel] RFC 9467 on Relaxed Packet Counter Verification for Babel MAC Authentication
rfc-editor@rfc-editor.org Tue, 16 January 2024 21:30 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D889C15154F; Tue, 16 Jan 2024 13:30:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.657
X-Spam-Level:
X-Spam-Status: No, score=-6.657 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, 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=ham 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 8msSa6OTOW3e; Tue, 16 Jan 2024 13:30:34 -0800 (PST)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [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 84D6DC14F6E1; Tue, 16 Jan 2024 13:29:30 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 50250B3AF0; Tue, 16 Jan 2024 13:29:30 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, babel@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240116212930.50250B3AF0@rfcpa.amsl.com>
Date: Tue, 16 Jan 2024 13:29:30 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/eXNaYhJAGVtWklH0R7Fy5bNYSoY>
Subject: [babel] RFC 9467 on Relaxed Packet Counter Verification for Babel MAC Authentication
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jan 2024 21:30:38 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9467
Title: Relaxed Packet Counter Verification for
Babel MAC Authentication
Author: J. Chroboczek,
T. Høiland-Jørgensen
Status: Standards Track
Stream: IETF
Date: January 2024
Mailbox: jch@irif.fr,
toke@toke.dk
Pages: 8
Updates: RFC 8967
I-D Tag: draft-ietf-babel-mac-relaxed-05.txt
URL: https://www.rfc-editor.org/info/rfc9467
DOI: 10.17487/RFC9467
This document relaxes the packet verification rules defined in "MAC
Authentication for the Babel Routing Protocol" (RFC 8967) in order to
make the protocol more robust in the presence of packet reordering.
This document updates RFC 8967.
This document is a product of the Babel routing protocol Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC