Re: [dnssd] New Version Notification for draft-sctl-service-registration-02.txt

Tom Pusateri <> Mon, 16 July 2018 12:59 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A7255129385 for <>; Mon, 16 Jul 2018 05:59:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id COn1w6cCwxm2 for <>; Mon, 16 Jul 2018 05:59:05 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 751BF130DF9 for <>; Mon, 16 Jul 2018 05:59:05 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id F0B68779; Mon, 16 Jul 2018 08:57:22 -0400 (EDT)
From: Tom Pusateri <>
Message-Id: <>
Content-Type: multipart/alternative; boundary="Apple-Mail=_92A2F957-31DA-410C-A8ED-F107CCFC64A3"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Mon, 16 Jul 2018 08:59:03 -0400
In-Reply-To: <>
Cc: dnssd <>
To: Ted Lemon <>
References: <> <> <> <> <> <>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <>
Subject: Re: [dnssd] New Version Notification for draft-sctl-service-registration-02.txt
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 16 Jul 2018 12:59:08 -0000

> On Jul 15, 2018, at 11:07 PM, Ted Lemon <> wrote:
> OIC, you mean which domain should be used to discover the default registration domain?
> Is this better? <>

Yes, the the dr._dns-sd._udp.<domain> part is more clear. Thanks.

The TTL addition still leaves ambiguity for the server implementation:

"Service Registration servers SHOULD ensure that TTLs are reasonable: neither too long nor too short.  The TTL should never be longer than the lease time.”

Can you give guidance for “too short”? “too long” seems to be > lease time. If this isn’t what you mean by “too long”, guidance on that would be appreciated too.

And finally, if the TTL is “too long” or “too short”, how does the server respond? Does the server accept the registration and modify the TTL? Does the server reject the registration and return an error? What error code?

One minor nit. If I understand the distinction correctly, you use “domain” if the following places where you should use “zone”:

Section 2:

However, they can be assumed to be able to provide registration domain discovery and routing.

Section 2.2:

As described above, full-featured devices are responsible for knowing in what domain they should register their services.