- Test - lists.nanog.org

Northern California fires and telecomm outages
by Mike 18 Oct '17

18 Oct '17

Hello fellow operators, The recent northern California fires wiped us out along with many other service providers and services including cellular, landline, e-911, cable and the like and I feel it's of operational concern the fragility of the telecommunications networks that link us together and the experiences had during this most recent event. I hope this topic is welcome and I apologize in advance for length. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=- I am the founder and owner of an Internet Service Provider business in Mendocino County, California and I also operate a CLEC (Competitive Local Exchange Carrier, a type of telecommunications company akin to ATT or Frontier), also in Mendocino County, California. The recent Northern California fires were again a direct and upfront demonstration of the potential for unanticipated widespread public disaster and again demonstrated how vulnerable we all are. Especially, the rising dependence on broadband service, and an expectation by end users that these services which are critical to them will continue functioning during emergencies as they may have no other access. There was a complete and total breakdown in telecommunication services due to fire which wiped out a primary telecommunications cable, and with it, e-911, land lines, cellular, cable and other telecommunication services. I hope that there will be a more complete public investigation and report on this latest incident, but in the mean time I would like to just offer what I know and to suggest where we could go from here. In the early morning of October 9, the Northern California fires were in effect and in Redwood Valley California, a fire was burning that destroyed a AT&T telecommunications cable that runs between Ukiah and Willits. This single cable is the primary carrier of nearly all telecommunications services north of Ukiah. Although I cannot comment on the totality of the outage due to this specific fire and line cut, it's widely reported elsewhere that services were affected all the way up to Arcata at least. For Mendocino County, I can report that this telecommunication outage resulted in loss of e-911, cellular, landline, cable and most all other broadband services, and caused a complete outage of our service too. This resulted in a virtual dark age, where reliable and up to date information concerning the emergency situation was unable to be communicated, people could not find their families or know whether they got out in time because nothing was working and no way to talk. We were reduced to using paper and posting notes at the Library or other emergency shelter locations or other places where people gathered in order to communicate. People in these areas also had to use cash to buy supplies. Nothing worked. We attempted to engage emergency restoration processes on our own for our own customers and services. We determined that we could rapidly deploy high capacity microwave connecting a remote location where we also already operate microwave, to our main point of presence at an ATT building in Ukiah, and provide a sufficient level of service to all of our customers that would be a huge benefit during this crisis. As a CLEC with an existing presence and power arrangement and so forth within this facility, it seemed natural that we should be able to go ahead and get a simple OK to go do the work. But, we encountered lethargy and insensitivity to the widespread outage and emergency conditions we are trying to address. We notified ATT of our need and only days later, without followup response, it was suggested that we somehow don't have the legal authority to install microwave (despite the fact that our 544 page contract with ATT that allows our presence within their facilities in the first place DOES SAY 'microwave' is allowed), and further they suggest we'd have to give up all of our existing contractual rights and that if it could happen, it would be only with months of delay and endless expense and bureaucratic nonsense that is only designed to slow down and de-incentivize any such initiative. The equipment we were proposing, is small, low power, lightweight, license free gear that could easily fit complete in a car and be deployed within hours without prior notice or coordination. The electrical and structural requirements are next to nothing, and present absolutely no risk to anyone or the facility. We could have had service restored and further, could have plugged a critical gap by creating an active backup telecommunications path which could be used in future emergencies. I am frustrated with the lack of cooperation to restore services during this latest incident and I think it speaks volumes about the mentality of the incumbent providers. They can't get it together, but here I am standing by with the solution at least for my own customers and why, they just don't want to allow me to do it either. Mendocino County (and northern counties also connected on this same telecommunication cable) have suffered similar telecommunications outages before. Prior to this event, a cable just north of Hopland was cut by two individuals thinking they were stealing copper, resulting in widespread outages lasting upwards of 14 hours. And prior to that, a car crash on the coast hit the one pole where the cable system comes in from the east, wiping out all services along the coast for an extended period of time. And before that, a fire in redwood valley just north of coyote valley casino along the roadway burned out the cable again as in this instance. And before that, another fire north of Willits burned the cable again. And the time before that, a backhoe south of Hopland dug up the cable and cut it, again resulting in far reaching outages affecting hundreds of thousands of people. These repeated outages are not being taken seriously and nothing in substance is being done to fortify the telecommunications network against the next disaster, despite the fact that disaster can and will occur again. We have repeatedly drawn attention to these vulnerabilities but the public perception and awareness of the risks wanes quickly once the crisis is over. I think the incumbent providers have had ample opportunity to address the underlaying causes of their repeated widespread outages, and the empty promises and assurances they have made after past prior disasters should be proof that no actual steps will be taken, that they either do not truly understand or care about the effect that loss of telecommunications services has and the risk it presents to the public. The basic fundamental problem facing the telecommunications network in Mendocino County, is the fact that it is structured without any sort of backup communication links. A primary communications cable extends north along highway 101 at Hopland and then goes into Ukiah. This cable then splits out at Ukiah and goes north up 101 thru Willits, while another segment goes west thru Boonville to Mendocino and then up and down along the coast. A cut at any of several points results in the complete isolation of communities past the cut as what occurred during the recent fire. A basic solution to such a situation then, is to have additional cables to increase the connections between areas, so that if a cable is cut and disrupts communication flowing one way, that the communications can flow over another path from another direction. But the incumbent providers have failed so far to do anything and are likely to continue to ignore this lack of redundancy. I believe that there are some realistic solutions available, and based on my business experience in Mendocino County, I have developed the beginnings of a plan of action. The short of it is, there needs to be a redundant network of geographically diverse, very high capacity telecommunication links that connect the core of the County, in order to overcome the existing problem of there being only 1 connection today. We would need new fiber to connect the major cities from alternate directions, and we further would need new connectivity to other sources of out of region telecommunication services besides AT&T (Such as Level3, who has their own independent cable route into the county). It would further require service providers and emergency responders to all lease connectivity on this redundant system for full effect, the net result however, could be a telecommunications system that stands up and continues functioning and with emergency first responders as well as the general public able to communicate during emergencies. Although I am busy with business and ensuring my customers recover from this event, I certainly am happy to add additional background or technical information if anyone is interested. Going forward, I also could also use help in identifying funding sources and other contacts who could help with some of the heavy lifting that is going to be needed here and so any pointers would certainly be appreciated. Thank you. Mike Ireton President Your Town Online, Inc DBA WillitsOnline Rural Broadband Now, LLC

5 6

facebook fna
by Aaron Gould 17 Oct '17

17 Oct '17

Anyone out here with facebook fna ? I could use an assist please, you can contact me directly. -Aaron Gould

1 0

Terminology Clarification - "Active Wave"
by Rod Beck 17 Oct '17

17 Oct '17

A financial firm asked me if a 10 gig wave offer was an "active wave". 😨 LAN PHY 10 GigE, WAN PHY 10 GigE, transparent, STM64, OC192. Yes. Active? Roderick Beck Director of Global Sales United Cable Company www.unitedcablecompany.com<http://www.unitedcablecompany.com> 85 Király utca, 1077 Budapest rod.beck(a)unitedcablecompany.com 36-30-859-5144 [1467221477350_image005.png]

4 4

4 or smaller digit ASNs
by James Breeden 16 Oct '17

16 Oct '17

Hello NANOG... I have a client interested in picking up a new AS number but they really want it to be 3 or 4 digits in length. Is there a process to request this from ARIN, or doss anyone know of unused ASns fitting this that anyone is looking to sell for some quick cash? Thanks! James Sent via the Samsung Galaxy S7 active, an AT&T 4G LTE smartphone

20 19

Re: Calgary <-> Toronto 100% Canadian Fibre Resiliency on failover
by Alyssa Moore 16 Oct '17

16 Oct '17

Regarding TransCanada: I recently read they are only just beginning to experiment with fibre optic monitoring systems for leak detection on short stretches of feeder pipeline in Alberta. The original plans for the RoW on the Northern Courier project (set to finish construction this year) included provisions for a communications conduit, but that was later scrapped. Leak detection: https://www.transcanada.com/en/stories-container/environmentsafety/new-rd-c… I doubt there's anything pipeline-related that spans the geography in question. On Fri, Oct 13, 2017 at 6:03 AM <nanog-request(a)nanog.org> wrote: > Send NANOG mailing list submissions to > nanog(a)nanog.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://mailman.nanog.org/mailman/listinfo/nanog > or, via email, send a message with subject or body 'help' to > nanog-request(a)nanog.org > > You can reach the person managing the list at > nanog-owner(a)nanog.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of NANOG digest..." > > > Today's Topics: > > 1. Seznam serveru (Lumir Srchlm) > 2. Re: Temp at Level 3 data centers (Marshall, Quincy) > 3. Re: Temp at Level 3 data centers (Matthew Pounsett) > 4. TSYS Contact (Dan White) > 5. RE: Calgary <-> Toronto 100% Canadian Fibre Resiliency on > failover (Jacques Latour) > 6. Re: 4 or smaller digit ASNs (Hank Nussbacher) > 7. Re: 4 or smaller digit ASNs (John Levine) > 8. RE: 4 or smaller digit ASNs (Naslund, Steve) > 9. Re: Temp at Level 3 data centers (Sam Silvester) > 10. Re: 4 or smaller digit ASNs (Steve Jones) > 11. Re: replacing compromised biometric authenticators (Rich Kulawiec) > 12. Re: 4 or smaller digit ASNs (valdis.kletnieks(a)vt.edu) > 13. Re: replacing compromised biometric authenticators > (Jean-Francois Mezei) > 14. Re: 4 or smaller digit ASNs (Jon Lewis) > 15. Re: Temp at Level 3 data centers (William Herrin) > 16. Re: 4 or smaller digit ASNs (Richard Hicks) > 17. Re: Temp at Level 3 data centers (Keith Stokes) > 18. Re: Temp at Level 3 data centers (Jean-Francois Mezei) > 19. Google Voice Security (J. Oquendo) > 20. Re: 4 or smaller digit ASNs (Brett Watson) > 21. Re: replacing compromised biometric authenticators (Alain Hebert) > 22. Re: 4 or smaller digit ASNs (Lee Howard) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 12 Oct 2017 15:02:11 +0200 > From: "Lumir Srchlm" <srchlm(a)its.cz> > To: " Lukáš Racek (lukas.racek(a)pentahospitals.cz > =?ISO-8859-2?B?KQ==?=" <lukas.racek(a)pentahospitals.cz>, > "=?ISO-8859-2?B?TWlyb3NsYXYgSHJpdvLhayAoZXh0ZXJuYWwp?=" > <hrivnak(a)nemosnet.cz>, "i mawsog via NANOG" <nanog(a)nanog.org> > Cc: "Tomas Blinka" <blinka(a)its.cz> > Subject: Seznam serveru > Message-ID: > < > OF16ECBD77.EEE27B0E-ONC12581B7.00477A64-C12581B7.00479CD4(a)post.its.cz> > > Content-Type: text/plain; charset="US-ASCII" > > Dobry den, > > zasilam slibeny seznam serveru. > > DC1 > > PHCZ_MIS > PHCZ_WSUS > PHCZ_RON > DC01_NV > PHCZ_ADFS01 > nv-vrc-fug-v-02 > pha-nav-v-003 > PHCZ_DC01 > DC01_NOS > PHCZ_DADFS01 > PHCZ_TERMGW > HART_NV > DC01_NSO > PHCZ_TERM1 > DC01_NSU > PHCZ_ESET > > > DC2 > PHCZ_DADFS02 > PHCZ_DC02 > PHCZ_ADFS02 > > S pozdravem > Lumir Srch > > ------------------------------ > > Message: 2 > Date: Thu, 12 Oct 2017 13:27:38 +0000 > From: "Marshall, Quincy" <Quincy.Marshall(a)reged.com> > To: "nanog(a)nanog.org" <nanog(a)nanog.org> > Subject: Re: Temp at Level 3 data centers > Message-ID: > < > 3438B611A2B2C04495EF0E1B25729C46BCD6EB(a)mbx032-e1-va-8.exch032.serverpod.net > > > > Content-Type: text/plain; charset=UTF-8 > > I have equipment in several L(3) DCs. I'd say that is generally the > exception however I have two notable facilities (smaller type 3) that have > troubles on occasion... reaching into the 80s as you commented. (Usually > during the warm southern summer days) . > > I found that my getting to know the facility manager/personnel very > useful. They gave staight up answers and have done what they could to > assist. > > -------- Original message -------- > From: Chuck Anderson <cra(a)WPI.EDU> > Date: 10/11/17 22:13 (GMT-05:00) > To: nanog(a)nanog.org > Subject: Re: Temp at Level 3 data centers > > Install an air conditioner in your rack. > > On Wed, Oct 11, 2017 at 02:39:19PM -0500, Andrew Latham wrote: > > David > > > > The issue has several components and is vendor agnostic. > > > > Set Point: The systems are specifically set at a temperature > > Capacity Ability: The systems can maintain a temperature > > Customer Desire: What you expect from sales promises. > > Sales Promise: What they might carefully avoid promising. > > > > I suggest you review your SLA and discuss with legal asap. You could > have a > > document defining your question's answer already but it sits in a filing > > cabinet file labeled business continuity. > > > > If the set point is X then they likely would answer quickly that that is > > the case. > > If the capacity is lacking then they would likely redirect the issue. > > If they don't care about the customer that alone should be an indicator > > If a promise exists in the SLA then the ball is in your court > > > > >From the emails I fear that we have confirmed that this is normal. So > your > > question "Is the temperature at Level 3 Data Centers normally in the > 80-90F > > range?" sounds like a Yes. > > > > Regardless of the situation always ask for names, titles, and ask vendors > > to repeat critical information like the status of cooling in a building > > designed to deal with cooling. Keep the vendors that do it well. > > > > > > > > On Wed, Oct 11, 2017 at 7:31 AM, David Hubbard < > > dhubbard(a)dino.hostasaurus.com> wrote: > > > > > Curious if anyone on here colo’s equipment at a Level 3 facility and > has > > > found the temperature unacceptably warm? I’m having that experience > > > currently, where ambient temp is in the 80’s, but they tell me that’s > > > perfectly fine because vented tiles have been placed in front of all > > > equipment racks. My equipment is alarming for high temps, so > obviously not > > > fine. Trying to find my way up to whomever I can complain to that’s > in a > > > position to do something about it but it seems the support staff have > been > > > told to brush questions about temp off as much as possible. Was > wondering > > > if this is a country-wide thing for them or unique to the data center I > > > have equipment in. I have equipment in several others from different > > > companies and most are probably 15-20 degrees cooler. > > > > > > Thanks, > > > > > > David > > --------------------------------------------------------------------------------------- > This email has been scanned for email related threats and delivered > safely by Mimecast. > For more information please visit http://www.mimecast.com > > --------------------------------------------------------------------------------------- > > ------------------------------ > > Message: 3 > Date: Thu, 12 Oct 2017 10:04:08 -0400 > From: Matthew Pounsett <matt(a)conundrum.com> > To: "nanog(a)nanog.org" <nanog(a)nanog.org>, dhubbard(a)dino.hostasaurus.com > Subject: Re: Temp at Level 3 data centers > Message-ID: > <CAAiTEH-dbvsy7XD5EBirwV=QYP=FqANS= > gPxyqsFwmFmZZuv3w(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > I'm a few years removed from having direct involvement in our DCs now, so I > don't have an example on hand to look at. Is cooling (and in-cabinet > temperature) not a part of the SLA? If it is, then there shouldn't be a > question of the DC staff brushing off complaints about the > temperature–either L3 should fix it or pay the penalties. If it isn't, > then I'd suggest having a look at your contract (and possibly looking a new > DCs) at renewal time. > > > ------------------------------ > > Message: 4 > Date: Thu, 12 Oct 2017 11:18:48 -0500 > From: Dan White <dwhite(a)olp.net> > To: <nanog(a)nanog.org> > Subject: TSYS Contact > Message-ID: <20171012161848.xggy2ixm24b3ww7m(a)dan.olp.net> > Content-Type: text/plain; charset="us-ascii"; format=flowed > > If there are any personnel from TSYS here, please contact me off list. > > -- > Dan White > BTC Broadband > Network Admin Lead > Ph 918.366.0248 <(918)%20366-0248> (direct) main: (918)366-8000 > <(918)%20366-8000> > Fax 918.366.6610 <(918)%20366-6610> email: dwhite(a)olp.net > http://www.btcbroadband.com > > > ------------------------------ > > Message: 5 > Date: Thu, 12 Oct 2017 16:46:55 +0000 > From: Jacques Latour <Jacques.Latour(a)cira.ca> > To: Jean-Francois Mezei <jfmezei_nanog(a)vaxination.ca>, > "nanog(a)nanog.org" <nanog(a)nanog.org> > Subject: RE: Calgary <-> Toronto 100% Canadian Fibre Resiliency on > failover > Message-ID: <b993e2657bcf452ea6557e35d58897d6(a)cira.ca> > Content-Type: text/plain; charset="utf-8" > > > > > Since the Trans Canada highway in that part of Ontario is actually a 2 > lane > > rural road, I am not sure people would have laid fibre along it knowing > the > > progressive work to widen it might require frequent relocation of the > fibre. > > That's a good point, what about along the Trans-Canadian pipeline? > https://www.transcanada.com/en/operations/maps/ Anyone know if there's > fibre there? > > ------------------------------ > > Message: 6 > Date: Thu, 12 Oct 2017 20:39:41 +0300 > From: Hank Nussbacher <hank(a)efes.iucc.ac.il> > To: nanog(a)nanog.org > Subject: Re: 4 or smaller digit ASNs > Message-ID: <cfd4c969-b6f1-5a23-267f-ae820ef3e03c(a)efes.iucc.ac.il> > Content-Type: text/plain; charset=utf-8 > > On 12/10/2017 08:47, Mel Beckman wrote: > > James, > > > > As far as I know, you can't buy an existing ASN for any amount of money. > You can buy the company that owns it, but that seems like boiling tea with > a blowtorch. > > > > I sincerely doubt there are unused low-number ASNs, but you could always > ask ARIN. > > > > I'm curious what your client's rationale is for wanting a low ASN. > It is called ASN-envy. > > -Hank > AS378 :-) > > > > It can't be efficiency, since the numbers all take the same number of > bits ultimately. If they just like small numbers, I'd advise them to forget > it -- life is too short. If they have a real technical reason that nobody > has foreseen (or at least I haven't foreseen), I'd love to hear it. > > > > > > -mel beckman > > > >> On Oct 11, 2017, at 10:01 PM, James Breeden <James(a)arenalgroup.co> > wrote: > >> > >> Hello NANOG... > >> > >> I have a client interested in picking up a new AS number but they > really want it to be 3 or 4 digits in length. > >> > >> Is there a process to request this from ARIN, or doss anyone know of > unused ASns fitting this that anyone is looking to sell for some quick cash? > >> > >> Thanks! > >> James > >> > >> > >> > >> > >> Sent via the Samsung Galaxy S7 active, an AT&T 4G LTE smartphone > > > > > ------------------------------ > > Message: 7 > Date: 12 Oct 2017 20:28:49 -0000 > From: "John Levine" <johnl(a)iecc.com> > To: nanog(a)nanog.org > Subject: Re: 4 or smaller digit ASNs > Message-ID: <20171012202849.43329.qmail(a)ary.lan> > Content-Type: text/plain; charset=utf-8 > > In article <20171012070551.GA52873(a)spider.typo.org> you write: > >> > I'm curious what your client's rationale is for wanting a low ASN. > > > >Dare I say it? > > > >Nerds often get overly excited at things that are generally pretty > >small... > > Too bad I can't sell my old NSI handle. > > R's, > JL7 > > > ------------------------------ > > Message: 8 > Date: Thu, 12 Oct 2017 20:40:42 +0000 > From: "Naslund, Steve" <SNaslund(a)medline.com> > To: "nanog(a)nanog.org" <nanog(a)nanog.org> > Subject: RE: 4 or smaller digit ASNs > Message-ID: > < > 9578293AE169674F9A048B2BC9A081B40262159F01(a)MUNPRDMBXA1.medline.com> > Content-Type: text/plain; charset="utf-8" > > I've got a DDN TAC access card if they are interested in that as well. > Might even be able to dig up a BBN PAD for them too. > > Steven Naslund > Chicago IL > > -----Original Message----- > From: NANOG [mailto:nanog-bounces@nanog.org] On Behalf Of John Levine > Sent: Thursday, October 12, 2017 3:29 PM > To: nanog(a)nanog.org > Subject: Re: 4 or smaller digit ASNs > > In article <20171012070551.GA52873(a)spider.typo.org> you write: > >> > I'm curious what your client's rationale is for wanting a low ASN. > > > >Dare I say it? > > > >Nerds often get overly excited at things that are generally pretty > >small... > > Too bad I can't sell my old NSI handle. > > R's, > JL7 > > ------------------------------ > > Message: 9 > Date: Thu, 12 Oct 2017 10:22:31 +1030 > From: Sam Silvester <sam.silvester(a)gmail.com> > To: "nanog(a)nanog.org" <nanog(a)nanog.org> > Subject: Re: Temp at Level 3 data centers > Message-ID: > <CAAAhk69MfV7c+ZVzftiH-yeqOL4V5=kWJ-j= > YNRvBeZdUAwkAA(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > On Thu, Oct 12, 2017 at 3:39 AM, Naslund, Steve <SNaslund(a)medline.com> > wrote: > > > If the ambient temperature is higher is means the temperatures throughout > > the device would be higher and the temp at those points is what really > > matters. I would also be concerned because if they lose one of the a/c > > units what would the ambient temperature rise to? I would want them to > > tell me what the set point of the a/c actually is. > > > > Bottom line 80 F input air is too hot in my opinion and apparently the > > equipment's opinion as well. > > > > My quick thoughts on the matter: > > 1. Above all else, know what your DC provider states in their SLA/contract. > 2. It's never a bad idea to try to be on the best possible personal terms > with the DC manager(s), the better you get along the more they're inclined > to share knowledge/issues and work with you on any concerns. > 3. You can't infer faults or lack of redundancy from the running > temperature - by way of example several facilities I know run at 25 degrees > celsius but if a chilled water unit in a given data hall fails there's a > number of DX units held in standby to take over. This is where point 2 > comes in handy as knowing somebody on the ground they'll often be quite > happy to run through failure scenarios with you and help make sure > everybody is happy with the risk mitigation strategy. > > Out of idle curiosity - I'm curious as to if the equipment that is alarming > is configurable or not? Reason I ask is I've heard users claiming > environmental parameters were out of spec before, but then it turned out it > was their own environmental monitoring they'd installed in the rack (using > default parameters out of the box, not configured to match the facility > SLA) that was complaining about a set point of 25... > > Cheers, > > Sam > > > ------------------------------ > > Message: 10 > Date: Thu, 12 Oct 2017 00:55:35 -0500 > From: Steve Jones <thatoneguysteve(a)gmail.com> > To: Mel Beckman <mel(a)beckman.org> > Cc: James Breeden <James(a)arenalgroup.co>, "nanog(a)nanog.org" > <nanog(a)nanog.org> > Subject: Re: 4 or smaller digit ASNs > Message-ID: > <CAGOa4nOgoZ1huFcQFHUKi_TpPgaEiuR2L= > hFy5_qn84QunoAkw(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > as i understand it, you cant do bgp at all under 5 > > On Thu, Oct 12, 2017 at 12:47 AM, Mel Beckman <mel(a)beckman.org> wrote: > > > James, > > > > As far as I know, you can't buy an existing ASN for any amount of money. > > You can buy the company that owns it, but that seems like boiling tea > with > > a blowtorch. > > > > I sincerely doubt there are unused low-number ASNs, but you could always > > ask ARIN. > > > > I'm curious what your client's rationale is for wanting a low ASN. It > > can't be efficiency, since the numbers all take the same number of bits > > ultimately. If they just like small numbers, I'd advise them to forget it > > -- life is too short. If they have a real technical reason that nobody > has > > foreseen (or at least I haven't foreseen), I'd love to hear it. > > > > > > -mel beckman > > > > > On Oct 11, 2017, at 10:01 PM, James Breeden <James(a)arenalgroup.co> > > wrote: > > > > > > Hello NANOG... > > > > > > I have a client interested in picking up a new AS number but they > really > > want it to be 3 or 4 digits in length. > > > > > > Is there a process to request this from ARIN, or doss anyone know of > > unused ASns fitting this that anyone is looking to sell for some quick > cash? > > > > > > Thanks! > > > James > > > > > > > > > > > > > > > Sent via the Samsung Galaxy S7 active, an AT&T 4G LTE smartphone > > > > > ------------------------------ > > Message: 11 > Date: Thu, 12 Oct 2017 16:58:35 -0400 > From: Rich Kulawiec <rsk(a)gsp.org> > To: nanog(a)nanog.org > Subject: Re: replacing compromised biometric authenticators > Message-ID: <20171012205835.GA5109(a)gsp.org> > Content-Type: text/plain; charset=us-ascii > > On Wed, Oct 11, 2017 at 05:04:08PM -0400, Ken Chase wrote: > > If the current best operating practice is to avoid biometrics, why are > they > > still in use out here? > > (1) for the same reason some idiots still use captchas > (2) new hotness > old and busted, regardless of merits > (3) because they facilitate coerced risk transference away from the > people who are actually responsible (and are paid to be so) to the > people who shouldn't be responsible (and aren't paid to be) > > ---rsk > > > > ------------------------------ > > Message: 12 > Date: Thu, 12 Oct 2017 16:58:52 -0400 > From: valdis.kletnieks(a)vt.edu > To: Steve Jones <thatoneguysteve(a)gmail.com> > Cc: Mel Beckman <mel(a)beckman.org>, "nanog(a)nanog.org" <nanog(a)nanog.org> > Subject: Re: 4 or smaller digit ASNs > Message-ID: <21717.1507841932(a)turing-police.cc.vt.edu> > Content-Type: text/plain; charset="utf-8" > > On Thu, 12 Oct 2017 00:55:35 -0500, Steve Jones said: > > as i understand it, you cant do bgp at all under 5 > > AS1312 does BGP quite nicely... Not sure what you meant there, unless the > text/plain lost the <font=sarcasm> tags... > >

1 0

Gonna be a long day for anybody with CPE that does WPA2..
by valdis.kletnieks＠vt.edu 16 Oct '17

16 Oct '17

Looks like WPA2 may have just become the new WEP. And it looks like we're all going to be reflashing a lot of devices. "The proof-of-concept exploit is called KRACK, short for Key Reinstallation Attacks. The research has been a closely guarded secret for weeks ahead of a coordinated disclosure that's scheduled for 8 a.m. Monday, east coast time. An advisory the US CERT recently distributed to about 100 organizations described the research this way: "US-CERT has become aware of several key management vulnerabilities in the 4-way handshake of the Wi-Fi Protected Access II (WPA2) security protocol. The impact of exploiting these vulnerabilities includes decryption, packet replay, TCP connection hijacking, HTTP content injection, and others. Note that as protocol-level issues, most or all correct implementations of the standard will be affected. The CERT/CC and the reporting researcher KU Leuven, will be publicly disclosing these vulnerabilities on 16 October 2017." https://arstechnica.com/information-technology/2017/10/severe-flaw-in-wpa2-…

9 8

19 years ago today (Oct 16th, 1998) we lost our guide - Jon Postel - RFC2468
by Rodney Joffe 15 Oct '17

15 Oct '17

To us greaybeards, it feels like just yesterday. And as Randy points out, this coming Friday we also remember Abha who passed away 16 years ago, in 2001. http://www.neebu.net/~khuon/abha/ Sigh.

3 2

abha
by Randy Bush 13 Oct '17

13 Oct '17

a moment of silence on this 16th anniversary of her tragic death

3 3

Temp at Level 3 data centers
by David Hubbard 13 Oct '17

13 Oct '17

Curious if anyone on here colo’s equipment at a Level 3 facility and has found the temperature unacceptably warm? I’m having that experience currently, where ambient temp is in the 80’s, but they tell me that’s perfectly fine because vented tiles have been placed in front of all equipment racks. My equipment is alarming for high temps, so obviously not fine. Trying to find my way up to whomever I can complain to that’s in a position to do something about it but it seems the support staff have been told to brush questions about temp off as much as possible. Was wondering if this is a country-wide thing for them or unique to the data center I have equipment in. I have equipment in several others from different companies and most are probably 15-20 degrees cooler. Thanks, David

23 29

Hong Kong to SHANGHAI routes
by Michael Morrison 13 Oct '17

13 Oct '17

We have noticed there's been an increase in latency from Hong Kong to SHANGHAI. Usually running about 70-80ms, up over 300ms now. Per a traceroute I can see NTT is jumping over to LA before going over to Sha(China Unicom) via Level 3. Anyone else on this thread seen this behavior and or have any information at to why this is happening? Level3? China Unicom? NTT? Any engineers from these companies on this thread? Regards, Michael M Sent from my iPhone

1 0