Your IP Address is: 3.16.128.248
Tip: try using "quotes around your search phrase"
You're viewing an archived page. It is no longer being updated.
Database Working Group RIPE 71
19 November 2015, 14:00-15:30
WG Chairs: Nigel Titley, Job Snijders, Piotr Strzyzewski
Scribe: Nigel Titley
AP67.5 [AA-WG] To check that the Anti-Abuse Working Group has properly specified both what should be done with mail that is sent to the abuse contact and (possibly) its format.
Still ongoing but will have a response by RIPE 72.
AP69.1 [RIPE NCC] Produce a self contained document describing migration of the changed: attribute to the last-modified:/created: attributes
(Discharged)
AP69.2 [RIPE NCC] Come up with some straw man proposals for displaying history for objects where available (Ongoing)
AP69.3 [RIPE NCC] To examine and report on possible solutions to improving geolocation data in the RIPE DB (Ongoing but if no progress by RIPE 72 then kill it)
AP70.1 [All] Discuss deprecation of plain text passwords in email (Ongoing)
AP70.2 [RIPE NCC] Come up with a proposal for the status: field to fix the requirement that certain objects may need multivalued status. (Ongoing)
The presentation is available at: https://ripe71.ripe.net/presentations/110-ripe71-db-update.pdf
In response to a question from the floor (RV), it was stated that documentation on RPKI transfer between RIRs has been delayed by awaiting proposals from Adress-Policy and the IETF. Tim is willing to help work on this paper.
It was noted (WW) that the original RFC-set on RPKI has been overtaken by events and should be re-examined.
AP71.1 [WW144] To organise an effort to look at this.
The presentation is available at: https://ripe71.ripe.net/presentations/177-DBWG-RIPE71.pdf
A request was received from the floor (RV) for the identity of the originator of a dual authentication request to be included in the notification to the other maintainer.
The presentation is available at: https://ripe71.ripe.net/presentations/123-rpslvsbgp.pdf
For further details see the presentation.
The presentation is available at: https://ripe71.ripe.net/presentations/122-afrinic_routing_registry.pdf
The presentation is available at: https://ripe71.ripe.net/presentations/111-ripe71-afrinic-irr-home.pdf
RV announced that he didn't object (applause). However there are operational concerns which must be monitored throughout the progress of the migration.
WW was concerned that we are fragmenting the data used to build network filters and this is increasing the fragility of the process.
Discussion to continue on the mailing list.
The presentation is available at: https://ripe71.ripe.net/presentations/176-route-object-ripe71.pdf
The presentation is available at: https://ripe71.ripe.net/presentations/115-Control-over-associating-objects-for-number-blocks.pdf
It was also noted that in many cases the owner of a lower level object may not be known to the RIPE NCC and the appropriate approach would be for the legacy holders to sort things out and then come back to the RIPE Database.
The argument appears to be that deciding who is the holder of the resource is non trivial.
Athina Fragkouli, RIEP NCC,pointed out that the RIPE NCC has no certainty of the ownership of the resource without conducting their due diligence checks.
Trying to fix this without appropriate authority opens the RIPE NCC to liability for irreversible effects due to their actions. Conversation to be concluded offline
Ran out of time
Ran out of time
Ran out of time