RFC 5709 on OSPFv2 HMAC-SHA Cryptographic Authentication

rfc-editor@rfc-editor.org Thu, 22 October 2009 23:47 UTC

Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 417F128C19E; Thu, 22 Oct 2009 16:47:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.916
X-Spam-Level:
X-Spam-Status: No, score=-16.916 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id urJRhK6K9rJS; Thu, 22 Oct 2009 16:47:16 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 6F72428C198; Thu, 22 Oct 2009 16:47:16 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id D2828350153; Thu, 22 Oct 2009 16:44:47 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5709 on OSPFv2 HMAC-SHA Cryptographic Authentication
From: rfc-editor@rfc-editor.org
Message-Id: <20091022234447.D2828350153@bosco.isi.edu>
Date: Thu, 22 Oct 2009 16:44:47 -0700 (PDT)
Cc: ospf@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, 22 Oct 2009 23:47:17 -0000

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

        
        RFC 5709

        Title:      OSPFv2 HMAC-SHA Cryptographic Authentication 
        Author:     M. Bhatia, V. Manral,
                    M. Fanto, R. White,
                    M. Barnes, T. Li,
                    R. Atkinson
        Status:     Standards Track
        Date:       October 2009
        Mailbox:    manav@alcatel-lucent.com, 
                    vishwas@ipinfusion.com, 
                    mfanto@aegisdatasecurity.com,
                    riw@cisco.com, 
                    mjbarnes@cisco.com,
                    tony.li@tony.li, 
                    rja@extremenetworks.com
        Pages:      14
        Characters: 30221
        Updates:    RFC2328

        I-D Tag:    draft-ietf-ospf-hmac-sha-07.txt

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

This document describes how the National Institute of Standards and
Technology (NIST) Secure Hash Standard family of
algorithms can be used with OSPF version 2's built-in, cryptographic
authentication mechanism.  This updates, but does not supercede,
the cryptographic authentication mechanism specified in RFC 2328.
[STANDARDS TRACK]

This document is a product of the Open Shortest Path First IGP Working Group of the IETF.

This is now a Proposed Standard Protocol.

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 Internet
Official Protocol Standards (STD 1) 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
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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
USC/Information Sciences Institute