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

rfc-editor@rfc-editor.org Thu, 11 September 2008 18:58 UTC

Return-Path: <imss-bounces@ietf.org>
X-Original-To: imss-archive@optimus.ietf.org
Delivered-To: ietfarch-imss-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1622B28C156; Thu, 11 Sep 2008 11:58:59 -0700 (PDT)
X-Original-To: imss@core3.amsl.com
Delivered-To: imss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1ADA428C156; Thu, 11 Sep 2008 11:58:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.163
X-Spam-Level:
X-Spam-Status: No, score=-17.163 tagged_above=-999 required=5 tests=[AWL=-0.164, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CXUSLt3IWr0F; Thu, 11 Sep 2008 11:58:56 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 4A69628C102; Thu, 11 Sep 2008 11:58:56 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 42766154A10; Thu, 11 Sep 2008 11:58:27 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20080911185827.42766154A10@bosco.isi.edu>
Date: Thu, 11 Sep 2008 11:58:27 -0700 (PDT)
Cc: imss@ietf.org, rfc-editor@rfc-editor.org
Subject: [imss] RFC 5324 on MIB for Fibre-Channel Security Protocols (FC-SP)
X-BeenThere: imss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Internet and Management Support for Storage Working Group <imss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/imss>, <mailto:imss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/imss>
List-Post: <mailto:imss@ietf.org>
List-Help: <mailto:imss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imss>, <mailto:imss-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: imss-bounces@ietf.org
Errors-To: imss-bounces@ietf.org

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@cisco.com, 
                    fmaino@cisco.com, 
                    kzm@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@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


_______________________________________________
imss mailing list
imss@ietf.org
https://www.ietf.org/mailman/listinfo/imss