Skip to Content.
Sympa Menu

per-entity - RE: [Per-Entity] HTTPS transport and TLS trust

Subject: Per-Entity Metadata Working Group

List archive

RE: [Per-Entity] HTTPS transport and TLS trust


Chronological Thread 
  • From: Paul Caskey <>
  • To: "Cantor, Scott" <>, "" <>
  • Subject: RE: [Per-Entity] HTTPS transport and TLS trust
  • Date: Tue, 6 Sep 2016 23:22:30 +0000
  • Accept-language: en-US
  • Authentication-results: spf=none (sender IP is ) ;
  • Ironport-phdr: 9a23:0sq09hapDB5rHOmQ9/L6Xrb/LSx+4OfEezUN459isYplN5qZpcm7bnLW6fgltlLVR4KTs6sC0LWG9f27EjVdqb+681k8M7V0HycfjssXmwFySOWkMmbcaMDQUiohAc5ZX0Vk9XzoeWJcGcL5ekGA6ibqtW1aMlzFOAF0PuX4HJLJx4Tyjrjqus6bXwIdzhG0Z691NlH+lg7WqtVcyd9pI6AtzQGP+FNPYPkQyG91cxbb1Q7x/IK9+oJi7zV4uvQq8MtFVqO8eL43B/QMFDk8dm0z+Mz3pDHCSwCI434bVCMRiBUeUCbf6xSvZp7stmPRv/F+1TjSadX9RKs3VCWK7qF3RQXuhTtdcTM17TeE2YRLkKtHrUf59FREyInObdTQbaImcw==
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:99

Agreed about that. I would say a regular load-balanced, multi-AZ
(availability zone) AWS setup would work fine.

I don't think a CDN adds much in that case.


> -----Original Message-----
> From:
>
> [
> ]
> On Behalf Of Cantor, Scott
> Sent: Tuesday, September 06, 2016 6:20 PM
> To:
>
> Subject: Re: [Per-Entity] HTTPS transport and TLS trust
>
> On 9/6/16 7:16 PM, Paul Caskey wrote:
> >
> > To the extent that's true, then I would question the need for a CDN,
> > as opposed to a normal highly-available infrastructure (which would be
> > less expensive to operate).
>
> I think the point of the CDN was not performance but in fact availability. I
> thought the issue was that InCommon wasn't comfortable providing that HA
> infrastructure, at least enough that it was thought to be worth
> investigating
> what a CDN would offer and cost.
>
> -- Scott



Archive powered by MHonArc 2.6.19.

Top of Page