draft-ietf-mtgvenue-iaoc-venue-selection-process-10.txt   draft-ietf-mtgvenue-iaoc-venue-selection-process-11.txt 
mtgvenue E. Lear, Ed. mtgvenue E. Lear, Ed.
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Intended status: Best Current Practice October 26, 2017 Intended status: Best Current Practice January 11, 2018
Expires: April 29, 2018 Expires: July 15, 2018
IETF Plenary Meeting Venue Selection Process IETF Plenary Meeting Venue Selection Process
draft-ietf-mtgvenue-iaoc-venue-selection-process-10 draft-ietf-mtgvenue-iaoc-venue-selection-process-11
Abstract Abstract
The IASA has responsibility for arranging IETF plenary meeting Venue The IASA has responsibility for arranging IETF plenary meeting Venue
selection and operation. This document details the IETF's Meeting selection and operation. This document details the IETF's Meeting
Venue Selection Process from the perspective of its goals, criteria Venue Selection Process from the perspective of the community's
and thought processes. It points to additional process documents on goals, criteria and thought processes. It points to additional
the IAOC Web Site that go into further detail and are subject to process documents on the IAOC Web Site that go into further detail
change with experience. and are subject to change with experience.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 29, 2018. This Internet-Draft will expire on July 15, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
skipping to change at page 2, line 26 skipping to change at page 2, line 26
3.3. Other Consideraitons . . . . . . . . . . . . . . . . . . 9 3.3. Other Consideraitons . . . . . . . . . . . . . . . . . . 9
4. Venue Selection Roles . . . . . . . . . . . . . . . . . . . . 9 4. Venue Selection Roles . . . . . . . . . . . . . . . . . . . . 9
4.1. IETF Participants . . . . . . . . . . . . . . . . . . . . 9 4.1. IETF Participants . . . . . . . . . . . . . . . . . . . . 9
4.2. IESG and IETF Chair . . . . . . . . . . . . . . . . . . . 10 4.2. IESG and IETF Chair . . . . . . . . . . . . . . . . . . . 10
4.3. The Internet Society . . . . . . . . . . . . . . . . . . 10 4.3. The Internet Society . . . . . . . . . . . . . . . . . . 10
4.4. IETF Administrative Oversight Committee . . . . . . . . . 10 4.4. IETF Administrative Oversight Committee . . . . . . . . . 10
4.5. IETF Administrative Support Activity . . . . . . . . . . 11 4.5. IETF Administrative Support Activity . . . . . . . . . . 11
4.6. IETF Administrative Director . . . . . . . . . . . . . . 11 4.6. IETF Administrative Director . . . . . . . . . . . . . . 11
4.7. IAOC Meetings Committee . . . . . . . . . . . . . . . . . 11 4.7. IAOC Meetings Committee . . . . . . . . . . . . . . . . . 11
5. Venue Selection Steps . . . . . . . . . . . . . . . . . . . . 11 5. Venue Selection Steps . . . . . . . . . . . . . . . . . . . . 11
5.1. Identification . . . . . . . . . . . . . . . . . . . . . 11 5.1. Identification . . . . . . . . . . . . . . . . . . . . . 12
5.2. Consultation . . . . . . . . . . . . . . . . . . . . . . 12 5.2. Consultation . . . . . . . . . . . . . . . . . . . . . . 12
5.3. Qualification . . . . . . . . . . . . . . . . . . . . . . 13 5.3. Qualification . . . . . . . . . . . . . . . . . . . . . . 13
5.4. Negotiation . . . . . . . . . . . . . . . . . . . . . . . 13 5.4. Negotiation . . . . . . . . . . . . . . . . . . . . . . . 13
5.5. Late Changes . . . . . . . . . . . . . . . . . . . . . . 13 5.5. Late Changes . . . . . . . . . . . . . . . . . . . . . . 14
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
7. Security Considerations . . . . . . . . . . . . . . . . . . . 14 7. Security Considerations . . . . . . . . . . . . . . . . . . . 14
8. Privacy Considerations . . . . . . . . . . . . . . . . . . . 14 8. Privacy Considerations . . . . . . . . . . . . . . . . . . . 14
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 14 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 14
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
11.1. Normative References . . . . . . . . . . . . . . . . . . 15 11.1. Normative References . . . . . . . . . . . . . . . . . . 15
11.2. Informative References . . . . . . . . . . . . . . . . . 16 11.2. Informative References . . . . . . . . . . . . . . . . . 16
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 16 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 16
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 17 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 18
1. Introduction 1. Introduction
The Internet Administrative Support Activity (IASA) has The IETF Internet Administrative Support Activity (IASA) has
responsibility for arranging IETF plenary meeting venue selection and responsibility for arranging IETF plenary meeting venue selection and
operation. The purpose of this document is to guide the IASA in operation. The purpose of this document is to guide the IASA in
their selection of regions, cities, facilities, and hotels. The IASA their selection of regions, cities, facilities, and hotels. The IASA
applies this guidance at different points in the process in an applies this guidance at different points in the process in an
attempt to faithfully meet the requirements of the IETF community. attempt to faithfully meet the requirements of the IETF community.
We specify a set of general criteria for venue selection and several We specify a set of general criteria for venue selection and several
requirements for transparency and community consultation. requirements for transparency and community consultation.
It remains the responsibility of the IASA to apply their best It remains the responsibility of the IASA to apply their best
judgment. The IASA accepts input and feedback both during the judgment. The IASA accepts input and feedback both during the
skipping to change at page 6, line 21 skipping to change at page 6, line 21
inform the community and address the matter on a case by case basis. inform the community and address the matter on a case by case basis.
o The Facility MUST provide sufficient space in an appropriate o The Facility MUST provide sufficient space in an appropriate
layout to accommodate the expected number of people to attend that layout to accommodate the expected number of people to attend that
meeting. meeting.
o The Facility and IETF Hotels MUST provide wheelchair access to o The Facility and IETF Hotels MUST provide wheelchair access to
accommodate the number of people who are anticipated to require accommodate the number of people who are anticipated to require
it. it.
o It MUST be possible to provision Internet Access to the Meeting o It MUST be possible to provision Internet Access to the Facility
Venue that allows attendees to utilize the Internet for all their and IETF Hotels that allows attendees to utilize the Internet for
IETF, business, and day to day needs. This includes, but is not all their IETF, business, and day to day needs. This includes,
limited to, native and unmodified IPv4 and IPv6 connectivity, but is not limited to, native and unmodified IPv4 and IPv6
global reachability, and no additional limitation that would connectivity, global reachability, and no additional limitation
materially impact their Internet use. To ensure availability, it that would materially impact their Internet use. To ensure
MUST be possible to provision redundant paths to the Internet. availability, it MUST be possible to provision redundant paths to
the Internet.
3.2. Important Criteria 3.2. Important Criteria
The criteria in this subsection are not mandatory, but are still The criteria in this subsection are not mandatory, but are still
highly significant. It may be necessary to trade one or more of highly significant. It may be necessary to trade one or more of
these criteria off against others. A Venue that meets more of these these criteria off against others. A Venue that meets more of these
criteria is on the whole preferable than another that meets fewer of criteria is on the whole preferable than another that meets fewer of
these criteria. Requirements classed as Important can also be these criteria. Requirements classed as Important can also be
balanced across Venue selections for multiple meetings. When a balanced across Venue selections for multiple meetings. When a
particular requirement in this section cannot be met, the IASA MUST particular requirement in this section cannot be met, the IASA MUST
skipping to change at page 6, line 50 skipping to change at page 6, line 51
as a result, have been inconvenienced in some way. as a result, have been inconvenienced in some way.
3.2.1. Venue City Criteria 3.2.1. Venue City Criteria
o Travel to the Venue is acceptable based on cost, time, and burden o Travel to the Venue is acceptable based on cost, time, and burden
for participants traveling from multiple regions. It is for participants traveling from multiple regions. It is
anticipated that the burden borne will be generally shared over anticipated that the burden borne will be generally shared over
the course of multiple years. the course of multiple years.
o The Venue is assessed as favorable for obtaining a host and o The Venue is assessed as favorable for obtaining a host and
sponsors. That is, the Meeting is in a location and at a price sponsors. That is, the Meeting is in a location that it is
that it is possible and probable to find a host and sponsors. possible and probable to find a host and sponsors.
o Travel barriers to entry, including visa requirements, are likely o Travel barriers to entry, including visa requirements, are likely
to be such that an overwhelming majority of participants who wish to be such that an overwhelming majority of participants who wish
to do so can attend. The term "travel barriers" is to be read to do so can attend. The term "travel barriers" is to be read
broadly by the IASA in the context of whether a successful meeting broadly by the IASA in the context of whether a successful meeting
can be had. can be had.
o Economic, safety, and health risks associated with this Venue are o Economic, safety, and health risks associated with this Venue are
acceptable. acceptable.
skipping to change at page 9, line 42 skipping to change at page 9, line 42
provide guidance regarding safety, location of local services, and provide guidance regarding safety, location of local services, and
understanding best ways to get to and from the Venue, and local understanding best ways to get to and from the Venue, and local
customs, as well as identify how our requirements are met. customs, as well as identify how our requirements are met.
4. Venue Selection Roles 4. Venue Selection Roles
The formal structure of IETF administrative support functions is The formal structure of IETF administrative support functions is
documented in BCP 101 [RFC4071], [RFC4371], [RFC7691]. The reader is documented in BCP 101 [RFC4071], [RFC4371], [RFC7691]. The reader is
expected to be familiar with the entities and roles defined by that expected to be familiar with the entities and roles defined by that
document, in particular for the IASA, ISOC, IAOC and IAD. This document, in particular for the IASA, ISOC, IAOC and IAD. This
section covers the meeting selection related roles of these and other section describes the roles involved in meeting venue selection
parties that participate in the process. Note that roles beyond (e.g., not who does what at the meetings). It is anticipated that
meeting selection, e.g., actually running and reporting on meetings, those roles will evolve. The IASA is responsible for keeping the
are outside the scope of this document. community informed in this regard, and MAY do so without updating
this memo.
4.1. IETF Participants 4.1. IETF Participants
While perhaps obvious, it is important to note that IETF meetings While perhaps obvious, it is important to note that IETF meetings
serve all those who contribute to the work of the IETF. This serve all those who contribute to the work of the IETF. This
includes those who attend meetings in person, from newcomer to includes those who attend meetings in person, from newcomer to
frequent attendee, to those who participate remotely, as well as frequent attendee, to those who participate remotely, as well as
those who do not attend but who also contribute their ideas. those who do not attend but who also contribute their ideas.
Potential new contributors are also considered in the process. Potential new contributors are also considered in the process.
skipping to change at page 10, line 40 skipping to change at page 10, line 41
o Executes all Venue contracts on behalf of the IETF at the request o Executes all Venue contracts on behalf of the IETF at the request
of the IASA of the IASA
o Solicits meeting sponsorships o Solicits meeting sponsorships
o Collects all meeting-related revenues, including registration o Collects all meeting-related revenues, including registration
fees, sponsorships, hotel commissions, and other miscellaneous fees, sponsorships, hotel commissions, and other miscellaneous
revenues revenues
ISOC also provides accounting services, such as invoicing and monthly ISOC sees to the provisioning and oversight of accounting services,
financial statements. such as invoicing and monthly financial statements.
4.4. IETF Administrative Oversight Committee 4.4. IETF Administrative Oversight Committee
The IETF Administrative Oversight Committee (IAOC) has the The IETF Administrative Oversight Committee (IAOC) has the
responsibility to oversee and select IETF meeting venues. It responsibility to oversee and select IETF meeting venues. It
instructs the IAD and Secretariat to work with the Internet Society instructs the IAD and Secretariat to work with the Internet Society
to write the relevant contracts. It approves the IETF meetings to write the relevant contracts. It approves the IETF meetings
calendar. In cooperation with the IAD, the IAOC takes necessary calendar. In cooperation with the IAD, the IAOC takes necessary
actions to ensure that the IASA is aware of participant concerns actions to ensure that the IASA is aware of participant concerns
about particular venues as early in the process as is feasible. about particular venues as early in the process as is feasible.
4.5. IETF Administrative Support Activity 4.5. IETF Administrative Support Activity
The IETF Administrative Support Activity (IASA) performs the meeting The IETF Administrative Support Activity (IASA) performs the meeting
selection process under the oversight of the IAOC. This includes selection process under the oversight of the IAOC. The IETF
identifying, qualifying and reporting on potential meeting sites, as Secretariat is under contract to support the meeting selection
well as supporting meeting Venue contract negotiation. The IETF process. This includes identifying, qualifying and reporting on
Secretariat is part of the IASA under the management of the IAD. The potential meeting sites, as well as supporting meeting Venue contract
IAD takes appropriate actions to solicit community input regarding negotiation. The IETF Secretariat is part of the IASA under the
both retrospective and prospective feedback from participants. management of the IAD. The IAD takes appropriate actions to solicit
community input regarding both retrospective and prospective feedback
from participants.
4.6. IETF Administrative Director 4.6. IETF Administrative Director
The IETF Administrative Director (IAD) coordinates and supports the The IETF Administrative Director (IAD) coordinates and supports the
activities of the IETF Secretariat, the IAOC Meetings Committee and activities of the IETF Secretariat, the IAOC Meetings Committee and
the IASA to ensure the timely execution of the meeting process. This the IASA to ensure the timely execution of the meeting process. This
includes participating in the IAOC Meetings Committee and ensuring includes participating in the IAOC Meetings Committee and ensuring
its efforts are documented, overseeing Secretariat contract its efforts are documented, overseeing Secretariat contract
negotiations with the Venue, and coordinating contract execution with negotiations with the Venue, and coordinating contract execution with
ISOC. The meetings budget is managed by the IAD. ISOC. The meetings budget is managed by the IAD.
4.7. IAOC Meetings Committee 4.7. IAOC Meetings Committee
The fundamental purpose of the Meetings Committee is to participate The fundamental purpose of the Meetings Committee is to participate
in the Venue selection process, and to formulate recommendations to in the Venue selection process, and to formulate recommendations to
the IAOC regarding meeting sites. It also tracks the meetings the IAOC regarding meeting sites. It also recommends extraordinary
sponsorship program, recommends extraordinary meeting-related meeting-related expenses, and recommends the IETF meetings calendar
expenses, and recommends the IETF meetings calendar to the IAOC. The to the IAOC. The charter of the committee is at:
charter of the committee is at: <https://iaoc.ietf.org/ <https://iaoc.ietf.org/committees.html#meetings>.
committees.html#meetings>.
Membership in the Meetings Committee is at the discretion of the Membership in the Meetings Committee is at the discretion of the
IAOC; it includes an IAOC appointed chair, the IETF Administrative IAOC; it includes an IAOC appointed chair, the IETF Administrative
Director (IAD), IAOC members, representatives from the Secretariat, Director (IAD), IAOC members, representatives from the Secretariat,
and interested members of the community. and interested members of the community.
5. Venue Selection Steps 5. Venue Selection Steps
The following sequence is used by the IAOC to select venues. Unless The following sequence is used by the IAOC to select venues. Unless
otherwise stated below, the IAOC may evolve these steps over time otherwise stated below, the IAOC may evolve these steps over time
without updating this document. without updating this document.
5.1. Identification 5.1. Identification
Four years out,the IASA identifies cities that might be candidates Four years out,the IASA identifies cities that might be candidates
for meetings. For example: for meetings, making use of the Secretariat as they deem appropriate.
For example:
a. The IASA selects regions, cities, and dates for meetings. a. The IASA selects regions, cities, and dates for meetings.
b. A list of target cities per region is provided to the b. A list of target cities per region is provided to the
Secretariat, with host preferences, if known. Secretariat, with host preferences, if known.
c. Potential venues in preferred cities are identified and receive c. Potential venues in preferred cities are identified and receive
preliminary investigation, including reviews of Official Advisory preliminary investigation, including reviews of official advisory
Sources, consultation with specialty travel services, frequent sources, consultation with specialty travel services, frequent
travelers and local contacts to identify possible barriers to travelers and local contacts to identify possible barriers to
holding a successful meeting in the target cities. holding a successful meeting in the target cities.
d. Investigated cities and findings are provided by the Secretariat d. Investigated cities and findings are provided by the Secretariat
to the Meetings Committee for further review. Meetings Committee to the Meetings Committee for further review. Meetings Committee
makes a recommendation to the IASA of investigated/target cities makes a recommendation to the IASA of investigated/target cities
to consider further as well as issues identified and the results to consider further as well as issues identified and the results
of research conducted. of research conducted.
5.2. Consultation 5.2. Consultation
skipping to change at page 14, line 40 skipping to change at page 14, line 48
The following people provided substantial text contributions to this The following people provided substantial text contributions to this
memo: memo:
Fred Baker Fred Baker
Email: fred.ietf@gmail.com Email: fred.ietf@gmail.com
Fred originated this work. Fred originated this work.
Ray Pelletier Ray Pelletier
Internet Society Email: Rpelletier13@gmail.com
Email: rpelletier@isoc.org
Laura Nugent Laura Nugent
Association Management Solutions Association Management Solutions
Email: lnugent@amsl.com Email: lnugent@amsl.com
Lou Berger Lou Berger
LabN Consulting, L.L.C. LabN Consulting, L.L.C.
Email: lberger@labn.net Email: lberger@labn.net
Ole Jacobsen Ole Jacobsen
The Internet Protocol Journal The Internet Protocol Journal
EMail: olejacobsen@me.com EMail: olejacobsen@me.com
Jim Martin Jim Martin
INOC INOC
skipping to change at page 15, line 23 skipping to change at page 15, line 28
Additional contributions came from Jari Arkko, Scott Bradner, Alissa Additional contributions came from Jari Arkko, Scott Bradner, Alissa
Cooper, Dave Crocker, Jordi Palet Martinez, Andrew Sullivan, and Cooper, Dave Crocker, Jordi Palet Martinez, Andrew Sullivan, and
other participants in the mtgvenue working group. Those listed in other participants in the mtgvenue working group. Those listed in
this section or as contributors may or may not agree with the content this section or as contributors may or may not agree with the content
of this memo. of this memo.
11. References 11. References
11.1. Normative References 11.1. Normative References
[MeetingNet]
O'Donoghue, K., Martin, J., Elliott, C., and J. Jaeggli,
"IETF Meeting Network Requirements", WEB
https://iaoc.ietf.org/ietf-network-requirements.html.
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision [RFC2026] Bradner, S., "The Internet Standards Process -- Revision
3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996, 3", BCP 9, RFC 2026, DOI 10.17487/RFC2026, October 1996,
<http://www.rfc-editor.org/info/rfc2026>. <http://www.rfc-editor.org/info/rfc2026>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, <https://www.rfc- DOI 10.17487/RFC2119, March 1997,
editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC4071] Austein, R., Ed. and B. Wijnen, Ed., "Structure of the [RFC4071] Austein, R., Ed. and B. Wijnen, Ed., "Structure of the
IETF Administrative Support Activity (IASA)", BCP 101, IETF Administrative Support Activity (IASA)", BCP 101,
RFC 4071, DOI 10.17487/RFC4071, April 2005, RFC 4071, DOI 10.17487/RFC4071, April 2005,
<http://www.rfc-editor.org/info/rfc4071>. <http://www.rfc-editor.org/info/rfc4071>.
[RFC4371] Carpenter, B., Ed. and L. Lynch, Ed., "BCP 101 Update for [RFC4371] Carpenter, B., Ed. and L. Lynch, Ed., "BCP 101 Update for
IPR Trust", BCP 101, RFC 4371, DOI 10.17487/RFC4371, IPR Trust", BCP 101, RFC 4371, DOI 10.17487/RFC4371,
January 2006, <http://www.rfc-editor.org/info/rfc4371>. January 2006, <http://www.rfc-editor.org/info/rfc4371>.
[RFC7691] Bradner, S., Ed., "Updating the Term Dates of IETF [RFC7691] Bradner, S., Ed., "Updating the Term Dates of IETF
Administrative Oversight Committee (IAOC) Members", Administrative Oversight Committee (IAOC) Members",
BCP 101, RFC 7691, DOI 10.17487/RFC7691, November 2015, BCP 101, RFC 7691, DOI 10.17487/RFC7691, November 2015,
<http://www.rfc-editor.org/info/rfc7691>. <http://www.rfc-editor.org/info/rfc7691>.
11.2. Informative References 11.2. Informative References
[MeetingNet]
O'Donoghue, K., Martin, J., Elliott, C., and J. Jaeggli,
"IETF Meeting Network Requirements", WEB
https://iaoc.ietf.org/ietf-network-requirements.html.
[RFC3935] Alvestrand, H., "A Mission Statement for the IETF", [RFC3935] Alvestrand, H., "A Mission Statement for the IETF",
BCP 95, RFC 3935, October 2004. BCP 95, RFC 3935, October 2004.
Appendix A. Change Log Appendix A. Change Log
[RFC Editor: Please remove this section prior to publication.] [RFC Editor: Please remove this section prior to publication.]
2016-01-12: Initial version 2016-01-12: Initial version
2016-01-21: Update to reflect https://iaoc.ietf.org/documents/ 2016-01-21: Update to reflect https://iaoc.ietf.org/documents/
skipping to change at page 17, line 38 skipping to change at page 17, line 42
adds a desiderata section, adds a mandatory filtering requirement, adds a desiderata section, adds a mandatory filtering requirement,
consolidates introductory text, moves procedural requirements into consolidates introductory text, moves procedural requirements into
Section 5, removes the definition of Headquarters Hotel, removes Section 5, removes the definition of Headquarters Hotel, removes
the MUST in late changes, and adds a desire for a local the MUST in late changes, and adds a desire for a local
participant in site selection. participant in site selection.
2017-09-12 These are last call edits. Big change is around Internet 2017-09-12 These are last call edits. Big change is around Internet
requirements. Also, address Andrew Sullivan comments, as well as requirements. Also, address Andrew Sullivan comments, as well as
SM comments. Brian Carpenter big scrub on IAOC to IASA. SM comments. Brian Carpenter big scrub on IAOC to IASA.
2017-10-20 Final edits based on Laura Nugent's review. Most are 2017-10-20 Final edits from WGLC based on Laura Nugent's review.
editorial for clarity. Also, remove large table and link to the Most are editorial for clarity. Also, remove large table and link
live copy. to the live copy.
2018-01-10 Changes based on AD review.
Author's Address Author's Address
Eliot Lear (editor) Eliot Lear (editor)
Cisco Systems Cisco Systems
Richtistrasse 7 Richtistrasse 7
Wallisellen CH-8304 Wallisellen CH-8304
Switzerland Switzerland
Phone: +41 44 878 9200 Phone: +41 44 878 9200
 End of changes. 25 change blocks. 
57 lines changed or deleted 61 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/