Re: ietf-nntp Initial draft FINALLY available

Evan Champion <evanc@synapse.net> Thu, 03 October 1996 02:33 UTC

Received: from cnri by ietf.org id aa20031; 2 Oct 96 22:33 EDT
Received: from PHEASANT.ACADEM.COM by CNRI.Reston.VA.US id aa27488; 2 Oct 96 22:33 EDT
Received: (from majordom@localhost) by pheasant.ACADEM.COM (8.7.5/8.7.3) id VAA26429 for ietf-nntp-outgoing; Wed, 2 Oct 1996 21:32:09 -0500
X-Authentication-Warning: pheasant.ACADEM.COM: majordom set sender to owner-ietf-nntp using -f
Received: from academ.com (root@ACADEM.COM [198.137.249.2]) by pheasant.ACADEM.COM (8.7.5/8.7.3) with ESMTP id VAA26425 for <ietf-nntp@PHEASANT.ACADEM.COM>; Wed, 2 Oct 1996 21:32:07 -0500
Received: from clarinet.synapse.net (clarinet.synapse.net [199.84.54.19]) by academ.com (8.7.6/8.7.1) with ESMTP id VAA05631; Wed, 2 Oct 1996 21:32:06 -0500 (CDT)
Received: from cello (cello.synapse.net [199.84.54.34]) by clarinet.synapse.net (8.8.0/8.8.0) with SMTP id WAA06894; Wed, 2 Oct 1996 22:32:03 -0400 (EDT)
Message-ID: <32532559.4D2B@synapse.net>
Date: Wed, 02 Oct 1996 22:30:49 -0400
From: Evan Champion <evanc@synapse.net>
X-Mailer: Mozilla 3.0 (WinNT; I)
MIME-Version: 1.0
To: Stan Barber <sob@academ.com>
CC: ietf-nntp@academ.com
Subject: Re: ietf-nntp Initial draft FINALLY available
References: <199610021407.JAA22072@academ.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

Stan Barber wrote:
> What is the point of having a IANA assigned port number then? What if I
> chose to run an HTTP server on port 119?

As I said in my last note, the reason is IMHO for interoperability
_only_.  You have to have some reference point for systems that wouldn't
otherwise know which port to connect to.  If you want to make
arrangements with your peers to do stock NNTP on a different port,
that's up to you (and there are lots of very logical reasons to do so,
as have been brought up by myself and other posters.)

One way to think of it is to divorce protocol from transport.  There is
no technical reason why NNTP _must_ run on 119/TCP (just like there is
no technical reason why NNTP must run over TCP, or that the servers be
connected by IP... )

If there is a technical justification for something then it should be
said with a MUST.  If something is being said as a suggestion (even a
strong suggestion) it should be said with a SHOULD.  IMHO MUST does not
apply here, but SHOULD certainly does.

Evan
--
Evan Champion            * Director, Network Operations
mailto:evanc@synapse.net * Directeur, Exploitation du reseau
http://www.synapse.net/  * Synapse Internet