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] DoH - TEOTIAWKI?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
e.vanuden at avm.de
e.vanuden at avm.de
Fri Oct 19 18:41:01 CEST 2018
DoH? How to resolve local add? How can Enterprise controll trafic? Using DoH will more or less switch of local DNS server, are we shure we want this? Groet, Eric Von: "Jim Reid" <jim at rfc1035.com> An: "Marco Davids" <Marco.Davids at sidn.nl> Kopie: "RIPE IoT WG List" <iot-wg at ripe.net> Datum: 19-10-2018 18:09 Betreff: Re: [iot-wg] "The Internet of Threats: Fighting FUD with MUD" Gesendet von: "iot-wg" <iot-wg-bounces at ripe.net> > 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. _______________________________________________ iot-wg mailing list iot-wg at ripe.net https://mailman.ripe.net/ -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/iot-wg/attachments/20181019/c16859b6/attachment.html>
- Previous message (by thread): [iot-wg] "The Internet of Threats: Fighting FUD with MUD"
- Next message (by thread): [iot-wg] DoH - TEOTIAWKI?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ iot-wg Archives ]