Re: [fun] [IAB] Revised homenet charter for IESG consideration

Mark Townsley <townsley@cisco.com> Tue, 28 June 2011 14:34 UTC

Return-Path: <townsley@cisco.com>
X-Original-To: fun@ietfa.amsl.com
Delivered-To: fun@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F7D411E8108; Tue, 28 Jun 2011 07:34:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 qcU01oMwBSs5; Tue, 28 Jun 2011 07:34:09 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id AC01F11E80BE; Tue, 28 Jun 2011 07:34:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=townsley@cisco.com; l=1701; q=dns/txt; s=iport; t=1309271649; x=1310481249; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=d6OIVz5EgWXT5bVAJ6Mvl1/xtbXtCEfB+KuXj/UR6vs=; b=NwlAxc0AmCnG7CKf9czOu7vvE7hjS6iwb8Zaxqo02R2hYRS+Ud32oMdt c2FNt/1fwIskRjoLtIfskV/WsgQdFsrw5LaZXoh1WvUINWhUifp1yvKpK bk/VVZK9/RYNBEx9weC68oxVbnhXHZtCDM5jhVBzUdTm7gl3YQ0qEbVzR w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAJflCU6Q/khL/2dsb2JhbABSp0F3iHeic545hjAEkhCEbos1
X-IronPort-AV: E=Sophos;i="4.65,437,1304294400"; d="scan'208";a="39662729"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 28 Jun 2011 14:34:05 +0000
Received: from [64.103.29.80] ([64.103.29.80]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p5SEY5kE006883; Tue, 28 Jun 2011 14:34:05 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Mark Townsley <townsley@cisco.com>
X-Priority: 3
In-Reply-To: <3078175EB93B4A4C95E7ACC5F7701D77@china.huawei.com>
Date: Tue, 28 Jun 2011 16:34:03 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <2184F014-FEAD-4958-843F-8ED099D0A320@cisco.com>
References: <4E031DCD.1010606@piuha.net><BEF28DA8BF08419EA670A910D2438F28@davidPC> <A1B5DD3D-84B7-49BF-B02C-1E44346768AC@cisco.com> <3078175EB93B4A4C95E7ACC5F7701D77@china.huawei.com>
To: Spencer Dawkins <spencer@wonderhamster.org>
X-Mailer: Apple Mail (2.1084)
Cc: ipdir@ietf.org, 'IAB' <iab@iab.org>, 'IESG' <iesg@ietf.org>, fun@ietf.org
Subject: Re: [fun] [IAB] Revised homenet charter for IESG consideration
X-BeenThere: fun@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "FUture home Networking \(FUN\)" <fun.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/fun>, <mailto:fun-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/fun>
List-Post: <mailto:fun@ietf.org>
List-Help: <mailto:fun-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/fun>, <mailto:fun-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jun 2011 14:34:09 -0000

Thanks Spencer. For my part, I have no problem with your proposed text.

- Mark

On Jun 28, 2011, at 4:23 PM, Spencer Dawkins wrote:

> Dear INT ADs,
> 
> I don't want to interrupt the food fight just to ask someone to pass the salt, but ... :D
> 
> The current (last I saw) proposed charter for HOMENET didn't seem quite clear enough that having "as few subnets as possible" doesn't make the complexity of having multiple subnets go away. I was hoping that this could be stated a little more bluntly.
> 
> Could I suggest something like
> 
> OLD: o Multiple segments: While less complex L3-toplogies involving as few
> subnets as possible are preferred in home networks for a variety of
> reasons including simpler management and service discovery,
> incorporation of dedicated segments remain necessary for some
> cases. For instance, ... (excellent reasons deleted because I wasn't questioning them)
> 
> NEW: o Multiple segments: While less complex L3-toplogies involving as few subnets as possible are preferred in home networks for a variety of reasons including simpler management and service discovery, the introduction of more than one subnet into a home network is enough to add complexity that needs to be addressed, and multiple dedicated segments are necessary for some cases. For instance, ... (excellent reasons remain unchanged)
> 
> I hope this is a helpful comment, because I don't want to derail the general conversation by saying something NOT helpful.
> 
> Spencer 
> _______________________________________________
> fun mailing list
> fun@ietf.org
> https://www.ietf.org/mailman/listinfo/fun