Re: ietf-nntp Initial draft FINALLY available
Brian Kantor <brian@nothing.ucsd.edu> Wed, 02 October 1996 14:53 UTC
Received: from cnri by ietf.org id aa06543; 2 Oct 96 10:53 EDT
Received: from PHEASANT.ACADEM.COM by CNRI.Reston.VA.US id aa11232;
2 Oct 96 10:53 EDT
Received: (from majordom@localhost) by pheasant.ACADEM.COM (8.7.5/8.7.3) id
JAA24227 for ietf-nntp-outgoing; Wed, 2 Oct 1996 09:50:11 -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 JAA24222 for
<ietf-nntp@PHEASANT.ACADEM.COM>; Wed, 2 Oct 1996 09:50:09 -0500
Received: from pheasant.ACADEM.COM (root@PHEASANT.ACADEM.COM [198.137.249.71])
by academ.com (8.7.6/8.7.1) with ESMTP id JAA24141;
Wed, 2 Oct 1996 09:50:08 -0500 (CDT)
Received: from nothing.ucsd.edu (nothing.ucsd.edu [132.239.1.4]) by
pheasant.ACADEM.COM (8.7.5/8.7.3) with SMTP id JAA24218;
Wed, 2 Oct 1996 09:50:04 -0500
Received: by nothing.ucsd.edu (8.6.12/UCSDGENERIC.5)
id HAA19065 to ; Wed, 2 Oct 1996 07:47:57 -0700
Date: Wed, 2 Oct 1996 07:47:57 -0700
From: Brian Kantor <brian@nothing.ucsd.edu>
Message-Id: <199610021447.HAA19065@nothing.ucsd.edu>
To: evanc@synapse.net, sob@academ.com
Subject: Re: ietf-nntp Initial draft FINALLY available
Cc: ietf-nntp@academ.com
Sender: owner-ietf-nntp@academ.com
Precedence: bulk
RFC977 specifies that when operating over a TCP based network, it should be contacted on TCP port 119. There is nothing to prohibit it operating on any other port (as might be desireable should a Kerberised version ever appear) but the well-known service port is 119. I believe it is appropriate to specify this in the document. - Brian
- ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available Ben Polk
- Re: ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available Ben Polk
- Re: ietf-nntp Initial draft FINALLY available Evan Champion
- Re: ietf-nntp Initial draft FINALLY available Chris Caputo
- Re: ietf-nntp Initial draft FINALLY available James Fidell
- Re: ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available Brian Kantor
- Re: ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available Rich Salz
- Re: ietf-nntp Initial draft FINALLY available Brian Kantor
- Re: ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available Ramanan
- Re: ietf-nntp Initial draft FINALLY available Brian Kantor
- Re: ietf-nntp Initial draft FINALLY available Rich Salz
- Re: ietf-nntp Initial draft FINALLY available Rich Salz
- Re: ietf-nntp Initial draft FINALLY available Nat Ballou
- Re: ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available Bob Sloane
- Re: ietf-nntp Initial draft FINALLY available Brian Kantor
- Re: ietf-nntp Initial draft FINALLY available Thomas 'Mike' Michlmayr
- Re: ietf-nntp Initial draft FINALLY available Ben Polk
- Re: ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available Bob Sloane
- Re: ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available William H. Magill
- Re: ietf-nntp Initial draft FINALLY available Brian Kantor
- Re: ietf-nntp Initial draft FINALLY available Evan Champion
- Re: ietf-nntp Initial draft FINALLY available USENET news manager
- Re: ietf-nntp Initial draft FINALLY available Evan Champion
- Re: ietf-nntp Initial draft FINALLY available chris (c.) lewis
- Re: ietf-nntp Initial draft FINALLY available William H. Magill
- Re: ietf-nntp Initial draft FINALLY available Ben Polk
- ietf-nntp XHDR versus XPAT USENET news manager