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

"Smith, Donald" <Donald.Smith@CenturyLink.com> Tue, 04 September 2012 15:36 UTC

Return-Path: <Donald.Smith@CenturyLink.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 76BD621F8569 for <opsec@ietfa.amsl.com>; Tue, 4 Sep 2012 08:36:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 XszhER1SqEHI for <opsec@ietfa.amsl.com>; Tue, 4 Sep 2012 08:36:17 -0700 (PDT)
Received: from suomp64i.qwest.com (suomp64i.qwest.com [155.70.16.237]) by ietfa.amsl.com (Postfix) with ESMTP id B9B9521F865B for <opsec@ietf.org>; Tue, 4 Sep 2012 08:36:14 -0700 (PDT)
Received: from lxdenvmpc030.qintra.com (lxdenvmpc030.qintra.com [10.1.51.30]) by suomp64i.qwest.com (8.14.4/8.14.4) with ESMTP id q84Fa971013768 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 4 Sep 2012 10:36:09 -0500 (CDT)
Received: from lxdenvmpc030.qintra.com (unknown [127.0.0.1]) by IMSA (Postfix) with ESMTP id C08831E0085; Tue, 4 Sep 2012 09:35:51 -0600 (MDT)
Received: from sudnp796.qintra.com (unknown [151.119.91.93]) by lxdenvmpc030.qintra.com (Postfix) with ESMTP id A48761E0077; Tue, 4 Sep 2012 09:35:51 -0600 (MDT)
Received: from sudnp796.qintra.com (localhost [127.0.0.1]) by sudnp796.qintra.com (8.14.4/8.14.4) with ESMTP id q84FZpup022953; Tue, 4 Sep 2012 09:35:51 -0600 (MDT)
Received: from vddcwhubex501.ctl.intranet (vddcwhubex501.qintra.com [151.119.128.28]) by sudnp796.qintra.com (8.14.4/8.14.4) with ESMTP id q84FZoHj022950 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 4 Sep 2012 09:35:51 -0600 (MDT)
Received: from PDDCWMBXEX503.ctl.intranet ([fe80::9033:ef22:df02:32a9]) by vddcwhubex501.ctl.intranet ([2002:9777:801c::9777:801c]) with mapi id 14.02.0283.003; Tue, 4 Sep 2012 09:35:51 -0600
From: "Smith, Donald" <Donald.Smith@CenturyLink.com>
To: "Panos Kampanakis (pkampana)" <pkampana@cisco.com>, "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: AQHNiVsNK9DruBX4gUS6BA5D5X09uJd6UImp
Date: Tue, 04 Sep 2012 15:35:50 +0000
Message-ID: <68EFACB32CF4464298EA2779B058889D0A1C71E4@PDDCWMBXEX503.ctl.intranet>
References: <20120821111757.8846.20372.idtracker@ietfa.amsl.com> <50336EBA.1080105@gont.com.ar> <67832B1175062E48926BF3CB27C49B24077F08@xmb-aln-x12.cisco.com>, <1C9F17D1873AFA47A969C4DD98F98A75062E81@xmb-rcd-x10.cisco.com>
In-Reply-To: <1C9F17D1873AFA47A969C4DD98F98A75062E81@xmb-rcd-x10.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [155.70.40.132]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
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, 04 Sep 2012 15:36:18 -0000

I too support this draft. I would be ok with bcp or informational. I lean a bit towards bcp but either category works as long as this reaches expected audiences.

So plus one for support and BCP but wouldn't object to info.


(coffee != sleep) & (!coffee == sleep)
 Donald.Smith@centurylink.com

________________________________________
From: opsec-bounces@ietf.org [opsec-bounces@ietf.org] on behalf of Panos Kampanakis (pkampana) [pkampana@cisco.com]
Sent: Sunday, September 02, 2012 4:33 PM
To: Gunter Van de Velde (gvandeve); Fernando Gont; 'opsec@ietf.org'
Cc: opsec chairs
Subject: Re: [OPSEC] New        Rev     of      draft-gont-opsec-ipv6-implications-on-ipv4-nets-02.txt

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