Evolutionizing the IETF Harald Alvestrand Subversive.

Slides:



Advertisements
Similar presentations
Question Exploration Guide
Advertisements

Corporate Culture and Values c o l o r w o r k s f o r y o u To help something grow, you must have an understanding of what it wants to become.
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.
RFC 2050 Working Group Ray Plzak ARIN On behalf of Mark McFadden.
Time Management By Zahira Gonzalez.
Project leaders will keep track of team progress using an A3 Report.
Timeliness, Effectiveness, Quality and the IETF Aaron Falk
Russ Housley IETF Chair 23 July 2012 Introduction to the IETF Standards Process.
What is a Working Group ID (and when to adopt one) Adrian Farrel Maastricht, July 2010.
Evolutionizing the IETF Status and plans Harald Alvestrand.
CEP Welcome September 1, Matthew J. Koehler September 1, 2005CEP Cognition and Technology Who’s Who?  Team up with someone you don’t.
OAuth 2.0 Security IETF OAuth WG Conference Call, 14th December 2012.
L2VPN WG “NVO3” Meeting IETF 82 Taipei, Taiwan. Agenda Administrivia Framing Today’s Discussions (5 minutes) Cloud Networking: Framework and VPN Applicability.
1 A short introduction to the IETF Harald Alvestrand IETF chair Harald Alvestrand IETF chair.
Problem Identification
How Teams Work. Task and Maintenance Needs  Task Activities – Any activity a team member does that contributes to the group’s performance purpose. 
A Comprehensive Approach to Quality (COACH) IETF 57 Vienna, Austria Monday, July 14, :00 – 15:00
NETCONF WG IETF 92 - Dallas TUESDAY, March 24, CDT Mehmet Ersue Mahesh Jethanandani 3/24/ IETF #92- NETCONF WG session.
The Team Meeting Process Author: VCU T/TAC Clipart found at:
SIRs, or AIRs, or something draft-carpenter-solution-sirs-01.txt Brian Carpenter without consulting my co-author Dave Crocker IETF 57, 07/03.
20th AIAA Advanced Measurement and Ground Testing Technology Conference Lessons Learned in AIAA Working Group Development E. Allen Arrington Dynacs/NASA.
IETF #82 DRINKS WG Meeting Taipei, Taiwan Fri, Nov 18 th
Routing Area Open Meeting Hiroshima, November 2009 Area Directors Ross Callon Adrian Farrel.
Activity 5: Lead this Group! Instructions: There are many ways for a leader to respond to situations that have developed within a group. How would you.
Some Tools For Team Building Faith and Light International Formation 2010.
Multi6 Working Group IETF-61, Washington D.C November 8-12, 2004.
NEWTRK WG Paris, August 5, Agenda 0 – agenda bashing – 10m 1 - introduction & status - chair- 10m discussion on the issues with ISD proposal.
Sophie Makris  What is a team?  A group of people pooling their skills, talents, and knowledge, with mutual support and resources, to provide.
AN INTRODUCTION Managing Change in Healthcare IT Implementations Sherrilynne Fuller, Center for Public Health Informatics School of Public Health, University.
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.
Team Development Objectives To know the stages in the development of teams To understand team roles To understand about team decisions To learn how to.
Team building Prepared by : MS\ Abeer foad MS\ Fatima Al- sakran Supervised by : Dr \ Nazik zakari.
SIPREC WG, IETF# , GMT+2 John Elwell (WG co-chair) Brian Rosen (WG co-chair)
File: /ram/wgchairs.sxi Date: 7 January, 2016 Slide 1 Process and Tools (PROTO) Team General Area Meeting IETF59, Seoul, Korea -- March 2004
New Supervisors’ Guide To Effective Supervision
BFD IETF 83. 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.
Polling and Voting Adrian Farrel Routing Area Director Maastricht, July 2010.
Content Vocabulary Word Documentation. Content Vocabulary 0 Teamwork: cooperative or coordinated effort on the part of a group of persons acting together.
The IETF World of Standardisation Jon Crowcroft, Computer Lab, Cambridge University.
Conducting Business Meetings Satorre, Joshua Jerem T. ENSP2 Instructor: Mr. Xavier Aquino Velasco - Associate/Lecturer III, FEU Tech.
File: /ram/wgchairs.sxi Date: 10 February, 2016 Slide 1 Margaret Wasserman WG Chairs Training.
IETF 851 Chairs: Flemming Andreasen Miguel A. Garcia [Paul Kyzivat substitute for this meeting]
CPS 82, Fall IETF: Internet Engineering Task Force l “governs” the Internet (according to some)  What does this mean? Who elects the members?
Solving The Collaboration Problem Collaboration is the working together of different people to achieve increase creative thinking and maximize intellectual.
Interface to the Routing System (IRS) BOF IETF 85, Atlanta November 2012.
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.
EDU BOF IESG Plenary – IETF57, Vienna Margaret Wasserman
HIP WG Gonzalo Camarillo David Ward IETF 80, Prague, Czech Republic THURSDAY, March 31, 2011, Barcelona/Berlin.
Agenda Behcet Sarikaya Dirk von Hugo November 2012 FMC BOF IETF
MODERN BoF Managing, Ordering, Distributing, Exposing, and Registering telephone Numbers IETF 92.
1 Yet Another Mail Working Group IETF 76 November 11, 2009.
Importance of formative literacy experiences Daniella Ramos.
Starting & Running A People First Chapter Kevin Smith Self-Advocate Coordinator People First of WV , ext. 102.
CLUE WG IETF-85 Mary Barnes (WG co-chair) Paul Kyzivat (WG co-chair)
ID Tracker States: An Internet Draft’s Path Through the IESG
WG Chairs Forum Wednesday 29 March 2017.
LMAP WG IETF 97 – Seoul, SK November 17, 2016 Dan Romascanu Jason Weil
Chairs: Flemming Andreasen Miguel A. Garcia
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.
IETF 86 Orlando MBONED.
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.
Why the Multistakeholder Approach Works
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.
RIPE Cooperation WG IGF update
Learning loves company
Effective Meeting.
16th November 2016 Gorry Fairhurst (via webrtc) David Black WG chairs
Effective Leadership Skills
Marc Linsner Richard Barnes Roger Marshall
Presentation transcript:

Evolutionizing the IETF Harald Alvestrand Subversive

The IETF is a success Producing relevant, high quality standards for the Internet Allowing open participation and fair sharing of ideas Increasing participation of relevant groups The leadership is providing an unified vision of the Internet that guides the standardization effort Using the Internet to create the Internet

The IETF is a failure Work is slow, output mediocre and irrelevant to the real problems facing the Internet Decisions are taken by backroom deals, intimidation and mob psychology The IESG imposes random mandates that are irrelevant to the problems at hand People leaving in disgust in droves Technically,the IETF is the most retrograde organization on the Internet

Core values of the IETF Cares for the Internet Technically competent Open process Volunteer core ”We reject kings, presidents and voting. We believe in rough consensus and running code ”

Not core values The division into WGs and Areas The three-step standards process The ASCII format for RFCs and I-Ds The format of IETF meetings The shape of WG mailing lists The power of the IESG

Recent changes in the world The dot-com boom has ended. With a bang. The Internet is still growing, but turning into ”part of basic plumbing” ICANN is reforming itself to do ”Internet coordination” (whatever that means) ITU wants to take a more active role on the Internet (if it can afford it) Governments are interested (and worried)

Recent changes in the IETF Increasing cooperation across the IETF –Areas working together, trying to achieve commonality Increasing the quality of the IESG process –The ”tracker”, installed this spring, has been a boon for making sure IESG items remain visible Increasing the transparency of IESG evaluation –Opened the tracker to the public on November 1 Trying to get more people talking –Technology directorates, evaluation teams

Recent non-changes No change to IESG personnel No change in the BOF procedures No change in how WGs are started No change in how WGs are managed No change in operator of secretariat, RFC Editor, IANA or ISOC relationship All of these have been suggested. All of these should be thought about. We won’t do them all.

So what is the problem? People perceive a problem. Perception is reality. We must know what the problems are before we can address them The leadership is not the right persons to identify the problems. Over to the community......

The Voices of Others

The Four Ugly Things (not written about the IETF) Putting men to death without having taught them Right – that is called savagery Expecting the completion of tasks without giving due warning – that is called oppression To be dilatory about giving orders, but to expect absolute punctuality – that is called being a tormentor And similarly, though meaning to let a man have something, to be grudging about bringing it out – that is called behaving like a petty functionary. Confucius, 500 BC

Where do we go from here???? What problem do we want to solve? –Creating relevant, high quality standards for the Internet How do we want to solve it? –Identify the problems that hurt –Find ways that work better –Do it!

Who is supposed to do this? Once we (who are we?) agree what ”this” is, of course Backrooms DO NOT WORK. The IETF works in the open. Huge groups alone DO NOT WORK. We know how to critique and fine-tune; we do not know how to create in the large. What next step?

A Strawman Process Charter a working group to define a problem statement (timeline – Spring 2002) Charter a working group to revise the IETF to address the problems raised Call on expertise within and outside the IETF to contribute Conduct public review of the process Accept the result through the public IETF process Find a method to evaluate the result later on

Strawman: Targets of the process Retain the openness Re-engage the community in the IETF process Retain the technical competence Decrease the saturation on managers Increase the ability to act rapidly and correctly Make the IETF a fun place to work!

Who has the token? The I* is working on this (this expression matches IESG, IAB and IETF) We need to make the IETF work while we’re working on this The management team cannot function effectively while critiquing itself The process must be rooted outside the leadership A person must be named – soon!

Conclusions The IETF is valuable The IETF has problems The IETF community is responsible for fixing those problems There’s lots of work ahead of us Now we would like to hear what you think the problem is…..

A parting thought….. We trained hard, but it seemed that everytime we were beginning to form up into teams, we would be reorganized. I was to learn later in life that we tend to meet any new situation by reorganizing; and a wonderful method it can be for creating the illusion of progress while producing confusion, inefficiency and demoralization. Petronius Arbiter (210 B.C.)