This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/iot-wg@ripe.net/

[iot-wg] "The Internet of Threats: Fighting FUD with MUD"

• Previous message (by thread): [iot-wg] "The Internet of Threats: Fighting FUD with MUD"
• Next message (by thread): [iot-wg] "The Internet of Threats: Fighting FUD with MUD"

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Jim Reid jim at rfc1035.com
Fri Oct 19 18:09:30 CEST 2018

> On 19 Oct 2018, at 16:23, Marco Davids <Marco.Davids at sidn.nl> wrote:
> 
> It seems that another idea of ours, restricting access based on
> DNS-queries, seems to already been incorporate in the current version of
> the draft. Cool ;-)

Marco, you might be too optimistic. :-(

If DoH takes off, IoT devices might well use port 443 rather than port 53 to do their lookups.

IMO DoH is going to be a game-changer. And not just for IoT.

• Previous message (by thread): [iot-wg] "The Internet of Threats: Fighting FUD with MUD"
• Next message (by thread): [iot-wg] "The Internet of Threats: Fighting FUD with MUD"

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ iot-wg Archives ]