idnits 2.17.1 draft-ietf-newtrk-sample-isd-stdproc-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1.a on line 15. -- Found old boilerplate from RFC 3978, Section 5.5 on line 487. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 498. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 509. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 509. ** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement -- however, there's a paragraph with a matching beginning. Boilerplate error? ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** The document seems to lack an RFC 3978 Section 5.4 Reference to BCP 78 -- however, there's a paragraph with a matching beginning. Boilerplate error? ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. ** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission of drafts without verbatim RFC 3978 boilerplate is not accepted. The following non-3978 patterns matched text found in the document. That text should be removed or replaced: By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. 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. == No 'Intended status' indicated for this document; assuming Proposed Standard == It seems as if not all pages are separated by form feeds - found 0 form feeds but 11 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** 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. ** There are 26 instances of too long lines in the document, the longest one being 1 character in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- 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 (October 2004) is 7133 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: 10 errors (**), 0 flaws (~~), 3 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group S. Bradner 3 Internet-Draft Harvard University 4 October 2004 6 Sample ISD for the IETF Standards Process 8 10 Status of this Memo 12 By submitting this Internet-Draft, each author represents that any 13 applicable patent or other IPR claims of which he or she is aware 14 have been or will be disclosed, and any of which he or she becomes 15 aware will be disclosed, in accordance with Section 6 of RFC 3668. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html 33 Abstract 34 This is a sample Internet Standards Documentation (ISD) for the IETF 35 Standards Process. This document follows the model proposed in 36 draft-ietf-newtrk-isd-repurposing-isd-00. 38 Copyright Notice 39 Copyright (C) The Internet Society. (2004) 41 1. Introduction 43 This is a sample Internet Standards Documentation (ISD) for the IETF 44 Standards Process. This document follows the model proposed in 45 draft-ietf-newtrk-isd-repurposing-isd-00. This sample is written as 46 if the ISD process started being used in 1993 so to show a possible 47 history feature. 49 2. ISD for the Internet standards Process 51 IETF Internet Standards Documentation 53 Name of ISD: ISD xxxx: The IETF Internet Standards Process 54 Last update: 17-Oct-2004 55 Maintainer: IESG 57 A: Abstract 58 This ISD documents the process currently used by the Internet 59 community for the standardization of protocols and procedures. The 60 Internet Standards process is an activity of the Internet Society 61 that is organized and managed on behalf of the Internet community by 62 the Internet Architecture Board (IAB) and the Internet Engineering 63 Steering Group (IESG). 65 B: Documents making up the Standard 66 RFC 2026 67 The Internet Standards Process -- Revision 3, S. Bradner (Ed.), 68 October 1996. (Status: BCP) 69 The Internet Standards Process described in this document is 70 concerned with all protocols, procedures, and conventions that are 71 used in or by the Internet, whether or not they are part of the 72 TCP/IP protocol suite. In the case of protocols developed and/or 73 standardized by non-Internet organizations, however, the Internet 74 Standards Process normally applies to the application of the 75 protocol or procedure in the Internet context, not to the 76 specification of the protocol itself. 77 The goals of the Internet Standards Process are: 79 o technical excellence; 80 o prior implementation and testing; 81 o clear, concise, and easily understood documentation; 82 o openness and fairness; and 83 o timeliness. 85 The procedures described in this document are designed to be fair, 86 open, and objective; to reflect existing (proven) practice; and 87 to be flexible. 89 The community needs this document because it spells out the way we 90 develop standards, the steps along the way, and the ways 91 disagreements and intellectual property rights are handled. [note 92 in draft - text from 9 Jul 96 Protocol Action announcement] 94 After 2026 had been used in the IETF for a number of years it 95 became clear that the intellectual property rights (IPR) section 96 (Section 10) was confusing because it mixed up patent rights, 97 copyrights and trademarks without making the different rules for 98 the different types of rights clear. In addition the 99 understanding of what constituted a contribution to the IETF 100 evolved. Because of this two new RFCs were developed (RFC 3667 101 and RFC 3668) to clarify the IPR issues. 103 RFC 3667 104 IETF Rights in Contributions, S. Bradner (Ed.), February 2004. 105 (Status: BCP) 106 This document (with RFC 3668) replaces section 10 of RFC 2026, and 107 provides a much more detailed description of the considerations 108 regarding intellectual property that need to be taken into account 109 when working in the IETF. 110 Particular attention is paid to copyright issues and issues 111 concerning requirements for implementation, such as patent 112 licensing. [note in draft - text adopted from 03 Nov 2003 Protocol 113 Action announcement] 115 RFC 3668 116 Intellectual Property Rights in IETF Technology, S. Bradner (Ed.), 117 February 2004. (Status: BCP) 118 This document (with RFC 3667) replaces section 10 of RFC 2026, and 119 provides a much more detailed description of the considerations 120 regarding intellectual property that need to be taken into account 121 when working in the IETF. 122 Particular attention is paid to copyright issues and issues 123 concerning requirements for implementation, such as patent 124 licensing. [note in draft - text adopted from 03 Nov 2003 Protocol 125 Action announcement] 127 C: Additional Relevant Documents 128 RFC 3668 129 Guidelines for Working Groups on Intellectual Property Issues, S. 130 Brim, February 2004. (Status: Informational) 131 The "Guidelines" document relates useful experience gathered when 132 working with IPR issues in the IETF. [note in draft - text from 03 133 Nov 2003 Protocol Action announcement] 135 D: Extensions to the Standard 136 RFC 3932 137 The IESG and RFC Editor Documents: Procedures, H. Alvestrand, 138 October 2004. (Status: BCP) 139 This document describes the IESG's procedures for handling 140 documents submitted for RFC publication via the RFC Editor, 141 subsequent to the changes proposed by the IESG at the Seoul IETF, 142 March 2004. [note in draft - text from 27 Jul 2004 Protocol Action 143 announcement] 145 E: Related ISDs 146 ISD XXXX IETF Working Group Processes 147 This ISD describes the IETF working group processes. 149 ISD XXXX IETF Mailing List Processes 150 This ISD describes the basic rules for IETF mailing lists. 152 F: Experimental Extensions 153 Internet Draft draft-klensin-process-july14 154 A model for IETF Process Experiments, J. Klensin, S. Dawkins 155 (Status: approved by the IESG) 156 This document proposes a way to change IETF processes that 157 provides notice to the community (via Last Call), a permanent 158 record (via RFCs) and a reasonable expectation that the process 159 changes will be evaluated for whether they worked or not, and 160 rolled back if they did not work. [note in draft - text from the 161 26 Jul 2004 Protocol Action announcement] 163 G: Obsolete Documents 164 RFC 1871 165 Addendum to RFC 1602 -- Variance Procedure, J. Postel. November 166 1995. 167 This RFC described a modification to the IETF procedures to allow 168 an escape from a situation where the existing procedures are not 169 working or do not seem to apply. This is a modification to the 170 procedures of RFC 1602 and 1603. This RFC was created to deal 171 with, among other things, an IPR deadlock concerning the PPP 172 compression control protocol. (See RFC 1915.) 174 RFC 1602 175 The Internet Standards Process -- Revision 2, Internet 176 Architecture Board, Internet Engineering Steering Group. March 177 1994 178 This RFC updated the description of the IETF Internet Standards 179 Process to more clearly define the IETF's intellectual property 180 related rules. 182 RFC 1310 183 The Internet Standards Process. L. Chapin. March 1992. 184 This RFC was the first description of the IETF Internet Standards 185 Process published in a stand alone RFC. It is now obsolete. 187 RFC 1200 188 IAB OFFICIAL PROTOCOL STANDARDS, Internet Activities Board, J. 189 Postel, Editor, April 1991 190 This document includes a description of the stages of the IETF 191 Internet Standards Process. It is now obsolete. 193 RFC 1140 194 IAB OFFICIAL PROTOCOL STANDARDS, Internet Activities Board, J. 195 Postel, Editor, May 1990 196 This document includes a description of the stages of the IETF 197 Internet Standards Process. It is now obsolete. 199 RFC 1100 200 IAB OFFICIAL PROTOCOL STANDARDS, Internet Activities Board, April 201 1989 202 This document includes a description of the stages of the IETF 203 Internet Standards Process. It is now obsolete. 205 RFC 1083 IAB OFFICIAL PROTOCOL STANDARDS, Internet Activities Board, 206 December 1988 207 This document includes a description of the stages of the IETF 208 Internet Standards Process. It is now obsolete. 210 =================================================================== 211 H: Historical Record 213 IETF Internet Standards Documentation 215 Name of ISD: ISD xxxx: The IETF Internet Standards Process 216 Last update: Oct-1996 217 Maintainer: IESG 219 A: Abstract 220 This ISD documents the process currently used by the Internet 221 community for the standardization of protocols and procedures. The 222 Internet Standards process is an activity of the Internet Society 223 that is organized and managed on behalf of the Internet community by 224 the Internet Architecture Board (IAB) and the Internet Engineering 225 Steering Group (IESG). 227 B: Documents making up the Standard 228 RFC 2026 229 The Internet Standards Process -- Revision 3, S. Bradner (Ed.), 230 October 1996. (Status: BCP) 231 The Internet Standards Process -- Revision 3, S. Bradner (Ed.), 232 October 1996. (Status: BCP) 233 The Internet Standards Process described in this document is 234 concerned with all protocols, procedures, and conventions that are 235 used in or by the Internet, whether or not they are part of the 236 TCP/IP protocol suite. In the case of protocols developed and/or 237 standardized by non-Internet organizations, however, the Internet 238 Standards Process normally applies to the application of the 239 protocol or procedure in the Internet context, not to the 240 specification of the protocol itself. 242 The goals of the Internet Standards Process are: 244 o technical excellence; 245 o prior implementation and testing; 246 o clear, concise, and easily understood documentation; 247 o openness and fairness; and 248 o timeliness. 250 The procedures described in this document are designed to be fair, 251 open, and objective; to reflect existing (proven) practice; and 252 to be flexible. 254 The community needs this document because it spells out the way we 255 develop standards, the steps along the way, and the ways 256 disagreements and intellectual property rights are handled. [note 257 in draft - text from 9 Jul 96 Protocol Action announcement] 259 C: Additional Relevant Documents 260 none 262 D: Extensions to the Standard 263 none 265 E: Related ISDs 266 none 268 F: Experimental Extensions 269 none 271 G: Obsolete Documents 272 RFC 1871 273 Addendum to RFC 1602 -- Variance Procedure, J. Postel. November 274 1995. 275 This RFC described a modification to the IETF procedures to allow 276 an escape from a situation where the existing procedures are not 277 working or do not seem to apply. This is a modification to the 278 procedures of RFC 1602 and 1603. This RFC was created to deal 279 with, among other things, an IPR deadlock concerning the PPP 280 compression control protocol. (See RFC 1915.) [note in draft - I 281 could not find the Protocol Action announcement for this document] 283 RFC 1602 284 The Internet Standards Process -- Revision 2, Internet 285 Architecture Board, Internet Engineering Steering Group. March 286 1994 287 This RFC updated the description of the IETF Internet Standards 288 Process to more clearly define the IETF's intellectual property 289 related rules. 291 RFC 1310 292 The Internet Standards Process. L. Chapin. March 1992. 293 This RFC was the first description of the IETF Internet Standards 294 Process published in a stand alone RFC. It is now obsolete. 296 RFC 1200 297 IAB OFFICIAL PROTOCOL STANDARDS, Internet Activities Board, J. 298 Postel, Editor, April 1991 299 This document includes a description of the stages of the IETF 300 Internet Standards Process. It is now obsolete. 302 RFC 1140 303 IAB OFFICIAL PROTOCOL STANDARDS, Internet Activities Board, J. 304 Postel, Editor, May 1990 305 This document includes a description of the stages of the IETF 306 Internet Standards Process. It is now obsolete. 308 RFC 1100 309 IAB OFFICIAL PROTOCOL STANDARDS, Internet Activities Board, April 310 1989 311 This document includes a description of the stages of the IETF 312 Internet Standards Process. It is now obsolete. 314 RFC 1083 IAB OFFICIAL PROTOCOL STANDARDS, Internet Activities Board, 315 December 1988 316 This document includes a description of the stages of the IETF 317 Internet Standards Process. It is now obsolete. 319 =================================================================== 320 H: Historical Record 322 IETF Internet Standards Documentation 324 Name of ISD: ISD xxxx: The IETF Internet Standards Process 325 Last update: Nov 1995 326 Maintainer: IESG 328 A: Abstract 329 This ISD documents the process currently used by the Internet 330 community for the standardization of protocols and procedures. The 331 Internet Standards process is an activity of the Internet Society 332 that is organized and managed on behalf of the Internet community by 333 the Internet Architecture Board (IAB) and the Internet Engineering 334 Steering Group (IESG). 336 B: Documents making up the Standard 337 RFC 1602 338 The Internet Standards Process -- Revision 2, Internet 339 Architecture Board, Internet Engineering Steering Group. March 340 1994 341 This describes the IETF Internet Standards Process. 343 C: Additional Relevant Documents 344 none 346 D: Extensions to the Standard 347 RFC 1871 348 Addendum to RFC 1602 -- Variance Procedure, J. Postel. November 349 1995. 350 This RFC describes a modification to the IETF procedures to allow 351 an escape from a situation where the existing procedures are not 352 working or do not seem to apply. This is a modification to the 353 procedures of RFC 1602 and 1603. This RFC was created to deal 354 with, among other things, an IPR deadlock concerning the PPP 355 compression control protocol. (See RFC 1915.) 357 E: Related ISDs 358 none 360 F: Experimental Extensions 361 none 363 G: Obsolete Documents 364 RFC 1310 365 The Internet Standards Process. L. Chapin. March 1992. 366 This RFC was the first description of the IETF Internet Standards 367 Process published in a stand alone RFC. It is now obsolete. 369 RFC 1200 370 IAB OFFICIAL PROTOCOL STANDARDS, Internet Activities Board, J. 371 Postel, Editor, April 1991 372 This document includes a description of the stages of the IETF 373 Internet Standards Process. It is now obsolete. 375 RFC 1140 376 IAB OFFICIAL PROTOCOL STANDARDS, Internet Activities Board, J. 377 Postel, Editor, May 1990 378 This document includes a description of the stages of the IETF 379 Internet Standards Process. It is now obsolete. 381 RFC 1100 382 IAB OFFICIAL PROTOCOL STANDARDS, Internet Activities Board, April 383 1989 384 This document includes a description of the stages of the IETF 385 Internet Standards Process. It is now obsolete. 387 RFC 1083 IAB OFFICIAL PROTOCOL STANDARDS, Internet Activities Board, 388 December 1988 389 This document includes a description of the stages of the IETF 390 Internet Standards Process. It is now obsolete. 392 =================================================================== 393 H: Historical Record 395 IETF Internet Standards Documentation 397 Name of ISD: ISD xxxx: The IETF Internet Standards Process 398 Last update: March 1994 399 Maintainer: IESG 401 A: Abstract 402 This ISD documents the process currently used by the Internet 403 community for the standardization of protocols and procedures. The 404 Internet Standards process is an activity of the Internet Society 405 that is organized and managed on behalf of the Internet community by 406 the Internet Architecture Board (IAB) and the Internet Engineering 407 Steering Group (IESG). 409 B: Documents making up the Standard 410 RFC 1602 411 The Internet Standards Process -- Revision 2, Internet 412 Architecture Board, Internet Engineering Steering Group. March 413 1994 414 This describes the IETF Internet Standards Process. 416 C: Additional Relevant Documents 417 none 419 D: Extensions to the Standard 420 none 422 E: Related ISDs 423 none 425 F: Experimental Extensions 426 none 428 G: Obsolete Documents 429 RFC 1310 430 The Internet Standards Process. L. Chapin. March 1992. 431 This RFC was the first description of the IETF Internet Standards 432 Process published in a stand alone RFC. It is now obsolete. 434 RFC 1200 435 IAB OFFICIAL PROTOCOL STANDARDS, Internet Activities Board, J. 436 Postel, Editor, April 1991 437 This document includes a description of the stages of the IETF 438 Internet Standards Process. It is now obsolete. 440 RFC 1140 441 IAB OFFICIAL PROTOCOL STANDARDS, Internet Activities Board, J. 442 Postel, Editor, May 1990 443 This document includes a description of the stages of the IETF 444 Internet Standards Process. It is now obsolete. 446 RFC 1100 447 IAB OFFICIAL PROTOCOL STANDARDS, Internet Activities Board, April 448 1989 449 This document includes a description of the stages of the IETF 450 Internet Standards Process. It is now obsolete. 452 RFC 1083 IAB OFFICIAL PROTOCOL STANDARDS, Internet Activities Board, 453 December 1988 454 This document includes a description of the stages of the IETF 455 Internet Standards Process. It is now obsolete. 457 9. Security Considerations 459 ISDs would not have a security considerations section 461 10. References 462 ISDs would not have a references section since the whole document is 463 a references section 465 12. Editor's Address 467 Scott Bradner 468 Harvard University 469 29 Oxford St. 470 Cambridge MA, 02138 472 Phone: +1 617 495 3864 473 EMail: sob@harvard.edu 475 13. Full copyright statement 477 Copyright (C) The Internet Society (2004). This document is subject 478 to the rights, licenses and restrictions contained in BCP 78 and 479 except as set forth therein, the authors retain all their rights. 481 This document and the information contained herein are provided on an 482 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 483 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 484 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 485 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 486 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 487 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 489 Intellectual Property 491 The IETF takes no position regarding the validity or scope of any 492 Intellectual Property Rights or other rights that might be claimed to 493 pertain to the implementation or use of the technology described in 494 this document or the extent to which any license under such rights 495 might or might not be available; nor does it represent that it has 496 made any independent effort to identify any such rights. Information 497 on the procedures with respect to rights in RFC documents can be 498 found in BCP 78 and BCP 79. 500 Copies of IPR disclosures made to the IETF Secretariat and any 501 assurances of licenses to be made available, or the result of an 502 attempt made to obtain a general license or permission for the use of 503 such proprietary rights by implementers or users of this 504 specification can be obtained from the IETF on-line IPR repository at 505 http://www.ietf.org/ipr. The IETF invites any interested party to 506 bring to its attention any copyrights, patents or patent 507 applications, or other proprietary rights that may cover technology 508 that may be required to implement this standard. Please address the 509 information to the IETF at ietf-ipr@ietf.org. 511 Acknowledgement 513 Funding for the RFC Editor function is currently provided by the 514 Internet Society.