I-D ACTION:draft-ietf-tcpimpl-needdoc-00.txt

Internet-Drafts@ns.ietf.org Fri, 13 March 1998 13:38 UTC

Return-Path: <owner-tcp-impl@relay.engr.sgi.com>
Message-Id: <199803131338.IAA27953@ns.ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;@cnri.reston.va.us
Cc: tcp-impl@engr.sgi.com
From: Internet-Drafts@ns.ietf.org
Reply-to: Internet-Drafts@ns.ietf.org
Subject: I-D ACTION:draft-ietf-tcpimpl-needdoc-00.txt
Date: Fri, 13 Mar 1998 08:38:39 -0500
Sender: owner-tcp-impl@relay.engr.sgi.com
Precedence: bulk
Status: RO
Content-Length: 3705
Lines: 105

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the TCP Implementation Working Group of the IETF.

	Title		: TCP Implementation Problems 
                          That Need To Be Documented
	Author(s)	: V. Paxson, M. Allman
	Filename	: draft-ietf-tcpimpl-needdoc-00.txt
	Pages		: 5
	Date		: 12-Mar-98
	
   The TCP-IMPL working group has documented a number of TCP
   implementation problems [PADHV98].  However, a significant number
   still have not been fully described and documented in the form used
   in [PADHV98].  This memo briefly describes a number of these,
   including commentary as to the authors' opinions regarding the
   importance of documenting the problem.  This memo is *not* intended
   to ever see light as an RFC of some form; its sole function is to
   facilitate working group discussion of which problems are more
   pressing to document than others, and to aid in arriving at a
   decision as to when [PADHV98] will be sufficiently complete to merit
   its publication as an Informational RFC.

   We divide the descriptions into ''serious'' problems, meaning those    we think should be included in [PADHV98] prior to its publication;
   ''security'' problems, which might not be viewed as implementation
   problems per se, but represent significant security problems of which
   TCP implementors should be aware; and ''less serious'' problems, those
   that, if the working group fails to find volunteers to document them,
   should not hold up [PADHV98].
 
   It might be worthwhile to separate the security problems out into
   their own document.  We particularly solicit working group input on
   this subject.


Internet-Drafts are available by anonymous FTP.  Login with the username
"anonymous" and a password of your e-mail address.  After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-tcpimpl-needdoc-00.txt".
A URL for the Internet-Draft is:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-tcpimpl-needdoc-00.txt

Internet-Drafts directories are located at:

	Africa:	ftp.is.co.za
	
	Europe: ftp.nordu.net
		ftp.nis.garr.it
			
	Pacific Rim: munnari.oz.au
	
	US East Coast: ds.internic.net
	
	US West Coast: ftp.isi.edu

Internet-Drafts are also available by mail.

Send a message to:	mailserv@ietf.org.  In the body type:
	"FILE /internet-drafts/draft-ietf-tcpimpl-needdoc-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
ftp://ftp.ietf.org/internet-drafts/draft-ietf-tcpimpl-needdoc-00.txt"><ftp://ftp.ietf.org/internet-drafts/draft-ietf-tcpimpl-needdoc-00.txt>