RFC 4369: Definitions of Managed Objects for Internet Fibre Channel Protocol (iFCP)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6173.
Current version: RFC 6173 — Definitions of Managed Objects for the Internet Fibre Channel Protocol (iFCP)
In plain English — editorial summary, not part of the RFC
The iFCP protocol (RFC 4172) provides Fibre Channel fabric functionality on an IP network in which TCP/IP switching and routing elements replace Fibre Channel components. The iFCP protocol is used between iFCP Gateways. This document provides a mechanism to monitor and control iFCP Gateway instances, and their associated sessions, using SNMP. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4369
- Published
- January 2006
- Authors
- K. Gibbons; C. Monia; J. Tseng; F. Travostino
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 29
- Also known as
- —
- Obsoleted by:
- RFC 6173
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4712Transport Mappings for Real-time Application Quality-of-Service Monitoring (RAQMON) Protocol Data Unit (PDU)Updated
October 2006
- RFC 5066Ethernet in the First Mile Copper (EFMCu) Interfaces MIBUpdated
November 2007
- RFC 3592Definitions of Managed Objects for the Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface TypeCurrent
September 2003
- RFC 3591Definitions of Managed Objects for the Optical Interface TypeCurrent
September 2003
- RFC 3440Definitions of Extension Managed Objects for Asymmetric Digital Subscriber LinesCurrent
January 2003
- RFC 3434Remote Monitoring MIB Extensions for High Capacity AlarmsCurrent
December 2002
- RFC 3433Entity Sensor Management Information BaseCurrent
December 2002
- RFC 2742Definitions of Managed Objects for Extensible SNMP AgentsCurrent
January 2000
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?