Re: [homegate] HOMENET working group proposal

Keith Moore <moore@network-heretics.com> Fri, 01 July 2011 13:36 UTC

Return-Path: <moore@network-heretics.com>
X-Original-To: homegate@ietfa.amsl.com
Delivered-To: homegate@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8485011E8148; Fri, 1 Jul 2011 06:36:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.569
X-Spam-Level:
X-Spam-Status: No, score=-3.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oi6MpFJXu2Hr; Fri, 1 Jul 2011 06:36:34 -0700 (PDT)
Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 5406821F84D7; Fri, 1 Jul 2011 06:36:14 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.messagingengine.com (Postfix) with ESMTP id 5552B20905; Fri, 1 Jul 2011 09:36:12 -0400 (EDT)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute4.internal (MEProxy); Fri, 01 Jul 2011 09:36:12 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=qpQfdnE3I93odyBFsVX+LbxFeGs=; b=lUGVFN02KT0lSochgz5ZpIhKBdjHgELi0QT1TSItpDuRMfgJ29blkR+YfktT/xUZuV86O+fdGjB/jlNanGfWhjtAxRlKxrMy5DwPp8Bff3WcTWtVnVlDhJDhQHNWBrkTMrg650AZdsyRCFY43LHJtukQ6BkGyE/CWHP+kLCKV3k=
X-Sasl-enc: i0cKhgjK5+moYNIol8osIEUhU+TVYZyUBERv5RehBeVl 1309527371
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 3E91A40444B; Fri, 1 Jul 2011 09:36:11 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <0B6FEF9D-430B-4C56-BB21-40C5ED888B51@townsley.net>
Date: Fri, 1 Jul 2011 09:35:53 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A8AB09DB-AD86-4DB9-8980-53759EB2F1B9@network-heretics.com>
References: <4E0AE696.4020603@piuha.net> <4E0BDCF3.1090003@gont.com.ar> <alpine.DEB.2.00.1106300707370.19581@uplift.swm.pp.se> <4E0C1CF8.7090601@gont.com.ar> <alpine.DEB.2.00.1106300923280.19581@uplift.swm.pp.se> <558D0669-8B2A-4514-B3FB-C690C40A4EF8@townsley.net> <0F995E91-9853-4018-91F0-0699E1A7A06F@network-heretics.com> <780C3063-AD82-46F3-874A-C4E1E61EE508@townsley.net> <DC5C1553-38E9-4853-9AEA-61FC34FC5EC8@network-heretics.com> <0B6FEF9D-430B-4C56-BB21-40C5ED888B51@townsley.net>
To: Mark Townsley <mark@townsley.net>
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Fri, 01 Jul 2011 07:02:54 -0700
Cc: IETF Discussion <ietf@ietf.org>, homegate@ietf.org, fun@ietf.org
Subject: Re: [homegate] HOMENET working group proposal
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 01 Jul 2011 13:36:35 -0000

On Jul 1, 2011, at 4:53 AM, Mark Townsley wrote:

> The idea is not to go out of our way for IPv4, but if the topic is IP agnostic anyway, so be it. To be clear, there is no *requirement* to support IPv4 here. However, there is no requirement to avoid IPv4 *if* it doesn't cause significant concession in the IPv6 design either.
> 
> This cuts both ways, if there is something that is working well in IPv4 that we need to carry over to IPv6 with simple extensions, we'll do that and capitalizing on that running-code should be considered a good thing. We don't want to invent new v6 protocols from scratch that don't work with IPv4 when there is no need. For example (and I think this is hinted at in the charter), we might use naming and service discovery that already exists for IPv4, adapted the the v6 homenet. This doesn't mean we need to re-invent a v6-only naming system from scratch - i'd much rather use one that is there, which very well may support v4 and v6. 
> 
>> 
>> please don't constrain home networks to work only within the confines of IPv4 brain damage.
> 
> What I think I am saying here is that we will do our best to perform as if our brains are not damaged, and equally try to avoid damaging our brains in the process.

+1

Keith