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: Scott Koranda <>
  • To: Patrick Radtke <>
  • Cc: Tom Scavo <>, "Cantor, Scott" <>, "" <>
  • Subject: Re: [Per-Entity] HTTPS transport and TLS trust
  • Date: Tue, 6 Sep 2016 18:44:55 -0500
  • Ironport-phdr: 9a23:wFvZTxQ7SzD3vmeWt2jTb9GIDNpsv+yvbD5Q0YIujvd0So/mwa64ZBKN2/xhgRfzUJnB7Loc0qyN7PCmBDdLuMvJmUtBWaIPfidNsd8RkQ0kDZzNImzAB9muURYHGt9fXkRu5XCxPBsdMs//Y1rPvi/6tmZKSV3XfDB4LeXtG4PUk9//l6Xro8WSME10g2+FaK9oLR615T/YutUVjMM2Mq8t0BrCoVNDev5M2HhpKV+Vgxfg94G7+5s1oApKvPd0zMVHTbmyXKMiRLpUBXxyKGMy/sTtuRDrQg6G539aWWITxEkbSzPZ5Q33C8+i+hDxsfBwjWzDZZX7

> To me the real advantage to the CDN is resilience to targeted attacks
> against the MDQ servers. To me the largest downside is that failure
> modes are now location specific, which can make it hard to provide an
> accurate federation wide status of the service. If the cloudfront edge
> in Toronto is having issues, who would it affect? how would they be
> affected? would Ops be able to determine there was partial outage?,
> etc, etc.

Right. I think that signals a need for Ops to invest in
relationships with the InCommon Participants and leverage them
for monitoring.

Put another way, unlike most other CDN customers, InCommon Ops can
have the advantage of strategically located partners with the
ability to contribute directly to sophisticated monitoring.

Scott K



Archive powered by MHonArc 2.6.19.

Top of Page