This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[dns-wg] Yeti DNS and the RIPE NCC
- Previous message (by thread): [dns-wg] Yeti DNS and the RIPE NCC
- Next message (by thread): [dns-wg] Yeti DNS and the RIPE NCC
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
João Damas
joao at bondis.org
Wed May 25 11:50:15 CEST 2016
Actually Jim, first comes the poll of the community to see if this fits, later comes what you suggest, if the community decides to ask the RIPE NCC to look into it, or have we become the Ministry of IP? Joao > On 25 May 2016, at 09:55, Jim Reid <jim at rfc1035.com> wrote: > > >> On 24 May 2016, at 13:41, Shane Kerr <shane at time-travellers.org> wrote: >> >> Please let us know what you think about this idea. > > <No hats> > Before we take this idea forward, could someone please suggest metrics and milestones that could be used to assess the success or failure of this activity? For bonus points, it would be good to know what sort of resource commitments will be needed and the level of reporting that can be expected from the NCC being involved in Yeti DNS. > > We should be careful to not have the NCC get into open-ended, vague commitments where there's uncertainty about the on-going value to the community. Experiments are all very well but both the WG and the NCC's DNS team need to know how/when to decide to kill the experiment or turn it into a formally supported resource or do something else with it. > >
- Previous message (by thread): [dns-wg] Yeti DNS and the RIPE NCC
- Next message (by thread): [dns-wg] Yeti DNS and the RIPE NCC
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]