Rob Blokzijl welcomed the participants to the 13th RIPE meeting. Apologies were received from the following persons:
Hans Nussbacher resigned as chairman of the mapping working group. Daniele Bovio has agreed to act as chairman.
The agenda was approved.
Joyce Reynolds wished to give a short presentation on the new IETF working groups in the User Services area.
Niall O'Reilly wished to make a short announcement concerning HEAnet.
Mikhail Popov presentation on the current state of networking in Russia was moved to Friday morning.
Logistics and organisational details for the meeting were handed to the RIPE vice-chairs for consideration, who reported back on Thursday 1st October.
The minutes from the 12th RIPE meeting were approved.
Action: Ruediger Volk Francis Dupont
Collect DNS tools and make available to public via NCC Archives. Action to be reviewed during the DNS working group.
Action: Tony Bates and Marten Terpstra
Produce a document on experiences of running IP/IXI. Action closed because it has been overtaken by the EMPB proposal.
Action: Rob Blokzijl and Daniel Karrenberg
Write a RIPE section to the Internet Monthly Report. Action completed.
Action: Erik-Jan Bos
Produce a recommendations document on security issues. Prepare for next technical session. Both action items open. Technical sessions planned for 14th RIPE meeting.
Action: Francis Dupont and Milan Sterba
Produce a cookbook on DNS. First version ready at the next RIPE meeting. Input
on the contents of the document is requested. Action open. No progress. Action has been deferred until the publication of a book which is thought to be useful input.
Action: Daniel Karrenberg
Make a new distribution of the database tools available. Action completed.
Action: Daniel Karrenberg
Coordination of vendor presentations at the next RIPE technical session. Action open.
Action: Daniel Karrenberg
Send the address of the ISO subcommittee that handles ISO-3166 work. Action completed.
Action: Marten Terpstra
To store and make available to public DNS tools. Action completed.
Action: Marten Terpstra
Install mailing list on RIPE machines for those working groups who requested a list. Action completed.
Action: Marten Terpstra
To archive routing recommendations in NCC document store. Action completed.
Action: Marten Terpstra
Collect information regarding the Second Root Name Server. The relevant IETF working group will be contacted regarding global requirements. Ongoing and dependant upon the decisions reached in the DNS working group.
Action: Marten Terpstra
To evaluate Domain Debugging Tools. Action open. Two tools evaluated and ongoing.
Action: Hank Nussbacher and Don Stikvoort
Write a charter for the RIPE mapping working group. Action open and moved to Daniele Bovio.
Action: Bernhard Stockman
Distribute the draft RIPE statistics document to the ripe-org mailing list for further comments. Action closed. No progress.
Action: Ruediger Volk
Produce a document on methods for incremental updates of the RIPE database. Action has been completed. Document can be found in ripe/docs/ripe-draft/ripe-drafts-inc-update-v0.txt
Action: Jean-Michel Jouanigot
Send routing recommendations to RIPE for approval. Action completed.
Action: Jean-Michel Jouanigot
Make available NLC software via anonymous FTP (via NCC). Action open and progressing.
Action: Jean-Michel Jouanigot
Discussions regarding the Routing Policy Description Form. Discuss this with Jessica Yu. Action open.
Action: Milan Sterba and Geza Turchanyi
Evaluate and consider nature of information for NIDUS. Action open.
Prior to the meeting, the RIPE position paper had been circulated. As such the paper is now considered to be a document which reflects consensus of opinion within the RIPE
community. The meeting thus agreed to the paper as is. The document currently in the RIPE document store:
/ripe/docs/ripe-draft
ripe-draft-position-v2.txt
will be given a document number and moved to:
/ripe/docs/ripe-docs
The RIPE NCC status report was presented by Daniel Karrenberg. It was based on the September quarterly report, which was included as a document at the meeting. What follows is a summary of that document. It was noted that the report was in fact a draft version so that comments concerning the content of the report could be incorporated if received. Comments were invited and welcomed.
The status report was based on comparisons drawn between the status report given at the 12th RIPE meeting. Activities reported comprised the following.
Since the beginning of September the NCC agreed to handle all requests for IP numbers from European organisations. Statistics were presented concerning the number and speed of response on requests. In response to an invitation by the NCC for local registries to identify themselves, the NCC is now able to forward a significant number of requests. It
was mentioned that it was the goal of the NCC to respond to all requests within 5 working days.
The RIPE database software has been completely rewritten. The changes mean that the software is now:
Using the RIPE Whois client it is now possible to query the RIPE database by default and use additional flags to query the US databases. The quotes are no longer necessary.The
new whois client can be found in /tools/ripe-whois.tar.Z
There have been ongoing discussions to resolve the inconsistencies between the RIPE database and the GSI database with Mark Kosters. Schema discussions continue and progress will be reported.
The hostcount is published monthly and can be found in the RIPE document store in the subdirectory ripe/hostcount. The error files and output are also contained in the same
directory.
The document store has been reorganised and made complete. Thanks were given to the RIPE chairman for his significant effort.
The RIPE NCC leaflets have been revised and version 2 of each leaflet has been drafted. Printing was subject to approval of the leaflets at the RIPE meeting.
Audiocast tests are ongoing. Those interested in taking part in the tests should contact the NCC.
It was pointed out to the audience that the statistical data presented in the Quarterly report were exclusive of the last week of September, in order that a draft of the report could be produced in time for the meeting.
The evaluation of the RIPE NCC status report was made by comparing the present with previous goals presented at the 12th RIPE meeting. In particular the following were noted:
The RIPE organisational position paper has been distributed, which explains the RARE to RIPE NCC relationship. To repeat, RARE provides the organisational framework for the
RIPE NCC. This has been and continues to be a satisfactory situation. The suggestion however to change this to put the RIPE NCC under the jurisdiction of the OU was not considered appropriate because it is thought that the OU will be a service provider and it is vital that RIPE NCC remains an impartial and fair organisation.
At the RARE CoA in Bratislava on September 24-25 it was agreed and stated that RIPE is and should remain a separate body in its own right.
As the financial reporting of the RIPE NCC is formally to the RARE treasurer a full financial report could not be made. The present financing of the RIPE NCC will be published in the minutes of the RARE CoA meeting. It was noted however, that the RIPE NCC budget expenditure after the first 6 months of operation has been as expected. However,
to fulfil all of the goals outlined in the activity plan (document ripe-35) with equal priority, more staff may be needed.
At the RARE CoA it was agreed that a fairer model for the financing of the RIPE NCC should be agreed upon. Currently there are many organisations who are not contributing to the funding of the RIPE NCC and who utilise the services provided. Therefore it was recommended that all organisations currently contributing should pay a fairer share of the
overall budget, with those organisations who currently utilise the services of the RIPE NCC, making a contribution.
Current contributing RARE organisations have agreed to continue financing the RIPE NCC from April 1st 1993 until 31st December 1993.
In the discussions that followed the complexity of the problem was noted, specifically how do you determine a "fair" contribution; accounting procedures must be in place; can
you rely upon voluntary contributions? The financing problems of the German NIC were also noted. It was proposed to begin discussions of the financing of the RIPE NCC with
the establishment of a financing task model. Discussions were moved to the BOF session on Delegated Registries.
A short written document in the form of a letter received from the Secretary-General of RARE on the outcome of the discussions with respect to the relationship between RARE
and RIPE was distributed as a meeting document and is also included below. To reiterate, the document stated that it was agreed that the existence of both RIPE and RARE within
Europe was useful and that each group would endeavour in its technical programs not to duplicate the work done by each other and the IETF.
-------------------------------------------
Dear Rob,
Enclosed please find the formulation of the CoA decision on the relation between RARE and RIPE, as approved by the REC:
Could you please carry the message to the RIPE meeting and use your influence to have this agreement accepted by the RIPE.
Best regards
Tomaz
--------------------------------------------
An outline of the function and purpose of the RARE Technical Program (RTC) was given. Briefly the RTC defines the technical program of RARE. The program is managed through the guidelines given by the RARE Executive Committee (REC).
Traditionally the technical activities of RARE have been OSI oriented, but this is changing so that much greater focus will be placed on general networking. There is a strong
desire by CoA, REC and the RTC to collaborate with RIPE and to avoid any duplication of effort. The methodology for this is to be discussed further but will start with the
suggestion that RIPE Chairman becomes a member of the RTC.
The need for both pragmatism and reality was stressed. Specifically: operational services must be the focus point; the workplan must reflect user needs; the piloting of new services is crucial; duplication of work is to be avoided with the recognition that there is no intention to compete with RIPE.
A short introduction to the Task Forces and the RARE Technical Reports (RTR's) was given.
An invitation to send comments concerning the RTC's was suggested.
An outline of the RARE working groups was presented. Prior to the meeting documents had been circulated describing the name of the working groups, the chairperson, the charter of the group and the main work items.
The proposal presented was to conduct a study to quantify Internet traffic on a global basis for a period of at least one month but preferably three, with cooperation and
involvement from the RIPE community.
Based on a study carried out at the University of Hawaii it was found that:
When the period of measurement was increased, the above figures decreased. A one and half month period gave around 10 per cent transit traffic, whilst a 6 month period gave 4.32 percent. The goals of the project were identified as follows:
To effectively sample the traffic flows, the duration of the study was proposed for a period of at least one month but preferably 3 months. To date, the data yielded from traffic
studies has proved difficult to analyse due to the shortage of the time period (between 1 - 3 hours) hence the longer period of study is felt necessary.
The study requires people at strategic traffic flow points to participate in a global effort to gather statistics over a 1-3 month period, at both network and application layers. The software developed at the University of Hawaii will be made publicly available. It was observed that secondary storage of all the gathered raw data will be required, therefore it may be necessary to find funding for the necessary equipment.
The paper tabled by Rekhter, Lee and Gerich on Global Address Assignments (Point 6 Recommendations) was circulated at the meeting to encourage discussion, so that a RIPE
position could be agreed upon. Thus a presentation was not given but a short statement was made explaining that the paper would be considered in the Delegated Registries BOF
session.
The need for coordination and alignment of procedures between the local and delegated registries inside Europe was introduced and it was noted that a special BOF session on
this topic was scheduled on the agenda for Thursday 1st October. Furthermore it was noted that at present there was no charge for this function and consideration during this
BOF session should be given to potential funding models.
This presentation was moved to Friday 2nd October and is reported under the Connectivity working group report.
The ECCO meeting discussed the long term strategy of the EBONE. There are basically two functions the EBONE could provide, to be a neutral platform for interconnections among service providers and to be a pan-European IP backbone. It was agreed that both functions were needed today.
The EBONE has to evolve towards an open market situation and to be trustworthy in such an environment EBONE has to have:
A strategy document will be produced before the end of 1992 where these issues will be described and to act as input to a revised MoU.
The ECCO decided that based on a proposal from Dennis Jennings the expenditures of EBONE shall include:
The expenditures will be recovered using a weighted system depending on connected bandwidth.
Based on the agreed financial model most EBONE members signed on for current or increased EBONE connectivity. With this amount of connectivity to the EBONE the cost for a 64 Kbps connection will be around 50 kECU per year.
Many new organizations have shown interest in becoming EBONE members such as Infonet, Alternet, US SPRINT and ANS all of whom have signed the EBONE MoU.
The today loose EBONE organization will not be sufficient for a long term EBONE. There is a need to more clearly define roles of the today existing EBONE bodies which are:
The EMC shall in the future consist of 5 - 10 members which are nominated by the EBONE members. At the meeting 11 participants volunteered to be in the EMC. The final compo-
sition will be voted on. Voting rights is given only to RBS sites.
There is a need for an EBONE Manager. Frode Greisen volunteered for this position which was accepted by the meeting. Frode will start to work 20 percent as EBONE manager during 1992 and with 50 percent during 1993.
EAT will continue to consist of representatives from the EBONE members and have the engineering responsibility of the EBONE. EOT will continue to consist of the EBONE NOC staff plus representatives from the EBS sites.
A smaller group will overlook the current EBONE organization and have a proposal ready before the end of 1992.
According to the MoU for EBONE-92 a proposal for a takeover of the EBONE by the OU was sent to the OU Steering Committee. There was no formal response from the OU. The possibility of EBONE existing within a proposed OU has to be reexamined at a later stage if necessary. Like the RIPE NCC, EBONE has to be neutral and not liaise with one of many service providers to continue to be trustworthy.
EBONE is an Internet i.e. it is a collection of networks. The technology does not provide all the magic needed for policy implementation. It is a framework for cooperation. EBONE tries to enhance fault management EBONE is a moving target where any member can influence events.
A technical proposal produced during the autumn 1991 outlined most of the things now being implemented. The EBS/RBS concept was invented by EBONE. Use of only commercial available routers. Distributed Management. Optional elements in the specification become needed.
Coordination and education are a challenge. EAT was invented in Geneva.
Re-implementation of European routing. Pilots BGP-3 pilots in Stockholm February 1992. Stockholm goes BGP-3 in March. ICMnet joined. Later this summer Amsterdam. London
went BGP from day one. NIKEF - JANET closed a loop via IXI. CERN joined later and Montpellier joined last but they also closed the loop.
In US the backbone has policy which creates problems so EBONE made the inverse and put poli- cies in the regions.
Backbone for the European R&D
Access:
Routing
No connectivity to the non-European Internet is planned in the foreseeable future.
Non European connectivity is NOT included in the charges to customers therefore an extra payment will be required for those requiring non-European connectivity.
The proposal was made to establish a Multicast backbone for Europe (MBONE). Reference was made to the special BOF session organised on this topic. All those interested were
invited to attend.
Reports from the working group sessions
Andreas Schachtner presented the report for the working group. Glenn Kowack sent his apologies for not being able to deliver the presentation himself.
It was noted that this was the third time that this working group has convened.
The following was agreed by the group:
To realise the above objectives, the following tasks were identified:
No volunteers for the work tasks outlined above came forward. As a minimum it was noted that these issues should be catalogued to facilitate ongoing discussions.
Action: Glenn Kowack investigate and catalogue points raised under Item 13.1.2 Group tasks.
Joyce Reynolds made a presentation on the new IETF working groups in the area of User Services. This presentation was also made to the wider audience, so is reported in full
under item 16 of the minutes under Any Other Business (AOB).
Two ideas were discussed in the Network Information Discovery and User Services (NIDUS) working group on the related themes of classifying network information organisations and services across Europe, as described below.
It was observed there is already a considerable amount of resource information available, held for example in the RIPE NCC Interactive Information Server. There was a suggestion
to survey the information available there and to include back pointers to information in this area stored by for example the RARE-ISUS working group.
Action: Geza Turchanyi and Nandor Horvath Agreed to work on the survey of the availability of existing information with respect to the RIPE document store.
The second suggestion was to define a new RIPE database object for resource information, to specify information on resource type, access methods and form of the data.
With regard to the second idea, concern was expressed over the difficulty in structuring such information and whether as a result the RIPE database would be suitable. Some
liaison was required with the RIPE Database working group in this matter. It was agreed that as a preliminary the kind of information required should be analysed, enabling a
refinement of the original idea.
Action: Milan Sterba Refine proposal for a new RIPE database object for resource information, to specify information on resource type, access methods and form of the data. Circulate proposal to the new mailing list for vote.
The RARE-NAP WG agenda is not yet available then this is only a proposal.
The DNS working group proposed the following work items for discussion:
Full reference for the book referred to above is "DNS and BIND" by Cricket Liu and Paul Albitz scheduled for publication during October 92 by O'Reilly and Associates. It was
noted that BIND 4.9 (the next version) is not yet available.
The proposed structure for the working group activity is to consider the following issues:
There was a proposal to establish a specific mailing list with respect to the technical work issues of the Database working group. Notification of the operation of the list would be announced to the ripe-list.
Action: Daniel Karrenberg/Marten Terpstra. To announce operation of db-wg group mailing list on the ripe-list.
There were more than 40 attendees at this working group session which lasted one and a half hours. There were 3 main topics for consideration:
The following topics were discussed:
13.5.1.1. Jean Michel Jouanigot presented a list of compilers that
13.5.1.2. Proposal of pilot
13.5.1.3. Policy based routing tag collection
The EBONE system will filter between EBS/RBS. A good way of describing this is by using Jessica Yu's proposed policy description form.
Hans Eriksson participated at this meeting and is one of the pioneers in this area. The WG discussions centred around the following:
It is necessary to find volunteers near strategic points in the physical infrastructure. EBONE EBS sites are covered.
A group of volunteers named MBONE-EU will be formed. For those interested in participate in this group get information and software from ftp.ripe.net in tools/mbone Frequently Asked Question list (FAQ-list) exists. Find a strategically positioned neighbour if you want to join. You can use the mailing list below if you wish to do so:
Mailing list: [email protected]
It was stressed by all involved that this multicasting should not be considered a production service but rather an experimental one.
Also regulatory issues of carrying voice were raised briefly.
Those present who had researched the issue stated that one is probably safe as long as no con- nection to the public telephone network is made. Local conditions can vary.
The multicast pilot from this RIPE meeting was not successful due to insufficient local line capacity.
Due to room scheduling problems There was no meeting of this group. Decisions were taken in the plenary session (see below).
Registry system of funding was not discussed due to time constraints and it was resolved to continue the discussion over the mailing list.
The attendees agreed that excellent work had been done and the document was of a very high standard. Some concerns were raised that the address allocation guidelines could be
perceived as hard and fast rules rather than guidelines. Also the guidelines should be revised at a later stage in the light of experience. Some reservations were felt about
the class B addresses being retained by the Internet Registry: it was resolved to agree to this for the present, with a view to further evaluation in the light of experience. To conclude, the consensus of opinion as expressed in the BOF was endorsed in the plenary session as representative of the RIPE opinion.
Action: Daniel Karrenberg prepare a document to reflect the RIPE position and circulate it on the ripe list.
It was observed that it may be necessary to reserve address space to be used for networks which are unlikely to ever require connectivity to the Internet. The case of supermarkets connecting their stores using tcp-ip to connect to their central cash centre as an example. Concern was expressed that this would otherwise unneccessarily lessen
the amount of global address space available. Volunteers were asked to come forward to draft a future RFC on this problem.
The German EBS meeting made review of IP activities in Germany. The GMD proposal for an EBS and two 256 lines financed by GMD was presented. EAT has accepted this as this
will improve Internet connectivity to Germany.
Good set of agreements between most IP nets in Germany which will continue with this effort.
Hungary is still waiting for an upgrade of the existing line between Budapest and Linz to 64 bit/s. There seems to be some technical problems, which could be solved by the end of
this year
The Warsaw-Vienna terrestrial IP line is now operational at 64 bit
Prague-Linz line has been upgraded to 64 bit/s and Bratislava-Vienna should be upgraded by the end of 1992
Several IP lines interconnect now different network clouds in the Moskow area to DESY
Germany, DNet Denmark, Alternet USA. None of these lines has NSF connected status yet.
The EARN line from Moskow has been downgraded to a dial-up link to Stockholm.
Action: Milan Sterba Produce CEEC report version 5.
By the end of october 1992 both Vienna-CERN (256 kbit/s) and Linz-Amsterdam (128 kbit/s) should be operational. Negotiations are going on about setting up an EBS in Austria.
The expected tariffs and other Ebone connectivity aspects have been briefly explained by Bernhard Stockman and Peter Lothberg.
Peter Lothberg announced a cheap IP solution for a PC router which is able to communicate with a cisco at 64 kbit/s. Info can be obtained by ftp from tftp.ebone.net
(directory./cheap)
At the next RIPE meeting in Prague there will be a presentation of cheap IP solutions implemented in the framework of the joint franco-czechoslovak project COPERNICUS.
Despite the strong commitment of RARE at JENC3 in Innsbruck to contribute to a better coordina- tion of network infrastructure building in CEE countries, EMPB lines have now been ordered between Amsterdam-Prague-Budapest-Bern and Amsterdam-Aarhus-Warsaw-Bern as the part of the EMPB project financed by the PHARE project. The setting up of these lines has been very poorly (if at all) coordinated with networking organisations in CEEC and never with RIPE. This lack of coordination will have negative impact on the possibilities of integration of these services to the global network and results in financial waste. PTT Telecom is now, after the lines have been ordered, willing to coordinate.
Misha Popov gave a presentation on the current state of networking in Russia, with respect to both the technical developments and the organisational changes that have
occurred since the last RIPE meeting. From the 5th October 1992, Russia will have improved connectivity from 9.6 Kbps to 64 k to DATEX-P in Germany.
During discussions, the following points were agreed upon:
The next meeting of the RTC is in Pisa on November 3-5th. It was agreed that Rob Blokzijl should attend to represent RIPE.
Torben Nielsen asked for volunteers for people to take part in his proposed study of Internet traffic. The target start date would be 1st January 1993 and the study would run for at least one month. Torben announced that he would create a mailing list for those interested. Details of the list would be sent to the ripe-list. The immediate tasks were identified as follows:
Action: Torben Nielsen Make slides of the Traffic Measurement presentation available in the RIPE document store.
The NCC offered to coordinate this in Europe. Daniele Bovio and Oliver Martin volunteered to help seek agreement for access to measurement points.
Action: NCC To keep in touch with Torben and disseminate information within RIPE as the measurement project continues.
The next meeting is to be held in Prague on January 25-27. Audiocast is intended but may not be possible if the local infrastructure cannot support it. The technical demonstrations are not on the agenda at present, but if volunteers come forward to organise them, they can be included into the usual 3 day RIPE meeting. The location for the 15th RIPE
meeting was proposed and agreed upon Amsterdam for 27-29th April 1993. An invitation has been received for a RIPE meeting to be held in Lisbon. A date was suggested - Janu-
ary 1994.
Request for groups willing to pilot OSPF and Dual IS-IS as IGP for EBONE. Please report to Jean-Michel Jouanigot. EBONE are interested in hearing from those who have any
experience with OSPF and Dual IS-IS.
Peter Lothberg has signed a contract accepting the position of EBONE skipper.
Daniele Bovio announced that late registration for the Pisa meeting on November 3-5 would now be cheaper due to exchange rate fluctuations.
The revised RIPE NCC leaflets on "Interactive Information Server" and the "Network Management Database" were approved subject to minor modifications.
Prior to the meeting Hans Nussbacher resigned as chairman of the Mapping Group. Daniele Bovio accepted an invitation to become the new chairman of the group. However, the mapping group did not formally convene at this meeting. Instead Daniele Bovio presented his thoughts on the possible future direction of work for the group. He considered the following tasks as important and immediate:
Action: Daniele Bovio prepare a document for consideration at the next RIPE meeting, but a message will also be sent to the Ripe-list asking for input on this activity.
A paper giving summary of the work of the IETF working groups in the User Services Area was distributed to those who attended the NIDUS working group and was available to
members of the audience who were interested. Also available were copies of the NISI-wg "NIC template" Those who did not receive the information can do so by contacting Joyce Reynolds.
A presentation was given by Joyce to the new working groups in this area. The four new working groups are:
IIIR is chartered to facilitate interoperability between Internet Information Services and to develop, specify, and align protocols designed to integrate the plethora of Internet information services (WAIS, archie, Prospero, etc.) into a single "virtually unified information service.
This working group is chartered to increase the useful base of information about networked information retrieval tools, their developers, interested organisations, and other
activities that relate to the production, dissemination, and support of NIR tools, NIR is a cooperative effort of the IETF, RARE and CNI.
URI is chartered to define a set of standards for the encoding of system independent Resource Location and Identification information for the use of Internet information
services.
The purpose of WNILS is to expand and define the standard for WHOIS services, to resolve issues associated with he variations in access, and to promote a consistent and
predictable service across the network.
The new working groups have a common architecture and will work together to eliminate redundancy.
A HEAnet NIC will be formed, employing one person initially. Thanks were expressed to the RIPE community for their valuable support.
Rob Blokzijl thanked the participants, with special thanks to the local organiser Philippe-Andre Prindeville. The 13th RIPE meeting was declared closed.
Open Actions
The open action list below is sorted by the first name of the primary responsible person as this is what our tools permit us to do easily and automagically.
Action: Antonio Blasco Bonito To make a proposal on how to do general purpose extensions to the database in a general manner.
Action: Bernhard Stockman - Tell Matti Rehndal to contact Marten Terpstra on issue of secondary name servers in Europe.
Action: Bob Day and Daniel Karrenberg Align the common explanatory document about IP number registration and the common template.
Action: Bob Day Circulate draft of an explanatory document about IP number registration.
Action: Daniel Karrenberg prepare a document to reflect the RIPE position and circulate it on the ripe list.
Action: Daniel Karrenberg Circulate a draft of a common IP number registration template.
Action: Daniel Karrenberg and Wilfried Woeber prepare a formal recommendation for input to RARE on a the ownership and "acceptable use of the database".
Action: Daniel Karrenberg to circulate new draft object definition for Autonomous System objects to the mailing list (and Ruediger Volk).
Action: Daniel Karrenberg Coordination of vendor presentations at the next RIPE technical session.
Action: Daniel Karrenberg Make a proposal on how to delete an object from the database.
Action: Daniel Karrenberg/Marten Terpstra. To announce operation of db-wg group mailing list on the ripe-list.
Action: Daniele Bovio prepare a document for consideration at the next RIPE meeting, but a message will also be sent to the Ripe-list asking for input on this activity.
Action: Erik-Jan Bos: Produce a recommendations document on security issues. Prepare for next technical session.
Action: Francis Dupont and Milan Sterba: Produce a cookbook on DNS. First version ready at the next RIPE meeting. Input on the contents of the document is requested.
Action: Geza Turchanyi and Nandor Horvath Agreed to work on the survey of the availability of existing information with respect to the RIPE document store.
Action: Glenn Kowack investigate and catalogue points raised under Item
Action: Hank Nussbacher and Don Stikvoort: Write a charter for the RIPE mapping working group.
Action: Jean-Michel Jouanigot and Marten Terpstra examine "non standard" use of fields. Further discussions are necessary.
Action: Jean-Michel Jouanigot Discussions regarding the Routing Policy Description Form. Discuss this with Jessica Yu.
Action: Jean-Michel Jouanigot Make available NLC software via anonymous FTP (via NCC).
Action: Joyce Reynolds Keep RIPE informed about developments around the new US NIC (NSF NIS contract award).
Action: Marten Terpstra Changes in the database format. Coordination discussions with US counterparts are ongoing.
Action: Marten Terpstra Collect information regarding the Second Root Name Server. The relevant IETF working group will be contacted regarding global requirements.
Action: Marten Terpstra To evaluate Domain Debugging Tools.
Action: Marten Terpstra To progress GSI/Merit/RIPE NCC exchange format discussions
Action: Milan Sterba and Geza Turchanyi: Evaluate and consider nature of information for NIDUS.
Action: Milan Sterba To work on draft proposal concerning the resource object and to circulate to the db-wg mailing list.
Action: Milan Sterba Produce CEEC report version 5.
Action: Milan Sterba Refine proposal for a new RIPE database object for resource information, to specify information on resource type, access methods and form of the data. Circulate proposal to the new mailing list for vote.
Action: Milan Sterba To circulate Link item proposal and circulate to new db-wg mailing list.
Action: NCC Routing object, routing privilege update.
Action: NCC Set up [email protected] mailing list.
Action: NCC To keep in touch with Torben and disseminate information within RIPE as the measurement project continues.
Action: NCC. To include the operational contact attribute in all object definitions besides persons
Action: Ruediger Volk Francis Dupont Collect DNS tools and make available to public via NCC Archives
Action: Torben Nielsen Make slides of the Traffic Measurement presentation available in the RIPE document store.