IAB Workshop on Stack Evolution in a Middlebox Internet (SEMI)
26-27 January 2015 – ETH Zürich, Switzerland
Submissions accepted at: https://www.easychair.org/conferences/?conf=semi2015
- Submission Deadline: 31 October 2014
- Notification Deadline: 17 November 2014
- Workshop Dates: 26-27 January 2015
The IAB has selected John Levine to serve on the 2015 ICANN NOMCOM. He is co-author of nine RFCs, and he brings a wealth of experience in both the IETF and ICANN. He is the past chair of the IRTF’s AntiSpam Research Group, and he has more recently delved into issues relating to zone cuts. At ICANN he is an active participant in the At-Large Advisory Committee (ALAC), and he has participated as an expert on the RSTEP committee. The IAB wishes John every success in this important role, and encourages the whole community to share their views with John about the various ICANN leadership positions that he will have a part in selecting.
The IAB thanks everyone who put their name forward as a candidate for this position, as well as Russ Mundy for his service in this role over the last year.
As part of the NTIA/IANA transition, the IAB is to select two people to serve as members of the co-ordination group. The IAB (less those whose names were under consideration for appointment) deliberated, and hereby appoints Russ Housley and Lynn St. Amour.
Russ is an IAB member and Chair of the IAB, and is a member of the IAB’s IANA Evolution program. Lynn continued as a member of the IAB’s IANA Evolution program after stepping down recently as CEO of ISOC.
We thank both Russ and Lynn for being willing to serve, and thank others who were willing to be considered.
The appointments have been communicated to ICANN in its role as convenor of the process.
The IAB has published RFC 7241: The IEEE 802/IETF Relationship.
Abstract: This document describes the standardization cooperation between Project 802 of the Institute of Electrical and Electronics Engineers (IEEE) and the Internet Engineering Task Force (IETF). This document obsoletes RFC 4441.
Note: This document was collaboratively developed by authors from both the IEEE 802 and IETF leadership and was reviewed and approved by the IEEE 802 Executive Committee prior to publication.
As part of its oversight responsibility for the Independent Stream, the IAB is solociting comments from the community on the performance of the Independent Stream Editor, Nevil Brownlee. We are interested in comments on what has gone well or badly in the last several years of operation of the Independent Stream and Nevil’s activities as ISE.
Please send comments to firstname.lastname@example.org. In addition, please CC email@example.com.
We would appreciate receiving comments as soon as possible, as the IAB will likely begin the next steps in the oversight process shortly after the end of IETF 90 in Toronto.
The IAB has published RFC 7305: Report from the IAB Workshop on Internet Technology Adoption and Transition (ITAT).
Abstract: This document provides an overview of a workshop held by the Internet Architecture Board (IAB) on Internet Technology Adoption and Transition (ITAT). The workshop was hosted by the University of Cambridge on December 4th and 5th of 2013 in Cambridge, UK. The goal of the workshop was to facilitate adoption of Internet protocols, through examination of a variety of economic models, with particular emphasis at the waist of the hourglass (e.g., the middle of the protocol stack). This report summarizes contributions and discussions. As the topics were wide ranging, there is no single set of recommendations for IETF participants to pursue at this time. Instead, in the classic sense of early research, the workshop noted areas that deserve further exploration. Note that this document is a report on the proceedings of the workshop. The views and positions documented in this report are those of the workshop participants and do not necessarily reflect IAB views and positions.
The IAB (on behalf of the IETF) has been asked to supply a member to the 2015 ICANN Nominating Committee (NomCom) by August 2014. The IAB would therefore like to ask the community for volunteers to serve on the ICANN NomCom. Our current appointee, Russ Mundy is unable to serve another term. The IAB thanks Russ for his service and wishes him well.
If you are interested in serving on the ICANN NomCom, please send a short e-mail to firstname.lastname@example.org and email@example.com with your motivation and information concerning your familiarity with the IETF and ICANN. The deadline for volunteering is 19 July 2014. Continue reading
The IAB has published RFC 7295: Report from the IAB/IRTF Workshop on Congestion Control.
Abstract: This document provides a summary of the IAB/IRTF Workshop on ‘Congestion Control for Interactive Real-Time Communication’, which took place in Vancouver, Canada, on July 28, 2012. The main goal of the workshop was to foster a discussion on congestion control mechanisms for interactive real-time communication. This report summarizes the discussions and lists recommendations to the Internet Engineering Task Force (IETF) community.
The views and positions in this report are those of the workshop participants and do not necessarily reflect the views and positions of the authors, the Internet Architecture Board (IAB), or the Internet Research Task Force (IRTF).
The IAB has appointed Matt Miller to serve as IETF liaison manager to ECMA TC39. Matt works at Cisco Systems and is also currently the chair of the JSON working group.
The IAB thanks Matt for putting his name forward, and wishes him success in this new role.
The IAB has published RFC 7288: Reflections on Host Firewalls.
Abstract: In today’s Internet, the need for firewalls is generally accepted in the industry, and indeed firewalls are widely deployed in practice. Unlike traditional firewalls that protect network links, host firewalls run in end-user systems. Often the result is that software may be running and potentially consuming resources, but then communication is blocked by a host firewall. It’s taken for granted that this end state is either desirable or the best that can be achieved in practice, rather than (for example) an end state where the relevant software is not running or is running in a way that would not result in unwanted communication. In this document, we explore the issues behind these assumptions and provide suggestions on improving the architecture going forward.