IOS new versions and network load

Mon Sep 18 12:58:16 UTC 2017

*nods* It appears to be very enterprise focused, but then it's mentioned on their PeeringDB page, so that makes one wonder. 

It doesn't seem like it would be easy for an ISP to manage given that they can't set the required domain search field via static or PPPoE. That would leave DHCP as the only way to assign that field and then that's assuming that whatever router is at the customer location passes that field through to the end user devices. 

It seems like it would be a lot more effective to ditch the requirement for the domain search field and just let the caching server tell Apple what prefixes it supports and there be an automated verification system using RIR records that the request is legitimate. 

----- 
Mike Hammett 
Intelligent Computing Solutions 
http://www.ics-il.com 

Midwest-IX 
http://www.midwest-ix.com 

----- Original Message -----

From: "Paul Stewart" <paul at paulstewart.org> 
To: "Mike Hammett" <nanog at ics-il.net> 
Cc: Nanog at nanog.org 
Sent: Monday, September 18, 2017 7:53:00 AM 
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 at 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 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). 
> 
> 