idnits 2.17.1 draft-ietf-poised95-ietf-orgs-01.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-16) 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. == 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: ---------------------------------------------------------------------------- == Line 217 has weird spacing: '...working group...' -- 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 (April 1996) is 10228 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 (~~), 2 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Richard Hovey 2 Internet Draft Digital Equipment Corporation 3 Scott Bradner 4 Harvard University 5 April 1996 7 The Organizations Involved in the IETF Standards Process 9 11 Status of this Memo 13 This document is an Internet-Draft. Internet-Drafts are working 14 documents of the Internet Engineering Task Force (IETF), its areas, 15 and its working groups. Note that other groups may also distribute 16 working documents as Internet-Drafts. 18 Internet-Drafts are draft documents valid for a maximum of six months 19 and may be updated, replaced, or obsoleted by other documents at any 20 time. It is inappropriate to use Internet-Drafts as reference 21 material or to cite them other than as ``work in progress.'' 23 To learn the current status of any Internet-Draft, please check the 24 1id-abstracts.txt listing contained in the Internet-Drafts Shadow 25 Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), 26 munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or 27 ftp.isi.edu (US West Coast). 29 Abstract 31 This document describes the organizations involved in the IETF. This 32 includes descriptions of the IESG and Working Groups and the 33 relationship with the Internet Society. 35 1. The IETF Standards Process 37 The process used by the Internet community for the standardization of 38 protocols and procedures is described in [B]. That document defines 39 the stages in the standardization process, the requirements for 40 moving a document between stages and the types of documents used 41 during this process. It also addresses the intellectual property 42 rights and copyright issues associated with the standards process. 44 2. Internet Standards Organizations and Roles 46 The following organizations and organizational roles are involved in 47 the Internet standards process. Contact information is contained in 48 Appendix A. 50 2.1 Internet Engineering Task Force 52 The Internet Engineering Task Force (IETF) is an open international 53 community of network designers, operators, vendors and researchers 54 concerned with the evolution of the Internet architecture and the 55 smooth operation of the Internet. It is the principal body engaged 56 in the development of new Internet Standard specifications. 58 2.2 IETF Working Groups 60 The technical work of the IETF is done in its Working Groups, which 61 are organized by topics into several Areas (e.g., routing, network 62 management, security, etc.) under the coordination of Area Directors. 63 Working Groups typically have a narrow focus and a lifetime bounded 64 by completion of a specific task. 66 For all purposes relevant to the Internet Standards development 67 process, membership in the IETF and its Working Groups is defined to 68 be established solely and entirely by individual participation in 69 IETF and Working Group activities. Participation in the IETF and its 70 Working Groups is by individual technical contributors rather than by 71 formal representatives of organizations. 73 Anyone with the time and interest to do so is entitled and urged to 74 participate actively in one or more IETF Working Groups and to attend 75 IETF meetings which are held three times a year. In most cases 76 active Working Group participation is possible through electronic 77 mail alone. Internet video conferencing is also being used to allow 78 for remote participation. 80 To ensure a fair and open process, participants in the IETF and its 81 Working Groups must be able to disclose, and must disclose to the 82 Working Group chairs any relevant current or pending intellectual 83 property rights that are reasonably and personally known to the 84 participant if they participate in discussions about a specific 85 technology. 87 New Working Groups are established within the IETF by explicit 88 charter. The guidelines and procedures for the formation and 89 operation of IETF working groups are described in detail in [A]. 91 A Working Group is managed by one or more Working Group chairs (see 92 section 2.9). It may also include editors of documents that record 93 the group's work (see section 2.10). Further details of Working Group 94 operation are contained in [A] 96 IETF Working Groups display a spirit of cooperation as well as a high 97 degree of technical maturity; IETF participants recognize that the 98 greatest benefit for all members of the Internet community results 99 from cooperative development of technically superior protocols and 100 services. 102 2.3 IETF Secretariat 104 The administrative functions necessary to support the activities of 105 the IETF are performed by a Secretariat consisting of the IESG 106 Secretary and his or her staff. The IESG Secretary is the formal 107 point of contact for matters concerning any and all aspects of the 108 Internet standards process, and is responsible for maintaining the 109 formal public record of the Internet standards process [B]. 111 2.4 Internet Society 113 The Internet Society (ISOC) is an international organization 114 concerned with the growth and evolution of the worldwide Internet and 115 with the social, political, and technical issues that arise from its 116 use. The ISOC is an organization with individual and organizational 117 members. The ISOC is managed by a Board of Trustees elected by the 118 worldwide individual membership. 120 Internet standardization is an organized activity of the ISOC, with 121 the Board of Trustees being responsible for ratifying the procedures 122 and rules of the Internet standards process [B]. 124 The way in which the members of the ISOC Board of Trustees are 125 selected, and other matters concerning the operation of the Internet 126 Society, are described in the ISOC By Laws [C]. 128 2.5 Internet Engineering Steering Group 130 The Internet Engineering Steering Group (IESG) is the part of the 131 Internet Society responsible for the management of the IETF technical 132 activities. It administers the Internet Standards process according 133 to the rules and procedures defined in [B]. The IESG is responsible 134 for the actions associated with the progression of technical 135 specification along the "standards track" including the initial 136 approval of new Working Groups and the final approval of 137 specifications as Internet Standards. The IESG is composed of the 138 IETF Area Directors and the chair of the IETF, who also serves as the 139 chair of the IESG. 141 The members of the IESG are nominated by a nominations committee (the 142 Nomcom), and are approved by the IAB. See [E] for a detailed 143 description of the Nomcom procedures. Other matters concerning its 144 organization and operation, are described in the IESG charter [does 145 not yet exist]. 147 2.6 Internet Architecture Board 149 The Internet Architecture Board (IAB) is chartered by the Internet 150 Society Trustees to provide oversight of the architecture of the 151 Internet and its protocols. The IAB appoints the IETF chair and is 152 responsible for approving other IESG candidates put forward by the 153 IETF nominating committee. The IAB is also responsible for reviewing 154 and approving the charters of new Working Groups that are proposed 155 for the IETF. 157 The IAB provides oversight of the process used to create Internet 158 Standards and serves as an appeal board for complaints of improper 159 execution of the standards process [B]. In general it acts as source 160 of advice to the IETF, the ISOC and the ISOC Board of Trustees 161 concerning technical, architectural, procedural, and policy matters 162 pertaining to the Internet and its enabling technologies. 164 The members of the IAB are nominated by a nominations committee (the 165 Nomcom), and are approved by the ISOC board. See [E] for a detailed 166 description of the Nomcom procedures. The membership of the IAB 167 consists of members selected by the Nomcom process and the IETF chair 168 sitting as a ex-officio member. Other matters concerning its 169 organization and operation, are described in the IAB charter [D]. 171 2.7 Internet Assigned Numbers Authority 173 Many protocol specifications include numbers, keywords, and other 174 parameters that must be uniquely assigned. Examples include version 175 numbers, protocol numbers, port numbers, and MIB numbers. The 176 Internet Assigned Numbers Authority (IANA) is responsible for 177 assigning the values of these protocol parameters for the Internet. 178 The IANA publishes tables of all currently assigned numbers and 179 parameters in RFCs entitled "Assigned Numbers" [E]. The IANA 180 functions as the "top of the pyramid" for DNS and Internet Address 181 assignment establishing policies for these functions. 183 The functions of the IANA are performed by one or more individuals or 184 organizations selected in accordance with the procedures defined by 185 the IANA charter [F]. 187 2.8 Request for Comments Editor 189 The RFC publication series [B] is managed by an Editor (which may in 190 practice be one or more individuals) responsible both for the 191 mechanics of RFC publication and for upholding the traditionally high 192 technical and editorial standards of the RFC series. 194 The functions of the RFC Editor are performed by one or more 195 individuals or organizations selected in accordance with the 196 procedures defined by the RFC Editor charter [G]. 198 2.9 Working Group Chair 200 Each IETF Working Group is headed by a chair (or by co-chairs) with 201 the responsibility for directing the group's activities, presiding 202 over the group's meetings, and ensuring that the commitments of the 203 group with respect to its role in the Internet standards process are 204 met. In particular, the WG chair is the formal point of contact 205 between the WG and the IESG, via the Area Director of the area to 206 which the WG is assigned. 208 The details on the selection and responsibilites of an IETF Working 209 Group chair can be found in [A]. 211 2.10 Document Editor Most IETF Working Groups focus their efforts on a 212 document, or set of documents, that capture the results of the 213 group's work. A Working Group generally designates a person or 214 persons to serve as the Editor for a particular document. The 215 Document Editor is responsible for ensuring that the contents of the 216 document accurately reflect the decisions that have been made by the 217 working group. 219 As a general practice, the Working Group Chair and Document Editor 220 positions are filled by different individuals to help ensure that the 221 resulting documents accurately reflect the consensus of the Working 222 Group and that all processes are followed. 224 2.11 Internet Research Task Force The Internet Research Task Force 225 (IRTF) is not directly involved in the Internet standards process. 226 It investigates topics considered to be too uncertain, too advanced, 227 or insufficiently well-understood to be the subject of Internet 228 standardization. When an IRTF activity generates a specification 229 that is sufficiently stable to be considered for Internet 230 standardization, the specification is processed through the IETF 231 using the rules in this document. 233 The IRTF is composed of individual Working Groups, but its structure 234 and mode of operation is much less formal than that of the IETF, due 235 in part to the fact that it does not participate directly in the 236 Internet standards process. The organization and program of work of 237 the IRTF is overseen by the Internet Research Steering Group (IRSG), 238 which consists of the chairs of the IRTF Working Groups. Details of 239 the organization and operation of the IRTF and its Working Groups may 240 be found in [H]. 242 3. Security Considerations 243 Security is not addressed in this memo 245 4. References 247 [A] Huizer,E. and D. Crocker, "IETF Working Group Guidelines and 248 Procedures", 03/24/1994. RFC 1603 250 [B] Bradner, S. (Ed) "The Internet Standards Process -- Revision 3", 251 x/y/96, RFC 1602bis 253 [C] By - Laws for the Internet Society, as amended: 254 gopher://info.isoc.org/00/isoc/basic_docs/bylaws.txt 256 [D] Huitema, C. and the IAB, "Charter of the Internet Architecture 257 Board (IAB)", 3/22/94, RFC1601 259 [E] Galvin, J (Ed.), "IAB and IESG Selection, Confirmation, and 260 Recall Process: Operation of the Nominating and Recall Committees", 261 x/y/96, nomcom RFC 263 [F] IANA Charter 265 [G] RFC Editor Charter 267 [H] IRTF charter 269 5. Author's Addresses: 271 Richard Hovey 272 Digital Equipment Corporation 273 1401 H Street NW 274 Washington DC 20005 276 email: hovey@wnpv01.enet.dec.com 277 phone: +1 202 383 5615 279 Scott Bradner 280 Harvard University 281 1350 Mass Ave. Rm 813 282 Cambridge MA 02138 284 email: sob@harvard.edu 285 phone: +1 617 495 3864 287 Appendix A - contact information 289 IETF - ietf@ietf.org, http://www.ietf.org 290 IESG - iesg@ietf.org 292 IAB - iab@ietf.org 294 Expire in six months