Shane, TFers, Thanks for holding the BoF and for sharing this. To repeat and expand on my input at the BoF. 1.) I am missing language about evolution of the requirements and the database itself. A high level stock taking exercise like this one that aims to be the basis for a service has to make it explicit that it addresses just about one point in time and things *will* change. It makes sense to spend a few paragraphs on how this will be handled. 2a.) -- ‘Provide registration information of Internet number resources’ is a primary purpose. I would use a title like “Authoritative and Accurate Registry of Internet Number Resources’. As far as I can see it ‘Enabling transfer of IP resources’ should be part of that. 2b.) I suggest grouping a number of the other separate items under ‘Facilitate Internet Operations and Operational Coordination’: - Facilitating communication about usage of the resources - Publishing routing policies by network operators (RIPE IRR) - Reverse Domain Name System (rDNS) - The RPKI Database It is important that we emphasise the RIPE DB is not just a registry but an operational tool. 3.) This iteration seems too detailed for me already. The charter is ‘… The purpose of the document is to establish community consensus at the general level. …’. I think it would make sense for the TF to take a step back and look for the general themes behind the detailed issues. And to look at it from the point of view of the users, first and foremost the primary users, those who register information in the database and use it for operational purposes. Thank you again for working on this. If it was easy it would just happen. Daniel