RFC 7860 on HMAC-SHA-2 Authentication Protocols in User-Based Security Model (USM) for SNMPv3
rfc-editor@rfc-editor.org Sat, 30 April 2016 03:13 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 5B59612D65A; Fri, 29 Apr 2016 20:13:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.898
X-Spam-Level:
X-Spam-Status: No, score=-107.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham 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 PNAE5BBiTNn6; Fri, 29 Apr 2016 20:13:40 -0700 (PDT)
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 8394812B035; Fri, 29 Apr 2016 20:13:40 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 1E913180003; Fri, 29 Apr 2016 20:13:20 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7860 on HMAC-SHA-2 Authentication Protocols in User-Based Security Model (USM) for SNMPv3
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160430031320.1E913180003@rfc-editor.org>
Date: Fri, 29 Apr 2016 20:13:20 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/UWXFIV52L4Muhiz-g--CiDHHtoA>
Cc: drafts-update-ref@iana.org, opsawg@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
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: Sat, 30 Apr 2016 03:13:42 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7860
Title: HMAC-SHA-2 Authentication Protocols in User-Based
Security Model (USM) for SNMPv3
Author: J. Merkle, Ed.,
M. Lochter
Status: Standards Track
Stream: IETF
Date: April 2016
Mailbox: johannes.merkle@secunet.com,
manfred.lochter@bsi.bund.de
Pages: 14
Characters: 29329
Obsoletes: RFC 7630
I-D Tag: draft-ietf-opsawg-hmac-sha-2-usm-snmp-new-05.txt
URL: https://www.rfc-editor.org/info/rfc7860
DOI: http://dx.doi.org/10.17487/RFC7860
This document specifies several authentication protocols based on the
SHA-2 hash functions for the User-based Security Model (USM) for
SNMPv3 defined in RFC 3414. It obsoletes RFC 7630, in which the MIB
MODULE-IDENTITY value was incorrectly specified.
This document is a product of the Operations and Management Area Working Group 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