[dnssd] Review of draft-ietf-dnssd-srp-05

[Manuel Amutio <[e-mail]>]

Hi,

I've revised the current version "draft_05" and in general it looks good to
me. I believe that it is an important improvement in the use of automatic
discovery of network services and it is greatly useful for IoT constrained
devices.

Leave my comments below.

Best,
Manuel


/------------- Typos --------------/
Page 9, first paragraph:
"This key pair MUST be unique to the device" is repeated twice.
"+" symbol appears twice.

Page 12, second paragraph:
"Instrructions"

/------------- Doubts -------------/
Page 9, section 2.4.1.1 Service Behavior:
"the key MAY be overwritten as a result of a full reset of the device
(e.g., a "factory reset")"

What happens then?

Page 10, section 2.4.2 Removing published services:
"To remove a service registration, the client retransmits its most recent
update..."
"However, in some cases a client may not have retained sufficient state to
know that some service instance is pointing to a host that it is removing."

Then, how is it able to retransmit an update of something that no longer
knows?

Page 15, section 2.6.2. Sleep Proxy:
This feature conditions the location of SRP Server, right?
If we thought in a Border Router, it would only be useful for external
traffic going through BR, but not for traffic initiated in the mesh
network.
Maybe I have misunderstood it.

Regarding the protocol used, I don't see a clear drawback to not allow
using UDP for the constrained devices. If the DNS service allows it, I
believe that this new protocol should support it too.