From owner-cvs-src@FreeBSD.ORG Thu Jan 24 14:40:28 2008 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A804B16A417; Thu, 24 Jan 2008 14:40:28 +0000 (UTC) (envelope-from karels@redrock.karels.net) Received: from redrock.karels.net (redrock.karels.net [206.196.45.2]) by mx1.freebsd.org (Postfix) with ESMTP id 397AA13C4D5; Thu, 24 Jan 2008 14:40:28 +0000 (UTC) (envelope-from karels@redrock.karels.net) Received: from redrock.karels.net (localhost [127.0.0.1]) by redrock.karels.net (8.13.8/8.13.6) with ESMTP id m0OEECWt097838; Thu, 24 Jan 2008 08:14:12 -0600 (CST) (envelope-from karels@redrock.karels.net) Message-Id: <200801241414.m0OEECWt097838@redrock.karels.net> To: Andre Oppermann From: Mike Karels In-reply-to: Your message of Thu, 24 Jan 2008 11:58:21 +0100. <47986F4D.6070208@freebsd.org> Date: Thu, 24 Jan 2008 08:14:12 -0600 Sender: karels@karels.net Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org, freebsd-net@freebsd.org Subject: Re: cvs commit: src/sys/netinet tcp_syncache.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: karels@karels.net List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jan 2008 14:40:28 -0000 Return-Path: owner-freebsd-net@freebsd.org Delivery-Date: Thu Jan 24 05:00:27 2008 Received: from staring.karels.net (root@staring.karels.net [206.196.45.1]) by redrock.karels.net (8.13.8/8.13.6) with ESMTP id m0OB0Rb6097199 for ; Thu, 24 Jan 2008 05:00:27 -0600 (CST) (envelope-from owner-freebsd-net@freebsd.org) Received: from mx2.freebsd.org (mx2.freebsd.org [69.147.83.53]) by staring.karels.net (8.11.6/8.11.2) with ESMTP id m0OB0QA08500 for ; Thu, 24 Jan 2008 05:00:26 -0600 (CST) Received: from hub.freebsd.org (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 398C833428; Thu, 24 Jan 2008 10:58:25 +0000 (UTC) (envelope-from owner-freebsd-net@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 10EE016A419; Thu, 24 Jan 2008 10:58:25 +0000 (UTC) (envelope-from owner-freebsd-net@freebsd.org) 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 CE46B16A478 for ; Thu, 24 Jan 2008 10:58:18 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id 2909C13C4DD for ; Thu, 24 Jan 2008 10:58:17 +0000 (UTC) (envelope-from andre@freebsd.org) Received: (qmail 98697 invoked from network); 24 Jan 2008 10:19:32 -0000 Received: from localhost (HELO [127.0.0.1]) ([127.0.0.1]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 24 Jan 2008 10:19:32 -0000 Message-ID: <47986F4D.6070208@freebsd.org> Date: Thu, 24 Jan 2008 11:58:21 +0100 From: Andre Oppermann User-Agent: Thunderbird 1.5.0.14 (Windows/20071210) MIME-Version: 1.0 To: Kip Macy References: <200711200656.lAK6u4bc021279@repoman.freebsd.org> <4797B77E.2090605@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Mike Silbersack , kmacy@freebsd.org, cvs-src@freebsd.org, cvs-all@freebsd.org, src-committers@freebsd.org, freebsd-net@freebsd.org Subject: Re: cvs commit: src/sys/netinet tcp_syncache.c 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: , Sender: owner-freebsd-net@freebsd.org Errors-To: owner-freebsd-net@freebsd.org > Kip Macy wrote: > > So it is clearly open to interpretation. > No, it is not. RFC1323 was written in 1992 before RFCs contained the > boiler plate definition of MUST, SHOULD, MAY and so on. The use of MUST, etc, originated in RFC1122 in 1989. That RFC also contains this: 1.2.2 Robustness Principle At every layer of the protocols, there is a general rule whose application can lead to enormous benefits in robustness and interoperability [IP:1]: "Be liberal in what you accept, and conservative in what you send" This quote is also on the RFC1122 working group coffee cup on my shelf. It seems to apply here. Mike