- eix-wg - mailman.ripe.net

ISC installed an f.root-servers.net instance in Johannesburg
by Carsten Schiefner 01 Oct '03

01 Oct '03

All, only remotely related (not in the RIPE region) - however, may still be of some interest as we had three presentation on this very topic during RIPE 46, furthermore the box is installed at JINX, the Johannesburg Internet exchange. http://www.itweb.co.za/sections/internet/2003/0309260853.asp Regrads, Carsten

2 1

Next phase in deploying anycast instances of k.root-servers.net
by Andrei Robachevsky 22 Sep '03

22 Sep '03

Dear colleague, After discussions at the last RIPE Meeting, we would like to clarify our current thinking about adding further anycast instances to k.root-servers.net. This message sets out the direction and further details the requirements for hosting such an instance and calls for expressions of interest from the Internet community to support this activity. I look forward to your support. Best regards, Andrei Robachevsky CTO, RIPE NCC General requirements and guidelines for expressions of interest for hosting a mirror instance of k.root-servers.net ============================================================== Introduction ------------ The RIPE NCC operates k.root-servers.net, one of the servers used as a name server for the DNS root zone. In order to further improve the distribution of the service in various Internet regions and its resilience against DDoS attacks the RIPE NCC is deploying mirror instances of the server worldwide as described in the ripe document "Distributing K-Root Service by Anycast Routing of 193.0.14.129" (RIPE 268). The first phase of this project included moving the cold standby instance of the server to service using anycast routing. This phase was completed in July 2003 and k.root-servers.net is currently deployed in two locations (LINX, London and AMS-IX, Amsterdam). The next phase will be mostly focused on the deployment of nodes with limited reachability in the RIPE NCC service region. The main motivation for this phase is: - Improving access to k.root-servers.net for a significant ISP community. - Isolating impact of an "external" DDoS attack. - Localising impact of a "local" DDoS attack. This document sets the direction and further details the requirements for hosting an instance of the k.root-servers.net server so that interested organisations may understand the general intentions and requirements of this phase of the project. Organisations wishing to express their interest in supporting this important activity may do so by following the guidelines below. Physical Sites -------------- Suitable sites for the location of mirror instances of the k.root-servers.net server will in most cases include an Internet exchange (IX) that offers a very high standard of infrastructure and Internet connectivity. The members of the IX should represent a significant ISP community in the region. In terms of physical infrastructure and services, a hosting site must satisfy the general requirements for root server locations, which are described in section 3.1 of RFC2870. Server Hardware --------------- All hardware for the instance of k.root-servers.net will be supplied at the host's expense. In most cases a typical configuration will be assembled by the RIPE NCC and shipped to the hosting site. The hardware will remain the property of the host, but will be operated solely by the RIPE NCC. The host will be asked to provide onsite physical support. However there is no requirement for the host to perform maintenance on the systems themselves, and administrative access will not be available. Connectivity and reachability ----------------------------- Though global reachability is not required for the instance of the k.root-servers.net server, it is critical that access to the server is provided in an open and non-discriminative manner to all members of the IX. However, it is important that global transit is co-ordinated with the RIPE NCC. Requirements for reachability are different for the management network of k.root-servers.net that is used by the RIPE NCC to perform system administration. It is required that connectivity of the management network is global and reliable. Expressions of Interest ----------------------- The RIPE NCC invites expressions of interest from organisations such as Internet Exchanges or other organisations that represent a significant ISP community in the region. Expressions of Interest should include details of the support which is being offered, such as hosting and connectivity. Please provide as much detail as possible, including physical infrastructure details, upstream and peer network connectivity details, and bandwidth availability. Please refer specifically to the provisions of RFC2870 in your response. Please send expressions of interest to: k-anycast(a)ripe.net If any further information is required, please also use this address.

1 0

RIPE 46 Presentations
by Mike Hughes 04 Sep '03

04 Sep '03

Hi all, Most presentations from the RIPE 46 EIX working group are now available online at http://www.ripe.net/ripe/meetings/ripe-46/presentations/ If your presentation was not run from the RIPE supplied laptop, or does not appear on the above webpage, please email it to webmaster(a)ripe.net. Thanks, Mike -- Mike Hughes Chief Technical Officer London Internet Exchange mike(a)linx.net http://www.linx.net/ "Only one thing in life is certain: init is Process #1"

1 0

K-anycast future deployment plans
by Andrei Robachevsky 28 Aug '03

28 Aug '03

Dear Colleagues, As you may know there will be two presentations related to K-anycast project at the RIPE meeting: a short one at the eix-wg outlining RIPE NCC's plans for future anycast deployment and hosting requirements, and one at the dn*-wg discussing the current technical setup of K and its operation. We also though it would be useful to have a separate meeting inviting those who has interest in hosting an instance of K, to discuss NCC's deployment plans, proposed setup and requirements in more detail and collect your feedback. We booked the Dam Room (first floor) for the meeting for Wednesday, 3.09, 17.30-18.30. Regards, Andrei Robachevsky CTO, RIPE NCC

1 0

EIX WG - Agenda Call for RIPE 46
by Fearghas McKay 12 Aug '03

12 Aug '03

Greetings The format is changing slightly - we are going to have two sessions one with IXP update presentations similar to the Euro-IX ones just focussing on growth, new technology, services etc aimed at ISPs primarily. To speed the updates we want to have a single laptop with everyone's presentation in advance so we can rattle through. Time limit will be circa 3 mins for previous presenters and 5 for new presentations. If you would like to present please send a note to myself & Mike Hughes <mike(a)linx.net> by August 27th. We will try to take late comers but there will only be the one session. The update should focus on background, growth and recent developments but should not include case studies in upgrades etc, they should be in the second session. Please send copies of your presentation to Mike and myself by September 1st so we can get them organised in time. The second session is where the " we did this and it was not fun " or "here are some interesting ideas", etc. items can go rather than being in the update presentation. The second session has a few preliminary items and more will be welcome. Again if possible we would like the presentations by September 1st so we can have a single laptop. Thanks Fearghas EIX-WG RIPE 46 Wednesday 3 September 2003 St Johns II Krasnapolsky Hotel Session One 11:00-12:30 0 Scribe Agenda Bashing 1 IXP presentations Lunch Break Session Two 14:00-15:30 2 Presentions Euro-IX update Regulatory Implications of Recent EU Directives for IXP Operators - Keith Mitchell Hosting a .root server - 3 short presentations from the root operators in the RIPE region explaining what they are looking for in a location - NetNOD, ISC & RIPE-NCC An overview of the PCH IXP database - Bill Woodcock 3 RIPE Address Policy & NCC-Sevices issues 4 AOCB

1 0

Regarding the IPv6 Request Form for Internet Exchange Points
by Aleksi Suhonen 11 Aug '03

11 Aug '03

Hello, The robot at hostmaster@ seems to mistake the IPv6 form for IXPs as an IPv4 form? When you others on this list applied for your address space, did you just send it directly as NO AUTO? And additionally, as there is no published IPv4 procedure for exchanges, how have you handled this situation? (Any other words of experience that might help me? ;-) -- Aleksi Suhonen / +358 45 6702048 TREX Tampere Region Exchange Oy www.trextampereregionexchange.fi

2 2