Re: [icnrg] Question about draft-irtf-icnrg-deployment-guidelines
"David R. Oran" <daveoran@orandom.net> Fri, 07 September 2018 12:26 UTC
Return-Path: <daveoran@orandom.net>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62841124D68 for <icnrg@ietfa.amsl.com>; Fri, 7 Sep 2018 05:26:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 Wj_yl56ggzEl for <icnrg@ietfa.amsl.com>; Fri, 7 Sep 2018 05:26:44 -0700 (PDT)
Received: from spark.crystalorb.net (spark.crystalorb.net [IPv6:2607:fca8:1530::c]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8594A12872C for <icnrg@irtf.org>; Fri, 7 Sep 2018 05:26:44 -0700 (PDT)
Received: from [192.168.171.1] ([IPv6:2601:184:4081:19c1:57c:369c:4671:7aa0]) (authenticated bits=0) by spark.crystalorb.net (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id w87CPrcf020707 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NO); Fri, 7 Sep 2018 05:25:55 -0700
From: "David R. Oran" <daveoran@orandom.net>
To: Marie-Jose Montpetit <marie@mjmontpetit.com>
Cc: "Trossen, Dirk" <Dirk.Trossen@InterDigital.com>, icnrg <icnrg@irtf.org>
Date: Fri, 07 Sep 2018 08:25:52 -0400
X-Mailer: MailMate (1.11.3r5520)
Message-ID: <EF8F72F3-F4E1-4A6A-815D-D93B3CE2041F@orandom.net>
In-Reply-To: <0A9520BD-8667-48B9-B790-110734351E88@mjmontpetit.com>
References: <65301FED-F5B8-451C-B42E-E6EE7950B204@mjmontpetit.com> <CO2PR10MB000753EFE64F5190B83C48FFF3000@CO2PR10MB0007.namprd10.prod.outlook.com> <0A9520BD-8667-48B9-B790-110734351E88@mjmontpetit.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/gXCpSPv_WxAfhNEi04kSRyOtHII>
Subject: Re: [icnrg] Question about draft-irtf-icnrg-deployment-guidelines
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/icnrg/>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Sep 2018 12:26:47 -0000
On 7 Sep 2018, at 5:30, Marie-Jose Montpetit wrote: > I will re-resed any thing about security then and see how the content > is protected in the ICN and see if (like we did) in P2P (well is was > social content consumption) if extra signatures can be added. For TV > and video the studios have their own mechanisms but this is not what I > am looking into (at least no now). > I don’t see this as a topic for a deployment document, so I’m not sure where you’re going with the question. If you depend on deployment characteristics/details to obtain important security/privacy/rights properties it is almost certainly too late and not going to be robust. Given that we have object-based security in ICN (with selective encryption at the application layer) it seems that any solution that even minimally depends on where the bits wind up being transmitted or stored would not comport well with the architecture. In fact, these properties are a major part what sets ICN apart from IP-based CDN systems. In the message below, I read in that the concern you are raising is about proving ownership and not protection against piracy, correct? Both need careful attention to the key management; the former in the distribution and lifetime of the encryption keys; the latter in the proof and ownership of the signing keys. Maybe you could take another swipe at explaining the scenarios you are considering and how they might interact with how an ICN system gets deployed. Cheers, DaveO. > Thanks > > mjm > Marie-Jose Montpetit, Ph.D. > mariejo@mit.edu > marie@mjmontpetit.com > +1-781-526-2661 > @SocialTVMIT > > > >> On Sep 7, 2018, at 2:13 AM, Trossen, Dirk >> <Dirk.Trossen@InterDigital.com> wrote: >> >> Hi Marie-Jose, >> >> Interesting question but, in this case (considering deployment >> options at the architecture level), I would consider that you provide >> already the right answer: it's not really part of it. >> >> Best, >> >> Dirk >> >> -----Original Message----- >> From: icnrg [mailto:icnrg-bounces@irtf.org] On Behalf Of Marie-Jose >> Montpetit >> Sent: 07 September 2018 04:29 >> To: icnrg <icnrg@irtf.org> >> Subject: [icnrg] Question about >> draft-irtf-icnrg-deployment-guidelines >> >> Hi: >> >> ahead of the interim meeting I was re-reading the >> draft-irtf-icnrg-deployment-guidelines in the context of some >> AR/VR/MR and multisource multidestination apps I am working on. One >> aspect that is not clear to me is what happens when content that has >> rights management (or local distribution ruiles) is distributed with >> ICN (books, video, VR games etc.). I remembered a convoluted solution >> that we had to use for P2P distribution of TV signals way back. >> >> Did I miss something or it’s not really part of it? >> >> Thanks >> >> mjm >> >> Marie-Jose Montpetit, Ph.D. >> mariejo@mit.edu >> marie@mjmontpetit.com >> +1-781-526-2661 >> @SocialTVMIT >> >> >> >> _______________________________________________ >> icnrg mailing list >> icnrg@irtf.org >> https://www.irtf.org/mailman/listinfo/icnrg >> _______________________________________________ >> icnrg mailing list >> icnrg@irtf.org >> https://www.irtf.org/mailman/listinfo/icnrg > _______________________________________________ > icnrg mailing list > icnrg@irtf.org > https://www.irtf.org/mailman/listinfo/icnrg DaveO
- [icnrg] Question about draft-irtf-icnrg-deploymen… Marie-Jose Montpetit
- Re: [icnrg] Question about draft-irtf-icnrg-deplo… Trossen, Dirk
- Re: [icnrg] Question about draft-irtf-icnrg-deplo… Marie-Jose Montpetit
- Re: [icnrg] Question about draft-irtf-icnrg-deplo… David R. Oran