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] Tweaks to RIPE 663: Secondary DNS Service for ccTLD Operators

• Previous message (by thread): [dns-wg] Tweaks to RIPE 663: Secondary DNS Service for ccTLD Operators
• Next message (by thread): [dns-wg] Tweaks to RIPE 663: Secondary DNS Service for ccTLD Operators

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Jim Reid jim at rfc1035.com
Thu May 26 20:29:46 CEST 2016

> On 26 May 2016, at 14:44, Romeo Zwart <romeo.zwart at ripe.net> wrote:
> 
> Following the guidelines of the working group, we (the NCC) have
> recently started reviewing eligibility of ccTLDs based on the existing
> document text. If the document moves back to a 'limbo-state' based on
> renewed discussion in the WG that makes it very difficult for the NCC to
> proceed.

Romeo, I think the NCC should continue with its current plans based on RIPE663 rather than wait for an updated document which might not emerge any time soon, if at all.

• Previous message (by thread): [dns-wg] Tweaks to RIPE 663: Secondary DNS Service for ccTLD Operators
• Next message (by thread): [dns-wg] Tweaks to RIPE 663: Secondary DNS Service for ccTLD Operators

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ dns-wg Archives ]