Re: [homegate] Proposed Charter Update - 2010/09/09

"David Harrington" <ietfdbh@comcast.net> Fri, 10 September 2010 02:56 UTC

Return-Path: <ietfdbh@comcast.net>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A688D3A67EC for <homegate@core3.amsl.com>; Thu, 9 Sep 2010 19:56:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.193
X-Spam-Level:
X-Spam-Status: No, score=-102.193 tagged_above=-999 required=5 tests=[AWL=0.406, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Uvqv7Yv3dusR for <homegate@core3.amsl.com>; Thu, 9 Sep 2010 19:56:44 -0700 (PDT)
Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [76.96.59.211]) by core3.amsl.com (Postfix) with ESMTP id 956103A6781 for <homegate@ietf.org>; Thu, 9 Sep 2010 19:56:44 -0700 (PDT)
Received: from omta01.westchester.pa.mail.comcast.net ([76.96.62.11]) by QMTA11.westchester.pa.mail.comcast.net with comcast id 4n9l1f0030EZKEL5BqxC6h; Fri, 10 Sep 2010 02:57:12 +0000
Received: from 23FX1C1 ([67.189.235.106]) by omta01.westchester.pa.mail.comcast.net with comcast id 4qxC1f0082JQnJT3MqxC5a; Fri, 10 Sep 2010 02:57:12 +0000
From: David Harrington <ietfdbh@comcast.net>
To: 'Paul Hoffman' <paul.hoffman@vpnc.org>
References: <14B94CC6-EA1D-44BD-9E01-457EB89C5E4E@nominet.org.uk> <p06240845c8aeaf99c3eb@[10.20.30.158]> <4ED69024CE914E21A1AFF4B8759FAAF4@23FX1C1> <p0624086ac8af271ac630@[10.20.30.158]>
Date: Thu, 09 Sep 2010 22:56:47 -0400
Message-ID: <BCAD6657898742249BA464932D0D70AC@23FX1C1>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <p0624086ac8af271ac630@[10.20.30.158]>
Thread-Index: ActQfOGF46m2BCcWR32sezqBD5+CNQAFK3cw
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
Cc: homegate@ietf.org
Subject: Re: [homegate] Proposed Charter Update - 2010/09/09
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homegate>
List-Post: <mailto:homegate@ietf.org>
List-Help: <mailto:homegate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Sep 2010 02:56:45 -0000

Hi,

Initial can be individual, adopted later.
Arch doc can morph while the WG decides on scope and priorities, and
finish after recharter.
I don't see a problem.

Maybe we have different assumptions about the contents of the arch
doc.
Home networks take many forms, so I don't see one stable architecture.
If the WG reaches consensus on home network arch contents and finishes
earlier than I anticipate, that's fine.

Ray raised a point - is the arch doc about home network design, or is
it a framework that describes how various technologies (the seven
bullets) fit together?

dbh

> -----Original Message-----
> From: Paul Hoffman [mailto:paul.hoffman@vpnc.org] 
> Sent: Thursday, September 09, 2010 8:13 PM
> To: David Harrington
> Cc: homegate@ietf.org
> Subject: Re: [homegate] Proposed Charter Update - 2010/09/09
> 
> OK, that all makes sense. I did not understand that the 
> purpose of the many drafts on many topics was to help the 
> rechartering effort. However, we still have some issues. The 
> current proposal is:
> 
> >Goals and Milestones:
> >---------------------
> >
> >Nov 2010 - Initial revision of a Home Network Architecture 
> document Mar 
> >2011 - Adopt a Home Network Architecture document as a WG 
> item Mar 2011 
> >- Individual drafts as WG candidates for Routed home 
> requirements Mar 
> >2011 - Individual drafts as WG candidates for Simple naming 
> >requirements Mar 2011 - Individual drafts as WG candidates for 
> >Multi-homing requirements Mar 2011 - Individual drafts as WG 
> candidates 
> >for QoS requirements Mar 2011 - Individual drafts as WG 
> candidates for 
> >Security requirements Mar 2011 - Individual drafts as WG 
> candidates for 
> >DNSSEC requirements Jul 2011 - Recharter the working group 
> Dec 2011 - 
> >Submission of the Home Network Architecture document to the IESG
> 
> Given what you said, I do not understand the first two and last
line.
> 
> - Why would the WG not adopt the early version of the Home 
> Network Architecture document?
> 
> - Why would the IESG want the WG to recharter when the WG 
> still hasn't agreed on the contents of the Home Network 
> Architecture document?
> 
> --Paul Hoffman, Director
> --VPN Consortium