RE: New Version Notification for draft-donley-ipv6-cpe-rtr-use-cases-and-reqs-00

"Chris Donley" <C.Donley@cablelabs.com> Mon, 27 July 2009 07:13 UTC

Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 70BF428C134 for <ietfarch-v6ops-archive@core3.amsl.com>; Mon, 27 Jul 2009 00:13:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.319
X-Spam-Level: *
X-Spam-Status: No, score=1.319 tagged_above=-999 required=5 tests=[AWL=0.503, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_MODEMCABLE=0.768, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1, SARE_MILLIONSOF=0.315, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gTxIBwhAlKXi for <ietfarch-v6ops-archive@core3.amsl.com>; Mon, 27 Jul 2009 00:13:09 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 703B528C133 for <v6ops-archive@lists.ietf.org>; Mon, 27 Jul 2009 00:13:08 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD)) (envelope-from <owner-v6ops@ops.ietf.org>) id 1MVKJi-000PCW-Up for v6ops-data0@psg.com; Mon, 27 Jul 2009 07:08:14 +0000
Received: from [192.160.73.61] (helo=ondar.cablelabs.com) by psg.com with esmtp (Exim 4.69 (FreeBSD)) (envelope-from <C.Donley@cablelabs.com>) id 1MVKJe-000PBr-F3 for v6ops@ops.ietf.org; Mon, 27 Jul 2009 07:08:12 +0000
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.3/8.14.3) with SMTP id n6R788ib019948; Mon, 27 Jul 2009 01:08:08 -0600
Received: from srvxchg3.cablelabs.com (10.5.0.25) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/511/kyzyl.cablelabs.com); Mon, 27 Jul 2009 01:08:08 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/511/kyzyl.cablelabs.com)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CA0E88.FE5C2250"
Subject: RE: New Version Notification for draft-donley-ipv6-cpe-rtr-use-cases-and-reqs-00
Date: Mon, 27 Jul 2009 01:06:44 -0600
Message-ID: <B1ED8A2E683E16479C92C3F4AE13677B1D7B2F@srvxchg3.cablelabs.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: New Version Notification for draft-donley-ipv6-cpe-rtr-use-cases-and-reqs-00
Thread-Index: AcoOQMtN9l7MqlfBRQCrogEMnAWzxQASAGHq
References: <B1ED8A2E683E16479C92C3F4AE13677B01E1A92E@srvxchg3.cablelabs.com> <B00EDD615E3C5344B0FFCBA910CF7E1D07A0270F@xmb-rtp-20e.amer.cisco.com> <B1ED8A2E683E16479C92C3F4AE13677B01E1AD62@srvxchg3.cablelabs.com> <B00EDD615E3C5344B0FFCBA910CF7E1D07A76B2C@xmb-rtp-20e.amer.cisco.com> <alpine.DEB.1.10.0907262347580.4558@uplift.swm.pp.se>
From: Chris Donley <C.Donley@cablelabs.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>, v6ops@ops.ietf.org
X-Approved: ondar
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

>From our perspective, it was an inadvertent omission.  We're happy to rectify that in the future.

Chris


-----Original Message-----
From: owner-v6ops@ops.ietf.org on behalf of Mikael Abrahamsson
Sent: Sun 7/26/2009 3:51 PM
To: v6ops@ops.ietf.org
Subject: RE: New Version Notification for draft-donley-ipv6-cpe-rtr-use-cases-and-reqs-00
 
On Sun, 26 Jul 2009, Hemant Singh (shemant) wrote:

> Thanks for all your replies.  Indeed, what Wes and I did in our IETF
> IPv6 CPE Rtr doc is to try and write one common document that works for
> cable, DSL, and even 3GPP legacy wireless data networks (3GPP was
> low-hanging fruit for our document because with a few minor additions we
> could satisfy their demands).

I'd just want to clarify that my intent in my opinions regarding this 
draft was to make it work in ETTH deployments as well. I hope this was 
just an omission in listing technologies and not a statement from the 
authors regarding the intents of the document to exclude ETTH?

I don't know the extent of L2 switches used in delivering ETTH across the 
world, but I'd guess it's in the millions of subscribers getting their 
Internet access this way.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se