Re: Undersea cable damages in the Atlantic?

Also FWIW, we've been informed of outages on TGN-EA (since 15/01/22) and IMEWE (since 15/10/21), both "away from the Mumbai coast." No ETR currently available. Rob

Re: Alien waves

Hi, Alien wavelengths is a fairly old concept and more generally just refers to running any wavelength over a DWDM system that isn't generated by that system's own transponders. These days it is more about leasing spectrum (Spectrum as a Service), but that comes in several different flavours. Th

Re: Whois vs GDPR, latest news

I don't. I have better things to do than babysit various accounts I've signed up over the years. Just because someone signs up for an account and forgets about it is not a good enough reason to have my information DESTROYED WITHOUT MY PERMISSION if I do happen to be busy that week to sign in som

Re: Cogent BCP-38

> Well, if you are using public IP addresses for infra you are violating your > RIR’s policy more than likely. [Citation needed.] :) Rob

Re: BBC reports Kenya fiber break

> Constantly shifting ice shelves and glaciers make a terrestrial cable > landing very difficult to implement on Antarctica.  Satellite connectivity > is likely the only feasible option.  There are very few places in > Antarctica that are reliably ice-free enough of the time to make a viable > terr

Re: Cogent IPv6

> Please don't use /127: > > Use of /127 Prefix Length Between Routers Considered Harmful >    http://tools.ietf.org/html/rfc3627 Do keep up. :-) Rob

Re: Packet over SONET failback

> PoS failure detection happens in under 50ms, but what about the failback?   > Same deal?  I ask because I've got two routers connected to opposite ends of > a spare PoS link that I've been playing with and I'm noticing that the > failback on the far side seems to be about 15 seconds (assuming t

Re: Using IPv6 with prefixes shorter than a /64 on a LAN

> You must be kiddin'... You're considering going through this mess again > in a few decades? I'm mildly surprised if you think we're going to be done with *this* mess in a few decades. Rob

Re: Inquiries to Acquire IPs

I saw a few reports of those today and wrote a short note to forewarn some other European R&E networks, plus our customers. http://webmedia.company.ja.net/edlabblogs/developmenteye/2010/07/03/wanted-memorable-24-for-us5k/ Yup, I know the date on the blog is off by one. :) Cheers, Rob

Re: ISP customer assignments

> This is a bit annoying though, yeah. But, I'm not sure I can think of a good > solution that doesn't involve us changing the routing system so that we can > handle a huge amount of intentional de-aggregates or something. Within the RIPE region we're currently discussing a document on IPv6 route

Re: Outages in wales ?

> but a buddy in wales have massive problems with internet connectivity For those that don't know, Wales is a relatively small constituent country of the United Kingdom (size-wise, it is 'about the size of Wales'): Small as it is, it has a numbe

Re: IPv4 Anycast?

> Then there is basically no inter-As anycast besides the anycast prefix for > DNS root, since I only noticed like 8 prefixes that are announced by more > than 3 ASes.. ...but inter-domain anycast is often achieved by using a single origin AS, which is then transited through the 'provider' autonom

Re: Google Over IPV6

> When I posted my original note, I was not really looking for end user > feedback, but rather is anyone peering V6 with them on either a public > fabric or private peer. Any idea if they have native V6 transit, or are > tunneling, and to where. They are peering over some IXPs and private peerings

Re: Dynamic IP log retention = 0?

> Not to disagree with any of your points, but the OP (which you quoted!) > was talking about Covad, while you're bashing Comcast. Any sufficiently advanced NANOG conversation is indistinguishable from Comcast-bashing. Rob (Not agreeing, just observing.)

Re: Mcast mpeg2 and unicast h.264 for NANOG-45

>> 25 mbit HDV, mpeg Transport Stream, UDP: 233.0.59.45 port 1234 > > Not seeing the mcast feed at all. What's the source address so we can try > to mtrace to it? I see it from: 128.104.23.100 (kona.doit.wisc.edu). Cheers, Rob

Re: Is it time to abandon bogon prefix filters?

> I see a number of hits on those entries, especially on 94/8. and 0/8. You do know that 94/8 has been assigned to the RIPE NCC, right? :-) Cheers, Rob

Re: "2M today, 10M with no change in technology"? An informal survey.

Ross, > > In another mailing list, someone has asserted that "noone believes > > router vendors who say [they can support 2M routes today and 10M with > > no change in technology]". > > Can you tell us who said this on which email list? In terms of the original statement, we were also given this