Re: [dnsoverhttp] You've got DNS in my HTTP! No, you've got HTTP in my DNS!!!!

I do not mind if there is a new model or structure in which DNS and Web are running.  But if we want to proceed towards a real BOF or WG in IETF in near future, I think we should defined the problem with a PS draft first. 

--Davey

songlinjian@gmail.com

From: Shane Kerr
Date: 2016-11-23 13:47
To: dnsoverhttp@ietf.org
Subject: [dnsoverhttp] You've got DNS in my HTTP! No, you've got HTTP in my DNS!!!!
All,

One thing that really stuck with me at the dnsoverhttp bar-BoF was when
someone said that DNS is adopting features that look like HTTP
(DNS sessions handling, DNS RR server-side push, etc.), and that HTTP
is adopting features that look like DNS (sending certificate chains,
providing address information, etc.).

I wonder if our models are starting to break down? Having two protocols
with seemingly very little in common adopting the same features kind of
implies that our abstractions are broken, right?

I can see a number of ways to approach this situation. We can muddle on
and end up duplicating functionality ad-hoc (not necessarily bad), we
can consider a new thingy that encompasses shared needs, we can push
each function to one part of the stack or the other. I don't know.

I don't have any proposals, just something that's been in my head. :)

Cheers,

--
Shane

_______________________________________________
dnsoverhttp mailing list
dnsoverhttp@ietf.org
https://www.ietf.org/mailman/listinfo/dnsoverhttp