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: Tom Scavo <>
  • To: "Cantor, Scott" <>
  • Cc: "" <>
  • Subject: Re: [Per-Entity] HTTPS transport and TLS trust
  • Date: Tue, 6 Sep 2016 19:24:22 -0400
  • Ironport-phdr: 9a23:+8Sw4hwBCDVQ5PjXCy+O+j09IxM/srCxBDY+r6Qd0uMQIJqq85mqBkHD//Il1AaPBtqLra8fwLOL+4nbGkU+or+5+EgYd5JNUxJXwe43pCcHRPC/NEvgMfTxZDY7FskRHHVs/nW8LFQHUJ2mPw6aijSI4DUTAhTyMxZubqSwQ9aKzpf/6+fnsbbaZRlPnn71Wrh1MAn85VHav88KhpEkcI420QaPr3dVLbd432RtcG6Uml7H7c6u+9Y37z5LsPs/8OZBV7n3ZaI1UeYeATg7ZTNmrPb3vAXOGFPcrkAXVX8bx18RW1DI

On Tue, Sep 6, 2016 at 7:19 PM, Cantor, Scott
<>
wrote:
> 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.

Well, our initial thought was to enable AWS Elastic Load Balancer for
automatic failover. It has not been tried, however, so I don't know if
it works as advertised.

Tom



Archive powered by MHonArc 2.6.19.

Top of Page