Debian Codegraph @

rfc6292.html

raw
1 <pre>Internet Engineering Task Force (IETF) P. Hoffman
2 Request for Comments: 6292 VPN Consortium
3 Category: Informational June 2011
4 ISSN: 2070-1721
5
6
7 <span class="h1">Requirements for a Working Group Charter Tool</span>
8
9 Abstract
10
11 The IETF intends to provide a new tool to Area Directors for the
12 creation, re-chartering, and closing of Working Groups. The tool
13 will also allow the IETF community to view the status of the
14 chartering process. This document describes the requirements for the
15 proposed new tool, and it is intended as input to a later activity
16 for the design and development of such a tool.
17
18 Status of This Memo
19
20 This document is not an Internet Standards Track specification; it is
21 published for informational purposes.
22
23 This document is a product of the Internet Engineering Task Force
24 (IETF). It represents the consensus of the IETF community. It has
25 received public review and has been approved for publication by the
26 Internet Engineering Steering Group (IESG). Not all documents
27 approved by the IESG are a candidate for any level of Internet
28 Standard; see <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.
29
30 Information about the current status of this document, any errata,
31 and how to provide feedback on it may be obtained at
32 <a href="http://www.rfc-editor.org/info/rfc6292">http://www.rfc-editor.org/info/rfc6292</a>.
33
34 Copyright Notice
35
36 Copyright (c) 2011 IETF Trust and the persons identified as the
37 document authors. All rights reserved.
38
39 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
40 Provisions Relating to IETF Documents
41 (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
42 publication of this document. Please review these documents
43 carefully, as they describe your rights and restrictions with respect
44 to this document. Code Components extracted from this document must
45 include Simplified BSD License text as described in Section 4.e of
46 the Trust Legal Provisions and are provided without warranty as
47 described in the Simplified BSD License.
48
49
50
51
52 <span class="grey">Hoffman Informational [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc6292">RFC 6292</a> WG Charter Tool Reqs June 2011</span>
55
56
57 Table of Contents
58
59 <a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
60 <a href="#section-1.1">1.1</a>. WG Charter Process Overview . . . . . . . . . . . . . . . <a href="#page-3">3</a>
61 <a href="#section-2">2</a>. General Requirements . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
62 <a href="#section-2.1">2.1</a>. WG Records . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
63 <a href="#section-2.2">2.2</a>. Comments . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
64 <a href="#section-2.3">2.3</a>. Naming of Charter Text Proposals . . . . . . . . . . . . . <a href="#page-5">5</a>
65 <a href="#section-2.4">2.4</a>. Wording of Announcements . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
66 <a href="#section-2.5">2.5</a>. Access to the Tool . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
67 <a href="#section-2.6">2.6</a>. Initializing the Tool . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
68 <a href="#section-3">3</a>. Creating and Rechartering WGs . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
69 <a href="#section-3.1">3.1</a>. Chartering a New WG . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
70 <a href="#section-3.2">3.2</a>. Rechartering an Existing WG . . . . . . . . . . . . . . . <a href="#page-8">8</a>
71 <a href="#section-3.3">3.3</a>. Ballots for Charter Approval . . . . . . . . . . . . . . . <a href="#page-9">9</a>
72 <a href="#section-4">4</a>. Requesting the Closing of a WG . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
73 <a href="#section-5">5</a>. Searching, Comparing, and Tracking Charters . . . . . . . . . <a href="#page-9">9</a>
74 <a href="#section-5.1">5.1</a>. Viewing and Searching the Charter Database . . . . . . . . <a href="#page-9">9</a>
75 5.2. Seeing Differences between Versions of Pre-Approval
76 Wordings . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
77 <a href="#section-5.3">5.3</a>. Tracking Charters with an Atom Feed . . . . . . . . . . . <a href="#page-10">10</a>
78 <a href="#section-6">6</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
79 <a href="#section-7">7</a>. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
80 <a href="#section-8">8</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
81 <a href="#section-8.1">8.1</a>. Normative References . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
82 <a href="#section-8.2">8.2</a>. Informative References . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108 <span class="grey">Hoffman Informational [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc6292">RFC 6292</a> WG Charter Tool Reqs June 2011</span>
111
112
113 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
114
115 [<a id="ref-RFC2418">RFC2418</a>] describes the guidelines and procedures for formation and
116 operation of IETF Working Groups (WGs). Since the publication of <a href="./rfc2418">RFC</a>
117 <a href="./rfc2418">2418</a> in 1998, the IETF has started many dozen new WGs, and has shut
118 down many dozen. In that time, many WGs have had some (often dozens)
119 changes to their charters.
120
121 Today, virtually all of the tasks associated with creating,
122 rechartering, and closing a WG are performed manually. An Area
123 Director (AD) requests one of these actions by manually sending a
124 message to the Secretariat's ticket system. A member of the
125 Secretariat staff manually updates the internal Secretariat database
126 and the IETF Datatracker, manually places the WG on the IESG
127 teleconference agenda (when appropriate), and manually sends out all
128 of the required messages and announcements.
129
130 The IETF Administrative Oversight Committee (IAOC) would like to
131 create a better tool for those tasks, and this document lists the
132 requirements for such a tool. When complete, this document may be
133 used to issue an RFP for the design and development of the tool.
134 This document was prepared at the request of the IAOC.
135
136 <span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. WG Charter Process Overview</span>
137
138 As described in [<a href="./rfc2418" title="&quot;IETF Working Group Guidelines and Procedures&quot;">RFC2418</a>], a key responsibility of the IESG is the
139 creation, re-chartering, and closing of WGs. Creation and
140 rechartering of WGs is a multi-step process that involves internal
141 review of a draft charter by the IESG and IAB, an external review of
142 the draft charter by the IETF community and by other standards
143 bodies, and (likely) approval of a final charter by the IESG. The
144 internal review by the IESG and IAB, and the external review by the
145 IETF community, often result in revisions to the draft charter.
146
147 Closing of a WG does not require review or approval by the IESG.
148 Rather, a WG may be closed at the request of an AD, normally the Area
149 Advisor for the WG.
150
151 Note that the charter and recharter processes do not involve changing
152 of WG milestones. A tool that handles milestone updates will likely
153 be created in the future.
154
155 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. General Requirements</span>
156
157 The tool described here holds records for new WGs that are being
158 considered as well as for all WGs whose charter are under review.
159
160
161
162
163
164 <span class="grey">Hoffman Informational [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc6292">RFC 6292</a> WG Charter Tool Reqs June 2011</span>
167
168
169 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. WG Records</span>
170
171 A WG record contains the following fields:
172
173 o name of the WG
174
175 o the WG's acronym
176
177 o names of the WG chairs (if known)
178
179 o names of the WG secretary (if any)
180
181 o names of the WG technical advisors (if any)
182
183 o shepherding AD
184
185 o IETF area
186
187 o charter text
188
189 o mailing list address and archive location
190
191 o previous mailing list (if any)
192
193 o other web sites (such as wikis, trackers, and/or project sites, if
194 any) including web sites existing prior to the WG formation
195
196 o earlier acronyms for the WG
197
198 o explanation for why the WG is being chartered or rechartered (if
199 any)
200
201 In addition, a WG record contains the state of the WG in the review
202 process. That state has one annotation: whether or not the state is
203 for a proposed WG or for an existing WG undergoing rechartering.
204 Some changes in state cause messages to be sent to the Secretariat so
205 that the Secretariat can perform additional steps, such as sending
206 out mail to various parties about the latest version of the charter
207 text, deadlines for an upcoming decision, and so on.
208
209 When a WG record is displayed, that display should also reflect
210 whether the WG currently exists or has been closed; that data comes
211 from a different part of the Datatracker database.
212
213 Any AD can modify fields in an existing WG record. Any AD can use
214 the tool to change the review state of a WG record. The normal order
215 for steps is shown in this document, but an AD can set the state to
216 any valid value at any time.
217
218
219
220 <span class="grey">Hoffman Informational [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc6292">RFC 6292</a> WG Charter Tool Reqs June 2011</span>
223
224
225 <span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Comments</span>
226
227 During the reviews for WG creation and rechartering, ADs can comment
228 on the reviews. Any AD can add a comment to the record of a WG that
229 is under review. Each comment can be flagged as either "blocking"
230 (meaning blocking forward movement until it is resolved) and "non-
231 blocking" (meaning that it is only informative or editorial).
232
233 <span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Naming of Charter Text Proposals</span>
234
235 Charter text proposals are to be kept for historical purposes. They
236 are kept in files with a specific naming pattern. The pattern for
237 charters before a WG is formed is:
238
239 charter-ietf-wgacronym-nn[-mm]
240
241 o "wgacronym" is the acronym of the proposed WG.
242
243 o "nn" is a two-digit charter number assigned in sequence. It
244 starts at "00" for before the WG is first chartered; the first
245 finished charter has a value of "01".
246
247 o "mm" is a two-digit proposal number assigned in sequence. It
248 starts at "00" for the first proposal for a particular version of
249 charter. It is omitted in the actual charter file.
250
251 For instance, if the "example" WG is chartered and then rechartered
252 twice, you might have the following sequence of files:
253
254 charter-ietf-example-00-00.txt (first proposal)
255 charter-ietf-example-00-01.txt (second proposal)
256 charter-ietf-example-00-02.txt (third proposal)
257 charter-ietf-example-01.txt (first charter)
258 charter-ietf-example-01-00.txt (first recharter proposal)
259 charter-ietf-example-01-01.txt (second recharter proposal)
260 charter-ietf-example-01-02.txt (third recharter proposal)
261 charter-ietf-example-02.txt (second charter)
262 charter-ietf-example-02-00.txt (next recharter proposal)
263 . . .
264 charter-ietf-example-03.txt (third charter)
265
266 <span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. Wording of Announcements</span>
267
268 An AD can view and edit the standard "WG Review" and "WG Action"
269 announcements before they are sent out during the WG creation,
270 rechartering, and closing processes. If the AD edits the message,
271 the Secretariat is alerted to that fact when they receive the
272 request.
273
274
275
276 <span class="grey">Hoffman Informational [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc6292">RFC 6292</a> WG Charter Tool Reqs June 2011</span>
279
280
281 <span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a>. Access to the Tool</span>
282
283 Area Directors and the IETF Secretariat currently have access to
284 perform some actions in the Datatracker that other community members
285 do not; this access control continues to be used in many of the
286 extensions listed in this document. Further, the IETF Secretariat
287 can perform all actions that can be performed by any AD in this tool.
288
289 <span class="h3"><a class="selflink" id="section-2.6" href="#section-2.6">2.6</a>. Initializing the Tool</span>
290
291 Records for all WGs that are being created, or are in the process of
292 charter updates, will be added before the tool is first publicly
293 deployed.
294
295 The database should also be initialized with current and historical
296 data, namely as much information as is currently known about existing
297 and closed WGs that can be done in a mostly-automated fashion.
298
299 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Creating and Rechartering WGs</span>
300
301 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Chartering a New WG</span>
302
303 Any AD can create a new WG record using a simple web form. Creating
304 a record should succeed as long as there is no other WG with the same
305 name. Names must be unique, so the tool will warn the AD if the
306 acronym that is being proposed has been used in earlier WG charter
307 proposals and suggest against its use for a new charter. By default,
308 the field in the form listing the shepherding AD will be prepopulated
309 with the name of the AD who is filling in the form. The AD can fill
310 in all the fields for the proposed WG. The names of the WG chairs
311 can be left off during the initial chartering process.
312
313 (Some Secretariat tools have trouble with acronyms of more than eight
314 characters: they truncate the name. This will probably be fixed in
315 the future. The new tool should have a configuration setting that is
316 set to 8 initially, and it should be adjusted when the Secretariat
317 tools are updated. There may also be problems with names that have
318 hyphens in them. However, WGs that have more than eight characters
319 in their names, and WGs with hyphens in their names, have existed for
320 over a year.)
321
322 Creating a new WG record causes the Datatracker state for this
323 potential new WG to be "Informal IESG review". When the record is
324 created, the AD proposes a length of time (in weeks) for the internal
325 review time; the default is one week.
326
327 The review states in which a WG can exist during its initial
328 chartering are:
329
330
331
332 <span class="grey">Hoffman Informational [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc6292">RFC 6292</a> WG Charter Tool Reqs June 2011</span>
335
336
337 o Informal IESG review -- This is the initial state, moved into by
338 the tool when an AD creates a WG record. When the WG record is
339 moved to this state, a message is sent to the Secretariat. The
340 normal next state is "Internal review" if the idea is accepted, or
341 "Not currently under review" if the idea is abandoned. The tool
342 should prompt the AD if they try to move to the next state in less
343 than the minimum elapsed time set by the AD when creating the WG,
344 but allow the move if the AD responds to the prompt.
345
346 o Internal review -- The IESG and IAB are reviewing the early draft
347 of the charter; this is the initial IESG and IAB review. When
348 moved to this state, a note is sent to the Secretariat to place
349 this on the next IESG telechat and to inform the IAB. The usual
350 next state is "External review" if the idea is adopted, or
351 "Informal IESG review" if the IESG decides the idea needs more
352 work, or "Not currently under review" if the idea is abandoned.
353
354 o External review -- The IETF community and possibly other standards
355 development organizations (SDOs) are reviewing the proposed
356 charter. When moved to this state, a note is sent to the
357 Secretariat to send out the external review announcement to the
358 appropriate lists. The external review announcement will be sent
359 out to the normal IETF-related mailing lists. The AD can specify
360 whether or not to send the announcement to other SDOs (with the
361 default being that it should be), and the AD can also specify
362 additional recipients who should receive the announcement. When
363 moved to this state, a separate note is sent to the Secretariat to
364 schedule discussion for the next IESG telechat. The usual next
365 state is "IESG review", although it might move to "Not currently
366 under review" if the idea is abandoned during the external review.
367
368 o IESG review -- The IESG is reviewing the discussion from the
369 external review of the proposed charter. The usual next state is
370 "WG exists", or "Not currently under review" if the idea is
371 abandoned.
372
373 o WG exists -- The WG was approved by the IESG. When moved to this
374 state, a note is sent to the Secretariat to publish the charter
375 and send the appropriate announcements. The WG remains in this
376 state until there is a request to update the charter.
377
378 o Not currently under review -- The proposed WG is not being
379 considered at this time. A proposed WG charter will remain in
380 this state until an AD moves it to "Informa1 IESG review".
381
382 All states above, except for "WG exists", are given the annotation
383 "Initial chartering".
384
385
386
387
388 <span class="grey">Hoffman Informational [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc6292">RFC 6292</a> WG Charter Tool Reqs June 2011</span>
391
392
393 The chartering process involves the proposed charter appearing on two
394 IESG telechats. The tool should allow an AD and/or the Secretariat
395 to select the telechat date for the approval events. When the
396 telechat is selected, the state determines where it appears on that
397 telechat's agenda.
398
399 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Rechartering an Existing WG</span>
400
401 Any AD can request that a WG be rechartered using a simple web form.
402 This form prompts with the current charter and allows all fields to
403 be edited. Asking for a recharter causes the Datatracker state for
404 this WG to be "Informal IESG review". When the recharter record is
405 created, the AD proposes a length of time (in weeks) for the internal
406 review time; the default is one week.
407
408 The review states in which a WG can exist during rechartering are:
409
410 o WG exists; Informal IESG recharter review -- This is the initial
411 state, moved into by the tool when an AD asks for a WG to be
412 rechartered. When the WG record is moved to this state, a message
413 is sent to the Secretariat. The normal next state is "WG exists;
414 Internal review" if the idea is accepted, or "WG exists" if this
415 attempt to recharter is abandoned. The tool should prompt the AD
416 if they try to move to the next state in less than the minimum
417 elapsed time set by the AD when asking to recharter the WG.
418
419 o WG exists; Internal recharter review -- The IESG and IAB are
420 reviewing the proposed new charter; this is the initial IESG and
421 IAB review of the new charter. When moved to this state, a note
422 is sent to the Secretariat to place this on the next IESG telechat
423 and to inform the IAB. The usual next state is "WG exists;
424 External review" if the idea is adopted, or "WG exists; Informal
425 IESG review" if the IESG decides the idea needs more work, or "WG
426 exists" if the current rechartering is abandoned or if the new
427 charter is approved during internal review.
428
429 o WG exists; External recharter review -- The IETF community and
430 possibly other SDOs are reviewing the proposed new charter. When
431 moved to this state, a note is sent to the Secretariat to send out
432 the external review announcement to the appropriate lists. The
433 external review announcement will be sent to the normal IETF-
434 related mailing lists. The AD can specify whether or not to send
435 the announcement to other SDOs (with the default being that it
436 should be), and the AD can also specify additional recipients who
437 should receive the announcement. The usual next state is "WG
438 exists; IESG review", although it might move to "WG exists" if the
439 current rechartering is abandoned during the external review.
440
441
442
443
444 <span class="grey">Hoffman Informational [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc6292">RFC 6292</a> WG Charter Tool Reqs June 2011</span>
447
448
449 o WG exists; IESG recharter review -- The IESG is reviewing the
450 discussion from the external review of the recharter. When moved
451 to this state, a note is sent to the Secretariat to schedule
452 discussion for the next IESG telechat. The usual next state is
453 "WG exists".
454
455 All states above are given the annotation "Rechartering".
456
457 When rechartering existing WGs, the IESG decides whether or not the
458 recharter needs an external review; many do not.
459
460 The rechartering process involves the proposed charter appearing on
461 one or two IESG telechats. The tool should allow an AD and/or the
462 Secretariat to select the telechat date for the approval events.
463 When the telechat is selected, the state determines where it appears
464 on that telechat's agenda.
465
466 <span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Ballots for Charter Approval</span>
467
468 The current Datatracker has facilities for ballots on adoption of
469 Internet-Drafts to become RFCs. A separate facility needs to be
470 created to allow balloting for initial chartering or rechartering
471 during IESG review. The balloting for charter and rechartering will
472 allow ADs to express "yes", "no", and "abstain" positions, and will
473 allow ADs to change their positions over time.
474
475 As described in <a href="#section-2.2">Section 2.2</a>, comments can be added to the record for
476 a WG. It is expected that such comments will be added during the
477 balloting process.
478
479 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Requesting the Closing of a WG</span>
480
481 An AD can use the tool to request that the Secretariat close an
482 existing WG. The request action will prompt the AD to provide
483 instructions regarding the disposition of each active Internet-Draft
484 (such as to withdraw the draft, move it to another WG, convert it to
485 an individual submission, and so on), wording for the closure
486 announcement, and the status of the WG mailing list (will it remain
487 open or should it be closed).
488
489 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Searching, Comparing, and Tracking Charters</span>
490
491 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Viewing and Searching the Charter Database</span>
492
493 All members of the IETF community can view the public portions of the
494 charter database. This public view should have an explanation of the
495 states given in this document. They can also search for a WG record
496 in the tool based on one or more of the following criteria:
497
498
499
500 <span class="grey">Hoffman Informational [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc6292">RFC 6292</a> WG Charter Tool Reqs June 2011</span>
503
504
505 o WG name (full or partial)
506
507 o WG acronym
508
509 o WG charter state
510
511 o Shepherding AD
512
513 o Area
514
515 o Text in any of the fields
516
517 o Earlier acronyms for the WG
518
519 Further, all users can view all snapshots of earlier versions of a
520 WG's charter. Snapshots include the Area, AD, WG name, WG acronym,
521 chairs, and charter text.
522
523 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Seeing Differences between Versions of Pre-Approval Wordings</span>
524
525 It needs to be easy to compare differences between different versions
526 of proposed charter language, up to and including the approved
527 version. Using the naming formats given in <a href="#section-2">Section 2</a>, this means
528 that it must be easy to compare wgacronym-charter-ss (for the highest
529 value of "ss") with wgacronym-recharter-ss-nn. It must also be
530 possible to compare any two versions of approved charters (that is,
531 of two values for "ss" in wgacronym-charter-ss). It also must be
532 easy to compare two versions that have different acronyms in the case
533 that the acronym changes during the chartering process.
534
535 <span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. Tracking Charters with an Atom Feed</span>
536
537 The tool needs to provide an Atom feed [<a href="./rfc4287" title="&quot;The Atom Syndication Format&quot;">RFC4287</a>] for the changes in a
538 charter. The contents of the feed are the full WG record, plus an
539 indication of what changed since the last entry in the feed.
540
541 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
542
543 Creating a new tool for tracking the charter of WGs does not affect
544 the security of the Internet in any significant fashion.
545
546 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Acknowledgements</span>
547
548 This document draws heavily on earlier work done on this topic by
549 other writers, such as previous IESG and IAB members. Various
550 members of the IESG contributed many suggestions to this document.
551 In particular David Harrington, Robert Sparks, and Russ Housley
552 contributed a great deal of wording and many ideas.
553
554
555
556 <span class="grey">Hoffman Informational [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc6292">RFC 6292</a> WG Charter Tool Reqs June 2011</span>
559
560
561 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span>
562
563 <span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span>
564
565 [<a id="ref-RFC2418">RFC2418</a>] Bradner, S., "IETF Working Group Guidelines and
566 Procedures", <a href="https://www.rfc-editor.org/bcp/bcp25">BCP 25</a>, <a href="./rfc2418">RFC 2418</a>, September 1998.
567
568 <span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span>
569
570 [<a id="ref-RFC4287">RFC4287</a>] Nottingham, M., Ed. and R. Sayre, Ed., "The Atom
571 Syndication Format", <a href="./rfc4287">RFC 4287</a>, December 2005.
572
573 Author's Address
574
575 Paul Hoffman
576 VPN Consortium
577
578 EMail: [email protected]
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612 Hoffman Informational [Page 11]
613 </pre>