Secdir last call review of draft-ietf-core-senml-etch-05

Christian Huitema via Datatracker <noreply@ietf.org> Tue, 03 September 2019 19:36 UTC

Return-Path: <noreply@ietf.org>
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 17E901200D5; Tue, 3 Sep 2019 12:36:52 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Christian Huitema via Datatracker <noreply@ietf.org>
To: secdir@ietf.org
Cc: ietf@ietf.org, core@ietf.org, draft-ietf-core-senml-etch.all@ietf.org
Subject: Secdir last call review of draft-ietf-core-senml-etch-05
X-Test-IDTracker: no
X-IETF-IDTracker: 6.100.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Christian Huitema <huitema@huitema.net>
Message-ID: <156753941202.21156.13374047126124906978@ietfa.amsl.com>
Date: Tue, 03 Sep 2019 12:36:52 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9pHolC9dd-cy3XIKgknveRoUhjU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 03 Sep 2019 19:36:52 -0000

Reviewer: Christian Huitema
Review result: Ready

I have reviewed this document as part of the security directorate's ongoing
effort to review all IETF documents being processed by the IESG.  These
comments were written primarily for the benefit of the security area directors.
 Document editors and WG chairs should treat these comments just like any other
last call comments.

The draft draft-ietf-core-senml-etch-05 defines new media types for the CoAP
iPATCH, PATCH, and FETCH methods for resources represented with the SenML data
model defined in RFC 8428.

The security considerations appropriately refer to the general considerations
of SenML.

The document is ready.