IETF Logo Mail Archive

Re: [v6ops] FW: ITU-T Recommendation ITU-T X.1037, Technical security guideline on deploying IPv6

Fernando Gont <fgont@si6networks.com> Sun, 09 June 2013 14:11 UTC

Return-Path: <fgont@si6networks.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3149821F9473 for <v6ops@ietfa.amsl.com>; Sun, 9 Jun 2013 07:11:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.626
X-Spam-Level:
X-Spam-Status: No, score=-1.626 tagged_above=-999 required=5 tests=[AWL=0.373, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VaVDCJOxIfqk for <v6ops@ietfa.amsl.com>; Sun, 9 Jun 2013 07:11:14 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 2CC3621F9362 for <v6ops@ietf.org>; Sun, 9 Jun 2013 07:11:13 -0700 (PDT)
Received: from [186.134.37.222] (helo=[192.168.0.6]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UlgKr-0002fG-Pk; Sun, 09 Jun 2013 16:11:10 +0200
Message-ID: <51B47E92.1090107@si6networks.com>
Date: Sun, 09 Jun 2013 15:09:38 +0200
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Nick Hilliard <nick@inex.ie>
References: <EF35EE4B92789843B1DECBC0E245586411523724@eusaamb102.ericsson.se> <51B2BB07.2040208@gmail.com> <51B45718.7030907@inex.ie>
In-Reply-To: <51B45718.7030907@inex.ie>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, Scott Mansfield <scott.mansfield@ericsson.com>
Subject: Re: [v6ops] FW: ITU-T Recommendation ITU-T X.1037, Technical security guideline on deploying IPv6
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Jun 2013 14:11:15 -0000

On 06/09/2013 12:21 PM, Nick Hilliard wrote:
> 
> Would there be any value in writing an ID in v6ops to cover this topic more
> comprehensively?  I guess it would go out of date very quickly.

We've doing that in separate documents, and different wgs (6man, opsec,
and v6ops). Most of the documents are based on the large IPv6 security
document I produced some time ago... and then published pieces of such
document as stand-alone documents, so that they would be easier to move
forward.

For example, the one for ND is here:
<http://tools.ietf.org/html/draft-gont-opsec-ipv6-nd-security> -- this
one being the largest.

And others can be found by searching my last name at
<https://www.rfc-editor.org/idsearch.html> an/or at:
<http://tools.ietf.org/id/gont?maxhits=100&key=date&dir=desc>.

Thanks!

Best regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492

v2.23.0 | Report a Bug | By Email