idnits 2.17.00 (12 Aug 2021) /tmp/idnits32434/draft-ietf-poised95-ietf-orgs-02.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 (2022-05-14) 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) 2022 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. == No 'Intended status' indicated for this document; assuming Proposed Standard 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.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (May 1996) is 9495 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) ** Obsolete normative reference: RFC 1603 (ref. 'A') (Obsoleted by RFC 2418) ** Obsolete normative reference: RFC 1602 (ref. 'B') (Obsoleted by RFC 2026) -- Possible downref: Non-RFC (?) normative reference: ref. 'C' ** Obsolete normative reference: RFC 1601 (ref. 'D') (Obsoleted by RFC 2850) -- Possible downref: Non-RFC (?) normative reference: ref. 'E' -- Possible downref: Non-RFC (?) normative reference: ref. 'F' -- Possible downref: Non-RFC (?) normative reference: ref. 'G' -- Possible downref: Non-RFC (?) normative reference: ref. 'H' Summary: 12 errors (**), 0 flaws (~~), 1 warning (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Richard Hovey 3 Internet Draft Digital Equipment Corporation 4 Scott Bradner 5 Harvard University 6 May 1996 8 The Organizations Involved in the IETF Standards Process 10 12 Status of this Memo 14 This document is an Internet-Draft. Internet-Drafts are working docu- 15 ments of the Internet Engineering Task Force (IETF), its areas, and 16 its working groups. Note that other groups may also distribute work- 17 ing documents as Internet-Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six months 20 and may be updated, replaced, or obsoleted by other documents at any 21 time. It is inappropriate to use Internet-Drafts as reference mate- 22 rial or to cite them other than as ``work in progress.'' 24 To learn the current status of any Internet-Draft, please check the 25 1id-abstracts.txt listing contained in the Internet-Drafts Shadow 26 Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), 27 munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or 28 ftp.isi.edu (US West Coast). 30 Abstract 32 This document describes the organizations involved in the IETF. This 33 includes descriptions of the IESG and Working Groups and the rela- 34 tionship with the Internet Society. 36 1. The IETF Standards Process 38 The process used by the Internet community for the standardization of 39 protocols and procedures is described in [B]. That document defines 40 the stages in the standardization process, the requirements for mov- 41 ing a document between stages and the types of documents used during 42 this process. It also addresses the intellectual property rights and 43 copyright issues associated with the standards process. 45 2. Internet Standards Organizations and Roles 47 The following organizations and organizational roles are involved in 48 the Internet standards process. Contact information is contained in 49 Appendix A. 51 2.1 Internet Engineering Task Force 53 The Internet Engineering Task Force (IETF) is an open international 54 community of network designers, operators, vendors and researchers 55 concerned with the evolution of the Internet architecture and the 56 smooth operation of the Internet. It is the principal body engaged 57 in the development of new Internet Standard specifications. 59 2.2 IETF Working Groups 61 The technical work of the IETF is done in its Working Groups, which 62 are organized by topics into several Areas (e.g., routing, network 63 management, security, etc.) under the coordination of Area Directors. 64 Working Groups typically have a narrow focus and a lifetime bounded 65 by completion of a specific task. 67 For all purposes relevant to the Internet Standards development pro- 68 cess, membership in the IETF and its Working Groups is defined to be 69 established solely and entirely by individual participation in IETF 70 and Working Group activities. Participation in the IETF and its Work- 71 ing Groups is by individual technical contributors rather than by 72 formal representatives of organizations. 74 Anyone with the time and interest to do so is entitled and urged to 75 participate actively in one or more IETF Working Groups and to attend 76 IETF meetings which are held three times a year. In most cases 77 active Working Group participation is possible through electronic 78 mail alone. Internet video conferencing is also being used to allow 79 for remote participation. 81 To ensure a fair and open process, participants in the IETF and its 82 Working Groups must be able to disclose, and must disclose to the 83 Working Group chairs any relevant current or pending intellectual 84 property rights that are reasonably and personally known to the par- 85 ticipant if they participate in discussions about a specific technol- 86 ogy. 88 New Working Groups are established within the IETF by explicit char- 89 ter. The guidelines and procedures for the formation and operation 90 of IETF working groups are described in detail in [A]. 92 A Working Group is managed by one or more Working Group chairs (see 93 section 2.9). It may also include editors of documents that record 94 the group's work (see section 2.10). Further details of Working Group 95 operation are contained in [A] 97 IETF Working Groups display a spirit of cooperation as well as a high 98 degree of technical maturity; IETF participants recognize that the 99 greatest benefit for all members of the Internet community results 100 from cooperative development of technically superior protocols and 101 services. 103 2.3 IETF Secretariat 105 The administrative functions necessary to support the activities of 106 the IETF are performed by a Secretariat consisting of the IETF Execu- 107 tive Director and his or her staff. The IETF Executive Director is 108 the formal point of contact for matters concerning any and all 109 aspects of the Internet standards process, and is responsible for 110 maintaining the formal public record of the Internet standards pro- 111 cess [B]. 113 2.4 Internet Society 115 The Internet Society (ISOC) is an international organization con- 116 cerned with the growth and evolution of the worldwide Internet and 117 with the social, political, and technical issues that arise from its 118 use. The ISOC is an organization with individual and organizational 119 members. The ISOC is managed by a Board of Trustees elected by the 120 worldwide individual membership. 122 Internet standardization is an organized activity of the ISOC, with 123 the Board of Trustees being responsible for ratifying the procedures 124 and rules of the Internet standards process [B]. 126 The way in which the members of the ISOC Board of Trustees are 127 selected, and other matters concerning the operation of the Internet 128 Society, are described in the ISOC By Laws [C]. 130 2.5 Internet Engineering Steering Group 132 The Internet Engineering Steering Group (IESG) is the part of the 133 Internet Society responsible for the management of the IETF technical 134 activities. It administers the Internet Standards process according 135 to the rules and procedures defined in [B]. The IESG is responsible 136 for the actions associated with the progression of technical specifi- 137 cation along the "standards track" including the initial approval of 138 new Working Groups and the final approval of specifications as Inter- 139 net Standards. The IESG is composed of the IETF Area Directors and 140 the chair of the IETF, who also serves as the chair of the IESG. 142 The members of the IESG are nominated by a nominations committee (the 143 Nomcom), and are approved by the IAB. See [E] for a detailed 144 description of the Nomcom procedures. Other matters concerning its 145 organization and operation, are described in the IESG charter [does 146 not yet exist]. 148 2.6 Internet Architecture Board 150 The Internet Architecture Board (IAB) is chartered by the Internet 151 Society Trustees to provide oversight of the architecture of the 152 Internet and its protocols. The IAB appoints the IETF chair and is 153 responsible for approving other IESG candidates put forward by the 154 IETF nominating committee. The IAB is also responsible for reviewing 155 and approving the charters of new Working Groups that are proposed 156 for the IETF. 158 The IAB provides oversight of the process used to create Internet 159 Standards and serves as an appeal board for complaints of improper 160 execution of the standards process [B]. In general it acts as source 161 of advice to the IETF, the ISOC and the ISOC Board of Trustees con- 162 cerning technical, architectural, procedural, and policy matters per- 163 taining to the Internet and its enabling technologies. 165 The members of the IAB are nominated by a nominations committee (the 166 Nomcom), and are approved by the ISOC board. See [E] for a detailed 167 description of the Nomcom procedures. The membership of the IAB con- 168 sists of members selected by the Nomcom process and the IETF chair 169 sitting as a ex-officio member. Other matters concerning its organi- 170 zation and operation, are described in the IAB charter [D]. 172 2.7 Internet Assigned Numbers Authority 174 Many protocol specifications include numbers, keywords, and other 175 parameters that must be uniquely assigned. Examples include version 176 numbers, protocol numbers, port numbers, and MIB numbers. The Inter- 177 net Assigned Numbers Authority (IANA) is responsible for assigning 178 the values of these protocol parameters for the Internet. The IANA 179 publishes tables of all currently assigned numbers and parameters in 180 RFCs entitled "Assigned Numbers" [E]. The IANA functions as the "top 181 of the pyramid" for DNS and Internet Address assignment establishing 182 policies for these functions. 184 The functions of the IANA are performed by one or more individuals or 185 organizations selected in accordance with the procedures defined by 186 the IANA charter [F]. 188 2.8 Request for Comments Editor 190 The RFC publication series [B] is managed by an Editor (which may in 191 practice be one or more individuals) responsible both for the mechan- 192 ics of RFC publication and for upholding the traditionally high tech- 193 nical and editorial standards of the RFC series. 195 The functions of the RFC Editor are performed by one or more 196 individuals or organizations selected in accordance with the proce- 197 dures defined by the RFC Editor charter [G]. 199 2.9 Working Group Chair 201 Each IETF Working Group is headed by a chair (or by co-chairs) with 202 the responsibility for directing the group's activities, presiding 203 over the group's meetings, and ensuring that the commitments of the 204 group with respect to its role in the Internet standards process are 205 met. In particular, the WG chair is the formal point of contact 206 between the WG and the IESG, via the Area Director of the area to 207 which the WG is assigned. 209 The details on the selection and responsibilites of an IETF Working 210 Group chair can be found in [A]. 212 2.10 Document Editor Most IETF Working Groups focus their efforts on a 213 document, or set of documents, that capture the results of the 214 group's work. A Working Group generally designates a person or per- 215 sons to serve as the Editor for a particular document. The Document 216 Editor is responsible for ensuring that the contents of the document 217 accurately reflect the decisions that have been made by the working 218 group. 220 As a general practice, the Working Group Chair and Document Editor 221 positions are filled by different individuals to help ensure that the 222 resulting documents accurately reflect the consensus of the Working 223 Group and that all processes are followed. 225 2.11 Internet Research Task Force The Internet Research Task Force 226 (IRTF) is not directly involved in the Internet standards process. 227 It investigates topics considered to be too uncertain, too advanced, 228 or insufficiently well-understood to be the subject of Internet stan- 229 dardization. When an IRTF activity generates a specification that is 230 sufficiently stable to be considered for Internet standardization, 231 the specification is processed through the IETF using the rules in 232 this document. 234 The IRTF is composed of individual Working Groups, but its structure 235 and mode of operation is much less formal than that of the IETF, due 236 in part to the fact that it does not participate directly in the 237 Internet standards process. The organization and program of work of 238 the IRTF is overseen by the Internet Research Steering Group (IRSG), 239 which consists of the chairs of the IRTF Working Groups. Details of 240 the organization and operation of the IRTF and its Working Groups may 241 be found in [H]. 243 3. Security Considerations 244 Security is not addressed in this memo 246 4. References 248 [A] Huizer,E. and D. Crocker, "IETF Working Group Guidelines and 249 Procedures", 03/24/1994. RFC 1603 251 [B] Bradner, S. (Ed) "The Internet Standards Process -- Revision 3", 252 x/y/96, RFC 1602bis 254 [C] By - Laws for the Internet Society, as amended: 255 gopher://info.isoc.org/00/isoc/basic_docs/bylaws.txt 257 [D] Huitema, C. and the IAB, "Charter of the Internet Architecture 258 Board (IAB)", 3/22/94, RFC1601 260 [E] Galvin, J (Ed.), "IAB and IESG Selection, Confirmation, and 261 Recall Process: Operation of the Nominating and Recall Committees", 262 x/y/96, nomcom RFC 264 [F] IANA Charter 266 [G] RFC Editor Charter 268 [H] IRTF charter 270 5. Author's Addresses: 272 Richard Hovey 273 Digital Equipment Corporation 274 1401 H Street NW 275 Washington DC 20005 277 email: hovey@wnpv01.enet.dec.com 278 phone: +1 202 383 5615 280 Scott Bradner 281 Harvard University 282 1350 Mass Ave. Rm 813 283 Cambridge MA 02138 285 email: sob@harvard.edu 286 phone: +1 617 495 3864 288 Appendix A - contact information 290 IETF - ietf@ietf.org, http://www.ietf.org 291 IESG - iesg@ietf.org 293 IAB - iab@ietf.org