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

"STARK, BARBARA H" <bs7652@att.com> Wed, 12 October 2011 21:17 UTC

Return-Path: <bs7652@att.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 F35A221F8BAC for <v6ops@ietfa.amsl.com>; Wed, 12 Oct 2011 14:17:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.197
X-Spam-Level:
X-Spam-Status: No, score=-106.197 tagged_above=-999 required=5 tests=[AWL=0.402, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 rlViBVy7jS4M for <v6ops@ietfa.amsl.com>; Wed, 12 Oct 2011 14:17:59 -0700 (PDT)
Received: from mail119.messagelabs.com (mail119.messagelabs.com [216.82.241.195]) by ietfa.amsl.com (Postfix) with ESMTP id 5747C21F8B57 for <v6ops@ietf.org>; Wed, 12 Oct 2011 14:17:59 -0700 (PDT)
X-Env-Sender: bs7652@att.com
X-Msg-Ref: server-3.tower-119.messagelabs.com!1318454277!44072468!1
X-Originating-IP: [144.160.20.146]
X-StarScan-Version: 6.3.6; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 1162 invoked from network); 12 Oct 2011 21:17:57 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-3.tower-119.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 12 Oct 2011 21:17:57 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id p9CLGZk2008392; Wed, 12 Oct 2011 17:16:36 -0400
Received: from 01GAF5142010624.AD.BLS.COM (01GAF5142010624.ad.bls.com [139.76.131.91]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with SMTP id p9CLGAEU007835; Wed, 12 Oct 2011 17:16:30 -0400
Received: from 01NC27689010627.AD.BLS.COM ([90.144.44.202]) by 01GAF5142010624.AD.BLS.COM with Microsoft SMTPSVC(6.0.3790.4675); Wed, 12 Oct 2011 17:16:58 -0400
Received: from 01NC27689010650.AD.BLS.COM ([90.144.44.120]) by 01NC27689010627.AD.BLS.COM with Microsoft SMTPSVC(6.0.3790.4675); Wed, 12 Oct 2011 17:16:57 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 12 Oct 2011 17:17:40 -0400
Message-ID: <750BF7861EBBE048B3E648B4BB6E8F4F1FE5E08D@crexc50p>
In-Reply-To: <24BE1240-F514-4408-BEE6-F37A9AB1E932@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [v6ops] new draft: draft-ietf-v6ops-6204bis
Thread-Index: AcyJIdMjn9Yf1dpFRTWf0wxGsEhNUQAAYYXw
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>
From: "STARK, BARBARA H" <bs7652@att.com>
To: Fred Baker <fred@cisco.com>, Simon Perreault <simon.perreault@viagenie.ca>
X-OriginalArrivalTime: 12 Oct 2011 21:16:57.0688 (UTC) FILETIME=[46392580:01CC8924]
Cc: 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: Wed, 12 Oct 2011 21:18:00 -0000

> 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