wiki:BostonLocal

Version 18 (modified by rsalz@…, 11 days ago) (diff)

--

IETF Boston-Local Community

The IETF Boston-Local Community first met in May 2015. Boston-Local has approximately 3 technical talks meetings a year and sometimes additional activities a desired.

Anyone interested in participating in the IETF or discussing related technical topics is more than welcome.

Meetings: Oct 2019 June 2018 Jan 2018 Oct 2017

Contact Information

ietf-hub-boston@ietf.org is the mailing list used for coordination and planning for meet-ups.

The Local Coordinators are:

Alia Atlas <akatlas at gmail.com>

Rich Salz <rsalz at akamai.com>

Dale Worley <worley at alum.mit.edu>

How to Give a Talk?

Please do volunteer to give a talk on a topic related to the IETF technologies. We particularly welcome talks about new internet-draft ideas and problems. In a more intimate group, it is easier to have significant discussion. Most talks are 15 minutes with another 15 minutes or more of conversation. Some topics can't possibly be covered in that time, so there's a lot of flexibility.

Scheduled Meetings

  • October 29th, 5-7pm at W3C 105 Broadway (Kendall Square) also known as 10 Cambridge Center

John Kleinsin, does the IETF have a future?

Phill Hallam-Baker, Bitcoin PoW is really WoW

Still have room for 1 or 2 others.

  • October 17, 2017: 5pm - 7pm (continuing into dinner) at The Burren, 247 Elm Street, Somerville, MA

The Burren has beverage and food available. We'll be in the back room.

Please RSVP

Continuous Verification for Cryptographic Protocol Development by Andres Molina-Markham (30 mins)

Abstract: The proliferation of connected devices has motivated a surge in the development of cryptographic protocols to support a diversity of devices and use cases. To address this trend, we propose continuous verification, a methodology for secure cryptographic protocol design that consists of three principles: (1) repeated use of verification tools; (2) judicious use of common message components; and (3) inclusion of verifiable model specifications in standards. Our recommendations are derived from previous work in the formal methods community, as well as from our past experiences applying verification tools to improve standards. Through a case study of IETF protocols for the IoT, we illustrate the power of continuous verification by (i) discovering flaws in the protocols using the Cryptographic Protocol Shapes Analyzer (CPSA); (ii) identifying the corresponding fixes based on the feedback provided by CPSA; and (iii) demonstrating that verifiable models can be intuitive, concise and suitable for inclusion in standards to enable third-party verification and future modifications.

An Introduction to i18n by John Klensin (45 mins)
Discussion on Network Automation and Intent-Based Networking by Dean Bogdanovic (45 mins)
An Outrageous Opinion on Information-Centric Networking (ICN) from the ICN Conference courtesy of Dave Oran (5 min)

  • Jan 16, 2018: 5pm - 7pm (spontaneous dinner afterwards) at 128 Technology, 200 Wheeler Rd, Burlington, MA 01803

Agenda:

Discussion on Bit-Indexed Explicit Replication (BIER) - a new Multicast techology by Jeffrey Zhang (30 mins)
Summary of best things from HotNets? by Dave Oran (10 mins)

  • June 12, 2018: 5pm - 7pm (spontaneous dinner afterwards) at Volta Networks in The Engine, 501 Massachusetts Avenue, Cambridge (Central Square)

Agenda: Discussion on Network Automation and Intent-Based Networking by Dean Bogdanovic (45 mins)
Writing internet-drafts in markdown by Dan York (20 mins)
Routing Around DMARC censorship by John Leslie (40 mins) Abstract: he DMARC Working Group was chartered in 2014, apparently after a DMARC spec was submitted to the Independent Series Editor, to document interop issues and methods to address these, seeking spec changes and a Usage Guide by May of 2015. This hope was abandoned, instead agreeing to publish RFC 7489 unmodified and starting work on an Authenticated Received Chain (ARC) protocol (target date October 2016, still in progress today with the -14 Internet Draft).

The issue of Mailing-List damage was well-known in 2014, but the WG charter required the WG to "seek to preserve interoperability with the installed base". Finally in 2018, the damage to IETF Mailing-Lists became severe enough that IETF leadership decided something must be done, and IETF folks learned that the attempted fix broke "all" Mailing-Lists briefly.

This session will discuss the remediations suggested by the Anti-Spam Research Group and the DMARC Working Group, hopefully with active participation from those present; and propose ways to look at this issue going forward.