draft-ietf-shmoo-cancel-meeting-05.txt   draft-ietf-shmoo-cancel-meeting-06.txt 
shmoo M. Duke shmoo M. Duke
Internet-Draft F5 Networks, Inc. Internet-Draft F5 Networks, Inc.
Intended status: Best Current Practice 24 June 2021 Intended status: Best Current Practice 9 August 2021
Expires: 26 December 2021 Expires: 10 February 2022
Considerations for Cancellation of IETF Meetings Considerations for Cancellation of IETF Meetings
draft-ietf-shmoo-cancel-meeting-05 draft-ietf-shmoo-cancel-meeting-06
Abstract Abstract
The IETF holds three in-person meetings per year to discuss and The IETF ordinarily holds three in-person meetings per year to
understand issues. However, various emergencies can make a planned discuss issues and advance the Internet. However, various
in-person meeting infeasible. This document provides criteria for emergencies can make a planned in-person meeting infeasible. This
making this judgment. document provides criteria to aid the IETF Administration LLC (LLC),
Internet Engineering Steering Group (IESG), and Internet Research
Task Force (IRTF) Chair in deciding to postpone, move, or cancel an
in-person IETF meeting.
Discussion Venues Discussion Venues
This note is to be removed before publishing as an RFC. This note is to be removed before publishing as an RFC.
Discussion of this document takes place on the mailing list Discussion of this document takes place on the mailing list
(shmoo@ietf.org), which is archived at (shmoo@ietf.org), which is archived at
https://mailarchive.ietf.org/arch/browse/shmoo/. https://mailarchive.ietf.org/arch/browse/shmoo/.
Source for this draft and an issue tracker can be found at Source for this draft and an issue tracker can be found at
skipping to change at page 1, line 44 skipping to change at page 1, line 47
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 https://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 26 December 2021. This Internet-Draft will expire on 10 February 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2021 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 (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 2, line 24 skipping to change at page 2, line 29
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Decision Criteria and Roles . . . . . . . . . . . . . . . . . 3 3. Decision Criteria and Roles . . . . . . . . . . . . . . . . . 3
3.1. IETF LLC . . . . . . . . . . . . . . . . . . . . . . . . 4 3.1. IETF LLC . . . . . . . . . . . . . . . . . . . . . . . . 4
3.2. IESG and IRTF Chair . . . . . . . . . . . . . . . . . . . 5 3.2. IESG and IRTF Chair . . . . . . . . . . . . . . . . . . . 5
4. Remedies . . . . . . . . . . . . . . . . . . . . . . . . . . 6 4. Remedies . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.1. Relocation . . . . . . . . . . . . . . . . . . . . . . . 6 4.1. Relocation . . . . . . . . . . . . . . . . . . . . . . . 6
4.2. Virtualization . . . . . . . . . . . . . . . . . . . . . 6 4.2. Virtualization . . . . . . . . . . . . . . . . . . . . . 6
4.3. Postponement . . . . . . . . . . . . . . . . . . . . . . 6 4.3. Postponement . . . . . . . . . . . . . . . . . . . . . . 7
4.4. Cancellation . . . . . . . . . . . . . . . . . . . . . . 7 4.4. Cancellation . . . . . . . . . . . . . . . . . . . . . . 7
5. Refunds . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 5. Refunds . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
6. Security Considerations . . . . . . . . . . . . . . . . . . . 8 6. Security Considerations . . . . . . . . . . . . . . . . . . . 8
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
8. Normative References . . . . . . . . . . . . . . . . . . . . 8 8. Normative References . . . . . . . . . . . . . . . . . . . . 8
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 8 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 9
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 8 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 9
B.1. Since draft-ietf-shmoo-cancel-meetings-03 . . . . . . . . 8 B.1. Since draft-ietf-shmoo-cancel-meetings-05 . . . . . . . . 9
B.2. Since draft-ietf-shmoo-cancel-meetings-02 . . . . . . . . 8 B.2. Since draft-ietf-shmoo-cancel-meetings-04 . . . . . . . . 9
B.3. Since draft-ietf-shmoo-cancel-meetings-01 . . . . . . . . 8 B.3. Since draft-ietf-shmoo-cancel-meetings-03 . . . . . . . . 9
B.4. Since draft-ietf-shmoo-cancel-meetings-00 . . . . . . . . 9 B.4. Since draft-ietf-shmoo-cancel-meetings-02 . . . . . . . . 9
B.5. Since draft-duke-shmoo-cancel-meetings-01 . . . . . . . . 9 B.5. Since draft-ietf-shmoo-cancel-meetings-01 . . . . . . . . 9
B.6. Since draft-duke-shmoo-cancel-meetings-00 . . . . . . . . 9 B.6. Since draft-ietf-shmoo-cancel-meetings-00 . . . . . . . . 9
B.7. Since draft-duke-remote-meetings-00 . . . . . . . . . . . 9 B.7. Since draft-duke-shmoo-cancel-meetings-01 . . . . . . . . 9
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 9 B.8. Since draft-duke-shmoo-cancel-meetings-00 . . . . . . . . 10
B.9. Since draft-duke-remote-meetings-00 . . . . . . . . . . . 10
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
Among the highlights of the IETF calendar are in-person general Among the highlights of the IETF calendar are in-person general
meetings, which happen three times a year at various locations around meetings, which happen three times a year at various locations around
the world. the world.
Various major events may affect the suitability of a scheduled in- Various major events may affect the suitability of a scheduled in-
person IETF meeting, though for some this may not be immediately person IETF meeting, though for some events this may not be
obvious. For example: immediately obvious. For example:
* A meeting venue itself may unexpectedly close or otherwise be * A meeting venue itself may unexpectedly close or otherwise be
unable to meet IETF meeting requirements due to a health issue, unable to meet IETF meeting requirements due to a health issue,
legal violation, or other localized problem. legal violation, or other localized problem.
* A natural disaster could degrade the travel and meeting * A natural disaster could degrade the travel and meeting
infrastructure in a planned location and make it unethical to infrastructure in a planned location and make it unethical to
further burden that infrastructure with a meeting. further burden that infrastructure with a meeting.
* War, civil unrest, or public health crisis could make a meeting * War, civil unrest, or public health crisis could make a meeting
unsafe and/or result in widespread national or corporate travel unsafe and/or result in widespread national or corporate travel
bans. bans.
* An economic crisis could sharply reduce resources available for * An economic crisis could sharply reduce resources available for
travel. travel, resulting in lower expected attendance.
* Changes in visa policy or other unexpected governmental * Changes in visa policy or other unexpected governmental
restrictions might make the venue inaccessible to numerous restrictions might make the venue inaccessible to numerous
attendees. attendees.
This document provides criteria to aid the IETF Administration LLC This document provides criteria to aid the IETF Administration LLC
(LLC) in deciding to postpone, move, or cancel an in-person IETF (LLC), Internet Engineering Steering Group (IESG), and Internet
meeting. Research Task Force (IRTF) Chair in deciding to postpone, move, or
cancel an in-person IETF meeting.
2. Conventions 2. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
In this document, the term "venue" refers to both the facility that In this document, the term "venue" refers to both the facility that
houses the sessions and the official meeting hotel(s). houses the sessions and the official meeting hotel(s), as defined in
[RFC8718].
3. Decision Criteria and Roles 3. Decision Criteria and Roles
The LLC assesses whether an in-person meeting is logistically and The LLC assesses whether an in-person meeting is logistically and
financially viable in light of events, and assembles information financially viable in light of events, and assembles information
about various travel restrictions that might impact attendance. The about various travel restrictions that might impact attendance. The
Internet Engineering Steering Group (IESG) and Internet Research Task Internet Engineering Steering Group (IESG) and Internet Research Task
Force (IRTF) Chair assess if the projected attendance is sufficient Force (IRTF) Chair assess if the projected attendance is sufficient
for a viable in-person meeting. for a viable in-person meeting.
skipping to change at page 4, line 17 skipping to change at page 4, line 17
The LLC is responsible for assessing the suitability of a venue for The LLC is responsible for assessing the suitability of a venue for
an IETF meeting and is responsible for any reassessment in response an IETF meeting and is responsible for any reassessment in response
to a major event that leaves the prior conclusion in doubt. If such to a major event that leaves the prior conclusion in doubt. If such
an event occurs more than fourteen weeks before the start of the an event occurs more than fourteen weeks before the start of the
scheduled meeting, it is deemed a non-emergency situation. Later scheduled meeting, it is deemed a non-emergency situation. Later
events, up to and including the week of a meeting itself, are deemed events, up to and including the week of a meeting itself, are deemed
an emergency situation. an emergency situation.
In non-emergency situations, if the LLC determines the scheduled In non-emergency situations, if the LLC determines the scheduled
meeting clearly cannot proceed (e.g., the venue has permanently meeting clearly cannot proceed (e.g., the venue has permanently
closed), then it MUST consult with the community on the reason(s) and closed), then it MUST share the reason(s) with the community and MUST
its proposed remedy. In less clear cases, the LLC SHOULD conduct a consult on its proposed remedy. In less clear cases, the LLC SHOULD
formal reassessment process that includes: conduct a formal reassessment process that includes:
* Consulting with the community on the process timetable. * Consulting with the community on the timetable of the decision
process.
* Consulting with the community on criteria to assess the impact of * Consulting with the community on criteria to assess the impact of
new developments. new developments.
* Consulting with the community on the form of the assessment
report.
* Publishing an assessment report and recommended remedy. * Publishing an assessment report and recommended remedy.
* Seeking approval of the IESG for the recommendation. * Seeking approval of the IESG and IRTF Chair for the
recommendation.
In emergency situations, which lack the time for a consultation In emergency situations, which lack the time for a consultation
process, this document provides criteria that have IETF consensus and process, this document provides criteria that have IETF consensus and
which the LLC MUST apply in its assessment. which the LLC MUST apply in its assessment.
The LLC will collect information about the likely impact to in-person The LLC will collect information about the likely impact to in-person
attendance of national travel advisories, national and corporate attendance of national travel advisories, national and corporate
travel bans, quarantine requirements, etc. and report the results to travel bans, availability of transportation, quarantine requirements,
the IESG. etc. and report the results to the IESG and IRTF Chair.
These criteria, some of which are derived from Section 3 of These criteria, some of which are derived from Section 3 of
[RFC8718], apply to venues that are re-evaluated due to an emergency: [RFC8718], apply to venues that are re-evaluated due to an emergency:
* Local safety guidelines allow the venue and hotels to host a * Local safety guidelines allow the venue and hotels to host a
meeting with the expected number of participants and staff. meeting with the expected number of participants and staff.
* It MUST be possible to provision Internet Access to the Facility * It is possible to provision Internet access to the venue that
and IETF Hotels that allows those attending in person to utilize allows those attending in person to utilize the Internet for all
the Internet for all their IETF, business, and day-to-day needs; their IETF, business, and day-to-day needs; in addition, there
in addition, there must be sufficient bandwidth and access for must be sufficient bandwidth and access for remote attendees.
remote attendees. Provisions include, but are not limited to, Provisions include, but are not limited to, native and unmodified
native and unmodified IPv4 and IPv6 connectivity, and global IPv4 and IPv6 connectivity, and global reachability; there may be
reachability; there may be no additional limitation that would no additional limitation that would materially impact their
materially impact their Internet use. To ensure availability, it Internet use. To ensure availability, it MUST be possible to
MUST be possible to provision redundant paths to the Internet. provision redundant paths to the Internet.
* A reasonable number of food and drink establishments are open and * A reasonable number of food and drink establishments are open and
available within walking distance to provide for the expected available within walking distance to provide for the expected
number of participants and staff. number of participants and staff.
* Local health and public safety infrastructure should expect to * Local health and public safety infrastructure expects to have
have adequate capacity to support an influx of visitors during the adequate capacity to support an influx of visitors during the
meeting week. meeting week.
Finally, the LLC MUST assess the impact on its own operations, Finally, the LLC MUST assess the impact on its own operations,
including: including:
* The number of critical support staff and contractors who can be at * The number of critical support staff, contractors, and volunteers
the venue. who can be at the venue.
* The financial impact of continuing a meeting, or implementing any * The financial impact of continuing a meeting, or implementing any
of the possible remedies. of the possible remedies.
The LLC SHOULD cancel a meeting if it judges a meeting to be The LLC SHOULD cancel an in-person meeting and explore potential
logistically impossible or inconsistent with its fiduciary remedies if it judges a meeting to be logistically impossible or
responsibilities. inconsistent with its fiduciary responsibilities.
In the event of considerations this document does not foresee, the In the event of considerations this document does not foresee, the
LLC should protect the health and safety of attendees and staff, as LLC should protect the health and safety of attendees and staff, as
well as the fiscal health of the organization, with approval from the well as the fiscal health of the organization, with approval from the
IESG and a plan to seek a later update of this document. IESG and IRTF Chair. The IESG should pursue a later update of this
document.
3.2. IESG and IRTF Chair 3.2. IESG and IRTF Chair
If the LLC assesses there are no fundamental logistical or financial If the LLC assesses there are no fundamental logistical or financial
obstacles to holding a meeting in an emergency situation, the IESG obstacles to holding a meeting in an emergency situation, the IESG
and IRTF Chair assess if projected attendance is high enough to and IRTF Chair assess if projected attendance is high enough to
achieve the benefit of an in-person meeting. achieve the benefit of an in-person meeting. The IESG and IRTF Chair
SHOULD cancel the in-person meeting if that benefit is insufficient.
The IESG is discouraged from relying on a simple head count of The IESG and IRTF Chair are discouraged from relying on a simple head
expected meeting attendance. Even dramatically smaller meetings with count of expected meeting attendance. Even dramatically smaller
large remote participation may be successful. In addition to the meetings with large remote participation may be successful. In
LLC's estimate, the IESG might consider: addition to the LLC's estimate, the IESG and IRTF Chair might
consider:
* Are many working groups and research groups largely unaffected by * Are many working groups and research groups largely unaffected by
the restrictions, so that they can operate effectively? the restrictions, so that they can operate effectively?
* Is there a critical mass of key personnel at most working group * Is there a critical mass of key personnel at most working group
meetings to leverage the advantages of in-person meetings, even if meetings to leverage the advantages of in-person meetings, even if
many participants are remote? many participants are remote?
4. Remedies 4. Remedies
If a meeting cannot be held at the scheduled time and place, the LLC If a meeting cannot be held at the scheduled time and place, the LLC,
and IESG have several options. The remedies in this section should IESG, and IRTF Chair have several options. The remedies in this
be considered in light of four principles, presented in no particular section should be considered in light of four principles, presented
order: in no particular order:
* Hold the scheduled sessions of a meeting in some format. * Hold the scheduled sessions of a meeting in some format.
* Provide benefits of in-person interactions when possible. * Provide benefits of in-person interactions when possible.
* Avoid exorbitant additional travel expenses due to last minute * Avoid exorbitant additional travel expenses due to last minute
flight changes, etc. flight changes, etc.
* Ensure the available time and resources allow the alternative to * Ensure sufficient time and resources to adequately prepare an
be adequately prepared. alternative.
The following remedies are listed in approximate declining order of
preference.
4.1. Relocation 4.1. Relocation
For attendees, the least disruptive response is to retain the meeting For attendees, the least disruptive response is to retain the meeting
week but move it to a more accessible venue. To the maximum extent week but move it to a more accessible venue. To the maximum extent
possible, this will be geographically close to the original venue. possible, this will be geographically close to the original venue.
In particular, the LLC SHOULD strive to meet the criteria in In particular, the LLC SHOULD meet the criteria in [RFC8718] and
[RFC8718] and [RFC8719]. [RFC8719].
Relocation that requires new air travel arrangements for attendees Relocation that requires new air travel arrangements for attendees
SHOULD NOT occur less than one month prior to the start of the SHOULD NOT occur less than one month prior to the start of the
meeting. meeting.
4.2. Virtualization 4.2. Virtualization
The second option, and one that has fewer issues with venue The second option, and one that has fewer issues with venue
availability, is to make a meeting fully remote. This requires availability, is to make a meeting fully online. This requires
different IETF processes and logistical operations that are outside different IETF processes and logistical operations that are outside
the scope of this document. the scope of this document.
4.3. Postponement 4.3. Postponement
Although it is more disruptive to the schedules of participants, the Although it is more disruptive to the schedules of participants, the
next best option is to delay a meeting until a specific date, at the next best option is to delay a meeting until a specific date, at the
same venue, at which conditions are expected to improve. The new end same venue, at which conditions are expected to improve. The new end
date of a meeting must be at least 30 days before the beginning of date of a meeting must be at least 30 days before the beginning of
the following IETF meeting, and a meeting must begin no earlier than the following IETF meeting, and a meeting MUST begin no earlier than
1 month after the postponement announcement. 30 days after the postponement announcement.
Due to scheduling constraints at the venue, this will usually not be Due to scheduling constraints at the venue, this will usually not be
feasible. However, it is more likely to allow attendees to recover feasible. However, it is more likely to allow attendees to recover
at least some of their travel expenses than other options. at least some of their travel expenses than other options.
Note that it is possible to both postpone and relocate a meeting, Note that it is possible to both postpone and relocate a meeting,
though this has the disadvantages of both. though this has the disadvantages of both.
4.4. Cancellation 4.4. Cancellation
The LLC and IESG may cancel a meeting entirely in the event that The LLC, IESG, and IRTF Chair may cancel a meeting entirely in the
worldwide conditions make it difficult for attendees to even attend event that worldwide conditions make it difficult for attendees to
remotely. Not holding a meeting at all can have wide implications, even attend online. Not holding a meeting at all can have wide
such as the nomination process and seating of new officers. implications, such as effects on the nomination process and seating
of new officers.
Cancellation is likely the only practical alternative when Cancellation is likely the only practical alternative when
emergencies occur immediately before or during a meeting, so that emergencies occur immediately before or during a meeting, so that
there is no opportunity to make other arrangements. there is no opportunity to make other arrangements.
5. Refunds 5. Refunds
The IETF SHOULD NOT reimburse registered attendees for unrecoverable The IETF SHOULD NOT reimburse registered attendees for unrecoverable
travel expenses (airfare, hotel deposits, etc). travel expenses (airfare, hotel deposits, etc).
skipping to change at page 7, line 39 skipping to change at page 8, line 5
registration fees is appropriate: registration fees is appropriate:
* Cancellation SHOULD result in a full refund to all participants. * Cancellation SHOULD result in a full refund to all participants.
It MAY be prorated if some portion of the sessions completed It MAY be prorated if some portion of the sessions completed
without incident. without incident.
* Upon postponement, the LLC SHOULD offer refunds to registered * Upon postponement, the LLC SHOULD offer refunds to registered
attendees who claim they cannot attend at the newly scheduled attendees who claim they cannot attend at the newly scheduled
time. Attendees can opt out of receiving a refund. time. Attendees can opt out of receiving a refund.
* When a meeting becomes remote, the LLC MUST refund registered * When a meeting is virtualized, the LLC MUST offer to refund
attendees the difference between their paid registration fee and registered attendees the difference between their paid
the equivalent fee for a remote meeting. The LLC SHOULD offer registration fee and the equivalent fee for an online meeting.
refunds to registered attendees who do not wish to attend a remote The LLC SHOULD offer refunds to registered attendees who do not
meeting. wish to attend an online meeting.
* The LLC SHOULD offer refunds to attendees whose nation of * The LLC SHOULD offer refunds to attendees whose government
residence forbids, or has issued a safety advisory against, visits forbids, or has issued a safety advisory against, visits to the
to the host venue, even if the in-person meeting will continue. host venue, even if the in-person meeting will continue. It
It SHOULD NOT refund cancellations due to employer policy or SHOULD NOT refund cancellations due to employer policy or personal
personal risk assessments. risk assessments.
These provisions intend to maintain trust between the IETF and its These provisions intend to maintain trust between the IETF and its
participants. However, under extraordinary threats to the solvency participants. However, under extraordinary threats to the solvency
of the organization, the LLC may suspend them. of the organization, the LLC may suspend them.
6. Security Considerations 6. Security Considerations
This document introduces no new concerns for the security of internet This document introduces no new concerns for the security of Internet
protocols. protocols.
7. IANA Considerations 7. IANA Considerations
There are no IANA requirements. There are no IANA requirements.
8. Normative References 8. Normative References
[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, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/rfc/rfc2119>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/rfc/rfc8174>.
[RFC8718] Lear, E., Ed., "IETF Plenary Meeting Venue Selection [RFC8718] Lear, E., Ed., "IETF Plenary Meeting Venue Selection
Process", BCP 226, RFC 8718, DOI 10.17487/RFC8718, Process", BCP 226, RFC 8718, DOI 10.17487/RFC8718,
February 2020, <https://www.rfc-editor.org/info/rfc8718>. February 2020, <https://www.rfc-editor.org/rfc/rfc8718>.
[RFC8719] Krishnan, S., "High-Level Guidance for the Meeting Policy [RFC8719] Krishnan, S., "High-Level Guidance for the Meeting Policy
of the IETF", BCP 226, RFC 8719, DOI 10.17487/RFC8719, of the IETF", BCP 226, RFC 8719, DOI 10.17487/RFC8719,
February 2020, <https://www.rfc-editor.org/info/rfc8719>. February 2020, <https://www.rfc-editor.org/rfc/rfc8719>.
Appendix A. Acknowledgments Appendix A. Acknowledgments
Jay Daley provided extensive input to make this document more usable
by the LLC. Many members of the IESG and the SHMOO working group
also provided useful comments.
Appendix B. Change Log Appendix B. Change Log
B.1. Since draft-ietf-shmoo-cancel-meetings-03 B.1. Since draft-ietf-shmoo-cancel-meetings-05
* Minor changes from IETF review
B.2. Since draft-ietf-shmoo-cancel-meetings-04
* Threshold for "emergency" changes to 14 weeks
* Clarified refund policy
* IETF Last Call nits
B.3. Since draft-ietf-shmoo-cancel-meetings-03
* Clarifications from AD review * Clarifications from AD review
B.2. Since draft-ietf-shmoo-cancel-meetings-02 B.4. Since draft-ietf-shmoo-cancel-meetings-02
* Added IRTF to IESG responsibilities * Added IRTF to IESG responsibilities
* WGLC Nits * WGLC Nits
B.3. Since draft-ietf-shmoo-cancel-meetings-01 B.5. Since draft-ietf-shmoo-cancel-meetings-01
* Added refund principles for hybrid meetings * Added refund principles for hybrid meetings
B.4. Since draft-ietf-shmoo-cancel-meetings-00 B.6. Since draft-ietf-shmoo-cancel-meetings-00
* Jay Daley's nits * Jay Daley's nits
* Distinguish the emergency and non-emergency process * Distinguish the emergency and non-emergency process
* Eliminated USSTATE/UKFO references * Eliminated USSTATE/UKFO references
* Clarified roles of LLC and IESG * Clarified roles of LLC and IESG
B.5. Since draft-duke-shmoo-cancel-meetings-01 B.7. Since draft-duke-shmoo-cancel-meetings-01
* Change to WG draft * Change to WG draft
B.6. Since draft-duke-shmoo-cancel-meetings-00 B.8. Since draft-duke-shmoo-cancel-meetings-00
* Added mention of IRTF * Added mention of IRTF
* Discussed consensus on cancellation * Discussed consensus on cancellation
B.7. Since draft-duke-remote-meetings-00 B.9. Since draft-duke-remote-meetings-00
* Defined "venue" * Defined "venue"
* Added principles for selecting remedies and rewrote alternatives. * Added principles for selecting remedies and rewrote alternatives.
* Added local authority travel advisories * Added local authority travel advisories
* Added some criteria from IETF 109 * Added some criteria from IETF 109
Author's Address Author's Address
 End of changes. 43 change blocks. 
94 lines changed or deleted 124 lines changed or added

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