On 13 Mar 2013, at 19:24, Michael Thomas <[email protected]> wrote: > On 03/13/2013 11:20 AM, Tim Chown wrote: >> >>> 3.7.1 Service Discovery >>> >>> This section starts out with telling us how it will be presented to the >>> user (GUI) >>> without any reference to why a user or anything else needs service >>> discovery. >>> As service discovery is not common on the internet today, I think this >>> requires >>> a lot more motivation/requirements before jumping and telling us that out of >>> scope GUI's will come to the rescue -- it's not even clear that >>> machine-machine >>> interfaces to find and configure, say, my IP speakers to my IP home >>> entertainment >>> system won't be the norm. >> Service discovery *is* common in home networks today. Currently users see >> such SD via whatever GUIs they use. But sure, the future is likely to also >> include device to device SD. > > Service discovery is *not* common. Only in the rarified environment of > IETF could such a statement be made with a straight face. Just because > appletalk, lan manager protocols, etc provide such functionality doesn't > mean they are in common use in homes.
I guess we'll have to agree to disagree there. > In any case, this isn't responsive to the larger point that this section > doesn't provide any motivation of why SD is needed or even important, > and if it is, what the homenet requirements are. The need for SD has been implicit from the start of the process. No one else has questioned that need, as yet. If others agree with you, it would be good if they spoke up now. Tim _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
