draft-ietf-nntpext-base-04.txt   draft-ietf-nntpext-base-05.txt 
skipping to change at line 24 skipping to change at line 24
(IETF), its areas, and its working groups. Note that other (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet- groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or made obsolete by other months and may be updated, replaced, or made obsolete by other
documents at any time. It is inappropriate to use Internet- documents at any time. It is inappropriate to use Internet-
Drafts as reference material or to cite them other than as Drafts as reference material or to cite them other than as
"work in progress." "work in progress."
To view the entire list of current Internet-Drafts, please check To learn the current status of any Internet-Draft, please
the "1id-abstracts.txt" listing contained in the Internet-Drafts check the "1id-abstracts.txt" listing contained in the
Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net Internet-Drafts Shadow Directories on ftp.is.co.za (Africa),
(Northern Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au nic.nordu.net (Europe), munnari.oz.au (Pacific Rim),
(Pacific Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu ds.internic.net (US East Coast), or ftp.isi.edu (US West
(US West Coast). Coast).
This document is a product of the NNTP Working Group, chaired This document is a product of the NNTP Working Group, chaired
by Ned Freed and Stan Barber. by Ned Freed and Stan Barber.
2. Abstract 2. Abstract
The Network News Transport Protocol has been in use in the The Network News Transport Protocol has been in use in the
Internet for a decade and remains one of the most popular Internet for a decade and remains one of the most popular
protocols (by volume) in use today. This document is a protocols (by volume) in use today. This document is a
replacement for RFC 977 and officially updates the protocol replacement for RFC 977 and officially updates the protocol
specification. It clarifies some vagueness in RFC 977, specification. It clarifies some vagueness in RFC 977,
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/