IETF Logo Mail Archive

[v6ops] New version of draft-chkpvc-enterprise-incremental-ipv6-01

"Eric Vyncke (evyncke)" <evyncke@cisco.com> Wed, 18 July 2012 14:11 UTC

Return-Path: <evyncke@cisco.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 AD20C21F878A for <v6ops@ietfa.amsl.com>; Wed, 18 Jul 2012 07:11:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.12
X-Spam-Level:
X-Spam-Status: No, score=-10.12 tagged_above=-999 required=5 tests=[AWL=-0.479, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, SARE_SUB_6CONS_WORD=0.356]
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 xM9ajOx0Oedl for <v6ops@ietfa.amsl.com>; Wed, 18 Jul 2012 07:11:38 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 776C921F8789 for <v6ops@ietf.org>; Wed, 18 Jul 2012 07:11:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=evyncke@cisco.com; l=8199; q=dns/txt; s=iport; t=1342620749; x=1343830349; h=from:to:cc:subject:date:message-id:mime-version; bh=dLKGm4qMLJfUkNxg/Ozgc41UTRAQq49DRn/SJ0Ec5Xo=; b=BZOzLBF8E6AXrnLJgmNPPLDYEKPH70AwblRUDvL3oTs+eNUCtDRQ5C07 zulPCCie3Pn7RR3d5zG/MK+yGYvH0lB/lHbQirEHok98AD7ZGbdzrmi/K kZ8/CjEX6+rR3xYEu9ngZo1Qu8FN5LQ/vpu7Fm/BD0wkXIfZDjKzenx6O Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ak4FAH7DBlCtJXHA/2dsb2JhbABFgkqtbwGJAYEHgiIBBBIBGkcFEgEqViYBBA4NGodrC51uoBeRL2ADiBiOP40QgWaCXw
X-IronPort-AV: E=Sophos; i="4.77,610,1336348800"; d="scan'208,217"; a="103014657"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-2.cisco.com with ESMTP; 18 Jul 2012 14:12:28 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id q6IECSGs005466 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 18 Jul 2012 14:12:28 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.178]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.02.0298.004; Wed, 18 Jul 2012 09:12:28 -0500
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: "v6ops@ietf.org WG" <v6ops@ietf.org>
Thread-Topic: New version of draft-chkpvc-enterprise-incremental-ipv6-01
Thread-Index: Ac1k71m1KkcMdiAsRzSbD5XMS6Agrw==
Date: Wed, 18 Jul 2012 14:12:27 +0000
Message-ID: <97EB7536A2B2C549846804BBF3FD47E1050E25@xmb-aln-x02.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.55.185.70]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19048.005
x-tm-as-result: No--35.838500-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: multipart/alternative; boundary="_000_97EB7536A2B2C549846804BBF3FD47E1050E25xmbalnx02ciscocom_"
MIME-Version: 1.0
Cc: "lee.howard@twcable.com" <lee.howard@twcable.com>, "victor.kuarsingh@rci.rogers.com" <victor.kuarsingh@rci.rogers.com>
Subject: [v6ops] New version of draft-chkpvc-enterprise-incremental-ipv6-01
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: Wed, 18 Jul 2012 14:11:39 -0000

We have updated our I-D about IPv6 enterprise deployment based on the few comments that we have received:
http://tools.ietf.org/html/draft-chkpvc-enterprise-incremental-ipv6-01 (abstract below)

The chairmen were kind enough to put us on the agenda on Friday even with a filename which does not include v6ops.

Thanks in advance for any comment,

-éric, Yanick, KK, Tim, Lee & Victor

Enterprise network administrators worldwide are in various stages of
   preparing for or deploying IPv6 into their networks.  The
   administrators face different challenges than operators of Internet
   access providers, and have reasons for different priorities.  The
   overall problem for many administrators will be to offer Internet-
   facing services over IPv6, while continuing to support IPv4, and
   while introducing IPv6 access within the enterprise IT network.  The
   overall transition will take most networks from an IPv4-only
   environment to a dual stack network environment and potentially an
   IPv6-only operating mode.  This document helps provide a framework
   for enterprise network architects or administrators who may be faced
   with many of these challenges as they consider their IPv6 support
   strategies.

v2.23.0 | Report a Bug | By Email