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

Dave Dugal <dave@juniper.net> Tue, 04 September 2012 16:27 UTC

Return-Path: <dave@juniper.net>
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 D671B21F8449 for <opsec@ietfa.amsl.com>; Tue, 4 Sep 2012 09:27:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 elfn4nq3GoQo for <opsec@ietfa.amsl.com>; Tue, 4 Sep 2012 09:27:24 -0700 (PDT)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163]) by ietfa.amsl.com (Postfix) with ESMTP id 997B121F8446 for <opsec@ietf.org>; Tue, 4 Sep 2012 09:27:20 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP ID DSNKUEYr5aLuwkXOrTzQokGnEnBbQBjqfYl9@postini.com; Tue, 04 Sep 2012 09:27:24 PDT
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 4 Sep 2012 09:24:26 -0700
Received: from [172.28.131.163] (172.28.131.163) by p-emfe01-wf.jnpr.net (172.28.145.24) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 4 Sep 2012 12:24:24 -0400
Message-ID: <50462B36.4010506@juniper.net>
Date: Tue, 04 Sep 2012 12:24:22 -0400
From: Dave Dugal <dave@juniper.net>
Organization: Juniper Networks, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: "Gunter Van de Velde (gvandeve)" <gvandeve@cisco.com>
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> <68EFACB32CF4464298EA2779B058889D0A1C71E4@PDDCWMBXEX503.ctl.intranet>
In-Reply-To: <68EFACB32CF4464298EA2779B058889D0A1C71E4@PDDCWMBXEX503.ctl.intranet>
X-Enigmail-Version: 1.4.4
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: "'opsec@ietf.org'" <opsec@ietf.org>, opsec chairs <opsec-chairs@tools.ietf.org>, Fernando Gont <fernando@gont.com.ar>
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 16:27:25 -0000

Please add my full support for adopting
draft-gont-opsec-ipv6-implications-on-ipv4-nets as an OPSEC WG document.

While this has enough merit to become a BCP, the current Intended Status
of Informational would be my preference.

- Dave

On 9/4/2012 11:35 AM, Smith, Donald <Donald.Smith@CenturyLink.com>
proclaimed ...
> 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
> _______________________________________________
> OPSEC mailing list
> OPSEC@ietf.org
> https://www.ietf.org/mailman/listinfo/opsec
> .
>