Technical Summary
This document defines Management Information Base (MIB) objects to
allow a network management protocol to be used to monitor and manage
local iFCP gateway instances, including the configuration of iFCP sessions
between gateways. This document updates, and obsoletes, RFC4369.
Working Group Summary
The WG process to create this document went very smoothly, in large part
owing to the existing publication of RFC4369. Comments were constructive
and were easily addressed with minor changes to the draft version. The
document was well-received and Working Group consensus was easily
reached.
Document Quality
The document is of high quality, and while written to support iFCP, has
architectural relevance to other current Internet protocols supporting the
SCSI family. The iFCP protocol, now largely historical, is deployed in
numerous products. The MIB objects in the document are therefore
expected to be relevant to iFCP management, as well as to provide a basis
for additional related efforts.
The area director is a MIB Doctor, and he found the module to be in good shape.
The document went through an independent MIB Doctor review, and certain SMIv2 requirements were addressed.
It passes libsmi syntax checks, id-nits, and RFC4181 guidelines.
Personnel
Document Shepherd: Tom Talpey (STORM WG co-chair),
Responsible Area Director: David Harrington
This document defines no new IANA registries.
RFC Editor Note
The authors of RFC 4369 are listed in the Authors' Addresses, but did not work on this update.
They were added to ensure they got credit for the original published version of this document.
They should not need to be contacted during auth48.