idnits 2.17.1 draft-ietf-forces-netlink-04.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3549 5 Title: Linux Netlink as an IP Services Protocol 6 Author(s): J. Salim, H. Khosravi, A. Kleen, A. Kuznetsov 7 Status: Informational 8 Date: July 2003 9 Mailbox: hadi@znyx.com, hormuzd.m.khosravi@intel.com, 10 ak@suse.de, kuznet@ms2.inr.ac.ru 11 Pages: 33 12 Characters: 72161 13 Updates/Obsoletes/SeeAlso: None 15 I-D Tag: draft-ietf-forces-netlink-04.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3549.txt 19 This document describes Linux Netlink, which is used in Linux both 20 as an intra-kernel messaging system as well as between kernel and 21 user space. The focus of this document is to describe Netlink's 22 functionality as a protocol between a Forwarding Engine Component 23 (FEC) and a Control Plane Component (CPC), the two components that 24 define an IP service. As a result of this focus, this document 25 ignores other uses of Netlink, including its use as a intra-kernel 26 messaging system, as an inter-process communication scheme (IPC), or 27 as a configuration tool for other non-networking or non-IP network 28 services (such as decnet, etc.). 30 This document is intended as informational in the context of prior art 31 for the ForCES IETF working group. 33 This document is a product of the Forwarding and Control Element 34 Separation Working Group of the IETF. 36 This memo provides information for the Internet community. It does 37 not specify an Internet standard of any kind. Distribution of this 38 memo is unlimited. 40 This announcement is sent to the IETF list and the RFC-DIST list. 41 Requests to be added to or deleted from the IETF distribution list 42 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 43 added to or deleted from the RFC-DIST distribution list should 44 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 46 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 47 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 48 help: ways_to_get_rfcs. For example: 50 To: rfc-info@RFC-EDITOR.ORG 51 Subject: getting rfcs 53 help: ways_to_get_rfcs 55 Requests for special distribution should be addressed to either the 56 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 57 specifically noted otherwise on the RFC itself, all RFCs are for 58 unlimited distribution.echo 59 Submissions for Requests for Comments should be sent to 60 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 61 Authors, for further information.