Re: [homegate] Update on BOF / WG formation

Joe Touch <touch@isi.edu> Fri, 24 September 2010 15:07 UTC

Return-Path: <touch@isi.edu>
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 A96AB3A6B18 for <homegate@core3.amsl.com>; Fri, 24 Sep 2010 08:07:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.537
X-Spam-Level:
X-Spam-Status: No, score=-102.537 tagged_above=-999 required=5 tests=[AWL=0.062, 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 zshD7b8v3+md for <homegate@core3.amsl.com>; Fri, 24 Sep 2010 08:07:24 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id 6659F3A6B8F for <homegate@ietf.org>; Fri, 24 Sep 2010 08:07:13 -0700 (PDT)
Received: from [192.168.1.90] (pool-71-105-94-39.lsanca.dsl-w.verizon.net [71.105.94.39]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id o8OF7Dd3020394 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Fri, 24 Sep 2010 08:07:23 -0700 (PDT)
Message-ID: <4C9CBEA0.4050703@isi.edu>
Date: Fri, 24 Sep 2010 08:07:12 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
MIME-Version: 1.0
To: "Stephen [kiwin] PALM" <palm@broadcom.com>
References: <2BD6ED58-174E-451F-BA22-0C824629FBB7@nominet.org.uk> <4C9C831D.2050307@cisco.com> <85403065-B886-421E-9CAF-C98BB6031E7F@nominet.org.uk> <4C9CB8D2.8040105@broadcom.com>
In-Reply-To: <4C9CB8D2.8040105@broadcom.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Ray Bellis <Ray.Bellis@nominet.org.uk>, "homegate@ietf.org" <homegate@ietf.org>
Subject: Re: [homegate] Update on BOF / WG formation
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, 24 Sep 2010 15:07:25 -0000

FWIW, I view the first steps here along the lines of PILC, i.e., 
document best practices using existing protocols.

If that process hints that there are potential gaps, then I would expect 
we would/could be rechartered to determine the gaps, and indicate where 
and how they would be best addressed.

If there are gaps and no other WG is more appropriate to do the work, or 
if it needs to be coordinated, then we could try to recharter for that task.

I do agree with the current approach, though - not to jump in assuming 
this is a new architectural component, or that it requires new 
protocols, until we understand what's really missing first.

Joe

On 9/24/2010 7:42 AM, Stephen [kiwin] PALM wrote:
> I also had questioned some of the aims of the proposed group when other
> groups
> were doing most, if not all, of the same things (albeit wearing
> different hats)
>
> On 9/24/2010 4:30 AM, Ray Bellis wrote:
>>
>>> I think the question on the table now is whether it is worthwhile to
>>> charter homenet for just this type of work or not. I tend to think the
>>> answer to that is no, but I want to hear from the list first.
>>
>> For the avoidance of doubt, that is my position too.
>>
>> Ray
>>
>>
>>
>> _______________________________________________
>> homegate mailing list
>> homegate@ietf.org
>> https://www.ietf.org/mailman/listinfo/homegate
>>
>