From owner-freebsd-net@FreeBSD.ORG Sun Jan 6 14:31:48 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F018616A420; Sun, 6 Jan 2008 14:31:48 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.freebsd.org (Postfix) with ESMTP id BFFFA13C467; Sun, 6 Jan 2008 14:31:48 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 2611983053; Sun, 6 Jan 2008 09:31:48 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Sun, 06 Jan 2008 09:31:48 -0500 X-Sasl-enc: hIZXm1v/XEp5jk+bgdWLzB+SqxKxPZ/jOLMCDbmrXXRi 1199629907 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 06EA110BF0; Sun, 6 Jan 2008 09:31:46 -0500 (EST) Message-ID: <4780E652.5040804@FreeBSD.org> Date: Sun, 06 Jan 2008 14:31:46 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.6 (X11/20070928) MIME-Version: 1.0 To: Julian Elischer References: <4772F123.5030303@elischer.org> <477416CC.4090906@elischer.org> <477D2EF3.2060909@elischer.org> <47802137.8020701@elischer.org> In-Reply-To: <47802137.8020701@elischer.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Qing Li , FreeBSD Net , Vadim Goncharov , arch@freebsd.org, Ivo Vachkov , Robert Watson Subject: Re: resend: multiple routing table roadmap (format fix) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jan 2008 14:31:49 -0000 Julian Elischer wrote: >> >> OK, but we should think about it in the future. In theory, routing >> socket's messages are easily extendable with FIB number in uint16_t, >> as message keeps it's length... > > I will do that with the advice of people who know that protocol better > than I do. I'm afraid Linux is still ahead of the game here. They adopted a tag-length-value protocol called NETLINK which solves many of the problems inherent in PF_ROUTE. It even has an RFC. BMS