[secdir] Secdir Review of draft-ietf-tcpm-tcp-rfc4614bis-05

Matthew Lepinski <mlepinski.ietf@gmail.com> Mon, 23 June 2014 02:27 UTC

Return-Path: <mlepinski.ietf@gmail.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DB921B2876; Sun, 22 Jun 2014 19:27:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yAC3IWkJnGS9; Sun, 22 Jun 2014 19:27:56 -0700 (PDT)
Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD69A1B2861; Sun, 22 Jun 2014 19:27:55 -0700 (PDT)
Received: by mail-wi0-f182.google.com with SMTP id bs8so3277385wib.3 for <multiple recipients>; Sun, 22 Jun 2014 19:27:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=3uxG3KKUwh4GrJjom2LwwpRU21ndD0mNR3X37R2S7cQ=; b=IIzhh4s4feDKdN0JJU7XQPVxTk5GZlkk5HNjUiDb0TwLBnXPCNU3Vh3A80xpTa3PBB uUSD26+VfVFrj6oM6WLDxUFs4QL46noRHncfRk9XzqnguaCy4p3GJZmlxKmIPRhb1dHI awRF4dY6LO2cJ8SWqcBM85WfE8ZK7AkvaBCq0Grl+3TZWh4sPib/hZ6zaoH6Sq+vj/bo B/sLIS08TbJEVo/mwWUdsRDCq5TvN/unEQ20V4tgSS3RRs3Zl5RRCqqjYbNC6NsHlAmg 6Hc2C2AOVoan9hDaIxMx1RHvhVbRWt4sV3xlozV+0Axdr2C5tOxkQivVJ9wVfOe9Ouzz rJAg==
MIME-Version: 1.0
X-Received: by 10.180.37.42 with SMTP id v10mr22177557wij.43.1403490474304; Sun, 22 Jun 2014 19:27:54 -0700 (PDT)
Received: by 10.216.191.1 with HTTP; Sun, 22 Jun 2014 19:27:54 -0700 (PDT)
Date: Sun, 22 Jun 2014 22:27:54 -0400
Message-ID: <CANTg3aCSKMZBuzpFqzjMzsOzLpvyBZk1dakDVz7qmADxVY5JtA@mail.gmail.com>
From: Matthew Lepinski <mlepinski.ietf@gmail.com>
To: draft-ietf-tcpm-tcp-rfc4614bis.all@tools.ietf.org, "secdir@ietf.org" <secdir@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Content-Type: multipart/alternative; boundary=e89a8f6473c72aa9f304fc779762
Archived-At: http://mailarchive.ietf.org/arch/msg/secdir/8a7SQqiIatU4V6yx_l4Dzs3R2WY
Subject: [secdir] Secdir Review of draft-ietf-tcpm-tcp-rfc4614bis-05
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jun 2014 02:28:00 -0000

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.

This draft is an update to the Roadmap for TCP specifications (RFC 4614).
The roadmap provides a pointer (along with a brief abstract) to key TCP
specifications. The update to the roadmap makes small changes to the
organization of the roadmap and (more importantly) adds pointers to a
number of more recent TCP-related specifications.

This document appears to be ready for publication. I found no problems with
this document.

As a collection of pointers to other specifications, this document does not
introduce any new security concerns. Security issues related to TCP are
addressed in individual specifications referenced in this roadmap. (Indeed,
one of the changes made in this update to the roadmap is to include more
pointers to documents related to TCP security, such as the specification
for TCP-AO.)