idnits 2.17.1 draft-ietf-mtgvenue-iaoc-venue-selection-process-06.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (April 18, 2017) is 2566 days in the past. Is this intentional? Checking references for intended status: Best Current Practice ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'I-D.barnes-healthy-food' is defined on line 740, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'MeetingNet' ** Obsolete normative reference: RFC 4071 (Obsoleted by RFC 8711) ** Obsolete normative reference: RFC 4371 (Obsoleted by RFC 8714) ** Obsolete normative reference: RFC 7691 (Obsoleted by RFC 8711) Summary: 3 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 mtgvenue R. Pelletier 3 Internet-Draft Internet Society 4 Intended status: Best Current Practice L. Nugent 5 Expires: October 20, 2017 Association Management Solutions 6 D. Crocker, Ed. 7 Brandenburg InternetWorking 8 L. Berger 9 LabN Consulting, L.L.C. 10 O. Jacobsen 11 The Internet Protocol Journal 12 J. Martin 13 INOC 14 F. Baker, Ed. 16 E. Lear, Ed. 17 Cisco Systems GmbH 18 April 18, 2017 20 IETF Plenary Meeting Venue Selection Process 21 draft-ietf-mtgvenue-iaoc-venue-selection-process-06 23 Abstract 25 The IAOC has responsibility for arranging IETF plenary meeting Venue 26 selection and operation. This document details the IETF's Meeting 27 Venue Selection Process from the perspective of its goals, criteria 28 and thought processes. It points to additional process documents on 29 the IAOC Web Site that go into further detail and are subject to 30 change with experience. 32 Status of This Memo 34 This Internet-Draft is submitted in full conformance with the 35 provisions of BCP 78 and BCP 79. 37 Internet-Drafts are working documents of the Internet Engineering 38 Task Force (IETF). Note that other groups may also distribute 39 working documents as Internet-Drafts. The list of current Internet- 40 Drafts is at http://datatracker.ietf.org/drafts/current/. 42 Internet-Drafts are draft documents valid for a maximum of six months 43 and may be updated, replaced, or obsoleted by other documents at any 44 time. It is inappropriate to use Internet-Drafts as reference 45 material or to cite them other than as "work in progress." 47 This Internet-Draft will expire on October 20, 2017. 49 Copyright Notice 51 Copyright (c) 2017 IETF Trust and the persons identified as the 52 document authors. All rights reserved. 54 This document is subject to BCP 78 and the IETF Trust's Legal 55 Provisions Relating to IETF Documents 56 (http://trustee.ietf.org/license-info) in effect on the date of 57 publication of this document. Please review these documents 58 carefully, as they describe your rights and restrictions with respect 59 to this document. Code Components extracted from this document must 60 include Simplified BSD License text as described in Section 4.e of 61 the Trust Legal Provisions and are provided without warranty as 62 described in the Simplified BSD License. 64 Table of Contents 66 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 67 1.1. Background . . . . . . . . . . . . . . . . . . . . . . . 3 68 1.2. Requirements Language . . . . . . . . . . . . . . . . . . 3 69 2. Venue Selection Objectives . . . . . . . . . . . . . . . . . 4 70 2.1. Core Values . . . . . . . . . . . . . . . . . . . . . . . 4 71 2.2. Venue Selection Non-Objectives . . . . . . . . . . . . . 6 72 3. Venue Selection Criteria . . . . . . . . . . . . . . . . . . 6 73 3.1. Venue City Criteria . . . . . . . . . . . . . . . . . . . 7 74 3.2. Basic Venue Criteria . . . . . . . . . . . . . . . . . . 8 75 3.3. Technical Services and Operations Criteria . . . . . . . 9 76 3.4. Lodging Criteria . . . . . . . . . . . . . . . . . . . . 10 77 3.5. Food and Beverage Criteria . . . . . . . . . . . . . . . 11 78 4. Venue Selection Roles . . . . . . . . . . . . . . . . . . . . 12 79 4.1. IETF Participants . . . . . . . . . . . . . . . . . . . . 12 80 4.2. IESG and IETF Chair . . . . . . . . . . . . . . . . . . . 13 81 4.3. The Internet Society . . . . . . . . . . . . . . . . . . 13 82 4.4. IETF Administrative Oversight Committee . . . . . . . . . 13 83 4.5. IETF Administrative Support Activity . . . . . . . . . . 13 84 4.6. IETF Administrative Director . . . . . . . . . . . . . . 14 85 4.7. IAOC Meeting Committee . . . . . . . . . . . . . . . . . 14 86 5. Venue Selection Steps . . . . . . . . . . . . . . . . . . . . 14 87 5.1. Identification . . . . . . . . . . . . . . . . . . . . . 14 88 5.2. Consultation . . . . . . . . . . . . . . . . . . . . . . 15 89 5.3. Qualification . . . . . . . . . . . . . . . . . . . . . . 15 90 5.4. Negotiation . . . . . . . . . . . . . . . . . . . . . . . 16 91 5.5. Late Changes . . . . . . . . . . . . . . . . . . . . . . 16 92 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 93 7. Security Considerations . . . . . . . . . . . . . . . . . . . 16 94 8. Privacy Considerations . . . . . . . . . . . . . . . . . . . 17 95 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17 96 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 97 10.1. Normative References . . . . . . . . . . . . . . . . . . 17 98 10.2. Informative References . . . . . . . . . . . . . . . . . 17 99 Appendix A. Site Qualification Visit Checklist . . . . . . . . . 18 100 Appendix B. Contingency Planning Flow Chart . . . . . . . . . . 24 101 Appendix C. Change Log . . . . . . . . . . . . . . . . . . . . . 25 102 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27 104 1. Introduction 106 The IAOC has responsibility for arranging IETF plenary meeting venue 107 selection and operation. The purpose of this document is to guide 108 the IAOC in their selection of regions, cities, and facilities, and 109 hotels. The IAOC applies this guidance at different points in the 110 process in an attempt to faithfully meet the requirements of the IETF 111 community. We specify a set of general criteria for venue selection 112 and several requirements for transparency and community consultation. 114 1.1. Background 116 Following IETF 94 and at IETF 95 there was a discussion on the IETF 117 list of the selection process and criteria for IETF meetings. In 118 response to that discussion, the IAOC and the IAOC Meetings Committee 119 took it upon themselves to more publicly document its process and 120 refine it, based on input from IETF Participants. 122 1.2. Requirements Language 124 Requirements called out in this document are identified by the degree 125 of requirement. The labels that are used are: 127 Mandatory: 128 If this requirement cannot be met, a particular location is 129 unacceptable for selection, and no contract is to be entered into. 130 Should the IAOC learn that a location no longer can meet a 131 mandatory requirement after having entered into a contract, it 132 will inform the community and address the matter on a case by case 133 basis. 135 Important: 136 Does not qualify as Mandatory, but is still highly significant. 137 It can be traded against other Important items, such that a Venue 138 that meets more of these criteria is on the whole more preferable 139 than another that meets less of these criteria. Requirements 140 classed as Important can also be balanced across Venue selections 141 for multiple meetings. 143 Desired: 145 We would very much like to meet this requirement, but the failure 146 to meet it will not disqualify a Venue. 148 While this document uses these terms and these meanings, it remains 149 the responsibility of the IAOC to apply their best judgment. The 150 IAOC accepts input and feedback both during the consultation process 151 and later (for instance when there are changes in the situation at a 152 chosen location). Any appeals remain subject to the provisions of 153 BCP101 [RFC4071]. As always, the community is encouraged to provide 154 direct feedback to the NOMCOM, IESG, and IAB regarding the discharge 155 of the IAOC's performance. 157 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 158 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 159 document are to be interpreted as described in [RFC2119]. 161 2. Venue Selection Objectives 163 2.1. Core Values 165 Some IETF values pervade the selection process. These often are 166 applicable to multiple requirements listed in this document. They 167 are not limited to the following, but at minimum include: 169 Why do we meet? 170 We meet to pursue the IETF's mission [RFC3935], partly by 171 advancing the development of Internet-Drafts and RFCs. We also 172 seek to facilitate attendee participation in multiple topics and 173 to enable cross-pollination of ideas and technologies. 175 Inclusiveness: 176 We would like to facilitate the onsite or remote participation of 177 anyone who wants to be involved. 179 Every country has limits on who it will permit within its borders. 180 However the IETF seeks to: 182 1. Minimize situations in which onerous entry regulations prevent 183 participants from attending meetings, or failing that to 184 distribute meeting locations such that onerous entry 185 regulations are not always experienced by the same attendees 187 2. Avoid meeting in countries with laws that effectively exclude 188 people on the basis of race, religion, gender, sexual 189 orientation, national origin, or gender identity 191 Where do we meet? 192 We meet in different locations globally, in order to spread the 193 difficulty and cost of travel among active participants, balancing 194 travel time and expense across the regions in which IETF 195 participants are based. 197 Internet Access: 198 As an organization, we write specifications for the Internet, and 199 we use it heavily. Meeting attendees need unfiltered access to 200 the general Internet and our corporate networks. "Unfiltered 201 access" in this case means that all forms of communication are 202 allowed. This includes, but is not limited to, access to 203 corporate networks via encrypted VPNs from the meeting Facility 204 and Hotels, including overflow hotels. We also need open network 205 access available at high enough data rates, at the meeting 206 Facility, to support our work, including the support of remote 207 participation. Beyond this, we are the first users of our own 208 technology. Any filtering may cause a problem with that 209 technologiy's development.[MeetingNet] 211 Focus: 212 We meet to have focused technical discussions. These are not 213 limited to scheduled breakout sessions, although of course those 214 are important. They also happen over meals or drinks -- including 215 a specific type of non-session that we call a "Bar BOF" -- or in 216 side meetings. Environments that are noisy or distracting prevent 217 that or reduce its effectiveness, and are therefore less desirable 218 as a meeting Facility. 220 Economics: 221 Meeting attendees participate as individuals. While many are 222 underwritten by employers or sponsors, many are self-funded. In 223 order to reduce participation costs and travel effort, we 224 therefore seek locations that provide convenient budget 225 alternatives for food and lodging, and which minimize travel 226 segments from major airports to the Venue. Within reason, budget 227 should not be a barrier to accommodation. 229 Least Astonishment and Openness: 230 Regular participants should not be surprised by meeting Venue 231 selections, particularly when it comes to locales. To avoid 232 surprise, the venue selection process, as with all other IETF 233 processes, should be as open as practicable. It should be 234 possible for the community to engage early to express its views on 235 prospective selections, so that the community, IAOC, and IAD can 236 exchange views as to appropriateness long before a venue contract 237 is considered. 239 2.2. Venue Selection Non-Objectives 241 IETF meeting Venues are not selected or declined with the explicit 242 purposes of: 244 Politics: 245 Endorsing or condemning particular countries, political paradigms, 246 laws, regulations, or policies. 248 Maximal attendance: 249 While the IETF strives to be as inclusive as possible both online 250 and in person, maximal meeting attendance in and of itself is not 251 a goal. It would defeat a key goal of meeting if active 252 contributors with differing points of view did not have the 253 opportunity to resolve their disagreements, no matter how full the 254 rooms. 256 Tourism: 257 Variety in site-seeing experiences. 259 3. Venue Selection Criteria 261 A number of criteria are considered during the site selection 262 process. The following list is not in any particular order, but 263 includes the major considerations. 265 The selection of a Venue always requires trade-offs. There are no 266 perfect venues. For example, a site might not have a single hotel 267 that can accommodate a significant number of the attendees of a 268 typical IETF. That doesn't disqualify it, but it might reduce its 269 desirability in the presence of an alternative that does provide that 270 single hotel. 272 Some evaluation criteria are subjective. For this reason, the IAOC 273 and Meetings Committee will specifically review, and affirm to their 274 satisfaction, that all "Mandatory" labeled criteria are satisfied by 275 a particular Venue, as part of the process defined below in 276 Section 5. 278 Three terms describe the places for which the IETF contracts 279 services: 281 Venue: 282 This is an umbrella term for the city, meeting resources and guest 283 room resources. 285 Facility: 287 The building that houses meeting rooms and associated resources. 288 It may also house an IETF Hotel or the Headquarters Hotel. 290 IETF Hotels: 291 One or more hotels, in close proximity to the Facility, where the 292 IETF guest room allocations are negotiated and IETF SSIDs are in 293 use. 295 Headquarters Hotel: 296 The hotel designated as primary for the IETF meeting. It include 297 IETF SSIDs for networking, might be adjoining -- or even contain 298 -- the meeting Facility -- and typically has the bulk of the hotel 299 room allocations. 301 3.1. Venue City Criteria 303 These concern basic aspects of a candidate city: 305 +------------------------------------------------------+------------+ 306 | Criteria | Required | 307 +------------------------------------------------------+------------+ 308 | Consultation with the IETF Community has not | "Mandatory | 309 | produced concerns sufficient to disqualify the | " | 310 | Venue. | | 311 +------------------------------------------------------+------------+ 312 | Travel to the Venue is acceptable based on cost, | "Important | 313 | time, and burden for participants traveling from | " | 314 | multiple regions. It is anticipated that the burden | | 315 | borne will be generally shared over the course of | | 316 | multiple years. | | 317 +------------------------------------------------------+------------+ 318 | The Venue is assessed as favorable for obtaining a | "Important | 319 | host and sponsors. That is, the Meeting is in a | " | 320 | location and at a price that it is possible and | | 321 | probable to find a host and sponsors. | | 322 +------------------------------------------------------+------------+ 323 | It is possible to enter into a multi-event contract | "Desired" | 324 | with the Facility and IETF Hotels to optimize | | 325 | meeting and attendee benefits, i.e., reduce | | 326 | administrative costs and reduce direct attendee | | 327 | costs, will be considered a positive factor. Such a | | 328 | contract can be considered after at least one IETF | | 329 | meeting has been held at the Facility. | | 330 +------------------------------------------------------+------------+ 331 | Travel barriers to entry, including visa | "Important | 332 | requirements, are unlikely to impede attendance by | " | 333 | an overwhelming majority of participants. | | 334 +------------------------------------------------------+------------+ 335 | Economic, safety, and health risks associated with | "Important | 336 | this Venue are acceptable. | " | 337 +------------------------------------------------------+------------+ 338 | Available travel issue assessments -- such as -- have been pointed out the IETF community. | | 341 | [[Editor's Note: The implication here is that a note | | 342 | has been sent to the IETF that includes travel | | 343 | assessments before a contract has been entered into. | | 344 | How is this intended to be operationalized? /d]] | | 345 +------------------------------------------------------+------------+ 347 3.2. Basic Venue Criteria 349 The IETF operates internationally and adjusts to local requirements. 350 Facilities selected for IETF Meetings conform with local health, 351 safety and accessibility laws and regulations. A useful discussion 352 of related considerations in evaluating this criterion is at: 354 357 *** Editor's Note *** 358 In the spirit of the 'international' focus, we need a 359 comprehensive document that is similar to the one cited, but 360 without a national focus. The current reference is US- 361 specific. /d 363 In addition: 365 +-----------------------------------------------------+-------------+ 366 | Criteria | Required | 367 +-----------------------------------------------------+-------------+ 368 | The Facility is assessed to be able to provide | "Mandatory" | 369 | sufficient space in an appropriate layout to | | 370 | accommodate the expected number of people to attend | | 371 | that meeting. | | 372 +-----------------------------------------------------+-------------+ 373 | There are sufficient places (e.g., a mix of | "Important" | 374 | hallways, bars, meeting rooms, and restaurants) for | | 375 | people to hold ad hoc conversations and group | | 376 | discussions. | | 377 +-----------------------------------------------------+-------------+ 378 | The cost of guest rooms, meeting space, meeting | "Important" | 379 | food and beverage is affordable, within the norms | | 380 | of business travel. | | 381 +-----------------------------------------------------+-------------+ 382 | The economics of the Venue are in line with | "Removed" | 383 | expectations agreed between ISOC and the IAOC. | | 384 +-----------------------------------------------------+-------------+ 385 | The Facility permits holding an IETF meeting under | "Desired" | 386 | "One Roof". That is, qualified meeting space and | | 387 | guest rooms are available in the same facility. | | 388 +-----------------------------------------------------+-------------+ 389 | The Facility permits easy wheelchair access. | "Mandatory" | 390 +-----------------------------------------------------+-------------+ 391 | The Facility is accessible by people with | "Important" | 392 | disabilities. | | 393 +-----------------------------------------------------+-------------+ 395 3.3. Technical Services and Operations Criteria 396 +-----------------------------------------------------+-------------+ 397 | Criteria | Required | 398 +-----------------------------------------------------+-------------+ 399 | The Facility's support technologies and services -- | "Important" | 400 | network, audio-video, etc. -- are sufficient for | | 401 | the anticipated activities at the meeting, or the | | 402 | Facility is willing to add such infrastructure or | | 403 | these support technologies and services might be | | 404 | provided by a third party, all at no -- or at an | | 405 | acceptable -- cost to the IETF. | | 406 +-----------------------------------------------------+-------------+ 407 | The Facility directly provides, or permits and | "Important" | 408 | facilitates, the delivery of a high performance, | | 409 | robust, unfiltered and unmodified IETF Network. | | 410 +-----------------------------------------------------+-------------+ 411 | The IETF Hotel(s) directly provide, or else permit | "Important" | 412 | and facilitate, the delivery of a high performance, | | 413 | robust, unfiltered and unmodified Internet service | | 414 | for the public areas and guest rooms; this service | | 415 | is typically included in the cost of the room. | | 416 +-----------------------------------------------------+-------------+ 417 | The overflow hotels provide reasonable, reliable, | "Desired" | 418 | unfiltered Internet service for the public areas | | 419 | and guest rooms; this service is included in the | | 420 | cost of the room. | | 421 +-----------------------------------------------------+-------------+ 423 3.4. Lodging Criteria 424 +-----------------------------------------------------+-------------+ 425 | Criteria | Required | 426 +-----------------------------------------------------+-------------+ 427 | The IETF Hotel(s) are within close proximity to | "Important" | 428 | each other and the Facility. | | 429 +-----------------------------------------------------+-------------+ 430 | The guest rooms at the IETF Hotel(s) are sufficient | "Important" | 431 | in number to house 1/3 or more of projected meeting | | 432 | attendees. | | 433 +-----------------------------------------------------+-------------+ 434 | Overflow Hotels can be placed under contract, | "Important" | 435 | within convenient travel time of the Facility and | | 436 | at a variety of guest room rates. | | 437 +-----------------------------------------------------+-------------+ 438 | The Venue environs include budget hotels within | "Important" | 439 | convenient travel time, cost, and effort. | | 440 +-----------------------------------------------------+-------------+ 441 | The IETF Hotel(s) permit easy wheelchair access. | "Mandatory" | 442 +-----------------------------------------------------+-------------+ 443 | The IETF Hotel(s) are accessible by people with | "Important" | 444 | disabilities. | | 445 +-----------------------------------------------------+-------------+ 446 | The IETF Headquarters Hotel has a space for use as | "Important" | 447 | a lounge, conducive to planned and accidental | | 448 | meetings and chatting, as well as working online. | | 449 | There are tables with seating, convenient for small | | 450 | meetings with laptops. The can be at an open bar or | | 451 | casual restaurant. Preferably the lounge area is on | | 452 | the path between the meeting rooms and the hotel | | 453 | entrance, and is available all day and night. | | 454 +-----------------------------------------------------+-------------+ 456 3.5. Food and Beverage Criteria 457 +-----------------------------------------------------+-------------+ 458 | Criteria | Required | 459 +-----------------------------------------------------+-------------+ 460 | The Venue environs, which includes both onsite, as | "Important" | 461 | well as areas within a reasonable walking distance | | 462 | or conveniently accessible by a short taxi, bus, or | | 463 | subway ride, have convenient and inexpensive | | 464 | choices for meals that can accommodate a wide range | | 465 | of dietary requirements. | | 466 +-----------------------------------------------------+-------------+ 467 | The Venue environs include grocery shopping that | "Important" | 468 | will accommodate a wide range of dietary | | 469 | requirements, within a reasonable walking distance, | | 470 | or conveniently accessible by a short taxi, bus, or | | 471 | subway ride, from the Facility and IETF Hotels. | | 472 +-----------------------------------------------------+-------------+ 473 | A range of attendee's health-related and religion- | "Important" | 474 | related dietary requirements can be satisfied with | | 475 | robust and flexible onsite service or through | | 476 | access to an adequate grocery. | | 477 +-----------------------------------------------------+-------------+ 479 4. Venue Selection Roles 481 The formal structure of IETF administrative support functions is 482 documented in BCP 101 [RFC4071], [RFC4371], [RFC7691]. The reader is 483 expected to be familiar with the entities and roles defined by that 484 document, in particular for the IASA, ISOC, IAOC and IAD. This 485 section covers the meeting selection related roles of these and other 486 parties that participate in the process. Note that roles beyond 487 meeting selection, e.g., actually running and reporting on meetings, 488 are outside the scope of this document. 490 4.1. IETF Participants 492 While perhaps obvious, it is important to note that IETF meetings 493 serve all those who contribute to the work of the IETF. This 494 includes those who attend meetings in person, from newcomer to 495 frequent attendee, to those who participate remotely, as well as 496 those who do not attend but contribute to new RFCs. Potential new 497 contributors are also considered in the process. 499 Participants have a responsibility to express their views about 500 venues early and often, by responding to surveys or other 501 solicitations from the IAD or IAOC, and by initiating fresh input as 502 the Participant becomes aware of changes in venues that have been 503 reviews. This permits those responsible for venue selection to be 504 made aware of concerns relating to particular locations well in 505 advance of having entered into contract discussions. 507 4.2. IESG and IETF Chair 509 The Internet Engineering Steering Group (IESG) comprises the IETF 510 Area Directors and the IETF Chair. Along with the IAB, the IESG is 511 responsible for the management of the IETF, and is the standards 512 approval board for the IETF, as described in BCP9 [RFC2026]. This 513 means that the IESG sets high level policies related to, among other 514 things, meeting venues. The IETF Chair, among other things, relays 515 these IESG-determined policies to the IAOC. The IETF Chair is also a 516 member of the IAOC. 518 4.3. The Internet Society 520 With respect to IETF meetings, the Internet Society (ISOC): 522 o Executes all Venue contracts on behalf of the IETF at the request 523 of the IAOC 525 o Solicits meeting sponsorships 527 o Collects all meeting-related revenues, including registration 528 fees, sponsorships, hotel commissions, and other miscellaneous 529 revenues 531 ISOC also provides accounting services, such as invoicing and monthly 532 financial statements. 534 4.4. IETF Administrative Oversight Committee 536 The IETF Administrative Oversight Committee (IAOC) has the 537 responsibility to oversee and select IETF meeting venues. It 538 instructs the IAD to work with the Internet Society to write the 539 relevant contracts. It approves the IETF meetings calendar. In 540 cooperation with the IAD, the IAOC takes necessary actions to ensure 541 that it is aware of participant concerns about particular venues as 542 early in the process as is feasible. 544 4.5. IETF Administrative Support Activity 546 The IETF Administrative Support Activity (IASA) supports the meeting 547 selection process. This includes identifying, qualifying and 548 reporting on potential meeting sites, as well as supporting meeting 549 Venue contract negotiation. The IETF Secretariat is part of the IASA 550 under the management of the IAD. The IAD takes appropriate actions 551 to solicit community input regarding both retrospective and 552 prospective feedback from participants. 554 4.6. IETF Administrative Director 556 The IETF Administrative Director (IAD) coordinates and supports the 557 activities of the IETF Secretariat, the IAOC Meetings Committee and 558 the IAOC to ensure the timely execution of the meeting process. This 559 includes participating in the IAOC Meeting Subcommittee and ensuring 560 its efforts are documented, leading Venue contract negotiation, and 561 coordinating contract execution with ISOC. The meetings budget is 562 managed by the IAD. 564 4.7. IAOC Meeting Committee 566 The fundamental purpose of the Meetings Committee is to participate 567 in the Venue selection process, and to formulate recommendations to 568 the IAOC regarding meeting sites. It also tracks the meetings 569 sponsorship program, recommends extraordinary meeting-related 570 expenses, and recommends the IETF meetings calendar to the IAOC. The 571 charter of the committee is at: . 574 Membership in the Meetings Committee is at the discretion of the 575 IAOC; it includes an IAOC appointed chair, the IETF Administrative 576 Director (IAD), IAOC members, representatives from the Secretariat, 577 and interested members of the community. 579 5. Venue Selection Steps 581 The following sequence is used by the IAOC to select venues. Unless 582 otherwise stated below, the IAOC may evolve these steps over time 583 without updating this document.[[ED- this chapeau text is not agreed. 584 On-list discussion continues.]] 586 5.1. Identification 588 Four years out, a process identifies cities that might be candidates 589 for meetings. For example: 591 a. The IAOC selects regions, cities, and dates for meetings. 593 b. A list of target cities per region is provided to the 594 Secretariat, with host preferences, if known. 596 c. Potential venues in preferred cities are identified and receive 597 preliminary investigation, including reviews of Official Advisory 598 Sources, consultation with specialty travel services, frequent 599 travelers and local contacts to identify possible barriers to 600 holding a successful meeting in the target cities. 602 d. Investigated cities and findings are provided by the Secretariat 603 to the Meetings Committee for further review. Meetings Committee 604 makes a recommendation to the IAOC of investigated/target cities 605 to consider further as well as issues identified and the results 606 of research conducted. 608 5.2. Consultation 610 The IAOC MUST consult the community about potential new venues prior 611 to them being booked. The timing and means by which it does so may 612 vary over time. The consultation may overlap with the previous step 613 (identification). 615 For example: 617 a. The IAOC asks the community whether there are any barriers to 618 holding a successful meeting in any of the target cities in the 619 set. 621 b. Community responses are reviewed and concerns investigated by the 622 Meetings Committee. The results together with recommendations 623 for whether each city should be considered as potential meeting 624 location is provided to the IAOC. 626 c. The IAOC identifies which cities are to be considered as a 627 potential meeting location. 629 d. On a public web page, the IAOC lists all candidate cities, when 630 community input was solicited, and if a city is to be considered 631 as a potential meeting location. 633 e. The Meetings Committee pursues potential meeting locations based 634 on the posted list of cities that have been identified as a 635 potential meeting locations. 637 5.3. Qualification 639 Visit: 641 a. Secretariat assesses "vetted" target cities to determine 642 availability and conformance to criteria. 644 b. Meetings Committee approves potential cities for site 645 qualification visit. 647 c. Site qualification visits are arranged by Secretariat and 648 preliminary negotiations are undertaken with selected potential 649 sites. 651 d. Site qualification visit is conducted using the checklist along 652 the lines of what is included in Appendix A; the site visit team 653 prepares a site report and discusses it with the Meetings 654 Committee. 656 5.4. Negotiation 658 2.75 - 3 years out, initiate contract negotiations: 660 a. The Meetings Committee reviews the Venue options based on Venue 661 selection criteria and recommends a Venue to the IAOC. Only 662 options that meet all Mandatory labeled criteria might be 663 recommended. 665 b. IAOC selects a Venue for contracting as well as a back-up 666 contracting Venue, if available. 668 c. Secretariat negotiates with selected Venue. IAD reviews contract 669 and requests IAOC and ISOC approval of contract and authority for 670 Secretariat to execute contract on ISOC's behalf. 672 d. Contracts are executed. 674 5.5. Late Changes 676 If at any time after a contract is signed the IAOC learns where a 677 Venue's circumstances have significantly changed, such that the 678 Important or Mandatory criteria can no longer be met, the IAOC MUST 679 reconsider the selection. A description of how reconsideration 680 currently takes place is found in Appendix B. The IAOC will gauge 681 the cost of making a change against the ability of the IETF to 682 conclude a successful meeting, and make a final determination based 683 on their best judgment. When there is enough time to do so, the IAOC 684 MUST consult the community about changes. 686 6. IANA Considerations 688 This memo asks the IANA for no new parameters. 690 7. Security Considerations 692 This note proposes no protocols, and therefore no new protocol 693 insecurities. 695 8. Privacy Considerations 697 This note reveals no personally identifying information apart from 698 its authorship. 700 9. Acknowledgements 702 This document was originally assembled and edited by Fred Baker. 703 Additional commentary came from Jari Arkko, Scott Bradner, Alissa 704 Cooper, and other participants in the MtgVenue working group. 706 10. References 708 10.1. Normative References 710 [MeetingNet] 711 O'Donoghue, K., Martin, J., Elliott, C., and J. Jaeggli, 712 "IETF Meeting Network Requirements", WEB 713 https://iaoc.ietf.org/ietf-network-requirements.html. 715 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 716 3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996, 717 . 719 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 720 Requirement Levels", BCP 14, RFC 2119, 721 DOI 10.17487/RFC2119, March 1997, 722 . 724 [RFC4071] Austein, R., Ed. and B. Wijnen, Ed., "Structure of the 725 IETF Administrative Support Activity (IASA)", BCP 101, 726 RFC 4071, DOI 10.17487/RFC4071, April 2005, 727 . 729 [RFC4371] Carpenter, B., Ed. and L. Lynch, Ed., "BCP 101 Update for 730 IPR Trust", BCP 101, RFC 4371, DOI 10.17487/RFC4371, 731 January 2006, . 733 [RFC7691] Bradner, S., Ed., "Updating the Term Dates of IETF 734 Administrative Oversight Committee (IAOC) Members", 735 BCP 101, RFC 7691, DOI 10.17487/RFC7691, November 2015, 736 . 738 10.2. Informative References 740 [I-D.barnes-healthy-food] 741 Barnes, M., "Healthy Food and Special Dietary Requirements 742 for IETF meetings", draft-barnes-healthy-food-07 (work in 743 progress), July 2013. 745 [RFC3935] Alvestrand, H., "A Mission Statement for the IETF", 746 BCP 95, RFC 3935, October 2004. 748 Appendix A. Site Qualification Visit Checklist 750 This section is based on the PreQualification RFP, dated January 23, 751 2016, which is available at . The contents of the link may be 753 changed as needed. 755 Prequalification Specification 757 +----------------+-------------------+----------+-------------------+ 758 | Meeting Dates: | _________________ | Contact: | _________________ | 759 +----------------+-------------------+----------+-------------------+ 760 | City: | _______________ | Phone: | _______________ | 761 +----------------+-------------------+----------+-------------------+ 762 | Venue | _______________ | Email: | _______________ | 763 | Considered: | | | | 764 +----------------+-------------------+----------+-------------------+ 766 Meeting Space Requirements: 768 +------------+--------+-------+---------+---------+---------+-------+ 769 | Purpose | Space | sf/sm | Room As | Daily | Days + | Total | 770 | | Requir | | signed | Rate + | (set- | Price | 771 | | ed / | | | (set-up | up) | | 772 | | Set | | | rate) | | | 773 +------------+--------+-------+---------+---------+---------+-------+ 774 | Registrati | 1200 / | 13,50 | Reg | | 6 + (1) | | 775 | on / | custom | 0 / | areas | | | | 776 | Breaks** | | 1254 | or | | | | 777 | | | | foyers | | | | 778 +------------+--------+-------+---------+---------+---------+-------+ 779 | NOC | 25 / | 1200 | | | 8 + (5) | | 780 | | conf | / 111 | | | | | 781 +------------+--------+-------+---------+---------+---------+-------+ 782 | Terminal | 75 / | 1350 | | | 7 + (1) | | 783 | Room | class | / 125 | | | | | 784 +------------+--------+-------+---------+---------+---------+-------+ 785 | Storage | | 350 / | | | 6 + (4) | | 786 | (if Reg < | | 33 | | | | | 787 | 1000sf) | | | | | | | 788 +------------+--------+-------+---------+---------+---------+-------+ 789 | Plenary * | 900 / | 8500 | | | 2 | | 790 | | theatr | / 790 | | | | | 791 | | e | | | | | | 792 +------------+--------+-------+---------+---------+---------+-------+ 793 | Breakout 1 | 80 / t | 800 / | | | 6 | | 794 | | heatre | 74 | | | | | 795 +------------+--------+-------+---------+---------+---------+-------+ 796 | Breakout 2 | 100 / | 1000 | | | 6 | | 797 | | theatr | / 93 | | | | | 798 | | e | | | | | | 799 +------------+--------+-------+---------+---------+---------+-------+ 800 | Breakout 3 | 100 / | 1000 | | | 6 | | 801 | | theatr | / 93 | | | | | 802 | | e | | | | | | 803 +------------+--------+-------+---------+---------+---------+-------+ 804 | Breakout 4 | 150 / | 1400 | | | 6 | | 805 | | theatr | / 130 | | | | | 806 | | e | | | | | | 807 +------------+--------+-------+---------+---------+---------+-------+ 808 | Breakout 5 | 150 / | 1400 | | | 7 | | 809 | | theatr | / 130 | | | | | 810 | | e | | | | | | 811 +------------+--------+-------+---------+---------+---------+-------+ 812 | Breakout 6 | 200 / | 1900 | | | 7 | | 813 | | theatr | / 177 | | | | | 814 | | e | | | | | | 815 +------------+--------+-------+---------+---------+---------+-------+ 816 | Breakout 7 | 250 / | 2400 | | | 6 | | 817 | | theatr | / 223 | | | | | 818 | | e | | | | | | 819 +------------+--------+-------+---------+---------+---------+-------+ 820 | Breakout 8 | 300 / | 2800 | | | 6 | | 821 | | theatr | / 260 | | | | | 822 | | e | | | | | | 823 +------------+--------+-------+---------+---------+---------+-------+ 824 | Office 1 R | 10 / | 1000 | | | 6 + (4) | | 825 | egistratio | conf | / 93 | | | | | 826 | n | | | | | | | 827 +------------+--------+-------+---------+---------+---------+-------+ 828 | Mtg Rm 1 | 8 / | 350 / | | | 6 | | 829 | (IAB) | conf | 33 | | | | | 830 +------------+--------+-------+---------+---------+---------+-------+ 831 | Mtg Rm 2 | 20 / | 900 / | | | 6 | | 832 | (ISOC1) | conf | 84 | | | | | 833 +------------+--------+-------+---------+---------+---------+-------+ 834 | Mtg Rm 3 | 20 / | 900 / | | | 6 | | 835 | (ISOC2) | conf | 84 | | | | | 836 +------------+--------+-------+---------+---------+---------+-------+ 837 | Mtg Rm 4 | 15 / | 650 / | | | 6 | | 838 | (IAOC / | conf | 60 | | | | | 839 | IAD) | | | | | | | 840 +------------+--------+-------+---------+---------+---------+-------+ 841 | Mtg Rm 5 | 15 / | 650 / | | | 6 | | 842 | (NC) | conf | 60 | | | | | 843 +------------+--------+-------+---------+---------+---------+-------+ 844 | Mtg Rm 6 | Nov 5 | 150 / | | | 6 | | 845 | (NC IV) | / conf | 14 | | | | | 846 +------------+--------+-------+---------+---------+---------+-------+ 847 | Mtg Rm 7 | 40 / u | 1550 | | | 7 | | 848 | (40U) | -shape | / 144 | | | | | 849 +------------+--------+-------+---------+---------+---------+-------+ 850 | Mtg Rm 8 | 20 / u | 950 / | | | 6 | | 851 | (20U) | -shape | 88 | | | | | 852 +------------+--------+-------+---------+---------+---------+-------+ 853 | Mtg Rm 9 | 16 / | 800 / | | | 6 | | 854 | (IESG) | conf | 74 | | | | | 855 +------------+--------+-------+---------+---------+---------+-------+ 856 | I: Postel | 40 / | 400 / | | | 1 | | 857 | Rec | rec | 37 | | | | | 858 | (WedPM) | | | | | | | 859 +------------+--------+-------+---------+---------+---------+-------+ 860 | I: AC (Fri | 70 / | 1700 | | | 1 | | 861 | PM) | custom | / 158 | | | | | 862 +------------+--------+-------+---------+---------+---------+-------+ 863 | I: BoT | 70 / | 1700 | Same as | | 2 | | 864 | (Sat / | custom | / 158 | AC | | | | 865 | Sun) | | | | | | | 866 +------------+--------+-------+---------+---------+---------+-------+ 867 | I: Bot | 40 / b | 550 / | | | 2 | | 868 | Lunch (Sat | anquet | 51 | | | | | 869 | / Sun) | | | | | | | 870 +------------+--------+-------+---------+---------+---------+-------+ 871 | I: Brfg | 150 / | 1400 | Same as | | 1 | | 872 | Panel (Tue | theatr | / 130 | BO4 | | | | 873 | lunch) | e | | | | | | 874 +------------+--------+-------+---------+---------+---------+-------+ 875 | I: Rec / | 50 / | 700 / | | | 1 | | 876 | Dinner | rec / | 65 | | | | | 877 | (Fri) | ban | | | | | | 878 +------------+--------+-------+---------+---------+---------+-------+ 879 | I: Fellows | 70 / | 900 / | | | 1 | | 880 | Dinner | rec / | 84 | | | | | 881 | | ban | | | | | | 882 +------------+--------+-------+---------+---------+---------+-------+ 883 | Lounge | 50 / | 600 / | | | 5 | | 884 | | lounge | 56 | | | | | 885 +------------+--------+-------+---------+---------+---------+-------+ 886 | Companion | 20 / | 200 / | | | 1 | | 887 | Rec | rec | 19 | | | | | 888 +------------+--------+-------+---------+---------+---------+-------+ 889 | Newcomers | 300 / | 2500 | | | 1 | | 890 | Rec | rec | / 232 | | | | | 891 +------------+--------+-------+---------+---------+---------+-------+ 892 | Welcome | 800 / | 6400 | | | 1 | | 893 | Rec | rec | / 595 | | | | | 894 +------------+--------+-------+---------+---------+---------+-------+ 895 | Hackathon | 200 / | 3000 | | | 2 + (1) | | 896 | | class | / 279 | | | | | 897 +------------+--------+-------+---------+---------+---------+-------+ 898 | Bits n | 700 / | 7000 | | | 2 | | 899 | Bytes | rec | / 650 | | | | | 900 +------------+--------+-------+---------+---------+---------+-------+ 902 * Breakouts 6 +7+8 (or some combination thereof) to be used as the 903 Plenary as Plenary and Breakouts do not run simultaneously 905 ** Additional space required, not included in total meeting space 907 Note: Prices quoted are those that will apply on the dates of the 908 event and include all tax, services and fees 910 Accomodation: 912 +-------+------+------+----------+-------+-------+----------+-------+ 913 | Day/D | Tota | Desi | Primary | Rate* | Desir | Overflow | Rate | 914 | ate | l Ro | red | Hotel Av | Prima | ed | Hotel Av | * Ove | 915 | | oms | Room | ailabili | ry | Rooms | ailabili | rflow | 916 | | Requ | s at | ty | Hotel | at Ov | ty | Hotel | 917 | | ired | Prim | | | erflo | | | 918 | | | ary | | | w Hot | | | 919 | | | Hote | | | els | | | 920 | | | l | | | | | | 921 +-------+------+------+----------+-------+-------+----------+-------+ 922 | Total | 5,25 | 4,24 | | | 1,005 | | | 923 | room | 0 | 5 | | | (180 | | | 924 | night | (780 | (600 | | | peak) | | | 925 | s | peak | peak | | | | | | 926 | | ) | ) | | | | | | 927 +-------+------+------+----------+-------+-------+----------+-------+ 928 | Monda | 5 | 5 | | | 0 | | | 929 | y | | | | | | | | 930 +-------+------+------+----------+-------+-------+----------+-------+ 931 | Tuesd | 15 | 15 | | | 0 | | | 932 | ay | | | | | | | | 933 +-------+------+------+----------+-------+-------+----------+-------+ 934 | Wedne | 25 | 25 | | | 0 | | | 935 | sday | | | | | | | | 936 +-------+------+------+----------+-------+-------+----------+-------+ 937 | Thurs | 50 | 50 | | | 0 | | | 938 | day | | | | | | | | 939 +-------+------+------+----------+-------+-------+----------+-------+ 940 | Frida | 185 | 150 | | | 35 | | | 941 | y | | | | | | | | 942 +-------+------+------+----------+-------+-------+----------+-------+ 943 | Satur | 500 | 400 | | | 100 | | | 944 | day | | | | | | | | 945 +-------+------+------+----------+-------+-------+----------+-------+ 946 | Sunda | 770 | 600 | | | 170 | | | 947 | y | | | | | | | | 948 +-------+------+------+----------+-------+-------+----------+-------+ 949 | Monda | 780 | 600 | | | 180 | | | 950 | y | | | | | | | | 951 +-------+------+------+----------+-------+-------+----------+-------+ 952 | Tuesd | 780 | 600 | | | 180 | | | 953 | ay | | | | | | | | 954 +-------+------+------+----------+-------+-------+----------+-------+ 955 | Wedne | 750 | 600 | | | 150 | | | 956 | sday | | | | | | | | 957 +-------+------+------+----------+-------+-------+----------+-------+ 958 | Thurs | 700 | 600 | | | 100 | | | 959 | day | | | | | | | | 960 +-------+------+------+----------+-------+-------+----------+-------+ 961 | Frida | 370 | 300 | | | 70 | | | 962 | y | | | | | | | | 963 +-------+------+------+----------+-------+-------+----------+-------+ 964 | Satur | 220 | 200 | | | 20 | | | 965 | day | | | | | | | | 966 +-------+------+------+----------+-------+-------+----------+-------+ 967 | Sunda | 100 | 100 | | | 0 | | | 968 | y | | | | | | | | 969 +-------+------+------+----------+-------+-------+----------+-------+ 971 o Guest-room Internet, breakfast, 10% commission, all tax, service 972 and fees are incorporated into the lodging rate. 974 o Guest-room rates quoted are those that will apply on the dates of 975 the event. 977 o Attendees will book individually. 979 Food and Beverage: 981 +----------------+-------------------------+------------------------+ 982 | Purpose | When | Service | 983 +----------------+-------------------------+------------------------+ 984 | Meet and Greet | Sunday afternoon (250 - | Cold appetizers, beer | 985 | | 350 people) | and wine | 986 +----------------+-------------------------+------------------------+ 987 | Welcome | Sunday evening (600 - | Appetizers and | 988 | Reception | 800 people) | cocktails (no-host | 989 | | | bar) | 990 +----------------+-------------------------+------------------------+ 991 | Companion | Sunday afternoon (20 - | Appetizers / non- | 992 | Reception | 30 people) | alcoholic beverages | 993 +----------------+-------------------------+------------------------+ 994 | AM Breaks | Daily beginning Monday | Continental breakfast | 995 | | (1,000+ people) | | 996 +----------------+-------------------------+------------------------+ 997 | PM Breaks | Daily beginning Monday | Light snack with | 998 | | (1,000+ people) | beverages | 999 +----------------+-------------------------+------------------------+ 1000 | Breakfast | Daily (15 to 60 people) | Continental or hot | 1001 | | | buffet | 1002 +----------------+-------------------------+------------------------+ 1003 | Lunch | Daily (15 to 70 people) | Box or buffet | 1004 +----------------+-------------------------+------------------------+ 1005 | Dinner | Friday and/or Sunday | Bar and hot buffet | 1006 | | evening (50 people) | | 1007 +----------------+-------------------------+------------------------+ 1008 | Bits n Bytes | Thursday evening (700+ | Appetizers and | 1009 | (reception) | people) | cocktails | 1010 +----------------+-------------------------+------------------------+ 1011 Technology: 1013 +----------------+--------------------------------+-----------------+ 1014 | Item | Question | Response | 1015 +----------------+--------------------------------+-----------------+ 1016 | Outside | Can we bring in our own | _______________ | 1017 | connection | external circuit? | | 1018 +----------------+--------------------------------+-----------------+ 1019 | Infrastructure | Can we use your cabling | _______________ | 1020 | | infrastructure to build a | | 1021 | | dedicated network, including | | 1022 | | installation of network | | 1023 | | equipment in data closets and | | 1024 | | phone rooms? | | 1025 +----------------+--------------------------------+-----------------+ 1026 | Access | Is it possible to have 24-hour | _______________ | 1027 | | access to data closets and | | 1028 | | phone rooms to support the | | 1029 | | network? | | 1030 +----------------+--------------------------------+-----------------+ 1031 | Wireless | Is it possible to deploy a | _______________ | 1032 | | wireless network? | | 1033 +----------------+--------------------------------+-----------------+ 1034 | Venue network | Would you be willing to | _______________ | 1035 | | disable your wireless network | | 1036 | | in the meeting and public | | 1037 | | spaces? | | 1038 +----------------+--------------------------------+-----------------+ 1039 | Infrastructure | Do all proposed meeting rooms | _______________ | 1040 | | have at least one available | | 1041 | | Category 5 twisted pair | | 1042 | | connection? | | 1043 +----------------+--------------------------------+-----------------+ 1045 Appendix B. Contingency Planning Flow Chart 1047 This section is based on the Contingency Planning Flow Chart which is 1048 available at . The contents of the link may changed as needed. 1051 ----- 1052 (Start) 1053 ----- 1054 | 1055 | 1056 v 1057 +----------------+ 1058 | Does the IAOC | +------------+ 1059 |believe there is| | Can an | +-------------+ 1060 |an unacceptable | Yes | effective | Yes | Secure | 1061 | risk in having |---->|F2F meeting |---->| alternate |----+ 1062 | the meeting in | |be organized| |meeting venue| | 1063 | the contracted | | elsewhere? | +-------------+ | 1064 | location? | +------------+ | 1065 +----------------+ /\ |No | 1066 |No / | | 1067 | Yes / | | 1068 v / | | 1069 +-----------------+ / | | 1070 | Does the | / +----------+ | 1071 |community believe|/ | Can an | | 1072 | there is an | |effective | | 1073 |unacceptable risk| | virtual | Yes | 1074 | in having the | |meeting be|--------+ | 1075 | meeting in the | |organized | | | 1076 | contracted | |elsewhere?| | | 1077 | location? | +----------+ | | 1078 +-----------------+ |No | | 1079 |No | | | 1080 | | | | 1081 v v v v 1082 ------- ------- ------- --------- 1083 (Proceed) (Cancel ) ( Hold ) ( Hold ) 1084 ( with ) ( the ) (virtual) (relocated) 1085 (meeting) (meeting) (meeting) ( meeting ) 1086 ------- ------- ------- --------- 1088 Appendix C. Change Log 1090 2016-01-12: Initial version 1092 2016-01-21: Update to reflect https://iaoc.ietf.org/documents/ 1093 VenueSelectionCriteriaJan2016.pdf and 1094 https://iaoc.ietf.org/documents/VenueSelectionProcess11Jan16.pdf, 1095 accessed from https://iaoc.ietf.org/private/privatemeetings.html. 1097 2016-02-23: Reorganize and capture IAOC Meetings Committee 1098 discussions. 1100 2016-03-03: Final from Design Team. 1102 2016-03-17: First update incorporating mtgvenue@ietf.org comments 1104 2016-05-20 Updated in accordance with editing by Laura Nugent, Dave 1105 Crocker, Lou Berger, Fred Baker, and others. 1107 posting as working group draft August 2, 2016 1109 Reorganized per Alissa Cooper outline Work in progress. In 1110 addition, contributors were re-organized to be authors. 1112 2016-10-28 Editor changeover. Further alignment with guidance by 1113 Alissa Cooper, Andrew Sullivan and the mtgvenue working group. 1114 Many various changes. 1116 2016-11-16 Extensive editorial, format and polishing pass. A few 1117 substance changes, including food section. 1119 2016-11-30 Additions based on working group meeting and off-list 1120 discussions; more editorial and format hacking. 1122 2016-12-24 Various clarifying bits to provide some glue between the 1123 high-level 'objectives' and the detailed criteria and roles, per 1124 suggestions fronm Lear. Editorial changes, per 12/27 response to 1125 Cooper. Refined uses of 'facility' and 'venue', per 12/4 response 1126 to Carpenter; also added Carpenter 'lounge' text. Moved community 1127 consultation to a separate criterion; removed 'acceptable to the 1128 IETF Community from the 2 entries that had it. Removed Post- 1129 Seroul Revisions and Text Carried Forward. 1131 2016-12-24 Address comments made on list by Stephen Farrell 1132 . Minor text change in Section 5. 1133 Replaced links in sections 5.3 and 5.5 with Appendix A and 1134 Appendix B 1136 2017-03-12 Add openness comment as requested by Stephen Farrell. 1137 Add statement about 4071 as proposed by Brian and modified by 1138 Jari. Elaborated on what "unfiltered" means, based on discussion 1139 between Eliot and Stephen. Preface to Section 5 as discussed 1140 between Lou and Stephen. Slight editorial tweak to that by Eliot. 1141 IETF operates internationally, as proposed by Brian. 1143 2017-04-18 Add new introductory text. Sharpen mandatory definition. 1144 Split first criteria into two, and reword them to be more 1145 actionable. Remove net cash positive requirement. Change many 1146 critera from Mandatory to Important. Remove consensus text. 1147 Modify chapeau. Add some normative MUSTs in Section 5, and 1148 restructure Section 5.5. A bunch of other stuff as well. Use 1149 diff. 1151 Authors' Addresses 1153 Ray Pelletier 1154 Internet Society 1156 Email: rpelletier@isoc.org 1158 Laura Nugent 1159 Association Management Solutions 1161 Email: lnugent@amsl.com 1163 Dave Crocker (editor) 1164 Brandenburg InternetWorking 1166 Email: dcrocker@bbiw.net 1168 Lou Berger 1169 LabN Consulting, L.L.C. 1171 Email: lberger@labn.net 1173 Ole Jacobsen 1174 The Internet Protocol Journal 1176 Email: olejacobsen@me.com 1178 Jim Martin 1179 INOC 1181 Email: jim@inoc.com 1183 Fred Baker (editor) 1185 Email: FredBaker.IETF@gmail.com 1186 Eliot Lear (editor) 1187 Cisco Systems GmbH 1189 Email: lear@cisco.com