per-entity - RE: [Per-Entity] distribution of aggregate metadata
Subject: Per-Entity Metadata Working Group
List archive
- From: "Cantor, Scott" <>
- To: Nick Roy <>
- Cc: Chris Phillips <>, "Per-Entity Metadata Working Group" <>
- Subject: RE: [Per-Entity] distribution of aggregate metadata
- Date: Thu, 11 Aug 2016 18:03:28 +0000
- Accept-language: en-US
- Authentication-results: spf=pass (sender IP is 164.107.81.208) smtp.mailfrom=osu.edu; canarie.ca; dkim=none (message not signed) header.d=none;canarie.ca; dmarc=bestguesspass action=none header.from=osu.edu;
- Ironport-phdr: 9a23:trWzEROfAlA35ztNulIl6mtUPXoX/o7sNwtQ0KIMzox0K/X5rarrMEGX3/hxlliBBdydsK0UzbeN+Pm9EUU7or+/81k6OKRWUBEEjchE1ycBO+WiTXPBEfjxciYhF95DXlI2t1uyMExSBdqsLwaK+i76xXcoFx7+LQt4IPjuUs6X1pzvlrP6x5qGRQRDh3KHZqI6eBOsqhT5t88KjJFkJ7prjBbFvy0bVf5RwDYiDluVgxHmoo+L95l/724Y7/ko8dJHS+OgV6MjUPpVAClwYDN939HiqRSWFVjH3XAbSGhD10MQWwU=
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
> Endpoint-hosted metadata that is signed by a federation operator starts to
> look a lot like a SAML version of what Roland’s proposing with OpenID
> Connect.
Except that it was SAML's/Liberty's idea to start with, but yes.
The move to batches was a combination of being easier to implement, easier
for deployers, and because it was easier to understand the security
properties.
There was a little bit of "Scott gets hives from mixing locations and names"
mixed in, and you have to work a bit to get back that layer of indirection in
ways that SAML didn't explore because it just went in the other direction.
In practice, nothing does make that distinction, so now your policies about
services have to change when their locations do. Try making attribute release
work in that world. Again, when there are 10 IdPs and they all release
everything to everyone, subject to consent, you sidestep that problem.
We also have the URN problem. Scott doesn't relish changing his IdP's name.
But I digress...
I don't think I would be that concerned about basic CDN reliability in
practice, *if* we're caching on disk. Which we're not at present. So that's
really my take-away, that nobody by and large really believes networks and
CDNs can meet anything above 3-4 9s. and semi-regular but unpredictable
outages are inevitable.
-- Scott
- Re: [Per-Entity] distribution of aggregate metadata, (continued)
- Re: [Per-Entity] distribution of aggregate metadata, Cantor, Scott, 08/11/2016
- Re: [Per-Entity] distribution of aggregate metadata, Chris Phillips, 08/11/2016
- Re: [Per-Entity] distribution of aggregate metadata, Patrick Radtke, 08/11/2016
- RE: [Per-Entity] distribution of aggregate metadata, Cantor, Scott, 08/11/2016
- Re: [Per-Entity] distribution of aggregate metadata, Scott Koranda, 08/11/2016
- Re: [Per-Entity] distribution of aggregate metadata, Nick Roy, 08/11/2016
- Re: [Per-Entity] distribution of aggregate metadata, Chris Phillips, 08/11/2016
- Re: [Per-Entity] distribution of aggregate metadata, Nick Roy, 08/11/2016
- RE: [Per-Entity] distribution of aggregate metadata, Cantor, Scott, 08/11/2016
- Re: [Per-Entity] distribution of aggregate metadata, Nick Roy, 08/11/2016
- RE: [Per-Entity] distribution of aggregate metadata, Cantor, Scott, 08/11/2016
- Re: [Per-Entity] distribution of aggregate metadata, Nick Roy, 08/11/2016
- Re: [Per-Entity] distribution of aggregate metadata, Walter Forbes Hoehn (wassa), 08/11/2016
- Re: [Per-Entity] distribution of aggregate metadata, Tom Scavo, 08/11/2016
- Re: [Per-Entity] distribution of aggregate metadata, Scott Koranda, 08/11/2016
- Re: [Per-Entity] distribution of aggregate metadata, Walter Forbes Hoehn (wassa), 08/11/2016
- RE: [Per-Entity] distribution of aggregate metadata, Cantor, Scott, 08/11/2016
- Re: [Per-Entity] distribution of aggregate metadata, Jorj Bauer, 08/11/2016
- RE: [Per-Entity] distribution of aggregate metadata, Cantor, Scott, 08/11/2016
- Re: [Per-Entity] distribution of aggregate metadata, Jorj Bauer, 08/11/2016
- RE: [Per-Entity] distribution of aggregate metadata, Cantor, Scott, 08/11/2016
Archive powered by MHonArc 2.6.19.