Subject: Re: [dnssd] Last Call: <draft-ietf-dnssd-requirements-04.txt> (Requirements for Scalable DNS-SD/mDNS Extensions) to Informational RFC

From: Markus Stenberg <[email-masked]>
Date: Mon, 5 Jan 2015 13:44:28 +0200

(Sorry about the late reply, too much vacation.. *grin*)

Comments:

- in e.g. section 2, I find use of ‘DNS-SD/mDNS framework’ confusing. DNS-SD works across links just fine; it is plain DNS. I would also omit the framework. Alternatively, perhaps DNS-SD+mDNS would convey the meaning better. section 6.5 uses ‘DNS-SD + mDNS implementation’ once.

- use case F: is it really justified? it is just mentioned in REQ14. based on my reading, if it was just added to C’s list of link technologies, it would be also inherited by D and E..

- REQ2: Does it apply to C? Small business/homenet + scopes - what would be the example?

- REQ5: I am not sure what ‘integrate’ means here. Unidirectional access (SSD -> DNS-SD/mDNS? SSD <- DNS-SD/mDNS?)? Bidirectional?

Cheers,

-Markus