per-entity - Re: [Per-Entity] HTTPS transport and TLS trust
Subject: Per-Entity Metadata Working Group
List archive
- From: Tom Scavo <>
- To: Scott Koranda <>
- Cc: Paul Caskey <>, David Walker <>, "" <>
- Subject: Re: [Per-Entity] HTTPS transport and TLS trust
- Date: Tue, 6 Sep 2016 19:16:20 -0400
- Ironport-phdr: 9a23:KgcPmx/ebLnf1f9uRHKM819IXTAuvvDOBiVQ1KB+2uwcTK2v8tzYMVDF4r011RmSAtWdtqkP0reempujcFJDyK7JiGoFfp1IWk1NouQttCtkPvS4D1bmJuXhdS0wEZcKflZk+3amLRodQ56mNBX660e/5j8KGxj5KRE9ZqGsQtaT3IyL0LWJ8JrPf01rgyC0Z797ZEGtrgLLv88aiKNtL68wzl3CpX4eKMpMwmY9GVWW1y3379m3tMp/6T9bsuwm389GTajgeakkF/pVAClwYDN939HiqRSWFVjH3XAbSGhD10MQWwU=
On Tue, Sep 6, 2016 at 6:51 PM, Scott Koranda
<>
wrote:
>
> [...]
> If anyone disagrees with that simple analysis please let me
> know.
I don't disagree but...
> The continued discussion on latency and gathering more numbers
> and more data is fine, but I don't see that they change
> anything about the approach we will recommend.
>
> Again, if anyone disagrees please say so, but my conclusion
> after seeing the numbers and understanding how clients will
> cache (per our earlier discussions) is that an InCommon MDQ
> service built on a commercial CDN is going to work well.
I'm not convinced the CDN layer is necessary. My initial timings
suggest the CDN does not provide huge benefit beyond what mdq-beta
alone can provide. More testing is needed, however.
Tom
- RE: [Per-Entity] HTTPS transport and TLS trust, (continued)
- RE: [Per-Entity] HTTPS transport and TLS trust, Cantor, Scott, 09/06/2016
- Re: [Per-Entity] HTTPS transport and TLS trust, David Walker, 09/06/2016
- RE: [Per-Entity] HTTPS transport and TLS trust, Paul Caskey, 09/06/2016
- Re: [Per-Entity] HTTPS transport and TLS trust, David Walker, 09/06/2016
- RE: [Per-Entity] HTTPS transport and TLS trust, Paul Caskey, 09/06/2016
- RE: [Per-Entity] HTTPS transport and TLS trust, , 09/06/2016
- RE: [Per-Entity] HTTPS transport and TLS trust, Paul Caskey, 09/06/2016
- Re: [Per-Entity] HTTPS transport and TLS trust, Scott Koranda, 09/06/2016
- Re: [Per-Entity] HTTPS transport and TLS trust, David Walker, 09/06/2016
- Re: [Per-Entity] HTTPS transport and TLS trust, Cantor, Scott, 09/06/2016
- Re: [Per-Entity] HTTPS transport and TLS trust, Scott Koranda, 09/06/2016
- Re: [Per-Entity] HTTPS transport and TLS trust, Tom Scavo, 09/06/2016
- Re: [Per-Entity] HTTPS transport and TLS trust, Nicholas Roy, 09/23/2016
- RE: [Per-Entity] HTTPS transport and TLS trust, Paul Caskey, 09/06/2016
- RE: [Per-Entity] HTTPS transport and TLS trust, Paul Caskey, 09/06/2016
- Re: [Per-Entity] HTTPS transport and TLS trust, Cantor, Scott, 09/06/2016
- RE: [Per-Entity] HTTPS transport and TLS trust, Paul Caskey, 09/06/2016
- Re: [Per-Entity] HTTPS transport and TLS trust, Tom Scavo, 09/06/2016
- Re: [Per-Entity] HTTPS transport and TLS trust, Patrick Radtke, 09/06/2016
- Re: [Per-Entity] HTTPS transport and TLS trust, Scott Koranda, 09/06/2016
- RE: [Per-Entity] HTTPS transport and TLS trust, Paul Caskey, 09/07/2016
- Re: [Per-Entity] HTTPS transport and TLS trust, Nicholas Roy, 09/23/2016
- Re: [Per-Entity] HTTPS transport and TLS trust, David Walker, 09/06/2016
- RE: [Per-Entity] HTTPS transport and TLS trust, Cantor, Scott, 09/06/2016
- Re: [Per-Entity] HTTPS transport and TLS trust, Scott Koranda, 09/06/2016
Archive powered by MHonArc 2.6.19.