On Feb 5, 2014, at 4:06 PM, Paul Hoffman <[email protected]> wrote:
> On Feb 5, 2014, at 7:17 AM, Osterweil, Eric <[email protected]> wrote: > >> Specifically, DANE is (imho) excellent example of a standard architecture >> for certificate discovery using DNS. > > As has been noted in many places over the past few decades, using the DNS for > information deliver vs. information discover are very different things. Jakob > and I have chosen to go with the standard assumption that the DNS is for > information delivery, and other protocols (these days, mostly HTTP) can be > used for information discovery. > > If the DANE WG wants to change this, and the IETF at large agrees, we can > certainly walk down that path, both with this document and with TLSA itself. Hey Paul, Thanks for the quick response. I am, however, a little puzzled by it. So, is there some reason why these discussions here (on the WG list) are not the actual substance of determining what the DANE WG wants? As I understand it (perhaps incorrectly?), we are discussing a working group document, so discussion of its contents should be inbounds and any resulting rough WG consensus should help direct its contents, no? As for the broader statement of what DNS is for, and what the IETF at large thinks, I think perhaps you have expressed your own opinion here, and I (personally) do not agree. In my view, DNS is (very much) a resource mapping (i.e. learning) mechanism. That's how we find routable endpoints for HTTP. ;) Content delivery aside. I suspect you and I may actually be on the same page on that one, but apparently not on the learning issue. Back to the main issue, I am following up on Scott's solicitation for discussion about his proposed changes, and expressing my support for them. I have read your response to those and responded to it, and I am happy to discuss the technical details further. Eric _______________________________________________ dane mailing list [email protected] https://www.ietf.org/mailman/listinfo/dane
