[imss] FW: RFC 4936 on Fibre Channel Zone Server MIB

["Romascanu, Dan (Dan)" <[e-mail]>]

 
Congratulations and thanks to the editors and the whole Working Group
for the publication of RFC 4935 and RFC 4936. 

Dan


 

-----Original Message-----
From: [e-mail] [mailto:[e-mail]] 
Sent: Saturday, August 04, 2007 6:00 AM
To: [e-mail]; [e-mail]
Cc: [e-mail]; [e-mail]
Subject: RFC 4936 on Fibre Channel Zone Server MIB


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

        
        RFC 4936

        Title:      Fibre Channel Zone Server MIB 
        Author:     C. DeSanti, H.K. Vivek,
                    K. McCloghrie, S. Gai
        Status:     Standards Track
        Date:       August 2007
        Mailbox:    [e-mail], 
                    [e-mail], 
                    [e-mail],  [e-mail]
        Pages:      84
        Characters: 170801
        Updates/Obsoletes/SeeAlso:   None

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

        URL:        http://www.rfc-editor.org/rfc/rfc4936.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 a
Fibre Channel Zone Server.  [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 [e-mail].  Requests to be added to or
deleted from the RFC-DIST distribution list should be sent to
[e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an
EMAIL message to [e-mail] with the message body 

help: ways_to_get_rfcs. For example:

        To: [e-mail]
        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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[e-mail].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...



_______________________________________________
IETF-Announce mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/ietf-announce


_______________________________________________
imss mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/imss