[secdir] Secdir last call review of draft-ietf-dhc-dhcp4o6-saddr-opt-04

Brian Weis <bew@cisco.com> Wed, 19 September 2018 23:57 UTC

Return-Path: <bew@cisco.com>
X-Original-To: secdir@ietf.org
Delivered-To: secdir@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 98BC1130DFF; Wed, 19 Sep 2018 16:57:24 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Brian Weis <bew@cisco.com>
To: <secdir@ietf.org>
Cc: draft-ietf-dhc-dhcp4o6-saddr-opt.all@ietf.org, dhcwg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.84.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <153740144458.21482.13412260727597192650@ietfa.amsl.com>
Date: Wed, 19 Sep 2018 16:57:24 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/MAEIkLJ3ThtOzBbkJ_zl0Kg2OUY>
Subject: [secdir] Secdir last call review of draft-ietf-dhc-dhcp4o6-saddr-opt-04
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 19 Sep 2018 23:57:25 -0000

Reviewer: Brian Weis
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

This document provides a new DHCPv4 option to enables a DHCP 4o6 client to
request binding of its DHCPv4 and DHCPv6 addresses in a Softwire. The security
considerations section states that the security considerations of DHCP 4o6 are
applicable to this draft, and I agree. I do not see any need for text beyond
what is already written. I believe it is Ready to publish.