[core] Opsdir telechat review of draft-ietf-core-cocoa-02
Scott Bradner <sob@sobco.com> Wed, 21 February 2018 19:21 UTC
Return-Path: <sob@sobco.com>
X-Original-To: core@ietf.org
Delivered-To: core@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 34B7F12DA01; Wed, 21 Feb 2018 11:21:29 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Scott Bradner <sob@sobco.com>
To: ops-dir@ietf.org
Cc: ietf@ietf.org, core@ietf.org, draft-ietf-core-cocoa.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.72.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151924088919.28302.2725971304170450273@ietfa.amsl.com>
Date: Wed, 21 Feb 2018 11:21:29 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/F_UXXUHTcgvPsRxRwgyMiV5qV2s>
Subject: [core] Opsdir telechat review of draft-ietf-core-cocoa-02
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Feb 2018 19:21:29 -0000
Reviewer: Scott Bradner Review result: Serious Issues I have not reviewed this document in any detail but since it makes no reference to RFC 5033 (Specifying New Congestion Control Algorithms) I consider it to be fatally incomplete RFC 5033 is a BCP which in my opinion must (MUST?) be followed in any document that purports to define a new congestion protocol, even at the informational level.
- [core] Opsdir telechat review of draft-ietf-core-… Scott Bradner