Will P2P applications really never learn to play nicely on the network?
So from an operations perspective, how should P2P protocols be designed?
There appears that the current solution at the moment is for ISP's to
put up barriers to P2P usage (like comcasts spoof'd RSTs), and thus P2P
What has happened? Well, application protocols have evolved to
accommodate NAT weirdness (e.g., SIP NAT discovery), and NATs have
undergone incremental improvements, and almost no end-users care about
NATs. As long as they can use the Google, BitTorrent and Skype, most
moms and dads
We've been pitching the idea to bittorrent tracker authors to include
a BGP feed and prioritize peers that are in the same ASN as the user
himself, but they're having performance problems already so they're
not so keen on adding complexity. If it could be solved better at the
client level
One note here is that even though you can get glue into com/net/org
using this method, there is no IPv6 glue for the root yet, as such even
if you manage to get the IPv6 glue in, it won't accomplish much (except
sending all IPv6 capable resolvers over IPv6 transport :) as all
resolvers will
The only ways into these machines would be if the NAT/PAT device were
misconfigured, another machine on the secure network were compromised, or
another gateway into the secure network was set up. Guess what? All of these
things would defeat a stateful inspection firewall as well.
I
When you can plug your computer in, and automatically (with no
clicking) get an IPv6 address,
Router Advertisements let you automatically configure as many IPv6
addresses as you feel like.
have something tell you where your DNS assist servers,
Microsoft had an old expired draft with
Iljitsch van Beijnum wrote:
Dear NANOGers,
It irks me that today, the effective MTU of the internet is 1500 bytes,
while more and more equipment can handle bigger packets.
What do you guys think about a mechanism that allows hosts and routers
on a subnet to automatically discover the MTU
An observation I would make is that the number of mac addresses per
person at the tech heavy meeting has climbed substantially over 1 (not
to 2 yet) so it's not so much that everyone brings a laptop... it's that
everyone brings a laptop, a pda and a phone, or two laptops. In a year
or two
Good thinking. Where do I sign? Regarding your first point, it's really
surprising that existing P2P applications don't include topology awareness.
After all, the underlying TCP already has mechanisms to perceive the
relative nearness of a network entity - counting hops or round-trip
latency.
This seems like a problem that could be solved in the
style of the CIDR report. Regular weekly reports of
v6 relays and locations as seen from various major ASes.
From my tr website I can see a few 6to4 gateways:
http://tr.meta.net.nz/output/2005-10-17_22:41_192.88.99.1.png
(beware, the
10 matches
Mail list logo
