usefor-usepro-03 February 2005

INTERNET-DRAFT                               Charles H. Lindsey
Usenet Format Working Group                  University of Manchester
                                   February 2005

      News Article Architecture and Protocols
         <draft-ietf-usefor-usepro-03.txt>

Status of this Memo

   By submitting this Internet-Draft, I certify that any applicable
   patent or other IPR claims of which I am aware have been
   disclosed, or will be disclosed, and any of which I become aware
   will be disclosed, in accordance with RFC 3668.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups. Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six
   months and may be updated, replaced, or obsoleted by other
   documents at any time. It is inappropriate to use Internet-Drafts
   as reference material or to cite them other than as "work in
   progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.html.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire in August 2005.

Abstract

   This Draft, together with its companion draft [USEFOR], are
   intended as standards track documents, together obsoleting RFC
   1036, which itself dates from 1987.

   This Standard defines the architecture of Netnews systems and
   specifies the requirements to be met by software which originates,
   distributes, stores and displays Netnews articles.

   Since the 1980s, Usenet has grown explosively, and many Internet and
   non-Internet sites now participate. In addition, the Netnews
   technology is now in widespread use for other purposes.

   Backward compatibility has been a major goal of this endeavour, but
   where this standard and earlier documents or practices conflict, this
   standard should be followed. In most such cases, current practice is
   already compatible with these changes.

   A companion Current Best Practice document [USEAGE], addressing
   requirements which are present for Social rather than Normative
   reasons is in preparation.



[The use of the words "this standard" within this document when
referring to itself does not imply that this draft yet has pretensions
to be a standard, but rather indicates what will become the case if and
when it is accepted as an RFC with the status of a proposed or draft
standard.]

[Remarks enclosed in square brackets and aligned with the left margin,
such as this one, are not part of this draft, but are editorial notes to
explain matters amongst ourselves, or to point out alternatives, or to
assist the RFC Editor.]

[In this draft, references to [NNTP] are to be replaced by references to
the RFC arising from the series of drafts draft-ietf-nntpext-base-*.txt,
which has now passed its IETF last call.]


                 Table of Contents

1.  Introduction ..................................................    0
  1.1.  Basic Concepts ............................................    0
  1.2.  Objectives ................................................    0
  1.3.  Historical Outline ........................................    0
2.  Definitions, Notations and Conventions ........................    0
  2.1.  Definitions ...............................................    0
  2.2.  Defining the Architecture .................................    0
  2.3.  Variant Headers ...........................................    0
  2.4.  Textual Notations .........................................    0
3.  Changes to the existing protocols .............................    0
  3.1.  Principal Changes .........................................    0
  3.2.  Transitional Arrangements .................................    0
4.  Transport .....................................................    0
5.  Definition of new Media Types .................................    0
  5.1.  Application/news-transmission .............................    0
  5.2.  Message/news obsoleted ....................................    0
  5.3.  Application/news-groupinfo ................................    0
  5.4.  Application/news-checkgroups ..............................    0
6.  Control Messages ..............................................    0
  6.1.  Digital Signature of Headers ..............................    0
  6.2.  Group Control Messages ....................................    0
    6.2.1.  The 'newgroup' Control Message ........................    0
      6.2.1.1.  The Body of the 'newgroup' Control Message ........    0
      6.2.1.2.  Initial Articles ..................................    0
      6.2.1.3.  Example ...........................................    0
    6.2.2.  The 'rmgroup' Control Message .........................    0
      6.2.2.1.  Example ...........................................    0
    6.2.3.  The 'mvgroup' Control Message .........................    0
      6.2.3.1.  Example ...........................................    0
    6.2.4.  The 'checkgroups' Control Message .....................    0
  6.3.  Cancel ....................................................    0
  6.4.  Ihave, sendme .............................................    0
  6.5.  Obsolete control messages.  ...............................    0
7.  Duties of Various Agents ......................................    0
  7.1.  General principles to be followed .........................    0
  7.2.  Duties of an Injecting Agent ..............................    0
    7.2.1.  Proto-articles ........................................    0
    7.2.2.  Procedure to be followed by Injecting Agents ..........    0
    7.2.3.  Procedure for Forwarding to a Moderator ...............    0
  7.3.  Duties of a Relaying Agent ................................    0
    7.3.1.  Path-Header Example ...................................    0
  7.4.  Duties of a Serving Agent .................................    0
  7.5.  Duties of a Posting Agent .................................    0
  7.6.  Duties of a Followup Agent ................................    0
  7.7.  Duties of a Reading Agent .................................    0
  7.8.  Duties of a Moderator .....................................    0
  7.9.  Duties of a Gateway .......................................    0
    7.9.1.  Duties of an Outgoing Gateway .........................    0
    7.9.2.  Duties of an Incoming Gateway .........................    0
    7.9.3.  Example ...............................................    0
8.  Security and Related Considerations ...........................    0
  8.1.  Leakage ...................................................    0
  8.2.  Attacks ...................................................    0
    8.2.1.  Denial of Service .....................................    0
    8.2.2.  Compromise of System Integrity ........................    0
  8.3.  Liability .................................................    0
9.  IANA Considerations ...........................................    0
10.  References ...................................................    0
11.  Acknowledgements .............................................    0
12.  Contact Address ..............................................    0
Appendix A.1 - A-News Article Format ..............................    0
Appendix A.2 - Early B-News Article Format ........................    0
Appendix A.3 - Obsolete Control Messages ..........................    0
Appendix B - Notices ..............................................    0
Appendix C - Change Log ...........................................    0


[This draft [USEPRO] and its partner [USEFOR] are an interim stage in
the splitting into two parts of the earlier draft [ARTICLE].  There is a
certain amount of material - basic concepts, definitions, etc - which
ultimately need occur in only one of the documents, and further such
material which may not be needed at all (e.g. terms currently defined
which in the event may not get used). For the moment, all such material
has been retained in the present draft (it being, in any case, easier to
take unwanted stuff out than to put new stuff in). It has also to be
decided, for such material which is needed by both documents, which one
(the "Primary") should contain it and which one should incorporate it by
reference (essentially, this draft is written so that it could be the
Primary).]

--- ../usefor-usepro-02/TOC.out          December 2004
+++ ../usefor-usepro-03/TOC.out          February 2005
@@ -1,9 +1,9 @@
 INTERNET-DRAFT                               Charles H. Lindsey
 Usenet Format Working Group                  University of Manchester
-                                   December 2004
+                                   February 2005
 
       News Article Architecture and Protocols
-         <draft-ietf-usefor-usepro-02.txt>
+         <draft-ietf-usefor-usepro-03.txt>
 
 Status of this Memo
 
@@ -29,7 +29,7 @@
    The list of Internet-Draft Shadow Directories can be accessed at
    http://www.ietf.org/shadow.html.
 
-   This Internet-Draft will expire in June 2005.
+   This Internet-Draft will expire in August 2005.
 
 Abstract
 
@@ -81,9 +81,7 @@
 2.  Definitions, Notations and Conventions ........................    0
   2.1.  Definitions ...............................................    0
   2.2.  Defining the Architecture .................................    0
-  2.3.  Header Properties .........................................    0
-    2.3.1.  Inheritable Headers ...................................    0
-    2.3.2.  Variant Headers .......................................    0
+  2.3.  Variant Headers ...........................................    0
   2.4.  Textual Notations .........................................    0
 3.  Changes to the existing protocols .............................    0
   3.1.  Principal Changes .........................................    0
@@ -142,6 +140,7 @@
 Appendix B - Notices ..............................................    0
 Appendix C - Change Log ...........................................    0
 
+
 [This draft [USEPRO] and its partner [USEFOR] are an interim stage in
 the splitting into two parts of the earlier draft [ARTICLE].  There is a
 certain amount of material - basic concepts, definitions, etc - which
@@ -154,12 +153,4 @@
 (the "Primary") should contain it and which one should incorporate it by
 reference (essentially, this draft is written so that it could be the
 Primary).]
-
-[Again, references in this document to sections which ultimately are
-expected to be in [USEFOR] are still to the old sections in [ARTICLE],
-since [USEFOR] is not stabilized enough to refer to specific sections in
-it yet. These references can be recognized by being prefixed with "a-".
-These references can be fixed up later as we find the proper places for
-them to point to. In any case, there will doubtless be more toing and
-froing of texts between the two documents before we are done.]