Dear All, As agreed at RIPE38 EIX-WG, herewith a brief summary of the various documents, activities, suggestions etc that has evolved from the work carried out towards the EIX BCP project, for comment and discussion. I have (roughly) divided the summary into 3 areas, 'ISP focussed' - matters that I perceive as having use or value largely to the ISP community, (but without differentiation between what may be of use to ISPs already present at IXPs, and what may be of use to ISPs wishing to start building a presence at IXPs.), 'IXP focussed' - matters that I perceive as having use or value largely to the IXP operator community, and 'Other' - for miscellaneous stuff. This summary is not exhaustive, nor is the structure or way in which I have separated the subjects expected to be any more than a starting point, (there is substantial overlap between many of the subjects), but hopefully it will be a reasonable basis for further discussion and progress. An important note to make is that there are a number of related activities by other parties underway, some toward the same goals and some that may have influence on, or be influenced by, this work. To try and avoid duplication of effort, provide the widest scope for this work, and to give credit to the other parties, I have identified these where I am aware of them in parenthesised notes. Identification of further instances would be appreciated and any omissions are unintentional. 1 ISP focussed activities/documents ----------------------------------- 1.1 General Information: 1.1.1 Definition of an IXP (History - the original 4 'NAPs' etc?) 1.1.2 Directory of home pages (NB - B Manning 'ep.net') 1.1.3 Brief history of each IX (Relate to 1.1?) 1.1.4 Governance/Management models (Inc. affiliations with other bodies) 1.1.5 Central FAQ depository ISP focus - cf 2.1.2 below) 1.2 Procedures: 1.2.1 Membership requirements/criteria (NB - NL and other work underway) (Inc. any special legal or regulatory requirements) 1.2.2 Application processes/guides (NB - NL and other work underway) (Inc. timescale estimates, relates to location info below) 1.2.3 Co-location availability/cost indicators (Must be objective and non-preferential) 1.2.4 Central application service (possibly too ambitious?) 1.3 Current Status: 1.3.1 Costs of membership & services included (NB - NL and other work underway) 1.3.2 Membership(AS No) 'matrix' (NB - NL and other work underway) 1.3.3 Contact details, 'role' entry points (NB - NL and other work underway) 1.3.4 Locations (NB - some sensitivity here - input from operators required) 1.3.5 Access/support contacts, procedures (NB - staffed/sub-contracted etc) 1.3.6 Other services/value adds (EG Multicast, IPv6, NTP etc etc) 1.3.7 Mailing lists available, and their uses (CF 1.4.4) 1.3.8 Central peering contact list (NB - consider B Norton work) 1.4 Technical: 1.4.1 Architecture and available connection modes 1.4.2 Connection procedures, in-building (Inc. contact details of who can/will cable) 1.4.3 Connection procedures , WAN connection (carrier availability & cost indicators WRT other co-los) 1.4.4 Ticketing/trouble systems (CF 1.3.7) 1.4.5 '3D' peering matrix - AS v AS v IXP (NB - NL work underway) (CF RR consistency - Shane Kerr/Maldwyn Morris) 1.4.6 IX routing availability/mapping (CF Hermes - Andrea Carmignani/RIS - Henk Uijterwaal) 2. IXP focussed activities/documents ------------------------------------ 2.1 General Information: 2.1.1 Website translation services (NB - NL work underway) 2.1.2 Central FAQ depository (IX focus - cf 1.1.5 above) 2.1.3 Mechanism to update details in section 1) (use of XTML??) 2.1.4 Common look & feel (NB - many web sites already exhibit this to some extent) 2.1.5 'Statement of Intent' (to encourage new IXPs) 2.1.6 Common information presentation and reporting (are there standards that could be applied?) 2.2 Procedures: 2.2.1 Identification of common application requirements (NB - NL work underway) 2.2.2 Standardisation/simplification of application procedure 2.2.3 Central function to 'pre-screen' applicants (Subject to individual IX requirements) 2.3 Current Status: 2.3.1 Clearer cost indication 2.3.2 Standardised format for membership listings (auto populate IXP Current status above?) 2.3.3 Recommended or standardised email 'role entry points' 2.3.4 Extension of discussion/knowledge sharing WRT value adds 2.4 Technical 2.4.1 Shared technical knowledge base (Inc. known issues, fixes, vendor contact points etc) (CF - Mike Hughes wish list) 2.4.2 Mailing list cross posting facility? 2.4.3 IP Addressing information (NB - re-visit IXP object in RIPE Database, Antony Antony?) 2.4.4 Common trouble/ticketing system (For issues affecting multiple IXPs 3 Other considerations ---------------------- 3.1 Peering agreements (Can further work simplify things for ISPs?) 3.2 Co-lo activities in this area (Should we have more dialogue with co-lo companies as a group?) 3.3 Consider outside ripe region? (Would we/others benefit from extending the availability of this work?) (OK, so we're not likely to get MAE buy in any time soon.......) Conclusion I have not particularly tried to determine the nature of each subject, (ie is whether it is a BCP, FYI or something else) and would like the group's feedback on this, as well as the general content. No doubt some suggestions will be seen as precocious, it is hoped this will stimulate further discussion. Suggestions for additions to, or modification of, any of the above is welcome and anticipated. I would like to thank everyone from within the working group and wider RIPE community who has given me input and ideas towards this, and in particular the 'behind the scenes' support of two of my colleagues, Terry and Fredrik, whom I mention by name because they have done lots of research work towards this, but have not, as yet, been unleashed to wreak havoc in the WG. Yet. Regards, Nic