<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: arial,helvetica,sans-serif; font-size: 10pt; color: #000000'>but hey... they're getting transit from VZB\MCI\UUNET... so it'll be great!<br><br><div><span name="x"></span><br><br>-----<br>Mike Hammett<br>Intelligent Computing Solutions<br>http://www.ics-il.com<br><br>Midwest-IX<br>http://www.midwest-ix.com<span name="x"></span><br></div><br><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Jon Lewis" <jlewis@lewis.org><br><b>To: </b>"NANOG" <nanog@nanog.org><br><b>Sent: </b>Friday, April 26, 2019 4:51:58 PM<br><b>Subject: </b>Re: Disney+ CDN<br><br>On Fri, 26 Apr 2019, Ross Tajvar wrote:<br><br>> Yeah, I'm going to send them an email and see if I can get ahold of their peering policy.<br>> I'm hoping they will update it as they get more attention from other networks. They may just be procrastinating<br>> setting things up. According to bgp.he.net they are only announcing one v4 /24 and one v6 /48, which could be<br>> enough IPs, but seems a little on the small side.<br><br>I'd be much more worried about only being on one IX than only advertising <br>a single /24 and /48. I'm guessing they've just not fully fleshed out the <br>peeringdb entry and maybe not fully built out the network infrastructure <br>yet. A CDN, with everything coming from one POP in NY is not going to cut <br>it.<br><br>----------------------------------------------------------------------<br> Jon Lewis, MCP :) | I route<br> | therefore you are<br>_________ http://www.lewis.org/~jlewis/pgp for PGP public key_________<br></div><br></div></body></html>