Opsdir telechat review of draft-baeuerle-netnews-cancel-lock-06

Joel Jaeggli <joelja@bogus.com> Fri, 06 October 2017 18:22 UTC

Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 31470134BF4; Fri, 6 Oct 2017 11:22:38 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Jaeggli <joelja@bogus.com>
To: ops-dir@ietf.org
Cc: draft-baeuerle-netnews-cancel-lock.all@ietf.org, ietf@ietf.org
Subject: Opsdir telechat review of draft-baeuerle-netnews-cancel-lock-06
X-Test-IDTracker: no
X-IETF-IDTracker: 6.63.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150731415816.13153.17649862649742679185@ietfa.amsl.com>
Date: Fri, 06 Oct 2017 11:22:38 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SrgkurKhwozYh5woInYKf4DWQpI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Oct 2017 18:22:38 -0000

Reviewer: Joel Jaeggli
Review result: Has Nits

I have reviewed draft-baeuerle-netnews-cancel-lock on behalf of the Operations
Directorate, for the IESG telechat review.

Modula the issues raised in the Genart Review (abnf validation) and security (
pre-image attack protection) I think this is a largely ready to go.

Under the best circumstances methods for article cancelation aren't necessarily
honored, are intended to  be employed by  a diverse group of end users
injecting netnews agents, or moderators, asserting various roles in managing
message removal and offer somewhere between poor to no assurance of efficacy.

To the extent that this methodology offers an improvement  to the set of
parties that chose to both employ it and honor it; it offers protection against
spurious removal requests from within the scope of their systems. the
protections offered by the MUST NOT in section 3.2 are weak as the message has
no integrity protection of substance and any such assurance that demand is
honored is a coordination problem between like-minded operators.