Skip to Content.
Sympa Menu

per-entity - Re: [Per-Entity] remaining BIG questions

Subject: Per-Entity Metadata Working Group

List archive

Re: [Per-Entity] remaining BIG questions


Chronological Thread 
  • From: David Walker <>
  • To: <>
  • Subject: Re: [Per-Entity] remaining BIG questions
  • Date: Wed, 14 Sep 2016 12:45:58 -0700
  • Authentication-results: spf=none (sender IP is ) ;
  • Ironport-phdr: 9a23:LFfwjRapWx0to6W9IJjvhkj/LSx+4OfEezUN459isYplN5qZpsW6bnLW6fgltlLVR4KTs6sC0LWG9f27EjVdqb+681k8M7V0HycfjssXmwFySOWkMmbcaMDQUiohAc5ZX0Vk9XzoeWJcGcL5ekGA6ibqtW1aNwvyLzV1J/j4X8v7x4Tyjrjqus6bXwId0CKwe/Z/Kgm3sRT5t88dho5nLaB3zQHG9ChmYeNTkE9hO1Of1yn14sS95tY3/ztZv/Es7eZBV7n3ZaI1UeYeATg7ZTNmrPb3vAXOGFPcrkAXVX8bx18RW1DI
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:99

On 09/14/2016 10:45 AM, Cantor, Scott wrote:
On 9/14/16, 12:20 PM,   wrote:

   I still have a number of unanswered questions regarding the
   distribution of per-entity metadata:
   
   1) Do we need preview-main-fallback servers or is a single production
   server adequate?
Notwithstanding Nick's comment, certainly this could be accomodated in many ways, but I tend to believe it's useful to have this ability, at least preview + main anyway. Preview could perhaps only be available from a single source, perhaps, vs. fully redundant.


I agree with Scott.  To me, the main purpose of preview is to deploy broad changes to the metadata in a way that it can be tested by participants.  The concern is only partially testing of TIER-supported software, but also software that is not supported by TIER, or is configured in an unexpected way.  Perhaps even more important, it allows those tests to observe impacts of metadata changes beyond simple software bugs, for example, attribute release decisions based on some new metadata element that a test IdP has been reconfigured to use.

Attachment: signature.asc
Description: OpenPGP digital signature




Archive powered by MHonArc 2.6.19.

Top of Page