Hi Hannes,
As you know EAP-pwd was presented to EMU and the ADs ruled that
it was out of scope. Since the ADs are the same, and the EMU charter
is the same then EAP-pwd must still be out of scope for EMU. So that
course is not available. What Bernard says makes a lot of sense.
Unfortunately,
On 26 jul 2009, at 11:10, Samuel Weiler wrote:
Earlier this month the IAB mailed IANA with a request to provide us
plans:
http://www.iab.org/documents/correspondence/2009-06-02-Roseman-Signing-by-IANA-of-ARPA.html
Thank you again for following up with IANA.
It looks like IANA has not
Hello all,
The links to the audio streams aren't currently on the ietf.org page.
We apologize and are working to correct this.
In the meantime, here is a list of direct links to the audio streams.
Kongresshall A http://feed.verilan.com/ietf/stream08.m3u
Kongresshall B
I quote from thepiratebay.org home page:
IPv4 21.613.113 peers (10.992.697 seeders + 10.620.416 leechers) in
1.969.865 torrents on tracker.
IPv6 210.410 peers (115.584 seeders + 94.826 leechers) in 174.895
torrents on tracker.
Most numbers are about 1%, and about 9% of torrents contain one
On 26 jul 2009, at 12:45, Arnt Gulbrandsen wrote:
I quote from thepiratebay.org home page:
IPv4 21.613.113 peers (10.992.697 seeders + 10.620.416 leechers) in
1.969.865 torrents on tracker.
IPv6 210.410 peers (115.584 seeders + 94.826 leechers) in 174.895
torrents on tracker.
Most
Iljitsch van Beijnum writes:
You do have to understand that IPv6 support was available in
BitTorrent clients for a long time, but then the Pirate Bay deployed
trackers (servers) that were incompatible with the existing clients,
so only people who both have IPv6 and a recent IPv6-capable
Arnt Gulbrandsen wrote:
Iljitsch van Beijnum writes:
You do have to understand that IPv6 support was available in
BitTorrent clients for a long time, but then the Pirate Bay deployed
trackers (servers) that were incompatible with the existing clients,
so only people who both have IPv6 and
I believe the intent was related to RADIUS security. The guidelines
document could be updated to address this.
The rationale behind the original exemption was that security required
changes on both the RADIUS client and server. Therefore the RADIUS
server would need a code change anyway,
