per-entity - Re: [Per-Entity] implementing a cache on the client

Subject: Per-Entity Metadata Working Group

List archive

Re: [Per-Entity] implementing a cache on the client

From: "Cantor, Scott" <>
To: Tom Scavo <>
Cc: Nick Roy <>, David Walker <>, "" <>
Subject: Re: [Per-Entity] implementing a cache on the client
Date: Thu, 28 Jul 2016 23:27:02 +0000
Accept-language: en-US
Authentication-results: spf=pass (sender IP is 164.107.81.218) smtp.mailfrom=osu.edu; incommon.org; dkim=none (message not signed) header.d=none;incommon.org; dmarc=bestguesspass action=none header.from=osu.edu;
Spamdiagnosticmetadata: NSPM
Spamdiagnosticoutput: 1:99

On 7/28/16 7:11 PM, Tom Scavo wrote:
>
> Yes, and eliminate the signing key and cert from the MDQ server
> altogether. The pull system we've deployed on mdq-beta is probably not
> the way to go. We should push signed metadata from a secure location
> (like UKf is doing) to an MDQ server with a TLS key as described
> above. This need not be a phase 1 feature in any case.

Yes, I think we expected we'd document both general approaches, but I
don't think there's much doubt about that direction being the best one
for all sorts of reasons.

-- Scott

RE: [Per-Entity] implementing a cache on the client, (continued)

List archive

Re: [Per-Entity] implementing a cache on the client