[Gen-art] Genart last call review of draft-ietf-spring-oam-usecase-06

Pete Resnick <presnick@qti.qualcomm.com> Wed, 28 June 2017 18:31 UTC

Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A75712EC75; Wed, 28 Jun 2017 11:31:24 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Pete Resnick <presnick@qti.qualcomm.com>
To: <gen-art@ietf.org>
Cc: spring@ietf.org, ietf@ietf.org, draft-ietf-spring-oam-usecase.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149867468440.7527.6305996146978005032@ietfa.amsl.com>
Date: Wed, 28 Jun 2017 11:31:24 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/LJeLVP1ACsDyQOYg7dZ6vHFEpY8>
Subject: [Gen-art] Genart last call review of draft-ietf-spring-oam-usecase-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jun 2017 18:31:24 -0000

Reviewer: Pete Resnick
Review result: Not Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at


Document: draft-ietf-spring-oam-usecase-06
Reviewer: Pete Resnick
Review Date: 2017-06-28
IETF LC End Date: 2017-06-30
IESG Telechat date: Not scheduled for a telechat

Summary: Not Ready for publication as Informational, but might be Ready for
publication as Proposed Standard

Major issues:

This is an admittedly unusual review. I have read through the entire document,
and the technical work seems fine, but is well beyond my technical expertise,
so I can't really comment on the technical correctness. However, it is
absolutely clear to me that this is *not* a "use case" document at all and I
don't think it's appropriate as an Informational document. This is clearly a
*specification* of a path monitoring system. It gives guidances as to required,
recommended, and optional parameters, and specifies how to use different
protocol pieces. It is at the very least what RFC 2026 refers to as an
"Applicability Statement (AS)" (see RFC 2026, sec. 3.2). It *might* be a BCP,
but it is not strictly giving "common guidelines for policies and operations"
(2026, sec. 5), so I don't really think that's right, and instead this should
be offered for Proposed Standard. Either way, I think Informational is not
correct. Importantly, I think there is a good likelihood that this document has
not received the appropriate amount of review; people tend to ignore
Informational "use case" documents, and there have been no Last Call comments
beyond Joel's RTG Area Review. Even in IESG review, an Informational document
only takes the sponsoring AD to approve; every other AD can summarily ignore
the document, or even ballot ABSTAIN, and the document will still be published
(though that does not normally happen). This document should have much more
than that level of review. I strongly recommend to the WG and AD that this
document be withdrawn as an Informational document and resubmitted for Proposed
Standard and have that level of review and scrutiny applied to it.

Minor issues:


Nits/editorial comments:

This document refers to RFC 4379, which has been obsoleted by RFC 8029. It
seems like the references should be updated.