RFC 4404 on Definitions of Managed Objects for Fibre Channel Over TCP/IP (FCIP)

rfc-editor@rfc-editor.org Mon, 27 February 2006 21:25 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FDprs-0003W1-VC; Mon, 27 Feb 2006 16:25:20 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FDpjK-0006Xl-HT for ietf-announce@ietf.org; Mon, 27 Feb 2006 16:16:30 -0500
Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FDpUv-0003Rj-UF for ietf-announce@ietf.org; Mon, 27 Feb 2006 16:01:38 -0500
Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.8/8.12.8) with ESMTP id k1RL1ZWV005587; Mon, 27 Feb 2006 13:01:35 -0800
Received: (from apache@localhost) by nit.isi.edu (8.12.8/8.12.8/Submit) id k1RL1Z9L005586; Mon, 27 Feb 2006 13:01:35 -0800
Date: Mon, 27 Feb 2006 13:01:35 -0800
Message-Id: <200602272101.k1RL1Z9L005586@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
X-Spam-Score: -14.8 (--------------)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc: rfc-editor@rfc-editor.org
Subject: RFC 4404 on Definitions of Managed Objects for Fibre Channel Over TCP/IP (FCIP)
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Errors-To: ietf-announce-bounces@ietf.org

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

        
        RFC 4404

        Title:      Definitions of Managed Objects for 
                    Fibre Channel Over TCP/IP (FCIP) 
        Author:     R. Natarajan,  A. Rijhsinghani
        Status:     Standards Track
        Date:       February 2006
        Mailbox:    anil@charter.net, 
                    r.natarajan@f5.com
        Pages:      33
        Characters: 60475
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ips-fcip-mib-09.txt

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

This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in TCP/IP-based internets.
In particular, it defines objects for managing  Fibre Channel Over
TCP/IP (FCIP) entities, which are used to interconnect Fibre Channel
(FC) fabrics with IP networks.  [STANDARDS TRACK]

This document is a product of the IP 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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

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

help: ways_to_get_rfcs. For example:

        To: rfc-info@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@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@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


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

...



_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce