Choosing IETF Meeting Venues IAOC and IAOC Meeting Committee.

Slides:



Advertisements
Similar presentations
IETF Calsify.
Advertisements

Whos who in the IETF Zoo? Geoff Huston Executive Director, Internet Architecture Board.
A Proposal to Improve IETF Productivity Geoff Huston Marshall Rose draft-huston-ietf-pact-00 October 2002.
European Network on Roma Community and Social Inclusion Proposal for the Operational and Organisational Structure Sevilla, 24 & 25 January 2008.
Organizing a Site Visit Here Christine King Director, Research Development Services OVPR January 18, 2012.
SNMP (Simple Network Management Protocol) Overview Draft Version.
State Plan for Independent Living UPDATE Overview, Impact and Involvement.
Russ Housley IETF Chair 23 July 2012 Introduction to the IETF Standards Process.
Cairo 2 November Agenda  Guidebook overview  Supporting and explanatory materials  Guidebook Module detail  Probable timelines 2.
- Internet Endowment - ISOC’s 20 th Anniversary: Global INET 2012, Internet Hall of Fame, Internet Wishing Tree, etc. - Jonathan.
Organizing successful Meetings by Chapters Dr. Jacob Baal-Schem
Office of Information Technology (OIT) PROJECT INITIATION DOCUMENTS - BUSINESS CASE, ALTERNATIVE ANALYSIS AND STATEMENT OF WORK (SOW)
Housing and the European World Health Organisation Healthy City Programme By Dave Leonard WHO Co-ordinator Sunderland.
IAOC Operations Report Jonne Soininen, Chair Ray Pelletier, IAD 25 March 2009 San Francisco, California, USA ® 1.
IAOC and IAD Report IETF87 Bob Hinden IAOC Chair Ray Pelletier IAD 31 July 2013.
IAOC Report IETF78 Bob Hinden IAOC Chair Ray Pelletier IAD 28 July 2010.
IETF 73, 19 November, 2008, Minneapolis, USA1 Internet Architecture Board Update Olaf M. Kolkman IAB Chair.
IAOC and IAD Report IETF84 Bob Hinden IAOC Chair Ray Pelletier IAD 1 August 2012.
IAOC Report Bob Hinden IAOC Chair Ray Pelletier IAD 16 November 2011.
Emergency Context Resolution with Internet Technologies (ecrit) IETF 76, Hiroshima Nov 11, 2009 Hannes Tschofenig Marc Linsner (attending virtually) Roger.
IAOC and IAD Report IETF85 Bob Hinden IAOC Chair Ray Pelletier IAD 7 November 2012.
Center for Risk Management of Engineering Systems University of Virginia, Charlottesville 1 Process Development and Integration for the Six-Year Program.
3rd WG meeting, Brussels Proposed Plan for Governance of the Washington Group Prepared by: Jennifer Madans, Barbara Altman, Beth Rasch (USA); Renée Langlois.
SCFAH Title: Draft Baseline Ad-Hoc Recommendation to SC on 3GPP2 Future Source: J. Brownley, Ad-Hoc Chair Abstract: This is a proposed draft.
Discussion on HTASC Future Tobias Haas XV HTASC 3 October, 2003 CERN.
SCFAH r1 Title: Working Draft “Ad-Hoc Recommendation to SC on 3GPP2 Future” Source: 3GPP2 Future Ad Hoc Abstract: This is the draft baseline.
IAOC Report to the ISOC Board Jonne Soininen, Chair Ray Pelletier, IAD 28 March 2009 San Francisco, California, USA ®
IAOC Operations Report Jonne Soininen, Chair Ray Pelletier, IAD 19 November 2008 Minneapolis, MN, USA ®
IAB Report Technical Plenary IETF 81 July 25, 2011.
SIRs, or AIRs, or something draft-carpenter-solution-sirs-01.txt Brian Carpenter without consulting my co-author Dave Crocker IETF 57, 07/03.
1 IETF Status at IETF 71 Russ Housley, IETF Chair.
IAOC Report IETF83 Bob Hinden IAOC Chair Ray Pelletier IAD 28 March 2012.
NomCom WG IETF58 Minneapolis. Agenda Agenda Review Review of changes made in draft-ietf-nomcom-2727bis-08.txt Review of proposals for closing open issues.
IETF and ISOC Internet Standardization Ole Jacobsen, Editor and Publisher The Internet Protocol Journal
The Internet Society (ISOC) Sebastián Bellagamba Manager – Regional Bureau for Latin America and the Caribbean
IT Transition: Lessons Learned 1. DON’T change customer experience 2. Don’t CHANGE customer experience 3. Don’t change CUSTOMER EXPERIENCE 4. Notification.
Authority To Citizen Alerts IETF 81 Quebec. Note: Note Well the Note Well Any submission to the IETF intended by the Contributor for publication as all.
IETF Trust Chair Report Bob Hinden for Marshall Eubanks July 2012.
Initial Plan from Feedback Suresh Krishnan Kathleen Moriarty
CCAMP Working Group Online Agenda and Slides at: Data tracker:
Technical Plenary Agenda IETF 81 Quebec City, Quebec July 25, 2011 Presentations: Jabber room:
Internet and Intranet Fundamentals Class 3 Session B.
IAB Chair Report IETF 88 – Vancouver, BC, CA 6 November 2013.
SCFAH Title: Draft Baseline Ad-Hoc Recommendation to SC on 3GPP2 Future ver2 Source: J. Brownley, Ad-Hoc Chair Abstract: This is a proposed.
IAOC Report IETF80 Bob Hinden IAOC Chair Ray Pelletier IAD 30 March 2011.
Welcome to the Plenary Harald Alvestrand IETF Chair IETF-61, Washington DC, USA.
MODERN BoF Managing, Ordering, Distributing, Exposing, and Registering telephone Numbers IETF 92.
1 Yet Another Mail Working Group IETF 76 November 11, 2009.
Reducing Unwanted Communications in SIP (RUCUS) BOF Hannes Tschofenig Francois Audet.
Long-term Archive and Notary Services (LTANS) Working Group.
Analysis of IETF under meeting criteria Laura Nugent.
Participatory Budgeting Cambridge Real Money! Real Power!
1 IETF 95 Buenos Aires, AR TEAS Working Group Online Agenda and Slide: Data tracker:
OPSAWG chairs: Scott Bradner Christopher Liljenstolpe.
SNMP (Simple Network Management Protocol) Overview
WG Chairs Forum Wednesday 29 March 2017.
IETF mtgvenue venue-selection-process-02
Organizing & Hosting International Events
NOTE WELL Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made.
NOMCOM 2014.
SNMP (Simple Network Management Protocol) Overview
Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made.
Wednesday Plenary Agenda
Organizing & Hosting International Events
Agenda IETF 82 Taipei November 14, 2011
IEEE Sections Congress 2020
IETF Trust Report Kaveh Ranjbar IETF Trust Chair
SIPBRANDY Chair Slides
Scott Bradner & Martin Thomson
Project Name Here Kick-off Date
Presentation transcript:

Choosing IETF Meeting Venues IAOC and IAOC Meeting Committee

Problem statement The meeting venue selection criteria and process is not publicly documented There are recurring discussions in that often revisit the same themes Discussion doesn't typically result in changes/improvements to the process Our solution: Publish our selection criteria and process in draft-baker-mtgvenue- iaoc-venue-selection-process and request feedback Intended status is BCP

Agenda: Opening comments Fred Baker: discuss context and draft briefly Laura Nugent (AMS): discuss trade-off analysis All: discuss What is the IAOC/IAOC Meeting Committee objective in this meeting? Hear commentary, with a view to a committee decision Goal: finish review in the hour we have No document re-engineering in real time

Who does the choosing? IAOC Leslie Daigle, IAOC Chair Jari Arkko, IETF Chair Ray Pelletier, IAD Kathy Brown, ISOC Pres/CEO Andrew Sullivan, IAB Chair Lou Berger, Nomcom appointee Scott Bradner, ISOC BoT appointee Tobias Gondrom, IESG appointee Benson Schliesser, IAB appointee IAOC Meeting Committee Ole Jacobsen, Chair Fred Baker Dave Crocker Bob Hinden Lou Berger (IAOC) Tobias Gondrom (IAOC) Jim Martin (NOC Team) Ray Pelletier (IAD) Marcia Beaulieu (AMS) Kirsten Machi (AMS) Stephanie McCammon (AMS) Alexa Morris (AMS) Laura Nugent (AMS)

Outline 1. Introduction 1.1. Requirements Language 2. Meeting Selection Participants and Responsibilities 2.1. The IETF Community 2.2. IESG and IETF Chair 2.3. The Internet Society 2.4. IETF Administrative Oversight Committee 2.5. IETF Administrative Support Activity 2.6. IETF Administrative Director 2.7. IAOC Meeting Committee 3. Venue Selection Process 3.1. Venue Selection Principles 3.2. Venue Selection Objectives 3.3. Venue Selection Criteria Venue City Considerations Basic Venue Criteria Technical Services and Operations Criteria Lodging Food and Beverage 3.4. Non-criteria 3.5. Venue Selection Timeline 3.6. Experience Notes 4. Transparency 5. IANA Considerations 6. Security Considerations 7. Privacy Considerations 8. Contributors

Venue Selection Principles Who are we? Multi-disciplinary, improve the Internet Why do we meet? To discuss and advance Internet Drafts and RFCs Where do we meet? Globally, to share cost and travel burden Inclusiveness: We want to facilitate participation by anyone Internet Access: Unfiltered access to facilitate our work Focus: Focused technical discussions, in breakouts and the hall Economics: Within reason, budget should not limit participation

Venue Selection Objectives Advancing standards development Facilitating participation by active contributors Sharing the travel pain; balancing travel time and expense across the regions from where IETF participants are based. Encouraging new contributors Continental Rotation IESG targets a rotation among North America, Europe, and Eastern Asia (“1-1-1”) IETF Chair can insert a meeting in another location, with community input (“1-1-1*”) Changing the rotation: Demonstrate participation from the region in question

Venue City Criteria Mandatory Acceptable travel costs Minimal barriers to entry Minimize economic, safety, and health risks Hosts? Sponsors? Desirable Prior successful meeting experience Possibility of a multi-event contract

Basic Venue Criteria Mandatory Meeting space is adequate Venue and hotels can be put under contract Cost of rooms, meeting space, food, and beverage is affordable Desirable Ideally, under one roof If not that, most participants could stay in primary IETF hotel(s) Accessible to people with disabilities

Technical Services and Operations Criteria Mandatory Venue network, A/V, etc are adequate, or we can upgrade them to be adequate Venue must permit and facilitate the delivery of a high performance, robust, unfiltered and unmodified IETF Network IETF SSID in IETF hotel(s) similarly high quality Desirable IETF SSID in overflow hotels similarly high quality

Lodging Mandatory Close to venue IETF hotel(s) house at least 1/3 of projected attendance Lower budget lodging near venue Overflow hotels can be contracted near venue, catering to budget Desirable Accessible to people with disabilities

Food and Beverage Mandatory Venue neighborhood has convenient and inexpensive choices for meals that can accommodate a wide range of dietary requirements. Desirable Venue neighborhood includes a grocery store that will accommodate a wide range of dietary requirements.

Venue Selection Timeline 4years out IAOC selects regions for meetings Target cities provided to Secretariat Potential venues identified Sites qualified Preliminary negotiations started IAOC Meetings Committee makes a recommendation to the IAOC IAOC approves recommendation 2-3/4 – 3 years out Contract negotiations eventually complete Contracts are executed Experience to date for Asia and Latin America is that, due to local business practice, the process of contracting takes longer and results in contracts not being finalized more than two, or sometimes one, years in advance of the meeting.

Draft discussion to date

Venue Selection Objectives Advancing standards development Facilitating participation by active contributors Sharing the travel pain; balancing travel time and expense across the regions from where IETF participants are based. Encouraging new contributors Generating funds to support IETF operations in support of standards development, including the Secretariat, IASA, and the RFC Editor. Continental Rotation IESG targets a rotation among North America, Europe, and Eastern Asia (“1-1-1”) IETF Chair can insert a meeting in another location, with community input (“1-1-1*”) Changing the rotation: Demonstrate participation from the region in question

Lodging Mandatory Close to venue IETF hotel(s) house at least 1/3 of projected attendance point suggests making it be ½ to 2/3 of attendees Lower budget lodging near venue Overflow hotels can be contracted near venue, catering to budget Desirable Accessible to people with disabilities

Venue City Criteria Considerations Mandatory Important Acceptable travel costs Minimal barriers to entry Minimize economic, safety, and health risks Hosts? Sponsors? Desirable Nice to have Prior successful meeting experience Possibility of a multi-event contract Review available travel information (such as ) for issues that would be counter to our principles on inclusiveness etc. [Mandatory or important]

Basic Venue Criteria Mandatory Meeting space is adequate Venue and hotels can be put under contract Cost of rooms, meeting space, food, and beverage is affordable The economics of the venue allow the meeting to be net cash positive. Desirable Ideally, under one roof If not that, most participants could stay in primary IETF hotel(s) Accessible to people with disabilities