On behalf of the IETF, the IAB names two technical experts to ICANN Technical Liaison Group (TLG). The ICANN Bylaws (Article XI-A, Section 2, Paragraph 6) asks the IETF, ITU-T, ETSI, and W3C to each provide two technical experts. The technical experts are expected to be “familiar with the technical standards issues that are relevant to ICANN’s activities.” These eight experts are expected to be “available as necessary to determine, through an exchange of e-mail messages, where to direct a technical question from ICANN when ICANN does not ask a specific TLG organization directly.”
The ICANN bylaws can be found at http://www.icann.org/en/about/governance/bylaws.
The current experts are Warren Kumari (term ends January 2016) and Paul Wouters (term ends 2017). Warren Kumari has indicated that he is willing to serve again. The IAB would like to see whether others are interested in serving in this capacity. Continue reading
This is the report from the IAB to the community about our activities since IETF 93. We’re taking the occasion of the compressed plenary to move more of our reporting to this email, which we’ll send before meetings. Of course, we encourage as ever discussion of things you want to raise in the plenary. We hope, however, that providing this in advance will allow you more time to prepare any questions you have about our activities, while allowing us to concentrate in the plenary on things we think raise issues or are most important for the community to think about. We want to know whether this new approach is agreeable. Let us know at the mic, or else send mail to firstname.lastname@example.org. You can do that about any other issue in this report too. In general, we value feedback and want to respond to issues you see. Continue reading
The IAB has published RFC 7669: Assigning Digital Object Identifiers to RFCs.
Abstract: This document describes the way that Digital Object Identifiers (DOIs) are assigned to past and future RFCs. The DOI is a widely used system that assigns unique identifiers to digital documents that can be queried and managed in a consistent fashion.
The IAB has published RFC 7663: Report from the IAB Workshop on Stack Evolution in a Middlebox Internet (SEMI).
Abstract: The Internet Architecture Board (IAB) through its IP Stack Evolution program, the Internet Society, and the Swiss Federal Institute of Technology (ETH) Zurich hosted the Stack Evolution in a Middlebox Internet (SEMI) workshop in Zurich on 26-27 January 2015 to explore the ability to evolve the transport layer in the presence of middlebox- and interface-related ossification of the stack. The goal of the workshop was to produce architectural and engineering guidance on future work to break the logjam, focusing on incrementally deployable approaches with clear incentives to deployment both on the endpoints (in new transport layers and applications) as well as on middleboxes (run by network operators). This document summarizes the contributions to the workshop and provides an overview of the discussion at the workshop, as well as the outcomes and next steps identified by 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.
On 7 October 2015, the IAB provided comments to the FCC on their proposed Amendment of Parts 0, 1, 2, 15 and 18 of the Commission’s Rules regarding Authorization of Radiofrequency Equipment (FCC 15-92):
The Internet Architecture Board (IAB) welcomes the efforts of the FCC to
simplify its procedures and to accelerate the verification processes
associated with Radio Frequency devices. We note, however, that there
may be additional clarification needed in one aspect of the proposed
rule making. As set out in Paragraph 20 of Notice of July 21st, the
document proposes that device manufacturers "incorporate software
security features that permit only those parties that have been
authorized by the manufacturer to make changes to the device's technical
The IAB welcomes the focus on security, but notes that software security
features of this type must be broad enough to permit device firmware
updates by parties other than the manufacturer itself. This is necessary
first because a manufacturer ceasing operation would otherwise leave all
hardware orphaned from update, which itself poses significant potential
security risks. It is also necessary because many radio frequency
devices originally intended for one set of use cases have been adapted
by the experimental and open source communities for new uses. Closing
off this source of innovation and advancement is clearly counter to the
interests promoted by the FCC.
We encourage the FCC to amend this plan to require both software
security features and a clearly defined program by which authorization
for access to these update features can be granted; this program should
be as simple as possible, so that open source communities, academia, and
other experimental efforts may be sustained.
Andrew Sullivan (IAB Chair)
for the IAB
The IAB is pleased to appoint Tim Wicinski to the ICANN Nomcom.
Tim has been involved with DNS and the standards processes for many years. In the past several years, he has been co-chair of the DNS Operations (DNSOP) Working Group within the IETF; and more recently the co-chair of the DNS Privacy Exchange (DPRIVE) Working Group. Tim is a Site Reliability Architect at Salesforce.com, with a focus on DNS and CDN technologies.
The IAB had several able candidates to choose from this year, which made the choice difficult. We thank all the volunteers for putting their names forward, and encourage their continued engagement with the IETF. The IAB also wishes to thank John Levine for his previous service as the IAB appointee on the ICANN Nomcom.
On 7 September 2015, the IAB sent correspondence to the IANA Stewardship Transition Coordination Group on the IANA Stewardship Transition Proposal. The IAB comments may be viewed here: https://www.iab.org/documents/correspondence-reports-documents/2015-2/iab-comments-on-icg-proposal/
This is an announcement of an IETF-wide Call for Comment on draft-iab-xml2rfcv2-01.
The document is being considered for publication as an Informational RFC within the IAB stream, and is available for inspection here:
Please note that the purpose of the document is to represent the state of the vocabulary as actually implemented in the xml2rfc system as of current writing. Therefore, if you have particular concerns about the design or functionality described in this I-D, the comments about those issues are best addressed to the authors of another draft (draft-hoffman-xml2rfc-21). Discussion of that draft is active on the email@example.com mailing list. We ask that comments about this draft focus on the degree to which it accurately reflects the current xml2rfc implementation, and whether it is clear, comprehensible, useful, and complete.
The Call for Comment will last until 2015-09-02. Please send comments to firstname.lastname@example.org. The RFC Editor has also asked that email@example.com be copied.