<html><head></head><body><div style="color:#000; background-color:#fff; font-family:Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:13px"><div id="yui_3_16_0_ym19_1_1542273855160_46589"><span></span><br></div><div class="qtdSeparateBR" id="yui_3_16_0_ym19_1_1542273855160_46590"><div id="yui_3_16_0_ym19_1_1542273855160_46595"><br></div><div id="yui_3_16_0_ym19_1_1542273855160_46646">I tend to agree with Tapani, <br></div><div id="yui_3_16_0_ym19_1_1542273855160_46846"><br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1542273855160_46816">I think when we use the term connected vehicles, we are referring to an IoT device so IP is definitely there as Farell referred to the low energy version of IPv6 (6LoPAN). <br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1542273855160_47066"><br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1542273855160_47137">The DNS latency (as Milton mentioned) is definitely a challenge in IoT/connected "vehicle guidance" but that is something which depends on a multitude of parameters particularly the access technology LTE/EvDo/WiFi/WIMAX/Zigbee etc. <br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1542273855160_47275"><br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1542273855160_47271">And so, when we talk to IoT (e.g. Connected Vehicle) DNS and IP are there. See for example the use of DNSNA and multicast-DNS in the IoT space. Moreover think of the DNS rebinding attacks on IoT devices. Similarly, think of the 2016 Dyn attack, that was accomplished through DNS lookup requests from a huge number of IoT devices. <br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1542273855160_47674"><br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1542273855160_47683">So yea, IoT devices (could be a connected vehicle, a toy, an IP camera etc) is closely linked to IP and DNS but I don't know if this is something which relates to NCSG at this point in time. thanks.<br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1542273855160_47828"><br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1542273855160_47914">Best, <br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1542273855160_47843">Zakir . <br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1542273855160_47764"><br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1542273855160_47825"><br></div></div><div class="yahoo_quoted" id="yui_3_16_0_ym19_1_1542273855160_46679" style="display: block;"> <div style="font-family: Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 13px;" id="yui_3_16_0_ym19_1_1542273855160_46678"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;" id="yui_3_16_0_ym19_1_1542273855160_46677"> <div dir="ltr" id="yui_3_16_0_ym19_1_1542273855160_46818"> <font id="yui_3_16_0_ym19_1_1542273855160_47048" size="2" face="Arial"> <hr id="yui_3_16_0_ym19_1_1542273855160_47050" size="1"> <b id="yui_3_16_0_ym19_1_1542273855160_47194"><span style="font-weight:bold;" id="yui_3_16_0_ym19_1_1542273855160_47193">From:</span></b> Tapani Tarvainen <ncsg@TAPANI.TARVAINEN.INFO><br> <b><span style="font-weight: bold;">To:</span></b> NCSG-DISCUSS@LISTSERV.SYR.EDU <br> <b><span style="font-weight: bold;">Sent:</span></b> Monday, November 12, 2018 11:20 PM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: new paper from the IWGDPT<br> </font> </div> <div class="y_msg_container" id="yui_3_16_0_ym19_1_1542273855160_46676"><br>While I don't know if any of this is relevant to NCSG now or ever, I'm<br clear="none">pretty sure some of the examples in the paper did use and depend on<br clear="none">public DNS (at least the one I know a bit more about, NordicWay COOP).<br clear="none"><br clear="none">So I think Stephanie was not far off the mark in higlighting this as<br clear="none">something that might become a thing of concern to NCSG at some point.<br clear="none"><br clear="none">But the point about DNS latency is good. I should check if they<br clear="none">considered the potential impact of DNS problems.<br clear="none"><br clear="none">Tapani<br clear="none"><div class="yqt3472775127" id="yqtfd50395"><br clear="none">On Nov 11 20:41, Mueller, Milton L (<a shape="rect" ymailto="mailto:milton@GATECH.EDU" href="mailto:milton@GATECH.EDU">milton@GATECH.EDU</a>) wrote:<br clear="none">> <br clear="none">> Steph:<br clear="none">> This paper deals with connected vehicles. You say that domain names will “undoubtedly be involved” at some point. I seriously don’t think they will be. The latency involved in resolving domain names would not be suitable for vehicle guidance. It’s not even clear that internet protocol will be involved in these technologies.<br clear="none">> <br clear="none">> FWIW<br clear="none">> --MM<br clear="none">> <br clear="none">> From: NCSG-Discuss [mailto:<a shape="rect" ymailto="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU" href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU">NCSG-DISCUSS@LISTSERV.SYR.EDU</a>] On Behalf Of Stephanie Perrin<br clear="none">> Sent: Saturday, November 10, 2018 11:46 AM<br clear="none">> To: <a shape="rect" ymailto="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU" href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU">NCSG-DISCUSS@LISTSERV.SYR.EDU</a><br clear="none">> Subject: new paper from the IWGDPT<br clear="none">> <br clear="none">> <br clear="none">> This is slightly off-topic, but members of this list who track IOT and privacy might be interested in this recently released paper from the Berlin Group (aka the International Working Group on Data Protection in Telecommunications). No specific focus on the DNS but this working paper is a good roundup of latest data protection thinking on this topic. There will undoubtedly be domain names involved at some point, the question seems to me to be who will control the data from a content perspective.<br clear="none">> <br clear="none">> Stephanie Perrin</div><br><br></div> </div> </div> </div></div></body></html>