While we don’t use Apple's caching servers we do have transparent caching in place which nets us about 82% of their content being serverd locally. On a big IOS update it will probably be close to 99% for that one title.
Would you be open to elaborating a bit on how that’s set up on your network? :) Regards, Marco Slater On 18 Sep 2017, 14:55 +0100, Luke Guillory <lguillory@reservetele.com>, wrote:
While we don’t use Apple's caching servers we do have transparent caching in place which nets us about 82% of their content being serverd locally. On a big IOS update it will probably be close to 99% for that one title.
Luke Guillory Vice President – Technology and Innovation
Tel: 985.536.1212 Fax: 985.536.0300 Email: lguillory@reservetele.com
Reserve Telecommunications 100 RTC Dr Reserve, LA 70084
_________________________________________________________________________________________________
Disclaimer: The information transmitted, including attachments, is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material which should not disseminate, distribute or be copied. Please notify Luke Guillory immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. Luke Guillory therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. .
-----Original Message----- From: NANOG [mailto:nanog-bounces@nanog.org] On Behalf Of Paul Stewart Sent: Monday, September 18, 2017 7:53 AM To: Mike Hammett Cc: Nanog@nanog.org Subject: Re: IOS new versions and network load
Curious as mentioned if anyone doing this on scale? I kind of doubt it but love to hear otherwise. My assumption is this is more Enterprise focused than ISP
Paul
Sent from my iPhone
On Sep 18, 2017, at 8:48 AM, Mike Hammett <nanog@ics-il.net> wrote:
We've been looking into the caching server bit lately given that we're not due to get an official Apple node for at least another year yet.
It looks very difficult to manage, given the DNS TXT records and domain search fields. If it was as simple as entering the supported IP ranges, it'd be a lot easier to implement.
The caching service does support a lot more than content than "once a year" https://support.apple.com/en-us/HT204675
----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com
Midwest-IX http://www.midwest-ix.com
----- Original Message -----
From: "Jean-Francois Mezei" <jfmezei_nanog@vaxination.ca To: "Eduardo Schoedler" <listas@esds.com.br Cc: Nanog@nanog.org Sent: Sunday, September 17, 2017 6:43:50 PM Subject: Re: IOS new versions and network load
On 2017-09-17 19:37, Eduardo Schoedler wrote:
Server is an app now, any MacOS can have it running.
But do carriers/ISPs really want to deal with a rack unfriendly Mac Mini or iMac at a carrier hotel? If the Server App could run on Linux, or if OS-X could boot on standard servers, perhaps, it it seems to be a very bad fit in carrier/enterprise environments.
Implementation will be a little tricky, because you need your customers to look a record in your domain.
I've tried reading some about it. The cache server app registers with Apple its existence and the IP address ranges it serves
When a client wants to download new IOS version, Apple checked and finds that the client's IP is served by the caching server whose "local" IP is a.b.c.d (akaL the inside NAT IP address). Tells client to get version of software from that IP address.
The DNS TXT records are used by the Caching Server to get the list of IP blocks it can serve. (not needed in the target small office environments where everyone is on same subnet and the caching server can tell the apple serves the one subnet it seves).