IETF Logo Mail Archive

Re: [homenet] [EXT] securing zone transfer

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 12 June 2019 00:48 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBFD612009C for <homenet@ietfa.amsl.com>; Tue, 11 Jun 2019 17:48:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 PdyVUiPrJNy0 for <homenet@ietfa.amsl.com>; Tue, 11 Jun 2019 17:48:03 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8863D120059 for <homenet@ietf.org>; Tue, 11 Jun 2019 17:48:03 -0700 (PDT)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:56b2:3ff:fe0b:d84]) by tuna.sandelman.ca (Postfix) with ESMTP id 672BF38183; Tue, 11 Jun 2019 20:46:37 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 179C9F29; Tue, 11 Jun 2019 20:48:00 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 13D2BC07; Tue, 11 Jun 2019 20:48:00 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Ted Lemon <mellon@fugue.com>, homenet <homenet@ietf.org>
In-Reply-To: <FFD7BFEB-CF80-4624-8D34-210A6C79BE57@fugue.com>
References: <CADZyTkkgd8f49V+yoZvPZXx3b-_YRzpgUY1-obroq9QMLnFWNw@mail.gmail.com> <cca26a8147924f1ab0d9447e3f083e0c@cira.ca> <FFD7BFEB-CF80-4624-8D34-210A6C79BE57@fugue.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Tue, 11 Jun 2019 20:48:00 -0400
Message-ID: <16282.1560300480@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/btCTFIpscdN0D-NhYj7LUxHp0Dw>
Subject: Re: [homenet] [EXT] securing zone transfer
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jun 2019 00:48:06 -0000

Ted Lemon <mellon@fugue.com> wrote:
    >for things that need internet connectivity, and have the primary DNS
    >server on the main land.   TSIG & DNS over TLS look like a good option
    >to look at.

    > Have you looked at draft-ietf-dnssd-srp
    > (https://tools.ietf.org/html/draft-ietf-dnssd-srp-01
    > <https://tools.ietf.org/html/draft-ietf-dnssd-srp-01>)?

Ted, I didn't think it was relevant, but I read it anyway.

It has been sometime since I tried to grok the SRP stuff, and last time it
was mostly to understand the more homenet related things.

  dnssd-srp> In other network environments, updates for names ending in
  dnssd-srp> "default.services.arpa" may be rewritten internally to  names with
  dnssd-srp> broader visibility.

Our goal with front-end-naming is to provide the "rewritten internally function".

I found section 2.3.2.  Testing using standard RFC2136-compliant servers out
of place. I think it belongs in an appendix?

This dnssd-srp protocol seems like it will work wonderfully within a homenet
(or small to medium sized campus). I think that is the goal.

I don't think it will work as the protocol for a homenet to publish a public
zone to the Internet without some additional security and setup. At least,
that's my feeling at this point.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email