<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Shawn,<div><br><div><div>On Mar 11, 2012, at 8:13 PM, Shawn Steele wrote:</div><blockquote type="cite"><div><font color="#000000"><br></font>So, as a 3rd party, I'm not sure how this information is very helpful to me? I mean, it'd tell me what the registry hoped to do for it's zone, but that may or may not match the DNS entries. I can discover valid domains by querying the DNS itself, I don't need to access the list.<br><br>I can see how this information might be helpful for tools that help people manage their zones, however any tools that talked to themselves wouldn't necessarily need this format (though it'd help to be able to import/export the data this way, and maybe interoperate better with other tools).<br><br>I guess what I'm getting at is: What kinds of applications are expected to consume this data? What's the target?<br></div></blockquote></div><br></div><div>The target is really registries, albeit potentially registries at multiple levels of the DNS — not just TLD registries. While other software like end-user applications consume the data, I am not sure what the benefit would be. Once it is in a DNS zone, it is a domain name, and would be expected to resolve. Tables are really beneficial as part of the provisioning process.</div><div><br></div><div>kim</div></body></html>