Re: [dnssd] The DNSSD WG has placed draft-sctl-service-registration in state "Call For Adoption By WG Issued"

Toke Høiland-Jørgensen <> Thu, 12 July 2018 10:40 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CD3431310C5 for <>; Thu, 12 Jul 2018 03:40:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id TcSojT0CgGyl for <>; Thu, 12 Jul 2018 03:40:35 -0700 (PDT)
Received: from ( [IPv6:2001:470:dc45:1000::1]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E7C87130DDA for <>; Thu, 12 Jul 2018 03:40:34 -0700 (PDT)
From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= <>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;; s=20161023; t=1531392030; bh=h6mrJyneWTe9iJLSvahdcsQgYHqekvy3h5NGnwzUBTw=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=RvaN8IxYYwF+JNVZbQAY9F8IOXlh4JKqjdzin3ZmTAZWI2AzG4A6eo+H3qNoUWquQ Oumb0sm+/LUcHrYAsD/xpIWgpkPNJBewaElO/xpj08D++8bDKGFcMMjinfO+aAmaiM CZJk/FAanPpoLo7bozCh5rpqhZP50Lepd2x1IVi2PxoP05oQGmT0sRhyLugfD9Mnx/ HFu6TAa0ejTa5KYF7MEqUtQG3iFR6C+3hckqjNRwKx3PZsbDMOYZX9t0E6g37653Ng wqhS9vtLiEVVn0GrNteihEprXSHVJrTpBpQ9/Ordpx1f8hByU12u2OEx3/bkQJg+vP itGFwHUijf9hA==
To: Ted Lemon <>
Cc: David Schinazi <>, dnssd <>
In-Reply-To: <>
References: <> <> <> <> <> <> <> <>
Date: Thu, 12 Jul 2018 12:40:29 +0200
X-Clacks-Overhead: GNU Terry Pratchett
Message-ID: <>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <>
Subject: Re: [dnssd] The DNSSD WG has placed draft-sctl-service-registration in state "Call For Adoption By WG Issued"
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: Thu, 12 Jul 2018 10:40:38 -0000

Ted Lemon <> writes:

> I just did a somewhat larger-than-expected update to the document to
> capture Toke's comments thus far. I also got a surprise guest review
> from a friend of mine, Tamara Kemper, who revealed a few opportunities
> to make the document clearer and better scoped. In the process of
> doing these two things I noticed that I'd fairly significantly
> misstated how SRV records work and left out some important details.
> The new document fixes all of these things (I hope). Sorry for adding
> so much text during an adoption call, but I didn't want to leave it
> for later because it would have made reading the document kind of
> unpleasant for Stuart, who I hope will review it this weekend, and if
> I hadn't done it now it would have taken at least twice as long later.
> The good news is that I'm pretty chuffed about the quality of the
> document now.

Thanks for the update! I think this version addresses my concerns from
the previous round. :)

A few other comments based on a quick read-through:

- Since registrations are always done with .local, it is up to the
  registration server to decide which domain(s) the registration ends up
  in, right? How is it supposed to do that if servicing multiple zones?
  Just based on source IP?

- The document says that clients must generate their own reverse PTR
  records. Should the server be able to do that on the clients behalf?
  It may be a matter of policy which ranges have reverse domain

- Related to the above, is it permitted for the registration server to
  modify the records submitted by clients before putting them into
  DNS? For example, to add PTR records, or to remove a subset of the
  records etc? The alternative to modifying would be to reject the whole
  registration if a subset is not admissible. If the server *is* allowed
  to modify things, should it communicate back to the client what it
  really did?

- You mention in the text that a network may use a different domain than for reverse PTRs. How does that work? Won't clients always
  do reverse lookups to