IOS new versions and network load

Mon Sep 18 12:48:10 UTC 2017

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 at vaxination.ca> 
To: "Eduardo Schoedler" <listas at esds.com.br> 
Cc: Nanog at 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). 