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] RIPE NCC secondary name services for ccTLDs
- Previous message (by thread): [dns-wg] RIPE NCC secondary name services for ccTLDs
- Next message (by thread): [dns-wg] RIPE NCC secondary name services for ccTLDs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Janos Zsako
zsako at iszt.hu
Thu Nov 12 16:32:18 CET 2015
Dear Romeo, > At RIPE 68 you, the working group, provided us with some guidelines > regarding the eligibility of new zones to be added to this service. We > intend to document these guidelines in the form of a new RIPE Document*, > of which a draft version is attached to this email. > > We welcome any comments you may have on this document. Thank you for this document. I think it reflects very nicely all the aspects discussed by the ad-hoc group and by the DNS-WG at RIPE 68. I have a small comment regarding the first bullet of point 4., which now reads: "If the number of delegations in the zone, or in any of its child zones, exceeds 10,000..." I think this clearly refers to any public child zone, i.e. a child zone that is administered by the ccTLD itself, and not to a delegated zone managed by a third party. Therefore I suggest adding the word "public" before "child". Best regards, Janos > Kind regards, > Romeo Zwart
- Previous message (by thread): [dns-wg] RIPE NCC secondary name services for ccTLDs
- Next message (by thread): [dns-wg] RIPE NCC secondary name services for ccTLDs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]