[storm] Last Call complete on "Definitions of Managed Objects for iFCP"

The deadline for comment having recently passed, the Working Group Last Call on draft-ietf-storm-ifcpmib is complete.

Numerous comments were received, as summarized below. These changes will be addressed by the editor and an updated document will be available in the near future.

Comment summary:
- Editorial changes: id-nits issues, IETF template conformance, MIB template conformance and grammar
- Restate the current discussions of SNMP use as an example only
- Remove description of iFCP and iFCP gateways from Abstract and move into body of document
- Be clear that the document itself is not a MIB, rather it defines a MIB module
- Add newly defined Descriptors and Object Identifiers to IANA considerations section
- Verify appropriate copyright notice in MODULE-IDENTITY and correct if necessary
- Possible issue in description of ifcpLclGtwyInstAddrTransMode regarding deprecation/obsoletion
- Possible issue in description of ifcpGatewayCompliance deprecation

The complete set of comments may be found in the STORM mailing list archive at the URLs below.

Thanks to all those who read and considered the document during Last Call. After the update and WG validation, the document will be forwarded to the next phase of IETF review.

Tom Talpey
STORM WG co-chair

Comments:
http://www.ietf.org/mail-archive/web/storm/current/msg00094.html
http://www.ietf.org/mail-archive/web/storm/current/msg00095.html

> -----Original Message-----
> From: storm-bounces@ietf.org [mailto:storm-bounces@ietf.org] On Behalf
> Of Tom Talpey
> Sent: Thursday, February 04, 2010 6:50 AM
> To: storm@ietf.org
> Subject: [storm] Working Group Last Call on "Definitions of Managed Objects
> for iFCP"
> 
> The STORM working group announces Last Call on the iFCP MIB definition
> document
> 
> 	http://www.ietf.org/id/draft-ietf-storm-ifcpmib-00.txt
> 
> which was chartered and published last November. The Last Call period will
> extend through Sunday February 21, 2010 at 11:59pm Eastern Standard Time,
> in expectation of completing any necessary edits prior to the March IETF
> publication deadlines.
> 
> Please send any and all technical comments directly to this mailing list:
> 	storm@ietf.org
> 
> Any editorial or other comments should be sent to the editor, cc'ing me:
> 	Prakash Venkatesen prakashvn -at- hcl.in
> 	Tom Talpey (STORM WG co-chair) ttalpey -at- microsoft.com
> 
> Additional information on the STORM WG agenda, work items and links to
> the active documents are available at
> 	http://www.ietf.org/dyn/wg/charter/storm-charter.html
> 
> The document Abstract is reproduced below.
> 
>    The iFCP protocol (RFC 4172) provides Fibre Channel fabric
>    functionality on an IP network in which TCP/IP switching and routing
>    elements replace Fibre Channel components.  The iFCP protocol is used
>    between iFCP Gateways.  This document provides a mechanism to monitor
>    and control iFCP Gateway instances, and their associated sessions,
>    using SNMP.
> 
>    This document obsoletes RFC4369.
> 
> Tom Talpey
> STORM WG co-chair
> _______________________________________________
> storm mailing list
> storm@ietf.org
> https://www.ietf.org/mailman/listinfo/storm