IETF Logo Mail Archive

Re: [Coin] challenges for COIN

Marie-Jose Montpetit <marie@mjmontpetit.com> Fri, 01 March 2019 19:22 UTC

Return-Path: <marie@mjmontpetit.com>
X-Original-To: coin@ietfa.amsl.com
Delivered-To: coin@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6AF4130EBE for <coin@ietfa.amsl.com>; Fri, 1 Mar 2019 11:22:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 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, URIBL_BLOCKED=0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KeObBOw5PF8K for <coin@ietfa.amsl.com>; Fri, 1 Mar 2019 11:22:09 -0800 (PST)
Received: from mail-qt1-x832.google.com (mail-qt1-x832.google.com [IPv6:2607:f8b0:4864:20::832]) (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 112D3130EDE for <coin@irtf.org>; Fri, 1 Mar 2019 11:22:09 -0800 (PST)
Received: by mail-qt1-x832.google.com with SMTP id a48so29101774qtb.4 for <coin@irtf.org>; Fri, 01 Mar 2019 11:22:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mjmontpetit-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=bmQl8yKwN1veQeLC2JSDj4seiLt2MFIB+rncFP5gIw0=; b=bcCc8xZfCQJVEqit3fr9zfsKLi+4+r6BvCEzSutzzKQ9TYmMsl0mcthYTzWFxoDuQv bO0o2t32Krs99INM4K2ljS+qVGepT5v50coNlg5VBLseAsWi54i37IvORG4SgJ+g22oQ 6h6jeV8MvrIyipruM/BjZV6LgqWrnx07+pdUGuP9ICWzfizLoSIj2N1Z05NSqdqLlRpM /rXpzVvN9sA6iF/RgxZeHkWX6fabrY2TtDNfO3S/KYFhqRtFNx413AzAfKR6ENti7leD MapOKW8/0gcPEbwAjaONN9c18oGhd+78AWv46kK91FF5EKuFGExcH+4DfV9TDVySlA5C P8jg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=bmQl8yKwN1veQeLC2JSDj4seiLt2MFIB+rncFP5gIw0=; b=uQhHQ4k2ypX3S+CyCzvkumQ/UeTpSooOaj/6vHpjSlxqPK6xLu75mKHfhKkez0KbJp 5H4wUvyf3ABKHej9fVmI/hHfKFtv+dzZHLC/AURWJ9yZzNNoJYYPQy3e5b2gbzGYDynb zoTlva7W7vFo3sNwqNsHW2vO0YBp+LDN9d3OTEfJMUPod+cl9tQrPrMRy2f3OUtTK1+V OH6vc4eLPge1SIhlR5bNKAWIhjc1niwUeWCCA7h2HP8A0/5HALNAEz0ul4SnIrGswyps ASOFgmnJLTKhorMxrDWO89W9xQDKIlkA0s34JrnU2dgtPkkOml/Yp0Rrle+S9F37h5y1 gexg==
X-Gm-Message-State: APjAAAX444UiiY3IhXEji/BnToObl3ZDXf3oTM1mkhujo5n+5wp38mhr wcKhBSL3ILeFO1ntST3uIqRM7w==
X-Google-Smtp-Source: APXvYqzTWznkBdNYDB4a3ZBoiZl1Ph17c5joX3EnVi6nm5R0oEzYiRVLFEu7nsClmAQk66b0dEFi3A==
X-Received: by 2002:ac8:3802:: with SMTP id q2mr5169849qtb.325.1551468127964; Fri, 01 Mar 2019 11:22:07 -0800 (PST)
Received: from heidi-lamarr.fios-router.home (pool-173-48-150-213.bstnma.fios.verizon.net. [173.48.150.213]) by smtp.gmail.com with ESMTPSA id u18sm9687775qka.25.2019.03.01.11.22.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 Mar 2019 11:22:07 -0800 (PST)
From: Marie-Jose Montpetit <marie@mjmontpetit.com>
Message-Id: <E68AB2EA-FC0B-4E4B-969E-0FCC87C5A5A4@mjmontpetit.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_0DD78BEC-743C-4441-AE56-8E7D450D1501"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Fri, 01 Mar 2019 14:22:05 -0500
In-Reply-To: <88D65716-E792-40A1-9427-56B505231350@gmail.com>
Cc: Carsten Bormann <cabo@tzi.org>, Dirk Kutscher <ietf@dkutscher.net>, coin@irtf.org
To: Aaron Falk <aaron.falk@gmail.com>
References: <AB07990D3CAE53419132AB701C45693CD6F3DA2E@dggeml529-mbx.china.huawei.com> <AFB99EE1-699B-45CA-88F2-8DE2B53D802A@dkutscher.net> <72D8741F-C415-4947-8B73-7EC224D04058@tzi.org> <88D65716-E792-40A1-9427-56B505231350@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/coin/zFhQNEgzG6qvmxWLGT-CzR7E60o>
Subject: Re: [Coin] challenges for COIN
X-BeenThere: coin@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "COIN: Computing in the Network" <coin.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/coin>, <mailto:coin-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/coin/>
List-Post: <mailto:coin@irtf.org>
List-Help: <mailto:coin-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/coin>, <mailto:coin-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Mar 2019 19:22:23 -0000

The “trust” delegation is a valid idea that has been proposed elsewhere. So good idea!

Thanks!

mjm 
Marie-Jose Montpetit, Ph.D.
mariejo@mit.edu
marie@mjmontpetit.com
+1-781-526-2661
@SocialTVMIT



> On Mar 1, 2019, at 2:15 PM, Aaron Falk <aaron.falk@gmail.com> wrote:
> 
> On 1 Mar 2019, at 11:02, Carsten Bormann wrote:
> 
> On Mar 1, 2019, at 13:25, Dirk Kutscher <ietf@dkutscher.net> wrote:
> 
> Let’s please forget the notion of “managed networks where privacy and security is not a big problem”.
> 
> +1 (with a very big ONE).
> 
> The usual approach here, however, is
> 
> (1) Somebody dreams up something under that flawed assumption
> (2) This something gets deployed
> (3) Security breaches start to get noticed
> (4) Some very weird usage restrictions are dreamt up to “manage” these security breaches
> (5) Insecure something plus the straightjacket from (4) becomes the new normal
> (6) This becomes the way “real networks are run” by “real engineers”
> (7) All this cannot be questioned any longer and becomes a drag on any further development.
> 
> Examples are galore. I’d offer RFC 6092…
> 
> The flip side of the coin [sic] is that, for research, it is usually quite useful to ignore some requirements, and that may include security.
> 
> I’m happy to see attention onto this topic. Perhaps what is needed for compute to work ‘in the network’ is to have an architecture where (at least) one of the endpoints can delegate trust to elements in ‘the network’ to act on their behalf and audit their actions. IMO, addressing this challenge will make this work (much more) valuable. YMMV, of course.
> 
> --aaron
> 
> -- 
> Coin mailing list
> Coin@irtf.org
> https://www.irtf.org/mailman/listinfo/coin

v2.23.0 | Report a Bug | By Email