RFC 4438: Fibre-Channel Name Server MIB
In plain English — editorial summary, not part of the RFC
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]
Document record
- Document ID
- RFC4438
- Published
- April 2006
- Authors
- C. DeSanti; V. Gaonkar; H.K. Vivek; K. McCloghrie; S. Gai
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 36
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4439Fibre Channel Fabric Address Manager MIBCurrent
March 2006
- RFC 4363Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering, and Virtual LAN ExtensionsCurrent
January 2006
- RFC 4319Definitions of Managed Objects for High Bit-Rate DSL - 2nd generation (HDSL2) and Single-Pair High-Speed Digital Subscriber Line (SHDSL) LinesCurrent
December 2005
- RFC 4318Definitions of Managed Objects for Bridges with Rapid Spanning Tree ProtocolCurrent
December 2005
- RFC 4560Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup OperationsCurrent
June 2006
- RFC 4268Entity State MIBCurrent
December 2005
- RFC 4624Multicast Source Discovery Protocol (MSDP) MIBCurrent
October 2006
- RFC 4625Fibre Channel Routing Information MIBCurrent
September 2006
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?