Hi all, This is the argument that I expected; single port allocation looks clean, and enables "simple" delivery of processing resources.
That's why we created ports, no? (please flame here, I have no idea about this historical claim). The underlying question raised by this lovely proposition is: Was that such a great idea in the first place, now that we know that surveillance is **what happens on the internet**. We need the tech community to re-evaluate assumptions based on what has been learned since RFC7258. I do not suggest that DKG's suggestion is the answer, but I suggest that it is worth consideration, and more importantly, the concepts behind it need considering. Should we mandate that all future protocols are "demuxible" from all previous? For me, I say "looks like a good idea" (stream based over TLS). Bring on the discussion. Regards, Hugo Connery -- Head of IT, DTU Environment, http://www.env.dtu.dk ________________________________________ From: dns-privacy [dns-privacy-boun...@ietf.org] on behalf of Joe Touch [to...@isi.edu] Sent: Thursday, 27 April 2017 19:13 To: Daniel Kahn Gillmor; Jan Včelák Cc: dns-privacy@ietf.org Subject: Re: [dns-privacy] Demultiplexing HTTP and DNS on the same listener [New Version Notification for draft-dkg-dprive-demux-dns-http-00.txt] Hi, all, Speaking as an IANA ports team reviewer: IMO this document needs to UPDATE the HTTPS specification. Otherwise, it's basically encouraging squatting on port 443 TCP, which is inappropriate. Keep in mind that any bit pattern that you *think* differentiates DNS from HTTPS is not yours to define - it is the purview of HTTPS to define or delegate in any way they see fit. You can certainly ask IANA for a new port on which to run both HTTPS and DNS, but it is inappropriate to change port 443 without coordination. Joe _______________________________________________ dns-privacy mailing list dns-privacy@ietf.org https://www.ietf.org/mailman/listinfo/dns-privacy _______________________________________________ dns-privacy mailing list dns-privacy@ietf.org https://www.ietf.org/mailman/listinfo/dns-privacy
