RFC 8967 on MAC Authentication for the Babel Routing Protocol

rfc-editor@rfc-editor.org Mon, 11 January 2021 20:39 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6107E3A1427; Mon, 11 Jan 2021 12:39:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.902
X-Spam-Level:
X-Spam-Status: No, score=-0.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.998, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 7Vn2JPYJLqNl; Mon, 11 Jan 2021 12:39:47 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6C0F3A1213; Mon, 11 Jan 2021 12:39:20 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 7831BF40761; Mon, 11 Jan 2021 12:39:12 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8967 on MAC Authentication for the Babel Routing Protocol
X-PHP-Originating-Script: 1005:ams_util_lib.php
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: <20210111203912.7831BF40761@rfc-editor.org>
Date: Mon, 11 Jan 2021 12:39:12 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/J9DdgxzystUkFXBRvJd32nogtrc>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jan 2021 20:39:55 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8967

        Title:      MAC Authentication for the Babel 
                    Routing Protocol 
        Author:     C. Dô,
                    W. Kolodziejak,
                    J. Chroboczek
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2021
        Mailbox:    clarado_perso@yahoo.fr, 
                    weronika.kolodziejak@gmail.com, 
                    jch@irif.fr
        Pages:      17
        Obsoletes:  RFC 7298

        I-D Tag:    draft-ietf-babel-hmac-12.txt

        URL:        https://www.rfc-editor.org/info/rfc8967

        DOI:        10.17487/RFC8967

This document describes a cryptographic authentication mechanism for
the Babel routing protocol that has provisions for replay avoidance. 
This document obsoletes RFC 7298.

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