- Test - lists.nanog.org

Re: ICANN - Formal Complaint re Verisign
by John Neiberger 18 Sep '03

18 Sep '03

>>>> Marc MERLIN <marc_news(a)merlins.org> 9/18/03 9:27:11 AM >>> > >On Thu, Sep 18, 2003 at 11:42:19AM +0100, Michael.Dillon(a)radianz.com wrote: >> And you can get SSL certs from alternative sources such as GeoTrust >> http://www.geotrust.com/ > >Bzzz, geotrust is Verisign > >http://www.google.com/search?sourceid=mozclient&ie=utf-8&oe=utf-8&q=Thawte+… >ought+by+Verisign > >Marc If GeoTrust is Verisign, why do they make a big deal out of competing with Verisign? http://www.geotrust.com/resources/market_share/index.htm John --

4 3

New routeviews service available (Address/Prefix -> AS/ASPATH mappings)
by David Meyer 18 Sep '03

18 Sep '03

All, In response to requests from many folks asking for prefix to AS mappings, routeviews is now providing 2 new services mapping and address or prefix to its origin AS and to its ASPath. These services are available via two zones: (i). asn.routeviews.org asn.routeviews.org maps an address or prefix into its origin AS, prefix, and prefix length, as seen by route-views2.routeviews.org (the data is held in TXT records). For example, the following command % dig txt 223.128.asn.routeviews.org returns (among other things) 223.128.asn.routeviews.org. 86400 IN TXT "3582" "128.223.0.0" "16" The syntax here is: "AS" "Prefix" "Prefix Length" (ii). aspath.routeviews.org aspath.routeviews.org is similar to asn.routeviews.org, except that it maps an address or prefix into the ASpath (rather than origin AS), prefix, and prefix length, as seen by route-views2.routeviews.org (again, the data is held in TXT records). For example, the following command % dig txt 223.128.aspath.routeviews.org returns (among other things) 223.128.aspath.routeviews.org. 86400 IN TXT "286 209 3356 3701 3582" "128.223.0.0" "16" The syntax here is: "ASPath" "Prefix" "Prefix Length" These zones are built twice per-day, 11:45 and 23:45 UTC. Finally, please let us know (help(a)routeviews.org) if you have questions, comments or suggestions for ways we might otherwise improve this service. One note: note that these zones are quite large, and reloading these produces a period of a few minutes during which the server may not reply. Thanks, Dave

1 0

IP issues with .com/.net change?
by Alex Kamantauskas 18 Sep '03

18 Sep '03

Not really operational content, but I was wondering if there was an intellectual property issue with the Verisign .com/.net redirect? For instance, <http://searchthewebwithgoogle.com/> brings you to a Verisign search engine. Or, even better, <http://getyourdomainnameatregister.com/> will bring you to a Verisign website. -- /ak

5 6

Virus uptick?
by David Lesher 18 Sep '03

18 Sep '03

I'm suddenly getting 3-4x the "M$ patch" and "bounced mail" virus attacks as compared to 2-3 days ago. Is this perhaps a result of VeriSlime's actions? [Note I'm talking raw volume at my accounts; so it's not the result of local filtering breaking.] -- A host is a host from coast to coast.................wb8foz(a)nrk.com & no one will talk to a host that's close........[v].(301) 56-LINUX Unless the host (that isn't close).........................pob 1433 is busy, hung or dead....................................20915-1433

4 3

Verisign suggestion
by Gerald 18 Sep '03

18 Sep '03

I'm just as irritated as most about the new executive decision that has been currently forced on us by Verisign which I really hope is reverted. Certain pieces of the news blurbs are bouncing around in my head and I came up with something for you to think about. The part of the Verisign thing that bugs me most at the moment: They don't pay a thing for all of these domains that they are now accepting queries for. It would seem to me to our benefit as an Internet community to word this in our favor and send Verisign a bill for manipulating their monopoly on the .net and .com zones. My suggestion: Since they are now accepting web queries on all of these typo domains, they should pay a reasonable fee (close to a full domain name registration fee) for each misguided soul that winds up on the Verisign web site. I believe the proceeds from this new bill they have brought upon themselves should help fund the organizations that entrusted Verisign to the task of holding the .net and .com zone. (IAB, ICANN, ... whomever is supposed to slap them back into doing what they were previously assigned them to do no more, no less) Are IAB/ICANN...etc non-profit? I really don't know who it should go to, but if there is money there, I'm sure it can improve something we collectively need. I also believe those same organizations deserve a cut of any related profit. If Yahoo/Inktomi pays $0.50 per click/search through, send $0.25 to IAB to improve $X. I think the "for free" angle any overseeing body wants to address this from. Speak to them in their language: "You just misappropriated something for free." I think we need to be ready to consider both of their responses to that: - reverting to the proper error messages (Amen we all go home...err wherever you go when you're not doing this) - making use of fixing the "for free" part. (read: using the profit for the community) Thus far, I've heard no mention of putting this to our own use. ...and for heavens sake, stop accepting any kind of request at all on port 25!! Just shut it down altogether. There is no reason for you to accept any connection of any kind on port 25! ...shutting up now, Gerald - How are ya? Never been better, ... Just once I'd like to be better.

6 6

RE: Worst design decisions?
by Colin Brown 18 Sep '03

18 Sep '03

I can't stand it when I sit down and find the keyboard in front of me has moved the "backslash" key. It drives me crazy and prompts me to find a real keyboard right away to work with. CB

1 0

Re: Virus uptick?
by David Lesher 18 Sep '03

18 Sep '03

I overlooked the OBVIOUS reason that someone just mentioned: > There is a new worm: > http://www.f-secure.com/v-descs/swen.shtml Damn, we need a TV-Guide type page listing all the first run and rerun M$ viruses. It's just too hard to keep them all straight.. -- A host is a host from coast to coast.................wb8foz(a)nrk.com & no one will talk to a host that's close........[v].(301) 56-LINUX Unless the host (that isn't close).........................pob 1433 is busy, hung or dead....................................20915-1433

1 0

Contact from Verio
by Joiner, Joshua 18 Sep '03

18 Sep '03

Someone from Verio please contact me off list. We are experiencing some routing issues through/to your network. Thanks, Josh

1 0

Re: Root Server Operators (Re: What *are* they smoking?)
by Paul Vixie 18 Sep '03

18 Sep '03

actually, i had it convincingly argued to me today that wildcards in root or top level domains were likely to be security problems, and that domains like .museum were the exception rather than the rule, and that bind's configuration should permit a knob like "don't accept anything but delegations unless it's .museum or a non-root non-tld". i guess the ietf has a lot to think about now. re: > Date: Wed, 17 Sep 2003 09:58:40 -0500 > From: Jack Bates <jbates(a)brightok.net> > User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4) Gecko/20030624 > To: Paul Vixie <paul(a)vix.com> > Cc: nanog(a)merit.edu > Subject: Re: Root Server Operators (Re: What *are* they smoking?) > Sender: owner-nanog(a)merit.edu > > > Paul Vixie wrote: > > no. not just because that's not how our internal hashing works, but > > because "hosted" tld's like .museum have had wildcards from day 1 and > > the registrants there are perfectly comfortable with them. there's > > no one-policy-fits-all when it comes to tld's, so we would not want > > to offer a knob that tried to follow a single policy for all tld's. > > I agree Paul. This is a policy issue and not a technical issue. TLDs that > are sponsored or setup with a specific design sometimes do and should be > allowed to use the wildcard for the tld. The issue has become that net and > com are public trusts and changes were made to them without authorization > by the public and damage was caused as a result. > > Just as root server operators are subject to operating as IANA dictates, so > should Verisign be subject to operating as IAB and ICANN dictate. The > Internet as a whole depends on the predictability of TLDs. It is impossible > to maintain a security policy based on unpredictable information. > > I would recommend that the TLDs which do utilize wildcards setup or > restrict such use in a predictable manner. While historically it has not > been an issue, such as nonexistant .museum domains being forged in email > envelopes, such practices could be exploited at a later time. The ability > to recognize that a domain is not registered and should not be used is > paramount in basic forgery detection. > > One method that might be considered for recursive servers as well as > resolvers, is the ability to specify if a wildcard entry will be accepted > or not, perhaps at any level or just at the 2nd level. Cached records which > are wildcards could be marked as such so that subsequent queries could > specify desire of accepting or not accepting the wildcard entry. A web > browser, for example, which supports its own redirections for NXDOMAIN, > might wish to ignore the wildcard records, as would smtp servers. > > While I believe that net and com should never have wildcards, the ability > to detect, cache, and override wildcards for tld's such as museum when the > application requires it is paramount. I realize that the client software > can perform the queries and detection itself, but in many cases, there > wouldn't be an effecient way to cache the information without the resolver > and recursive cache being aware of the process and performing such > detection would require two queries versus one. > > > -Jack >

4 3

Sven-Haegar Koch: Re: Root Server Operators (Re: What *are* they smoking?)
by Paul Vixie 18 Sep '03

18 Sep '03

forwarding as requested.

1 0