Minutes of the 2016-12-14 IAB Teleconference (Tech Chat & Business Meeting)
1. Roll-call, agenda-bash, administrivia, minutes
- Jari Arkko (IETF Chair)
- Michelle Cotton
- Ralph Droms
- Heather Flanagan (RFC Editor Liaison)
- Mat Ford (ISOC Liaison)
- Ted Hardie
- Joe Hildebrand
- Russ Housley
- Lee Howard
- Suresh Krishnan (IESG Liaison)
- Allison Mankin (incoming IRTF Chair)
- Cindy Morgan (IAB Executive Administrative Manager)
- Erik Nordmark
- Robert Sparks
- Andrew Sullivan (IAB Chair)
- Dave Thaler
- Martin Thomson
- Brian Trammell
- Amy Vezza (IETF Secretariat)
- Suzanne Woolf
- Lars Eggert (IRTF Chair)
- Adrian Perrig
Two new items were added to the agenda.
1.3. Meeting Minutes
The minutes of the 7 December 2016 business meeting were approved.
2. Tech Chat: Architectural Transition and Planning for Partial Deployment of a Future Internet Architecture
Adrian Perrig joined the IAB to talk about the SCION (Scalability, Control, and Isolation On Next-Generation Networks) Architecture. There is a belief that the Internet is immutable. Benefits are limited, especially for early adopters. The goal is to provide so many benefits, even for early adopters, such that one cannot turn back (e.g., the transition to smart phones).
SCION’s architectural design goals include:
- High availability, even for networks with malicious parties
- Secure entity authentication
- Flexible trust
- Transparent operation
- Balanced control among ISPs, senders, and receivers
- Scalability, efficiency, and flexibility
SCION’s Trust Root Configuration (TRC) is such that each isolation domain (ISD) defines a set of trust roots for different operations. The TRC file is used to bootstrap trust on a host. The TRC contains the policy for updating each PKI’s roots of trusts.
SCION is a complete re-design of the network architecture to resolve numerous fundamental problems, such as:
- BGP protocol convergence issues
- Separation of control and data planes
- Isolation of mutually untrusted control planes
- Path control by senders and receivers
- Simpler routers (no forwarding tables)
- Root of trust selectable by each ISD
SCION is an isolation architecture for the control plane, but a transparency architecture for the data plane.
Adrian Perrig said that SCION has a chance for adoption because it has tangible properties and improvements over the present Internet to drive adoption, such as:
- Multipath communication
- High availability, DDoS defense
- Transparency and control over paths for senders
- Strong security guarantees
Additionally, there is no global coordination required to adopt SCION, and there are no IPR constraints on adoption.
Jari Arkko asked if isolation domains might lead to Internet fragmentation, where there could be a different Internet in Switzerland versus China. Adrian Perrig replied that the isolation domains are expected to grow organically and overlap with each other. End users would be able to inspect the routes of trust.
Erik Nordmark asked what the scope of future work on SCION is. Adrian Perrig replied that the last six years have been spent on the basic architecture, but a lot of research is still needed on path construction beacon messages, and what information should be added to those.
Allison Mankin asked how much network measurement has been done during the SCION trials. Adrian Perrig replied that they are conducting real-world measurement right now.
For more details on SCION, please see <https://www.scion-architecture.net/>.
3. Monthly Reports
3.1. ISOC Liaison Report
–Begin ISOC Liaison Report, Mat Ford–
–End ISOC Liaison Report, Mat Ford–
3.2. IRTF Chair Report
–Begin IRTF Chair Report, Lars Eggert–
* ANRP 2017 nomination period ending Nov 6. Out of the 39 submissions for the 2017 ANRPs, six were awarded a prize. The nominees have been notified, and travel planning is underway. * The proposed Network Machine Learning will not be chartered, and the mailing list has closed.
–End IRTF Chair Report, Lars Eggert–
3.3. IANA Liaison Report
–Begin IANA Liaison Report, Michelle Cotton–
IANA Services Liaison Report – 14 December 2016 SLA Deliverables Update: - ICANN met 99% of processing goal times for the October 2016 and 96% of processing goal times for the November 2016 monthly statistics reports, exceeding the SLA goal to meet 90% of processing goal times. These times include the steps that ICANN has control over and not time it is waiting on requesters, document authors or other experts. - The 2017 Supplemental Agreement is currently being drafted and will be reviewed by ICANN and IETF/IAB Leadership in the coming weeks. This Supplemental Agreement between ICANN and the IETF is projected to be signed in March 2017. - With the expiration of the NTIA IANA Functions contract on September 30, 2016, the annual review of protocol parameter requests as detailed in the SLA (completed through a SOC 2 audit review) will be completed 2 months early to end with the IANA Functions contract time-period. Future annual reviews will follow the new time-period October 1– September 30. Other News: - The report based on the 2016 Customer Satisfaction Survey for the IANA Services has been completed and the report will be posted in late December 2016. - All protocol parameter operational reports will continue to be posted on the iana.org website, and PTI Board information will be posted on pti.icann.org.
–End IANA Liaison Report, Michelle Cotton–
3.4. RFC Editor Liaison Report
–Begin RFC Editor Liaison Report, Heather Flanagan–
RFC Editor Liaison Report, October 2016 RFC Series Editor update - Format update The various format drafts are wrapping up their AUTH48 actions; the goal is to have the documents published in time for IETF 97. A link to the document cluster for all format drafts is here: https://www.rfc- editor.org/cluster_info.php?cid=C294 The response period for the RFC Format Tools RFP has closed. The Tools Management Committee is discussing the proposals received and hope to have a recommendation to the IAOC in time for IETF 97. The related RFP for the CSS was awarded to Spherical Cow Group; work has begun on that aspect of the format project. - Digital Signatures for RFCs Due to some uncertainty about the overall security aspects of the digital signature project, specifically around the handling of signing key revocation, further work on the digital signature project is on hold until key stakeholders can meet face to face immediately before IETF 97. An updated proposal will be drafted after that discussion happens. - IETF 97 The RSE will hold office hours at the RFC Editor desk on Monday afternoon and Wednesday morning. RPC update - SLA See: https://www.rfc-editor.org/report-summary/ The RPC met the SLA at Tier 2 for Q3. Q4 2016: So far, Q4 has been quite busy, as the Format-related documents have moved to AUTH48, an expedited request for https:// datatracker.ietf.org/doc/draft-ietf-netmod-routing-cfg/ has been received, and a legal request has been received. In addition, the RFC Editor is preparing for the upcoming IETF 97. - Staffing The RFC Editor requested funding for an additional editor because of the increased format-related workload expected in 2017. The IAOC has approved funding for July 2017 - December 2018. Background: There is a significantly increased workload associated with the transition to xml2rfc v3 for the RPC. In addition to the editor team learning the v3 vocabulary and new tools, the team needs to generate new procedures, update the RFC Editor website regarding process, update their database to accommodate the multiple file formats, and continue to simultaneously publish RFCs using the existing v2 vocabulary and tools. - RFC Editor Liaison Report, November 2016 RFC Series Editor update Format The IAOC is still discussing the bids for the RFC Format tools work. While those bids are under discussion, the work for the CSS has started and an initial draft of the proposed look and feel has been released for public comment (https://rfc-format.github.io/draft-iab-rfc-css-bis/sample.html). Feedback is being collected via rfc-interest and on github (https://github.com/rfc-format/draft-iab-rfc-css-bis/issues). Digital preservation The data feed that allows the National Library of Sweden to ingest RFCs into their digital repository has been complete. All past RFCs are now archived in that repository, and all new RFCs will be added as they are published. Digital signatures After several discussions over the course of IETF 97, the RFC Series Editor and the RSOC agreed to move the digital signature project to "dormant.". The goal of the project was to save the RPC time in responding to subpoenas. Given the current state of understanding around digital signatures in the legal community, the variation of proposed expected practice in different jurisdictions, and the complexity of both signing and verifying signatures over time, the goal of saving time cannot be realized at this point. If and when technology and policy change around digital signatures, we will review this project again. RPC update - SLA See: https://www.rfc-editor.org/report-summary/ The RPC is meeting the SLA at Tier 1 for Q4. - Staffing Given the expected timing for the RFC Format project, the RFC Editor has requested that the actual addition of the additional editor, approved for July 2017-December 2018, be delayed until approximately three months before the new format is expected to go into production (18 months after the coding starts). - IANA The RPC is working with the IANA Services Operator to understand any impact on RFC language based on the IANA IPR agreement.
–End RFC Editor Liaison Report, Heather Flanagan–
4. Future Tech Plenaries
Allison Mankin reported that Dave Clark has accepted the IAB’s invitation to speak at the IETF 98 plenary. The Plenary Planning Program will follow up on this.
Mat Ford will upload a new revision of draft-iab-carisreport that incorporates the comments received to date.
Dave Thaler reported that he has uploaded a new revision of draft-iab-protocol-transitions that incorporates the comments received to date with one exception; that comment was not addressed in the document because Dave could not come up with a way to generalize the comment enough for the document. The IAB agreed to review draft-iab-protocol-transitions-04 and decide whether it is ready for community review, and to think about whether there is a way to incorporate that last comment into the document.
7. Process for IAB Review under RFC 4846
The IAB received a request under RFC 4846 to review a draft that the Independent Stream Editor declined to publish. Robert Sparks and Ted Hardie will send a message to the ISE asking for the rationale for not publishing the document. The IAB will discuss potential additional reviewers of the document on the IAB list.
Suzanne Woolf reported that draft-ietf-homenet-dot is currently in Working Group Last Call; the WGLC was cross-posted to the DNSOP list. Comments are starting to come in against the request to ask IANA for an update to the root zone to support an unsigned delegation of .homenet to IANA name servers and AS112. Suzanne and Suresh Krishnan will follow up with the IESG to make sure they are aware of the concerns about that request.
9. Followup on IAB appointments
Robert Sparks reported that Nevil Brownlee has accepted the reappointment as Independent Series Editor for a one-year term beginning in February 2017. Cindy Morgan will send a formal announcement.
Cindy Morgan reported that Kaveh Ranjbar has accepted the appointment to the IAOC for a two-year term beginning at IETF 98. Cindy will send a formal announcement.