InCommon Operations Notifications

[Thomas Scavo <>]

HTTP compression has been enabled on the following aggregates as of the dates 
shown:

April 7: Preview aggregate
April 11: IdP-only aggregate
April 18: Main aggregate

Since the server configuration has been stable for over three (3) weeks, the 
fallback aggregate will be enabled for compression on Thursday, May 11. This 
will complete the deployment of HTTP compression on md.incommon.org.

If you have any questions or concerns, please contact us at 


Tom
________________________________________
From: 

 
<>
 on behalf of Thomas Scavo 
<>
Sent: Monday, April 17, 2017 9:07:15 AM
To: 

Subject: [InCommon NOTICE] Re: enabling HTTP Compression on md.incommon.org

HTTP Compression has been enabled on both the Preview Aggregate and the 
IdP-only Aggregate. Likewise we will enable compression on the Main Aggregate 
tomorrow, Tuesday, April 18. If you have any questions or experience any 
issues, please contact us at 


After Tuesday, only the Fallback Aggregate will not be compression-enabled. 
We will keep it that way for a couple of weeks until we’re sure the migration 
has been successful. We’ll let you know when the Fallback Aggregate is 
scheduled for the final transition.

Visit this new wiki page for more info re HTTP Compression: 
https://spaces.internet2.edu/x/sI2TBg

Tom

________________________________________
From: 

 
<>
 on behalf of Thomas Scavo 
<>
Sent: Wednesday, April 5, 2017 9:08 AM
To: 

Cc: InCommon Administration
Subject: [InCommon NOTICE] enabling HTTP Compression on md.incommon.org

You are receiving this message because you are an InCommon Site Administrator 
(or are otherwise subscribed to this mailing list). This message is FYI only.

The InCommon metadata aggregate is approaching 43MB and continues to grow. To 
compensate, InCommon Operations will enable HTTP Compression [1] on the 
metadata server (md.incommon.org) as follows:

Friday, April 7: Preview Aggregate (InCommon-metadata-preview.xml)
Tuesday, April 11: IdP-only Aggregate (InCommon-metadata-idp-only.xml)

The remaining metadata aggregates [2] (including the main production 
aggregate) will be enabled for HTTP Compression at a later date TBD.

There is nothing you need to do to realize the benefits of HTTP Compression. 
On or after the above date, if you are consuming either the Preview Aggregate 
or the IdP-only Aggregate, you may observe reduced bandwidth utilization and 
decreased download time during metadata refresh. This is especially true of 
the Preview Aggregate, which is just 8MB compressed.

The client and the server negotiate compression automatically. The server 
will send a compressed metadata aggregate if (and only if) your metadata 
client indicates support for compression in the HTTP request. Check your 
client software documentation for details.

If you have any concerns or experience any issues, please contact us at 


[1] https://en.wikipedia.org/wiki/HTTP_compression
[2] Metadata Aggregates https://spaces.internet2.edu/x/SoG8Ag

-----
Tom Scavo
For InCommon Operations