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

"Chris Donley" <C.Donley@cablelabs.com> Thu, 23 July 2009 15:46 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 D16CE3A69F2 for <ietfarch-v6ops-archive@core3.amsl.com>; Thu, 23 Jul 2009 08:46:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.642
X-Spam-Level: *
X-Spam-Status: No, score=1.642 tagged_above=-999 required=5 tests=[AWL=0.542, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_MODEMCABLE=0.768, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_13=0.6, RDNS_NONE=0.1, 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 LxRloOIvoN9O for <ietfarch-v6ops-archive@core3.amsl.com>; Thu, 23 Jul 2009 08:46:01 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 015173A6783 for <v6ops-archive@lists.ietf.org>; Thu, 23 Jul 2009 08:46:01 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD)) (envelope-from <owner-v6ops@ops.ietf.org>) id 1MU0Qf-000Af8-4p for v6ops-data0@psg.com; Thu, 23 Jul 2009 15:41:57 +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 1MU0Qb-000Aeh-EZ for v6ops@ops.ietf.org; Thu, 23 Jul 2009 15:41:55 +0000
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.3/8.14.3) with SMTP id n6NFfoNT019475; Thu, 23 Jul 2009 09:41:50 -0600
Received: from srvxchg3.cablelabs.com (10.5.0.25) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/511/kyzyl.cablelabs.com); Thu, 23 Jul 2009 09:41:50 -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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: New Version Notification for draft-donley-ipv6-cpe-rtr-use-cases-and-reqs-00
Date: Thu, 23 Jul 2009 09:41:50 -0600
Message-ID: <B1ED8A2E683E16479C92C3F4AE13677B01E1AD74@srvxchg3.cablelabs.com>
In-Reply-To: <4A67B6F2.7050608@gmail.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: AcoLMWoilbuFx/WWTBuX+YiM8X1QjAAepIGA
References: <B1ED8A2E683E16479C92C3F4AE13677B01E1A92E@srvxchg3.cablelabs.com> <B00EDD615E3C5344B0FFCBA910CF7E1D07A0270F@xmb-rtp-20e.amer.cisco.com> <B1ED8A2E683E16479C92C3F4AE13677B01E1AD62@srvxchg3.cablelabs.com> <4A67B6F2.7050608@gmail.com>
From: Chris Donley <C.Donley@cablelabs.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: "Hemant Singh (shemant)" <shemant@cisco.com>, v6ops@ops.ietf.org, "Wes Beebee (wbeebee)" <wbeebee@cisco.com>
X-Approved: ondar
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

Brian,

We'd be amenable to that approach (combining the documents, if
possible).

Chris

-----Original Message-----
From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com] 
Sent: Wednesday, July 22, 2009 7:04 PM
To: Chris Donley
Cc: Hemant Singh (shemant); v6ops@ops.ietf.org; Wes Beebee (wbeebee)
Subject: Re: New Version Notification for
draft-donley-ipv6-cpe-rtr-use-cases-and-reqs-00

Chris,

On 2009-07-23 11:03, Chris Donley wrote:
> Hemant,
> 
> Thanks for your feedback.  
> 
> One of the issues that we have with the v6ops CPE Router draft is that
> it is hard to tell what is base functionality, what is optional, and
> what is architecture-dependent.  We present our draft to the working
> group as a complement to the v6ops CPE Router draft to detail our use
> cases, architectural assumptions, and requirements. While this draft
is
> specific to our needs, we believe that most of our draft is applicable
> to the wider community, and that a final document should address the
use
> cases and requirements of the wider community; we don't presume to
speak
> for the Broadband Forum or other groups, and encourage them to share
> their use cases/requirements, as well. 
> 
> As you suggested, there is a significant degree of overlap between our
> respective drafts.  That is intentional.  We tried to align as much as
> possible to avoid confusion. 

But I'm afraid that's impossible. Two overlapping documents = confusion,
by definition. I think the only reasonable goal is a combined document,
or possibly two complementary documents.

It's very encouraging to see use-case driven work in this area of
course.
It would be well worth while the effort of integrating the two drafts.

    brian