Re: [Dots] Call for adoption on draft-boucadair-dots-server-discovery

["Konda, Tirumaleswar Reddy" <[e-mail]>]

Hi Daniel,

After the discovery of the DOTS server, the DOTS client must authenticate the DOTS server and vice-versa. If the DOTS agents cannot mutually authenticate each other, the discovery mechanism is of no use.


The only way to automate the discovery of DOTS server and automatically configure the explicit trust anchor store for the attached domain on the DOTS client is to use BRSKI (see https://tools.ietf.org/html/draft-ietf-anima-bootstrapping-keyinfra-17), using BRSKI the device (co-located with DOTS client) would have already learned and validated the network domain name, and can use DNS-SD to discover the DOTS server.



Further, S-NAPTR lookup helps provision the preferred DOTS signal channel transport protocol b/w the client and server, and the destination port of the DOTS server.



I don’t see the need to support mDNS and “.local” or “.home.apra”.


Cheers,
-Tiru

From: Dots <[e-mail]> On Behalf Of Daniel Migault
Sent: Tuesday, January 15, 2019 8:54 AM
To: Flemming Andreasen <[e-mail]>
Cc: Roman Danyliw <[e-mail]>; [e-mail]
Subject: Re: [Dots] Call for adoption on draft-boucadair-dots-server-discovery


CAUTION: External email. Do not click links or open attachments unless you recognize the sender and know the content is safe.


________________________________
I support the adoption of the draft.

While this should not prevent the adoption, I would avoid mDNS and prefer the use of SD with unicast DNS. For homenet, .local should be replaced by home.arpa.  I am not sure NAPTR solution could not be replaced by DNS-SD as well. I am happy to look at these discussions.

Yours,
Daniel


On Mon, Jan 14, 2019 at 12:29 PM Flemming Andreasen <[e-mail]<mailto:[e-mail]>> wrote:
I support WG adoption of this draft.

Thanks

-- Flemming
On 1/9/19 2:17 PM, Roman Danyliw wrote:

Hello!



Excluding support from the draft authors, the interest in adoption (or any response) was low on the list (one) and also at IETF 103.  The previous discussion around this draft was more spirited.  My concern is that this call may have been lost in the end of year holidays.  To that end, I'm extending the call for adoption.



Please provide feedback to the list/chairs if you believe that this document should be adopted as a WG document.  This extended adoption call will end on Tuesday, January 22.



Regards,

Roman and Frank



-----Original Message-----

From: Dots [mailto:[e-mail]] On Behalf Of Roman Danyliw

Sent: Friday, November 30, 2018 5:22 PM

To: [e-mail]<mailto:[e-mail]>

Subject: [Dots] Call for adoption on draft-boucadair-dots-server-discovery



Hello!



This is the start of a two week call for input on the WG adoption of the

document:



draft-boucadair-dots-server-discovery

https://tools.ietf.org/html/draft-boucadair-dots-server-discovery-05



The document has been presented and discussed at IETF 103, IETF 100 and

IETF 99;  and revisions have been made based on WG feedback.  Discussion

of adoption of this draft was previously deferred pending submission of the

signal draft for publication (which occurred in September 2018).



At the IETF 103 meeting, there were not many participants who had read the

draft.



Please provide feedback to the list/chairs if you believe that this document

should be adopted as a WG document.  The adoption call will end on

December 14 2018.



Regards,

Roman and Frank



_______________________________________________

Dots mailing list

[e-mail]<mailto:[e-mail]>

https://www.ietf.org/mailman/listinfo/dots

_______________________________________________

Dots mailing list

[e-mail]<mailto:[e-mail]>

https://www.ietf.org/mailman/listinfo/dots

...



_______________________________________________
Dots mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/dots