Re: [OPSEC] New Rev of draft-gont-opsec-ipv6-implications-on-ipv4-nets-02.txt

"Gunter Van de Velde (gvandeve)" <gvandeve@cisco.com> Tue, 21 August 2012 11:27 UTC

Return-Path: <gvandeve@cisco.com>
X-Original-To: opsec@ietfa.amsl.com
Delivered-To: opsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7085421F8682 for <opsec@ietfa.amsl.com>; Tue, 21 Aug 2012 04:27:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.433
X-Spam-Level:
X-Spam-Status: No, score=-10.433 tagged_above=-999 required=5 tests=[AWL=0.166, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CECJcKLVJfC8 for <opsec@ietfa.amsl.com>; Tue, 21 Aug 2012 04:27:18 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id A8AB321F856F for <opsec@ietf.org>; Tue, 21 Aug 2012 04:27:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=gvandeve@cisco.com; l=2343; q=dns/txt; s=iport; t=1345548438; x=1346758038; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=Pxw2Hx31EDsEIRDwufjP3b+BgrTDUoovDTE7JzvUgeg=; b=lo4Q0WzNUyDB7gSV7C75Xy51l9y4B+rXvZZ4D1WhN6o7JtvJ9dXEN6a8 KCj17JiAu6V0TU7nlLnWnbrw9brPY9+AsK46mwa/WTuqdKoMw90rgwUr8 29emXY/FmxT6+/FYo/kTSOdMnXbSFkM7Iygz9RPVNDYVNslH6z7YRoS1m I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EADZwM1CtJV2Y/2dsb2JhbABFul+BB4IgAQEBBAEBAQ8BCh00CwwEAgEIEQMBAQELFAkHJwsUCQgCBAENBQgBGYdrC5h/oDWLCIY8YAOWZo0ZgWaCYQ
X-IronPort-AV: E=Sophos;i="4.77,802,1336348800"; d="scan'208";a="113713924"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-6.cisco.com with ESMTP; 21 Aug 2012 11:27:18 +0000
Received: from xhc-aln-x14.cisco.com (xhc-aln-x14.cisco.com [173.36.12.88]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id q7LBRIsY025655 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 21 Aug 2012 11:27:18 GMT
Received: from xmb-aln-x12.cisco.com ([169.254.7.122]) by xhc-aln-x14.cisco.com ([173.36.12.88]) with mapi id 14.02.0283.003; Tue, 21 Aug 2012 06:27:17 -0500
From: "Gunter Van de Velde (gvandeve)" <gvandeve@cisco.com>
To: Fernando Gont <fernando@gont.com.ar>, "'opsec@ietf.org'" <opsec@ietf.org>
Thread-Topic: [OPSEC] New Rev of draft-gont-opsec-ipv6-implications-on-ipv4-nets-02.txt
Thread-Index: AQHNf47wjfVm1Ww1L02M21WjyxEjMZdkHuYQ
Date: Tue, 21 Aug 2012 11:27:17 +0000
Message-ID: <67832B1175062E48926BF3CB27C49B24077F08@xmb-aln-x12.cisco.com>
References: <20120821111757.8846.20372.idtracker@ietfa.amsl.com> <50336EBA.1080105@gont.com.ar>
In-Reply-To: <50336EBA.1080105@gont.com.ar>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.61.100.21]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19128.004
x-tm-as-result: No--37.617400-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: opsec chairs <opsec-chairs@tools.ietf.org>
Subject: Re: [OPSEC] New Rev of draft-gont-opsec-ipv6-implications-on-ipv4-nets-02.txt
X-BeenThere: opsec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: opsec wg mailing list <opsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsec>, <mailto:opsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsec>
List-Post: <mailto:opsec@ietf.org>
List-Help: <mailto:opsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsec>, <mailto:opsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Aug 2012 11:27:19 -0000

With this note the OPSEC chairs would like to probe for WG adoption.

During the cause of events and discussion on the WG mailing list, this document has been seen as valuable for the WG to adopt as work item.

2 questions need to be addressed:

1. Please find 2 weeks to provide feedback on this draft. Please say yes/no on WG adoption. 
2. Should this be BCP or Informational track

G/

-----Original Message-----
From: opsec-bounces@ietf.org [mailto:opsec-bounces@ietf.org] On Behalf Of Fernando Gont
Sent: 21 August 2012 13:19
To: 'opsec@ietf.org'
Cc: opsec chairs
Subject: [OPSEC] New Rev of draft-gont-opsec-ipv6-implications-on-ipv4-nets-02.txt

Folks,

FYI, I have posted a new rev of the aforementioned I-D, which is meant to address the feedback I have received so far.

This version should be ready for the formal wg call for adoption-.

Thanks!

Best regards,
Fernando




-------- Original Message --------
Subject: New Version Notification for
draft-gont-opsec-ipv6-implications-on-ipv4-nets-02.txt
Date: Tue, 21 Aug 2012 04:17:57 -0700
From: internet-drafts@ietf.org
To: fernando@gont.com.ar


A new version of I-D, draft-gont-opsec-ipv6-implications-on-ipv4-nets-02.txt
has been successfully submitted by Fernando Gont and posted to the IETF repository.

Filename:	 draft-gont-opsec-ipv6-implications-on-ipv4-nets
Revision:	 02
Title:		 Security Implications of IPv6 on IPv4 Networks
Creation date:	 2012-08-21
WG ID:		 Individual Submission
Number of pages: 18
URL:
http://www.ietf.org/internet-drafts/draft-gont-opsec-ipv6-implications-on-ipv4-nets-02.txt
Status:
http://datatracker.ietf.org/doc/draft-gont-opsec-ipv6-implications-on-ipv4-nets
Htmlized:
http://tools.ietf.org/html/draft-gont-opsec-ipv6-implications-on-ipv4-nets-02
Diff:
http://www.ietf.org/rfcdiff?url2=draft-gont-opsec-ipv6-implications-on-ipv4-nets-02

Abstract:
   This document discusses the security implications of native IPv6
   support and IPv6 transition/co-existence technologies on "IPv4-only"
   networks, and describes possible mitigations for the aforementioned
   issues.





The IETF Secretariat




_______________________________________________
OPSEC mailing list
OPSEC@ietf.org
https://www.ietf.org/mailman/listinfo/opsec