[Iot-directorate] Iotdir telechat review of draft-ietf-taps-transport-security-11

Mohit Sethi via Datatracker <noreply@ietf.org> Wed, 01 April 2020 10:44 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: iot-directorate@ietf.org
Delivered-To: iot-directorate@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B37843A0800; Wed, 1 Apr 2020 03:44:52 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Mohit Sethi via Datatracker <noreply@ietf.org>
To: iot-directorate@ietf.org
Cc: taps@ietf.org, last-call@ietf.org, draft-ietf-taps-transport-security.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.123.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <158573789268.30918.7424398883276797270@ietfa.amsl.com>
Reply-To: Mohit Sethi <mohit.m.sethi@ericsson.com>
Date: Wed, 01 Apr 2020 03:44:52 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/iot-directorate/xTVOvQ7kI78sDPZQuVsTvGB2x0s>
Subject: [Iot-directorate] Iotdir telechat review of draft-ietf-taps-transport-security-11
X-BeenThere: iot-directorate@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Mailing list for the IoT Directorate Members <iot-directorate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iot-directorate>, <mailto:iot-directorate-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iot-directorate/>
List-Post: <mailto:iot-directorate@ietf.org>
List-Help: <mailto:iot-directorate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iot-directorate>, <mailto:iot-directorate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2020 10:44:53 -0000

Reviewer: Mohit Sethi
Review result: Ready with Nits

This document provides a summary of common security protocols. It then
discusses the interfaces that exist between applications and security protocols
as well as security protocols and transport services.

Major issues: The document header says that this document is about interfaces
between security protocols and transport services. Yet, later on, I find that
the document is also discussing the interfaces between security protocols and
applications. Perhaps you could add 'applications' to the title -> 'Interaction
Between Applications, Security Protocols, and Transport Services'

Editorial issues:
- Instead of saying 'This protocol obsoletes TCP MD5 "signature" options', can
we say 'TCP-AO obsoletes....' to avoid confusion of what is 'this' - Please
expand 'and IPsec AH [RFC4302]' -> IP Authentication Header - Are you talking
about cryptographic agility here 'security protocols: confidentiality, privacy
protections, and agility.' ? - Consider changing 'interface surface exposed '->
interface exposed by'. Otherwise it sounds too similar to attack surface
exposed. - Expand EAP and reference RFC3748. - Perhaps you could say that
Source Address Validation (SAV) to prevent DoS is relevant for protocols that
use unreliable transport?