IETF Logo Mail Archive

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

jabley@hopcount.ca Mon, 08 July 2019 20:40 UTC

Return-Path: <jabley@hopcount.ca>
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 8D15B1202F7 for <dnsop@ietfa.amsl.com>; Mon, 8 Jul 2019 13:40:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.702
X-Spam-Level:
X-Spam-Status: No, score=-0.702 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, PDS_NO_HELO_DNS=1.295, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopcount.ca
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 gwdScZuYnwpr for <dnsop@ietfa.amsl.com>; Mon, 8 Jul 2019 13:40:40 -0700 (PDT)
Received: from mail-io1-xd2f.google.com (mail-io1-xd2f.google.com [IPv6:2607:f8b0:4864:20::d2f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 382A91202BD for <dnsop@ietf.org>; Mon, 8 Jul 2019 13:40:38 -0700 (PDT)
Received: by mail-io1-xd2f.google.com with SMTP id z3so23389939iog.0 for <dnsop@ietf.org>; Mon, 08 Jul 2019 13:40:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=ZGDT1YdNXGxRkG648E/45xDx6nRrd9SdXhOWtuC0/wE=; b=FC1NO+QPzv+uJktBh/l2804/qEl8npiabC+y+/SzdPAFXE2LmVXihVT+E9C+ITg/zE CFiWLahypB+ZxzjLFS1BiK780lhytEdTuAoO1hbvuBsuOtY4/k6PsX/eVkU7dAliHKLV vrRoa4s8xOPKt+zmuyR0Beqrp+62zZPywL2H0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=ZGDT1YdNXGxRkG648E/45xDx6nRrd9SdXhOWtuC0/wE=; b=IjTOwW/JN7/Ex42R8BIKD0eewjm/HbL1y6QS17HF6g+D0jqDWNwoeH0/pOTBpqq+FE FC6COStRTgC5LDeZMg5genUjmvKUIiCxcztzO9DDWLRqkbQF6NfadVoeSXqzfpxFpGwy Djmg+VtqRIAIacTBrzAVOprUMrgR2zY3Z3wcWmtYPrB8rbBQH4JqUBj/4hv1qf/lPhau hT+EQZn+jbQl8lFqmKmhhbXW15qSVfUD4ecM75AU+PgKDfTZYjIR+tNqHJ5/4u+cBcNB MUDRNOvzNTTNVzrUYotRqqcSPXhGPkm7HEMtIq3/BNOlXyHo/L++u7mPj6TVWLB+pr+p pE7g==
X-Gm-Message-State: APjAAAWICSnum/MzaV7U6R4QoUzXbtqe5u8WRFCqNbP7mCEtImUuelO3 jKM/8AAZ6Snh7bVkizKqe0QUhw==
X-Google-Smtp-Source: APXvYqykaAY0Vywq5pE3PGdvnRh3XizXnueA0UlFnvDyxh0wtVfa9w5ZtQxo2sKqXLvvWQ+1CzWASg==
X-Received: by 2002:a5d:9643:: with SMTP id d3mr22150602ios.227.1562618437327; Mon, 08 Jul 2019 13:40:37 -0700 (PDT)
Received: from [192.168.1.50] (24-246-23-138.cable.teksavvy.com. [24.246.23.138]) by smtp.gmail.com with ESMTPSA id b20sm14716579ios.44.2019.07.08.13.40.35 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 08 Jul 2019 13:40:36 -0700 (PDT)
From: jabley@hopcount.ca
Message-Id: <E3C51B06-8EA9-4634-B931-61A06985A811@hopcount.ca>
Content-Type: multipart/signed; boundary="Apple-Mail=_F5EB24BC-4873-432F-95C0-604B02F6FF10"; protocol="application/pgp-signature"; micalg="pgp-sha1"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Mon, 08 Jul 2019 16:40:34 -0400
In-Reply-To: <a0309614-bd25-08d4-003d-4615779910f6@isc.org>
Cc: Wessels Duane <dwessels@verisign.com>, "dnsop@ietf.org WG" <dnsop@ietf.org>
To: Witold Krecicki <wpk@isc.org>
References: <20190706213024.GA56650@isc.org> <CAJhMdTMwCiAS+S_j-i3BXPZ=G1zVhAq+YKH07RsDWRgezPhejg@mail.gmail.com> <caa695e7-21e6-9c41-1814-1f4c1d64df7f@isc.org> <CAJhMdTPK3iqg4sF0Kr+jGAXTf2MZ8FAP0DgwQw1kVBHa65wTNA@mail.gmail.com> <191886397.1948062.1562455685612.JavaMail.zimbra@isc.org> <CAJhMdTNvO=TjNUV=6wHwLJB_c+tqwk4zY24jGbi5a0SqdSUsag@mail.gmail.com> <561203a3-7fd9-94cc-5b13-3639b123f8e2@isc.org> <C467FE93-F6CE-4DB4-80E8-654B1485A1F6@hopcount.ca> <BCD5A218-CF1A-4569-B8A2-7BC8B499CC4B@verisign.com> <a0309614-bd25-08d4-003d-4615779910f6@isc.org>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/CBmm5JWKhNe3V6FasxAIxRoQOuo>
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: Mon, 08 Jul 2019 20:40:49 -0000

Hi Witold,

On Jul 8, 2019, at 16:05, Witold Krecicki <wpk@isc.org> wrote:

W dniu 08.07.2019 o 19:20, Wessels, Duane pisze:

> One more thing - this feature is intended for operators, not for regular
> users. We should have more tolerance for shootfooting features there.

I don't have anything extra to add to my earlier observations and I understand in general the points you are making.

One small thing though, on your text above -- I'm not sure precisely what you mean by those words, but it seems possible that you're distinguishing between large, commercial DNS service operators and others who might be smaller, non-commercial, hobbyist, amateur, or something.

I think we should be careful about specifications that appear to promote centralisation or otherwise make assumptions about what particular kinds of operators can or will do. I think our audience includes the full spectrum. (I also don't think small, hobbyist operators have any kind of monopoly on operational accidents, having been involved in more than a couple large-scale events in my time.)

If we can design protocols that can fail in a safe way, I think we should, regardless of whether we imagine safety shoes are being worn.


Joe

v2.23.0 | Report a Bug | By Email