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/dns-wg@ripe.net/
[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 ]
Jim Reid
jim at rfc1035.com
Wed May 25 12:04:55 CEST 2016
> On 25 May 2016, at 10:50, João Damas <joao at bondis.org> wrote: > > Actually Jim, first comes the poll of the community to see if this fits, Well Joao the community already seems to be heading in that direction. YMMV. That said, it would be helpful for the WG to have a better understanding of the requirements before asking the NCC to investigate. > later comes what you suggest, if the community decides to ask the RIPE NCC to look into it, Up to a point. Though before the NCC does look into this (or anything else for that matter), I think the NCC should have a sense of what the WG's expectations and objectives are. Unclear requirements help nobody. > or have we become the Ministry of IP? I have no idea what this Ministry does or why they should interfere in WG matters. :-)
- 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 ]