RIPE 36

1. Scribe: Henk Uijterwaal
2. Agenda: no changes to the proposed agenda
3. EIX OPS lists
The list is now operational, subscription by invitation only, contact FM to
get subscribed, one can be subscribed after having presented at least once
at an EIX meeting.
4. IX Report
* SFINX1/Frank Simon.
* SFINX1: Public exchange point, not for profit. Service: managed service
(Renater configures) or hosted service (DIY). 52 ISP's, 46 on hosted
service.
* SFINX2: 3 km from SFINX1 with Giga-ethernet between the two sites,
connection operational since yesterday evening. Bigger switches than at S1.
Only hosted service at S2.
New services at S2: giga-ethernet, route server, NTP, advanced statistics,
(sparse mode) multicast (perhaps as an additionally billed service),
specific peering via VLAN. IPv6 is foreseen at a later stage. It is
expected that bigger ISP's will move from S1 to S2.
* Questions from the floor:
* Policy on private interconnects? Answer: will not be allowed.
* Any additional services? Answer: can be discussed.
* Policy for joining? Answer: anybody can join, it is not Renater's task to
judge if an ISP should join or not. The owner of the building has agreed
that they will not host a second IX in the same building
* No Multicast or IPv6, do you prevent people from doing this? Answer: No,
but you have to set this up yourself.
* Any more locations in the future? Answer: yes, we are thinking about
SFINX3, foreseen for September
* Power in the racks? Answer: 220v or 48v in the rack, UPS is available as
a service.
* LINX/Nic Lewis
* Background: UK National IX, neutral organization, aim to keep UK traffic
in the UK (or EU traffic in the EU). Not a co-lo provider.
* Membership now 105 members (95 at RIPE36), 49 from UK,
* Gigabit ethernet: Slow take-up, got better. Now 16 members with 26 ports.
Adding 3Š4 more each month
* Switches:
* Packet-Engine PowerRail. No new Power-Rail machines foreseen as Alcatel
does not do any more development on them.
* Extreme "Black diamond" first one to be installed in the next
* Foundry BigIron 8000, under test. High port density, only the realistic
alternative with fully non-blocking architecture. Very responsive to
support questions.
* Stats: www2.linx.net/stats. Current peak is 2.3 Gb/s. 1.5 on average
* New sites: funded by co-lo providers, open "bidding" process resulted
into 4 interested sites. Interconnected with a dark-fiber ring. Will put an
Extreme and Foundry switch at each site. Site3: Redbus interhouse (now),
Site 4: Telehouse (east), June. Sites 5-7 IX, Interxion, Guardian in
June/July. (Slightly delayed for all kinds of reasons). Writing a document
about expanding to new sites, and publish FYI for other IX's
* Additional stuff: pilot multicast exchange. New stats with RRDtool. 3
Cesium NTP clocks as stratum 1 servers.
* AMS-IX/Niels den Otter
* 2 sites, Foundry switches, 2 Gb/s between them. Connections at 10M, 100M, 1G
* Traffic volume: now 1.6 Gb peak.
* 99 ISP's connected, most Dutch ISP's, more and more international ones,
18 new members since RIPE36
* Expansion sites: request from ISP's, will put out request for proposals
in 1..2 months
* VIX/Christian Panigl
* Grown from 10 members in 1997 to 58 members. Peaks 200Š300 Mb/s
* No route server. Considering to do public statistics.
* Office hour access only, outside hours on best-effort basis only
* No Y2K problems.
* Requirements for ISP joining the VIX: should be LIR, should have ASN,
should have international connectivity independent of existing members
(soft requirement), have prefixes registered in RIPE-DB
* Private interconnects are allowed
* Will stop with newsfeed service, unless the members will organize
something themselves
* Hamburg IX. V.Jurgens
Most traffic in Germany so-far goes Hamburg -> Frankfurt IX -> Hamburg.
PoP's in 2 buildings. 95% of the sites in a 2 km radius. Operation started
in March. URL: www.inx-hamburg.de Has a lot of space available and welcomes
new members. Offered as a service from a company (POP), may set up an
operation company at a later stage.
5. Input for the RIPE NCC Activity Plan 2001
The chair asked for topics that could be put on the RIPE-NCC activity plan
for 2001 and then be pursued by the NCC. Comments from the floor:
* Requests for presentations from IX. Consensus: this is not a NCC
activity, but deserves action.
* Suggestion: IX-object in data-base. Special address ranges for IX's
* Suggestion: how to raise the profile of this group
* Suggestion: BCP for IX's, volunteers Nic Lewis, Š
* Suggestion: Tools. Need requirements. Problem pointed out by Bill
Manning: some sites filter on tools, how to announce this. Keith: 24/7 is
essential. Common infrastructure: set up IX as LIR with the exchange a
subset of /19. Bill: this should be in the BCP. Need tools coordinator.
Henk: even if there is no coordinator, then suggestions on how use TTM
tools at IX's are still welcome.
6. Peering Decision Tree/Bill Norton
Bill presented a paper on the Peering decision tree. This paper is
available on request by mailing him. It has also been presented at NANOG
and LINX. Steps in setting up a peering:
* Phase I: Who do you peer with? Transit is expensive. Monitor where
traffic goes, set up point-to-point connection to site where most traffic
goes. Often no real measurements but best guess.
* Phase II: contact and qualification. WMN set up a spreadsheet with who
wants to peer with somebody else and is happy to add European ISP's.
* Phase III: Implementation
Comments and questions from the floor
* Question: request to put a peering object in the data-base. Discussion
about email addresses: suggest to make a role account (peering@x.net) for
peering. Others suggest to contact people instead of a role account. No
consensus.
* Cost comparison. Direct exchanges better if you have more than 5 peers,
direct lines if <5.
* Which exchange to use: main criteria are: access, deployment, current
presence, operations, business issues, cost, credibility, exchange
population, exiting IX,
* Value of Internet exchange starts at 0, increases as more ISP have
presence until one hits a situation where cost savings are larger than the
cost of equipment. This goes very fast, until there is no more capacity in
the IX.
* Comment: where you go, depends on how you want to profile yourself.
Also, where are the big boys in an area, do you want to be close to them.
* Comment: IX should be able to handle the traffic from a peer, now and in
the foreseeable future.
7. Mike Hughes/IXP wishlist update. Started as an idea following visits to
vendors, topics that are now in the draft
* Document on IXP environment: security, scalability, multicast
* Document general type of IXP setup
* Security and management: dynamic MAC address limiting, wire speed ACL
* Scalability and Resilience: push vendors to develop something
* Multicast
Plans to have a draft document by RIPE37. Input welcome