Re: Send-N draft: draft-bellis-enum-send-n-02 published
| Newsgroups | gmane.ietf.enum |
|---|---|
| Message-ID | <OF759CECC8.C87153D1-ON80257472.0051AFEE-80257472.005250B3@nominet.org.uk> |
> I fail to see why your use for DNS should take precedence over existing > DNS types at all, this will only lead to disparity between countries, I > find the idea of databasing this information useful, but don't break > existing systems to achieve it. My use doesn't take precedence. If you need to use wildcards, and the absolute Send-N form isn't suitable for you, just don't put in any Send-N records at all. They're completely optional. The need to wildcard can take precedence. There are plenty of cases where bad things are possible through misconfiguration of DNS records, and the usual answer is "don't do that". I'm struggling to understand why that's not considered a valid answer in this case. For what it's worth, section 5.7 of the Enumservices Guide draft specifically requests that Registration documents should identify any incompatibilities with wildcard records. That's an explicit understanding that such incompatibilities are possible. Ray