RFC 6094 on Summary of Cryptographic Authentication Algorithm Implementation Requirements for Routing Protocols

rfc-editor@rfc-editor.org Thu, 03 February 2011 04:00 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id C462D3A67CC; Wed, 2 Feb 2011 20:00:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.306
X-Spam-Status: No, score=-102.306 tagged_above=-999 required=5 tests=[AWL=0.294, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id BDitSDjPV52x; Wed, 2 Feb 2011 20:00:46 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 3E0BB3A6778; Wed, 2 Feb 2011 20:00:44 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id D031EE0746; Wed, 2 Feb 2011 20:04:05 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6094 on Summary of Cryptographic Authentication Algorithm Implementation Requirements for Routing Protocols
From: rfc-editor@rfc-editor.org
Message-Id: <20110203040405.D031EE0746@rfc-editor.org>
Date: Wed, 2 Feb 2011 20:04:05 -0800 (PST)
Cc: opsec@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Thu, 03 Feb 2011 04:00:47 -0000

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

        RFC 6094

        Title:      Summary of Cryptographic Authentication Algorithm 
                    Implementation Requirements for Routing Protocols 
        Author:     M. Bhatia, V. Manral
        Status:     Informational
        Stream:     IETF
        Date:       February 2011
        Mailbox:    manav.bhatia@alcatel-lucent.com, 
        Pages:      11
        Characters: 24583
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-opsec-igp-crypto-requirements-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6094.txt

The routing protocols Open Shortest Path First version 2 (OSPFv2),
Intermediate System to Intermediate System (IS-IS), and Routing
Information Protocol (RIP) currently define cleartext and MD5
(Message Digest 5) methods for authenticating protocol packets.
Recently, effort has been made to add support for the SHA (Secure
Hash Algorithm) family of hash functions for the purpose of
authenticating routing protocol packets for RIP, IS-IS, and OSPF.

To encourage interoperability between disparate implementations, it
is imperative that we specify the expected minimal set of algorithms,
thereby ensuring that there is at least one algorithm that all
implementations will have in common.

Similarly, RIP for IPv6 (RIPng) and OSPFv3 support IPsec algorithms
for authenticating their protocol packets.

This document examines the current set of available algorithms, with
interoperability and effective cryptographic authentication
protection being the principal considerations.  Cryptographic
authentication of these routing protocols requires the availability
of the same algorithms in disparate implementations.  It is desirable
that newly specified algorithms should be implemented and available
in routing protocol implementations because they may be promoted to
requirements at some future time.  This document is not an Internet 
Standards Track specification; it is published for informational purposes.

This document is a product of the Operational Security Capabilities for IP Network Infrastructure Working Group of the IETF.

INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

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