[saag] Fwd: Last Call: <draft-ietf-opsec-v6-21.txt> (Operational Security Considerations for IPv6 Networks) to Informational RFC

Benjamin Kaduk <kaduk@mit.edu> Wed, 13 November 2019 07:20 UTC

Return-Path: <kaduk@mit.edu>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 26E8F12088E for <saag@ietfa.amsl.com>; Tue, 12 Nov 2019 23:20:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 57SDWMOYhx08 for <saag@ietfa.amsl.com>; Tue, 12 Nov 2019 23:20:35 -0800 (PST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu []) (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 D3D81120886 for <saag@ietf.org>; Tue, 12 Nov 2019 23:20:33 -0800 (PST)
Received: from kduck.mit.edu ([]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id xAD7KToh028556 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <saag@ietf.org>; Wed, 13 Nov 2019 02:20:32 -0500
Date: Tue, 12 Nov 2019 23:20:29 -0800
From: Benjamin Kaduk <kaduk@mit.edu>
To: saag@ietf.org
Message-ID: <20191113072029.GU32847@kduck.mit.edu>
References: <157348692828.7549.5693363954495959926.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <157348692828.7549.5693363954495959926.idtracker@ietfa.amsl.com>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/pLyVJouWbaeU-Hrw6DSIVczVna4>
Subject: [saag] Fwd: Last Call: <draft-ietf-opsec-v6-21.txt> (Operational Security Considerations for IPv6 Networks) to Informational RFC
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Nov 2019 07:20:37 -0000

Hi all,

A lot of different topics in here, but might be worth a skim to see if
there's anything related to your respective expertise...


On Mon, Nov 11, 2019 at 07:42:08AM -0800, The IESG wrote:
> The IESG has received a request from the Operational Security Capabilities
> for IP Network Infrastructure WG (opsec) to consider the following document:
> - 'Operational Security Considerations for IPv6 Networks'
>   <draft-ietf-opsec-v6-21.txt> as Informational RFC
> The IESG plans to make a decision in the next few weeks, and solicits final
> comments on this action. Please send substantive comments to the
> last-call@ietf.org mailing lists by 2019-12-02. Exceptionally, comments may
> be sent to iesg@ietf.org instead. In either case, please retain the beginning
> of the Subject line to allow automated sorting.
> Abstract
>    Knowledge and experience on how to operate IPv4 securely is
>    available: whether it is the Internet or an enterprise internal
>    network.  However, IPv6 presents some new security challenges.  RFC
>    4942 describes the security issues in the protocol but network
>    managers also need a more practical, operations-minded document to
>    enumerate advantages and/or disadvantages of certain choices.
>    This document analyzes the operational security issues in several
>    places of a network (enterprises, service providers and residential
>    users) and proposes technical and procedural mitigations techniques.
>    Some very specific places of a network such as the Internet of Things
>    are not discussed in this document.
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-opsec-v6/
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-opsec-v6/ballot/
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce