Diff: rfc9456v5.txt - rfc9456.txt

	rfc9456v5.txt	rfc9456.txt

	Internet Engineering Task Force (IETF) K. Vaughn, Ed.	Internet Engineering Task Force (IETF) K. Vaughn, Ed.
	Request for Comments: 9456 Trevilon LLC	Request for Comments: 9456 Trevilon LLC

	Updates: 6353 September 2023	Updates: 6353 November 2023
	Category: Standards Track	Category: Standards Track
	ISSN: 2070-1721	ISSN: 2070-1721

	Updates to the TLS Transport Model for SNMP	Updates to the TLS Transport Model for SNMP

	Abstract	Abstract

	This document updates RFC 6353 ("Transport Layer Security (TLS)	This document updates RFC 6353 ("Transport Layer Security (TLS)
	Transport Model for the Simple Network Management Protocol (SNMP)")	Transport Model for the Simple Network Management Protocol (SNMP)")
	to reflect changes necessary to support Transport Layer Security	to reflect changes necessary to support Transport Layer Security

	skipping to change at line 289 ¶	skipping to change at line 289 ¶
	an application profile; hence, all the compliance requirements in	an application profile; hence, all the compliance requirements in
	[RFC8446] apply.	[RFC8446] apply.

	4. MIB Module Definitions	4. MIB Module Definitions

	This SNMP-TLS-TM-MIB module imports items from [RFC2578], [RFC2579],	This SNMP-TLS-TM-MIB module imports items from [RFC2578], [RFC2579],
	[RFC2580], [RFC3411], and [RFC3413]. It also references [RFC1123],	[RFC2580], [RFC3411], and [RFC3413]. It also references [RFC1123],
	[RFC5246], [RFC5280], [RFC5591], [RFC5890], [RFC5952], [RFC5953],	[RFC5246], [RFC5280], [RFC5591], [RFC5890], [RFC5952], [RFC5953],
	[RFC6353], and [STD58].	[RFC6353], and [STD58].


	<CODE BEGINS> file "snmp-tls-tm-mib.mib"	<CODE BEGINS> file "SNMP-TLS-TM-MIB"
	SNMP-TLS-TM-MIB DEFINITIONS ::= BEGIN	SNMP-TLS-TM-MIB DEFINITIONS ::= BEGIN

	IMPORTS	IMPORTS
	MODULE-IDENTITY, OBJECT-TYPE,	MODULE-IDENTITY, OBJECT-TYPE,
	OBJECT-IDENTITY, mib-2, snmpDomains,	OBJECT-IDENTITY, mib-2, snmpDomains,
	Counter32, Unsigned32, Gauge32, NOTIFICATION-TYPE	Counter32, Unsigned32, Gauge32, NOTIFICATION-TYPE
	FROM SNMPv2-SMI -- RFC 2578 or any update thereof	FROM SNMPv2-SMI -- RFC 2578 or any update thereof
	TEXTUAL-CONVENTION, TimeStamp, RowStatus, StorageType,	TEXTUAL-CONVENTION, TimeStamp, RowStatus, StorageType,
	AutonomousType	AutonomousType
	FROM SNMPv2-TC -- RFC 2579 or any update thereof	FROM SNMPv2-TC -- RFC 2579 or any update thereof
	MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP	MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
	FROM SNMPv2-CONF -- RFC 2580 or any update thereof	FROM SNMPv2-CONF -- RFC 2580 or any update thereof
	SnmpAdminString	SnmpAdminString
	FROM SNMP-FRAMEWORK-MIB -- RFC 3411 or any update thereof	FROM SNMP-FRAMEWORK-MIB -- RFC 3411 or any update thereof
	snmpTargetParamsName, snmpTargetAddrName	snmpTargetParamsName, snmpTargetAddrName
	FROM SNMP-TARGET-MIB -- RFC 3413 or any update thereof	FROM SNMP-TARGET-MIB -- RFC 3413 or any update thereof
	;	;

	snmpTlstmMIB MODULE-IDENTITY	snmpTlstmMIB MODULE-IDENTITY

	LAST-UPDATED "202308140000Z"	LAST-UPDATED "202310310000Z"

	ORGANIZATION "Operations and Management Area Working Group	ORGANIZATION "Operations and Management Area Working Group
	<mailto:opsawg@ietf.org>"	<mailto:opsawg@ietf.org>"
	CONTACT-INFO	CONTACT-INFO
	"Author: Kenneth Vaughn	"Author: Kenneth Vaughn
	<mailto:kvaughn@trevilon.com>"	<mailto:kvaughn@trevilon.com>"
	DESCRIPTION	DESCRIPTION
	"This is the MIB module for the TLS Transport Model	"This is the MIB module for the TLS Transport Model
	(TLSTM).	(TLSTM).


	skipping to change at line 337 ¶	skipping to change at line 337 ¶
	of the IETF Trust's Legal Provisions Relating to IETF	of the IETF Trust's Legal Provisions Relating to IETF
	Documents (https://trustee.ietf.org/license-info).	Documents (https://trustee.ietf.org/license-info).

	The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL',	The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL',
	'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED',	'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED',
	'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document	'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document
	are to be interpreted as described in BCP 14 (RFC 2119)	are to be interpreted as described in BCP 14 (RFC 2119)
	(RFC 8174) when, and only when, they appear in all	(RFC 8174) when, and only when, they appear in all
	capitals, as shown here."	capitals, as shown here."


	REVISION "202308140000Z"	REVISION "202310310000Z"
	DESCRIPTION	DESCRIPTION
	"This version of this MIB module is part of	"This version of this MIB module is part of
	RFC 9456; see the RFC itself for full legal	RFC 9456; see the RFC itself for full legal
	notices. This version does the following:	notices. This version does the following:

	1) Updates the definition of SnmpTLSFingerprint	1) Updates the definition of SnmpTLSFingerprint
	to clarify the registry used for the one-octet	to clarify the registry used for the one-octet
	hash algorithm identifier.	hash algorithm identifier.

	2) Capitalizes key words in conformance with	2) Capitalizes key words in conformance with

	skipping to change at line 1475 ¶	skipping to change at line 1475 ¶
	<mailto:snmp-tlstm-reg-review@ietf.org> mailing list. Registration	<mailto:snmp-tlstm-reg-review@ietf.org> mailing list. Registration
	requests sent to the mailing list for review SHOULD use an	requests sent to the mailing list for review SHOULD use an
	appropriate subject (e.g., 'Request to register value in "SNMP-TLSTM	appropriate subject (e.g., 'Request to register value in "SNMP-TLSTM
	HashAlgorithms" registry'). In addition, designated experts should	HashAlgorithms" registry'). In addition, designated experts should
	consult with the <mailto:tls-reg-review@ietf.org> mailing list to	consult with the <mailto:tls-reg-review@ietf.org> mailing list to
	make sure that any new hash algorithms are considered for inclusion	make sure that any new hash algorithms are considered for inclusion
	in this registry.	in this registry.

	Designated experts SHOULD ascertain the existence of suitable	Designated experts SHOULD ascertain the existence of suitable
	documentation that defines a hash algorithm and SHOULD also verify	documentation that defines a hash algorithm and SHOULD also verify

	that the request does not conflict or duplicate other entries in the	that the request does not conflict with or duplicate other entries in
	registry. The experts should also provide a recommendation as to how	the registry. The experts should also provide a recommendation as to
	the "Recommended" column of the registry should be updated. Only	how the "Recommended" column of the registry should be updated. Only
	publicly available specifications that represent current industry-	publicly available specifications that represent current industry-
	accepted practices should receive an assignment of "Y" in the	accepted practices should receive an assignment of "Y" in the
	"Recommended" column; all other specific assignments in the registry	"Recommended" column; all other specific assignments in the registry
	should receive an assignment of "N". Assignments that are	should receive an assignment of "N". Assignments that are
	nonspecific (e.g., reserved values) SHOULD NOT receive an assigned	nonspecific (e.g., reserved values) SHOULD NOT receive an assigned
	value for the "Recommended" column.	value for the "Recommended" column.

	Within the three-week review period, the designated experts will	Within the three-week review period, the designated experts will
	either approve or deny the registration request, communicating this	either approve or deny the registration request, communicating this
	decision to the review list and IANA. Denials SHOULD include an	decision to the review list and IANA. Denials SHOULD include an

End of changes. 5 change blocks.
	7 lines changed or deleted	7 lines changed or added
This html diff was produced by rfcdiff 1.48.