idnits 2.17.1 draft-iab-wgannounce-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-19) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. ** Expected the document's filename to be given on the first page, but didn't find any == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 3 longer pages, the longest (page 1) being 65 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == Couldn't figure out when the document was first submitted -- there may comments or warnings related to the use of a disclaimer for pre-RFC5378 work that could not be issued because of this. Please check the Legal Provisions document at https://trustee.ietf.org/license-info to determine if you need the pre-RFC5378 disclaimer. -- The document date (October 1997) is 9683 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 9 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IAB and IESG B. Carpenter 3 Internet Draft 4 October 1997 6 Improved Working Group Coordination 8 Abstract 10 draft-iab-wgannounce-00.txt 12 This is a proposal for a pragmatic way to improve working group 13 coordination between various standards-related organisations, by use 14 of a shared mailing list for early announcement of new activities. 16 Status of this Memo 18 This document is an Internet-Draft. Internet-Drafts are working 19 documents of the Internet Engineering Task Force (IETF), its areas, 20 and its working groups. Note that other groups may also distribute 21 working documents as Internet-Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet- Drafts as reference 26 material or to cite them other than as ``work in progress.'' 28 To learn the current status of any Internet-Draft, please check the 29 ``1id-abstracts.txt'' listing contained in the Internet- Drafts 30 Shadow Directories on ds.internic.net (US East Coast), nic.nordu.net 31 (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific 32 Rim). 34 Proposal 36 A number of organisations develop technical specifications or 37 standards related to the Internet. Especially in the upper protocol 38 layers, the areas of interest often overlap between two or more 39 organisations. It is therefore in everyone's interest that when new 40 activities are started in a given organisation, the others know about 41 it. This is not intended to cause forced marriages of working groups, 42 or interference by one organisation in another, but just to ensure 43 that everyone will know where liaison and coordination is needed. 45 This proposal has been deliberately kept as simple and easy as 46 possible, with the intention of being trivial to implement and 47 operate. 49 The proposal is that an ad hoc email list should be created, e.g. 50 new-work@ietf.org . Each participating organisation would supply 51 approximately two email addresses to be added to this list. 52 [Examples for the IETF could be the IAB Chair and the IETF Executive 53 Director]. It is suggested that these addresses should be 54 individuals rather than mailing lists, to avoid email difficulties 55 with multiple layers of distribution lists. 57 Each participating organisation would undertake to send an ASCII 58 message to this list *prior to* deciding to start a new 59 standardisation effort related to the Internet. That is all; there is 60 no other formal obligation. The addressees in each organisation are 61 expected to distribute these messages within their own organisation 62 as relevant. They should follow up any case where there appears to 63 be an issue of coordination or liaison, using any suitable 64 procedures. 66 The granularity of this will depend on each organisation and will be 67 determined by each organisation. [An example for the IETF would be 68 to send each draft WG Charter or charter update to the list, or, for 69 JTC1, each NWI submission. For organisations with quasi-permanent 70 working groups, it would be necessary to send a message for each new 71 major work item.] 73 In cases where complete specifications are being fast-tracked by one 74 of the participating organisations, the warning message should be 75 sent at the earliest possible stage, before formal processing has 76 started. 78 The initial list of organisations invited to join this system is (in 79 alphabetical order) 81 DAVIC ECMA ETSI IETF ITU-T JTC1 OMG TOG W3C 83 The list can of course be expanded, but should not include 84 organisations of purely national or otherwise very limited scope, and 85 should only include organisations that actively produce Internet- 86 related technical specifications. Lower layer fora (ATM, Frame Relay, 87 ADSL...) are not included because they generally have simple one-to- 88 one relationships with Internet standards from the IETF alone. 90 Security considerations 92 It would be preferable if the authorised senders to the list used a 93 common method of email authentication. 95 Acknowledgements 97 The IAB and the IESG contributed to this proposal. 99 Author's Address 101 Brian E Carpenter 102 Internet Division 103 IBM United Kingdom Laboratories brian@hursley.ibm.com 104 MP 185, Hursley Park phone: +44 1962 816833 105 Winchester, Hampshire SO21 2JN, UK fax: +44 1962 818101