stewart@xyplex.com (Bob Stewart) (06/02/90)
Hi,
This is to announce the creation of an IETF working group (WG) to apply the
host requirements RFCs to special purpose hosts. See the attached preliminary
WG charter for more information.
Bob Stewart
Chair, IETF Special-purpose Host Requirements WG
--------
Special-purpose Host Requirements Working Group
Chairman:
Bob Stewart/Xyplex rlstewart@eng.xyplex.com
First Meeting:
August, 1990
Mailing Lists:
General discussion: ietf-hosts@nnsc.nsf.net
To subscribe: ietf-hosts-request@nnsc.nsf.net
Description of Working Group:
The Special-purpose Host Requirements working group is chartered to
clarify application of the Host Requirements RFCs (1122 and 1123) to systems
that are technically hosts but are not intended to support general network
applications. These special-purpose hosts include, for example, terminal
servers (a "Telnet host"), or file servers (an "FTP host" or an "NFS host").
The Host Requirements RFCs address the typical, general-purpose system
with a variety of applications and an open development environment, and gives
only passing consideration to special-purpose hosts. As a result, suppliers
of special-purpose hosts must bend the truth or make excuses when users
evaluate their products against the Requirements RFCs. Users must then decide
whether such a product is in fact deficient or the requirements truely do not
apply. This process creates work and confusion, and undermines the value of
the RFCs. The commercial success of the Internet protocols and their use in
increasingly unsophisticated environments exacerbates the problem.
The working group must define principles and examples for proper
functional subsets of the general-purpose host and specifically state how such
subsets affect the requirements. The working group must determine the balance
between an exhaustive list of specific special-purpose hosts and philosphy
that remains subject to debate. For the most part, it should be possible to
base decisions on existing experience and implementations. The
special-purpose requirements will be stated as differences from the existing
RFCs, not replacements, and will refer rather than stand alone.
Since they define strict subsets of the Host Requirements RFCs, the
Special-purpose Host Requirements appear to be an easier job and can be
developed and stabilized within 8-12 months. Most of the group's business can
be conducted over the Internet through email.
Goals and Milestones:
1. July 1990: mailing list discussion of charter and collection of concerns.
2. August 1990: First IETF Meeting: discussion and final approval of charter;
discussion and agreement on approach, including models, format, level
and type of detail. Make writing assignments.
3. October 1990: First draft document.
4. November 1990: Second IETF Meeting: review first draft document,
determine necessary revisions. Follow up discussion on mailing list.
5. January 1991: Revised document.
6. February 1991: Third IETF Meeting: make document an Internet Draft.
Continue revisions based on comments received at meeting and over e-mail.
7. April 1991: Final draft document.
6. May 1991: Fourth IETF meeting: review final draft and if OK, give
to IESG for publication as RFC.