On 7 December 2016, the IAB responded to the ICANN call for public comments on the Revised Proposed Implementation of GNSO Thick Whois Consensus Policy Requiring Consistent Labeling and Display of RDDS (Whois) Output for All gTLDs.
This is the usual IAB report to the community about our activities since the previous meeting (in this case, since IETF 96 in Berlin). As ever, we hope that this form allows you to prepare topics you might want to discuss during the open mic. But of course, if you have views you want to make known by email, we’re easy to reach: send mail to email@example.com to reach our public discussion list, and firstname.lastname@example.org to reach just the IAB.
The IAB has a few chartered roles. We confirm the appointments to the IESG and perform standards process oversight and handle appeals. We also perform architectural oversight (including appointing the IRTF Chair), we manage the RFC series and the IETF’s relationship with IANA, and we handle liaisons both to ISOC and to other organizations. We try to ensure that anything we do is part of one of these areas of responsibility, and we try to make sure these are all covered.
The Internet Architecture Board (IAB), following discussions in the Internet Engineering Task Force (IETF), advises its partner Standards Development Organizations (SDOs) and organizations that the pool of unassigned IPv4 addresses has been exhausted, and as a result we are seeing an increase in both dual-stack (that is, both IPv4 and IPv6) and IPv6-only deployments, a trend that will only accelerate. Therefore, networking standards need to fully support IPv6. The IETF as well as other SDOs need to ensure that their standards do not assume IPv4.
The IAB expects that the IETF will stop requiring IPv4 compatibility in new or extended protocols. Future IETF protocol work will then optimize for and depend on IPv6.
Preparation for this transition requires ensuring that many different environments are capable of operating completely on IPv6 without being dependent on IPv4 [see RFC 6540]. We recommend that all networking standards assume the use of IPv6, and be written so they do not require IPv4. We recommend that existing standards be reviewed to ensure they will work with IPv6, and use IPv6 examples. Backward connectivity to IPv4, via dual-stack or a transition technology, will be needed for some time. The key issue for SDOs is to remove any obstacles in their standards which prevent or slow down the transition in different environments.
In addition, the IETF has found it useful to add IPv6 to its external resources (e.g., Web, mail) and to also run IPv6 on its conference network since this helps our participants and contributors and also sends the message that we are serious about IPv6. That approach might be applicable to other SDOs.
We encourage the industry to develop strategies for IPv6-only operation. We welcome reports of where gaps in standards remain, requiring further developments in IPv6 or other protocols. We are also ready to provide support or assistance in bridging those gaps.
As described in BCP 101 (RFC 4071) and BCP 113 (RFC 4333), the IESG and the IAB each select one person for a two-year IAOC term in alternate years. This year, the IAB will select one person for a term beginning in March 2017.
Following the call for nominations, which ran from 5 October 2016 through 2 November 2016, the IAB contacted each person that was nominated, asking them to accept or reject their nomination. At this point, 7 people have indicated a willingness to serve. They are:
Abdelhamid AL Rahamneh
Gatta Sambasiva Rao
The IAB is actively soliciting confidential comments on these people and their ability to serve on the IAOC. The IAB needs to receive these comments by 30 November 2016 in order to make a selection in December 2016. Please send comments to email@example.com and firstname.lastname@example.org.
Note that the NomCom will also be selecting a person to serve on the IAOC for a two-year term. This process is orthogonal, the IAB is not privy to comments you might have submitted to the NomCom.
The IAB has re-appointed Paul Wouters to serve a two-year term on the ICANN Technical Liaison Group (TLG). The IAB thanks Paul for his willingness to serve the community in this capacity.
As part of its oversight responsibility for the Independent Stream, the IAB is soliciting 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 iab-chair at iab.org. In addition, please CC execd at iab.org.
We would appreciate receiving comments by Tuesday, November 29, 2016 as the IAB will likely begin the next steps in the oversight process shortly after the end of IETF 97 in Seoul.
The IAB names two technical experts to the ICANN Technical Liaison Group (TLG). The TLG is tasked with connecting the ICANN Board with appropriate sources of technical advice on specific matters pertinent to ICANN’s activities.
Warren Kumari and Paul Wouters are the current experts. Paul’s current term ends in early 2017; he has indicated that he is willing to serve for an additional two-year term.
The IAB would like to solicit comments from the community on the performance of Paul Wouters on the ICANN TLG. Please send comments to iab-chair at iab.org and execd at iab.org.
We would appreciate receiving comments by Wednesday, October 26.
This is a call for nominations for the IAB appointment to the IETF Administrative Oversight Committee (IAOC). The nomination period will close on 2 November 2016.
IAOC membership is described in BCP 101 (RFC 4071) Section 4, with selection guidelines and process documented in BCP 113 (RFC 4333). In alternate years, the IESG and the IAB each select one person for a two-year IAOC term. This year, the IAB will select one person for a term beginning in March 2017. Note that the NomCom is also selecting an IAOC member.
Candidates for these IAOC positions should have knowledge of the IETF, knowledge of contracts and financial procedures, and familiarity with the administrative support needs of the IAB, the IESG, and the IETF standards process. Candidates are also expected to be able to understand the respective roles and responsibilities of the IETF and ISOC in this activity, and be able to articulate these roles within the IETF community.
Acceptable candidates must be prepared to exercise all the duties of an IAOC member. These responsibilities include, but are not limited to, the setting (in consultation with the community and after carefully considering their input) of administrative support policies, oversight of the administrative operations of the IETF, and representing the interests of the IETF to the IAOC. The IAOC meets for a couple of hours at each IETF meeting, holds two conference calls each month, and meets for two days in a separate meeting, usually in May. Acceptable candidates must be able to undertake full participation in all IAOC meetings and activities.
IAOC members also serve as the trustees of the IETF Trust. Please note that the role of the IETF Trust is expanding as part of the IANA stewardship transition.
The IAB-selected member of the IAOC does not directly represent the IAB. The IAB and IESG selected members are accountable directly to the IETF community. As such, candidates do not need to be current members of the IAB or the IESG and, in fact, we prefer nominations and volunteers from the rest of the community.
If you are interested in serving on the IAOC, or know of someone who may be a good fit for this position, please send the name and email address to <email@example.com> and <firstname.lastname@example.org>.
The IAB will respond with a questionnaire, asking for the candidates’ qualifications and willingness to serve.
The names of all people who declare themselves willing to serve will be made public on the email@example.com list after the end of the solicitation period. The plan is to post the list of candidates by 4 November 2016.
The IAB expects to make a decision in December 2016.
The IAB has been deliberating the appointment from the IETF community to the ICANN NomCom over the past several weeks. After seeking feedback from the IETF community, the IAB has decided to re-appoint Tim Wicinski to this position.
The IAB extends its sincere thanks to Tim for serving the community in this role.
On 14 September 2016, the IAB posted a statement on the IANA Stewarship Transition: