[rfc-dist] RFC 4438 on Fibre-Channel Name Server MIB

[rfc-editor at rfc-editor.org ([e-mail])]

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

        
        RFC 4438

        Title:      Fibre-Channel Name Server MIB 
        Author:     C. DeSanti, V. Gaonkar,
                    H.K. Vivek, K. McCloghrie,
                    S. Gai
        Status:     Standards Track
        Date:       April 2006
        Mailbox:    cds at cisco.com, 
                    vgaonkar at cisco.com, 
                    hvivek at cisco.com,  kzm at cisco.com, 
                    retired
        Pages:      36
        Characters: 70156
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-imss-fc-nsm-mib-05.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4438.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 the Name Server function of a Fibre Channel network.
The Fibre Channel Name Server provides a means for Fibre Channel
ports to register and discover Fibre Channel names and attributes.  [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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

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

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...