Your IP Address is: 34.229.223.223
Tip: try using "quotes around your search phrase"
You're viewing an archived page. It is no longer being updated.
RIPE Meeting: |
54 |
Working Group: |
Database |
Status: |
Final |
Revision Number: |
2 |
RIPE 54 Database Working Group Minutes
Tallinn - Friday, 26 October 09:00-10:30
[53.5 WW144]
Wait for the formal consensus of the ENUM Working Group on renaming NON-REGISTRY to OTHER (in the org object type) and then ask the RIPE NCC to make the change. [Done]
[53.4 WW144]
Alert Routing Working Group about the implications of the ASN16 to ASN32 transition on tools. [Done]
[53.3 RIPE NCC]
To make sure that if there is a "flag day" for ASN32 behaviour then the planning and introduction for this is done properly and advertised appropriately. [Done]
[53.2 RIPE NCC]
To check and point out this requirement to various software developers: including but not limited to IRRToolSet, Quagga etc. [Done, but see below]
[53.1 WW144]
Close AP50.1 (To make the country attribute on inetnum and inet6num optional and multiple) and properly reformulate it. [Done 2/1/2007]
[51.9 RIPE NCC]
To contact a subset of the spam tool writers and make sure that they are aware of the change in behaviour as required by AP51.8 [Done]
[51.8 RIPE NCC]
To properly implement database behaviour to always return irt object on address queries, if it exists. [Done, but see below]
Remote Participation
[AP54.2 RIPE NCC + Chairs]
To check through documents and decide how to split manuals into RIPE and non-RIPE Documents.
It was noted (Gert Doering) that the lack of references to IRT objects are due to the lack of -c behaviour and that we should go ahead with the implementation of this by default. This action has taken considerable time and we would like to have a flag day very shortly.
[AP54.1 RIPE NCC]
To go ahead with final implementation of IRT query behaviour, within four weeks.
[AP54.3 RIPE NCC]
Go ahead and investigate ensuring that all objects are maintained, including timeline and notifications. Submit proposal to the working group.
[AP54.4 RIPE NCC]
To investigate the provision of a 'white pages' facility for industry-related persons.
Discussion on the "country:" attribute.
[AP54.5 DP-TF]
To analyse better the function of the country attribute in inetnum and inet6num.
Originates from the data protection issue (data must be relevant to the purpose of the RIPE Database).
Steady rise in unreferenced objects. It was noted that a small number of people actually want to be in the database and that the removal notice should offer the means to remain in the database for those who want to remain in the database just so that people can remain if they wish. A work-around to retain your person object might be to create a poem object. Reuse of NIC handles caused some comment, as maintainers might use a NIC handle not understanding that they had possibly changed. It was suggested that objects should be quarantined rather than deleted.
Concern was expressed that there may be external references into the database. The issue of NIC handles shared with the ARIN database was also raised.
General consensus was that we do need to get rid of the unreferenced objects but there was no consensus.
[AP54.6 RIPE NCC]
To summarise the discussion and write up for the mailing list
Resource Certification Task Force: Iimpact on RIPE Database, if any - Nigel Titley.
DNS Working Group: Retire "rev-srv:" Attribute in inetnum - Peter Koch, DENIC
[AP54.7 RIPE NCC] To prepare a plan for removal of the "rev-srv:" attribute from the inetnum, inet6num objects.
WW144 asked if the mandate and/or the chairs of the group needed changing. There was no enthusiasm for replacing the clown at the front or of changing his mandate.