From training at ripe.net Mon Jan 6 10:40:26 2014 From: training at ripe.net (Training Services) Date: Mon, 06 Jan 2014 10:40:26 +0100 Subject: [ipv6-wg] [training] RIPE NCC Webinars - new dates Message-ID: <52CA7A0A.3040503@ripe.net> Dear colleagues, We are pleased to announce the launch of new dates for our Webinars. The RIPE NCC Webinars are live and take only one hour. You can interact with our trainers without leaving your desk. We focus on the topics and issues most important for LIRs. Register now at https://www.ripe.net/lir-services/training/e-learning/webinars Participation is limited to 20 people, so don't hesitate if you want to take part! If you have questions, please email . We look forward to seeing you online. Kind regards, RIPE NCC Training Services From maildanrl at gmail.com Thu Jan 9 21:18:54 2014 From: maildanrl at gmail.com (Dan Luedtke) Date: Thu, 9 Jan 2014 21:18:54 +0100 Subject: [ipv6-wg] Follow up on RIPE67 IPv6 Only experiment In-Reply-To: <87ppowq1yt.fsf@stepladder-it.com> References: <11CC31A3-BEEA-49A0-8675-EC7437EC90ED@marcoh.net> <87ppowq1yt.fsf@stepladder-it.com> Message-ID: Hi all, On Mon, Dec 16, 2013 at 3:56 PM, Benedikt Stockebrand wrote: > If I may offer one more suggestion, what about a "real" IPv6-only > network without 464XLAT or anything, preferably as yet another SSID? I NAT64/DNS64 works fine (until someone decides to validate DNS records) > This *will* break things, but that way we can see *what* breaks, so we > can figure out what things need to be fixed. >From my experience with NAT64 you only break protocols that are already fundamentally broken :) Best regards, Dan -- Dan Luedtke http://www.danrl.de From dwing at cisco.com Fri Jan 10 10:05:55 2014 From: dwing at cisco.com (Dan Wing) Date: Fri, 10 Jan 2014 01:05:55 -0800 Subject: [ipv6-wg] Follow up on RIPE67 IPv6 Only experiment In-Reply-To: References: <11CC31A3-BEEA-49A0-8675-EC7437EC90ED@marcoh.net> <87ppowq1yt.fsf@stepladder-it.com> Message-ID: <0E4C2295-287D-45E6-98B1-3C625CBC1208@cisco.com> On Jan 9, 2014, at 12:18 PM, Dan Luedtke wrote: > Hi all, > > On Mon, Dec 16, 2013 at 3:56 PM, Benedikt Stockebrand > wrote: >> If I may offer one more suggestion, what about a "real" IPv6-only >> network without 464XLAT or anything, preferably as yet another SSID? I > NAT64/DNS64 works fine (until someone decides to validate DNS records) NAT64 works with host DNSSEC validation, provided that DNSSEC-validating host also does its own DNS64 function. The interaction of NAT64 with host DNSSEC validation is described in RFC6147. -d > >> This *will* break things, but that way we can see *what* breaks, so we >> can figure out what things need to be fixed. >> From my experience with NAT64 you only break protocols that are > already fundamentally broken :) > > > Best regards, > > Dan > > -- > Dan Luedtke > http://www.danrl.de > From bs at stepladder-it.com Fri Jan 10 12:13:00 2014 From: bs at stepladder-it.com (Benedikt Stockebrand) Date: Fri, 10 Jan 2014 11:13:00 +0000 Subject: [ipv6-wg] Follow up on RIPE67 IPv6 Only experiment In-Reply-To: (Dan Luedtke's message of "Thu, 9 Jan 2014 21:18:54 +0100") References: <11CC31A3-BEEA-49A0-8675-EC7437EC90ED@marcoh.net> <87ppowq1yt.fsf@stepladder-it.com> Message-ID: <871u0gf5tv.fsf@stepladder-it.com> Hi Dan and list, Dan Luedtke writes: > On Mon, Dec 16, 2013 at 3:56 PM, Benedikt Stockebrand > wrote: >> If I may offer one more suggestion, what about a "real" IPv6-only >> network without 464XLAT or anything, preferably as yet another SSID? I > NAT64/DNS64 works fine (until someone decides to validate DNS records) Now I assume that there may be some people who are willing to keep NAT64/DNS64 and/or 464XLAT and/or NAT-PT and/or TRT and/or SIIT and/or whatever else they've already set up alive and available all the time, but I know that there are people who intend to get rid of them---and IPv4 in general---and the additional workload they generate as soon as possible. The point of my suggestion is to see how dependent we still are on IPv4 and identify the things we still need to work on. As far as "works fine" is concerned: It adds work to the admins, depending on your enterprises's size it adds extra hardware, it makes troubleshooting more complex and as such it increases cost while lowering reliability/availability. >> This *will* break things, but that way we can see *what* breaks, so we >> can figure out what things need to be fixed. > From my experience with NAT64 you only break protocols that are > already fundamentally broken :) Nonsense. If you add ever more restrictions to what protocols are allowed to do and what not, then all you achieve is that coders will add more and more violations to your restrictions, either because they can't really keep track of your restrictions or because your restrictions break their perfectly valid application requirements. RFC 3439, section 2, has more on this in a general way. Cheers, Benedikt -- Business Grade IPv6 Consulting, Training, Projects Benedikt Stockebrand, Dipl.-Inform. http://www.stepladder-it.com/ From Ondrej.Caletka at cesnet.cz Fri Jan 10 12:39:11 2014 From: Ondrej.Caletka at cesnet.cz (=?UTF-8?B?T25kxZllaiBDYWxldGth?=) Date: Fri, 10 Jan 2014 12:39:11 +0100 Subject: [ipv6-wg] Follow up on RIPE67 IPv6 Only experiment In-Reply-To: <0E4C2295-287D-45E6-98B1-3C625CBC1208@cisco.com> References: <11CC31A3-BEEA-49A0-8675-EC7437EC90ED@marcoh.net> <87ppowq1yt.fsf@stepladder-it.com> <0E4C2295-287D-45E6-98B1-3C625CBC1208@cisco.com> Message-ID: <52CFDBDF.3020207@cesnet.cz> Dne 10.1.2014 10:05, Dan Wing napsal(a): > NAT64 works with host DNSSEC validation, provided that DNSSEC-validating host also does its own DNS64 function. The interaction of NAT64 with host DNSSEC validation is described in RFC6147. And it's worth noting that RFC 7050 finally adds ability for end host to discover whether NAT64 is used in the network and what prefix is used. This is quite handy information for endpoint to do the DNS64 on its own. -- Ond?ej Caletka -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5563 bytes Desc: Elektronicky podpis S/MIME URL: From mir at ripe.net Mon Jan 13 15:32:16 2014 From: mir at ripe.net (Mirjam Kuehne) Date: Mon, 13 Jan 2014 15:32:16 +0100 Subject: [ipv6-wg] New on RIPE Labs: How Many RIPE Atlas Probes Can Resolve IPv6-only Domain Names? In-Reply-To: <52D3F8D3.8020004@ripe.net> References: <52D3F8D3.8020004@ripe.net> Message-ID: <52D3F8F0.5080909@ripe.net> Dear colleagues, Please find a new article on RIPE Labs submitted by St?phane Bortzmeyer: How Many RIPE Atlas Probes Can Resolve IPv6-only Domain Names? https://labs.ripe.net/Members/stephane_bortzmeyer/how-many-ripe-atlas-probes-can-resolve-ipv6-only-domain-names Kind regards, Mirjm Kuehne RIPE NCC From dez at otenet.gr Fri Jan 17 09:57:22 2014 From: dez at otenet.gr (Yannis Nikolopoulos) Date: Fri, 17 Jan 2014 10:57:22 +0200 Subject: [ipv6-wg] RIPE 554 Errata Page In-Reply-To: <51A723BF.5080608@go6.si> References: <51A2595D.4040902@boeddinghaus.de> <03BFA93D-3219-4812-A8A5-893A807488D3@ripe.net> <97EB7536A2B2C549846804BBF3FD47E112FEC5E4@xmb-aln-x02.cisco.com> <87189339-FA01-450F-8C42-56D1326CF631@ecs.soton.ac.uk> <51A5C374.7010907@gmail.com> <51A723BF.5080608@go6.si> Message-ID: <52D8F072.6050107@otenet.gr> On 05/30/2013 01:02 PM, Jan Zorz @ go6.si wrote: > Cheers, Jan > > P.S: Compiling the lists of changes, will post the link when > considerably long enough ;) > hello Jan (and list), if you're still compiling the list, you should add RFC7084 instead of RFC6204 (if you haven't already) cheers, Yannis From sander at steffann.nl Fri Jan 17 14:56:21 2014 From: sander at steffann.nl (Sander Steffann) Date: Fri, 17 Jan 2014 14:56:21 +0100 Subject: [ipv6-wg] RIPE 554 Errata Page In-Reply-To: <52D8F072.6050107@otenet.gr> References: <51A2595D.4040902@boeddinghaus.de> <03BFA93D-3219-4812-A8A5-893A807488D3@ripe.net> <97EB7536A2B2C549846804BBF3FD47E112FEC5E4@xmb-aln-x02.cisco.com> <87189339-FA01-450F-8C42-56D1326CF631@ecs.soton.ac.uk> <51A5C374.7010907@gmail.com> <51A723BF.5080608@go6.si> <52D8F072.6050107@otenet.gr> Message-ID: Hi, > if you're still compiling the list, you should add RFC7084 instead of RFC6204 (if you haven't already) Thank you! All input is welcome :-) Sander From training at ripe.net Mon Jan 20 10:46:53 2014 From: training at ripe.net (Training Services) Date: Mon, 20 Jan 2014 10:46:53 +0100 Subject: [ipv6-wg] [training] RIPE NCC Webinars - new dates Message-ID: <52DCF08D.2030903@ripe.net> Dear colleagues, We are pleased to announce the launch of new dates for our Webinars. The RIPE NCC Webinars are live and take only one hour. You can interact with our trainers without leaving your desk. We focus on the topics and issues most important for LIRs. Register now at https://www.ripe.net/lir-services/training/e-learning/webinars Participation is limited to 20 people, so don't hesitate if you want to take part! If you have questions, please email . We look forward to seeing you online. Kind regards, RIPE NCC Training Services From marcoh at marcoh.net Thu Jan 23 19:04:46 2014 From: marcoh at marcoh.net (Marco Hogewoning) Date: Thu, 23 Jan 2014 19:04:46 +0100 Subject: [ipv6-wg] Fwd: RACI @ RIPE 68 - Opportunity for Students and Researchers References: <52E13CCB.8020908@ripe.net> Message-ID: If you are or know somebody doing research that is somewhat Internet related (doesn?t have to be IPv6 :). RIPE NCC has again put a call out for applicants to the RACI programme. And I am sure that I can speak for my fellow chair that we are happy to consider any IPv6 related material for inclusion in our work group. MarcoH (in his role as co-chair of this working group) > Dear colleagues, > > The RIPE Academic Cooperation Initiative (RACI) is providing a number of > students and researchers the opportunity to participate at RIPE 68 in > Warsaw from 12-16 May. We are offering packages that include meeting > registration and paid travel and accommodation, and we are currently > seeking applications from across the RIPE NCC service region. > > We would like to ask for your assistance to raise awareness of the RACI > program. Many in the RIPE community have strong connections with > academic institutions, and we are keen to make those institutions and > their students aware of this great opportunity. > > RACI gives students and researchers the opportunity to present their > work in front of some the leading technical figures in the Internet > world, receive feedback on their research from experts and have their > work published on the RIPE Labs website for community feedback. The RACI > program also benefits the RIPE community by introducing newer members to > the community who can give interesting presentations at RIPE Meetings > that might not otherwise be seen. > > The initiative is coordinated with the RIPE Programme Committee to allow > the RACI participants to present their research, either during > plenary/working group sessions, or in lightning talks at other > designated sessions. > > Students and researchers may wish to present on any topic relevant to > the RIPE community, including (but not limited to): > > - Network measurement and analysis > - IPv6 deployment > - BGP routing > - Network security > - Internet governance > > Students and researchers who are interested in RACI sponsorship can fill > out the application form on the RIPE 68 webpages: > https://ripe68.ripe.net/programme/raci/application/ > > All applications must be received by Friday, 25 April 2014. Applicants > will be informed about the status of their application by Friday, 2 May > 2014. Any applications received after 25 April 2014 will be considered > for RACI at RIPE 69, to be held in London from 3-7 November 2014. > > More information on RACI is available at: > https://ripe68.ripe.net/programme/raci/ > > Best regards, > > The RACI Coordination Team > RIPE NCC