- NANOG - lists.nanog.org

Re: Interesting new dns failures
by Tim Franklin 22 May '07

22 May '07

Jay R. Ashworth wrote: > Such is not my experience, and I strongly advise people against such > stupidity. Oh, I'd absolutely advise against it - but the branding people and the lawyers typically think otherwise. The case that gets a bit murky for me is genuinely multi-national entities. In *theory* that ought to be what .com is for, but registering yourcompany.cc for every country where you have an operating entity looks sort of legit. (Yes, I've been asked to do this before.) > But if we play to their ignorance, they'll *never* learn, will they? > > I don't have overmuch trouble getting people to understand microsys.us Oh, if there's the slightest hint of interest in learning, I'll explain - apologies if I implied otherwise. Regards, Tim.

2 2

Re: OK - functioning administration of 44.0.0.0/8
by Brandon Butterworth 22 May '07

22 May '07

> Any reason it hasn't migrated over to IPv6 and 44/8 returned to the > free pool? Old software, efficiency (lots of the embedded low power hardware), no need to as 44. is all the space needed. Lots of other reasons I don't know When it started it was quite advanced, it was pretty much the only IP in the UK in the mid 80s. For some ISPs UK dial up Internet access started out using software developed for ampr Google and http://en.wikipedia.org/wiki/KA9Q have more details for those wondering. brandon

3 3

Re: OK - functioning administration of 44.0.0.0/8
by Brandon Butterworth 22 May '07

22 May '07

> The last time I looked into this there wasn't anything being done with > the block It's been in use for a very long time (>10years) > but now I see lots of people assigned to do various things - > should have looked before I said anything, but in 2001 this was totally > dead, at least in Iowa/Nebraska. Over the last few years broadband availability has obsoleted many uses of it. There was some 44. vpn'd over the Internet (probably still is, I closed the GB7BBC gateway into that last year) As there are legal restrictions on traffic into amateur networks it's generally not directly connected to the Internet brandon

2 1

Re: Interesting new dns failures
by Tim Franklin 21 May '07

21 May '07

Stewart Honsberger wrote: > Which is why new TLDs like .xxx et al. are redundant. I can see that > becoming a haven for vanity domains. It gets worse. In a previous life, I had the job of de-bunking^Wevaluating whichever bunch of alt-root snake-oil salesmen had managed to get an audience with our CTO with the pitch that it would be absolutely brilliant if everyone could just invent their own TLD. "Just imagine - Fooboz could own .fooboz, then they could have sales.fooboz, support.fooboz, widgets.fooboz..." "You know sales.fooboz.com, www.sales.fooboz.com, and www.fooboz.com/sales all work today, right?" Added to that their own panel of "Internet experts" to decide if a given Fooboz out of 47 (last time I checked) potential trade-mark holders on 'fooboz' and countless possible companies of the same name has the *real* claim on the .fooboz TLD. Feh. That way lies madness. Regards, Tim.

1 0

RE: qwest backbone
by James Laszko 21 May '07

21 May '07

we are seeing big issues between sbc/at&t and anything connected to level3... James -----Original Message----- From: "Gregori Parker" <Gregori.Parker(a)theplatform.com> Subj: RE: qwest backbone Date: Mon May 21, 2007 1:36 pm Size: 676 bytes To: "NANOG list" <nanog(a)nanog.org> Savvis is also reporting severed fiber, unclear as to whether it's their own or upstream -----Original Message----- From: owner-nanog(a)merit.edu [mailto:owner-nanog@merit.edu] On Behalf Of prue Sent: Monday, May 21, 2007 1:12 PM To: davidu(a)everydns.net Cc: nanog Subject: Re: qwest backbone Hi, I believe I can offer some insight into this outage. I have gotten a report which is affecting another network: Level3 fiber cut between Seattle and Olympia Olympia is a city south of Seattle about 50 miles or so, for those who don't know the area. I imagine, based on your reports, that Qwest is also being affected by the fiber cut. Walt

1 0

Re: qwest backbone
by prue 21 May '07

21 May '07

Hi, I believe I can offer some insight into this outage. I have gotten a report which is affecting another network: Level3 fiber cut between Seattle and Olympia Olympia is a city south of Seattle about 50 miles or so, for those who don't know the area. I imagine, based on your reports, that Qwest is also being affected by the fiber cut. Walt

2 1

qwest backbone
by Philip Lavine 21 May '07

21 May '07

Any issues on the qwest backbone ____________________________________________________________________________________Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase. http://farechase.yahoo.com/

4 4

Re: Interesting new dns failures
by Fergie 21 May '07

21 May '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - -- "Chris L. Morrow" <christopher.morrow(a)verizonbusiness.com> wrote: >> >> While I agree with you, there are many of us who know that these >> fast-flux hosts are malicious due to malware & malicious traffic >> analysis... > >Oh, so we switched from 'the domain is bad because..' to 'the hosts using >the domain are bad because...' I wasn't assuming some piece of intel at >the TLD that told the TLD that 'hostX that was just named NS for domain >foo.bar is also compromised'. I was assuming a s'simple' system of >'changing NS's X times in Y period == bad'. I admit that's a might naive, >but given the number, breadth, content, operators of lists of 'bad things' >on the internet today I'm not sure I'd rely on them for a global decision >making process, especially if I were a TLD operator potentially liable for >removal of a domain used to process real business :( Well, I don't think I ever implied that, but let's say that there are certainly some fast-flux behavior (fluxing across multiple administratively managed prefix blocks, NS fast-flux) which should immediately raise a red flag. Decisions based on those flags are policy issues -- whether or not someone decides to take action upon only on that information or do further research, is something that has to be determined by the person(s) who detect the behavior, etc. Having said that, most people don't even realize that fast-flux exists... - - ferg -----BEGIN PGP SIGNATURE----- Version: PGP Desktop 9.6.1 (Build 1012) wj8DBQFGUeNhq1pz9mNUZTMRAgC5AJ98cW092rV7ghrlIzjLP89qjiurDACdEFaV qUxEcKgfr42Mh9IQAOmaKr0= =Hrk0 -----END PGP SIGNATURE----- -- "Fergie", a.k.a. Paul Ferguson Engineering Architecture for the Internet fergdawg(at)netzero.net ferg's tech blog: http://fergdawg.blogspot.com/

1 0

Re: Interesting new dns failures
by Fergie 21 May '07

21 May '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - -- "Chris L. Morrow" <christopher.morrow(a)verizonbusiness.com> wrote: >So, I think that what we (security folks) want is probably not to >auto-squish domains in the TLD because of NS's moving about at some rate >other than 'normal' but to be able to ask for a quick takedown of said >domain, yes? I don't think we'll be able to reduce false positive rates >low enough to be acceptable with an 'auto-squish' method :( Hi Chris, While I agree with you, there are many of us who know that these fast-flux hosts are malicious due to malware & malicious traffic analysis... I completely agree with you, however, on the issue of making assumptions that it will always be malicious -- of course, that will not always be the case. :-) - - ferg -----BEGIN PGP SIGNATURE----- Version: PGP Desktop 9.6.1 (Build 1012) wj8DBQFGUd/7q1pz9mNUZTMRAigSAKDgooaGUsp+GT0sEYcEOivjY0afFwCfWmk6 EaWuXUl9W+3+uQEAEJ1c1SQ= =V6Mu -----END PGP SIGNATURE----- -- "Fergie", a.k.a. Paul Ferguson Engineering Architecture for the Internet fergdawg(at)netzero.net ferg's tech blog: http://fergdawg.blogspot.com/

2 1

[info@arin.net: [arin-announce] ARIN Board Advises Internet Community on Migration to IPv6]
by bmanning＠karoshi.com 21 May '07

21 May '07

this might be of interest to the operator community. --bill --------- forwarded --------------- ARIN and the other Regional Internet Registries have distributed Internet Protocol version 6, IPv6, alongside IPv4 since 1999. To date, ARIN has issued both protocol versions in tandem and has not advocated one over the other. ARIN has closely monitored trends in demand and distribution for both protocol versions with the understanding that the IPv4 available resource pool would continue to diminish. The available IPv4 resource pool has now been reduced to the point that ARIN is compelled to advise the Internet community that migration to IPv6 is necessary for any applications that require ongoing availability from ARIN of contiguous IP number resources. On 7 May 2007, the ARIN Board of Trustees passed the following resolution: RESOLUTION OF THE BOARD OF TRUSTEES OF ARIN ON INTERNET PROTOCOL NUMBERING RESOURCE AVAILABILITY WHEREAS, community access to Internet Protocol (IP) numbering Resources has proved essential to the successful growth of the Internet; and, WHEREAS, ongoing community access to Internet Protocol version 4 (IPv4) numbering resources can not be assured indefinitely; and, WHEREAS, Internet Protocol version 6 (IPv6) numbering resources are available and suitable for many Internet applications, BE IT RESOLVED, that this Board of Trustees hereby advises the Internet community that migration to IPv6 numbering resources is necessary for any applications which require ongoing availability from ARIN of contiguous IP numbering resources; and, BE IT ORDERED, that this Board of Trustees hereby directs ARIN staff to take any and all measures necessary to assure veracity of applications to ARIN for IPv4 numbering resources; and, BE IT RESOLVED, that this Board of Trustees hereby requests the ARIN Advisory Council to consider Internet Numbering Resource Policy changes advisable to encourage migration to IPv6 numbering resources where possible. Implementation of this resolution will include both internal and external components. Internally, ARIN will review its resource request procedures and continue to provide policy experience reports to the Advisory Council. Externally, ARIN will send progress announcements to the ARIN community as well as the wider technical audience, government agencies, and media outlets. ARIN will produce new documentation, from basic introductory fact sheets to FAQs on how this resolution will affect users in the region. ARIN will focus on IPv6 in many of its general outreach activities, such as speaking engagements, trade shows, and technical community meetings. For more information visit the IPv6 Information Center at: http://www.arin.net/v6/v6-info.html. Regards, Raymond A. Plzak President and CEO American Registry for Internet Numbers (ARIN) ----- End forwarded message -----

1 0