IETF Logo Mail Archive

Re: Submission of charter for POISON

"Erik Huizer (SURFnet ExpertiseCentrum bv)" <Erik.Huizer@sec.nl> Sat, 20 July 1996 18:13 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07950; 20 Jul 96 14:13 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa07946; 20 Jul 96 14:13 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa09254; 20 Jul 96 14:13 EDT
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07939; 20 Jul 96 14:12 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa07935; 20 Jul 96 14:12 EDT
Received: from survis.surfnet.nl by CNRI.Reston.VA.US id aa09244; 20 Jul 96 14:12 EDT
Received: from surah.surfnet.nl by survis.surfnet.nl with SMTP (PP) with ESMTP; Sat, 20 Jul 1996 20:09:39 +0200
Received: from surfnet.nl (actually host surah.surfnet.nl) by surah.surfnet.nl with SMTP (PP) with ESMTP; Sat, 20 Jul 1996 20:10:35 +0200
To: Keith Moore <moore@cs.utk.edu>
cc: Fred Baker <fred@cisco.com>, IESG <iesg@CNRI.Reston.VA.US>, poised@tis.com
Subject: Re: Submission of charter for POISON
In-reply-to: Your message of "Fri, 19 Jul 1996 14:55:45 EDT." <199607191855.OAA04620@ig.cs.utk.edu>
Organisation: SURFnet ExpertiseCentrum bv
Address: Radboudburcht, P.O. Box 19115, 3501 DC Utrecht, NL
Phone: +31 302 305 305
Telefax: +31 302 305 329
X-url: http://www.sec.nl/persons/huizer/
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <20694.837886232.1@surfnet.nl>
Date: Sat, 20 Jul 1996 20:10:32 +0200
X-Orig-Sender: iesg-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Erik Huizer (SURFnet ExpertiseCentrum bv)" <Erik.Huizer@sec.nl>
Message-ID: <9607201412.aa09244@CNRI.Reston.VA.US>

And we already started working on it. It is in the charter as the
second bullit item:
-Standards process; The standards process document as produced by
Poised95 is
  not yet complete. The document needs to be updated with specific
regard to
  the standards document structure categorization and publication.
  Proposed editor: Scott Bradner

At the last meeting we tsarted discussing the document structure.
Discussion can be divided into three separate issues:
- How to distinguish IETF developed and Standards RFCs from plain vanilla RFCs.
  (i.e. STD versus RFC or STD as RFC)
- What categories Standards and IETF RFCs we need and how we name
them. (i.e. BCP, TS, AS, etc.)
- The format of the documents. (i.e. is ASCII outdated? HTML? PS?,
PDS?)


Erik

v2.23.0 | Report a Bug | By Email