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

Paul Hoffman <paul.hoffman@vpnc.org> Fri, 10 September 2010 00:12 UTC

Return-Path: <paul.hoffman@vpnc.org>
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 6A98F3A68E9 for <homegate@core3.amsl.com>; Thu, 9 Sep 2010 17:12:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.173
X-Spam-Level:
X-Spam-Status: No, score=-101.173 tagged_above=-999 required=5 tests=[AWL=0.873, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 OHwT2Szfqmsa for <homegate@core3.amsl.com>; Thu, 9 Sep 2010 17:12:11 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 6F6273A684A for <homegate@ietf.org>; Thu, 9 Sep 2010 17:12:11 -0700 (PDT)
Received: from [10.20.30.158] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o8A0CaGf061313 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Sep 2010 17:12:37 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0624086ac8af271ac630@[10.20.30.158]>
In-Reply-To: <4ED69024CE914E21A1AFF4B8759FAAF4@23FX1C1>
References: <14B94CC6-EA1D-44BD-9E01-457EB89C5E4E@nominet.org.uk> <p06240845c8aeaf99c3eb@[10.20.30.158]> <4ED69024CE914E21A1AFF4B8759FAAF4@23FX1C1>
Date: Thu, 09 Sep 2010 17:12:34 -0700
To: David Harrington <ietfdbh@comcast.net>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
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 00:12:12 -0000

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