ION Cape Town, 8 September 2015: The Internet Society is working toward fostering a larger and more engaged network operator community around the IETF and protocol development work. Part of that work was a survey of network operators in 2014 and an Internet-Draft about its results. We’re also interested specifically in bringing more African engineers with operational experience into the IETF, and perhaps even bringing a physical IETF meeting to the continent of Africa within the next few years. We’ll outline some of our recent work and hope to make this an interactive session to learn from the local community how to encourage more IETF participation.
2. What is the Internet Society?
The Internet Society (ISOC) is a cause-based organization that works with
governments, industries, and others to ensure the technologies and policies
that helped develop and evolve the Internet will continue into the future.
Our programs cultivate an Internet that is open to everyone, everywhere and
aim to ensure that it will continue to be a tool for creativity, innovation, and
economic growth.
MISSION: To promote the open development, evolution,
and use of the Internet for the benefit of all people
throughout the world.
VISION: The Internet is for everyone
5. 5
Internet Engineering Task Force
• “We make the Internet work better”
• The mission of the IETF is to produce high
quality, relevant technical and engineering
documents that influence the way people
design, use, and manage the Internet in
such a way as to make the Internet work
better. These documents include protocol
standards, best current practices, and
informational documents of various kinds.
[RFC 3935]
6. Brief history of the IETF
• First meeting held in January 1986
• 21 attendees at Linkabit in San Diego
• Evolution from ARPA
• Internet Configuration Control Board (ICCB) in 1979
• Internet Activities Board (1983)
• Working Groups introduced at 5th meeting, Feb 1987
• Structure of IAB, IETF, IRTF set at 14th meeting, July 1989
• ISOC formed and set as organizational home in 1992
• International meetings since 1990
• First meeting outside US in 1990 (Vancouver)
• First European meeting in 1993 (Amsterdam)
• First Asian meeting in 2000 (Adelaide)
• First Latin American meeting scheduled for 2016 (Buenos Aires)
• There have been 92 IETF meetings as of March 2015
7. 7
IETF Participants
• An open and international community
Network designers
Operators
Vendors
Researchers
• Interested individuals
People, not companies
10. IETF Awareness activities in Africa
• ISOC IETF Fellowship
• The ISOC IETF fellowship was introduced in 2006 with Alain Aina and Michuki Mwangi being the
first fellows
• 44 fellows from Africa have attended the IETF since 2006
• IETF awareness workshops in the African Region
• AIS 2011 – Tanzania Workshop
• Panel discussions on the importance of IETF. Session had over 30 participants
• AIS 2012 – Gambia workshop
• IETF Remote hubs in Cameroon, Ethiopia, Kenya & Uganda
• Total of 212 attendees between AIS and remote hubs
• AIS 2013 – Zambia workshop
• Discussions on the importance of IETF and how to participate. Event had 36 attendees
• AIS 2014 – Djibouti
• Update and discussions on IETF activities. Event had 40 attendees
• IETF Fellowships to African Policy makers for the last 3 years
11. Africa’s contribution to Internet Standards
Development
• There is a small number of individuals actively
involved with the IETF from Africa
• In March 2015, RFC7479 authored by S. Moonesamy
from Mauritius was published.
• Others that have contributed to drafts that have latter
been published as RFCs like Alan Barret, Alain Aina,
etc
• AfriNIC staff have also been actively involved in the
IETF.
12. Improving Africa’s participation to IETF
- Why?
- Since it is being part of the future of the Internet
- Africa is ready
- It now has the critical mass of Internet experts to be part of IETF
- How?
- Participation in working groups
- Participating to IETF meetings (face to face or remotely)
- Bringing IETF meetings to Africa
13. Bringing an IETF meeting to Africa
• The IAOC conducts “meeting preference surveys”
during IETF meetings for selection of venue
• The 2010 meeting survey showed that:
• 44.8% of respondents were in favor of attending an IETF held in
South or Central America
• 39.8% of respondents were in favor of attending an IETF held in
Africa
• Why not Africa until now?
• Not many participants from Africa in working groups
• IETF participants pay their travel costs
• Perception that Africa does not have the capacity to host an IETF
meeting
• Perception of lack of security
14. Bringing an IETF meeting to Africa
Objective:
• To successfully host the first IETF meeting in Africa in
2018
How ?
• By growing the IETFers community in Africa
• By mobilizing the Af* community around this objective
• By changing the (false) perceptions
15. Next step – Community Mobilization
• Establish a community based task-force to lead the
efforts towards having first IETF meeting event in
Africa
• The task-force will define its scope and engage the
technical community towards this goal
• We are counting on the technical community’s
support to become IETF ambassadors
• The technical community can contribute by:
• Creating awareness within your technical forums and institutions
• Support the task-force efforts in identifying the local technical
communities and institutions
The Internet Society:
Encourages open development of standards, protocols, administration.
Enables economic growth in developing countries through education and training
Fosters participation and and develops new leaders in areas important to the evolution of the Internet.
Provides reliable information about the Internet.
Leads and facilitates discussion of issues that affect Internet evolution and developments.
The Internet Society works globally, across the broad range of policy, technology, and development, which allows it to bring unique perspectives and insight about how to address some of the significant issues facing the Internet today.
100+ organization members
Tens of thousands of individual members
90+ chapters worldwide
Regional Bureaus: Africa, Europe, Latin America & Caribbean, North America, South & South East Asia
The first IETF meeting was held in January 1986 at Linkabit in San Diego, with 21 attendees.
The 4th IETF, held at SRI in Menlo Park in October 1986, was the first that vendors attended.
The concept of Working Groups was introduced at the 5th IETF meeting at the NASA Ames Research Center in California in February 1987.
The 7th IETF, held at MITRE in McLean, Virginia, in July 1987, was the first meeting with more than 100 attendees.
The 14th IETF meeting was held at Stanford University in July 1989. It marked a major change in the structure of the IETF universe. The structure of the IAB (then the Internet Activities Board, now the Internet Architecture Board), which until that time oversaw many "task forces", was changed, leaving it with only two: the IETF and the IRTF. The IRTF is tasked to consider long-term research problems in the Internet. The IETF also changed at that time.
After the Internet Society (ISOC) was formed in January 1992, the IAB proposed to ISOC that the IAB's activities should take place under the auspices of the Internet Society. During INET92 in Kobe, Japan, the ISOC Trustees approved a new charter for the IAB to reflect the proposed relationship.
The IETF met in Amsterdam, The Netherlands, in July 1993. This was the first IETF meeting held in Europe, and the US/non-US attendee split was nearly 50/50.
The IETF first met in Asia (in Adelaide, Australia) in 2000.
Currently, the IETF meets in North America, Europe, and Asia. The intention is to meet once a year in each region, although due to scheduling issues there are often more meetings in North America and fewer in Asia and Europe. The number of non-US attendees continues to be high — about 50%, even at meetings held in the United States.
From: http://www.ietf.org/tao.html