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

Toke Høiland-Jørgensen <toke@toke.dk> Thu, 12 July 2018 22:50 UTC

Return-Path: <toke@toke.dk>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37CEE13120A for <dnssd@ietfa.amsl.com>; Thu, 12 Jul 2018 15:50:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
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: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=toke.dk
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VWlmnS0INSrx for <dnssd@ietfa.amsl.com>; Thu, 12 Jul 2018 15:50:15 -0700 (PDT)
Received: from mail.toke.dk (mail.toke.dk [52.28.52.200]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 523431311F6 for <dnssd@ietf.org>; Thu, 12 Jul 2018 15:50:15 -0700 (PDT)
From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= <toke@toke.dk>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1531435813; bh=5gzlBpDFq+Dw/Y40ypYvmwGw/0rhv4Dl9yEtKho47C0=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=p0p/wcWbNrTvcTPWAgK+20pjjjvUfGPwNjuvp1FgQzj5XX0HFQWNN1pDK0Yls4/ai bB9ydQfwcP9hbP94Foazyqua7xUbvLJEvYVhkGjf4rF1unM4CSJDtyBj3aHoE1yw5y Aj6mhYalgJSFkC2OsFU/FCKI0S4iqmcEfuGmXz2rQaWP+5FwI2e7+xpLviWdDLMFsW tx9ogdESACNM3u8K1yPjS/1qwZRGG/OnNcTe/833i1UamgmHvli5RFxXyYU+JcF5f+ 007pDULxPF/c8Rdp1an69RzBH06OUl3JtRQn5zH1LJnv4eep2iqV2rlL9zy3zUei/Z UzlFzxCet1Tlw==
To: Ted Lemon <mellon@fugue.com>
Cc: David Schinazi <dschinazi@apple.com>, dnssd <dnssd@ietf.org>
In-Reply-To: <CAPt1N1ney2Sf4SYsfEAPqS7sVVxcfni77DKYXXzhJ=8jzi=+EA@mail.gmail.com>
References: <153064569308.5111.7449468818446130425.idtracker@ietfa.amsl.com> <EB70166C-B64B-4509-909D-76978CA00A36@apple.com> <87lgare65v.fsf@toke.dk> <AC270951-0AA4-45D0-9F1A-83067489BF27@fugue.com> <87in5td3ar.fsf@toke.dk> <A667C059-FEBB-4159-A053-0B7AFE35F5FD@fugue.com> <87r2kbcl3h.fsf@toke.dk> <CAPt1N1=kNRiNLMEkSjMmcG+U5Bg6OACkQTAkO6t1b-rzYnza0w@mail.gmail.com> <87fu0obuua.fsf@toke.dk> <CAPt1N1=ktPp-T8fg17fAaT=FznDytnXr2N3Uz1rUL+En_QOKUA@mail.gmail.com> <874lh4bicx.fsf@toke.dk> <CAPt1N1mLA3knwxW0R9Ayb29Og4hh=y+6X9OaPSZW58noYv-4+A@mail.gmail.com> <871sc8b2n9.fsf@toke.dk> <CAPt1N1=npjQS-AyuxtZ3DGLJw12-MA1NZa633maXbJs98rEHUQ@mail.gmail.com> <87tvp49mb6.fsf@toke.dk> <CAPt1N1kp+bt3bcrH9_V0R+M-_tVTH8GjUCj8vEueT7UDP++TOQ@mail.gmail.com> <87pnzs9lrt.fsf@toke.dk> <CAPt1N1ney2Sf4SYsfEAPqS7sVVxcfni77DKYXXzhJ=8jzi=+EA@mail.gmail.com>
Date: Fri, 13 Jul 2018 00:50:09 +0200
X-Clacks-Overhead: GNU Terry Pratchett
Message-ID: <87muuw9ihq.fsf@toke.dk>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/ANV1t7Yr-cz82CNkCxVClxfNrYI>
Subject: Re: [dnssd] The DNSSD WG has placed draft-sctl-service-registration in state "Call For Adoption By WG Issued"
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jul 2018 22:50:18 -0000

Ted Lemon <mellon@fugue.com> writes:

> Hm. For the cloud case, with NAT, that seems kind of problematic
> anyway, because now you have A records in the public DNS pointing at
> RFC1918 addresses.

Unless the registration server knows how to talk to the gateway resolver
and install the RFC1918 addresses as local only (and put the global v6
addresses into global DNS). That's what I'm doing now; but having the
registration server in the cloud means I can use a standard unbound
instance on the gateway; and also the gateway doesn't need to have
access to update the global DNS...

-Toke