October 2015 - Test - lists.nanog.org

Fwd: [arin-announce] Combined Registration Services Agreement Released
by John Curran 07 Oct '15

07 Oct '15

Folks - Apologies for the distraction, but the revised RSA/LRSA is out, and it addresses some of the concerns raised in this community. See attached announcement for details. /John Begin forwarded message: From: ARIN <info(a)arin.net<mailto:info@arin.net>> Date: October 7, 2015 at 11:31:49 AM GMT-4 To: <arin-announce(a)arin.net<mailto:arin-announce@arin.net>> Subject: [arin-announce] Combined Registration Services Agreement Released ARIN is pleased to announce the release of the new combined Registration Services Agreement ("RSA Version 12.0 / LRSA version 4.0"). This agreement is the successor to existing RSA and LRSA agreements. On 1 September 2015, ARIN concluded its consultation with the community with regards to this combined agreement. The revisions found in this new agreement were based on the feedback received from the community over the past few years. RSA Version 12.0 / LRSA Version 4.0 is an update to the previous RSA Version 11.0 and LRSA Version 3.0, which were already quite similar in terms. This single agreement will be used moving forward effective 6 October 2015 and includes notable and substantive revisions including but not limited to: * The agreements term's are only applicable to "Included Number Resources" (i.e. the Internet number resources pursuant to the agreement, not any other number resources that parties may hold under an existing LRSA or under no agreement) * Similarly clarifying that "Included Number Resources" are not property is only applicable to the "Included Number Resources" in the agreement * Provides uniform service terms and conditions (other than fees) for all customers receiving services from ARIN * Defines ARIN's services that are covered by the agreement, including resource certification * Provides a more balanced agreement with more limited rights to ARIN and more equivalent rights to holders * Clarifying the notification provisions to protect both parties * ARIN's Fee Schedule will not be applied retroactivity, and * Clarifying renewals to meet the needs of governmental entities. Existing holders of Internet number resources have the opportunity to upgrade to this new version of the registration services agreement. They can retain their current registration services agreement if they choose. To view RSA Version 12.0 / LRSA Version 4.0 please visit: https://www.arin.net/resources/agreements/rsa.pdf Note that the final RSA Version 12.0 / LRSA Version 4.0 incorporates changes and clarifications as a result of the community consultation on the earlier draft that closed on 1 September 2015. Differences between that earlier draft and the final RSA Version 12.0 / LRSA Version 4.0 are highlighted in a redlined document: https://www.arin.net/resources/agreements/changes_rsa12_draft.pdf Anyone needing further information about the RSA Version 12.0 / LRSA Version 4.0 can call the Financial Services Help Desk at +1-703-227-9886 or send an email to billing(a)arin.net<mailto:billing@arin.net>. Nothing in this announcement alters or otherwise modifies any terms of RSAs previously signed. Regards, John Curran President & CEO American Registry for Internet Numbers, Ltd. (ARIN) _______________________________________________ ARIN-Announce You are receiving this message because you are subscribed to the ARIN Announce Mailing List (ARIN-announce(a)arin.net<mailto:ARIN-announce@arin.net>). Unsubscribe or manage your mailing list subscription at: http://lists.arin.net/mailman/listinfo/arin-announce Please contact info(a)arin.net<mailto:info@arin.net> if you experience any issues.

1 0

Inexpensive probes for automated bandwidth testing purposes
by Lorell Hathcock 07 Oct '15

07 Oct '15

Greetings, NANOG. Happy Saturday to all. I am running a DOCSIS network that has a noisy cable plant. I want to be able to substantiate and quantify users' bandwidth issues. I would like a set of inexpensive probes that I could place at selected customer's homes/businesses that would on a scheduled basis perform bandwidth tests. Likely I would need to place a server in the head end or across the internet that would allow me to isolate and test certain network segments. I've looked into these in the past and was presented with some wonderfully expensive units that would duplicate my network problems into company financial problems as well. Any ideas? I know there are other ways to measure noise in the cable plant and I am working on those as well. I will soon be running other, non-DOCSIS networks and need to have the same capabilities to test available bandwidth on those networks. Thanks! Lorell Hathcock Sent from my iPad

8 7

RIPE atlas probes
by Weir, Colin 06 Oct '15

06 Oct '15

?Hello attendees, I have a few RIPE Atlas probes with me at the conference for distribution. If you're interested in participating in RIPE measurements, please get in touch with me off-list and I'll be happy to give you one. We have a special interest in the following ASNs, which currently lack any RIPE probes. CANADA 7122 MTS-ASN - MTS Allstream Inc. 803 SASKTEL - Saskatchewan Telecommunications 22995 BARR-XPLR-ASN - Xplornet Communications Inc. 54614 CIKTELECOM-CABLE - CIK Telecom INC 36522 BELLMOBILITY-1 - BELL MOBILITY INC. 11290 RAPIDUS - COGECO Cable Canada Inc. 23184 PERSONA - PERSONA COMMUNICATIONS INC. 7992 COGECOWAVE - Cogeco Cable 11260 EASTLINK-HSI - EastLink 11814 DISTRIBUTEL-AS11814 - DISTRIBUTEL COMMUNICATIONS LTD. 6407 PRIMUS-AS6407 - Primus Telecommunications Canada Inc. 35911 BNQ-1 - Telebec 855 CANET-ASN-4 - Bell Aliant Regional Communications, Inc. 15290 ALLST-15290 - Allstream Corp. USA 15169 GOOGLE - Google Inc. 16509 AMAZON-02 - Amazon.com<http://amazon.com/>, Inc. 21928 T-MOBILE-AS21928 - T-Mobile USA, Inc. 32934 FACEBOOK - Facebook, Inc. 22394 CELLCO - Cellco Partnership DBA Verizon Wireless 20057 ATT-MOBILITY-LLC-AS20057 - ATT Mobility LLC 3549 LVLT-3549 - Level 3 Communications, Inc. -- Colin Weir Engineer, Quality of Experience, Comcast Cable Desk: 215-286-5406 Cell: 215-279-1733

3 2

This came up in the security meeting today in Monteal - New tacacs Work!
by Christopher Morrow 06 Oct '15

06 Oct '15

As mentioned, there's a draft to collect and 'fix' problems that we (google netops folks) see with tacacs+ today: <https://tools.ietf.org/html/draft-dahm-opsawg-tacacs-01> If folk can give this a quick read, send comments to the authors (see draft for emails of authors) OR the ops area wg list: <https://mailarchive.ietf.org/arch/search/?email_list=opsawg> that would be good... even better if you find your favorite vendor critters and ask them their plans in this area. Someone asked, in the meeting, about: "What about key auth?" that sounds like a great thing to take up with Thorsten and Andrej :) -chris

1 0

Telus ADSL IPv6 Roll Out
by Steve Mikulasik 06 Oct '15

06 Oct '15

Looks like Telus is rolling out IPv6 to their ADSL customers. My ISP modem/router is getting a /64 at home. I have a really big smile right now [😊] <http://www.civeo.com/>

2 2

Request for contact from KPN
by Chris Russell 06 Oct '15

06 Oct '15

Hi Apologies for using the list - is anyone from KPN around and can drop me a line off-list ? Ta Chris

1 0

Updated NANOG 65 DD4BC presentation file.
by Roland Dobbins 06 Oct '15

06 Oct '15

I'd inadvertently failed to upload the final revision of the DD4BC presentation file from NANOG 65 - please find the updated .pdf file here, apologies for my confusion: <https://app.box.com/s/2kpbqfdl1ko3qhfhe4y8ekd1rvj24vfd> ----------------------------------- Roland Dobbins <rdobbins(a)arbor.net>

1 0

Re: [outages] Akamai Cert Issues today
by Jay Ashworth 04 Oct '15

04 Oct '15

----- Original Message ----- > From: "coolhandluke via Outages" <outages(a)outages.org> > > -We're wondering what happened yesterday to break all these > > disparate > > websites > note that this is *by design*, as sean pointed out. > > the "fix" is simple: don't use https on www.irs.gov. any ssl pages > served by the irs as served on different hostnames. > > as to why your users just started it, nfi. my best guess is that they > weren't using https previously. Well, "more people may be using HTTPS-Anywhere" may have something to do with it. Or, it might be that some new browser release just enabled HTTP/2.0, which in many implementations *requires* SSL and might also trip this, as noted in a posting on the topic which I just inadvertantly posted to this same mailing list 5 minutes ago. :-) 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

2 1

Looking for upstream provider with BGP Flow Spec support / RFC 5575
by Pavel Odintsov 04 Oct '15

04 Oct '15

Hello, dear Nanog Community! I'm looking for upstreams with BGP Flow Spec / RFC 5575 support in US (West and East coast are welcome). We have implemented support for BGP Flow Spec traffic filtering in our own open source DDoS detection toolkit and using it on our own MX routers. Works really well. But we are experiencing so much attacks on channel overflow and want to lock part of traffic on upstream's side. Thanks! -- Sincerely yours, Pavel Odintsov

1 0

HTTP/2.0 to ship in weeks
by Jay Ashworth 04 Oct '15

04 Oct '15

We all knew about this, right? http://arstechnica.com/information-technology/2015/02/http2-finished-coming… One - few - many - all? What's that? 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 1