SEARCH
0-9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Prev | Current Page 414 | Next

Abdul Kasim, Prasanna Adhikari, Nan Chen, and Norman Finn

"Delivering Carrier Ethernet: Extending Ethernet Beyond the LAN"

Such a
feature is available due to the decision to use standard Ethernet frames as the transport
mechanism for OAM information and procedures.
SNMP over Ethernet RFC 1089 defines SNMP protocol over Ethernet networks, describing
an experimental method by which the SNMP as specified in Case et al [3] can
be used over Ethernet MAC layer framing instead of the Internet UDP/IP protocol stack.
This specification is critical for LAN-based network elements which contain no higher
layer protocol functionality. This particular implementation allows for relaying SNMP
frames in a pure Ethernet environment and thus is perfectly suited for deployment in
a Carrier Ethernet environment. The original RFC 1089 will soon be replaced by the
new RFC 4789 entitled ???simple network management protocol (SNMP) over IEEE 802
Networks??? (publication date November 2006, available online at http://www.ietf.org/rfc/
rfc4789.txt), which defines the details of the SNMP over Ethernet implementation. In
accordance with the current RFC draft specification, SNMP over IEEE 802 networks features
a number of inherent restrictions. Using SNMP over IEEE 802 transport mapping
restricts messages to a single logical IEEE 802 LAN, bridged LAN, or VLAN domain,
Passive Optical Networks (PONs) 167
while only a single SNMP engine can be addressed on a given IEEE 802 network interface,
with all the command generators and notification receivers as well as command
responders and notification originators sharing a single transport endpoint.


Pages:
402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426