- NANOG - lists.nanog.org

Better Conversation following tools for Wireshark?
by Jay R. Ashworth 04 Apr '16

04 Apr '16

I have to do a little interactive monitoring this week, and while I want to run Wireshark to log the packets, I'd also like to be able to do some more hands on, flow-based monitoring, and the Conversations tool in WS2.x isn't up to the task; it won't let me roll up all traffic for a local IP into a single line, for example, as iftop will. I thought I'd be able to do this with ntop, but even though I can see that monitoring is enable to the switchport from WS, ntop only shows me the broadcast connections. Are there any better tools for this sort of work, that will cooperate with WS on a Win7Pro box? (Yeah, yeah; I know; it's all I have handy and I'm out of days; I had the flu last week like everyone else.) Cheers, -- jra -- Jay R. Ashworth Baylink jra(a)baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274

1 0

Re: Some doubts on large scale BGP/AS design and black hole routing risk
by Scott Weeks 04 Apr '16

04 Apr '16

--- hank(a)efes.iucc.ac.il wrote: From: Hank Nussbacher <hank(a)efes.iucc.ac.il> Also providers lie either intentionally or by mistake. ---------------------------------------- s/ or by mistake// There fixed that. ;-) scott

1 0

Re: Microwave link capacity
by Scott Weeks 04 Apr '16

04 Apr '16

--- jfmezei_nanog(a)vaxination.ca wrote: From: Jean-Francois Mezei <jfmezei_nanog(a)vaxination.ca> In a context of providing rural communities with modern broadband. Reading some tells me that Microwave links can be raised to 1gbps. How common is that ? I assume that cell phone towers have modern microwave links (when not directly on fibre). What sort of capacity would typically be provided ? And in the case of a remote village/town served by microwave originally designed to handle just phone calls, how difficult/expensive is it to upgrade to 1gbps or higher capacity ? Just a change of radio ? or radio and antenna, keeping only the tower ? ----------------------------------------------- It depends on the system installed. For example, with Aviat Eclipse ODU 600 you can start out small and grow. They have an "Eclipse Node" that supports throughput capacities to 366 Mbit/s Ethernet, 100xE1, 127xDS1, 4xDS3, STM1+1E1, or 2xSTM1/OC3. If you upgrade to their "Packet Node" it will support Gigabit bandwidth in addition to the above BWs. They have regular slots and you just change cards. scott

1 0

Time Warner IPv6 - need answers
by Philip Lavine 04 Apr '16

04 Apr '16

When is TW in Los Angeles going to support ipv6 prefix delegation? I received a /128 (even though the advanced tech support said they did not support it).

1 0

Someone Please Help Me Understand
by Eric Rogers 04 Apr '16

04 Apr '16

Ok, I'm trying to learn, so bear with me. We are an ISP in Indianapolis that has full routes from 3 different providers HE.Net in Columbus OH being one. We also are peered with 2 peering exchanges, including EquinixIX in Chicago. The problem is Instagram and Facebook (same company, I know) for our customers seems very slow. This is where I need a way to troubleshoot/understand more. I did a traceroute to the IP that is serving the pictures, and it resolves to the FBCDN servers in Dallas, and is showing packet loss and pings once it hits Dallas, and are in the 1xxs of ms. Tracing route to instagram-p3-shv-01-dfw1.fbcdn.net [31.13.66.52] over a maximum of 30 hops: 1 4 ms 3 ms 4 ms 10.7.0.1 2 20 ms 43 ms 42 ms inmtvlobs-rtr-01.dynamic.pdsconnect.me [192.69.57.1] 3 25 ms 47 ms 29 ms inmtvlmwt-rtr-01.infrastructure.pdsconnect.me [192.69.48.162] 4 46 ms 32 ms 58 ms inindyhen-core1.infrastructure.pdsconnect.me [192.69.48.193] 5 36 ms 53 ms 51 ms ge2-4.core1.cmh1.he.net [184.105.32.1] 6 47 ms 41 ms 75 ms 10ge1-2.core1.chi1.he.net [184.105.222.165] 7 57 ms 57 ms 53 ms 100ge14-1.core2.chi1.he.net [184.105.81.97] 8 57 ms 73 ms 84 ms 100ge12-1.core1.mci3.he.net [184.105.81.209] 9 75 ms 73 ms 102 ms 10ge15-6.core1.dal1.he.net [184.105.222.10] 10 93 ms 103 ms 92 ms eqix-da1.facebook.com [206.223.118.176] 11 102 ms 101 ms * psw01c.dfw1.tfbnw.net [173.252.65.196] 12 92 ms 97 ms 105 ms msw1aq.01.dfw1.tfbnw.net [204.15.21.89] 13 110 ms * 98 ms instagram-p3-shv-01-dfw1.fbcdn.net [31.13.66.52] Since I am peered with the route servers in EquinixIX Chicago, shouldn't the data be coming from there, or at least hit their routers? In my trace, it shows HE to Chicago, then to Dallas. How does FB decide what IP the content gets displayed from, and is there anything I can do as a provider? If it is DNS, I can obviously clear the cache to see if it gets new IPs. If I'm not getting FB peering IPs in Chicago, do I need to peer directly? Should I get FaceBook involved? Eric Rogers PDS Connect (317) 831-3000 x200

4 8

SAFNOG-3 Meeting - Date Change Updates
by Mark Tinka 04 Apr '16

04 Apr '16

Hello all. Due to an unfortunate set of circumstances, the SAFNOG-3 meeting dates have changed. Please visit the SAFNOG web site for details on this, at the URL below: http://safnog.org/ The SAFNOG-3 meeting is still going ahead as described on the web site. Detailed planning for the meeting is ongoing, and further updates will be communicated to the community in the coming weeks. You may also subscribe to the SAFNOG mailing list for regular updates at the URL below: http://lists.safnog.org/listinfo/safnog We look forward to seeing you all in Windhoek, later this year. For any questions, please send e-mail to: secretariat <at> safnog <dot> org Cheers, Mark Tinka On Behalf of the SAFNOG Management Committee

1 0

What services does Microsoft AS8075 provide when peering at IXPs?
by Eric A Louie 04 Apr '16

04 Apr '16

I had this question posed by a marketing type in my office. Does anyone know the answer? Is it microsoft.com, msdn, outllook365, msn.com, outlook.com, azure, windows updates, xbox? what else is possibly covered or omitted in their peering service? I suppose we have a customer who is an Azure customer that wants to know if their Azure traffic will stay in our network or still go through the Internet. I've tried asking peering(a)microsoft.com twice, but it looks like they have their ignore filter up. Thanks, -e-

3 3

Re: What services does Microsoft AS8075 provide when peering at IXPs?
by Eric Louie 03 Apr '16

03 Apr '16

Hi Todd I found an answer. It's everything public Microsoft. If it's private Office 365 or private Azure, it doesn't come through the peering fabric. Best regards, Eric Sent from my Verizon Wireless 4G LTE smartphone -------- Original message -------- From: Todd Crane <todd.crane(a)n5tech.com> Date: 4/3/2016 16:06 (GMT-08:00) To: Eric A Louie <elouie(a)yahoo.com> Subject: Re: What services does Microsoft AS8075 provide when peering at IXPs? Eric, This may or may not be what your after, but these are the prefixes we receive from them in Phoenix on Phoenix-IX. Peering is requested via the form at http://www.microsoft.com/Peering/PeeringForm. The peering(a)microsoft.com may be setup to ignore everybody that is not an established peer. That is just a guess. We have had no need to contact them, so we haven’t tried. -Todd Prefix Nexthop MED Lclpref AS path * 13.64.0.0/11 206.41.105.44 100 8075 I * 13.104.0.0/14 206.41.105.44 100 8075 I * 13.107.3.0/24 206.41.105.44 100 8075 8068 I * 13.107.4.0/24 206.41.105.44 100 8075 8068 I * 13.107.5.0/24 206.41.105.44 100 8075 8068 I * 13.107.6.0/24 206.41.105.44 100 8075 8068 I * 13.107.7.0/24 206.41.105.44 100 8075 8068 I * 13.107.9.0/24 206.41.105.44 100 8075 8068 I * 13.107.12.0/24 206.41.105.44 100 8075 8068 I * 13.107.13.0/24 206.41.105.44 100 8075 8068 I * 13.107.15.0/24 206.41.105.44 100 8075 8068 I * 13.107.16.0/24 206.41.105.44 100 8075 8068 I * 13.107.18.0/24 206.41.105.44 100 8075 8068 I * 13.107.24.0/24 206.41.105.44 100 8075 8068 I * 13.107.44.0/24 206.41.105.44 100 8075 8068 I * 13.107.58.0/24 206.41.105.44 100 8075 8068 I * 13.107.160.0/24 206.41.105.44 100 8075 8068 I * 13.107.240.0/24 206.41.105.44 100 8075 8068 I * 23.96.0.0/14 206.41.105.44 100 8075 I * 23.100.0.0/15 206.41.105.44 100 8075 I * 23.102.0.0/16 206.41.105.44 100 8075 I * 23.103.64.0/18 206.41.105.44 100 8075 I * 23.103.128.0/17 206.41.105.44 100 8075 I * 40.64.0.0/10 206.41.105.44 100 8075 I * 40.90.4.0/24 206.41.105.44 100 8075 8068 I * 51.8.0.0/16 206.41.105.44 100 8075 I * 51.10.0.0/15 206.41.105.44 100 8075 I * 51.12.0.0/15 206.41.105.44 100 8075 I * 51.18.0.0/16 206.41.105.44 100 8075 I * 51.51.0.0/16 206.41.105.44 100 8075 I * 51.53.0.0/16 206.41.105.44 100 8075 I * 51.103.0.0/16 206.41.105.44 100 8075 I * 51.104.0.0/15 206.41.105.44 100 8075 I * 51.107.0.0/16 206.41.105.44 100 8075 I * 51.116.0.0/16 206.41.105.44 100 8075 I * 51.120.0.0/16 206.41.105.44 100 8075 I * 51.124.0.0/16 206.41.105.44 100 8075 I * 51.132.0.0/16 206.41.105.44 100 8075 I * 51.136.0.0/15 206.41.105.44 100 8075 I * 51.138.0.0/16 206.41.105.44 100 8075 I * 51.140.0.0/14 206.41.105.44 100 8075 I * 51.144.0.0/15 206.41.105.44 100 8075 I * 52.96.0.0/12 206.41.105.44 100 8075 I * 52.112.0.0/14 206.41.105.44 100 8075 I * 52.120.0.0/14 206.41.105.44 100 8075 I * 52.125.0.0/16 206.41.105.44 100 8075 I * 52.126.0.0/15 206.41.105.44 100 8075 I * 52.130.0.0/15 206.41.105.44 100 8075 I * 52.132.0.0/14 206.41.105.44 100 8075 I * 52.136.0.0/13 206.41.105.44 100 8075 I * 52.145.0.0/16 206.41.105.44 100 8075 I * 52.146.0.0/15 206.41.105.44 100 8075 I * 52.148.0.0/14 206.41.105.44 100 8075 I * 52.152.0.0/13 206.41.105.44 100 8075 I * 52.160.0.0/11 206.41.105.44 100 8075 I * 52.224.0.0/11 206.41.105.44 100 8075 I * 64.4.0.0/18 206.41.105.44 100 8075 I * 64.4.48.0/24 206.41.105.44 100 8075 8068 I * 64.41.193.0/24 206.41.105.44 100 8075 20046 I * 65.52.0.0/14 206.41.105.44 100 8075 I * 65.54.0.0/24 206.41.105.44 100 8075 3598 I * 65.54.1.0/24 206.41.105.44 100 8075 3598 I * 65.54.2.0/24 206.41.105.44 100 8075 3598 I * 65.55.28.0/22 206.41.105.44 100 8075 3598 I * 65.55.28.0/23 206.41.105.44 100 8075 3598 ? * 65.55.44.0/24 206.41.105.44 100 8075 8075 I * 65.55.112.0/24 206.41.105.44 100 8075 20046 I * 65.55.117.0/24 206.41.105.44 100 8075 8075 I * 65.55.171.0/24 206.41.105.44 100 8075 20046 I * 65.55.188.0/24 206.41.105.44 100 8075 3598 I * 65.55.230.0/24 206.41.105.44 100 8075 8075 I * 65.55.231.0/24 206.41.105.44 100 8075 8075 I * 65.221.5.0/24 206.41.105.44 100 8075 20046 I * 66.119.144.0/20 206.41.105.44 100 8075 I * 70.37.0.0/17 206.41.105.44 100 8075 I * 70.37.128.0/18 206.41.105.44 100 8075 I * 91.190.216.0/23 206.41.105.44 100 8075 198015 I * 91.190.218.0/23 206.41.105.44 100 8075 198097 I * 91.190.220.0/24 206.41.105.44 100 8075 198097 I * 94.245.64.0/18 206.41.105.44 100 8075 I * 104.40.0.0/13 206.41.105.44 100 8075 I * 104.44.75.0/24 206.41.105.44 100 8075 8068 I * 104.146.0.0/19 206.41.105.44 100 8075 I * 104.146.128.0/17 206.41.105.44 100 8075 I * 104.208.0.0/13 206.41.105.44 100 8075 I * 111.221.16.0/20 206.41.105.44 100 8075 I * 111.221.64.0/18 206.41.105.44 100 8075 I * 131.107.0.0/16 206.41.105.44 100 8075 3598 I * 131.107.0.0/20 206.41.105.44 100 8075 3598 I * 131.107.217.0/24 206.41.105.44 100 8075 3598 I * 131.253.1.0/24 206.41.105.44 100 8075 I * 131.253.5.0/24 206.41.105.44 100 8075 I * 131.253.6.0/24 206.41.105.44 100 8075 I * 131.253.8.0/24 206.41.105.44 100 8075 I * 131.253.12.0/22 206.41.105.44 100 8075 8075 I * 131.253.16.0/23 206.41.105.44 100 8075 23468 I * 131.253.18.0/24 206.41.105.44 100 8075 I * 131.253.21.0/24 206.41.105.44 100 8075 8068 I * 131.253.22.0/23 206.41.105.44 100 8075 23468 I * 131.253.24.0/21 206.41.105.44 100 8075 I * 131.253.32.0/20 206.41.105.44 100 8075 I * 131.253.33.0/24 206.41.105.44 100 8075 I * 131.253.61.0/24 206.41.105.44 100 8075 I * 131.253.62.0/23 206.41.105.44 100 8075 I * 131.253.72.0/22 206.41.105.44 100 8075 8070 I * 131.253.80.0/20 206.41.105.44 100 8075 8070 I * 131.253.112.0/21 206.41.105.44 100 8075 8070 I * 131.253.120.0/22 206.41.105.44 100 8075 8070 I * 131.253.128.0/17 206.41.105.44 100 8075 I * 132.245.0.0/16 206.41.105.44 100 8075 I * 134.170.0.0/16 206.41.105.44 100 8075 I * 137.116.0.0/15 206.41.105.44 100 8075 I * 137.135.0.0/16 206.41.105.44 100 8075 I * 138.91.0.0/16 206.41.105.44 100 8075 I * 138.196.0.0/16 206.41.105.44 100 8075 I * 146.147.0.0/16 206.41.105.44 100 8075 I * 150.171.0.0/16 206.41.105.44 100 8075 I * 157.55.0.0/16 206.41.105.44 100 8075 I * 157.56.0.0/16 206.41.105.44 100 8075 I * 157.58.0.0/16 206.41.105.44 100 8075 3598 I * 157.58.2.0/23 206.41.105.44 100 8075 23468 I * 157.58.192.0/19 206.41.105.44 100 8075 3598 I * 157.58.248.0/23 206.41.105.44 100 8075 3598 ? * 157.60.23.0/24 206.41.105.44 100 8075 I * 157.60.31.0/24 206.41.105.44 100 8075 I * 167.220.0.0/17 206.41.105.44 100 8075 3598 I * 167.220.8.0/24 206.41.105.44 100 8075 3598 I * 167.220.9.0/24 206.41.105.44 100 8075 3598 I * 167.220.10.0/24 206.41.105.44 100 8075 3598 I * 167.220.16.0/20 206.41.105.44 100 8075 3598 I * 167.220.24.0/22 206.41.105.44 100 8075 3598 I * 167.220.28.0/23 206.41.105.44 100 8075 6584 8073 I * 167.220.40.0/21 206.41.105.44 100 8075 3598 I * 167.220.48.0/21 206.41.105.44 100 8075 3598 I * 167.220.64.0/19 206.41.105.44 100 8075 3598 I * 167.220.148.0/22 206.41.105.44 100 8075 3598 I * 167.220.152.0/24 206.41.105.44 100 8075 3598 I * 167.220.192.0/22 206.41.105.44 100 8075 6584 I * 167.220.196.0/22 206.41.105.44 100 8075 6584 I * 167.220.200.0/24 206.41.105.44 100 8075 6584 I * 167.220.201.0/24 206.41.105.44 100 8075 6584 I * 167.220.232.0/22 206.41.105.44 100 8075 8071 I * 167.220.236.0/22 206.41.105.44 100 8075 3598 I * 167.220.240.0/22 206.41.105.44 100 8075 I * 167.220.248.0/21 206.41.105.44 100 8075 3598 I * 168.61.0.0/16 206.41.105.44 100 8075 I * 168.62.0.0/15 206.41.105.44 100 8075 I * 191.232.0.0/13 206.41.105.44 100 8075 I * 192.48.225.0/24 206.41.105.44 100 8075 I * 192.84.159.0/24 206.41.105.44 100 8075 I * 192.84.160.0/23 206.41.105.44 100 8075 I * 192.92.196.0/24 206.41.105.44 100 8075 62540 I * 192.197.157.0/24 206.41.105.44 100 8075 I * 193.149.64.0/19 206.41.105.44 100 8075 I * 193.221.113.0/24 206.41.105.44 100 8075 8075 I * 194.69.96.0/22 206.41.105.44 100 8075 6584 I * 194.69.100.0/22 206.41.105.44 100 8075 6584 I * 194.69.126.0/23 206.41.105.44 100 8075 6584 I * 198.49.8.0/24 206.41.105.44 100 8075 8075 I * 198.105.232.0/22 206.41.105.44 100 8075 3598 I * 198.180.95.0/24 206.41.105.44 100 8075 3598 I * 198.200.130.0/24 206.41.105.44 100 8075 I * 198.206.164.0/24 206.41.105.44 100 8075 I * 199.2.137.0/24 206.41.105.44 100 8075 3598 I * 199.30.16.0/20 206.41.105.44 100 8075 I * 199.60.28.0/24 206.41.105.44 100 8075 I * 199.74.210.0/24 206.41.105.44 100 8075 I * 199.103.90.0/23 206.41.105.44 100 8075 I * 199.103.122.0/24 206.41.105.44 100 8075 I * 199.242.48.0/21 206.41.105.44 100 8075 I * 202.89.224.0/21 206.41.105.44 100 8075 I * 204.14.180.0/24 206.41.105.44 100 8075 8068 I * 204.79.135.0/24 206.41.105.44 100 8075 I * 204.79.179.0/24 206.41.105.44 100 8075 I * 204.79.180.0/24 206.41.105.44 100 8075 62540 I * 204.79.195.0/24 206.41.105.44 100 8075 8075 I * 204.79.197.0/24 206.41.105.44 100 8075 8068 I * 204.79.252.0/24 206.41.105.44 100 8075 8075 I * 204.95.96.0/20 206.41.105.44 100 8075 I * 204.152.140.0/23 206.41.105.44 100 8075 I * 204.176.46.0/24 206.41.105.44 100 8075 20046 I * 204.182.144.0/24 206.41.105.44 100 8075 3598 I * 204.255.244.0/23 206.41.105.44 100 8075 3598 I * 206.138.168.0/21 206.41.105.44 100 8075 I * 206.191.224.0/19 206.41.105.44 100 8075 I * 207.46.0.0/19 206.41.105.44 100 8075 I * 207.46.33.0/24 206.41.105.44 100 8075 I * 207.46.34.0/23 206.41.105.44 100 8075 I * 207.46.36.0/22 206.41.105.44 100 8075 I * 207.46.40.0/21 206.41.105.44 100 8075 I * 207.46.48.0/20 206.41.105.44 100 8075 I * 207.46.64.0/18 206.41.105.44 100 8075 I * 207.46.98.0/24 206.41.105.44 100 8075 8075 I * 207.46.128.0/17 206.41.105.44 100 8075 I * 207.68.128.0/18 206.41.105.44 100 8075 I * 207.82.250.0/23 206.41.105.44 100 8075 I * 208.68.136.0/21 206.41.105.44 100 8075 I * 208.76.45.0/24 206.41.105.44 100 8075 8075 I * 208.76.46.0/24 206.41.105.44 100 8075 8075 I * 208.84.0.0/24 206.41.105.44 100 8075 8075 I * 208.84.1.0/24 206.41.105.44 100 8075 I * 208.84.2.0/24 206.41.105.44 100 8075 8075 I * 208.84.3.0/24 206.41.105.44 100 8075 I * 209.1.15.0/24 206.41.105.44 100 8075 20046 I * 209.1.112.0/23 206.41.105.44 100 8075 I * 209.185.128.0/22 206.41.105.44 100 8075 I * 209.185.240.0/22 206.41.105.44 100 8075 I * 209.240.192.0/19 206.41.105.44 100 8075 I * 213.199.128.0/18 206.41.105.44 100 8075 I * 216.32.180.0/22 206.41.105.44 100 8075 I * 216.32.180.0/24 206.41.105.44 100 8075 20046 I * 216.32.240.0/22 206.41.105.44 100 8075 I * 216.33.240.0/22 206.41.105.44 100 8075 I * 216.34.51.0/24 206.41.105.44 100 8075 20046 I * 2001:df0:7::/48 2001:504:3b::44 100 8075 I * 2001:df0:d7::/48 2001:504:3b::44 100 8075 I * 2001:4898::/32 2001:504:3b::44 100 8075 3598 I * 2001:4899::/32 2001:504:3b::44 100 8075 I * 2001:489a:2000::/35 2001:504:3b::44 100 8075 8070 I * 2404:f800::/32 2001:504:3b::44 100 8075 I * 2404:f801::/32 2001:504:3b::44 100 8075 8071 I * 2404:f801:8028::/48 2001:504:3b::44 100 8075 3598 I * 2404:f801:8030::/48 2001:504:3b::44 100 8075 I * 2404:f801:8058::/48 2001:504:3b::44 100 8075 3598 I * 2404:f801:9000::/48 2001:504:3b::44 100 8075 3598 I * 2404:f801:a808::/48 2001:504:3b::44 100 8075 8071 I * 2603:1000::/25 2001:504:3b::44 100 8075 I * 2620:0:30::/45 2001:504:3b::44 100 8075 I * 2620:1ec::/36 2001:504:3b::44 100 8075 I * 2620:1ec:4::/48 2001:504:3b::44 100 8075 8068 I * 2620:1ec:5::/48 2001:504:3b::44 100 8075 8068 I * 2620:1ec:6::/48 2001:504:3b::44 100 8075 8068 I * 2620:1ec:7::/48 2001:504:3b::44 100 8075 8068 I * 2620:1ec:a::/48 2001:504:3b::44 100 8075 8068 I * 2620:1ec:b::/48 2001:504:3b::44 100 8075 8068 I * 2620:1ec:c::/48 2001:504:3b::44 100 8075 8068 I * 2620:1ec:34::/48 2001:504:3b::44 100 8075 8068 I * 2620:1ec:a92::/48 2001:504:3b::44 100 8075 8068 I * 2620:1ec:c11::/48 2001:504:3b::44 100 8075 8068 I * 2801:80:1d0::/48 2001:504:3b::44 100 8075 I * 2a01:110::/32 2001:504:3b::44 100 8075 6584 I * 2a01:110:8008::/48 2001:504:3b::44 100 8075 6584 I * 2a01:110:8012::/48 2001:504:3b::44 100 8075 6584 I * 2a01:110:a008::/48 2001:504:3b::44 100 8075 6584 I * 2a01:111::/32 2001:504:3b::44 100 8075 I * 2a01:111:2003::/48 2001:504:3b::44 100 8075 8068 I * 2a01:111:202c::/48 2001:504:3b::44 100 8075 8068 I * 2a01:111:202e::/48 2001:504:3b::44 100 8075 8068 I > On Apr 1, 2016, at 11:02 AM, Eric A Louie via NANOG <nanog(a)nanog.org> wrote: > > I had this question posed by a marketing type in my office. Does anyone know the answer? > Is it microsoft.com, msdn, outllook365, msn.com, outlook.com, azure, windows updates, xbox? what else is possibly covered or omitted in their peering service? I suppose we have a customer who is an Azure customer that wants to know if their Azure traffic will stay in our network or still go through the Internet. > I've tried asking peering(a)microsoft.com twice, but it looks like they have their ignore filter up. > > Thanks, -e-

1 0

Last call for presentations and Draft programme for RIPE 72
by Benno Overeinder 02 Apr '16

02 Apr '16

Colleagues, A list of currently accepted RIPE 72 presentations is now published at: https://ripe72.ripe.net/programme/meeting-plan/draft-programme/ There are still few slots remaining for a final RIPE 72 programme and RIPE Programme Committee will accept new proposals until 15 April 2016. This is our last call for you to submit your proposals. You can find the CFP for RIPE 72 below, or at https://ripe72.ripe.net/submit-topic/cfp/, for your proposals for plenary session presentations, tutorials, workshops, BoFs (Birds of a Feather sessions) and lightning talks. Please also note that speakers do not receive any extra reduction or funding towards the meeting fee at the RIPE Meetings. Kind regards, Benno Overeinder RIPE PC Chair https://www.ripe.net/participate/meetings/ripe-meetings/pc -------------------->>><<<-------------------- Call for Presentations A RIPE Meeting is an open event where Internet Service Providers, network operators and other interested parties get together. Although the meeting is mostly technical, it is also a chance for people to meet and network with others in their field. RIPE 72 will take place from 23-27 May 2016 in Copenhagen, Denmark. The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the plenary sessions, BoFs (Birds of a Feather sessions), panels, workshops, tutorials and lightning talks at RIPE 72. See the full descriptions of the different presentation formats, https://ripe72.ripe.net/submit-topic/presentation-formats/. Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than 15 April 2016. Proposals submitted after this date will be considered depending on the remaining available space in the programme. The PC is looking for presentations covering topics of network engineering and operations, including but not limited to: - IPv6 deployment - Managing IPv4 scarcity in operations - Commercial transactions of IPv4 addresses - Data centre technologies - Network and DNS operations - Internet governance and regulatory practices - Network and routing security - Content delivery - Internet peering and mobile data exchange Submissions RIPE Meeting attendees are quite sensitive to keeping presentations non-commercial, and product marketing talks are strongly discouraged. Repeated audience feedback shows that the most successful talks focus on operational experience, research results, or case studies. For example, presenters wishing to describe a commercial solution should focus on the underlying technology and not attempt a product demonstration. Presenters should indicate how much time they will require. In general, the time allocated for the different presentation formats is as follows: - Plenary presentations: 20-25 minutes presentation with 5-10 minutes discussion - Tutorials: up to two hours (Monday morning) - Workshops: one hour (during evening sessions) to two hours (Monday morning) - BoFs: approximately one hour - Lightning talks: 10 minutes The following general requirements apply: - Proposals must be submitted using the meeting submission system, https://ripe72.ripe.net/submit-topic/submission-form/. - Lightning talks should also be submitted using the meeting submission system (https://ripe72.ripe.net/submit-topic/submission-form/) and can be submitted any time up to and including the meeting week. The allocation of lightning talks will be announced on short notice---in some cases on the same day but often one day prior to the time slot allocated. - Presenters who propose a panel or BoF are encouraged to include speakers from several (perhaps even competing) companies and/or a neutral facilitator. - All presentation proposals will only be considered by the PC if they contain at least draft presentation slides (slides may be updated later on). For panels, proposals must contain a clear description, as well as the names of invited panellists, presenters and moderators. - Due to potential technical issues, presenters/panellists should be physically present at the RIPE Meeting. If you have any questions or requests concerning content submissions, please email pc [at] ripe [dot] net. -- Benno J. Overeinder NLnet Labs http://www.nlnetlabs.nl/

1 0

PlayStation Network blocking an IP
by Velocity Lists 01 Apr '16

01 Apr '16

Can someone form Sony's Playstation network give me call or contact me offlist. One of our apartment complexes has been reporting errors of PS4s not working for a few days then they start working again. PSN Support is telling the users to call us. We have diagnosed it and PSN is blocking the IP of the complex and it has nothing to do with us. Velocity Online Rodger Lewis rclewis(a)velocityonline.net 850-205-4638 x201

4 3