[DNSOP] Review of draft-ietf-dnsop-attrleaf-fix

"Murray S. Kucherawy" <superuser@gmail.com> Wed, 18 July 2018 15:37 UTC

Return-Path: <superuser@gmail.com>
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 D00AD13118F for <dnsop@ietfa.amsl.com>; Wed, 18 Jul 2018 08:37:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Zb1llV_uFR-H for <dnsop@ietfa.amsl.com>; Wed, 18 Jul 2018 08:37:17 -0700 (PDT)
Received: from mail-lj1-x22b.google.com (mail-lj1-x22b.google.com [IPv6:2a00:1450:4864:20::22b]) (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 AF036131203 for <dnsop@ietf.org>; Wed, 18 Jul 2018 08:37:07 -0700 (PDT)
Received: by mail-lj1-x22b.google.com with SMTP id s12-v6so4509039ljj.0 for <dnsop@ietf.org>; Wed, 18 Jul 2018 08:37:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=LQN+Rv5k0X6YEAugJcWgX6yGCovdCVPIYP170Pvq+6I=; b=SQcUgaDw/phfTXESxNhwmZigGOmqlPMFBbk7Db0wQy9ekIIcd/ntUpuH24lEnHFtr8 AU8bonpTy2/ACacKBFdGd85GUGe5IKppYHEjp0C+ZnKk2gtZQTVlLyFMJiqp8mFUNohw Agj1vsigk4U9VDrvpT0xYUyEF9hr7B/2OvZDPTvtptA4lGMcuBSgKpnh5PMSSGgC8Tyn Vr+mrEfPiiXaTfsE0a/gTw45KannWZfgXewBKJGflgzgEWKthBrLXnPf+F922SRwihJ6 +65rtBzsBGxda/FBbk/XZRh8tGJ64HkGovC+NiQQslFFEsDr8/J5HEReDueQw1i2bYfv yaqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=LQN+Rv5k0X6YEAugJcWgX6yGCovdCVPIYP170Pvq+6I=; b=BYHLdLTOpTkGnb4wy0PbzBQRXcbPDQ/83GwgAEfOAZS2LngSGYs2DftIsyUFddJytX nnmEVapjEdgx7PYIOMOk0dGVncyHhbTE1QTuUQXoyw1kLsDXMCgsjGBzRANrfSeeISJS pXcsURac+ziNTPnD4RPSzLNEM7+w8p9m8T03M1PwTUeFKQiAShM47CW0UOqUmTQh7lhM YADGA2u/uneYZyd/KPX31TusGMuljjEgpnX2VMExOfwc7YKv3UNpwrW/DUADgALU2OJe nb1qoMvIHZuhiNlzr4OpLFsHerumztd0GvrapVjJdX9Hin8gBKa7kCLS/h8ARAjbQqyY t/Ww==
X-Gm-Message-State: AOUpUlGeOI5rAeD+vcvx2eX0zf5GDWAE5OfB5bkFpiKsJuO1FNR4f3yY qN9KPbqembJPHp5oChQzHXsjP4/TQtscF3Ydq3SoNw==
X-Google-Smtp-Source: AAOMgpdAZ+1jUuuE7hEPMpu9OuAFaLhTC8UFo0+WwvfptvSGdaEwcbzEM+sihIoCDUhTftHvUxBM2i7ePBHcCmfAK1s=
X-Received: by 2002:a2e:1dc8:: with SMTP id w69-v6mr5294739lje.110.1531928225741; Wed, 18 Jul 2018 08:37:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a2e:3a13:0:0:0:0:0 with HTTP; Wed, 18 Jul 2018 08:37:05 -0700 (PDT)
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Wed, 18 Jul 2018 11:37:05 -0400
Message-ID: <CAL0qLwaEYRprp8J81tAGzEc62kAHbMuM=xP81+wFhxTVDNs+_A@mail.gmail.com>
To: dnsop@ietf.org
Content-Type: multipart/alternative; boundary="000000000000b77f17057147d597"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/uqo1mwosNG-cRE_wNU5MNprYa3I>
Subject: [DNSOP] Review of draft-ietf-dnsop-attrleaf-fix
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.27
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, 18 Jul 2018 15:37:23 -0000

I've reviewed this document and it also looks like it's pretty much ready.
My suggestions here are also pretty minor:

As the other document, this one uses MUST without the RFC2119 boilerplate.

Section 3.2 replaces text in Section 4.1 of something, but I don't know
what; the prior paragraph refers to multiple other documents.  I suggest:
(a) clarify which document's 4.1 is being replaced, and (b) don't bother
including the original (replaced) text.

I believe Section 4 can include a note to the RFC Editor to remove it prior
to publication.

Section 5, as in the other document, is too terse.  I suggest summarizing
the fact that the only thing going on here is creating of IANA requirements
on future work, and updating old documents to reference those requirements.

-MSK