[nwcrg] Fwd: IAB Workshop Call for Papers: Design Expectations vs. Deployment Reality

Marie-Jose Montpetit <marie@mjmontpetit.com> Sat, 13 April 2019 19:08 UTC

Return-Path: <marie@mjmontpetit.com>
X-Original-To: nwcrg@ietfa.amsl.com
Delivered-To: nwcrg@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 889491202E1 for <nwcrg@ietfa.amsl.com>; Sat, 13 Apr 2019 12:08:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mjmontpetit-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id zejkcBgg2LhB for <nwcrg@ietfa.amsl.com>; Sat, 13 Apr 2019 12:08:48 -0700 (PDT)
Received: from mail-qt1-x82b.google.com (mail-qt1-x82b.google.com [IPv6:2607:f8b0:4864:20::82b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1B7C1200B1 for <nwcrg@irtf.org>; Sat, 13 Apr 2019 12:08:47 -0700 (PDT)
Received: by mail-qt1-x82b.google.com with SMTP id k2so15039285qtm.1 for <nwcrg@irtf.org>; Sat, 13 Apr 2019 12:08:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mjmontpetit-com.20150623.gappssmtp.com; s=20150623; h=from:mime-version:subject:message-id:date:to; bh=k+9sa+xSIMQ4dTgihCPGcQXqG09HBOK+gPUoRFoLQ8U=; b=sO9bHzy7wNPJer09szVliki+tyK98/m/tgBXZVm/qY299Vz9MAsWDzLAIo2X3UjPqE 0NDzNHgJpIeNhy6Yz/wZ73u6b0fEg1DM2DQ/QLxJmD6crOGiMxCuoUzQBlifH3X8kSc7 TRl03NKR1uw659bOpEauWwQPpCmmN3cEds3Q41hjDqkDiTO026ANFC5g7L8yLSwPSeC8 23UKXQmZr269BnoNEb4YMfAxCf0S9dDPiOmWLI1LUNdVRXg6U1I3WRYjnA6rAH3sFvU2 0CKPL3UFy0toYi3TGGeGMl6zRIN9cJUqnwIo025VTDXT1ukibVsgRf9Wbi7xknTnCk3M vRPg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:message-id:date:to; bh=k+9sa+xSIMQ4dTgihCPGcQXqG09HBOK+gPUoRFoLQ8U=; b=CvHNINqLwTMnG4GDd3bEpDfV3hh1q3y37lZ7uzAC4HNQXQ0XhDBrCjBE0t1hqErgK1 TgAAeOlw3bhnNbapM7qMZfFRh4UuSHk4c56tJnjkhjMRiNTdFpZQLYCU1RhNkdLsIKcj gk0EYiSOtjHhoTvoOa4k5+GUw6cd0HHjmeI7GUjocWheYLPlMHjQoAGpdJhyvG6R9Za4 EX4F85rmi7w4kctNzxnVbaMPUB7yYF2udkqshEhP4hQiu68bkswRPZgBlhfY/e7p3s9R 2KGp6zWQc2DsE1QOfGj3kUthdMZwfo0MORjGbCS69CQKGmrCw1ad3w4y+I59olZwV5hJ G5Tg==
X-Gm-Message-State: APjAAAVyB5ARJhZHdCkjIPD1mQshLUUdF3ZK9ExpT3YPaZh3KlGV7lQI fNKgapjV1vOu7fMscBl0o0QIFnUFSpQ=
X-Google-Smtp-Source: APXvYqzK1hy7lN+mIrnFcQYpW2M5BerdA6O+8zZSUoObjFJPuB1nmwinMXTZZOa08j79UfyN+e9xjw==
X-Received: by 2002:a0c:81e2:: with SMTP id 31mr54142788qve.179.1555182526787; Sat, 13 Apr 2019 12:08:46 -0700 (PDT)
Received: from heidi-lamarr.fios-router.home (pool-173-48-150-213.bstnma.fios.verizon.net. []) by smtp.gmail.com with ESMTPSA id u57sm31748692qta.12.2019. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 13 Apr 2019 12:08:46 -0700 (PDT)
From: Marie-Jose Montpetit <marie@mjmontpetit.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_E47F7414-A2F7-4EDF-8C65-B5704DEDFFE1"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Message-Id: <AEC07AED-F523-48BB-92AF-2C1DA480E9B9@mjmontpetit.com>
Date: Sat, 13 Apr 2019 15:08:44 -0400
To: coin@irtf.org, nwcrg <nwcrg@irtf.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/nwcrg/RU4jQJ_Cd7feReYJoAw8Fk7kVSg>
Subject: [nwcrg] Fwd: IAB Workshop Call for Papers: Design Expectations vs. Deployment Reality
X-BeenThere: nwcrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IRTF Network Coding Research Group discussion list <nwcrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/nwcrg>, <mailto:nwcrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nwcrg/>
List-Post: <mailto:nwcrg@irtf.org>
List-Help: <mailto:nwcrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/nwcrg>, <mailto:nwcrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Apr 2019 19:08:50 -0000

Of interest to some of you?

From: IAB Chair <iab-chair@iab.org>
To: ietf@ietf.org, ietf-announce@ietf.org, execd@iab.org
Subject: IAB Workshop Call for Papers: Design Expectations vs. Deployment Reality
Date: Fri, 12 Apr 2019 11:28:40 -0700
Design Expectations vs. Deployment Reality in Protocol Development
A number of protocols have presumed specific deployment models during the development or early elaboration of the protocol.  Actual deployments have sometimes run contrary to these early expectations when economies of scale, DDoS resilience, market consolidation, or other factors have come into play. These factors can result in the deployed reality being highly concentrated.
This is a serious issue for the Internet, as concentrated, centralized deployment models present risks to user choice, privacy, and future protocol evolution.
On occasion, the differences to expectations were almost immediate, but they also occur after a significant time has passed from the protocol’s initial development.
Examples include:
Email standards, which presumed many providers running in a largely uncoordinated fashion, but which has seen both significant market consolidation and a need for coordination to defend against spam and other attacks. The coordination and centralized defense mechanisms scale better for large entities, which has fueled additional consolidation.
The DNS, which presumed deep hierarchies but has often been deployed in large, flat zones, leading to the nameservers for those zones becoming critical infrastructure. Future developments in DNS may see concentration through the use of globally available common resolver services, which evolve rapidly and can offer better security. Paradoxically, concentration of these queries into few services creates new security and privacy concerns.
The Web, which is built on a fundamentally decentralized design, but which is now often delivered with the aid of Content Delivery Networks.  Their services provide scaling, distribution, and Denial of Service prevention in ways that new entrants and smaller systems operators would find difficult to replicate.  While truly small services and truly large ones may operate using only their own infrastructure, many others are left with the only practical choice being the use of a globally available commercial service.
Similar developments may happen with future technologies and services. For instance, the growing use of Machine Learning technology presents challenges for distributing effective implementation of a service throughout a pool of many different providers. 
In RFC 5218 the IAB tackled what made for a successful protocol.  In RFC 8170, the IAB described how to handle protocol transitions.  This workshop will explore cases where the initial system design assumptions turned out to be wrong, looking for patterns in what caused those assumptions to fail (e.g., concentration due to DDoS resilience) and in how those failures impact the security, privacy, and manageability of the resulting deployments.
While the eventual goals might include proposing common remediations for specific cases of confounded protocol expectations, the IAB is currently inviting papers which:
	• Describe specific cases where systems assumptions during protocol development were confounded by later deployment conditions.
	• Survey a set of cases to identify common factors in these confounded expectations.
	• Explore remediations which foster user privacy, security and provider diversity in the face of these changes. 

Important Dates
The workshop will be held June 4-5 in Helsinki, Finland.
Position papers must be submitted by May 3rd at the latest. The program committee will review submitted position papers and send an invitation to the workshop to one of the paper authors. Invitations will be distributed by May 9 at the latest.
Position Paper Requirements
Interested parties must submit a brief document of one to four pages, formatted as HTML, PDF, or plain text. We welcome papers that describe existing work, answers to the questions listed above, new questions, write-ups of deployment experience, lessons-learned from successful or failed attempts, and ideally a vision towards taking deployment considerations better in account when designing new Internet technology. Re-submissions from work presented elsewhere are allowed.
Program Committee
The following persons are IAB contacts for this workshop:
    Jari Arkko
    Stephen Farrell
    Ted Hardie
    Christian Huitema
    Melinda Shore
    Brian Trammell
Position papers should be sent by email to dedr-pc@iab.org.


Marie-Jose Montpetit, Ph.D.