Re: [v6ops] draft-ietf-v6ops-6204bis WGLC

Mark Townsley <mark@townsley.net> Fri, 23 March 2012 22:49 UTC

Return-Path: <mark@townsley.net>
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 E625F21F8522 for <v6ops@ietfa.amsl.com>; Fri, 23 Mar 2012 15:49:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.892
X-Spam-Level:
X-Spam-Status: No, score=-2.892 tagged_above=-999 required=5 tests=[AWL=0.107, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
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 AxrhOCS7Gunl for <v6ops@ietfa.amsl.com>; Fri, 23 Mar 2012 15:49:11 -0700 (PDT)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2332321F851E for <v6ops@ietf.org>; Fri, 23 Mar 2012 15:49:10 -0700 (PDT)
Received: by werb10 with SMTP id b10so3587999wer.31 for <v6ops@ietf.org>; Fri, 23 Mar 2012 15:49:10 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=subject:mime-version:from:in-reply-to:date:cc:message-id:references :to:x-mailer:x-gm-message-state:content-type :content-transfer-encoding; bh=sYB9204mdsEktQ8813H5/N2x9BQS9USlIUGA9/HgnsE=; b=lQH+9jaOU6uAssT6ExM6H1rn1CK5GoN6XrZOyVoS2sg51LB96xjlhPpOyh1SRuY57V w/UrIBI+Oni051vvHjBthdIZyX3c6eZ35H6NAacKrSLDiMvWodUJ0BF9VeZqQgKuMLXA qSeBrc22JqyYURF2+3lO6wjK5NwWfFPRFtJGtpeza0awkWPx08302CVlLOMZHuP8orBl 0pNzbDErgnJxZwVklhi+mVyZv7YeFuc/qVsE5VZjzUPHsOfyEjCzFQWxCRjdEiB3PSWj EH3XQxGJapNXU8PxweVkNEjJGT9PGlnI+zf0A34d5GXlQUOl39tcFhDm2j8a8ldme7Om MeVQ==
Received: by 10.180.79.135 with SMTP id j7mr651457wix.19.1332542950310; Fri, 23 Mar 2012 15:49:10 -0700 (PDT)
Received: from ams-townsley-8914.cisco.com (64-103-25-233.cisco.com. [64.103.25.233]) by mx.google.com with ESMTPS id l5sm17579978wia.11.2012.03.23.15.49.07 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 23 Mar 2012 15:49:08 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1257)
From: Mark Townsley <mark@townsley.net>
In-Reply-To: <6A0BFABB-225C-4D14-83F5-4398AF0E5CC3@cisco.com>
Date: Fri, 23 Mar 2012 23:49:05 +0100
Message-Id: <A2297077-2804-407E-9971-5459F0E39806@townsley.net>
References: <6A0BFABB-225C-4D14-83F5-4398AF0E5CC3@cisco.com>
To: Fred Baker <fred@cisco.com>
X-Mailer: Apple Mail (2.1257)
X-Gm-Message-State: ALoCoQkHTB7imna/StEEgSEO8S/hIdIUxc6OliWylj8uJ10LUV5Ns7YE/j6Ru3xJ46J23Yd+dcxY
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: v6ops@ietf.org, v6ops-chairs@tools.ietf.org, Ron Bonica <ron@bonica.org>
Subject: Re: [v6ops] draft-ietf-v6ops-6204bis WGLC
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: Fri, 23 Mar 2012 22:49:12 -0000

The current description of 6rd and ds-lite in 6204bis dangerously avoids the issue of how to gracefully transition from a native IPv4 to Dual-Stack lite, in particular with a retail CPE vs. ISP-managed CPE. The same is true for graceful sunsetting of 6rd to native IPv6.

Ole and I captured the rather heated discussion on v6ops a couple of months back in the following document: draft-townsley-troan-ipv6-ce-transitioning-02

I believe the problem here is that there is demand from operators to include DS-Lite and 6rd in this document is very strong, yet the implementation details have not been specified well enough to allow DS-Lite and Native IPv4 or Native IPv6 and 6rd to coexist in a consistent and non-distruptive manner with one another. This is fairly dangerous as it will undoubtedly lead to highly variant implementation. I can easily see this sinking the ability to incrementally deploy DS-Lite in a retail CPE setting, for example. It could also be detrimental to sunsetting of 6rd.

I'd be happy to present the issue to v6ops. I think the issue needs to be voiced (as the draft appeared since the last meeting, it has not had airtime in any IETF meeting yet, despite us revving a couple of times). 

- Mark
 

On Mar 8, 2012, at 10:30 PM, Fred Baker wrote:

> This is to initiate a two week working group last call of draft-ietf-v6ops-6204bis. Please read it now. If you find nits (spelling errors, minor suggested wording changes, etc), comment to the authors; if you find greater issues, such as disagreeing with a statement or finding additional issues that need to be addressed, please post your comments to the list. The draft will be on the agenda at IETF 83, and I would like to send the authors home with a work plan to complete it if it is not to the WG's liking.
> 
> We are looking specifically for comments on the importance of the document as well as its content. If you have read the document and believe it to be of operational utility, that is also an important comment to make.
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops