Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)
RFC 5953

Received changes through RFC Editor sync (changed abstract to 'This document describes a Transport Model for the Simple Network Management Protocol (SNMP), that uses either the Transport Layer Security protocol or the Datagram Transport Layer Security (DTLS) protocol. The TLS and DTLS protocols provide authentication and privacy services for SNMP applications. This document describes how the TLS Transport Model (TLSTM) implements the needed features of a SNMP Transport Subsystem to make this protection possible in an interoperable way.

This Transport Model is designed to meet the security and operational needs of network administrators. It supports the sending of SNMP messages over TLS/TCP and DTLS/UDP. The TLS mode can make use of TCP's improved support for larger packet sizes and the DTLS mode provides potentially superior operation in environments where a connectionless (e.g., UDP) transport is preferred. Both TLS and DTLS integrate well into existing public keying infrastructures.

This document also defines a portion of the Management Information Base (MIB) for use with network management protocols. In particular, it defines objects for managing the TLS Transport Model for SNMP. [STANDARDS-TRACK]')

The following Last Call Announcement was sent out:

From: The IESG
Date: May 9, 2011 1:43:31 PM PDT
To:
IETF-Announce
Cc: isms@ietf.org
Subject: Second Last
Call: rfc5953 (Transport Layer Security (TLS) Transport Model for the Simple
Network Management Protocol (SNMP)) to Draft Standard
Reply-To: ietf@ietf.org

The IESG has received a request from the isms WG (isms) to consider the
following document:

- 'Transport Layer Security (TLS) Transport Model for the Simple Network
  Management Protocol (SNMP) '
RFC 5953 as a Draft Standard

Two issues were raised during the first Last Call: 1) references to IDNA 2003
(RFC 3490) need to be replaced by references to IDNA 2008 (RFC 5890), and 2)
references to RFC 1033 need to be replaced by references to 1123.  This Last
Call is focused on these two issues.

To address these points the following changes were made:

OLD:

A hostname is always in US-ASCII (as per [RFC1033]);
internationalized hostnames are encoded in US-ASCII as domain
names after transformation via the ToASCII operation specified
in [RFC3490].  The ToASCII operation MUST be performed with the
UseSTD3ASCIIRules flag set.  The hostname is followed by a
colon ':' (US-ASCII character 0x3A) and a decimal port number
in US-ASCII.  The name SHOULD be fully qualified whenever
possible.

NEW:

A hostname is always in US-ASCII (as per [RFC1123]);
internationalized hostnames are encoded as A-labels as specified
in [RFC5890].  The hostname is followed by a
colon ':' (US-ASCII character 0x3A) and a decimal port number
in US-ASCII.  The name SHOULD be fully qualified whenever
possible.

Changing the references also means the downref call needs to be updated, as
follows:

This specification contains eight normative references to standards
track documents of lower maturity: RFCs 1123, 3584, 4347, 4366,
5246, 5280, 5890, and 5952.

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2011-05-23. Exceptionally,
comments may be sent to iesg@ietf.org instead. In either case, please
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://datatracker.ietf.org/doc/rfc5953/

Implementation Report can be accessed at
http://www.ietf.org/iesg/implementation.html

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/rfc5953/

The following Last Call Announcement was sent out:

From: The IESG
Date: May 9, 2011 1:43:31 PM PDT
To: IETF-Announce
Cc: isms@ietf.org
Subject: Second Last Call: rfc5953 (Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)) to Draft Standard
Reply-To: ietf@ietf.org

The IESG has received a request from the isms WG (isms) to consider the
following document:

- 'Transport Layer Security (TLS) Transport Model for the Simple Network
  Management Protocol (SNMP) '
RFC 5953 as a Draft Standard

Two issues were raised during the first Last Call: 1) references to IDNA 2003 (RFC 3490) need to be replaced by references to IDNA 2008 (RFC 5890), and 2) references to RFC 1033 need to be replaced by references to 1123.  This Last Call is focused on these two issues.

To address these points the following changes were made:

OLD:

A hostname is always in US-ASCII (as per [RFC1033]);
internationalized hostnames are encoded in US-ASCII as domain
names after transformation via the ToASCII operation specified
in [RFC3490].  The ToASCII operation MUST be performed with the
UseSTD3ASCIIRules flag set.  The hostname is followed by a
colon ':' (US-ASCII character 0x3A) and a decimal port number
in US-ASCII.  The name SHOULD be fully qualified whenever
possible.

NEW:

A hostname is always in US-ASCII (as per [RFC1123]);
internationalized hostnames are encoded as A-labels as specified
in [RFC5890].  The hostname is followed by a
colon ':' (US-ASCII character 0x3A) and a decimal port number
in US-ASCII.  The name SHOULD be fully qualified whenever
possible.

Changing the references also means the downref call needs to be updated, as follows:

This specification contains eight normative references to standards
track documents of lower maturity: RFCs 1123, 3584, 4347, 4366,
5246, 5280, 5890, and 5952.

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2011-05-23. Exceptionally,
comments may be sent to iesg@ietf.org instead. In either case, please
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://datatracker.ietf.org/doc/rfc5953/

Implementation Report can be accessed at
http://www.ietf.org/iesg/implementation.html

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/rfc5953/