[imss] FW: RFC 5324 on MIB for Fibre-Channel Security Protocols (FC-SP)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[imss] FW: RFC 5324 on MIB for Fibre-Channel Security Protocols (FC-SP)



Congratulations!

The WG has completed its charter. 

Champagne, please!

Dan


-----Original Message-----
From: ietf-announce-bounces at ietf.org
[mailto:ietf-announce-bounces at ietf.org] On Behalf Of
rfc-editor at rfc-editor.org
Sent: Thursday, September 11, 2008 9:58 PM
To: ietf-announce at ietf.org; rfc-dist at rfc-editor.org
Cc: imss at ietf.org; rfc-editor at rfc-editor.org
Subject: RFC 5324 on MIB for Fibre-Channel Security Protocols (FC-SP)


A new Request for Comments is now available in online RFC libraries.

        
        RFC 5324

        Title:      MIB for Fibre-Channel Security Protocols 
                    (FC-SP) 
        Author:     C. DeSanti, F. Maino,
                    K. McCloghrie
        Status:     Standards Track
        Date:       September 2008
        Mailbox:    cds at cisco.com, 
                    fmaino at cisco.com, 
                    kzm at cisco.com
        Pages:      216
        Characters: 449246
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-imss-fc-fcsp-mib-03.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5324.txt

This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community.
In particular, it describes managed objects for information related to
FC-SP, the Security Protocols defined for Fibre Channel.  [STANDARDS
TRACK]

This document is a product of the Internet and Management Support for
Storage Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and
suggestions for improvements.  Please refer to the current edition of
the Internet Official Protocol Standards (STD 1) for the standardization
state and status of this protocol.  Distribution of this memo is
unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see
http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute


_______________________________________________
IETF-Announce mailing list
IETF-Announce at ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce
_______________________________________________
imss mailing list
imss at ietf.org
https://www.ietf.org/mailman/listinfo/imss



Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.