Re: ietf-nntp FAQ Extension to NNTP
Jacob Palme <jpalme@dsv.su.se> Sun, 25 August 1996 09:38 UTC
Received: from ietf.org by ietf.org id aa28806; 25 Aug 96 5:38 EDT
Received: from cnri by ietf.org id aa28802; 25 Aug 96 5:38 EDT
Received: from PHEASANT.ACADEM.COM by CNRI.Reston.VA.US id aa03995;
25 Aug 96 5:38 EDT
Received: (from majordom@localhost) by pheasant.ACADEM.COM (8.7.5/8.7.3) id
JAA00323 for ietf-nntp-outgoing; Sun, 25 Aug 1996 09:32:37 -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 JAA00319 for
<ietf-nntp@PHEASANT.ACADEM.COM>; Sun, 25 Aug 1996 09:32:35 -0500
Received: from ester.dsv.su.se (ester.dsv.su.se [130.237.161.10]) by
academ.com (8.7.5/8.7.1) with ESMTP id EAA07351 for <ietf-nntp@academ.com>;
Sun, 25 Aug 1996 04:33:14 -0500 (CDT)
Received: from localhost (jpalme@localhost)
by ester.dsv.su.se (8.7.1/8.7.1) with SMTP id LAA08617;
Sun, 25 Aug 1996 11:33:09 +0200 (MET DST)
Date: Sun, 25 Aug 1996 11:33:09 +0200 (MET DST)
Sender: ietf-archive-request@ietf.org
From: Jacob Palme <jpalme@dsv.su.se>
To: Rich Salz <rsalz@osf.org>
cc: ietf-nntp@academ.com
Subject: Re: ietf-nntp FAQ Extension to NNTP
In-Reply-To: <9608241623.AA14355@sulphur.osf.org>
Message-ID: <Pine.SUN.3.94.960825112945.8533C-100000@ester.dsv.su.se>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Orig-Sender: owner-ietf-nntp@academ.com
Precedence: bulk
On Sat, 24 Aug 1996, Rich Salz wrote: > >MIME has an external reference format, > > NNTP does not rely/use/need/refer-to MIME. > > I think we should keep it that way. > > This does not mean that the "messages" returned by GROUPDATA > cannot refer to such things. If all newsreaders knew the external-body > type. Why should NNTP not use MIME? MIME supplies a lot of very useful features like embedded images, messages in HTML format, sending large images by only sending the URL instead of the whole file, etc. NNTP at present uses non-standardized methods for images in messages and does not allow messages in HTML format or sending URL-s instead of the text of large binaries. Either NNTP will have to develop its own standards for doing this, or use MIME. Since it is becoming more and more common that the same client is used for both e-mail and network news, it would be very advantageous if the format is as similar as possible in e-mail and in network news. ------------------------------------------------------------------------ Jacob Palme <jpalme@dsv.su.se> (Stockholm University and KTH) for more info see URL: http://www.dsv.su.se/~jpalme
- ietf-nntp FAQ Extension to NNTP Pat Brans
- Re: ietf-nntp FAQ Extension to NNTP Dave Barr
- Re: ietf-nntp FAQ Extension to NNTP Rich Salz
- Re: ietf-nntp FAQ Extension to NNTP Rich Salz
- Re: ietf-nntp FAQ Extension to NNTP Dave Barr
- Re: ietf-nntp FAQ Extension to NNTP Stan Barber
- Re: ietf-nntp FAQ Extension to NNTP Brian Hernacki
- Re: ietf-nntp FAQ Extension to NNTP Jean van Waterschoot
- Re: ietf-nntp FAQ Extension to NNTP John Stanley
- Re: ietf-nntp FAQ Extension to NNTP Jacob Palme DSV-SU/KTH
- Re: ietf-nntp FAQ Extension to NNTP Rich Salz
- Re: ietf-nntp FAQ Extension to NNTP Brian Kantor
- Re: ietf-nntp FAQ Extension to NNTP Stan Barber
- Revision of RFC 1036 (Was: Re: ietf-nntp FAQ Exte… Jonathan Grobe
- Re: ietf-nntp FAQ Extension to NNTP Jacob Palme
- Re: ietf-nntp FAQ Extension to NNTP Stan Barber
- Re: ietf-nntp FAQ Extension to NNTP Brian Kantor