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

Ole Troan <otroan@employees.org> Thu, 13 October 2011 07:52 UTC

Return-Path: <ichiroumakino@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 00C4321F8AEE for <v6ops@ietfa.amsl.com>; Thu, 13 Oct 2011 00:52:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level:
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[AWL=-0.300, 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 pWRPNDcU2qVE for <v6ops@ietfa.amsl.com>; Thu, 13 Oct 2011 00:52:19 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2707E21F8AEA for <v6ops@ietf.org>; Thu, 13 Oct 2011 00:52:19 -0700 (PDT)
Received: by wwf22 with SMTP id 22so879133wwf.13 for <v6ops@ietf.org>; Thu, 13 Oct 2011 00:52:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=rxwoXFvt//UjeHIGN26pR6TjJ2+QbdrvSE5QEDISHTI=; b=XmsESt0IAXC0UVQBAHK3nsLZzk+87xqHS9YAUw+L/Vp60yY91AQHPQg4V0hOKsA106 phmOozGa4cBr4IQCsMRHkfEIdTMDahyMyjAUJ7f33Tm7WYr8NRRXyh89NkNM5roL3PuV Kv1n1euBQGTREvkO0fXzw5UQpLsSOBTkxVpFU=
Received: by 10.227.179.76 with SMTP id bp12mr850022wbb.82.1318492338188; Thu, 13 Oct 2011 00:52:18 -0700 (PDT)
Received: from dhcp-osl-vl300-64-103-53-235.cisco.com (dhcp-osl-vl300-64-103-53-235.cisco.com. [64.103.53.235]) by mx.google.com with ESMTPS id l40sm4450691wbm.10.2011.10.13.00.52.16 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 13 Oct 2011 00:52:17 -0700 (PDT)
Sender: Ole Troan <ichiroumakino@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="iso-8859-1"
From: Ole Troan <otroan@employees.org>
In-Reply-To: <282BBE8A501E1F4DA9C775F964BB21FE3EB758B7B3@GRFMBX704BA020.griffon.local>
Date: Thu, 13 Oct 2011 09:52:14 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <7C1ED2F7-0562-4DE7-95B7-6ED266D69916@employees.org>
References: <201110111355.p9BDt1M23806@ftpeng-update.cisco.com><282BBE8A501E1F4DA9C775F964BB21FE3EB758B7A8@GRFMBX704BA020.griffon.local><1B8E4C5A-D08B-4F37-B701-A39745136A33@cisco.com><4E95ED46.1010404@viagenie.ca> <24BE1240-F514-4408-BEE6-F37A9AB1E932@cisco.com> <750BF7861EBBE048B3E648B4BB6E8F4F1FE5E08D@crexc50p> <282BBE8A501E1F4DA9C775F964BB21FE3EB758B7B3@GRFMBX704BA020.griffon.local>
To: Maglione Roberta <roberta.maglione@telecomitalia.it>
X-Mailer: Apple Mail (2.1084)
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] new draft: draft-ietf-v6ops-6204bis
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: Thu, 13 Oct 2011 07:52:20 -0000

Roberta,

> I agree with Barbara: it would be better to have all the requirements related to IPv4/IPv6 migration in a single document.
> When we talk about IPv6 migration we always consider also the phase of IPv4/IPv6 co-existence in order to make the transition happening. I mentioned CGN, but what I had in mind is the DS-Lite case where CGN is embedded in the AFTR and PCP fits in this scenario.

"Basic requirements for IPv4/IPv6 transition for CE routers"?

cheers,
Ole

> -----Original Message-----
> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of STARK, BARBARA H
> Sent: mercoledì 12 ottobre 2011 23.18
> To: Fred Baker; Simon Perreault
> Cc: v6ops@ietf.org
> Subject: Re: [v6ops] new draft: draft-ietf-v6ops-6204bis
> 
>> I'm not certain that an IPv6 CPE Routers document should be giving
>> instructions for IPv4 CPE Routers... I'd personally rather keep this
>> one clean and pull the rest into an IPv4-related draft. Color me
>> biased.
> 
> That's ok. I'm biased too. Just differently.
> 
> My bias is:
> Extending the life of IPv4 and deploying IPv6 are not separate topics.
> The same people are working on both, simultaneously, in order to provide
> a holistic solution. While the access network may have many physical
> components, and support connecting to different customers in a variety
> of ways, it is engineered and designed as a whole. The vast majority of
> consumer-grade customers aren't asking for IPv6 or IPv4. They want their
> Internet connection to work. A single CE router must be able to provide
> them with this working Internet connection. And since it all goes into
> one CE router, it would be better if the CE router vendor could find it
> in one document. The more places they have to look, the more likely it
> is they'll miss something.
> 
> My preference is one document to describe all the stuff needed to
> provide that working Internet connection.
> We didn't need all the other IPv4 stuff, because we were working off an
> assumption that CE router vendors already had that working, and weren't
> looking for guidance.
> I'd rather change the document scope than not provide guidance on new
> capabilities that are critical for having a functioning Internet
> connection.
> Barbara
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
> 
> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.
> 
> This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops