Editor's note: These minutes have note yet been edited. POISSON/Poised 95 minutes Chair and minutes: Erik Huizer, SURFnet ExpertiseCentrum ------- The poised95 WG has finished it's work. This meeting was a bof as a start of a new WG called POISSON. The charter of the POISSON WG contains 2 major workitems: - Review the standards document structure in light of the new standards process. - Review RFC-1603 (procedures and guidelines for WG chairs and Areas) in the light of the new standards process. Other minor workitems are: - code of conduct for IETF - review of documents from other bodies that relate to the IETF standards process (e.g. IESG charter). Charter discussion ================== two minor chasnges to the charter were suggested. Otherwise everyone agreed the charter should be submitted to the IESG. Document structure =================== There are three issues to discuss: 1. The RFC series. Confusion on RFCs versus standards. 2. The subseries. Confusion on BCP versus AS versus TS. 3. The format. Text as the main version or maybe HTML. A discussion was held on the RFC series as a publication mechanism for the IETF standards. It was suggested that modifying the RFC series won't work, but that we either use RFCs for standards work only, or take the standards work elsewhere. The alternative is of course to do nothing. There was no concensus, and the matter will be taken up again after proposals have been documented to the mailing list. In the mean time the WG suggests to the RFC editor to a) starting with RFC 2000 to assure that the Internet Standards document is is republished every time as an RFC with a number ending in 00. (RFC 2100, RFC 2200 etc.). This will make standards more easily findable and accessible. b) provide an up-to-date Webpage with an overview of the Intenet standards with pointers to the relevant documents. Proposals for revising the subseries and format were deferred to the list. Code of conduct =============== The code of conduct document by Mike O'Dell was discussed briefly. It was suggested to enhance the document with example practices (e.g. how to react to a mailinglist FLAME). This will be done on the list.