IETF Logo Mail Archive

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

Bob Harold <rharolde@umich.edu> Wed, 11 April 2018 12:50 UTC

Return-Path: <rharolde@umich.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 AEC87126CE8 for <dnsop@ietfa.amsl.com>; Wed, 11 Apr 2018 05:50:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umich.edu
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 iY3YKJxB8QNp for <dnsop@ietfa.amsl.com>; Wed, 11 Apr 2018 05:50:08 -0700 (PDT)
Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (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 95B70124BE8 for <dnsop@ietf.org>; Wed, 11 Apr 2018 05:50:07 -0700 (PDT)
Received: by mail-lf0-x235.google.com with SMTP id x70-v6so2461775lfa.0 for <dnsop@ietf.org>; Wed, 11 Apr 2018 05:50:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umich.edu; s=google-2016-06-03; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=dX0DEduh7dLLtOxx2IxFFbmGuZdFHL6sxOaDHyCYmtw=; b=dfCZW9hSwSI1kAngDE1zXQm7tGSfIDiFW5ky97yd9s507Rb6MAf6PfB8UfPiFyFiEH D07ZLDxMs7ORNesiPgBf6afOG8pw8EseI0opvuVM/KXpJ8MQchVN6TJvgv/v9qlOLSqL +FGCJXWOmvGHSsgRklInzRPkusXB77ciK7uvZ8PA/JndNr8ErRWPR8TzfBJJoZUXmRRf 6qKG/EhC7Rho9HsHK7P5cVIBrmHxpYyfQxRxIiACOWRS7VT7fXa+dHqHf2Bx14ejbS2p Ngmdg8ZM2eKzYN5v4bpnjkbuclQ9UvDbuH0yGSKqwnzDeGmH9dF4ZChlHa3/u3kcwmfJ y4fw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=dX0DEduh7dLLtOxx2IxFFbmGuZdFHL6sxOaDHyCYmtw=; b=KVFoWFD/qCDH8nRqTqZCFC7ZqZbcV1GLy1kkdyWS134Wkg4Iq6U2cuwepbWrTHKgej sryjafHhCPXciL0Fjf36c2gVYOnlASCLvQycxuR/oznMTuXsNGdQ0BTwOXf17xqEdtov d0qNXNkmqzvhbnl0wZ6P/WBrPZHtEETAudeIas2RcboyLw9LP87wX/JLRDJyL2QhPEzF ZnsVv9MhOsfqDW0hdZwh/XRj08ZiwbiD9vrfgghkqZ1ghV/7p6yXJLrjAOnH8lSzFnDq wWCa0z+C7Qs8nx3zNLFEieEDmcae81lTjdYb1uQKObfvS5slI3UMHh6JKHTCCCPThybV 8MbQ==
X-Gm-Message-State: ALQs6tDTPH4RLYLbboGGL3kD5b9S3jODeCoeY2zMubivwxNXCTUeQpsp cbQ92reRpmGm/AY5yzrB86tcdbBS11JG9gMQSvIshToc
X-Google-Smtp-Source: AIpwx4/PFkqizwGkgbgmKOvBRM+JqP0a/4EqA2MyGk4ZTBI6s6jbj4g3ifSeZRboTMP1n0TLuHno3imlPC2NoMjkCls=
X-Received: by 2002:a19:105:: with SMTP id 5-v6mr667934lfb.86.1523451005411; Wed, 11 Apr 2018 05:50:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.46.66.211 with HTTP; Wed, 11 Apr 2018 05:50:04 -0700 (PDT)
In-Reply-To: <CAJE_bqcMYqZuw-z_sLAU3GrKf8s-4dRV_BJicWnDqyL3NDPsSg@mail.gmail.com>
References: <CADyWQ+FX+G52ENFM24joYV7EuegK4YCNrcayKKLJghbzz4z8xg@mail.gmail.com> <CAJE_bqcMYqZuw-z_sLAU3GrKf8s-4dRV_BJicWnDqyL3NDPsSg@mail.gmail.com>
From: Bob Harold <rharolde@umich.edu>
Date: Wed, 11 Apr 2018 08:50:04 -0400
Message-ID: <CA+nkc8CNFW-cVYj8W8pifQMfV9iVV7caFg3D_rA-QVeSOg-zWA@mail.gmail.com>
To: dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000002c70605699214b2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/q-Vfh9V9Qrt9leZyYmCeGYtsgM0>
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:50:11 -0000

On Tue, Apr 10, 2018 at 4:57 PM, 神明達哉 <jinmei@wide.ad.jp> wrote:

> At Tue, 10 Apr 2018 14:56:53 -0400,
> tjw ietf <tjw.ietf@gmail.com> wrote:
>
> > This draft was widely accepted in Singapore, and the chairs were waiting
> for
> > a revision before starting a call for adoption. That revision took a few
> > months
> > but it has been done and DNSOP is ready to start a call for adoption.
> >
> > This draft addresess the bug found in the existing RFC.
> >
> > This starts a Call for Adoption for draft-dupont-dnsop-rfc2845bis
> >
> > The draft is available here:
> > https://datatracker.ietf.org/doc/draft-dupont-dnsop-rfc2845bis/
> >
> > Please review this draft to see if you think it is suitable for adoption
> > by DNSOP, and comments to the list, clearly stating your view.
>
> I support the adoption.  I've already reviewed the draft and provided
> (minor) feedback:
> https://www.ietf.org/mail-archive/web/dnsop/current/msg22063.html
>
> --
> JINMEI, Tatuya
>
>
> I support adoption.

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.

6.5.1.  Key check and error handling
Why is this only for a "non-forwarding server" ? --- Answer is in 6.7, A
reference to there might be helpful.

-- 
Bob Harold

v2.23.0 | Report a Bug | By Email