transport
Click on the red underlined text to get to the source
... RFC2580].
This document, Transport Mappings for the Simple Network Management
Protocol, defines how the management protocol [RFC3416 ...
... carried over a variety of protocol suites. It is the purpose of this
document to define how the SNMP maps onto an initial set of transport
domains. At the time of this writing, work was in progress to define
an IPv6 mapping, described in [RFC3419 ...
... IPv4 transport domain.
The corresponding transport address is of type
SnmpUDPAddress."
::= { snmpDomains 1 }
...
... DESCRIPTION
"The SNMP over CLNS transport domain.
The corresponding transport address is of type
...
... SNMP over CLNS transport domain.
The corresponding transport address is of type
SnmpOSIAddress."
::= { snmpDomains 2 }
...
... DESCRIPTION
"The SNMP over CONS transport domain.
The corresponding transport address is of type
...
... SNMP over CONS transport domain.
The corresponding transport address is of type
SnmpOSIAddress."
::= { snmpDomains 3 }
...
... "The SNMP over DDP transport domain. The corresponding
transport address is of type SnmpNBPAddress."
...
... DDP transport domain. The corresponding
transport address is of type SnmpNBPAddress."
::= { snmpDomains 4 }
...
... "The SNMP over IPX transport domain. The corresponding
transport address is of type SnmpIPXAddress."
...
... IPX transport domain. The corresponding
transport address is of type SnmpIPXAddress."
::= { snmpDomains 5 }
...
... UDP over IPv4.
The corresponding transport address is of type
SnmpUDPAddress."
::= { rfc1157Proxy 1 }
...
...
This is the preferred transport mapping.
...
... When an SNMP entity uses this transport mapping, it must be capable
of accepting messages up to and including 484 octets in size. It is
recommended that implementations be capable of accepting messages of
...
...
This is an optional transport mapping.
...
... [IS8072A] for the OSI Connectionless-mode Transport Service (CLTS),
using the algorithm specified in Section 8.
...
... SNMP entities
supporting command responder applications to listen on transport
selector "snmp-l" (which consists of six ASCII characters), when
...
... notification receiver
applications be configured to listen on transport selector "snmpt-l"
(which consists of seven ASCII characters, six letters and a hyphen)
...
... CO-mode network service to realize the CLTS, the
suggested transport selectors are "snmp-o" and "snmpt-o", for command
responders and notification ...
... When an SNMP entity uses this transport mapping, it must be capable
of accepting messages that are at least 484 octets in size.
Implementation of larger values is encouraged whenever possible.
...
...
This is an optional transport mapping.
...
... When an SNMP entity uses this transport mapping, it must be capable
of accepting messages that are at least 484 octets in size.
Implementation of larger values is encouraged whenever possible.
...
...
This is an optional transport mapping.
...
... When an SNMP entity uses this transport mapping, it must be capable
of accepting messages that are at least 546 octets in size.
Implementation of larger values is encouraged whenever possible.
...
... SNMPv1, as defined in
[RFC2576], it was deemed useful to define a transport domain,
rfc1157Domain, which indicates the transport mapping for SNMP ...
... RFC2576], it was deemed useful to define a transport domain,
rfc1157Domain, which indicates the transport mapping for SNMP
messages as defined in [RFC1157 ...
... Information processing systems - Open Systems Interconnection - Transport Service Definition, International Organization for Standardization. International Standard 8072, June 1986. ...
... Information processing systems - Open Systems Interconnection - Transport Service Definition - Addendum 1: Connectionless-mode Transmission, International Organization for Standardization. International Standard 8072/AD 1, December 1986. ...
... Daniele, M. and J. Schoenwaelder, "Textual Conventions for Transport Addresses", RFC 3419prop, November 2002. ...