| 1 |
<pre>Network Working Group S. Crocker |
| 2 |
Request for Comments: 1640 TIS |
| 3 |
Category: Informational June 1994 |
| 4 |
|
| 5 |
|
| 6 |
<span class="h1">The Process for Organization of Internet Standards</span> |
| 7 |
<span class="h1">Working Group (POISED)</span> |
| 8 |
|
| 9 |
Status of this Memo |
| 10 |
|
| 11 |
This memo provides information for the Internet community. This memo |
| 12 |
does not specify an Internet standard of any kind. Distribution of |
| 13 |
this memo is unlimited. |
| 14 |
|
| 15 |
Abstract |
| 16 |
|
| 17 |
This report, originally prepared in January 1993 provides a summary |
| 18 |
of the POISED WG, starting from the events leading to the formation |
| 19 |
of the WG to the end of 1992. Necessarily, this synopsis represents |
| 20 |
my own perception, particularly for the "prehistory" period. Quite a |
| 21 |
few people hold strong views about both the overall sequence and |
| 22 |
specific events. My intent here is to convey as neutral a point of |
| 23 |
view as possible. |
| 24 |
|
| 25 |
Background and Formation of POISED Working Group |
| 26 |
|
| 27 |
The POISED WG resulted from two sequences of activity, both |
| 28 |
intimately related to the growth of the Internet. During 1991, there |
| 29 |
was great concern that the IP address space was being depleted and |
| 30 |
that the routing tables were growing too large. Some change in the |
| 31 |
IP addressing and routing mechanisms seemed inevitable, and it became |
| 32 |
urgent to explore and choose what those changes should be. The ROAD |
| 33 |
Working Group was formed to study the issues and recommend changes. |
| 34 |
The ROAD group returned with a specific recommendation for the short |
| 35 |
term, but did not reach a conclusion on a long term plan. |
| 36 |
|
| 37 |
The IESG then formulated a plan of action for further exploration of |
| 38 |
the issues and forwarded these recommendations to the IAB. In June |
| 39 |
1992, after the INET '92 meeting in Kobe, Japan, the IAB met and |
| 40 |
considered the IESG's recommendations. After considering the IESG's |
| 41 |
recommendations, the IAB felt that additional ideas were also |
| 42 |
important, particularly some of the addressing ideas in the CLNP |
| 43 |
protocol. The IAB communicated its concerns, and there was immediate |
| 44 |
controversy along two dimensions. One dimension was technical: What |
| 45 |
is the best course for evolving the IP protocol? How important or |
| 46 |
useful are the ideas in the OSI protocol stack? The other dimension |
| 47 |
was political: Who makes decisions within the Internet community? |
| 48 |
Who chooses who makes these decisions? |
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Crocker [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc1640">RFC 1640</a> POISED WG Report June 1994</span> |
| 55 |
|
| 56 |
|
| 57 |
As often happens during periods of conflict, communication suffered |
| 58 |
among the several parties. The June communication from the IAB was |
| 59 |
understood by many an IAB decision or, equivalently, a sense of the |
| 60 |
decisions the IAB would make in the future. In contrast, many if not |
| 61 |
all on the IAB felt that they were trying to open up the discussion |
| 62 |
and their memos were intended as advice and not decisions. From my |
| 63 |
perspective, this form of miscommunication was partly due to the |
| 64 |
extended size of the Internet technical community. When the |
| 65 |
community was much smaller, the IAB was in close contact with the day |
| 66 |
to day workings of the technical groups. With the creation of the |
| 67 |
IESG and area directorates, there are now two or three layers between |
| 68 |
a working group and the IAB. |
| 69 |
|
| 70 |
These matters came to a head during the IETF meeting in July in |
| 71 |
Cambridge, MA. It was made clear that the consideration of changes |
| 72 |
to the IP protocol remained open. Work on that topic has proceeded |
| 73 |
and is reported in the appropriate forums. However, it became clear |
| 74 |
that it was necessary to examine the decision process and the |
| 75 |
procedures for populating the IESG and IAB. With respect to the |
| 76 |
procedures for selecting IAB and IESG members, the procedures that |
| 77 |
were in place derived from the creation of the Internet Society |
| 78 |
(ISOC) and the ISOC's sponsorship of the IAB. These procedures had |
| 79 |
been developed during the early part of 1992 and had been adopted by |
| 80 |
the ISOC during its meeting in Kobe in June. Hence, as fast as the |
| 81 |
ISOC was building the framework for supporting the Internet |
| 82 |
community, the community was questioning its structure and processes. |
| 83 |
|
| 84 |
Following the IETF meeting, Vint Cerf, Internet Society president, |
| 85 |
called for the formation of working group to examine the processes |
| 86 |
and particularly the selection process (Attachment 1). During |
| 87 |
August, the working group was formed, I was asked to chair it, and a |
| 88 |
charter for the WG was formulated (Attachment 2). (The acronym is |
| 89 |
due to Erik Huizer and originally stood for The Process for |
| 90 |
Organization of Internet Standards and Development. It was shortened |
| 91 |
to fit into the space available on paper and in the IETF |
| 92 |
Secretariat's database.) |
| 93 |
|
| 94 |
Deliberations: August through mid-November |
| 95 |
|
| 96 |
The formation of the POISED WG provided a forum for discussion of |
| 97 |
process issues. An estimated 20 MB of messages filled up disks all |
| 98 |
over the world. Much of this discussion was fragmented or focused on |
| 99 |
narrow issues. The salient point that emerged was the need for a |
| 100 |
well defined process for selecting leaders with explicit community |
| 101 |
representation in the selection process. There was also substantial |
| 102 |
discussion of the role of the IAB -- to what extent should it make |
| 103 |
decisions and to what extent should it provide technical guidance? -- |
| 104 |
and the relationship between the IAB and IESG. |
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Crocker [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc1640">RFC 1640</a> POISED WG Report June 1994</span> |
| 111 |
|
| 112 |
|
| 113 |
After several weeks of discussion, Carl Malamud and I attempted to |
| 114 |
capture the main elements of the discussion by presenting a specific |
| 115 |
proposal for the reorganization of the entire structure. The main |
| 116 |
elements of the proposal were: |
| 117 |
|
| 118 |
o Retention of the WG and area structure now in place within the |
| 119 |
IETF. |
| 120 |
|
| 121 |
o Replacement of the IAB and IESG by two boards, one devoted to |
| 122 |
technical management and one devoted to oversight of the |
| 123 |
process. |
| 124 |
|
| 125 |
o Well defined terms for members of both boards. |
| 126 |
|
| 127 |
o Selection by committees with input from the community. |
| 128 |
|
| 129 |
This proposal was technically radical in the sense that it proposed |
| 130 |
new structures to replace existing structures instead of proposing |
| 131 |
changes within the existing system. The proposal focused all further |
| 132 |
discussion and set the stage for the fall IETF in mid-November in |
| 133 |
Washington D.C. |
| 134 |
|
| 135 |
November IETF meeting |
| 136 |
|
| 137 |
By virtue of the intensity of interest throughout the community, the |
| 138 |
POISED WG was one of the focal points of the IETF meeting. The |
| 139 |
schedule included a plenary session Tuesday morning to present the |
| 140 |
current state of the POISED WG discussions, a formal POISED WG |
| 141 |
session Tuesday afternoon and an open IESG meeting Thursday evening |
| 142 |
devoted to the POISED issues. The formal schedule was only the tip |
| 143 |
of the iceberg; numerous meetings took place over breakfast, lunch |
| 144 |
and dinner, in the halls and off in the corners. The more active |
| 145 |
participants probably had a dozen or more separate meetings on this |
| 146 |
over the three most active days, Tuesday, Wednesday and Thursday. |
| 147 |
|
| 148 |
Amidst all this frenetic activity, remarkable progress occurred at |
| 149 |
two key points. At the Tuesday afternoon POISED WG meeting, Lyman |
| 150 |
Chapin, IAB chair, Phill Gross, IETF chair and IAB member, and other |
| 151 |
IAB members proposed changes within the existing IAB/IESG structure |
| 152 |
which converged with the process management elements of the Malamud- |
| 153 |
Crocker proposal. The key point was that all processing of standards |
| 154 |
actions, including the final decision to advance a specification |
| 155 |
along the standards track, would be made by the IESG. This change in |
| 156 |
the process shortens the decision cycle and brings it a step closer |
| 157 |
to the working group. Convergence on this key point obviated a |
| 158 |
radical proposal and signaled the building of a consensus on how the |
| 159 |
standards process should evolve. Over the next two days attention |
| 160 |
then turned to the selection process. |
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Crocker [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc1640">RFC 1640</a> POISED WG Report June 1994</span> |
| 167 |
|
| 168 |
|
| 169 |
As indicated above, there was a strong feeling in the community that |
| 170 |
the IAB and IESG members should be selected with the consensus of the |
| 171 |
community. A natural mechanism for doing this is through formal |
| 172 |
voting. However, a formal voting process requires formal delineation |
| 173 |
of who's enfranchised. One of the strengths of the IETF is there |
| 174 |
isn't any formal membership requirement, nor is there a tradition of |
| 175 |
decision through votes. Decisions are generally reached by |
| 176 |
consensus with mediation by leaders when necessary. |
| 177 |
|
| 178 |
Various formulas were considered, and the one that emerged was that |
| 179 |
IAB and IESG members would be selected by a nomination and recruiting |
| 180 |
committee. The committee is to consist of seven members from the |
| 181 |
community, with non-voting representatives from the IAB and IESG and |
| 182 |
a non-voting chair provided by the ISOC. The seven members are to be |
| 183 |
volunteers, with selection by lot if there are more than seven |
| 184 |
volunteers. The only requirement for volunteers is they must have |
| 185 |
attended two IETF meetings. This requirement is designed to ensure |
| 186 |
the nomination committee has some familiarity with the Internet |
| 187 |
community and the standards process. |
| 188 |
|
| 189 |
IAB and IESG members are to serve two years. Half of each body is to |
| 190 |
have terms starting in odd years, and half is to have terms starting |
| 191 |
in even years. Selections to the IESG have to be ratified by the |
| 192 |
IAB, and selections to the IAB had to be ratified by the ISOC. In |
| 193 |
the event that the nomination committee is unable to reach a |
| 194 |
consensus on a single candidate for each position, it may forward |
| 195 |
multiple nominations to the ratifying body, and the ratifying body |
| 196 |
will select the candidate. |
| 197 |
|
| 198 |
In addition to this selection process, a recall mechanism was |
| 199 |
outlined using a similar scheme. The ISOC is to supply an ombudsman |
| 200 |
who will field complaints after all oversight processes have been |
| 201 |
exhausted. If the ombudsman is unable to resolve a complaint after a |
| 202 |
cooling off period, a recall committee, selected at random among |
| 203 |
volunteering community members, will consider the matter. A two |
| 204 |
thirds vote by the committee is necessary to remove someone. |
| 205 |
|
| 206 |
This proposal was formulated and circulated during Wednesday and |
| 207 |
Thursday and presented at the IESG open plenary. In contrast to the |
| 208 |
extraordinarily contentious open IESG meeting in Cambridge, this |
| 209 |
meeting was characterized by a strenuous effort by numerous people, |
| 210 |
representing diverse points of view, to reach consensus on this |
| 211 |
proposal, and the meeting ended with a distinct decision to proceed |
| 212 |
on this basis. Given the strong consensus that emerged at that |
| 213 |
meeting, the group decided to implement the selection process by the |
| 214 |
next IETF meeting, with the new IESG and IAB members to begin their |
| 215 |
terms at the termination of the IETF meeting in March. |
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Crocker [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc1640">RFC 1640</a> POISED WG Report June 1994</span> |
| 223 |
|
| 224 |
|
| 225 |
On Friday, the IAB and IESG met jointly to determine what to do next. |
| 226 |
Both groups agreed to implement the change in processing standards |
| 227 |
actions quickly and cooperatively and to identify the positions which |
| 228 |
are open for selection. Within a couple of weeks, the IAB finished |
| 229 |
processing the standards actions in its queue, and IESG began to |
| 230 |
handle standards actions on its own. |
| 231 |
|
| 232 |
December ISOC meeting |
| 233 |
|
| 234 |
The Internet Society Trustees met December 10 and 11 at CNRI in |
| 235 |
Reston, VA. The process and organization of the IAB and IETF was one |
| 236 |
of their major concerns. A session of the Trustees at 3:00 p.m. EST, |
| 237 |
December 10, was broadcast via the Internet. It was not clear how |
| 238 |
many people listened, but Geoff Huston, Internet Trustee, was spliced |
| 239 |
in separately from Australia. |
| 240 |
|
| 241 |
At this session, I presented the POISED WG results deliberations and |
| 242 |
asked on behalf of the IETF that the Trustees approve the selection |
| 243 |
process described above. For the long run, a new charter is needed. |
| 244 |
Given the very compressed schedule for these activities, there has |
| 245 |
not been time to draft and refine a new charter, so the Trustees were |
| 246 |
asked to approve the general direction of the reorganization of the |
| 247 |
IAB and IETF and give temporary approval to the selection process in |
| 248 |
order to permit the first round of selections to proceed. |
| 249 |
|
| 250 |
The Trustees expressed strong approval for the work of the POISED WG |
| 251 |
and general approval for the direction of the effort. One area of |
| 252 |
concern for the Trustees is the legal liability of the Internet |
| 253 |
Society regarding decisions the IESG might make in the future. The |
| 254 |
Trustees made it quite clear that they are not inclined to |
| 255 |
micromanage the IETF process, but they do feel compelled to |
| 256 |
understand the legal issues and help construct a charter which is |
| 257 |
consistent with their responsbilities as Trustees. |
| 258 |
|
| 259 |
The session adjourned with agreement to proceed on the current course |
| 260 |
and for the IETF, IAB and ISOC Trustees to work together to draft the |
| 261 |
appropriate charter. |
| 262 |
|
| 263 |
Future activities |
| 264 |
|
| 265 |
Both the IESG and IAB have selected the positions which must be |
| 266 |
filled through the new selection process. As I write this, Vint Cerf |
| 267 |
has been working to find a chair for the nominations committee, and |
| 268 |
the process should move forward during January and February. |
| 269 |
Communications on the details of the nomination process will be |
| 270 |
published on the IETF mailing list and possibly other forums. As |
| 271 |
described above, the selection process should be complete well before |
| 272 |
the next IETF meeting, and preferably by the end of February. |
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Crocker [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc1640">RFC 1640</a> POISED WG Report June 1994</span> |
| 279 |
|
| 280 |
|
| 281 |
The other open agenda item is the draft of a new charter for the IAB |
| 282 |
and IETF and adoption of the charter by the ISOC. This is the next |
| 283 |
order of business for the POISED WG. |
| 284 |
|
| 285 |
|
| 286 |
|
| 287 |
|
| 288 |
|
| 289 |
|
| 290 |
|
| 291 |
|
| 292 |
|
| 293 |
|
| 294 |
|
| 295 |
|
| 296 |
|
| 297 |
|
| 298 |
|
| 299 |
|
| 300 |
|
| 301 |
|
| 302 |
|
| 303 |
|
| 304 |
|
| 305 |
|
| 306 |
|
| 307 |
|
| 308 |
|
| 309 |
|
| 310 |
|
| 311 |
|
| 312 |
|
| 313 |
|
| 314 |
|
| 315 |
|
| 316 |
|
| 317 |
|
| 318 |
|
| 319 |
|
| 320 |
|
| 321 |
|
| 322 |
|
| 323 |
|
| 324 |
|
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Crocker [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc1640">RFC 1640</a> POISED WG Report June 1994</span> |
| 335 |
|
| 336 |
|
| 337 |
ATTACHMENT 1: Message from Vint Cerf to the IETF, et al. |
| 338 |
|
| 339 |
To: [email protected] |
| 340 |
Cc: [email protected], [email protected], [email protected], |
| 341 |
internet-society-trustees:;@IETF.NRI.Reston.VA.US, |
| 342 |
internet-society-members:;@IETF.NRI.Reston.VA.US, |
| 343 |
[email protected] |
| 344 |
Subject: Request for Recommendations |
| 345 |
Date: Wed, 12 Aug 92 21:46:48 -0400 |
| 346 |
From: [email protected] |
| 347 |
Message-Id: <[email protected]> |
| 348 |
|
| 349 |
|
| 350 |
|
| 351 |
|
| 352 |
To: IETF Chairman |
| 353 |
CC: IAB, IETF, IRTF, ISOC Trustees, and ISOC Members |
| 354 |
From: President, Internet Society |
| 355 |
Subject: Request for Recommendations on IAB/IETF/IRTF/ISOC Procedures |
| 356 |
|
| 357 |
Introduction |
| 358 |
|
| 359 |
In June, 1992, The Internet Society Board of Trustees received a |
| 360 |
proposed charter for an Internet Architecture Board to be created |
| 361 |
within the Internet Society. The new Internet Architecture Board was |
| 362 |
envisioned to be made up of the then current members of the Internet |
| 363 |
Activities Board. The functions of the IETF and the IRTF would be |
| 364 |
brought under the umbrella of the Internet Society as elements of the |
| 365 |
newly chartered Internet Architecture Board. The Trustees voted to |
| 366 |
accept the proposed charter, which is contained in <a href="./rfc1358">RFC 1358</a>. |
| 367 |
|
| 368 |
In the period between June and July, a great deal of discussion |
| 369 |
occurred both by email and at the IETF meeting in Boston about the |
| 370 |
procedures by which the IAB, IETF, and IRTF should work together |
| 371 |
under the general umbrella of the Internet Society. Among the many |
| 372 |
points raised, three seemed particularly important to consider: |
| 373 |
|
| 374 |
1. Procedures for making appointments to the Internet Architecture |
| 375 |
Board. |
| 376 |
|
| 377 |
2. Procedures for resolving disagreements among the IETF, IESG, |
| 378 |
and IAB in matters pertaining to the Internet Standards. |
| 379 |
|
| 380 |
3. Methods for ensuring that for any particular Internet Standard, |
| 381 |
procedures have been followed satisfactorily by all parties |
| 382 |
so that everyone with an interest has had a fair opportunity |
| 383 |
to be heard. |
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Crocker [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc1640">RFC 1640</a> POISED WG Report June 1994</span> |
| 391 |
|
| 392 |
|
| 393 |
Effective discussion of these issues requires the availability of an |
| 394 |
open venue, an opportunity to comment by email, and the possibility |
| 395 |
of conducting face-to-face meetings. Recognizing this, the IAB has |
| 396 |
recommended that the most effective means available to the Internet |
| 397 |
Community for gathering recommendations for refining our existing |
| 398 |
procedures is to request that an IETF Working Group be formed. |
| 399 |
|
| 400 |
I am pleased to make this request of the IETF to create such a WG. |
| 401 |
It would be extremely helpful to have recommendations on the three |
| 402 |
topics listed above by the first of December, 1992, in time to be |
| 403 |
presented at the Internet Society Board of Trustees meeting scheduled |
| 404 |
for December 10th. |
| 405 |
|
| 406 |
With respect to point 1 above, the current procedures for making IAB |
| 407 |
appointments are contained in the IAB charter (<a href="./rfc1358">RFC 1358</a>). <a href="./rfc1310">RFC 1310</a> |
| 408 |
contains a description of the current process by which Internet |
| 409 |
Standards are achieved. Points (2) and (3) could be discussed in the |
| 410 |
context of the present procedures described in <a href="./rfc1310">RFC 1310</a>, which |
| 411 |
recognizes a number of open issues in an appendix. |
| 412 |
|
| 413 |
The Internet Society Trustees hope that members of the IAB, IRTF, |
| 414 |
IESG, and IETF, as well as general members of the Internet Society, |
| 415 |
will take the time to share their thoughts in the proposed working |
| 416 |
group forum. It is vital to the future of the Internet that these key |
| 417 |
groups work together well. Certainly, the Internet Society Trustees |
| 418 |
are committed to doing everything possible to facilitate effective |
| 419 |
procedures and to preserve and enhance the special spirit of the |
| 420 |
Internet Community which has created and maintains the health and |
| 421 |
growth of the global Internet. |
| 422 |
|
| 423 |
Vint Cerf |
| 424 |
President |
| 425 |
Internet Society |
| 426 |
|
| 427 |
|
| 428 |
|
| 429 |
|
| 430 |
|
| 431 |
|
| 432 |
|
| 433 |
|
| 434 |
|
| 435 |
|
| 436 |
|
| 437 |
|
| 438 |
|
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Crocker [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc1640">RFC 1640</a> POISED WG Report June 1994</span> |
| 447 |
|
| 448 |
|
| 449 |
Process for Organization of Internet Standards (poised) |
| 450 |
|
| 451 |
Charter |
| 452 |
|
| 453 |
Chair(s): |
| 454 |
Steve Crocker <[email protected]> |
| 455 |
|
| 456 |
Mailing lists: |
| 457 |
General Discussion:[email protected] |
| 458 |
To Subscribe: [email protected] |
| 459 |
Archive: nri.reston.va.us:~/poised/current |
| 460 |
|
| 461 |
Description of Working Group: |
| 462 |
|
| 463 |
The goal of this working group is to examine the Internet |
| 464 |
standards process and the responsibilities of the IAB, with |
| 465 |
attention to the relationship between the IAB and IETF/IESG. |
| 466 |
|
| 467 |
The need for this working group was suggested during discussions |
| 468 |
at the July 1992 IETF. This led to a request from the Internet |
| 469 |
Society president to form such a working group. |
| 470 |
|
| 471 |
The WG will consider the following matters: |
| 472 |
|
| 473 |
1. Procedures for making appointments to the Internet |
| 474 |
Architecture Board. |
| 475 |
|
| 476 |
2. Procedures for resolving disagreements among IETF, IESG and |
| 477 |
IAB in matters pertaining to the Internet Standards. |
| 478 |
|
| 479 |
3. Methods for assuring that for any particular Internet |
| 480 |
Standard, procedures have been followed satisfactorily by |
| 481 |
all parties so that everyone with an interest has had a |
| 482 |
fair opportunity to be heard. |
| 483 |
|
| 484 |
|
| 485 |
The WG will begin with a review of the procedures for making |
| 486 |
IAB appointments as documented in <a href="./rfc1358">RFC 1358</a> and a review of |
| 487 |
the standards-making process documented in <a href="./rfc1310">RFC 1310</a>. |
| 488 |
|
| 489 |
The WG has a goal of issuing a final report in time for IESG |
| 490 |
consideration and publication as an RFC before the |
| 491 |
ISOC Board of Trustee's meeting in December 1992. Given the |
| 492 |
compressed timescale, the WG will conduct most of its |
| 493 |
deliberations by electronic mail on the POISED WG mailing |
| 494 |
list. There will also be a preliminary report and discussions |
| 495 |
at the November 1992 IETF meeting in Washington, DC. |
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Crocker [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc1640">RFC 1640</a> POISED WG Report June 1994</span> |
| 503 |
|
| 504 |
|
| 505 |
This will be a normal IETF WG, i.e. the mailing list and all |
| 506 |
discussions will be completely open. |
| 507 |
|
| 508 |
Goals and Milestones: |
| 509 |
|
| 510 |
Sep 92 Gather initial set of issues and write a preliminary report. |
| 511 |
|
| 512 |
Oct 92 Post as an Internet Draft the initial recommendations to the |
| 513 |
ISOC Board. |
| 514 |
|
| 515 |
Nov 92 Open discussion and presentation of the work of the POISED |
| 516 |
Working Group at Washington D.C. IETF meeting. |
| 517 |
|
| 518 |
Dec 92 Submit the recommendations document to the IESG for posting |
| 519 |
as an Informational RFC. This document will be subsequently |
| 520 |
transmitted to the ISOC Board. |
| 521 |
|
| 522 |
Security Considerations |
| 523 |
|
| 524 |
Security issues are not discussed in this memo. |
| 525 |
|
| 526 |
Author's Address |
| 527 |
|
| 528 |
Steve Crocker |
| 529 |
Trusted Inforamtion Systems, Inc. |
| 530 |
3060 Washington Road |
| 531 |
Glenwood, MD 21738 |
| 532 |
|
| 533 |
Phone: (301) 854-6889 |
| 534 |
EMail: [email protected] |
| 535 |
|
| 536 |
|
| 537 |
|
| 538 |
|
| 539 |
|
| 540 |
|
| 541 |
|
| 542 |
|
| 543 |
|
| 544 |
|
| 545 |
|
| 546 |
|
| 547 |
|
| 548 |
|
| 549 |
|
| 550 |
|
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
Crocker [Page 10] |
| 557 |
</pre> |