IETF Logo Mail Archive

Re: [homenet] securing zone transfer

Ray Bellis <ray@bellis.me.uk> Fri, 07 June 2019 21:32 UTC

Return-Path: <ray@bellis.me.uk>
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 4BA241200D5 for <homenet@ietfa.amsl.com>; Fri, 7 Jun 2019 14:32:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=portfast.net
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 P1LUddxyCxzf for <homenet@ietfa.amsl.com>; Fri, 7 Jun 2019 14:32:00 -0700 (PDT)
Received: from mail.portfast.net (mail.portfast.net [IPv6:2a03:9800:20:1::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F24961200B2 for <homenet@ietf.org>; Fri, 7 Jun 2019 14:31:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=portfast.net; s=dkim; h=Content-Transfer-Encoding:Content-Type:In-Reply-To: MIME-Version:Date:Message-ID:From:References:To:Subject:Sender:Reply-To:Cc: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=vPQfa3eX3Es0pMS1XJg+Ua7qJ//A8p/6PJ+2Zxy9VWE=; b=aMvo2ROdmWuME78szR1sNdlKGz F/ydQOgIKETIDKGKItwmkgqmf4UMa8zuDHT3+i4JT7LvRQz1wzy95RxdcrNaWZ0LWdjFykWBSJytu znKGj5NF7IDsNq0BhuFUjrCrQ2A+bn8QkvVdBFLVQ9S1VNlgZXlzkNfcPDFFxZAEM5K0=;
Received: from [88.212.170.147] (port=57120 helo=Rays-MacBook-Pro.local) by mail.portfast.net ([188.246.200.9]:465) with esmtpsa (fixed_plain:ray@bellis.me.uk) (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1hZMSr-0000X9-9J (Exim 4.89) for homenet@ietf.org (return-path <ray@bellis.me.uk>); Fri, 07 Jun 2019 21:31:57 +0000
To: homenet@ietf.org
References: <CADZyTkkgd8f49V+yoZvPZXx3b-_YRzpgUY1-obroq9QMLnFWNw@mail.gmail.com>
From: Ray Bellis <ray@bellis.me.uk>
Message-ID: <73d98e8d-4496-98dd-350f-28b93692b1bc@bellis.me.uk>
Date: Fri, 07 Jun 2019 22:31:56 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <CADZyTkkgd8f49V+yoZvPZXx3b-_YRzpgUY1-obroq9QMLnFWNw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/YMur-9HHV6lnSW5TfgQ025bUs4o>
Subject: Re: [homenet] 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: Fri, 07 Jun 2019 21:32:02 -0000


On 07/06/2019 21:03, Daniel Migault wrote:
> Hi,
> 
> The front end naming architecture uses a primary and a secondary dns 
> server to synchronize a zone. The expected exchanges are (SOA, NOTIFY, 
> IXFR, AXFR. We would like to get feed backs from the working group on 
> what are the most appropriated way to secure this channel.
> 
> Options we have considered are TSIG, IPsec, TLS, DTLS. TSIG does not 
> provide confidentiality, and we would rather go for user space 
> security.  Are there any recommendation for using TLS or DTLS in that 
> case ?

Please don't invent something new.  DNS over TLS should be fine for 
channel security, with TSIG embedded inside that if additional 
authorisation is required.

Ray

v2.23.0 | Report a Bug | By Email