When will audio recordings of sessions be available?
If one misses hearing a session live, will it be possible to listen to the recording this week, or will we have to wait a week or two? - Philip ___ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
RE: review of draft-zorn-radius-pkmv1-04.txt
> 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, regardless of whether the attributes were complex or simple. That rationale applies not just to "RADIUS security" but also to authentication mechanisms, many of which were previously implemented with complex attributes (e.g. CHAP). So I'm not clear that we're talking about a "loophole" here. > encapsulation using RFC 2548 MPPE-Key attributes... I was unclear about how this is supposed to work. Is the idea to apply the MPPE-Key encryption mechanism to the attribute specified in the draft, or is the idea to actually use the MPPE-Key attributes themselves? If the former, more detail should be provided. If the latter, is it necessary to define two attribute formats or would it be simpler to go with one? If the RFC 2548 MPPE-Key attributes are used, is the format the same as that defined in RFC 2548 (just a wrapped key) or is the wrapping applied to a complex attribute? > a four octet Integer should be used instead of a two octet data type > (which doesn't exist in RADIUS) As I recall, the security exemption didn't apply to creation of new RADIUS data types, correct? ___ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
Re: Actual IPv6 deployment observed
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 a recent IPv6-capable client >> are in those numbers. I had to null-route the PB IPv6 address to get >> my old client to work again over IPv4... > > So considerably more than 1% of random filesharing users have IPv6 > already? I assume that also means >1% of random DSL connections have > IPv6 already. No, it is not "Native IPv6 over DSL" or any other form unfortunately. ou have to start thanking Microsoft for pushing 6to4 and especially Teredo, having it automatically on new platforms and having clients like uTorrent auto-enable it on install for those that don't. For instance read a bit here: http://mailman.nanog.org/pipermail/nanog/2008-August/003051.html Greets, Jeroen signature.asc Description: OpenPGP digital signature ___ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
Re: Actual IPv6 deployment observed
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 client are in those numbers. I had to null-route the PB IPv6 address to get my old client to work again over IPv4... So considerably more than 1% of random filesharing users have IPv6 already? I assume that also means >1% of random DSL connections have IPv6 already. Arnt ___ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
Re: Actual IPv6 deployment observed
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 numbers are about 1%, and about 9% of torrents contain one or more IPv6-capable peers. Ooh aah. 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 client are in those numbers. I had to null-route the PB IPv6 address to get my old client to work again over IPv4... Another example of how NOT to migrate from old stuff to new stuff. ___ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
Actual IPv6 deployment observed
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 or more IPv6-capable peers. Ooh aah. Arnt ___ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
Links to audio streams
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 http://feed.verilan.com/ietf/stream01.m3u Kongresshall C http://feed.verilan.com/ietf/stream02.m3u Cabaret http://feed.verilan.com/ietf/stream03.m3u 300 http://feed.verilan.com/ietf/stream04.m3u 307 http://feed.verilan.com/ietf/stream05.m3u Small Stage http://feed.verilan.com/ietf/stream06.m3u Large Stage http://feed.verilan.com/ietf/stream07.m3u Nick Kukich Network Engineering nkuk...@verilan.com www.verilan.com VeriLAN Event Services, Inc. 215 SE Morrison Street Suite 7000 Portland, OR 97214 Tel: 503 907-1427 Fax: 503 224-8833 Cell: 503 290-8676 This e-mail contains proprietary information and may be confidential. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this message is strictly prohibited. If you received this message in error, please delete it immediately. ___ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
Re: [IAB] Status of DNSSEC signing of .arpa?
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 yet signed .arpa nor related zones. Have they provided the IAB with a plan? Not yet. --Olaf Kolkman PGP.sig Description: This is a digitally signed message part ___ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
