[OPSAWG] RFC 7630 on HMAC-SHA-2 Authentication Protocols in the User-based Security Model (USM) for SNMPv3

rfc-editor@rfc-editor.org Wed, 14 October 2015 23:50 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AB6D1A9026; Wed, 14 Oct 2015 16:50:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
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 h4ewc-8FtyIC; Wed, 14 Oct 2015 16:50:05 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 0D8A51A901E; Wed, 14 Oct 2015 16:50:05 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id AB4C31832B6; Wed, 14 Oct 2015 16:49:51 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20151014234951.AB4C31832B6@rfc-editor.org>
Date: Wed, 14 Oct 2015 16:49:51 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/opsawg/a0UpWSQW7abGOzE0mizEA2EgJ5s>
Cc: drafts-update-ref@iana.org, opsawg@ietf.org, rfc-editor@rfc-editor.org
Subject: [OPSAWG] RFC 7630 on HMAC-SHA-2 Authentication Protocols in the User-based Security Model (USM) for SNMPv3
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Oct 2015 23:50:06 -0000

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

        
        RFC 7630

        Title:      HMAC-SHA-2 Authentication Protocols in the 
                    User-based Security Model (USM) for SNMPv3 
        Author:     J. Merkle, Ed.,
                    M. Lochter
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2015
        Mailbox:    johannes.merkle@secunet.com, 
                    manfred.lochter@bsi.bund.de
        Pages:      14
        Characters: 29324
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-opsawg-hmac-sha-2-usm-snmp-06.txt

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

        DOI:        http://dx.doi.org/10.17487/RFC7630

This memo specifies new HMAC-SHA-2 authentication protocols for the
User-based Security Model (USM) for SNMPv3 defined in RFC 3414.

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/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