From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262008AbTHTOuu (ORCPT ); Wed, 20 Aug 2003 10:50:50 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262004AbTHTOuu (ORCPT ); Wed, 20 Aug 2003 10:50:50 -0400 Received: from d12lmsgate-5.de.ibm.com ([194.196.100.238]:32688 "EHLO d12lmsgate-5.de.ibm.com") by vger.kernel.org with ESMTP id S262002AbTHTOur (ORCPT ); Wed, 20 Aug 2003 10:50:47 -0400 Message-ID: <3F43891E.9060204@zurich.ibm.com> Date: Wed, 20 Aug 2003 16:43:42 +0200 From: Roman Pletka User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020903 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Stephan von Krawczynski CC: bloemsaa@xs4all.nl, davem@redhat.com, alan@lxorguk.ukuu.org.uk, willy@w.ods.org, richard@aspectgroup.co.uk, carlosev@newipnet.com, lamont@scriptkiddie.org, davidsen@tmr.com, marcelo@conectiva.com.br, netdev@oss.sgi.com, linux-net@vger.kernel.org, layes@loran.com, torvalds@osdl.org, linux-kernel@vger.kernel.org Subject: Re: [2.4 PATCH] bugfix: ARP respond on all devices References: <353568DCBAE06148B70767C1B1A93E625EAB58@post.pc.aspectgroup.co.uk> <20030819145403.GA3407@alpha.home.local> <20030819170751.2b92ba2e.skraw@ithnet.com> <20030819085717.56046afd.davem@redhat.com> <20030819185219.116fd259.skraw@ithnet.com> <3F43362A.7090802@zurich.ibm.com> <20030820161512.6ccdd963.skraw@ithnet.com> X-Enigmail-Version: 0.63.3.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Stephan von Krawczynski wrote: > > 2.3.2 Address Resolution Protocol -- ARP > > 2.3.2.1 ARP Cache Validation > > An implementation of the Address Resolution Protocol (ARP) > [LINK:2] MUST provide a mechanism to flush out-of-date cache > entries. If this mechanism involves a timeout, it SHOULD be > possible to configure the timeout value. > > ... > > [LINK:2] "An Ethernet Address Resolution Protocol," D. Plummer, RFC-826, > November 1982. > > > Please read carefully what you have quoted: It says: *An* implementation... and then goes on with a citation of RFC 826. A simple citation does not make a valid standard yet. It just refers to it as an example for this specific issue. That's all. -- Roman