draft-ietf-mtgvenue-iaoc-venue-selection-process-07.txt   draft-ietf-mtgvenue-iaoc-venue-selection-process-08.txt 
mtgvenue R. Pelletier mtgvenue E. Lear, Ed.
Internet-Draft Internet Society Internet-Draft Cisco Systems GmbH
Intended status: Best Current Practice L. Nugent Intended status: Best Current Practice July 24, 2017
Expires: November 15, 2017 Association Management Solutions Expires: January 25, 2018
D. Crocker, Ed.
Brandenburg InternetWorking
L. Berger
LabN Consulting, L.L.C.
O. Jacobsen
The Internet Protocol Journal
J. Martin
INOC
F. Baker, Ed.
E. Lear, Ed.
Cisco Systems GmbH
May 14, 2017
IETF Plenary Meeting Venue Selection Process IETF Plenary Meeting Venue Selection Process
draft-ietf-mtgvenue-iaoc-venue-selection-process-07 draft-ietf-mtgvenue-iaoc-venue-selection-process-08
Abstract Abstract
The IAOC has responsibility for arranging IETF plenary meeting Venue The IAOC 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 its goals, criteria
and thought processes. It points to additional process documents on and thought processes. It points to additional process documents on
the IAOC Web Site that go into further detail and are subject to the IAOC Web Site that go into further detail and are subject to
change with experience. change with experience.
skipping to change at page 1, line 48 skipping to change at page 1, line 35
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 http://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 November 15, 2017. This Internet-Draft will expire on January 25, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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 (http://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 . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Venue Selection Objectives . . . . . . . . . . . . . . . . . 4 2. Venue Selection Objectives . . . . . . . . . . . . . . . . . 3
2.1. Core Values . . . . . . . . . . . . . . . . . . . . . . . 4 2.1. Core Values . . . . . . . . . . . . . . . . . . . . . . . 3
2.2. Venue Selection Non-Objectives . . . . . . . . . . . . . 5 2.2. Venue Selection Non-Objectives . . . . . . . . . . . . . 5
3. Meeting Criteria . . . . . . . . . . . . . . . . . . . . . . 6 3. Meeting Criteria . . . . . . . . . . . . . . . . . . . . . . 5
3.1. Mandatory Criteria . . . . . . . . . . . . . . . . . . . 6 3.1. Mandatory Criteria . . . . . . . . . . . . . . . . . . . 6
3.2. Important Criteria . . . . . . . . . . . . . . . . . . . 6 3.2. Important Criteria . . . . . . . . . . . . . . . . . . . 6
3.3. Other Consideraitons . . . . . . . . . . . . . . . . . . 9 3.3. Other Consideraitons . . . . . . . . . . . . . . . . . . 9
4. Venue Selection Roles . . . . . . . . . . . . . . . . . . . . 10 4. Venue Selection Roles . . . . . . . . . . . . . . . . . . . . 9
4.1. IETF Participants . . . . . . . . . . . . . . . . . . . . 10 4.1. IETF Participants . . . . . . . . . . . . . . . . . . . . 9
4.2. IESG and IETF Chair . . . . . . . . . . . . . . . . . . . 10 4.2. IESG and IETF Chair . . . . . . . . . . . . . . . . . . . 10
4.3. The Internet Society . . . . . . . . . . . . . . . . . . 11 4.3. The Internet Society . . . . . . . . . . . . . . . . . . 10
4.4. IETF Administrative Oversight Committee . . . . . . . . . 11 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 Meeting Committee . . . . . . . . . . . . . . . . . 12 4.7. IAOC Meeting Committee . . . . . . . . . . . . . . . . . 11
5. Venue Selection Steps . . . . . . . . . . . . . . . . . . . . 12 5. Venue Selection Steps . . . . . . . . . . . . . . . . . . . . 11
5.1. Identification . . . . . . . . . . . . . . . . . . . . . 12 5.1. Identification . . . . . . . . . . . . . . . . . . . . . 11
5.2. Consultation . . . . . . . . . . . . . . . . . . . . . . 12 5.2. Consultation . . . . . . . . . . . . . . . . . . . . . . 12
5.3. Qualification . . . . . . . . . . . . . . . . . . . . . . 13 5.3. Qualification . . . . . . . . . . . . . . . . . . . . . . 13
5.4. Negotiation . . . . . . . . . . . . . . . . . . . . . . . 14 5.4. Negotiation . . . . . . . . . . . . . . . . . . . . . . . 13
5.5. Late Changes . . . . . . . . . . . . . . . . . . . . . . 14 5.5. Late Changes . . . . . . . . . . . . . . . . . . . . . . 13
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. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 14
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15
10.1. Normative References . . . . . . . . . . . . . . . . . . 15 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 15
10.2. Informative References . . . . . . . . . . . . . . . . . 15 11.1. Normative References . . . . . . . . . . . . . . . . . . 15
11.2. Informative References . . . . . . . . . . . . . . . . . 16
Appendix A. Site Qualification Visit Checklist . . . . . . . . . 16 Appendix A. Site Qualification Visit Checklist . . . . . . . . . 16
Appendix B. Contingency Planning Flow Chart . . . . . . . . . . 22 Appendix B. Contingency Planning Flow Chart . . . . . . . . . . 22
Appendix C. Change Log . . . . . . . . . . . . . . . . . . . . . 23 Appendix C. Change Log . . . . . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 25 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 25
1. Introduction 1. Introduction
[[ED: The issue tracker for this document can be found at [[ED: The issue tracker for this document can be found at
https://github.com/elear/mtgvenue/issues/.]] https://github.com/elear/mtgvenue/issues/.]]
The IAOC has responsibility for arranging IETF plenary meeting venue The IAOC has responsibility for arranging IETF plenary meeting venue
selection and operation. The purpose of this document is to guide selection and operation. The purpose of this document is to guide
the IAOC in their selection of regions, cities, and facilities, and the IAOC in their selection of regions, cities, and facilities, and
hotels. The IAOC applies this guidance at different points in the hotels. The IAOC applies this guidance at different points in the
process in an attempt to faithfully meet the requirements of the IETF process in an attempt to faithfully meet the requirements of the IETF
community. We specify a set of general criteria for venue selection community. We specify a set of general criteria for venue selection
and several requirements for transparency and community consultation. and several requirements for transparency and community consultation.
It remains the responsibility of the IAOC to apply their best It remains the responsibility of the IASA to apply their best
judgment. The IAOC accepts input and feedback both during the judgment. The IASA accepts input and feedback both during the
consultation process and later (for instance when there are changes consultation process and later (for instance when there are changes
in the situation at a chosen location). Any appeals remain subject in the situation at a chosen location). Any appeals remain subject
to the provisions of BCP101 [RFC4071]. As always, the community is to the provisions of BCP101 [RFC4071]. As always, the community is
encouraged to provide direct feedback to the NOMCOM, IESG, and IAB encouraged to provide direct feedback to the NOMCOM, IESG, and IAB
regarding the discharge of the IAOC's performance. regarding the discharge of the IAOC's performance.
Three terms describe the places for which the IETF contracts Three terms describe the places for which the IETF contracts
services: services:
Venue: Venue:
skipping to change at page 4, line 20 skipping to change at page 4, line 4
applicable to multiple requirements listed in this document. They applicable to multiple requirements listed in this document. They
are not limited to the following, but at minimum include: are not limited to the following, but at minimum include:
Why do we meet? Why do we meet?
We meet to pursue the IETF's mission [RFC3935], partly by We meet to pursue the IETF's mission [RFC3935], partly by
advancing the development of Internet-Drafts and RFCs. We also advancing the development of Internet-Drafts and RFCs. We also
seek to facilitate attendee participation in multiple topics and seek to facilitate attendee participation in multiple topics and
to enable cross-pollination of ideas and technologies. to enable cross-pollination of ideas and technologies.
Inclusiveness: Inclusiveness:
We would like to facilitate the onsite or remote participation of We would like to facilitate the onsite or remote participation of
anyone who wants to be involved. anyone who wants to be involved.
Every country has limits on who it will permit within its borders. Every country has limits on who it will permit within its borders.
However the IETF seeks to: However the IETF seeks to:
1. Minimize situations in which onerous entry regulations prevent 1. Minimize situations in which onerous entry regulations
participants from attending meetings, or failing that to inhibit, discourage, or prevent participants from attending
distribute meeting locations such that onerous entry meetings, or failing that to distribute meeting locations such
regulations are not always experienced by the same attendees that onerous entry regulations are not always experienced by
the same attendees; and
2. Avoid meeting in countries with laws that effectively exclude 2. Avoid meeting in countries with laws that effectively exclude
people on the basis of race, religion, gender, sexual people on the basis of race, religion, gender, sexual
orientation, national origin, or gender identity orientation, national origin, or gender identity.
Where do we meet? Where do we meet?
We meet in different locations globally, in order to spread the We meet in different locations globally, in order to spread the
difficulty and cost of travel among active participants, balancing difficulty and cost of travel among active participants, balancing
travel time and expense across the regions in which IETF travel time and expense across the regions in which IETF
participants are based. participants are based.
Internet Access: Internet Access:
As an organization, we write specifications for the Internet, and As an organization, we write specifications for the Internet, and
we use it heavily. Meeting attendees need unfiltered access to we use it heavily. Meeting attendees need unfiltered access to
skipping to change at page 7, line 5 skipping to change at page 6, line 37
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 more preferable than another that meets less criteria is on the whole more preferable than another that meets less
of these criteria. Requirements classed as Important can also be of 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 IAOC MUST particular requirement in this section cannot be met, the IAOC MUST
notify the community at the time the venue is booked. Furthermore, notify the community at the time the venue is booked. Furthermore,
the IAOC is requested to assist those who, as a result, may be the IAOC is requested to assist those who, as a result, may be
inconvenienced in some way. inconvenienced in some way.
3.2.1. Venue City Critera 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 and at a price
that it is possible and probable to find a host and sponsors. that it is possible and probable to find a host and sponsors.
o Travel barriers to entry, including visa requirements, are o Travel barriers to entry, including visa requirements, are likely
unlikely to impede attendance by an overwhelming majority of to be such that an overwhelming majority of participants can
participants. attend. The term "travel barriers" is to be read broadly by the
IASA in the context of whether a successful meeting 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.
3.2.2. Basic Venue Criteria 3.2.2. Basic Venue Criteria
The following requirements relate to the Venue and Facilities. The following requirements relate to the Venue and Facilities.
The IETF operates internationally and adjusts to local requirements. The IETF operates internationally and adjusts to local requirements.
Facilities selected for IETF Meetings conform with local health, Facilities selected for IETF Meetings conform with local health,
safety and accessibility laws and regulations. A useful discussion safety and accessibility laws and regulations. A useful discussion
of related considerations in evaluating this criterion is at: of related considerations in evaluating this criterion is at:
<http://www.sigaccess.org/welcome-to-sigaccess/resources/accessible- <http://www.sigaccess.org/welcome-to-sigaccess/resources/accessible-
conference-guide/> conference-guide/>
*** Editor's Note ***
In the spirit of the 'international' focus, we need a
comprehensive document that is similar to the one cited, but
without a national focus. The current reference is US-
specific. /d
In addition: In addition:
o There are sufficient places (e.g., a mix of hallways, bars, o There are sufficient places (e.g., a mix of hallways, bars,
meeting rooms, and restaurants) for people to hold ad hoc meeting rooms, and restaurants) for people to hold ad hoc
conversations and group discussions in the combination of spaces conversations and group discussions in the combination of spaces
offered by the facilities, hotels and bars/restaurants in the offered by the facilities, hotels and bars/restaurants in the
surrounding area, within walking distance (5-10'). surrounding area, within walking distance (5-10').
o The cost of guest rooms, meeting space, meeting food and beverage o The cost of guest rooms, meeting space, meeting food and beverage
is affordable, within the norms of business travel. is affordable, within the norms of business travel.
skipping to change at page 10, line 36 skipping to change at page 10, line 12
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 contribute to new RFCs. Potential new those who do not attend but contribute to new RFCs. Potential new
contributors are also considered in the process. contributors are also considered in the process.
Participants have a responsibility to express their views about Participants have a responsibility to express their views about
venues early and often, by responding to surveys or other venues early and often, by responding to surveys or other
solicitations from the IAD or IAOC, and by initiating fresh input as solicitations from the IAD or IAOC, and by initiating fresh input as
the Participant becomes aware of changes in venues that have been the Participant becomes aware of changes in venues that have been
reviews. This permits those responsible for venue selection to be reviewed. This permits those responsible for venue selection to be
made aware of concerns relating to particular locations well in made aware of concerns relating to particular locations well in
advance of having entered into contract discussions. advance of having entered into contract discussions.
4.2. IESG and IETF Chair 4.2. IESG and IETF Chair
The Internet Engineering Steering Group (IESG) comprises the IETF The Internet Engineering Steering Group (IESG) comprises the IETF
Area Directors and the IETF Chair. Along with the IAB, the IESG is Area Directors and the IETF Chair. Along with the IAB, the IESG is
responsible for the management of the IETF, and is the standards responsible for the management of the IETF, and is the standards
approval board for the IETF, as described in BCP9 [RFC2026]. This approval board for the IETF, as described in BCP9 [RFC2026]. This
means that the IESG sets high level policies related to, among other means that the IESG sets high level policies related to, among other
skipping to change at page 11, line 28 skipping to change at page 10, line 50
ISOC also provides accounting services, such as invoicing and monthly ISOC also provides accounting services, such as invoicing and monthly
financial statements. 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 to work with the Internet Society to write the instructs the IAD to work with the Internet Society to write the
relevant contracts. It approves the IETF meetings calendar. In relevant contracts. It approves the IETF meetings calendar. In
cooperation with the IAD, the IAOC takes necessary actions to ensure cooperation with the IAD, the IAOC takes necessary actions to ensure
that it is aware of participant concerns about particular venues as that the IASA is aware of participant concerns about particular
early in the process as is feasible. 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) supports the meeting The IETF Administrative Support Activity (IASA) performs the meeting
selection process. This includes identifying, qualifying and selection process under the oversight of the IAOC. This includes
reporting on potential meeting sites, as well as supporting meeting identifying, qualifying and reporting on potential meeting sites, as
Venue contract negotiation. The IETF Secretariat is part of the IASA well as supporting meeting Venue contract negotiation. The IETF
under the management of the IAD. The IAD takes appropriate actions Secretariat is part of the IASA under the management of the IAD. The
to solicit community input regarding both retrospective and IAD takes appropriate actions to solicit community input regarding
prospective feedback from participants. 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 IAOC to ensure the timely execution of the meeting process. This the IAOC to ensure the timely execution of the meeting process. This
includes participating in the IAOC Meeting Subcommittee and ensuring includes participating in the IAOC Meeting Subcommittee and ensuring
its efforts are documented, leading Venue contract negotiation, and its efforts are documented, leading Venue contract negotiation, and
coordinating contract execution with ISOC. The meetings budget is coordinating contract execution with ISOC. The meetings budget is
managed by the IAD. managed by the IAD.
skipping to change at page 14, line 28 skipping to change at page 13, line 47
and requests IAOC and ISOC approval of contract and authority for and requests IAOC and ISOC approval of contract and authority for
Secretariat to execute contract on ISOC's behalf. Secretariat to execute contract on ISOC's behalf.
d. Contracts are executed. d. Contracts are executed.
e. The venue is announced. At this time, the announcement MUST e. The venue is announced. At this time, the announcement MUST
include any notable travel risks or references thereto. include any notable travel risks or references thereto.
5.5. Late Changes 5.5. Late Changes
If at any time after a contract is signed the IAOC learns where a If at any time after a contract is signed the IAOC learns
Venue's circumstances have significantly changed, such that the circumstances have changed such that it is not certain that Important
Important or Mandatory criteria can no longer be met, the IAOC MUST or Mandatory criteria can be met by a Venue, the IAOC MUST reconsider
reconsider the selection. A description of how reconsideration the selection. A description of how reconsideration currently takes
currently takes place is found in Appendix B. The IAOC will gauge place is found in Appendix B. The IAOC will gauge the cost of making
the cost of making a change against the ability of the IETF to a change against the ability of the IETF to conclude a successful
conclude a successful meeting, and make a final determination based meeting, and make a final determination based on their best judgment.
on their best judgment. When there is enough time to do so, the IAOC When there is enough time to do so, the IAOC is expected to consult
is expected to consult the community about changes. the community about changes.
6. IANA Considerations 6. IANA Considerations
This memo asks the IANA for no new parameters. This memo asks the IANA for no new parameters.
[The RFC-Editor may remove this section prior to publicaiton.]
7. Security Considerations 7. Security Considerations
This note proposes no protocols, and therefore no new protocol This note proposes no protocols, and therefore no new protocol
insecurities. insecurities.
8. Privacy Considerations 8. Privacy Considerations
This note reveals no personally identifying information apart from This note reveals no personally identifying information apart from
its authorship. its authorship.
9. Acknowledgements [The RFC-Editor may remove this section prior to publicaiton.]
This document was originally assembled and edited by Fred Baker. 9. Contributors
Additional commentary came from Jari Arkko, Scott Bradner, Alissa
Cooper, and other participants in the MtgVenue working group.
10. References The following people provided substantial text contributions to this
memo:
10.1. Normative References Fred Baker
Email: fred.ietf@gmail.com
Fred originated this work.
Ray Pelletier
Internet Society
Email: rpelletier@isoc.org
Laura Nugent
Association Management Solutions
Email: lnugent@amsl.com
Lou Berger
LabN Consulting, L.L.C.
Email: lberger@labn.net
Ole Jacobsen
The Internet Protocol Journal
EMail: olejacobsen@me.com
Jim Martin
INOC
Email: jim@inoc.com
10. Acknowledgements
Additional contributions came from Jari Arkko, Scott Bradner, Alissa
Cooper, Dave Crocker, Jordi Palet Martinez, Andrew Sullivan, and
other participants in the mtgvenue working group. Those listed in
this section or as contributors may or may not agree with the content
of this memo.
11. References
11.1. Normative References
[MeetingNet] [MeetingNet]
O'Donoghue, K., Martin, J., Elliott, C., and J. Jaeggli, O'Donoghue, K., Martin, J., Elliott, C., and J. Jaeggli,
"IETF Meeting Network Requirements", WEB "IETF Meeting Network Requirements", WEB
https://iaoc.ietf.org/ietf-network-requirements.html. 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>.
skipping to change at page 15, line 43 skipping to change at page 16, line 5
[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>.
10.2. Informative References 11.2. Informative References
[I-D.barnes-healthy-food] [I-D.barnes-healthy-food]
Barnes, M., "Healthy Food and Special Dietary Requirements Barnes, M., "Healthy Food and Special Dietary Requirements
for IETF meetings", draft-barnes-healthy-food-07 (work in for IETF meetings", draft-barnes-healthy-food-07 (work in
progress), July 2013. progress), July 2013.
[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. Site Qualification Visit Checklist Appendix A. Site Qualification Visit Checklist
skipping to change at page 25, line 15 skipping to change at page 25, line 15
diff. diff.
2017-05-14 Happy Mother's Day. This version removes the tabular 2017-05-14 Happy Mother's Day. This version removes the tabular
format of requirements, moves mandatory requirements up front, format of requirements, moves mandatory requirements up front,
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.
Authors' Addresses Author's Address
Ray Pelletier
Internet Society
Email: rpelletier@isoc.org
Laura Nugent
Association Management Solutions
Email: lnugent@amsl.com
Dave Crocker (editor)
Brandenburg InternetWorking
Email: dcrocker@bbiw.net
Lou Berger
LabN Consulting, L.L.C.
Email: lberger@labn.net
Ole Jacobsen
The Internet Protocol Journal
Email: olejacobsen@me.com
Jim Martin
INOC
Email: jim@inoc.com
Fred Baker (editor)
Email: FredBaker.IETF@gmail.com
Eliot Lear (editor) Eliot Lear (editor)
Cisco Systems GmbH Cisco Systems GmbH
Email: lear@cisco.com Email: lear@cisco.com
 End of changes. 29 change blocks. 
114 lines changed or deleted 101 lines changed or added

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