per-entity - Re: [Per-Entity] HTTPS transport and TLS trust
Subject: Per-Entity Metadata Working Group
List archive
- From: Nicholas Roy <>
- To: <>
- Subject: Re: [Per-Entity] HTTPS transport and TLS trust
- Date: Fri, 23 Sep 2016 10:04:14 -0600
- Authentication-results: spf=none (sender IP is ) ;
- Ironport-phdr: 9a23:zPgb3BJr/LzMW9N6ktmcpTZWNBhigK39O0sv0rFitYgXLPnxwZ3uMQTl6Ol3ixeRBMOAtKIC1rGd6v2ocFdDyKjCmUhKSIZLWR4BhJdetC0bK+nBN3fGKuX3ZTcxBsVIWQwt1Xi6NU9IBJS2PAWK8TXhpQIVT0HnOBAwK+LpG5LDp8Wx3Oe3/prVJQJSi2zuT6l1KUCQrA7Rsc0fmsNYLbd5nh3TpWpgeuJKyHluKE7J2Rvw+5Hjr9ZY7y1Mtqd5pIZ7WqLgcvFgQA==
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
On 9/6/16 5:16 PM, Tom Scavo wrote:
On Tue, Sep 6, 2016 at 6:51 PM, Scott Koranda
<>
wrote:
[...]I don't disagree but...
If anyone disagrees with that simple analysis please let me
know.
The continued discussion on latency and gathering more numbersI'm not convinced the CDN layer is necessary. My initial timings
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.
suggest the CDN does not provide huge benefit beyond what mdq-beta
alone can provide. More testing is needed, however.
The CDN also has the virtue of offloading the traffic from the Ann Arbor and redundant site networks.
Nick
Tom
- Re: [Per-Entity] HTTPS transport and TLS trust, (continued)
- 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, Scott Koranda, 09/06/2016
- RE: [Per-Entity] HTTPS transport and TLS trust, Paul Caskey, 09/07/2016
Archive powered by MHonArc 2.6.19.