RFC 3549: Linux Netlink as an IP Services Protocol
In plain English — editorial summary, not part of the RFC
This document describes Linux Netlink, which is used in Linux both as an intra-kernel messaging system as well as between kernel and user space. The focus of this document is to describe Netlink's functionality as a protocol between a Forwarding Engine Component (FEC) and a Control Plane Component (CPC), the two components that define an IP service. As a result of this focus, this document ignores other uses of Netlink, including its use as a intra-kernel messaging system, as an inter- process communication scheme (IPC), or as a configuration tool for other non-networking or non-IP network services (such as decnet, etc.). This document is intended as informational in the context of prior art for the ForCES IETF working group. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3549
- Published
- July 2003
- Authors
- J. Salim; H. Khosravi; A. Kleen; A. Kuznetsov
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 33
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3561Ad hoc On-Demand Distance Vector (AODV) RoutingCurrent
July 2003
- RFC 3562Key Management Considerations for the TCP MD5 Signature OptionCurrent
July 2003
- RFC 3567Intermediate System to Intermediate System (IS-IS) Cryptographic AuthenticationObsoleted
July 2003
- RFC 3569An Overview of Source-Specific Multicast (SSM)Current
July 2003
- RFC 3573Signalling of Modem-On-Hold status in Layer 2 Tunneling Protocol (L2TP)Current
July 2003
- RFC 3509Alternative Implementations of OSPF Area Border RoutersCurrent
April 2003
- RFC 3609Tracing Requirements for Generic TunnelsCurrent
October 2003
- RFC 3612Applicability Statement for Restart Mechanisms for the Label Distribution Protocol (LDP)Current
September 2003
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?