[...] the inability of DNS to support multi-lingual characters requires fixing, and that right now ONLY RealNames fixes this natively in the browser that is on 90% + desktops.
The Internet Corporation for Assigned Names and Numbers (ICANN) has set up the Internationalized Domain Names (IDN) committee to discuss making domain names available in character sets other than ASCII.
I read a paper about the risk of homeomorphic attacks but I can't get my grubby little hands on it anymore:(
Your "ATA/100" motherboard does not support 48-bit addresing.
Two weeks ago, ASUS released a new BIOS for the A7V133-C motherboard. ASUS claims that version 1009 adds support for 48-bit HDD. Would that mean that the motherboard now supports HDD larger than 120 GB?
Actually, full-duplex means a point-to-point link with separate receive and transmit paths. Hence, no collision can occur.
If you had gig hubs, you would be limited to maybe 10 meter cables or something?
Half-duplex Gigabit Ethernet was designed for a 200-meter network diameter. That's why the designers came up with carrier extension. If a frame is smaller than 512 bytes, it is extended to meet the 512-bytes minimum.
By default the MTU size on a gigabit card is way too low.
Hmmm... The MTU for Ethernet is 1500 bytes. AFAIK, that's what the 802.3 standard says. Perhaps you're talking about Jumbo Frames? Are they supported by every vendor?
Currently, all Gigabit Ethernet equipment is based on the full-duplex mode of operation. To date, none of the vendors have plans to develop equipment based on half-duplex Gigabit Ethernet operation.
Which would explain why there are no Gigabit Ethernet hubs available (hubs aka repeaters are half-duplex devices). Carrier extension and frame bursting are not needed in full-duplex mode, which would make the design of full-duplex devices simpler, I guess.
On a side note, in the article, they used Ethernet Jumbo Frames which were not part of the official IEEE standard as of the writing of the book.
Face it, processors are faster than telecommunications.
The architects of IPv6 disagree. They did away with fragmentation inside routers and made the header size constant to shave a few milliseconds off every packet. With the advent of Tbps optical links and optical routing, processors are about to bite the dust.
But just passing mention of DOS attacks - these are boring to academics because they are easy to do and impossible to counter so there's no research to do and no papers to write.
You should take a look at Peter Reiher's work (UCLA). Namely a project on detecting DDoS attacks by observing traffic at routers near the source of the attack (sponsored by DARPA) and another project allowing routers to filter IP packets with spoofed source addresses (sponsored by the NSF).
I'd say at the [high] bitrates I encode at it's as good if not better than MP3
Bitrates are irrelevant. Graham Mitchell has written a very nice introduction to compressed audio with Vorbis. You'll want to read the sections entitled "A Bit On Bitrates", "CBR? VBR? ABR?" and "Just Say No To Bitrate".
[...] for a program that #DEFINED a bunch of english words as chunks of C that did the same thing the english words did, and then wrote a short *compilable* program in totally readable pseudocode...
The normal PCI bus can carry 133 MB/s (1066 Mb/s) but only during bursts.
I think we can agree that "consumer-grade" PCI is running out of steam, even on personal computers. However, there are several contenders waiting at the gate. HyperTransport, 3GIO, RapidIO, PCI-X, InfiniBand. One of them is bound to show up eventually in high-end personal computers. I think I can keep on drooling:)
802.3ae, as the IEEE lovingly calls it, is backed by the 10GEA (10 Gbps Ethernet Alliance). The founding members of the 10GEA are small companies you might have heard of such as 3Com, Cisco, Intel, Nortel or Sun.
As another cost-cutting measure, Citylink uses a generic computer running Debian Linux and SMTP management software [...]
Hmmm... Shouldn't that be SNMP as in Simple Network Management Protocol?
Straight from RFC 2962:
There are currently three versions of SNMP. SNMP version 1 (SNMPv1) protocol is defined in STD 15, RFC 1157. The SNMP version 2c (SNMPv2c) protocol is defined in RFC 1901, RFC 1905 and RFC 1906. Finally, the SNMP version 3 (SNMPv3) protocol is defined in RFC 1905, 1906, RFC 2572 and RFC 2574. See RFC 2570 for a more detailed overview over the SNMP standards.
So people, instead of JHD (Just Hit Delete), please try to find the time to figure out where the spam was sent from and where the spamvertized sites are hosted and report the spammers or things may become very ugly...
It's not always easy to extract useful information from a message's header, especially when the spammers intentionally go out of their way to obfuscate it.
Spamcop automates the process with fairly good results.
ls will print several files per line. Therefore, it is pointless to count the lines. You would want "ls/usr/bin | wc -w" or "ls -l/usr/bin | wc -l" (only the first would yield the correct result).
Apparently he is using a bot to repeatedly check for newly expiring domains, hoping to capitalize on the traffic from people's old bookmarks/search engine listings. I'm calling this "expire-squatting".
ICANNWatch had a story on this new form of semantics attack. They call it "The XXX-piring Namespace".
Slashdot Mirror
I read a paper about the risk of homeomorphic attacks but I can't get my grubby little hands on it anymore :(
Currently, all Gigabit Ethernet equipment is based on the full-duplex mode of operation. To date, none of the vendors have plans to develop equipment based on half-duplex Gigabit Ethernet operation.
Which would explain why there are no Gigabit Ethernet hubs available (hubs aka repeaters are half-duplex devices). Carrier extension and frame bursting are not needed in full-duplex mode, which would make the design of full-duplex devices simpler, I guess.
On a side note, in the article, they used Ethernet Jumbo Frames which were not part of the official IEEE standard as of the writing of the book.
Intel bought the complete Alpha technology from Compaq -- including engineers, software developers and infrastructure managers (June 25th, 2001).
I enjoyed two articles on ExtremeTech: High-Performance Buses and Interconnects by Leon Erlanger (dated November 8, 2001) and The Interconnect Conundrum by Nick Stam (dated January 28, 2002).
802.3ae, as the IEEE lovingly calls it, is backed by the 10GEA (10 Gbps Ethernet Alliance). The founding members of the 10GEA are small companies you might have heard of such as 3Com, Cisco, Intel, Nortel or Sun.
Straight from RFC 2962:
There are currently three versions of SNMP. SNMP version 1 (SNMPv1) protocol is defined in STD 15, RFC 1157. The SNMP version 2c (SNMPv2c) protocol is defined in RFC 1901, RFC 1905 and RFC 1906. Finally, the SNMP version 3 (SNMPv3) protocol is defined in RFC 1905, 1906, RFC 2572 and RFC 2574. See RFC 2570 for a more detailed overview over the SNMP standards.
Spamcop automates the process with fairly good results.
In their "completely rewritten" TCP stack for NT5, Microsoft uses 0x402E. Interestingly, that is exactly the number used by OpenBSD and FreeBSD.
$ man ls
-1 Force output to be one entry per line. This is the default when output is not to a terminal.
ls will print several files per line. Therefore, it is pointless to count the lines. You would want "ls
If you dig PR, then head to 802.11 Planet. You'll get all the corporate lubing you could ever hope for.
802.11a is not new, it's been around since 1999. Check the IEEE website. They have the document available for free download.