Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.toronto.edu!ietf-nntp-distribution-owner Message-ID: Date: Tue, 4 Jun 1991 16:42:47 -0400 From: lear@turbo.bio.net (Eliot) Original-To: ietf-nntp@turbo.bio.net Subject: a new nntp draft Newsgroups: list.ietf-nntp Distribution: list Sender: list-admin@cs.toronto.edu Approved: list.ietf-nntp@mail.cs.toronto.edu Lines: 31 Here is the state of the world with the new version of NNTP. I am in the process of writing a draft, which I hope to post to this group within the next week or so. That draft currently has ALL the proposed changes listed in Brian Kantor's draft. I saw a note from Brian questioning his method of options negotiation in that draft, but for the moment, I intend to set up what I'm working on as a strawman (there are a few parts that I definitely want to change). In the draft I'm breaking down the functionality into three groups - commands needed for news readering functionality, commands needed for transfer functionality, and commands needed for both. The goal is that eventually (probably not this release) we ought to be able to drop the commands needed for news reading functionality, when the news reading protocol is done. To that end, I now invite your comments about how a news reader protocol ought to be organized. For example: - Should the protocol retain an ASCII command interface, like NNTP? - How can we handle network database access? What interface should be provided for a database? Natural language? Some form of regular expression search? etc? - What form of access control / authentication mechanism should we include? Comments? Eliot Lear [lear@turbo.bio.net]