From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [52.28.52.200]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id DA3B33CB36 for ; Wed, 17 Apr 2019 10:56:47 -0400 (EDT) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1555513006; bh=e8SH/R0dWf1swhdODwDzwmkbBf45thuoDauuKshOUdM=; h=From:To:Subject:Date:From; b=OuP6aDctkIO/JuRlrZBzasO1v14JapP76lhmC0GtF+yuop4DGrOdaauT6ox61ewq+ O9wMUIBsV06IgH8o1o0m/LgVGtxTjpcBm1MwnwR6du6DW67qmN8c9RiqEJ/fakEAqO jBW2EtG7ZOqLzBTx+WQN8xye0ECZkZES5ennc7I66CeBxGzG4mHIBNOvrlOBxDqLni bNY038BE8yQ0EZZV6OEnBBfg1IGmdAjFQ3nhzRd3mT2m+tP41MM+URGYXPtjOPdeO5 0jJM/4HIbNjVbCNeZas/m4KHgB4kaf4KgMsNTVM308pEUSBcrugMdHytjjvhmNkAVC IAP0RDZPUEGKA== To: bloat@lists.bufferbloat.net Date: Wed, 17 Apr 2019 15:56:44 +0100 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87ef60r87n.fsf@toke.dk> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Subject: [Bloat] Fwd: [Maprg] FW: IAB Workshop Call for Papers: Design Expectations vs. Deployment Reality X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Apr 2019 14:56:48 -0000 --=-=-= Content-Type: text/plain Figure there may be a few people on this list that might have opinions about this... :) -Toke --=-=-= Content-Type: message/rfc822 Content-Disposition: inline Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on mail.toke.dk X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-101.9 required=5.0 tests=BAYES_00,SHORTCIRCUIT shortcircuit=ham autolearn=disabled version=3.4.2 Delivered-To: toke@toke.dk Received: from mail.toke.dk by mail.toke.dk with LMTP id QFVzFTUwt1x/OQAAOr1fkg (envelope-from ) for ; Wed, 17 Apr 2019 15:55:01 +0200 Authentication-Results: mail.toke.dk; spf=pass (mailfrom) smtp.mailfrom=irtf.org (client-ip=4.31.198.44; helo=mail.ietf.org; envelope-from=maprg-bounces@irtf.org; receiver=) Authentication-Results: mail.toke.dk; dkim=pass (1024-bit key) header.d=ietf.org header.i=@ietf.org header.b=QpXB0Tpm; dkim=pass (1024-bit key) header.d=ietf.org header.i=@ietf.org header.b=EAk89p94; dkim=fail reason="signature verification failed" (1024-bit key) header.d=ericsson.com header.i=@ericsson.com header.b=MPKLja4R Received: from mail.ietf.org (mail.ietf.org [4.31.198.44]) by mail.toke.dk (Postfix) with ESMTPS id 5A636603A2A for ; Wed, 17 Apr 2019 15:54:57 +0200 (CEST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C55A1205CD for ; Wed, 17 Apr 2019 06:54:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1555509295; bh=ww4mAeEfCmyU0gXo6E/z8ttr1TdUl6h2WWLXctJ8L5s=; h=From:To:Date:References:In-Reply-To:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe; b=QpXB0Tpmh/PzOQoAhRVbTlZIOCJgCqCyiNCEZ/EkPv8yAvzwSUS14NlihD0O+pywj 0rfCQetdRaToWuPOHTpqJ9EP2svldP8SGOVhMJcGfjhdyUzNFOiWtwMR/9ImmHGjvr 9P61uIsQp/VDnA9YskOhRQL6m5krhuYgFTb07x7Y= X-Mailbox-Line: From maprg-bounces@irtf.org Wed Apr 17 06:54:48 2019 Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 925AE1201BB; Wed, 17 Apr 2019 06:54:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1555509288; bh=ww4mAeEfCmyU0gXo6E/z8ttr1TdUl6h2WWLXctJ8L5s=; h=From:To:Date:References:In-Reply-To:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe; b=EAk89p94Q1Am8n7kdHm5O9ApgkdfRs6V/wvn/CufcxAVaH5fSxDPvPBptVpbfQIL/ vN3pCehkzeTCaK73aeA/yyL7H28/i93VZw/OY83QIZvYgJIgEGFzGmkL78g8izzIny N8tzQSEBpu2pXO4VlckoX4SUJ0jl9TxU1qK/bxeg= X-Original-To: maprg@ietfa.amsl.com Delivered-To: maprg@ietfa.amsl.com X-Virus-Scanned: amavisd-new at amsl.com Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com Received: from FRA01-MR2-obe.outbound.protection.outlook.com (mail-eopbgr90041.outbound.protection.outlook.com [40.107.9.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A52E120104 for ; Wed, 17 Apr 2019 06:54:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=FYVMHkDeL4/2oUJhdH82F8prMEnN25VqWrOnycdruG4=; b=MPKLja4REe8O8nneGYBy/RL3We9x1xwk4e6YRdY5kLBv+w89a8tBjxWbIwxiujE5bhW9wNpp9AXe9LjlCu0MAZPHRN+e2My1rQBoJV/yVupXOtFVA5z4HA5cNmljNHLwlxcR9pmLLNvJWFGSFtEzDsic7vn/XsvGzCtga5tR7Bc= Received: from PR1PR07MB5898.eurprd07.prod.outlook.com (20.177.212.19) by PR1PR07MB4938.eurprd07.prod.outlook.com (20.177.210.24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1813.9; Wed, 17 Apr 2019 13:54:39 +0000 Received: from PR1PR07MB5898.eurprd07.prod.outlook.com ([fe80::9d5b:fab9:4cc2:2f0d]) by PR1PR07MB5898.eurprd07.prod.outlook.com ([fe80::9d5b:fab9:4cc2:2f0d%5]) with mapi id 15.20.1813.009; Wed, 17 Apr 2019 13:54:39 +0000 From: Mirja Kuehlewind To: "maprg\@irtf.org" Thread-Topic: IAB Workshop Call for Papers: Design Expectations vs. Deployment Reality Thread-Index: AQHU8V29EBiHoww4YECMxF7YBTDVDKZAiP0A Date: Wed, 17 Apr 2019 13:54:39 +0000 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <49B5C5A0-4605-4BF0-AC51-43235C02AACD@ericsson.com> References: <7fe7b482-62c6-f998-e3de-034b0d7bcd90@iab.org> In-Reply-To: <7fe7b482-62c6-f998-e3de-034b0d7bcd90@iab.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=mirja.kuehlewind@ericsson.com; x-originating-ip: [129.192.10.2] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 32f1649a-b255-43e1-fff7-08d6c33c3c1d x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600140)(711020)(4605104)(2017052603328)(7193020); SRVR:PR1PR07MB4938; x-ms-traffictypediagnostic: PR1PR07MB4938: x-ms-exchange-purlcount: 3 x-microsoft-antispam-prvs: x-forefront-prvs: 0010D93EFE x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(376002)(39860400002)(136003)(396003)(366004)(199004)(189003)(6436002)(6486002)(66066001)(76176011)(229853002)(446003)(476003)(36756003)(2501003)(68736007)(14454004)(81166006)(11346002)(33656002)(486006)(66574012)(81156014)(8676002)(99286004)(2616005)(8936002)(1730700003)(316002)(6116002)(3846002)(2906002)(6916009)(86362001)(5640700003)(2473003)(5660300002)(256004)(14444005)(966005)(82746002)(105586002)(2351001)(478600001)(106356001)(25786009)(6512007)(6306002)(44832011)(6506007)(186003)(97736004)(102836004)(83716004)(53936002)(305945005)(71190400001)(7736002)(26005)(71200400001)(225293001); DIR:OUT; SFP:1101; SCL:1; SRVR:PR1PR07MB4938; H:PR1PR07MB5898.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: fw6IguWswOYfllfJtnhBmkaK1sXtUJvLc6sbXCcJtOefuI3XHwwCmQWvuGDeah/Ytk5dPdMB2kAXbTJbq2gVBx0QZ7Er8iIxlOrbWzH/59pK2o75j5FhkACJxPSUvMrYDQEqTu+lbTCC/i5pbsFVr2ppUSTluZy5MWGYi+F1VB/hVIWh7LKKIiVh70WVY92SibYjKm5Psn+2XyQX4tBK9Q7h6QCiAKjDaP8FIP4EASvL2GvT+jw7Eay3e+p+uOjosMYA+/1LXMXpyjnwjwgpC3FIw44dyJKWtA2MQY0njwD/7Id8d6j6OnKSlPixbzOZCfaWMl4GHdDBIcszciVWNwne0LJbW1SL4KgIAd6d0HkP7pK4d6XSVEBdD8WAI6CbSIlDaPUz4s89JrqOUlkZWZX3nvAQs+B2+aSHUSrwDiM= Content-ID: <9C262CFCB38CF641A67025AC0477A978@eurprd07.prod.outlook.com> X-OriginatorOrg: ericsson.com X-MS-Exchange-CrossTenant-Network-Message-Id: 32f1649a-b255-43e1-fff7-08d6c33c3c1d X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Apr 2019 13:54:39.2446 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-Transport-CrossTenantHeadersStamped: PR1PR07MB4938 Archived-At: X-Topics: CfP Subject: [Maprg] FW: IAB Workshop Call for Papers: Design Expectations vs. Deployment Reality X-BeenThere: maprg@irtf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Measurement and Analysis for Protocols \(MAP\) \(Proposed\) RG mailing list" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: maprg-bounces@irtf.org Sender: "Maprg" MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi folks, please see a call for (position) papers for an IAB workshop on Design Expec= tations vs. Deployment Reality below. This could be particular interesting = for this groups as what is usually measured is deployment reality part of t= he questions targeted below.=20 Submission deadline is already May 3, however, a short summary of deploymen= t problem you have detected in an eventually already published study would = be sufficient.=20 The workshop will be on June 4/5 in Helsinki. Find more information below a= lso here: https://www.iab.org/activities/workshops/dedr-workshop/=20 Mirja =EF=BB=BFOn 12.04.19, 20:30, "IETF-Announce on behalf of IAB Chair" wrote: Design Expectations vs. Deployment Reality in Protocol Development =20=20=20=20 A number of protocols have presumed specific deployment models during = the development or early elaboration of the protocol. Actual deployments h= ave sometimes run contrary to these early expectations when economies of sc= ale, DDoS resilience, market consolidation, or other factors have come into= play. These factors can result in the deployed reality being highly concen= trated. =20=20=20=20 This is a serious issue for the Internet, as concentrated, centralized = deployment models present risks to user choice, privacy, and future protoco= l evolution. =20=20=20=20 On occasion, the differences to expectations were almost immediate, but= they also occur after a significant time has passed from the protocol=E2= =80=99s initial development. =20=20=20=20 Examples include: =20=20=20=20 Email standards, which presumed many providers running in a largely unc= oordinated fashion, but which has seen both significant market consolidatio= n and a need for coordination to defend against spam and other attacks. The= coordination and centralized defense mechanisms scale better for large ent= ities, which has fueled additional consolidation. =20=20=20=20 The DNS, which presumed deep hierarchies but has often been deployed in= large, flat zones, leading to the nameservers for those zones becoming cri= tical infrastructure. Future developments in DNS may see concentration thro= ugh the use of globally available common resolver services, which evolve ra= pidly and can offer better security. Paradoxically, concentration of these = queries into few services creates new security and privacy concerns. =20=20=20=20 The Web, which is built on a fundamentally decentralized design, but wh= ich is now often delivered with the aid of Content Delivery Networks. Thei= r services provide scaling, distribution, and Denial of Service prevention = in ways that new entrants and smaller systems operators would find difficul= t to replicate. While truly small services and truly large ones may operat= e using only their own infrastructure, many others are left with the only p= ractical choice being the use of a globally available commercial service. =20=20=20=20 Similar developments may happen with future technologies and services. = For instance, the growing use of Machine Learning technology presents chall= enges for distributing effective implementation of a service throughout a p= ool of many different providers. =20=20=20=20 In RFC5218 the IAB tackled what m= ade for a successful protocol. In RFC 8170 , the IAB described how to handle protocol transitions. This worksho= p 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 imp= act the security, privacy, and manageability of the resulting deployments. =20=20=20=20 While the eventual goals might include proposing common remediations fo= r specific cases of confounded protocol expectations, the IAB is currently = inviting papers which: =20=20=20=20 * Describe specific cases where systems assumptions during protocol dev= elopment were confounded by later deployment conditions. =20=20=20=20 * Survey a set of cases to identify common factors in these confounded = expectations. =20=20=20=20 * Explore remediations which foster user privacy, security and provider= diversity in the face of these changes. =20=20=20=20 Important Dates =20=20=20=20 The workshop will be held June 4-5 in Helsinki, Finland. =20=20=20=20 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 b= y May 9 at the latest. =20=20=20=20 Position Paper Requirements =20=20=20=20 Interested parties must submit a brief document of one to four pages, f= ormatted as HTML, PDF, or plain text. We welcome papers that describe exist= ing work, answers to the questions listed above, new questions, write-ups o= f deployment experience, lessons-learned from successful or failed attempts= , and ideally a vision towards taking deployment considerations better in a= ccount when designing new Internet technology. Re-submissions from work pre= sented elsewhere are allowed. =20=20=20=20 Program Committee =20=20=20=20 The following persons are IAB contacts for this workshop: =20=20=20=20=20=20 Jari Arkko Stephen Farrell Ted Hardie Christian Huitema Melinda Shore Brian Trammell =20=20=20=20 Position papers should be sent by email to=20 dedr-pc@iab.org . =20=20=20=20 _______________________________________________ Maprg mailing list Maprg@irtf.org https://www.irtf.org/mailman/listinfo/maprg --=-=-=--