Domain: techtarget.com
Stories and comments across the archive that link to techtarget.com.
Comments · 663
-
Karma-Whoring Definition
peering
Peering is the arrangement of traffic exchange between Internet service providers (ISPs). Larger ISPs with their own backbone networks agree to allow traffic from other large ISPs in exchange for traffic on their backbones. They also exchange traffic with smaller ISPs so that they can reach regional end points. Essentially, this is how a number of individual network owners put the Internet together. To do this, network owners and access providers, the ISPs, work out agreements that describe the terms and conditions to which both are subject. Bilateral peering is an agreement between two parties. Multilateral peering is an agreement between more than two parties.
Peering requires the exchange and updating of router information between the peered ISPs, typically using the Border Gateway Protocol (Border Gateway Protocol). Peering parties interconnect at network focal points such as the network access points (network access point) in the United States and at regional switching points. Initially, peering arrangements did not include an exchange of money. More recently, however, some larger ISPs have charged smaller ISPs for peering. Each major ISP generally develops a peering policy that states the terms and conditions under which it will peer with other networks for various types of traffic.
Private peering is peering between parties that are bypassing part of the public backbone network through which most Internet traffic passes. In a regional area, some ISPs exchange local peering arrangements instead of or in addition to peering with a backbone ISP. In some cases, peering charges include transit charges, or the actual line access charge to the larger network. Properly speaking, peering is simply the agreement to interconnect and exchange routing information. -
Re:Will someone explain to me...
Non-karma-whoring explanation: http://whatis.techtarget.com/definition/0,289893,
s id9_gci212768,00.html -
The more things change...Sounds like the IP analog for radio Frequency Hopping Spread Spectrum (FHSS). Which, by the way, was invented and patented as a radio security technique during WWII by movie star Hedy Lamarr and her pianist. A movie star geek girl? I was definitely born in the wrong generation...
--
-
It is a standard...
Before we keep flaming sony for not adhereing to a standard (which is true in a lot of cases), the new drive does adhere to the proposed (and I believe certified) Purple Book specification. Now if wether or not someone else will adopt this, I don't know...
-
Microcomputer
"It's not a PC, but rather a microcomputer"
Silly me, I always thought the PC was a microcomputer.
-- -
Re:Question
Many links on XML here.
-
Re:One thing you can doI see three problems here.
One, it's a pain in the ass to go to the bank every time you want a fresh number.
Two, there are only so many numbers available in the 16-digit LUHN-verified pool currently in existence. There are even further restrictions:
- Based on the first digit:
- 2=Vendor
- 3=Amex [Discover too?]
- 4=Visa
- 5=MC
- 6=Store/Other [Discover too?]
- Based on the first 4 or 6 digits, ie:
- 4510=Royal Bank Visa
- 4512=Royal Bank Gold/Platinum Visa
- 4512 12xx=Royal Bank Gold/Platinum Visa from Central Card Center area
- etc...
- 4480=Security First Network Bank
Three, it's more trouble than it's worth, considering you are only legally responsible for the first $50 of unauthorized charges to your card, and most banks won't even hold you to that. I've had merchants double-bill me (and once some totally unauthorized charge from Denmark showed up), and Royal Bank instantly credited my account for the full amount and mailed me a form to sign and return stating that the charge in question was unauthorized. In every instance, the whole process took less than 5 minutes of my time and was totally painless.
Essentially, the banks themselves are the only ones left holding the bag when fraudulent use occurs. As a result, they either hold the money back from the merchant's future payments or write it off. Joe Consumer (you and I) aren't liable for it, and generally aren't affected by it. Worst case, if the abuse on your particular card keeps up, they might cancel your card and send you a new one with a different number. Big deal.
-- - Based on the first digit:
-
Re:FUD
And Linus saying so himself.
Torvalds on Linux (Q&A): They aren't laughing now -
Re:Help me out
JMS is the Java Message Service. ETX is a product from TIBCO; there's also a TIBCO product called Rendezvous, and I presume that's what the original poster meant by "RV". "UDB" is "Universal Database", used in connection with IBM's DB2 database product in its various incarnations.
-
RBL Usage info - READ THIS
There are three ways that RBL may be used, listed at this address:
http://mail-abuse.org/rbl/usage.htmlONLY ONE OF THE USAGE METHODS results in blackholing all ip traffic, that is the Subscription via BGP. This option is only available to larger networks with routers which have an ASN (see whatis.com if you don't know what an ASN is.)
I know of very very few networks which use RBL in this manner. There must be a few, but it seems like a pain in the ass, and there are negative effects of doing it, as indicated on the RBL description of the service.
Anyone choosing to implement such an esoteric blackholing system for all ip traffic from RBL-listed hosts is likely FULLY AWARE that they will be dropping some hosts, and must consider that an acceptable risk. If you are a client of such an organization, and don't buy into that, then leave. My guess would be that most that have successful implementations of BGP RBL subscription had buy-in from their clients before they set it up.
My guess is that 95% or more of RBL subscribers use the "Direct usage via DNS lookup by mailserver" method of applying RBL blocking. This method has ZERO IMPACT on http, ftp, dns, ICMP, or any other type of traffic other than SMTP.
This Slashdot article was written by someone who does not understand the nature of the Internet and the RBL on a detailed level, and who is obviously dipping into conspiracy theories a bit... his little diatribe on above.net sounds like the manifesto of a lunatic. To the author: Get over it, sir. You don't understand the technology, and you don't understand the decisions made by ISPs who implement the RBL. I wish you well in your career, but this isn't going to be the ground-breaking story you thought it was. Feel free to write me if you'd like to speak to me further.
Sincerely,
~Acheron -
A home network is not a VPN!
The Comcast subscriber agreement already banned connecting a home LAN to the cable modem. A VPN allows your home system to appear to be part of private WAN across the public Internet. In reality, this change doesn't take anything away, as connecting to a non-Comcast WAN was already prohibited, but this makes it an explicit statement for people like Roblimbo who don't know what makes a LAN, a WAN, and a VPN different.
-
A home network is not a VPN!
The Comcast subscriber agreement already banned connecting a home LAN to the cable modem. A VPN allows your home system to appear to be part of private WAN across the public Internet. In reality, this change doesn't take anything away, as connecting to a non-Comcast WAN was already prohibited, but this makes it an explicit statement for people like Roblimbo who don't know what makes a LAN, a WAN, and a VPN different.
-
A home network is not a VPN!
The Comcast subscriber agreement already banned connecting a home LAN to the cable modem. A VPN allows your home system to appear to be part of private WAN across the public Internet. In reality, this change doesn't take anything away, as connecting to a non-Comcast WAN was already prohibited, but this makes it an explicit statement for people like Roblimbo who don't know what makes a LAN, a WAN, and a VPN different.