Re: [DNSOP] proposal: Covert in-band zone data

Samuel Weiler <weiler@csail.mit.edu> Thu, 25 July 2019 14:53 UTC

Return-Path: <weiler@csail.mit.edu>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 694B912016D for <dnsop@ietfa.amsl.com>; Thu, 25 Jul 2019 07:53:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.234
X-Spam-Level:
X-Spam-Status: No, score=-1.234 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665] autolearn=no 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 HQnhhb2PKCKc for <dnsop@ietfa.amsl.com>; Thu, 25 Jul 2019 07:53:30 -0700 (PDT)
Received: from cyrus.watson.org (cyrus.watson.org [204.107.128.30]) by ietfa.amsl.com (Postfix) with ESMTP id AC6CF120286 for <dnsop@ietf.org>; Thu, 25 Jul 2019 07:53:30 -0700 (PDT)
Received: from dhcp-8906.meeting.ietf.org (dhcp-8906.meeting.ietf.org [31.133.137.6]) by cyrus.watson.org (Postfix) with ESMTPSA id 1432F31B44; Thu, 25 Jul 2019 14:53:30 +0000 (UTC)
Date: Thu, 25 Jul 2019 10:53:29 -0400
From: Samuel Weiler <weiler@csail.mit.edu>
To: Evan Hunt <each@isc.org>
cc: dnsop <dnsop@ietf.org>
In-Reply-To: <20190706213024.GA56650@isc.org>
Message-ID: <alpine.OSX.2.20.1907251048230.29273@dhcp-8906.meeting.ietf.org>
References: <20190706213024.GA56650@isc.org>
User-Agent: Alpine 2.20 (OSX 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/v02ik07w6FvZabRe08AV584Vl6U>
Subject: Re: [DNSOP] proposal: Covert in-band zone data
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jul 2019 14:53:33 -0000

Both docs in this set should say something more about authenticity and 
integrity, particularly since DNSSEC cannot be used to establish the 
same.  (The security considerations sections mention confidentiality. 
Authenticity and integrity are likely important for most use cases.)

On the whole, I'm not a fan of this overall approach, though I'm 
willing to wait and see.

-- Sam