From owner-freebsd-net@FreeBSD.ORG Tue Jan 16 18:41:28 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AE30F16A546 for ; Tue, 16 Jan 2007 18:41:28 +0000 (UTC) (envelope-from rrs@cisco.com) Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by mx1.freebsd.org (Postfix) with ESMTP id 8962613C4BD for ; Tue, 16 Jan 2007 18:41:28 +0000 (UTC) (envelope-from rrs@cisco.com) Received: from sj-dkim-8.cisco.com ([171.68.10.93]) by sj-iport-4.cisco.com with ESMTP; 16 Jan 2007 10:41:28 -0800 Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137]) by sj-dkim-8.cisco.com (8.12.11/8.12.11) with ESMTP id l0GIfSED004578; Tue, 16 Jan 2007 10:41:28 -0800 Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id l0GIfEhq015578; Tue, 16 Jan 2007 10:41:28 -0800 (PST) Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 16 Jan 2007 10:41:14 -0800 Received: from [127.0.0.1] ([171.68.225.134]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 16 Jan 2007 10:41:14 -0800 Message-ID: <45AD1C0F.7000701@cisco.com> Date: Tue, 16 Jan 2007 13:40:15 -0500 From: Randall Stewart User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.8) Gecko/20061029 FreeBSD/i386 SeaMonkey/1.0.6 MIME-Version: 1.0 To: Chuck Swiger References: <20070112163057.2a3ec8f0.rnsanchez@wait4.org> <45A807F8.7080603@FreeBSD.org> <45ACCFF4.4040709@cisco.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 16 Jan 2007 18:41:14.0231 (UTC) FILETIME=[E6734070:01C7399D] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1873; t=1168972888; x=1169836888; c=relaxed/relaxed; s=sjdkim8002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rrs@cisco.com; z=From:=20Randall=20Stewart=20 |Subject:=20Re=3A=20Problem=20with=20port=200 |Sender:=20; bh=+bmNdpC/d3cASx5Opm3DVSUqAWNwq2Ke1AltbjUFeGs=; b=And1bg26aHzrbZtro9KTZUc+kTqaGJB61juZvq02HcWRPjulVA2CbUbk0pbd2atYwY6L6L9K h9KlQYzCHj0Wc/a0G/CLEbVSgXX2MAlG0axfLacMAiT4hQ3R6HZWhCAQ; Authentication-Results: sj-dkim-8; header.From=rrs@cisco.com; dkim=pass (sig from cisco.com/sjdkim8002 verified; ); Cc: freebsd-net Subject: Re: Problem with port 0 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: Tue, 16 Jan 2007 18:41:28 -0000 Chuck Swiger wrote: > On Jan 16, 2007, at 5:15 AM, Randall Stewart wrote: >> So... I guess this really leads to a question.. >> >> What does "reserved" mean by IANA. > > "reserved" means one "SHOULD NOT" use that port, where the phrase in > caps is defined in RFC-2119 (http://www.ietf.org/rfc/rfc2119.txt). And: > > http://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers > > ...states: "0/tcp,udp: Reserved; do not use (but is a permissible source > port value if the sending process does not expect messages in response)" > > ---Chuck > So let me see if I understand the statements above.. We are using the SHOULD NOT.. which is YOU REALLY REALLY REALLY REALLY REALLY REALLY should not do this unless you have some very dramatic demonstrative need to do so and know the FULL consequences of the action. The bit from wikipedia, while not authoritative in my mind, says you can send FROM the port, but don't expect an answer back.. which implies you cannot bind it and/or cannot read from it if your source port is 0... Of course in TCP this is totally useless since you have to get something back in order to setup the handshake. In UDP I guess one could get a packet if the other O/S did not have any bind restrictions.. or one were to use a raw socket. But why all this for something you SHOULD NOT DO.. one of the consequences in my mind of this is that not all O/S's may be able to read your data .. nor respond to it. Seems to me a lot of hassle when one can just use a different port :-0 Of course I am not saying we should not make this work.. I just am uncomfortable with it .. just as a generality :-) And I am sure glad we used the MUST NOT term in SCTP when we did the BIS document .. no grey area there :-) R -- Randall Stewart NSSTG - Cisco Systems Inc. 803-345-0369 803-317-4952 (cell)