IETF Logo Mail Archive

Re: ietf-nntp Mention port 433 in draft?

News Master <news@ednet.co.uk> Tue, 16 September 1997 12:42 UTC

Received: from cnri by ietf.org id aa10720; 16 Sep 97 8:42 EDT
Received: from announcer.academ.com (majordomo@ANNOUNCER.ACADEM.COM [198.137.249.60]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid IAA08153 for <ietf-archive@cnri.reston.va.us>; Tue, 16 Sep 1997 08:45:49 -0400 (EDT)
Received: (from majordomo@localhost) by announcer.academ.com (8.8.5/8.8.5) id HAA07429; Tue, 16 Sep 1997 07:41:09 -0500 (CDT)
Received: from academ.com (root@ACADEM.COM [198.137.249.2]) by announcer.academ.com (8.8.5/8.8.5) with ESMTP id HAA07424 for <ietf-nntp@ANNOUNCER.ACADEM.COM>; Tue, 16 Sep 1997 07:41:07 -0500 (CDT)
Received: from handel.ednet.co.uk (root@handel.ednet.co.uk [195.89.132.2]) by academ.com (8.8.5/8.8.5) with ESMTP id HAA24689 for <ietf-nntp@academ.com>; Tue, 16 Sep 1997 07:41:05 -0500 (CDT)
Received: from monteverdi.ednet.co.uk (news@monteverdi.ednet.co.uk [195.89.132.3]) by handel.ednet.co.uk (8.8.7/8.6.6) with SMTP id NAA32541 for <ietf-nntp@academ.com>; Tue, 16 Sep 1997 13:40:54 +0100
Date: Tue, 16 Sep 1997 13:40:56 +0100
From: News Master <news@ednet.co.uk>
To: ietf-nntp@academ.com
Subject: Re: ietf-nntp Mention port 433 in draft?
In-Reply-To: <199709160711.CAA22045@academ.com>
Message-ID: <Pine.LNX.3.91.970916133138.17560B-100000@monteverdi.ednet.co.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

On Tue, 16 Sep 1997, Stan Barber wrote:

> I just checked with IANA's list of port numbers and there is nothing in
> that list that indicates that port 433 has anything to do with news or
> NNTP. Here is exactly what is listed. 

RFC1700 has a contact name for NNSP: Rob Robertson. The email address 
given is @berkeley.edu but he is now working @wired.com. I was in 
touch with him in June regarding this; here are his comments:

[begin quote]
> pretty much, just that, strip all the newsreading stuff out of NNTP,
> add the streaming transfer commands, and run the server off of port
> 433. 
[end quote]

To this end, I have been using 433 internally for news transit for some 
time, and found newsreading much more responsive with INN not having to 
bother forking. As a result, I'm effectively running two different 
protocols on two different ports: the NNSP subset with CHECK/TAKETHIS for 
transit, and the NNRP subset with XOVER/ARTICLE et al for reading.

Sometimes I've wondered if the standard could be better served by
formally splitting it into two "subprotocols" such as these. 

-- 
edNET News Administration                             Edinburgh's local ISP:
Newsmaster: Joshua Goodall <joshua@ednet.co.uk>       http://www.ednet.co.uk/

v2.23.0 | Report a Bug | By Email