idnits 2.17.1 draft-hoffman-tao-as-web-page-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- -- The draft header indicates that this document obsoletes RFC4677, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 19, 2012) is 4296 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Obsolete informational reference (is this intentional?): RFC 4677 (Obsoleted by RFC 6722) Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group P. Hoffman, Ed. 3 Internet-Draft VPN Consortium 4 Obsoletes: 4677 (if approved) July 19, 2012 5 Intended status: Informational 6 Expires: January 20, 2013 8 Publishing the "Tao of the IETF" as a Web Page 9 draft-hoffman-tao-as-web-page-04 11 Abstract 13 This document describes how the "Tao of the IETF", which was 14 published as a series of RFCs in the past, is instead being published 15 as a web page. It also contains the procedure for publishing and 16 editing that web page. 18 Status of this Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on January 20, 2013. 35 Copyright Notice 37 Copyright (c) 2012 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 1. Introduction 52 The "Tao of the IETF" ("Tao") describes the inner workings of IETF 53 meetings and Working Groups, discusses organizations related to the 54 IETF, and introduces the standards process. It is not a formal IETF 55 process document but instead an informational overview. The Tao has 56 traditionally been published as an RFC. It has been RFCs 1391, 1539, 57 1718, 3160; it is currently [RFC4677]. 59 At the time this document is published, there is a strong desire in 60 the IETF community to turn the Tao into a web page that can be edited 61 more easily than an RFC. This document describes how that happens. 62 At the same time, this document formally obsoletes the last version 63 of the Tao that was published as an RFC because that last version, 64 RFC 4677, is no longer be considered the "latest" version of the Tao: 65 the new web page is. 67 This document contains the procedure agreed to by the IESG. The Tao 68 has traditionally been an IETF consensus document, which means that 69 the IESG has had the final say about what the Tao contained before it 70 was sent to the RFC Editor. Thus, the IESG should have final say for 71 what the Tao says when it is a web page. 73 2. Procedure for Publishing and Editing the Tao 75 The Tao is published at and 76 . The initial content for the Tao web 77 page is based on the last Internet-Draft that was meant to replace 78 RFC 4677. 80 The Tao is edited by one or more people as designated by the IESG. 81 Suggestions for changes to the Tao are discussed on the 82 tao-discuss@ietf.org mailing list. 84 The editor of the Tao decides which proposed changes should be 85 submitted to the IESG for approval. The editor publishes the 86 proposed changes in a version at 87 . The IESG may 88 accept as many of the proposed changes as it wishes. The IESG then 89 submits the changed version to the IETF Secretariat for publication 90 on the IETF web page at the URLs given above. The Tao editor and the 91 IESG should confirm that the page that actually appears on the web 92 site is as intended. 94 Each version of the Tao has a visible timestamp near the beginning of 95 the document. All published versions are archived using URLs of the 96 form , and a list 97 of the revisions is available at . 99 From time to time, translations of versions of the Tao are made into 100 other languages. These translations do not represent IETF consensus 101 and may be provided on an "as is" basis. The issues of how 102 translations are recorded, made available, cross-referenced to 103 versions of the Tao, and archived are outside the scope of this 104 document and for future study. 106 3. Proposals for How The Tao Web Page Should Be Developed 108 During the discussion that led to this document, there were many 109 proposals for how the Tao as a web page should be published and 110 edited. Some wanted just a web page; some wanted a web page and 111 periodic snapshots as RFCs; some wanted a wiki that could be easily 112 edited by anyone in the IETF community, with a master editor who 113 would revert bad edits; some wanted a wiki with a more limited group 114 of contributors. The procedure in Section 2 above was the rough 115 consensus of the discussion. 117 4. IANA Considerations 119 None. 121 5. Security Considerations 123 The Tao is available over TLS at . 125 6. Informative References 127 [RFC4677] Hoffman, P. and S. Harris, "The Tao of IETF - A Novice's 128 Guide to the Internet Engineering Task Force", RFC 4677, 129 September 2006. 131 Author's Address 133 Paul Hoffman (editor) 134 VPN Consortium 136 Email: paul.hoffman@vpnc.org