[secdir] Secdir last call review of draft-ietf-sunset4-ipv6-ietf-01
<Steve.Hanna@infineon.com> Sat, 07 October 2017 15:48 UTC
Return-Path: <steve.hanna@infineon.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B3A613495E; Sat, 7 Oct 2017 08:48:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.6
X-Spam-Level:
X-Spam-Status: No, score=-1.6 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=infineon.com
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 ss6Prf1pJedV; Sat, 7 Oct 2017 08:48:46 -0700 (PDT)
Received: from smtp11.infineon.com (smtp11.infineon.com [IPv6:2a00:18f0:1e00:4::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E00113495C; Sat, 7 Oct 2017 08:48:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=infineon.com; i=@infineon.com; q=dns/txt; s=IFXMAIL; t=1507391326; x=1538927326; h=from:to:subject:date:message-id:mime-version; bh=Brhbj9/nX+YmWO00BGW2zrdrsOBiZQtMOD+Br5ZsIS8=; b=JgJRJOx4KSunkHf/Lv/nzDi2/tyBeDcTODiutdik9yfRVq4nri1E9Qp4 HXn62qb6U+IZYezwSUISrIQYJ2m7zvsTVidIy+UNUdTs3OlwCHtAmxg5j inVAdB/+vr0m2+K6P0lU08BYjWu3FdU/z6ZXuwYDmbEuCoUsHP0BiZzWm s=;
X-SBRS: None
Received: from unknown (HELO mucxv003.muc.infineon.com) ([172.23.11.20]) by smtp11.infineon.com with ESMTP/TLS/AES256-GCM-SHA384; 07 Oct 2017 17:48:43 +0200
Received: from MUCSE706.infineon.com (mucse706.infineon.com [172.23.7.80]) by mucxv003.muc.infineon.com (Postfix) with ESMTPS; Sat, 7 Oct 2017 17:48:43 +0200 (CEST)
Received: from MUCSE703.infineon.com (172.23.7.73) by MUCSE706.infineon.com (172.23.7.80) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.669.32; Sat, 7 Oct 2017 17:48:43 +0200
Received: from MUCSE707.infineon.com (172.23.7.81) by MUCSE703.infineon.com (172.23.7.73) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.669.32; Sat, 7 Oct 2017 17:48:43 +0200
Received: from MUCSE707.infineon.com ([172.23.106.27]) by MUCSE707.infineon.com ([172.23.106.27]) with mapi id 15.01.0669.032; Sat, 7 Oct 2017 17:48:42 +0200
From: Steve.Hanna@infineon.com
To: secdir@ietf.org, iesg@ietf.org, draft-ietf-sunset4-ipv6-ietf.all@ietf.org
Thread-Topic: Secdir last call review of draft-ietf-sunset4-ipv6-ietf-01
Thread-Index: AdM/ghbQ8KSz/K3jTp+5m7DVA0m3Xg==
Date: Sat, 07 Oct 2017 15:48:42 +0000
Message-ID: <bd0f24bfca544357af0d76eec70ed462@infineon.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.23.8.247]
Content-Type: multipart/alternative; boundary="_000_bd0f24bfca544357af0d76eec70ed462infineoncom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/cdHDgRHRT1JSA4jQ-xRPMtQ5uBw>
Subject: [secdir] Secdir last call review of draft-ietf-sunset4-ipv6-ietf-01
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.22
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: <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: Sat, 07 Oct 2017 15:48:47 -0000
Reviewer: Steve Hanna Review result: Ready This document states that the IETF will stop working on IPv4, with certain exceptions. While this document is controversial and concerns have been expressed regarding the wisdom of adopting it, I don't see any security concerns related to adopting it. In fact, the document clearly states that "the IETF needs to continue to update IPv4-only protocols and features for vital operational or security issues." Therefore, I don't foresee any security issues related to adopting the document.