[dnssd] draft-sctl-service-registration call for adoption

[Tom Pusateri <[e-mail]>]

I’ll put this on the mailing list for the benefit of those not at the meeting today.

The document draft-sctl-service-registration is not a general purpose Service Registration Protocol. It has made many compromises to allow registration in a single Update message for constrained devices but there is no encryption or authentication/authorization mechanism that can be used outside an administrative domain.

Since RFC 6763 summarizes in Appendix A:
      Service discovery requires a service registration protocol.
      DNS already has one: DNS Dynamic Update

DNS Dynamic Update is generic and can handle service registration from anywhere under any conditions. But it’s chatty and so there is a need for something that is more efficient for constrained devices.

draft-sctl-service-registration does this by instructing you how to use DNS Dynamic Update is a particular way. It’s a profile of usage.

Therefore, I don’t think we should call this Service Registration Protocol which is a generic name because it isn’t a generic solution. 

I propose “DNS Update Profile for Constrained Services”.

Without a name change, I don’t support adoption of this draft.

Thanks,
Tom