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] Delegation checking policy/procedure at ARIN
- Previous message (by thread): [dns-wg] Delegation checking policy/procedure at ARIN
- Next message (by thread): [dns-wg] Delegation checking policy/procedure at ARIN
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Stephane Bortzmeyer
bortzmeyer at gitoyen.net
Thu May 15 09:34:27 CEST 2003
On Wed, May 14, 2003 at 07:24:44PM +0200, JFC (Jefsey) Morfin <jefsey at jefsey.com> wrote a message of 64 lines which said: > BPs should say that restrictions are to be documented both > in plain text and decribing case per case the tested reasons > of a denial so one can document when the testing is wrong. They are. Any one can see it by itself at http://zonecheck.nic.fr/v2/. > BPs should also say that the intended registration should > be valid when the denial of registration is due to its wrong > analysis of the registrant configuration. There is no reason > why the first come first served rule would defeated by an > error of the Registry. It is not (the ticket is not closed immediately when there is a configuration error). > BPs could say that the registry should provide its proposed > DNS configuration, so the Registrant could implement it to > get registered. For which software? BIND8, BIND9, nsd, PowerDNS? > Will you address IDNA? Yes.
- Previous message (by thread): [dns-wg] Delegation checking policy/procedure at ARIN
- Next message (by thread): [dns-wg] Delegation checking policy/procedure at ARIN
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]