IETF Logo Mail Archive

Re: [DNSOP] Call for Adoption: draft-dupont-dnsop-rfc2845bis

Joe Abley <jabley@hopcount.ca> Wed, 11 April 2018 12:55 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 F31C7126CE8 for <dnsop@ietfa.amsl.com>; Wed, 11 Apr 2018 05:55:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, UNPARSEABLE_RELAY=0.001] autolearn=ham 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 fdlMEcXFSJLH for <dnsop@ietfa.amsl.com>; Wed, 11 Apr 2018 05:55:45 -0700 (PDT)
Received: from mail-lf0-x233.google.com (mail-lf0-x233.google.com [IPv6:2a00:1450:4010:c07::233]) (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 3EE37124BE8 for <dnsop@ietf.org>; Wed, 11 Apr 2018 05:55:45 -0700 (PDT)
Received: by mail-lf0-x233.google.com with SMTP id x70-v6so2486848lfa.0 for <dnsop@ietf.org>; Wed, 11 Apr 2018 05:55:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=from:mime-version:references:in-reply-to:date:message-id:subject:to :cc:content-transfer-encoding; bh=7IervLNIja5N9+u4c5KhRENWg2s1gI/enwD+RF/VplA=; b=DJrYiE5snBxx3J3RpARVCan3NXaBr2PNUiTYuarGddNJhxCce64QwmfQ0eCo9sPK7Y p8+G4kb1N2OOfRFJb1XCEGnYefqvYPIlrdsZYyhqMQSZvqqkxXdJlHtx8MhS88CnZeD8 VgX/FUS8m6qU3/pJp1GNUm63r866isKRK1Zfw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:references:in-reply-to:date :message-id:subject:to:cc:content-transfer-encoding; bh=7IervLNIja5N9+u4c5KhRENWg2s1gI/enwD+RF/VplA=; b=NoEseHjqiI/m483962a/b6gVSru6Dqiis8xwMz4N833ZZclIghFRRoOA79Mir9iXwf enKFnj9Rfn+ufEJsIuG0fJGykdqlxU6LtNgQbYaw3LTZFZ0OVggTve/eHefw01d6exC0 +ff/6T2azGJke72/FA6ghP81kpIZ2MZFkU6f085Xn0i4cnmP+X7iNnZ56JQNbQgZtCfT Fm/kpAS2kPbt3TmNxxeR1hvqG39B1WMHxdNlX3GW7+PWORcVGXkI2AYmYzcXPQjePxPe CPvmPt5CpKstAeLxXnJM8yTb1M4fpA7oq9rueBVt/o1l167VbSqIJGvyuzzF1TJZYoUo uwpA==
X-Gm-Message-State: ALQs6tBxMjceVQdP9FfrhCgQvN+uxC0eEbK/jOPvsj5ZtE0ur4+/K92A blAJPg80QBkTL7lemYQ6wyVFldXGryMGqvjM5QfYCg==
X-Google-Smtp-Source: AIpwx4/wNBuVYbyhWjwlctgeEo9a6pqVsP07H1OXcghKwjTGTWcAg289zOhB086Y7SvCreQ6sv8rtpUdH1g9TXEw8SA=
X-Received: by 2002:a19:c713:: with SMTP id x19-v6mr2975838lff.32.1523451343464; Wed, 11 Apr 2018 05:55:43 -0700 (PDT)
Received: from unknown named unknown by gmailapi.google.com with HTTPREST; Wed, 11 Apr 2018 08:55:42 -0400
From: Joe Abley <jabley@hopcount.ca>
Mime-Version: 1.0 (1.0)
References: <CADyWQ+FX+G52ENFM24joYV7EuegK4YCNrcayKKLJghbzz4z8xg@mail.gmail.com> <CAJE_bqcMYqZuw-z_sLAU3GrKf8s-4dRV_BJicWnDqyL3NDPsSg@mail.gmail.com> <CA+nkc8CNFW-cVYj8W8pifQMfV9iVV7caFg3D_rA-QVeSOg-zWA@mail.gmail.com>
In-Reply-To: <CA+nkc8CNFW-cVYj8W8pifQMfV9iVV7caFg3D_rA-QVeSOg-zWA@mail.gmail.com>
Date: Wed, 11 Apr 2018 08:55:42 -0400
Message-ID: <CAJhMdTPRjmuaWSiBoF9AkuHeQNqShEC7qmyFFzfDt6kGr-rZ6g@mail.gmail.com>
To: Bob Harold <rharolde@umich.edu>
Cc: dnsop <dnsop@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/4FIxSxoHURyd_XOrAYzoCDbofSM>
Subject: Re: [DNSOP] Call for Adoption: draft-dupont-dnsop-rfc2845bis
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 11 Apr 2018 12:55:47 -0000

Hi Bob,

On Apr 11, 2018, at 08:50, Bob Harold <rharolde@umich.edu> wrote:

> In various places, like 4.3.  TSIG Record Format, "resolver and server" is used which seems a little vague to me, since I use TSIG between master and slave authoritative servers, neither of which is a resolver.  Would it make sense to use "sender and receiver" ?  Or 6.5.4. uses "client" and "server" and that would work, if used consistently everywhere.

Since you can send and receive both responses and queries, I prefer
"initiator" and "responder" to "sender" and "receiver". I think I
first saw those terms used in one of Vixie's drafts, and I liked them.

"Client" and "server" have semantic overtones (e.g. relating to end
users and services) and I find them less precise unless the context is
very clear.


Joe

v2.23.0 | Report a Bug | By Email