4 ms·
Below are the purposes in 2.7(b)(ii). Note that the prior agreement already included purposes 1-3, but 4-6 are new. > (1) to comply with specifications adopted
by lolinder 4y ago
Below are the purposes in 2.7(b)(ii). Note that the prior agreement already included purposes 1-3, but 4-6 are new.
> (1) to comply with specifications adopted by any industry group generally recognized as authoritative
with respect to the Internet (e.g., RFCs),
> (2) to correct mistakes made by Verisign or any Registrar in connection with a domain name registration, or
> (3) for the non-payment of fees to Verisign; and,
> (4) to protect against imminent and substantial threats to the security and
stability of the Registry TLD, System, Verisign’s nameserver operations or the internet,
> (5) to ensure compliance with applicable law, government rules or regulations, or pursuant to any legal order or subpoena of any government, administrative or governmental authority, or court of competent jurisdiction, and/or
> (6) to stop or prevent any violations of any terms and conditions of this Agreement, the Operational Requirements, or pursuant to Verisign’s Registry Agreement with ICANN;
- derefr 4y ago> (1) to comply with specifications adopted by any industry group generally recognized as authoritative with respect to the Internet (e.g., RFCs), This clause is probably the original motivation for this subsection (with 4, 5, and 6 being "obvious" corollaries of it): the .net TLD is the (de-facto?) place where Autonomous Systems expect to be able to register conventionally-named zones (format AS\d+\.NET), under which they then often register DNS names for things like backbone Internet switches. Insofar as these ASes might be binding control-plane components to network middleboxes through these DNS names (unlikely, given the layer of the stack they operate on, but you never know), a takeover of their AS\d+\.NET domain-name would enable a wide-ranging attack on Internet infrastructure. Additionally — though much less likely — you might be able to do some nefarious things just by squatting on an AS\d+\.NET domain name. If some engineer at the NOC is new there, and worked for other AS NOCs who did use AS\d+\.NET domain names to home equipment, but their new job doesn't, but they don't know that yet, they might misconfigure a system in a way that'd be innocuous if the domain was unregistered, but very bad if it was registered to an attacker.
- yrro 4y agoI wonder why on earth this wasn't done properly by reserving, say, as.arpa. or at least using your AS number beneath a (properly registered) asn.net?
- derefr 4y agoWhat you're imagining the function of the hypothetical "asn.net" to be, was just the intended function of the "net" TLD as a whole: it was a namespace for registering computer networks under, to give those networks' devices authoritative FQDNs in PTR records, and to give services like WHOIS something to point to to talk about "the operator of network X." This intention included distinct Autonomous Systems, yes; but also ISP networks (which usually exist across many ASes to do their work). Even today, if you do a PTR lookup on your own residential IP address, it probably resolves to a .net-suffixed FQDN. I'm not sure when exactly Verisign (registrar operator of the .net TLD for its entire lifetime so far) went off the rails and began allowing usages outside the scope of "the management of computer networks." Almost certainly wasn't until a few years after the birth of the web (when everything having a marketable domain name became hip.) .net was definitely viewed as a "special" TLD, with special registration requirements, for a good long while — up through to at least the '90s, and possibly into the early '00s. Honestly, I think it might just be a scalability-of-verification issue. Verisign might be able to check that every registrant in the US is a network operator (as was effectively all they had to do in the '80s); but every registrant in the entire world? A bit much to ask. Which leads me to my current belief about why the network rules of .net as a TLD are currently the way they are: it's the least-work option for Verisign to keep the TLD going for its intended purpose. Rather than needing to individually verify every zone as a network, per the current rules, Verisign only needs to step in if a problem arises, or if there's a dispute between usages. When such a thing happens, Verisign then does the "verification as being used for the operation of a computer network" step it theoretically should have been doing anyway; and if the domain fails the verification, Verisign takes it away. --- That's for the DNS homing part. What about the "having an abuse website to complain to" part? Well, in practice, AS network operators just don't care all that much about Internet principles of self-hosting, federation, public goods, etc. where their human-readable information is concerned. Because of this, most ASes who own AS\d+\.NET zones don't actually maintain websites on them; and in fact don't maintain public websites anywhere. Instead — just like individuals hooked on Facebook — they rely on updating their human-readable metadata in public databases owned by private companies. For every website like http://as9009.net/ http://as9009.net/, there are ten ASes that would just tell you to go look at https://www.peeringdb.com/asn/9009 https://www.peeringdb.com/asn/9009.
- yrro 4y agoHmm these don't seem too nefarious to me... 4) probably don't need to worry about this unless you're using a .net domain to control your botnet 5) is this a practical change? If a court or government told them to take a domain down before they would have done so anyway right? 6) as a customer, it's not good idea to violate your contract with a service provider anyway right?