[OPSAWG] RFC 9456 on Updates to the TLS Transport Model for SNMP
rfc-editor@rfc-editor.org Wed, 08 November 2023 10:42 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58B03C18E55C; Wed, 8 Nov 2023 02:42:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.467
X-Spam-Level:
X-Spam-Status: No, score=-4.467 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_HELO_SOFTFAIL=0.732, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id drfSXr5WRYTb; Wed, 8 Nov 2023 02:42:17 -0800 (PST)
Received: from rfcpa.amsl.com (unknown [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF211C198470; Wed, 8 Nov 2023 02:42:17 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 8B86A119CD; Wed, 8 Nov 2023 02:42:17 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, opsawg@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20231108104217.8B86A119CD@rfcpa.amsl.com>
Date: Wed, 08 Nov 2023 02:42:17 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/RZ2Kucgk_J173FECkZQH0kTq9U8>
Subject: [OPSAWG] RFC 9456 on Updates to the TLS Transport Model for SNMP
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.39
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, 08 Nov 2023 10:42:21 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9456
Title: Updates to the TLS Transport Model for SNMP
Author: K. Vaughn, Ed.
Status: Standards Track
Stream: IETF
Date: November 2023
Mailbox: kvaughn@trevilon.com
Pages: 30
Updates: RFC 6353
I-D Tag: draft-ietf-opsawg-tlstm-update-15.txt
URL: https://www.rfc-editor.org/info/rfc9456
DOI: 10.17487/RFC9456
This document updates RFC 6353 ("Transport Layer Security (TLS)
Transport Model for the Simple Network Management Protocol (SNMP)")
to reflect changes necessary to support Transport Layer Security
version 1.3 (TLS 1.3) and Datagram Transport Layer Security version
1.3 (DTLS 1.3), which are jointly known as "(D)TLS 1.3". This
document is compatible with (D)TLS 1.2 and is intended to be
compatible with future versions of SNMP and (D)TLS.
This document updates the SNMP-TLS-TM-MIB as defined in RFC 6353.
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