[sunset4] New draft: draft-kaliwoda-sunset4-dual-ipv6-coexist

"Arkadiusz Kaliwoda (akaliwod)" <akaliwod@cisco.com> Thu, 13 September 2012 22:04 UTC

Return-Path: <akaliwod@cisco.com>
X-Original-To: sunset4@ietfa.amsl.com
Delivered-To: sunset4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D87D121F867C for <sunset4@ietfa.amsl.com>; Thu, 13 Sep 2012 15:04:12 -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 kUhytovJ11Rs for <sunset4@ietfa.amsl.com>; Thu, 13 Sep 2012 15:04:12 -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 C959221F867A for <sunset4@ietf.org>; Thu, 13 Sep 2012 15:04:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4020; q=dns/txt; s=iport; t=1347573852; x=1348783452; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=DskLQoJgu3jI0apBTFvSRIKZFp0gmkcXulJ9xV6vD8k=; b=jqCIOPGlO/x5kvI8vvKsgE9Ldo4QPcFxyFtRbQRoubJxr2sWoqc1kozs Fwj/vKNxJyUpNFqwBXUNHEM1617nr++asDVZV/BxABFjNVFmYGAX0froK q2mY3CDjkdCUGp6njNxvIh25DxEk4pPOjnq6XWpI6FIHAaUCtoFfW4/2/ U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAAlXUlCtJXG9/2dsb2JhbABFhge1BG6BB4IgAQEBBBIBEBFRBgEZBAEBAwIGHQMCBDAUAQgJAQQTCAEZh2sLmheBKI0ZkwOBIYlvhSUyYAOWdI0kgWmCZoIX
X-IronPort-AV: E=Sophos;i="4.80,419,1344211200"; d="scan'208";a="121419255"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-5.cisco.com with ESMTP; 13 Sep 2012 22:04:06 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id q8DM46I1027661 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <sunset4@ietf.org>; Thu, 13 Sep 2012 22:04:06 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.159]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.02.0298.004; Thu, 13 Sep 2012 17:04:05 -0500
From: "Arkadiusz Kaliwoda (akaliwod)" <akaliwod@cisco.com>
To: "sunset4@ietf.org" <sunset4@ietf.org>
Thread-Topic: New draft: draft-kaliwoda-sunset4-dual-ipv6-coexist
Thread-Index: Ac2R+21YDslgOCGyRDSYxe7VZHlovw==
Date: Thu, 13 Sep 2012 22:04:05 +0000
Message-ID: <C7DD0A1145B71949BBD65DF56D408BA80F4EEE43@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.61.88.133]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19182.001
x-tm-as-result: No--31.518100-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: [sunset4] New draft: draft-kaliwoda-sunset4-dual-ipv6-coexist
X-BeenThere: sunset4@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: sunset4 working group discussion list <sunset4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sunset4>, <mailto:sunset4-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sunset4>
List-Post: <mailto:sunset4@ietf.org>
List-Help: <mailto:sunset4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sunset4>, <mailto:sunset4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Sep 2012 22:04:13 -0000

Hi All,

I have submitted a new draft “draft-kaliwoda-sunset4-dual-ipv6-coexist” that defines a problem of introducing IPv6/IPv4 translation service in IPv6 enabled network. I think this problem will have an impact on the transition from IPv4 to IPv6. 

IMHO today many operators are focused on adding IPv6 support in their network including access network and CPEs, in order to provide dual stack data service for their customers. Service Providers are also very much concerned on handling the IPv4 exhaust problem, especially when the number of subscribers thus hosts in the network keeps on increasing fast. Once these challenges are under control and as soon as more consumer devices are IPv6-ready, the process of sunsetting IPv4 will start for good. Not only in the SP network where 4over6 technologies are of key importance and where this transition has already started in some cases. More importantly in the context of this draft, the transition from IPv4 or dual-stack to IPv6-only will also start in the end hosts. If such transition starts sooner, of it has already started, then I think it makes the identified problem even more interesting and important.

I hope you will find the problem defined in the draft valid and relevant to the scope of SUNSET4 Working Group. 

Please find the links to the document and abstract below. 

Thank you for review of the draft and your comments.

Regards
Kali


-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Wednesday, September 12, 2012 9:43 PM
To: Arkadiusz Kaliwoda (akaliwod)
Subject: New Version Notification for draft-kaliwoda-sunset4-dual-ipv6-coexist-00.txt


A new version of I-D, draft-kaliwoda-sunset4-dual-ipv6-coexist-00.txt
has been successfully submitted by Arkadiusz Kaliwoda and posted to the IETF repository.

Filename:	 draft-kaliwoda-sunset4-dual-ipv6-coexist
Revision:	 00
Title:		 Co-existence of both dual-stack and IPv6-only hosts
Creation date:	 2012-09-12
WG ID:		 Individual Submission
Number of pages: 7
URL:             http://www.ietf.org/internet-drafts/draft-kaliwoda-sunset4-dual-ipv6-coexist-00.txt
Status:          http://datatracker.ietf.org/doc/draft-kaliwoda-sunset4-dual-ipv6-coexist
Htmlized:        http://tools.ietf.org/html/draft-kaliwoda-sunset4-dual-ipv6-coexist-00


Abstract:
   Some networks are expected to support IPv4-only, dual-stack, and
   IPv6-only hosts at the same time.  Such networks may want to add
   IPv6/IPv4 translation for the IPv6-only host so it can access servers
   on the IPv4 Internet.  Adding translation service to the IPv6-enabled
   network may change dual-stack host behavior and affect the way
   deployed network is working.  This document defines the problem
   statement for such networks.

                                                                                  


The IETF Secretariat