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

"Panos Kampanakis (pkampana)" <pkampana@cisco.com> Sun, 02 September 2012 22:33 UTC

Return-Path: <pkampana@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 262C421F84F6 for <opsec@ietfa.amsl.com>; Sun, 2 Sep 2012 15:33:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[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 oDL8O9XYkc6M for <opsec@ietfa.amsl.com>; Sun, 2 Sep 2012 15:33:55 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 5E7D921F84CF for <opsec@ietf.org>; Sun, 2 Sep 2012 15:33:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkampana@cisco.com; l=2958; q=dns/txt; s=iport; t=1346625235; x=1347834835; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=JOPxPxWiBoELUIUujBqAp080BAowlI++zYnb8fAb5U0=; b=ksFDavmkgsD1dY8VcF3cv1wwy2v0aHhGo1DxQOgXKwq6fI0Ban6GLeSf gR6x8bfgEjepvN2C3rg0R5QGLgTgb5G6ZPgyqVtxneeJxP3WM8hTZ1GAZ zurNirzqCOQh7SIbdnesLkMFI9mjA4LJPpWxc+rZH9Zgk86vuGoKenXlC E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAAbeQ1CtJV2Z/2dsb2JhbABFuyGBB4IgAQEBBAEBAQ8BCh00CwwEAgEIEQMBAQELFAkHJwsUCQgCBAENBQgBGYdrC5p3nw+LDYZDYAOWbY0fgWeCYw
X-IronPort-AV: E=Sophos;i="4.80,356,1344211200"; d="scan'208";a="117631339"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-5.cisco.com with ESMTP; 02 Sep 2012 22:33:54 +0000
Received: from xhc-aln-x07.cisco.com (xhc-aln-x07.cisco.com [173.36.12.81]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id q82MXsxa015896 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 2 Sep 2012 22:33:54 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.216]) by xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.02.0298.004; Sun, 2 Sep 2012 17:33:54 -0500
From: "Panos Kampanakis (pkampana)" <pkampana@cisco.com>
To: "Gunter Van de Velde (gvandeve)" <gvandeve@cisco.com>, 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: AQHNf4/xMv9kGvkdN06QC8tsypxtgZd3td1A
Date: Sun, 02 Sep 2012 22:33:53 +0000
Message-ID: <1C9F17D1873AFA47A969C4DD98F98A75062E81@xmb-rcd-x10.cisco.com>
References: <20120821111757.8846.20372.idtracker@ietfa.amsl.com> <50336EBA.1080105@gont.com.ar> <67832B1175062E48926BF3CB27C49B24077F08@xmb-aln-x12.cisco.com>
In-Reply-To: <67832B1175062E48926BF3CB27C49B24077F08@xmb-aln-x12.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.116.63.179]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19158.001
x-tm-as-result: No--39.527400-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: Sun, 02 Sep 2012 22:33:56 -0000

1. Yes. I had provided my thouhgts/feedback for Fernando in previous emails.
2. Informational (had expressed my reasoning in previous thread)

Panos


-----Original Message-----
From: opsec-bounces@ietf.org [mailto:opsec-bounces@ietf.org] On Behalf Of Gunter Van de Velde (gvandeve)
Sent: Tuesday, August 21, 2012 7:27 AM
To: Fernando Gont; 'opsec@ietf.org'
Cc: opsec chairs
Subject: Re: [OPSEC] New Rev of draft-gont-opsec-ipv6-implications-on-ipv4-nets-02.txt

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
_______________________________________________
OPSEC mailing list
OPSEC@ietf.org
https://www.ietf.org/mailman/listinfo/opsec