Re: [v6ops] [Fwd: I-D Action: draft-carpenter-v6ops-icp-guidance-02.txt]

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 01 February 2012 20:32 UTC

Return-Path: <brian.e.carpenter@gmail.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 54EB821F8666 for <v6ops@ietfa.amsl.com>; Wed, 1 Feb 2012 12:32:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.123
X-Spam-Level:
X-Spam-Status: No, score=-103.123 tagged_above=-999 required=5 tests=[AWL=-0.124, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 ZiieBUk1SRVr for <v6ops@ietfa.amsl.com>; Wed, 1 Feb 2012 12:32:37 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6DA7521F864D for <v6ops@ietf.org>; Wed, 1 Feb 2012 12:32:37 -0800 (PST)
Received: by iagf6 with SMTP id f6so2448530iag.31 for <v6ops@ietf.org>; Wed, 01 Feb 2012 12:32:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=tGxVjWAR3Ytlca210TrPXiz3FGdQJ66+5JUQtcaWVFs=; b=pQNSnYPr+20ZWuj5AOt1euhlTm7MZMRvxO/afqf1De9jaoB7iFm5/RKdgwM7fJmpc4 9OIlSCZVov1weTogzRungwJ4Ay7fxUN+6JRUye4tSghEhObG5eLhCl6XIX77LL7Oifbd QSzI4uhXGwiZ5CDXTKbIX5tTKCD35buk2zzsI=
Received: by 10.42.131.136 with SMTP id z8mr171475ics.5.1328128356919; Wed, 01 Feb 2012 12:32:36 -0800 (PST)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz. [130.216.38.124]) by mx.google.com with ESMTPS id ut1sm145704igc.2.2012.02.01.12.32.33 (version=SSLv3 cipher=OTHER); Wed, 01 Feb 2012 12:32:35 -0800 (PST)
Message-ID: <4F29A15F.7090202@gmail.com>
Date: Thu, 02 Feb 2012 09:32:31 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: IPv6 Operations <v6ops@ietf.org>
References: <4F0B975E.60604@gmail.com> <DCC302FAA9FE5F4BBA4DCAD46569377917375D4C85@PRVPEXVS03.corp.twcable.com>
In-Reply-To: <DCC302FAA9FE5F4BBA4DCAD46569377917375D4C85@PRVPEXVS03.corp.twcable.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Subject: Re: [v6ops] [Fwd: I-D Action: draft-carpenter-v6ops-icp-guidance-02.txt]
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, 01 Feb 2012 20:32:38 -0000

> I'm still on the fence about the draft status - I'm no longer opposed to adopting it as a WG item if that's the general consensus, but I think it would be ok as an individual draft as well.

May I ask the WG chairs to put that question to the WG? We can
of course make an update with the various comments received
recently, either as a WG draft or for individual submission,
as long as we get guidance by the end of this month.

Also do people want to use meeting time for this topic, or can
we handle it on the list?

Regards
   Brian Carpenter

On 2012-01-12 03:53, George, Wes wrote:
> Brian - Thanks for addressing my comments in this version.
> 
> I'm still on the fence about the draft status - I'm no longer opposed to adopting it as a WG item if that's the general consensus, but I think it would be ok as an individual draft as well.
> 
> A couple of additional comments from this read.
> 
> In your introduction, You mention the "first do no harm" concept - don't make IPv4 worse by deploying IPv6 (with the implication that some IPv6 transition technologies might have that effect).
> I think you might be able to take that a step further and note that IPv4 *extension* technologies (CGN, etc) on the client side may also have that effect, meaning that this is one of the reasons why ubiquitous IPv6 support (perhaps "on by default" even) is critical for ASP/ICP - it increases the chances that their service transits to an end customer largely unmolested by IPv4 extension technologies.
> 
> Additionally, it might be worth mentioning the connection between the ICP/ASP and their partners and their partner's uplinks - that is, if an ASP/ICP has a direct business relationship with the consumers/clients of their content or the networks that connect them to their clients, they should be working with those partners to ensure that they have a plan to enable IPv6 on their side (especially in implementations that require IPv6 support in specialized programs or systems for the IPv6 support on the ICP/ASP to be useful), and that they have first-class IPv6 connectivity between the networks. This coordination and testing detail is something that's sometimes overlooked, and while it's getting to a point where it might be a safe assumption that IPv6 is already available on the remote side, at this point it's worth mentioning explicitly.
> 
> Thanks,
> 
> Wes George
> 
>> -----Original Message-----
>> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf
>> Of Brian E Carpenter
>> Sent: Monday, January 09, 2012 8:42 PM
>> To: IPv6 Operations
>> Subject: [v6ops] [Fwd: I-D Action: draft-carpenter-v6ops-icp-guidance-
>> 02.txt]
>>
>> Hi,
>>
>> We've updated this according to the comments received since Taipei.
>>
>> At this point we'd like opinions about the future of the document.
>> Should it become a WG draft, or should we progress it as an
>> individual submission?
>>
>>     Brian
>>
>> -------- Original Message --------
>> Subject: I-D Action: draft-carpenter-v6ops-icp-guidance-02.txt
>> Date: Fri, 06 Jan 2012 11:37:09 -0800
>> From: internet-drafts@ietf.org
>> Reply-To: internet-drafts@ietf.org
>> To: i-d-announce@ietf.org
>>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>>
>>       Title           : IPv6 Guidance for Internet Content and
>> Application Service Providers
>>       Author(s)       : Brian Carpenter
>>                           Sheng Jiang
>>       Filename        : draft-carpenter-v6ops-icp-guidance-02.txt
>>       Pages           : 16
>>       Date            : 2012-01-06
>>
>>    This document provides guidance and suggestions for Internet Content
>>    Providers and Application Service Providers who wish to offer their
>>    service to both IPv6 and IPv4 customers.
>>
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-carpenter-v6ops-icp-guidance-
>> 02.txt
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> This Internet-Draft can be retrieved at:
>> ftp://ftp.ietf.org/internet-drafts/draft-carpenter-v6ops-icp-guidance-
>> 02.txt
>>
>> _______________________________________________
>> I-D-Announce mailing list
>> I-D-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/i-d-announce
>> Internet-Draft directories: http://www.ietf.org/shadow.html
>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>
>>
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
> 
> This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
>